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.
Quattro upgrade leaves legacy broadcom-wl-dkms installed on BCM4350 Macs, disabling brcmfmac
Reported by rsharma1157 · filed Aug 28, 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
Summary
Upgrading an Intel Mac with Broadcom BCM4350 (14e4:43a3) from Omarchy 3.x to Quattro can leave the legacy broadcom-wl-dkms package installed. Quattro already treats 14e4:43a3 as a brcmfmac device, but the legacy broadcom-wl-dkms package blacklists brcmfmac. The proprietary wl module then fails during initialization, leaving the system with no Wi-Fi interface.
Reproduction / observed behavior
Hardware:
Broadcom BCM4350 802.11ac
PCI ID: 14e4:43a3
Apple subsystemAfter upgrading to Quattro:
broadcom-wl-dkms 6.30.223.271-48 installedThe wl module builds successfully via DKMS, but fails at runtime:
wl driver 6.30.223.271 failed with code 1
ERROR @wl_cfg80211_detach
NULL ndev->ieee80211ptr, unable to deref wlResult:
iw dev
# no interfaces
nmcli device status
# no Wi-Fi deviceA pre-upgrade snapshot on the same machine showed the BCM4350 working normally with the in-kernel driver:
Kernel driver in use: brcmfmac
wlp2s0 wifi connectedRemoving broadcom-wl-dkms from the current Quattro installation and rebooting the current kernel immediately restored Wi-Fi:
Kernel driver in use: brcmfmac
wlp2s0 wifi connectedThis was verified on both the pre-upgrade snapshot and the current Quattro kernel, so this is not a kernel downgrade workaround; the causal difference is the legacy broadcom-wl-dkms package/blacklist.
Relevant Quattro behavior
install/hardware/apple/fix-brcmfmac-supplicant.sh already includes 14e4:43a3 in the brcmfmac path.
install/hardware/fix-bcm43xx.sh only installs broadcom-wl for 14e4:43a0 / 14e4:4331, not 43a3.
So the missing piece appears to be cleanup of legacy broadcom-wl / broadcom-wl-dkms state during the 3.x -> Quattro transition.
Suggested fix
In bin/omarchy-upgrade-to-quattro, detect Apple BCM4350 (14e4:43a3) and remove legacy broadcom-wl / broadcom-wl-dkms before Quattro hardware setup runs.
This should be hardware-gated rather than added to the generic retired-package list, because broadcom-wl is still intentionally used for other Broadcom chipsets.
Example logic:
remove_conflicting_legacy_broadcom_driver() {
local sys_vendor
sys_vendor=$(cat /sys/class/dmi/id/sys_vendor 2>/dev/null || true)
if [[ $sys_vendor == Apple* ]] &&
lspci -nn | grep -qi '14e4:43a3'; then
local pkg
for pkg in broadcom-wl broadcom-wl-dkms; do
if package_installed_exact "$pkg"; then
log "Removing legacy $pkg for Apple BCM4350; Quattro uses brcmfmac"
as_root pacman -Rns --noconfirm "$pkg" ||
warn "Could not remove legacy Broadcom driver '$pkg'"
fi
done
fi
}Happy to test a proposed patch on the affected machine.
View raw text
## Summary
Upgrading an Intel Mac with Broadcom BCM4350 (`14e4:43a3`) from Omarchy 3.x to Quattro can leave the legacy `broadcom-wl-dkms` package installed. Quattro already treats `14e4:43a3` as a `brcmfmac` device, but the legacy `broadcom-wl-dkms` package blacklists `brcmfmac`. The proprietary `wl` module then fails during initialization, leaving the system with no Wi-Fi interface.
## Reproduction / observed behavior
Hardware:
```text
Broadcom BCM4350 802.11ac
PCI ID: 14e4:43a3
Apple subsystem
```
After upgrading to Quattro:
```text
broadcom-wl-dkms 6.30.223.271-48 installed
```
The `wl` module builds successfully via DKMS, but fails at runtime:
```text
wl driver 6.30.223.271 failed with code 1
ERROR @wl_cfg80211_detach
NULL ndev->ieee80211ptr, unable to deref wl
```
Result:
```text
iw dev
# no interfaces
nmcli device status
# no Wi-Fi device
```
A pre-upgrade snapshot on the same machine showed the BCM4350 working normally with the in-kernel driver:
```text
Kernel driver in use: brcmfmac
wlp2s0 wifi connected
```
Removing `broadcom-wl-dkms` from the current Quattro installation and rebooting the current kernel immediately restored Wi-Fi:
```text
Kernel driver in use: brcmfmac
wlp2s0 wifi connected
```
This was verified on both the pre-upgrade snapshot and the current Quattro kernel, so this is not a kernel downgrade workaround; the causal difference is the legacy `broadcom-wl-dkms` package/blacklist.
## Relevant Quattro behavior
`install/hardware/apple/fix-brcmfmac-supplicant.sh` already includes `14e4:43a3` in the `brcmfmac` path.
`install/hardware/fix-bcm43xx.sh` only installs `broadcom-wl` for `14e4:43a0` / `14e4:4331`, not `43a3`.
So the missing piece appears to be cleanup of legacy `broadcom-wl` / `broadcom-wl-dkms` state during the 3.x -> Quattro transition.
## Suggested fix
In `bin/omarchy-upgrade-to-quattro`, detect Apple BCM4350 (`14e4:43a3`) and remove legacy `broadcom-wl` / `broadcom-wl-dkms` before Quattro hardware setup runs.
This should be hardware-gated rather than added to the generic retired-package list, because `broadcom-wl` is still intentionally used for other Broadcom chipsets.
Example logic:
```bash
remove_conflicting_legacy_broadcom_driver() {
local sys_vendor
sys_vendor=$(cat /sys/class/dmi/id/sys_vendor 2>/dev/null || true)
if [[ $sys_vendor == Apple* ]] &&
lspci -nn | grep -qi '14e4:43a3'; then
local pkg
for pkg in broadcom-wl broadcom-wl-dkms; do
if package_installed_exact "$pkg"; then
log "Removing legacy $pkg for Apple BCM4350; Quattro uses brcmfmac"
as_root pacman -Rns --noconfirm "$pkg" ||
warn "Could not remove legacy Broadcom driver '$pkg'"
fi
done
fi
}
```
Happy to test a proposed patch on the affected 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 09:47 UTC