Hide Forgot
Description of problem: The kernel loads the firmware first time for this stick. However if you unplug and plug in the stick, it fails to reload the firmware, saying: Feb 1 19:25:40 spin kernel: [3311344.655369] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware Feb 1 19:26:41 spin kernel: [3311405.298283] dvb-usb: did not find the firmware file. (dvb-usb-dib0700-1.20.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2) The "solution" to this is to: (1) unplug the stick (2) kill gnome-dvb-daemon (generally a good idea anyway since this is a crap bit of software) (3) modprobe -r dvb_usb_dib0700 (4) modprobe -r dvb_usb (5) plug in the stick (6) it now succeeds to load the firmware Version-Release number of selected component (if applicable): 3.2.0-0.rc1.git2.1.fc17.x86_64 How reproducible: 100%
This Ubuntu bug seems relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/388383
I'm guessing latest rawhide (3.3.0-0.rc2.git0.2.fc17) exhibits the same issue? 3.2-rc1 is rather stale. Mauro?
Sorry for the delay. I updated my kernel the other day and the same issue occurs with this kernel: Linux spin.home.annexia.org 3.3.0-0.rc2.git4.1.fc17.x86_64 #1 SMP Mon Feb 6 17:53:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
I'm seeing this too, on a Freecom DVB stick ("WideView WT-220U PenType Receiver (Typhoon/Freecom)"). I'm running a fully up to date Fedora 17 installation.
I too see this with a Freecom DVB stick on a Fresh FC17 install. dvb-usb-wt220u-02.fw firmware uname -rv 3.4.4-5.fc17.x86_64 #1 SMP Thu Jul 5 20:20:59 UTC 2012 udev-182-3.fc17.x86_64 Please advise which/any logs would be required for debugging. Thanks.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Is this still an issue with the 3.9 kernels in F19?
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.