Created attachment 68562 [details] output of dmesg I use the driver broadcom-wl, networkmanager, nm-applet. After my upgrade to kernel 3.0, my wireless is gone... I read the following bug report submitted by people with similar problem https://bugzilla.kernel.org/show_bug.cgi?id=40712 However blacklisting bcma did not help.. In the attachment is the output of dmesg. I don't know where I find the kernel.logs :s
Kernel logs are in /var/log usually, but dmesg provides similar info. The chip you're using uses an older architecture, and you're likely running into issues with the ssb or b43 modules claiming the device before the broadcom-wl driver can attach to it. Can you do an 'lsmod | egrep "ssb|b43|wl"'? If ssb or b43 are listed, try removing those before loading the broadcom-wl driver.
When I type lsmod | egrep "ssb|b43|wl" nothing happens...
Ok, so no driver of any kind appears to be loaded. How did you do the upgrade to kernel 3.0? Did you build and install it yourself, or did you get it as a package from your distro? Which distro are you using? Most likely, you'll need to build and install a new copy of the wl driver. See http://www.broadcom.com/support/802.11/linux_sta.php
I did the upgrade with pacman -Syu, in Arch linux.
Not very familiar with Arch, but what do these commands report: pacman -Ss broadcom-wl pacman -Qs broadcom-wl Also, /var/log/pacman.log may have some interesting info from when you ran the 'pacman -Syu' command.
pacman -Ss broadcom-wl displays nothing. Strange I remember obtaining the driver through pacman :s When I do pacman -Qs broadcom-wl, I get the following output. local/broadcom-wl 5.100.82.38-4 Broadcom 802.11abgn hybrid Linux networking driver I updated the kernel with pacman at [2011-08-08 23:17] The pacman.log file is in the attachment
Created attachment 68652 [details] pacman.log
In the Arch linux wiki on wireless drivers: https://wiki.archlinux.org/index.php/Broadcom_BCM4312#Loading_the_wl_kernel_module There's a little bullet buried under "Wi-Fi card does not work/show up (broadcom-wl)" that says: > If you have recently upgraded your kernel, you need to rebuild the > broadcom-wl > package with the new kernel installed to update the module. From your pacman log, it looks like the broadcom-wl package was last installed before your 3.0 kernel upgrade (assuming I'm understanding the log correctly). Can you try reinstalling the package with 'pacman -S broadcom-wl'?
I tried doing that befor but apparently the broadcam-wl was nowhere to be found, in the standard pacman repository. Looking on the Arch Wiki I found that is is part of the AUR (Arch User Repository), which is a collection of package builds, which you can not acces with pacman. yaourt is a program from the AUR which uses the same syntax als pacman and does the downloading unpackaging and building for you. So 'yaourt -S broadcom-wl' did the job, my wireless is working now. thx for the help!
Great. Is there anything that the Arch folks should do in terms of sorting out the package dependencies and the pacman vs. yaourt issues?
package dependencies are dealt with very well both in pacman and yaourt. The problem was that I ddn't know that I needed to install my wireless driver again, and that I forgot it came from the AUR. I don't know why it isn't part of the pacman repository, but maybe they have their reasons for that. I do think it would be nice if pacman would give a warning after updating the kernel something like "If you use the following wireless drivers you need to reinstall them"
Agreed, a warning would be nice. I'll close this driver bug since there's nothing to be changed in the driver.
Not a driver bug.