OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network high occasional DISPUTE

Stop broadcom-wl from hard-freezing a BCM4331 MacBook

omarchyarchlaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Cause verified against install/hardware/fix-bcm43xx.sh, which really does omarchy-pkg-add broadcom-wl dkms linux-headers for both 14e4:43a0 and 14e4:4331. But the fix is broken in two ways. (1) broadcom-wl and broadcom-wl-dkms *conflict* (confirmed on the Arch package page), so exactly one can be installed and pacman -Rns broadcom-wl broadcom-wl-dkms aborts with 'target not found' and removes NOTHING. 2>/dev/null only hides the error. (2) b43 firmware is NOT in linux-firmware-broadcom. The Arch broadcom-wl file list is just usr/lib/modprobe.d/broadcom-wl.conf + wl.ko.zst, and b43 needs proprietary firmware extracted by b43-fwcutter (AUR b43-firmware). Installing b43-fwcutter alone leaves the machine with no Wi-Fi at all. The rm targets are also wrong paths: the blacklist ships in /usr/lib/modprobe.d/, not /etc/modprobe.d/, and disappears with the package.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Do NOT apply this on a BCM4360 (14e4:43a0): there is no in-kernel driver for it and removing broadcom-wl there leaves you with no Wi-Fi at all.

Symptom

On a mid-2011 MacBook Air/Pro with Broadcom BCM4331, the machine hard-freezes (no console, no SysRq, power button only) either in the live installer while Wi-Fi is being set up, or shortly after boot on the installed system. Before installation the in-kernel driver worked fine.

Cause

Omarchy's install/hardware/fix-bcm43xx.sh installs broadcom-wl whenever it sees 14e4:43a0 (BCM4360) **or** 14e4:4331 (BCM4331). BCM4360 genuinely needs wl, since there is no in-kernel driver, but BCM4331 is fully supported by the in-kernel b43 driver. Worse, the broadcom-wl package ships a modprobe blacklist for b43, ssb and bcma, so installing it does not merely add an alternative, it disables the working in-kernel path.

Fix


lspci -nn | grep -i network        # confirm [14e4:4331]

# Remove whichever variant is actually installed (they conflict; naming both aborts)
for p in broadcom-wl broadcom-wl-dkms; do
  pacman -Qq "$p" >/dev/null 2>&1 && sudo pacman -Rns "$p"
done

# The blacklist ships in /usr/lib/modprobe.d and goes away with the package.
# Only remove a local override if you actually have one:
ls -l /etc/modprobe.d/ | grep -i -E 'broadcom|b43|wl'

b43 needs firmware that Arch cannot redistribute: b43-fwcutter only extracts it, it ships none:


sudo pacman -S --needed b43-fwcutter linux-firmware-broadcom
# then install the AUR package that downloads Broadcom's blob and runs fwcutter:
#   paru -S b43-firmware      (BCM4331 needs the 5.100.138 firmware)
ls /usr/lib/firmware/b43/    # must be non-empty before rebooting
sudo reboot

After reboot: dmesg | grep b43 should show the firmware loading, and ip link should show a wl* device.

To get in if it freezes first, append at the boot menu: modprobe.blacklist=wl

Verify

lsmod | grep -E '^(b43|wl)' shows b43 loaded and wl absent. ip link lists the interface (often named wlp2s0b1 under b43) and the machine stays up under Wi-Fi load.

Sources

broadcom-wl-bcm4331-hard-freeze