Hide Forgot
Description of problem: wifi card don't appear since kernel update wifi is ok with 3.1.9-1.fc16.i686 chipset wifi is BCM4322 Version-Release number of selected component (if applicable): ok in 3.1.9-1.fc16.i686 nok in 3.2.2-1.fc16.i686 and 3.2.5-3.fc16.i686 Additional info: probably similar to the bug 786180
Can you be more specific about "doesn't work"? Is there a crash? Does the driver load? Does it establish a connection and work for a little while? Please attach the output of running 'dmesg' shortly after you establish that it isn't working. Have you tried the latest available f16 kernels? What is the latest version that you tried?
in first excuse me but i'm a newbee on linux i think the driver doesn't load but i'm not sure this is with the lastest version [root@fred fred]# uname -r 3.3.1-5.fc16.i686 [root@fred fred]# lspci -nn | grep Wireless 09:00.0 Network controller [0280]: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01) [root@fred fred]# dmesg | grep Wireless [root@fred fred]# ifconfig lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:988 errors:0 dropped:0 overruns:0 frame:0 TX packets:988 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:76296 (74.5 KiB) TX bytes:76296 (74.5 KiB) p4p1 Link encap:Ethernet HWaddr 00:25:B3:5C:EB:A0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interruption:16 [root@fred fred]# with the lastest version who wifi works [root@fred fred]# lspci -nn | grep Wireless 09:00.0 Network controller [0280]: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01) [root@fred fred]# uname -r 3.1.9-1.fc16.i686 [root@fred fred]# dmesg | grep Wireless [ 24.038769] eth0: Broadcom BCM432b 802.11 Hybrid Wireless Controller 5.100.82.112 [root@fred fred]# ifconfig eth0 Link encap:Ethernet HWaddr 00:21:00:F0:A1:DE inet adr:10.0.0.106 Bcast:10.0.0.255 Masque:255.255.255.0 adr inet6: fe80::221:ff:fef0:a1de/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:107463 errors:0 dropped:0 overruns:0 frame:848 TX packets:58519 errors:6 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:159609661 (152.2 MiB) TX bytes:4878976 (4.6 MiB) Interruption:17 lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:206 errors:0 dropped:0 overruns:0 frame:0 TX packets:206 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:15432 (15.0 KiB) TX bytes:15432 (15.0 KiB) p4p1 Link encap:Ethernet HWaddr 00:25:B3:5C:EB:A0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interruption:16 [root@fred fred]# i remember but i used a driver in RPM Fusion (package broadcom-wl )
It looks like you have a device that might not be supported by the b43 driver. I'll still need to see the output of running "dmesg" shortly after you reboot.
Created attachment 577820 [details] output of dmesg i don't know what i should looking for so i send you all the output of command dmesg
I don't see any output from the ssb or b43 drivers. Can you show me the output you get from running 'modinfo ssb'?
Created attachment 577845 [details] output dmesg in 3.1.9 this is the ouput of modinfo ssb filename: /lib/modules/3.3.1-5.fc16.i686/kernel/drivers/ssb/ssb.ko license: GPL description: Sonics Silicon Backplane driver alias: pci:v000014E4d0000432Bsv*sd*bc*sc*i* alias: pci:v000014E4d00004329sv*sd*bc*sc*i* alias: pci:v000014E4d00004328sv*sd*bc*sc*i* alias: pci:v000014E4d00004325sv*sd*bc*sc*i* alias: pci:v000014E4d00004324sv*sd*bc*sc*i* alias: pci:v000014E4d00004321sv*sd*bc*sc*i* alias: pci:v000014E4d00004320sv*sd*bc*sc*i* alias: pci:v000014E4d00004319sv*sd*bc*sc*i* alias: pci:v000014A4d00004318sv*sd*bc*sc*i* alias: pci:v000014E4d00004318sv*sd*bc*sc*i* alias: pci:v000014E4d00004315sv*sd*bc*sc*i* alias: pci:v000014E4d00004312sv*sd*bc*sc*i* alias: pci:v000014E4d00004311sv*sd*bc*sc*i* alias: pci:v000014E4d00004307sv*sd*bc*sc*i* alias: pci:v000014E4d00004306sv*sd*bc*sc*i* alias: pci:v000014E4d00004301sv*sd*bc*sc*i* depends: mmc_core intree: Y vermagic: 3.3.1-5.fc16.i686 SMP mod_unload 686 i put in attachement the ouput of dmesg in version 3.1.9. maybe you will find what isn't going on
Looks like ssb should have been loaded, but wasn't. Perhaps you have it blacklisted somewhere under /etc/modprobe.d? grep ssb /etc/modprobe.d/* What happens if you load ssb manually? modprobe ssb You'll need to be root for modprobe to succeed, of course. Does that load the driver?
this is the output that you asked [root@fred fred]# grep ssb /etc/modprobe.d/* /etc/modprobe.d/broadcom-wl-blacklist.conf:blacklist ssb [root@fred fred]# when i wrote "modprobe ssb" nothing happened but i looked in dmesg and i had this message [ 756.223243] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x17, vendor 0x4243) [ 756.223266] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x10, vendor 0x4243) [ 756.223286] ssb: Core 2 found: PCI-E (cc 0x820, rev 0x0B, vendor 0x4243) [ 756.223305] ssb: Core 3 found: PCI (cc 0x804, rev 0x0E, vendor 0x4243) [ 756.223324] ssb: Core 4 found: USB 2.0 Device (cc 0x81A, rev 0x05, vendor 0x4243) [ 756.223342] ssb: Core 5 found: UNKNOWN (cc 0x8FF, rev 0x00, vendor 0x4243) [ 756.223361] ssb: Core 6 found: Internal Memory (cc 0x80E, rev 0x03, vendor 0x4243) [ 756.256691] ssb: Sonics Silicon Backplane found on PCI device 0000:09:00.0
OK, so the ssb module is not loading because you have it blacklisted. You probable did this (perhaps inadvertantly) when you installed the broadcom-wl package. Why are you using that, btw? Most Broadcom hardware should be supported with the standard kernel at this point. After you loaded the ssb module, did the b43 module get loaded too? It should show-up when running 'lsmod'. You might try a simple 'modprobe b43' just to be sure. What output from b43 shows-up in dmesg?
do you know why this package is blacklisted only after 3.1.9? when I use this kernel (3.1.9 ), all works fine i don't remember i did something who can blacklisted my wireless card i used this package because when i installed fedora on this laptop (HP 6735b), wireless networks didn't work and i looked on internet and i found a method to install this driver it's on fedora french forum (links: http://forums.fedora-fr.org/viewtopic.php?id=55520 it's in french, maybe you understand ) so i did what you asked me to do and this is the output [root@fred ~]# lsmod | grep b43 [root@fred ~]# modprobe ssb [root@fred ~]# lsmod | grep b43 [root@fred ~]# modprobe b43 [root@fred ~]# lsmod | grep b43 b43 339007 0 mac80211 427444 1 b43 cfg80211 169437 2 b43,mac80211 bcma 25040 1 b43 ssb 55028 1 b43 mmc_core 97466 2 b43,ssb [root@fred ~]# in dmesg (after the command modprobe b43) [ 4537.071787] cfg80211: Calling CRDA to update world regulatory domain [ 4537.133923] cfg80211: World regulatory domain updated: [ 4537.133940] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 4537.133954] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 4537.133967] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 4537.133978] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 4537.133990] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 4537.134001] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 4537.189382] b43-phy0: Broadcom 4322 WLAN found (core revision 16) [ 4537.270380] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 4537.270750] Registered led device: b43-phy0::tx [ 4537.270782] Registered led device: b43-phy0::rx [ 4537.270820] Registered led device: b43-phy0::radio [ 4537.270844] Broadcom 43xx driver loaded [ Features: PMNLS ] [ 4537.305186] cfg80211: Calling CRDA for country: FR [ 4537.311266] cfg80211: Regulatory domain changed to country: FR [ 4537.311270] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 4537.311274] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 4537.311277] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 4537.311279] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm) [ 4537.311282] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm) [ 4537.329956] b43-phy0 ERROR: Firmware file "b43/ucode16_mimo.fw" not found [ 4537.329965] b43-phy0 ERROR: Firmware file "b43-open/ucode16_mimo.fw" not found [ 4537.329971] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website. [root@fred ~]#
It _is_ blacklisted on 3.1.9 -- there you are using a different driver (broadcom-wl), which presumably you installed based on the instructions at the French link above. The broadcom-wl driver is not supported by Fedora. The RPMFusion folks have it packaged to help those who might need it, but it isn't clear to me that you actually do need it. Anyway, driver modules are specific to a kernel version, so when your kernel got upgraded the broadcom-wl module no longer worked with the new kernel. It looks to me like you should try uninstalling broadcom-wl, and obtaining firmware for b43 using the "wireless.kernel.org" link from the dmesg output in the previous comment. Unfortunately, Fedora cannot provide this firmware directly due to lack of a license. You will have to obtain that yourself. Alternatively, you might look for an update to the broadcom-wl driver that matches the new kernel. As I said above, this is not supported by Fedora so I can't really help there. I'm sorry that neither option is completely simple. FWIW, I would advise that former option, as that should keep you from having to do anything when the kernel gets updated again.
i found a driver with rpmfusion who are available with this kernel i didn't know the driver is specific on each kernel, and i have to upgrade it in each new kernel. it isn't very usefull thank a lot to have spent a lot of your time on my issue. all works fine now, thanks