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

Unlock 5 GHz on a Broadcom BCM43602 MacBook

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

The regulatory-domain half is verified and is the real, reproducible fix: core/any/wireless-regdb ships /etc/conf.d/wireless-regdom, /usr/bin/set-wireless-regdom and /usr/lib/udev/rules.d/85-regulatory.rules, and omarchy's install/hardware/set-wireless-regdom.sh already writes a WIRELESS_REGDOM line from the timezone, so the record's unconditional tee -a appends a *second* WIRELESS_REGDOM line. The NVRAM half is weak: no clm_blob available is a benign informational message on many brcmfmac parts, brcmfmac falls back to the on-device NVRAM on Macs, and the record tells the user to install an unvetted binary blob from a bugzilla attachment into /usr/lib/firmware. Lead with regdom. Make the NVRAM step an explicitly optional last resort.

The cause above was rewritten on 2026-08-30 to match this note; the fix was corrected by the audit itself.
RISK

Installing an NVRAM file for the wrong board can push out-of-spec transmit power. Only use a file matched to your exact Mac model.

Symptom

On a 2015 to 2017 Intel Mac, Wi-Fi works but only ever sees and joins 2.4 GHz networks. Dual-band APs appear only once, on channel 1 to 11, with poor throughput (~104/144 Mbit/s at -66 dBm). 5 GHz SSIDs never show up in a scan. Kernel log:


brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43602-pcie for chip BCM43602/2
brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)

Cause

Almost always the regulatory domain: with none set, the driver falls back to the most restrictive world domain and iw phy only ever advertises Band 1 (2.4 GHz). wireless-regdb ships /etc/conf.d/wireless-regdom, /usr/bin/set-wireless-regdom and /usr/lib/udev/rules.d/85-regulatory.rules, and Omarchy's install/hardware/set-wireless-regdom.sh already writes a WIRELESS_REGDOM line derived from the timezone, so the value may be set but wrong, and it must be edited rather than appended to. The board-NVRAM theory is much weaker than it looks: no clm_blob available is a benign informational message on many brcmfmac parts, and on Macs brcmfmac falls back to the on-device NVRAM.

Fix


lspci -nn | grep -i network      # expect [14e4:43ba]
iw reg get                       # country 00 = world roaming -> 5 GHz mostly no-IR/disabled
iw phy | grep -E 'Band|MHz \[(3[6-9]|4[0-9]|1[0-6][0-9])\]' | head

Fix the regulatory domain first. This alone restores 5 GHz on most Macs. Replace the existing line rather than appending a duplicate:


grep -n WIRELESS_REGDOM /etc/conf.d/wireless-regdom
sudo sed -i 's/^[#[:space:]]*WIRELESS_REGDOM=.*/WIRELESS_REGDOM="US"/' /etc/conf.d/wireless-regdom   # your ISO 3166 code
grep -c '^WIRELESS_REGDOM=' /etc/conf.d/wireless-regdom   # must be exactly 1
sudo iw reg set US
iw reg get
sudo nmcli device wifi rescan && nmcli device wifi list

Only if 5 GHz is still absent after the regdom is correct, and only with a file you trust for your exact board, add board NVRAM:


sudo install -Dm644 brcmfmac43602-pcie.txt /usr/lib/firmware/brcm/brcmfmac43602-pcie.txt
sudo modprobe -r brcmfmac && sudo modprobe brcmfmac
dmesg | grep brcmfmac | tail

If that makes things worse, remove the file and reload the driver. It is not shipped by linux-firmware-broadcom and is not required for the chip to work.

Verify

iw phy | grep 'Band 2' now matches, iw dev wlan0 link reports a 5 GHz frequency (e.g. freq: 5745) and much higher rates (867/650 Mbit/s), and 5 GHz SSIDs appear in nmcli device wifi list.

Sources

bcm43602-mac-no-5ghz-missing-nvram