Bugzilla – Bug 709073
No wireless module since updating to 3.0 kernel
Last modified: 2011-08-20 07:34:05 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.829.0 Safari/535.1 SUSE/14.0.829.0 After updating to kernel 3.0.0-38.1 today from the Tumbleweed repo, my wireless quit working. ifconfig no longer shows wlan0. I'm using ifup and YaST no longer recognizes my wireless card. In the network configuration tool, no modules are listed and YaST doesn't save it when I enter rt2800 in the module field. lsmod doesn't list any rt2800 modules, but /usr/src/linux-3.0.0-38/drivers/net/wireless/rt2x00 shows rt2800pci.c and rt2800pci.h. iwconfig shows: lo no wireless extensions eth0 no wireless extensions The package rt2860-1.8.0.0-10.1.noarch is installed. Reproducible: Always Steps to Reproduce: 1.Update to the 3.0 kernel 2. 3. Actual Results: wireless stops working- my wireless card is no longer recognized. Expected Results: Wireless should still work.
I can confirm this happened to me too after upgrading to kernel-desktop-3.0.0 from Tumbleweed repo, but with a BCM43224 card and broadcom-wl driver. Used to work fine with kernel-desktop-2.6.39 You'll see in the following debug snippets that this is no trivial misconfiguration or missing firmware. Something broke with kernel-desktop-3.0.0 and it is not obvious. Expecially that "tail -f /var/log/messages" while modprobing gives no (!) output (no missing firmware, no complaints, nothing) is very suspecious. -------------------------------------------- relevant ouput from lspci: -------------------------------------------- 03:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) Subsystem: Hewlett-Packard Company Device 1510 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at c2400000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information: Len=78 <?> Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 00-00-82-ff-ff-92-00-26 Capabilities: [16c] Power Budgeting <?> Kernel driver in use: bcma-pci-bridge -------------------------------------------- Checking for firmware: -------------------------------------------- envy:~ # find /lib/firmware/ -iname "bcm43xx*" | xargs ls -l -rw-r--r-- 1 root root 97344 8. Jul 03:26 /lib/firmware/brcm/bcm43xx-0.fw -rw-r--r-- 1 root root 180 8. Jul 03:26 /lib/firmware/brcm/bcm43xx_hdr-0.fw -------------------------------------------- grepping dmesg: -------------------------------------------- envy:~ # dmesg | grep -i -E "(broadcom|wl|03\:00\.0)" [ 0.000000] DMI: Hewlett-Packard HP ENVY 14 Notebook PC /1436, BIOS F.23 11/11/2010 [ 1.029581] pci 0000:03:00.0: [14e4:4353] type 0 class 0x000280 [ 1.029603] pci 0000:03:00.0: reg 10: [mem 0xc2400000-0xc2403fff 64bit] [ 1.029693] pci 0000:03:00.0: supports D1 D2 [ 2.549003] usb 1-1.3: Manufacturer: Broadcom Corp [ 8.623455] bcma-pci-bridge 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 8.623485] bcma-pci-bridge 0000:03:00.0: setting latency timer to 64 [ 8.931011] wl: module license 'unspecified' taints kernel. -------------------------------------------- ifconfig: -------------------------------------------- envy:~ # ifconfig eth0 Link encap:Ethernet Hardware Adresse D8:D3:85:3A:A0:A7 inet Adresse:172.16.1.115 Bcast:172.16.3.255 Maske:255.255.252.0 inet6 Adresse: fe80::dad3:85ff:fe3a:a0a7/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:33435 errors:0 dropped:2 overruns:0 frame:0 TX packets:19790 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:1000 RX bytes:29038095 (27.6 Mb) TX bytes:1694896 (1.6 Mb) Interrupt:43 Basisadresse:0x4000 lo Link encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:351 errors:0 dropped:0 overruns:0 frame:0 TX packets:351 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:0 RX bytes:31203 (30.4 Kb) TX bytes:31203 (30.4 Kb) -------------------------------------------- modprobing wl: -------------------------------------------- envy:~ # modprobe -v wl insmod /lib/modules/3.0.0-38-desktop/updates/wl.ko -------------------------------------------- Output of "tail -f /var/log/messages" while modprobing: -------------------------------------------- NONE!
Same here. Working RT2860 with 2.6.39 which stopped after upgrading to 3.0. -------------------------------------------- relevant ouput from lspci: -------------------------------------------- 02:00.0 Network controller: RaLink RT2860 Subsystem: Micro-Star International Co., Ltd. Device 6890 Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at dfc00000 (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting -------------------------------------------- Checking for firmware: -------------------------------------------- -rw-r--r-- 1 root root 8192 8. Jul 03:26 /lib/firmware/rt2561.bin -rw-r--r-- 1 root root 8192 8. Jul 03:26 /lib/firmware/rt2561s.bin -rw-r--r-- 1 root root 8192 8. Jul 03:26 /lib/firmware/rt2661.bin -rw-r--r-- 1 root root 8192 8. Jul 03:26 /lib/firmware/rt2860.bin -rw-r--r-- 1 root root 8192 8. Jul 03:26 /lib/firmware/rt2870.bin -------------------------------------------- dmesg is quite unspectacular : -------------------------------------------- [ 0.270112] pci 0000:02:00.0: [1814:0781] type 0 class 0x000280 [ 0.270137] pci 0000:02:00.0: reg 10: [mem 0xdfc00000-0xdfc0ffff] [ 0.270248] pci 0000:02:00.0: PME# supported from D0 D3hot [ 0.270257] pci 0000:02:00.0: PME# disabled [ 0.914535] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt -------------------------------------------- ifconfig: -------------------------------------------- eth0 Link encap:Ethernet Hardware Adresse 00:21:85:50:A2:6D inet Adresse:192.168.0.10 Bcast:192.168.0.255 Maske:255.255.255.0 inet6 Adresse: fe80::221:85ff:fe50:a26d/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:261581 errors:0 dropped:0 overruns:0 frame:0 TX packets:151938 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:1000 RX bytes:383616705 (365.8 Mb) TX bytes:11212952 (10.6 Mb) Interrupt:40 Basisadresse:0xa000 lo Link encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:312763 errors:0 dropped:0 overruns:0 frame:0 TX packets:312763 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:0 RX bytes:374243077 (356.9 Mb) TX bytes:374243077 (356.9 Mb) -------------------------------------------- modprobe rt2x00pci: -------------------------------------------- insmod /lib/modules/3.0.0-38-desktop/kernel/net/rfkill/rfkill.ko insmod /lib/modules/3.0.0-38-desktop/kernel/net/wireless/cfg80211.ko insmod /lib/modules/3.0.0-38-desktop/kernel/net/mac80211/mac80211.ko insmod /lib/modules/3.0.0-38-desktop/kernel/drivers/net/wireless/rt2x00/rt2x00lib.ko insmod /lib/modules/3.0.0-38-desktop/kernel/drivers/net/wireless/rt2x00/rt2x00pci.ko -------------------------------------------- /var/log/messages" while modprobing: -------------------------------------------- Jul 30 10:22:02 tsnb01 kernel: [ 4598.962593] cfg80211: Calling CRDA to update world regulatory domain Jul 30 10:22:02 tsnb01 kernel: [ 4599.099090] cfg80211: World regulatory domain updated: Jul 30 10:22:02 tsnb01 kernel: [ 4599.099098] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Jul 30 10:22:02 tsnb01 kernel: [ 4599.099106] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Jul 30 10:22:02 tsnb01 kernel: [ 4599.099113] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Jul 30 10:22:02 tsnb01 kernel: [ 4599.099120] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Jul 30 10:22:02 tsnb01 kernel: [ 4599.099126] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Jul 30 10:22:02 tsnb01 kernel: [ 4599.099133] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Good to see that I am not the only one! Could all of you please vote for this bug to give it some priority? It really is important since I've lost all wireless net connectivity and can only connect with cable network.
I was also able to use the brcmsmac driver with kernel 2.6.39 (but preferred broadcom-wl for being more stable). With kernel 3.0.0, brcmsmac is behaving exactly like wl: Modprobing it just writes the staging-tree warning to /var/log/messages and nothing else. It used to write a lot of debug output. I just mentioned this to show that it even happens with built-in kernel drivers and not only 3rd party drivers.
Well, my Intel Wireless 6250 adapter also died after update to kernel 3.0 from Tumbleweed, but in this case I believe it's kernel-firmware package to blame, providing incompatible firmware.
Could all our issues here be related to an incompatible firmware package? Mine's kernel-firmware-20110709-42.1.noarchfrom Tubleweed repo. Can some kernel developer clarify?
I checked in /lib/modules and there is no rt2800pci.ko file. There is only rt2800lib.ko and rt2800usb.ko. There was an update for kernel-firmware today, 20110709-47.1, that contains rt2860.bin but my wireless card still isn't recognized. Could my wifi problem be something as simple as the rt2800pci module has been left out of the 3.0 kernel being supplied for Tumbleweed?
Exactly the same symptoms for BRCM43224 cards on Arch Linux overe here: https://bbs.archlinux.org/viewtopic.php?pid=970078 So this is most likely supposed to be an upstream bug, isn't it?
It seems to matter WHEN the module is loaded! I had "brcmsmac" and "brcm80211" blacklisted because of wl. "rmmod wl" and "modprobe brcmsmac" afterwards never worked but now I removed the wl module completely and uncommented the blacklist lines for the brcm driver in /etc/modprobe.d/50-blacklist.conf. And guess what? The brcmsmac driver loaded as done before manually a 1000 times but this time it created a "wlan1" interface.
The rt2800 disappeared in 3.0. We enabled another one. Could you test with kernel 3.0.2 from (after it builds): http://download.opensuse.org/repositories/Kernel:/stable/standard/ ? For the rest of the cards (broadcom, intel), create a separate report.
3.0.2 is working for me. It's logging that WPA is untested but no problems so far with WPA2 enabled.
I installed kernel 3.0.3-1 desktop today and rt2800pci is found and my wireless is working. Now I'm getting this from ifconfig: eth0 Link encap:Ethernet HWaddr 6C:F0:49:55:B8:49 inet addr:192.xxx.x.xx Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::6ef0:49ff:fe55:b849/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:180 errors:0 dropped:0 overruns:0 frame:0 TX packets:95 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:17381 (16.9 Kb) TX bytes:12118 (11.8 Kb) Interrupt:44 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:142 errors:0 dropped:0 overruns:0 frame:0 TX packets:142 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:13451 (13.1 Kb) TX bytes:13451 (13.1 Kb) wlan0 Link encap:Ethernet HWaddr 00:0E:08:10:00:72 inet addr:192.xxx.x.xx Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20e:8ff:fe10:72/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:251 errors:0 dropped:0 overruns:0 frame:0 TX packets:133 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:29765 (29.0 Kb) TX bytes:20843 (20.3 Kb) I added the x's to conceal my ip address. This issue looks to be resolved.
How long before this kernel is added to the Tumbleweed repo?
(In reply to comment #13) > How long before this kernel is added to the Tumbleweed repo? Few days or a week. Thanks.