Zoltan Hoppar <hopparz <at> gmail.com> writes: > ... > Still shows no wifi network, just "disconnected" at NM. > But the driver is in: > (lspci -vnn)06:00.0 Network controller [0280]: Broadcom Corporation BCM4312 > 802.11b/g LP-PHY [14e4:4315] (rev 01) > > Subsystem: Hewlett-Packard Company Device [103c:1508] Physical Slot: 1 > Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 92000000 > (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> > > Kernel driver in use: wl > Kernel modules: wl, ssb > The problem is doesn't see the ESSID's, just "disconnected". > Or simply just doesnt support this driver? > ... Hi, I have just looked at your output and seen these lines > Kernel driver in use: wl > Kernel modules: wl, ssb which indicate that there is another proprietary driver from Broadcom http://www.broadcom.com/support/802.11/linux_sta.php http://www.broadcom.com/docs/linux_sta/README.txt that is downloadable from rpmfusion repository # yum install kmod-wl ... Installing : kmod-wl-2.6.33.6-147.2.4.fc13.i686-5.60.48.36-1.fc13.1 Installing : broadcom-wl-5.60.48.36-1.fc13.noarch Installing : kmod-wl-5.60.48.36-1.fc13.10.i686 Now, this baby is blacklisting b43 driver in $ # cat /etc/modprobe.d/broadcom-wl-blacklist.conf # modules blacklisted for broadcom-wl blacklist bcm43xx blacklist ssb blacklist b43 blacklist ndiswrapper OK. So, you have a choice of trying both, wl and b43, but remember to blacklist the other when you try one. I would try the b43 as we followed the instructions in my other posts, but in this case we would have to remove the blacklisting of it: # mv /etc/modprobe.d/broadcom-wl-blacklist.conf /etc/modprobe.d/broadcom-wl-blacklist.conf-orig and blacklist the wl in turn :-) # echo "blacklist wl" > /etc/modprobe.d/broadcom-b43-blacklist.conf Please remember that and restore/neutralize them when you will try the wl driver ! One more thing, remove wl and related modules # lsmod |grep -i wl # modprobe -r wl Now follow with the instructions from my other recent post to load b43 and bind it to our wireless device. If you succeed, you should see it in: # lspci -vnn # lsmod |grep -i b43 # cat /var/log/messages You may reboot then to make the entire process run its course and get all dmesg and /var/log/messages. Let us know how did it go. Having choices that "just work" is a beauty -:) JB -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
