You are not logged in.
I have this chip:
Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02)
Offline
ok thanks for the info, and can you tell me what packages you install to support it?
(I would like to see if I can use another driver than the one I use right now as it is not stable)
Thank you
Pitou!
Offline
You can download the needed firmwares from AUR (https://wiki.archlinux.org/index.php/br … reless#b43). B43 works quiet good for me, except for the unsupported 5 Ghz band.
Offline
I just ran into this issue as well, but the LTS kernel wasn't configured and I didn't have a live usb at hand. Another way for to boot normally is to temporarily blacklist the wl module by appending modprobe.blacklist=wl to the kernel command line. When using systemd boot, this is as easy as pressing 'e' in your menu and appending this to the end of the line.
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
As a test, I upgraded Arch in two VM's running on a Debian OS laptop.
1. Arch 32 bit + xfce4 desktop upgraded to 4.8.2 kernel. Reboot, startx, crashed the desktop. Reboot, install linux-lts kernel, startx, everything works. Haven't tried rebooting the 4.8.2 kernel.
2. Arch 64 bit + openbox desktop upgraded to 4.8.2 kernel, reboot, startx, everything works, no crash. No need for lts kernel.
Only guessing, maybe some difference in the new kernel 32 and 64 bit versions. Or it could be the two Arch VM's are just configured differently.
tex
Offline
running wifi-menu caused a kernel crash for me.
I solved by cd'ing to /var/cache/pacman/pkg/ and downgrading linux, linux-headers and virtualhost to 4.7.6
Offline
As a major note, the kernel 4.8.3 update, which I just booted into, does NOT have this same issue. At least it did not for me. It booted right up and there have been no hiccups or anything.
Offline
I just upgraded another Arch 32 bit VM in a different laptop. The new kernel is 4.8.3 - and seems to be working fine. Posting this through said VM.
tex
Offline
ChangeLog-4.8.3 nothing related to the change to cfg80211_scan_done which caused the null pointer issue in the wl module supplied by broadcom-wl.
Why would VM's experience this issue unless the broadcom wireless card is also passed through to the VM and the VM also uses an unpatched version of the wl module.
Offline