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.
fix-bcm43xx.sh installs broadcom-wl for BCM4331, which hard-freezes a 2011 MacBook Air where in-kernel b43 works
Reported by willhemming · filed Aug 20, 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
What happened
install/hardware/fix-bcm43xx.sh installs broadcom-wl whenever it detects a BCM4360 (14e4:43a0) or BCM4331 (14e4:4331). On a mid-2011 MacBook Air (MacBookAir4,1, BCM4331), the wl driver hard-froze the machine in the live/install environment. The in-kernel b43 driver (firmware from linux-firmware-broadcom) drives the same chip without issue — the installed system has been running wifi on b43 (interface wlp2s0b1) stably since 2026-08-19.
Note also that broadcom-wl ships a modprobe blacklist for b43/ssb/bcma, so installing it doesn't just add an alternative driver — it disables the working in-kernel path.
What I expected
The installer's Broadcom handling not to install a driver that locks up the hardware it detected, when a working in-kernel driver exists for that chip.
Suggestion
The two chips the script matches are in different situations:
- BCM4360 (
14e4:43a0): no open in-kernel driver —broadcom-wlis genuinely the only option, keep as-is. - BCM4331 (
14e4:4331): supported by in-kernelb43withlinux-firmware-broadcom. Preferring that (or at least not blacklisting it) would avoid the freeze.
I only have one BCM4331 machine (the 2011 Air), so I can't say whether wl misbehaves on the 2012 MacBooks the comment mentions — if wl is known-needed there, gating on DMI rather than PCI ID alone might be the safer shape.
System details
- MacBookAir4,1 (mid-2011 11"), i5-2467M Sandy Bridge, BCM4331 (
14e4:4331) - Omarchy install performed 2026-08-19
Happy to gather logs or test a patched script on this machine.
View raw text
## What happened `install/hardware/fix-bcm43xx.sh` installs `broadcom-wl` whenever it detects a BCM4360 (`14e4:43a0`) **or** BCM4331 (`14e4:4331`). On a mid-2011 MacBook Air (`MacBookAir4,1`, BCM4331), the `wl` driver hard-froze the machine in the live/install environment. The in-kernel `b43` driver (firmware from `linux-firmware-broadcom`) drives the same chip without issue — the installed system has been running wifi on `b43` (interface `wlp2s0b1`) stably since 2026-08-19. Note also that `broadcom-wl` ships a modprobe blacklist for `b43`/`ssb`/`bcma`, so installing it doesn't just add an alternative driver — it disables the working in-kernel path. ## What I expected The installer's Broadcom handling not to install a driver that locks up the hardware it detected, when a working in-kernel driver exists for that chip. ## Suggestion The two chips the script matches are in different situations: - **BCM4360** (`14e4:43a0`): no open in-kernel driver — `broadcom-wl` is genuinely the only option, keep as-is. - **BCM4331** (`14e4:4331`): supported by in-kernel `b43` with `linux-firmware-broadcom`. Preferring that (or at least not blacklisting it) would avoid the freeze. I only have one BCM4331 machine (the 2011 Air), so I can't say whether `wl` misbehaves on the 2012 MacBooks the comment mentions — if `wl` is known-needed there, gating on DMI rather than PCI ID alone might be the safer shape. ## System details - MacBookAir4,1 (mid-2011 11"), i5-2467M Sandy Bridge, BCM4331 (`14e4:4331`) - Omarchy install performed 2026-08-19 Happy to gather logs or test a patched script on this machine.
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 04:52 UTC