I will reboot for another couple of times to check whether this behavior is persistent.Īfter two consecutive successful reboot and connection, I think the driver is working again now. What's really strange is that after last successful connection with maxcpus=1 bootarg, I am able to connect to wireless network without kernel panic again. I stopped using broadcom-wl because after some update, I can not connect to my office wireless network with that. Just remember it uses ethX instead of wlanX. Have you tried brcm80211 with maxcpus=1 in your grub.cfg?įrom my experiences broadcom-wl is the most stable driver so far. Using closed-source broadcom-wl package from AUR made wicd unable to find wlan0 interface. I don't know what causes this sudden failure. I have installed and uninstalled several font packages since the kernel update, which seems irrelevant. The wireless network has not been changed lately, and restarting the router makes no difference. But if I try to connect to a wireless network, I get a kernel panic when associating. If I have a wired connection linked to my computer, it can boot into gdm and establish a wired connection successfully, and I can see the wireless networks available in wicd interface. I am using wicd to manage wireless networks. However, after a reboot this afternoon, the driver makes kernel panic when associating. The wireless card was usable during several reboots since then. The kernel package is updated a couple of days ago. My version of kernel26 package is 2.6.26.3-1.
I am using brcm80211 package from AUR, which uses the kernel staging branch open source driver.