Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1244GitHub issuePublicDecided· Out of scope

BCM43602 (pre-T2 2017 MacBook Pro): feature_disable=0x82000 is not enough — regulatory domain is also required

Reported by benjarlett · filed Aug 29, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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

BCM43602 (pre-T2 2017 MacBook Pro): feature_disable=0x82000 is not enough — regulatory domain is also requiredrevision 1 · captured 2026-09-28 21:24 UTC via poll

On a MacBookPro14,3 (2017, BCM43602 rev 02) running Omarchy 4.0.1 / kernel 7.1.9-arch1-2, Wi-Fi would not associate to a WPA2 AP after install — associating → disconnected in ~200–600 ms, repeating until NetworkManager's 45 s timeout gave a spurious no-secrets error.

The merged #6652 quirk (options brcmfmac feature_disable=0x82000) was tried and did not resolve it on this machine.

Root cause: cfg80211 boots with no regulatory domain set — this hardware has no ACPI/EFI regulatory-hint source for brcmfmac to read — so it stays in the default "world" domain and association fails until enough beacon-derived country hints accumulate (~47 minutes here). dmesg was silent the whole time until the moment association finally succeeded: cfg80211: Regulatory domain changed to country: GB.

Verified fix:

# /etc/modprobe.d/cfg80211.conf
options cfg80211 ieee80211_regdom=GB

then rebuild the Limine-managed unified kernel image (sudo limine-mkinitcpio, or limine-update per the installed version) and reboot. (May also need sudo rfkill unblock wifi + enabling NetworkManager's Wi-Fi radio if a soft-block persists.)

Result: cold-reboot verified — iw reg get shows country GB: DFS-ETSI from boot, the saved profile associates immediately with no retries, and the fix survives reboots.

Suggest the installer consider setting the user's regulatory domain on Apple/Broadcom hardware rather than relying on beacon-hint accumulation.

View raw text
On a MacBookPro14,3 (2017, BCM43602 rev 02) running Omarchy 4.0.1 / kernel 7.1.9-arch1-2, Wi-Fi would not associate to a WPA2 AP after install — `associating → disconnected` in ~200–600 ms, repeating until NetworkManager's 45 s timeout gave a spurious `no-secrets` error.

The merged #6652 quirk (`options brcmfmac feature_disable=0x82000`) was tried and did **not** resolve it on this machine.

**Root cause:** `cfg80211` boots with no regulatory domain set — this hardware has no ACPI/EFI regulatory-hint source for `brcmfmac` to read — so it stays in the default "world" domain and association fails until enough beacon-derived country hints accumulate (~47 minutes here). `dmesg` was silent the whole time until the moment association finally succeeded: `cfg80211: Regulatory domain changed to country: GB`.

**Verified fix:**
```
# /etc/modprobe.d/cfg80211.conf
options cfg80211 ieee80211_regdom=GB
```
then rebuild the Limine-managed unified kernel image (`sudo limine-mkinitcpio`, or `limine-update` per the installed version) and reboot. (May also need `sudo rfkill unblock wifi` + enabling NetworkManager's Wi-Fi radio if a soft-block persists.)

**Result:** cold-reboot verified — `iw reg get` shows `country GB: DFS-ETSI` from boot, the saved profile associates immediately with no retries, and the fix survives reboots.

Suggest the installer consider setting the user's regulatory domain on Apple/Broadcom hardware rather than relying on beacon-hint accumulation.

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 10:01 UTC