-
Notifications
You must be signed in to change notification settings - Fork 534
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
Comments
I would like to note that since upgrading my PCs to Xubuntu 13.10 I no longer see this issue. |
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:
|
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 |
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. |
@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. |
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. |
Although I'm using the FUNcube Dongle Pro (and not Pro+), I think I stumbled upon this error, getting the very same 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:
|
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. 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 |
@csete Is this till reproducible? |
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.
The text was updated successfully, but these errors were encountered: