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-2121GitHub issuePublicDecided· Out of scope

linux-omarchy 7.2.5: mt7925e cannot associate with any BSS ("Rejecting MLO as it is not supported by AP", auth request to driver failed); linux-lts works

Reported by mjh-cad · filed Sep 30, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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

linux-omarchy 7.2.5: mt7925e cannot associate with any BSS ("Rejecting MLO as it is not supported by AP", auth request to driver failed); linux-lts worksrevision 1 · captured 2026-09-30 08:15 UTC via poll

Summary

After updating on 2026-09-30 (which installed linux-omarchy 7.2.5-3), the MediaTek MT7925 (mt7925e, PCIe) Wi-Fi card cannot connect to a known network on linux-omarchy. Every authentication attempt fails immediately in the driver, on every band (2.4, 5 and 6 GHz). Booting linux-lts 6.18.49-3 on the same machine, with the same firmware and config, connects normally.

System

  • Omarchy 4.0.4-1, bootloader Limine 12.8.0
  • Card: MEDIATEK MT7925 (RZ717) Wi-Fi 7 [14c3:0717], driver mt7925e
  • Firmware: linux-firmware 20260810-2 (WM Firmware ... Build Time: 20260605184805)
  • NetworkManager 1.58.1 + wpa_supplicant (not iwd)
  • Kernels: fails on 7.2.5-3-omarchy; works on 6.18.49-3-lts and 6.18.46-1-lts
  • AP: one SSID on three BSSIDs: 2.4 GHz ch7 (WPA2/WPA3), 5 GHz ch100 (WPA2/WPA3), 6 GHz 5975 MHz (WPA3 only). The AP does not do MLO.

Steps to reproduce

  1. Install linux-omarchy 7.2.5-3 and boot into it.
  2. Let NetworkManager autoconnect to a saved WPA2/WPA3 network whose AP broadcasts multiple bands.
  3. The connection never comes up; NM ends with config -> failed (reason 'ssid-not-found').

Logs (7.2.5-3-omarchy)

Every attempt, on every BSSID, fails in about 60 ms without any frames being sent:

kernel: wlp9s0: Rejecting MLO as it is not supported by AP
wpa_supplicant: wlp9s0: SME: Trying to authenticate with ba:7c:61:ef:f1:75 (SSID='CadRetail' freq=5500 MHz)
wpa_supplicant: wlp9s0: Failed to get MLO link info
wpa_supplicant: wlp9s0: SME: Authentication request to the driver failed
wpa_supplicant: wlp9s0: Added BSSID ba:7c:61:ef:f1:75 into ignore list, ignoring for 10 seconds
wpa_supplicant: wlp9s0: SME: Trying to authenticate with 9a:7c:61:ef:f1:71 (SSID='CadRetail' freq=2442 MHz)
wpa_supplicant: wlp9s0: SME: Authentication request to the driver failed
wpa_supplicant: wlp9s0: SME: Trying to authenticate with 10:7c:61:ef:f1:79 (SSID='CadRetail' freq=5975 MHz)
wpa_supplicant: wlp9s0: SME: Authentication request to the driver failed
...
wpa_supplicant: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CadRetail" auth_failures=2 duration=20 reason=CONN_FAILED
NetworkManager: device (wlp9s0): state change: config -> failed (reason 'ssid-not-found')

This repeats until NetworkManager gives up. On linux-lts the same attempts reach send auth, associated, and CTRL-EVENT-CONNECTED.

Retest with profile pinned to 5 GHz (802-11-wireless.band a)

Still fails after locking the connection to 5 GHz, so the WPA3-only 6 GHz BSS is not involved. In a 2-minute window on 7.2.5-3-omarchy: 11 attempts, all at freq=5500 MHz (ch100, a normal non-MLO WPA2/WPA3 BSS). Every one logged Rejecting MLO as it is not supported by AP and Authentication request to the driver failed. NM cycled config -> failed (reason 'ssid-not-found') every ~28 s.

The same profile connects straight away on 6.18.49-3-lts, reaching CTRL-EVENT-CONNECTED and a DHCP lease.

Not yet tested on this machine: the stock Arch linux 7.2.3-arch1-3. So it isn't clear whether this is specific to linux-omarchy or an upstream 7.2 mac80211/mt7925 regression. #11219 reports mt7925e associating (with other issues) on 7.2.3-arch1-3, which points at linux-omarchy.

Expected

linux-omarchy should associate with non-MLO APs, as linux-lts does. The "Rejecting MLO" path seems to fail the whole authentication request instead of falling back to a normal non-MLO association.

Workaround

Boot linux-lts: put linux-lts first in BOOT_ORDER in /etc/default/limine.

Related

  • #11219: a different mt7925e issue (deauth with reason 15 right after the 4-way handshake)
View raw text
### Summary

After updating on 2026-09-30 (which installed `linux-omarchy 7.2.5-3`), the MediaTek MT7925 (mt7925e, PCIe) Wi-Fi card cannot connect to a known network on `linux-omarchy`. Every authentication attempt fails immediately in the driver, on every band (2.4, 5 and 6 GHz). Booting `linux-lts 6.18.49-3` on the same machine, with the same firmware and config, connects normally.

### System

- Omarchy 4.0.4-1, bootloader Limine 12.8.0
- Card: MEDIATEK MT7925 (RZ717) Wi-Fi 7 [14c3:0717], driver `mt7925e`
- Firmware: linux-firmware 20260810-2 (`WM Firmware ... Build Time: 20260605184805`)
- NetworkManager 1.58.1 + wpa_supplicant (not iwd)
- Kernels: fails on `7.2.5-3-omarchy`; works on `6.18.49-3-lts` and `6.18.46-1-lts`
- AP: one SSID on three BSSIDs: 2.4 GHz ch7 (WPA2/WPA3), 5 GHz ch100 (WPA2/WPA3), 6 GHz 5975 MHz (WPA3 only). The AP does not do MLO.

### Steps to reproduce

1. Install `linux-omarchy 7.2.5-3` and boot into it.
2. Let NetworkManager autoconnect to a saved WPA2/WPA3 network whose AP broadcasts multiple bands.
3. The connection never comes up; NM ends with `config -> failed (reason 'ssid-not-found')`.

### Logs (7.2.5-3-omarchy)

Every attempt, on every BSSID, fails in about 60 ms without any frames being sent:

```
kernel: wlp9s0: Rejecting MLO as it is not supported by AP
wpa_supplicant: wlp9s0: SME: Trying to authenticate with ba:7c:61:ef:f1:75 (SSID='CadRetail' freq=5500 MHz)
wpa_supplicant: wlp9s0: Failed to get MLO link info
wpa_supplicant: wlp9s0: SME: Authentication request to the driver failed
wpa_supplicant: wlp9s0: Added BSSID ba:7c:61:ef:f1:75 into ignore list, ignoring for 10 seconds
wpa_supplicant: wlp9s0: SME: Trying to authenticate with 9a:7c:61:ef:f1:71 (SSID='CadRetail' freq=2442 MHz)
wpa_supplicant: wlp9s0: SME: Authentication request to the driver failed
wpa_supplicant: wlp9s0: SME: Trying to authenticate with 10:7c:61:ef:f1:79 (SSID='CadRetail' freq=5975 MHz)
wpa_supplicant: wlp9s0: SME: Authentication request to the driver failed
...
wpa_supplicant: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="CadRetail" auth_failures=2 duration=20 reason=CONN_FAILED
NetworkManager: device (wlp9s0): state change: config -> failed (reason 'ssid-not-found')
```

This repeats until NetworkManager gives up. On linux-lts the same attempts reach `send auth`, `associated`, and `CTRL-EVENT-CONNECTED`.

### Retest with profile pinned to 5 GHz (`802-11-wireless.band a`)

Still fails after locking the connection to 5 GHz, so the WPA3-only 6 GHz BSS is not involved. In a 2-minute window on `7.2.5-3-omarchy`: 11 attempts, all at `freq=5500 MHz` (ch100, a normal non-MLO WPA2/WPA3 BSS). Every one logged `Rejecting MLO as it is not supported by AP` and `Authentication request to the driver failed`. NM cycled `config -> failed (reason 'ssid-not-found')` every ~28 s.

The same profile connects straight away on `6.18.49-3-lts`, reaching `CTRL-EVENT-CONNECTED` and a DHCP lease.

Not yet tested on this machine: the stock Arch `linux 7.2.3-arch1-3`. So it isn't clear whether this is specific to linux-omarchy or an upstream 7.2 mac80211/mt7925 regression. #11219 reports mt7925e associating (with other issues) on 7.2.3-arch1-3, which points at linux-omarchy.

### Expected

`linux-omarchy` should associate with non-MLO APs, as `linux-lts` does. The "Rejecting MLO" path seems to fail the whole authentication request instead of falling back to a normal non-MLO association.

### Workaround

Boot `linux-lts`: put `linux-lts` first in `BOOT_ORDER` in `/etc/default/limine`.

### Related

- #11219: a different mt7925e issue (deauth with reason 15 right after the 4-way handshake)

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 20:18 UTC