New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Funcube Dongle Pro+ reports not enough bandwidth #91

Open
csete opened this Issue Jul 23, 2013 · 8 comments

Comments

4 participants
@csete
Owner

csete commented Jul 23, 2013

On some systems, the kernel driver will erroneously report "not enough bandwidth" when the Funcube Dongle Pro+ is attached to a USB2 or USB3 port, leaving the fcdpp unusable.

To check whether you have this issue, insert your FCD Pro+ and type dmesg. If you see the message "not enough bandwidth" in one of the last lines your are having this issue.

See the discussion here: #88
Kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=60581

A workaround is to reattach the device to a USB1, USB2 or USB3 port (depending on which driver is failing) or via a USB1 hub.

USB3 ports seem to work as well.

@csete

This comment has been minimized.

Show comment
Hide comment
@csete

csete Feb 25, 2014

Owner

I would like to note that since upgrading my PCs to Xubuntu 13.10 I no longer see this issue.

Owner

csete commented Feb 25, 2014

I would like to note that since upgrading my PCs to Xubuntu 13.10 I no longer see this issue.

@fsphil

This comment has been minimized.

Show comment
Hide comment
@fsphil

fsphil Apr 16, 2014

Ever find out anything more about this? I just upgraded my laptop to something a bit faster to run gqrx and discovered that I can't use the FCDP+ on it. The original FCD works fine.

gqrx is giving me "aOaO" and the kernel is complaining about:

[21284.010978] ALSA sound/usb/clock.c:309 6:1:1: cannot get freq at ep 0x81
[21284.013917] ALSA sound/usb/endpoint.c:910 cannot submit urb 0, error -28: not enough bandwidth

fsphil commented Apr 16, 2014

Ever find out anything more about this? I just upgraded my laptop to something a bit faster to run gqrx and discovered that I can't use the FCDP+ on it. The original FCD works fine.

gqrx is giving me "aOaO" and the kernel is complaining about:

[21284.010978] ALSA sound/usb/clock.c:309 6:1:1: cannot get freq at ep 0x81
[21284.013917] ALSA sound/usb/endpoint.c:910 cannot submit urb 0, error -28: not enough bandwidth
@csete

This comment has been minimized.

Show comment
Hide comment
@csete

csete Apr 16, 2014

Owner

I'm not actively doing anything on this issue at the moment. When I get updates I post them here. Some other people have posted updates on issue #88

Owner

csete commented Apr 16, 2014

I'm not actively doing anything on this issue at the moment. When I get updates I post them here. Some other people have posted updates on issue #88

@fsphil

This comment has been minimized.

Show comment
Hide comment
@fsphil

fsphil Nov 21, 2014

The recently released 96kHz firmware seems to work around this problem. It's not quite playing right still, I suspect gqrx is still treating it as a 19200kHz stream. Need to hack at it a bit more.

http://www.funcubedongle.com/?p=1647

fsphil commented Nov 21, 2014

The recently released 96kHz firmware seems to work around this problem. It's not quite playing right still, I suspect gqrx is still treating it as a 19200kHz stream. Need to hack at it a bit more.

http://www.funcubedongle.com/?p=1647

@csete

This comment has been minimized.

Show comment
Hide comment
@csete

csete Nov 21, 2014

Owner

@fsphil You should be able to select any sample rate in gqrx. It is a drop down list where you can enter any value manually. But let me know if it doesn't work.

Owner

csete commented Nov 21, 2014

@fsphil You should be able to select any sample rate in gqrx. It is a drop down list where you can enter any value manually. But let me know if it doesn't work.

@fsphil

This comment has been minimized.

Show comment
Hide comment
@fsphil

fsphil Nov 22, 2014

Yea I can change the text in the sample rate box but it has no effect. The problem seems to be in gr-osmosdr, it (fairly) assumes the FCDP+ is always 192kHz. Changing this to 96khz gets everything playing fine. I'll see if I can come up with a smarter solution.

fsphil commented Nov 22, 2014

Yea I can change the text in the sample rate box but it has no effect. The problem seems to be in gr-osmosdr, it (fairly) assumes the FCDP+ is always 192kHz. Changing this to 96khz gets everything playing fine. I'll see if I can come up with a smarter solution.

@glmax

This comment has been minimized.

Show comment
Hide comment
@glmax

glmax Jun 25, 2016

Although I'm using the FUNcube Dongle Pro (and not Pro+), I think I stumbled upon this error, getting the very same not enough bandwidth along with the aOs on the console.

One thing I noticed is that not only gqrx has this error. The FCD Source block of GNURadio shows the exact same behavior in the same situations. So it looks like gqrx on its own doesn't cause the problem.

Apart from that, I found out that the problem occurs (at least for me, Arch 4.6.2) when certain kinds of USB devices are plugged in during the moment in which the actual RF reception is started. Plugging in such a device when the reception is already running does not cause any problem.

I tried out some devices:

  • Plugged in mouses and keyboards didn't work.
  • My mobile phone which (without further drivers) only serves as a card reader for its microSD card didn't work.
  • Printers or external USB storage devices like simple UBS sticks, HDDs or a USB card reader stick worked.

glmax commented Jun 25, 2016

Although I'm using the FUNcube Dongle Pro (and not Pro+), I think I stumbled upon this error, getting the very same not enough bandwidth along with the aOs on the console.

One thing I noticed is that not only gqrx has this error. The FCD Source block of GNURadio shows the exact same behavior in the same situations. So it looks like gqrx on its own doesn't cause the problem.

Apart from that, I found out that the problem occurs (at least for me, Arch 4.6.2) when certain kinds of USB devices are plugged in during the moment in which the actual RF reception is started. Plugging in such a device when the reception is already running does not cause any problem.

I tried out some devices:

  • Plugged in mouses and keyboards didn't work.
  • My mobile phone which (without further drivers) only serves as a card reader for its microSD card didn't work.
  • Printers or external USB storage devices like simple UBS sticks, HDDs or a USB card reader stick worked.
@dl1ksv

This comment has been minimized.

Show comment
Hide comment
@dl1ksv

dl1ksv Jun 26, 2016

Contributor

This is a kernel issue that I experienced with the funcube dongle and the funcube pro+. It depends on the usb controller hardware. In my case it was a usb3 one.
I reported a bug on kernel.org
See Bug 70531

Starting with kernel 3.19 this problem was solved (perhaps only for my system ) , although other problems arise. But in most cases the system is usable. Gnuradio and gqrx both work.

Meanwhile I'm using a kernel 4.5

Contributor

dl1ksv commented Jun 26, 2016

This is a kernel issue that I experienced with the funcube dongle and the funcube pro+. It depends on the usb controller hardware. In my case it was a usb3 one.
I reported a bug on kernel.org
See Bug 70531

Starting with kernel 3.19 this problem was solved (perhaps only for my system ) , although other problems arise. But in most cases the system is usable. Gnuradio and gqrx both work.

Meanwhile I'm using a kernel 4.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment