Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
BCM43602 Macs only see 2.4 GHz Wi-Fi out of the box
Reported by shawnyeager · filed Aug 21, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
2015–2017 Intel Macs with Broadcom BCM43602 (14e4:43ba) associate fine on 2.4 GHz under brcmfmac, but never list or join 5 GHz networks. linux-firmware-broadcom ships the chip firmware and no board calibration file, so the driver loads with placeholder 5 GHz values (aa5g=1, no per-channel tx-power tables) and iw phy only advertises Band 1.
Verified on MacBookPro14,3 (same chip as MacBookPro14,2):
- Before: associated on 2437 MHz (ch 6), -66 dBm, 104 / 144 Mbit/s, scan is 2.4 GHz only
- After installing a calibrated NVRAM and rebooting: 5745 MHz (ch 149), -40 dBm, 867 / 650 Mbit/s, Band 2 present, dual-band APs listed on both frequencies
Kernel log on the broken path:
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)Fix
PR: https://github.com/basecamp/omarchy/pull/7671
Credit
The field recipe this follows is @csk-grit42's HOWTO-wifi.md in OmarchyOnMacBookPro14.2-2017---A1706-. That write-up identified the missing BCM43602 NVRAM (kernel.org bugzilla attachment 290569) and the host regulatory-domain handoff that unlocks 5 GHz on these Macs.
View raw text
2015–2017 Intel Macs with Broadcom BCM43602 (`14e4:43ba`) associate fine on 2.4 GHz under `brcmfmac`, but never list or join 5 GHz networks. `linux-firmware-broadcom` ships the chip firmware and no board calibration file, so the driver loads with placeholder 5 GHz values (`aa5g=1`, no per-channel tx-power tables) and `iw phy` only advertises Band 1. Verified on MacBookPro14,3 (same chip as MacBookPro14,2): - Before: associated on 2437 MHz (ch 6), -66 dBm, 104 / 144 Mbit/s, scan is 2.4 GHz only - After installing a calibrated NVRAM and rebooting: 5745 MHz (ch 149), -40 dBm, 867 / 650 Mbit/s, Band 2 present, dual-band APs listed on both frequencies Kernel log on the broken path: ``` 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) ``` ## Fix PR: https://github.com/basecamp/omarchy/pull/7671 ## Credit The field recipe this follows is [@csk-grit42](https://github.com/csk-grit42)'s [HOWTO-wifi.md](https://github.com/csk-grit42/OmarchyOnMacBookPro14.2-2017---A1706-/blob/main/HOWTO-wifi.md) in [OmarchyOnMacBookPro14.2-2017---A1706-](https://github.com/csk-grit42/OmarchyOnMacBookPro14.2-2017---A1706-). That write-up identified the missing BCM43602 NVRAM (kernel.org bugzilla attachment 290569) and the host regulatory-domain handoff that unlocks 5 GHz on these Macs.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 08:17 UTC