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.
linux-omarchy 7.2.5-3: Intel AX200 can't authenticate on 5 GHz (auth timeout), 2.4 GHz fine; stock linux 7.2.3 works
Reported by patseev · filed Oct 11, 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
After the 4.0.4 update made linux-omarchy the default boot entry, my AX200 can no longer join my 5 GHz network. NetworkManager silently falls back to the 2.4 GHz SSID on the same router. Booting the stock linux 7.2.3 entry restores 5 GHz immediately.
System
- Omarchy 4.0.4-1, AMD Ryzen 7 8745HS
- Intel Wi-Fi 6 AX200 8086:2723 / 8086:0084, iwlwifi, firmware 77.aa2dd297.0 cc-a0-77.ucode (identical on both kernels)
- linux-firmware 20260810-2, wireless-regdb 2026.05.30-1, NetworkManager 1.58.1 + wpa_supplicant 2.12
- AP: TP-Link, 5 GHz on ch 36 (5180 MHz) / 80 MHz; regdomain ES
On `7.2.5-3-omarchy`: every 5 GHz attempt times out at the auth stage (12 attempts over ~7.5 h, 0 successes):
wlp3s0: send auth to 30:68:93:7f:94:f3 (try 1/3)
iwlwifi 0000:03:00.0: Not associated and the session protection is over already...
wlp3s0: Connection to AP 30:68:93:7f:94:f3 lost
...
wlp3s0: authentication with 30:68:93:7f:94:f3 timed out2.4 GHz (ch 10, 2457 MHz) on the same AP connects on the first try every time.
On `7.2.3-arch1-3` (rebooted minutes later): connects to the same 5 GHz BSSID on the first attempt, ch 36 / 80 MHz.
Notes
- The wireless-relevant kernel config (IWL*, CFG80211*, MAC80211*) is identical between the two kernels except CFG80211_CERTIFICATION_ONUS, so this looks like a code difference: Omarchy patches or an upstream 7.2.3 → 7.2.5 change. I can't tell which yet.
- Not #13030: this is an AMD host with no DMAR/AER errors, and the radio works on 2.4 GHz.
- Workaround: put linux first in BOOT_ORDER in /etc/default/limine and run limine-update.
Only one boot on linux-omarchy so far. Happy to test 7.2.7 or a debug build.
Filed by Claude Opus 5.5 via Claude Code.
View raw text
After the 4.0.4 update made `linux-omarchy` the default boot entry, my AX200 can no longer join my 5 GHz network. NetworkManager silently falls back to the 2.4 GHz SSID on the same router. Booting the stock `linux` 7.2.3 entry restores 5 GHz immediately. **System** - Omarchy 4.0.4-1, AMD Ryzen 7 8745HS - Intel Wi-Fi 6 AX200 `8086:2723` / `8086:0084`, `iwlwifi`, firmware `77.aa2dd297.0 cc-a0-77.ucode` (identical on both kernels) - `linux-firmware` 20260810-2, `wireless-regdb` 2026.05.30-1, NetworkManager 1.58.1 + wpa_supplicant 2.12 - AP: TP-Link, 5 GHz on ch 36 (5180 MHz) / 80 MHz; regdomain ES **On `7.2.5-3-omarchy`:** every 5 GHz attempt times out at the auth stage (12 attempts over ~7.5 h, 0 successes): ``` wlp3s0: send auth to 30:68:93:7f:94:f3 (try 1/3) iwlwifi 0000:03:00.0: Not associated and the session protection is over already... wlp3s0: Connection to AP 30:68:93:7f:94:f3 lost ... wlp3s0: authentication with 30:68:93:7f:94:f3 timed out ``` 2.4 GHz (ch 10, 2457 MHz) on the same AP connects on the first try every time. **On `7.2.3-arch1-3` (rebooted minutes later):** connects to the same 5 GHz BSSID on the first attempt, ch 36 / 80 MHz. **Notes** - The wireless-relevant kernel config (`IWL*`, `CFG80211*`, `MAC80211*`) is identical between the two kernels except `CFG80211_CERTIFICATION_ONUS`, so this looks like a code difference: Omarchy patches or an upstream 7.2.3 → 7.2.5 change. I can't tell which yet. - Not #13030: this is an AMD host with no DMAR/AER errors, and the radio works on 2.4 GHz. - Workaround: put `linux` first in `BOOT_ORDER` in `/etc/default/limine` and run `limine-update`. Only one boot on `linux-omarchy` so far. Happy to test `7.2.7` or a debug build. Filed by Claude Opus 5.5 via Claude Code.
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-11 20:49 UTC