[Bug 753734] New: Base:System/udev: Bug iwlwifi firmware load error
https://bugzilla.novell.com/show_bug.cgi?id=753734 https://bugzilla.novell.com/show_bug.cgi?id=753734#c0 Summary: Base:System/udev: Bug iwlwifi firmware load error Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: rmilasan@suse.com ReportedBy: scalpel4k@gmail.com QAContact: opensuse-communityscreening@forge.provo.novell.com Found By: --- Blocker: --- the latest update udev-181 does not load the iwlwifi firmware anymore. Consequently wifi does no lobger work. I switched back to the last version 173 which solves the problem for me right now. I also realized that there is no more /lib/udev/rules.d/50-firmware.rules file in the rpm. I tried to use the old rules file but that didn't work. I use the packages from Base:System if available otherwise from Factory. This is the syslog output:
Mar 18 19:27:32 linux01 kernel: [ 5.258542] iwlwifi 0000:0c:00.0: device EEPROM VER=0x120, CALIB=0x4 Mar 18 19:27:32 linux01 kernel: [ 5.258545] iwlwifi 0000:0c:00.0: Device SKU: 0xF0 Mar 18 19:27:32 linux01 kernel: [ 5.258556] iwlwifi 0000:0c:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels Mar 18 19:27:32 linux01 kernel: [ 5.259937] iwlwifi 0000:0c:00.0: request for firmware file 'iwlwifi-5000-5.ucode' failed. Mar 18 19:27:32 linux01 kernel: [ 5.260522] iwlwifi 0000:0c:00.0: request for firmware file 'iwlwifi-5000-4.ucode' failed. Mar 18 19:27:32 linux01 kernel: [ 5.261572] iwlwifi 0000:0c:00.0: request for firmware file 'iwlwifi-5000-3.ucode' failed. Mar 18 19:27:32 linux01 kernel: [ 5.262023] iwlwifi 0000:0c:00.0: request for firmware file 'iwlwifi-5000-2.ucode' failed. Mar 18 19:27:32 linux01 kernel: [ 5.264825] iwlwifi 0000:0c:00.0: request for firmware file 'iwlwifi-5000-1.ucode' failed. Mar 18 19:27:32 linux01 kernel: [ 5.264879] iwlwifi 0000:0c:00.0: no suitable firmware found!
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c1
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c2
Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c3
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c4
Luca Beltrame
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c5
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c6
--- Comment #6 from Luca Beltrame
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c7
--- Comment #7 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c8
--- Comment #8 from Luca Beltrame
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c9
--- Comment #9 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c10
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c11
--- Comment #11 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c12
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c13
Jiri Slaby
You should try again, it should have been fixed in the latest update. The problem was or seems it was the missing /usr/lib/firmware link.
Of course I did. But it still doesn't work. What kind of debug info should I provide? # ll /usr/lib/firmware lrwxrwxrwx 1 root root 13 25. dub 09.27 /usr/lib/firmware -> /lib/firmware # rpm -q `rpmqpack |egrep 'kmod|udev'|sort` kmod-8-2.1.x86_64 libgudev-1_0-0-182-2.1.x86_64 libkmod2-8-2.1.x86_64 libmikmod-3.1.12-15.5.x86_64 libudev-devel-182-2.1.x86_64 libudev0-182-2.1.x86_64 libudev0-32bit-182-2.1.x86_64 udev-182-2.1.x86_64 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c14
--- Comment #14 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c15
Jiri Slaby
Well you can enable debuggin in udev in /etc/udev/udev.conf change udev_log=err to udev_log=debug, then just reboot. Take /var/log/syslog from your system and attach it here.
The sequence is: * I plug the device * kernel sends an uevent (FIRMWARE/add), timeout=60 * udev sleeps 60s * udev wakes up, forks firmware loader (there is no FW dir at this time) Log extracted: 45:34 kernel: dvb-usb: found a 'Hauppauge Nova-TD Stick (52009)' in cold state, will try to load a firmware 45:34 udevd: seq 2787 queued, 'add' 'firmware' 46:35 kernel: dvb-usb: did not find the firmware file. (dvb-usb-dib0700-1.20.fw) 46:35 udevd: seq 2787 forked new worker [24357] 46:35 udevd[24357]: seq 2787 running 46:35 udevd[24357]: IMPORT builtin 'firmware' /lib/udev/rules.d/50-udev-default.rules:107 46:35 udevd[24357]: error: can not open '/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-6/firmware/1-6/loading' -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c16
--- Comment #16 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c17
Jiri Slaby
I have that TV tunner and it does not need firmware,
No you do not. This device definitely needs firmware. 1) The driver requests that as you can see. 2) The device doesn't work unless it is loaded.
we are talk about iwlwifi not about your DVB-T usb tunner.
The bug is primarily about defunct firmware loading. This is the same bug unless the original reporter confirms it works for him now. I doubt so. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c18
--- Comment #18 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c19
--- Comment #19 from Jiri Slaby
OK, do you have the "firmware" for the device? Just please output simply "ls -la /lib/firmware/{dvb-t-firmware-files}"
Yes, indeed: $ ls -la /lib/firmware/dvb-usb-dib0700-1.20.fw That is *not* the problem. The problem is that udev is waiting 1 minute and then tries to load it while the /sys node is gone already... What it is doing the minute? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c20
--- Comment #20 from Jiri Slaby
What it is doing the minute?
To add, when I run udevadm monitor I see a kernel uevent for firmware/add then 1 minute gap and even then a udev uevent for firmware/add appears. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c21
--- Comment #21 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c22
--- Comment #22 from Jiri Slaby
What kernel are you running?
Today's -next. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c23
--- Comment #23 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c24
--- Comment #24 from Jiri Slaby
Give me some time, I have the DVB-T at home, exactly the same as you, will try to reproduce it myself. I can't say anything until I see it also.
OK... Some more info that might help: 1) it's not stick-specific. It happens with two more dvb-t sticks. 2) but the _first_ plug-in works OK on all of them. If I remove it and plug it back, it: * times out, or * after 30s some udev worker is killed and firmware loaded -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c25
Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c26
Jiri Slaby
Jiri, please enable udev debugging (/etc/udev/udev.conf -> udev_log="debug"), reboot (or reload udev), remove the stick, plug it again, wait a ~minute and then attach /var/log/messages here. Hopefully it will show us something. Thanks.
Is this something different to attachment 493479? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c27
--- Comment #27 from Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c28
Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c29
Jiri Slaby
I am not maintainer of udev.
Right, reassigning back to Robert. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c30
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c31
--- Comment #31 from Jiri Slaby
http://download.opensuse.org/repositories/home:/rmilasan:/branches:/Base:/Sy...
Unfortunately udev from this does not load firmware at all. The kernel says: as10x_usb: device has been detected DVB: registering new adapter (PCTV Systems picoStick (74e)) DVB: registering adapter 2 frontend 0 (PCTV Systems picoStick (74e))... firmware 2-1: firmware_loading_store: unexpected value (0) as10x_usb: unable to locate firmware file: as102_data1_st.hex -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c32
Jiri Slaby
Also was talking to Petr Uzel and he was thinking that the best idea would be to do an strace to see whats going on.
Here you go. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c33
--- Comment #33 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c34
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c35
Jiri Slaby
Sorry for rushing into it, but first could you tell me where is that firmware located on your computer?
At usual places (/usr/lib/firmware is a link to /lib/firmware): # ll /lib/firmware/as102_data* /usr/lib/firmware/as102_data* -rw-r--r-- 1 root root 95500 31. říj 2011 /lib/firmware/as102_data1_st.hex -rw-r--r-- 1 root root 81820 31. říj 2011 /lib/firmware/as102_data2_st.hex -rw-r--r-- 1 root root 95500 31. říj 2011 /usr/lib/firmware/as102_data1_st.hex -rw-r--r-- 1 root root 81820 31. říj 2011 /usr/lib/firmware/as102_data2_st.hex
could you please re-run the same exact test using the DVB-T. This are not very concrete tests when you always test with something else.
Could we proceed only with pico stick (as102 driver) from now on? What other info do you want from that? Or do you want to debug specifically on nova-TD (dib0700 driver)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c36
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c37
--- Comment #37 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c38
--- Comment #38 from Jiri Slaby
Well we can procced with the pico stick, but also would like to see the strace for the DVB-T if you don't mind.
Pico stick is a DVB-T device.
Please attach the output of strace when pluggin in the DVB-T
Here you go. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c39
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c40
--- Comment #40 from Jiri Slaby
enable debuggin in udev
Syslog is here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c41
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c42
Jiri Slaby
So it works with the udev from the repo and kernel 3.4.0 or with your kernel -next or both?
Both. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c43
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c44
Jiri Slaby
But previously you said it doesn't. Did you change something?
Nope, I thought you did. That is indeed weird. But it works now with both sticks on both kernels... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c45
--- Comment #45 from Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c46
Robert Milasan
https://bugzilla.novell.com/show_bug.cgi?id=753734
https://bugzilla.novell.com/show_bug.cgi?id=753734#c47
--- Comment #47 from Bernhard Wiedemann
participants (1)
-
bugzilla_noreply@novell.com