Proof Portal

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-4407GitHub issuePublicReceived

MT7925U USB Wi-Fi fails after warm reboot on Omarchy kernel 7.0.3; upstream mt76 fix available

Reported by SamCod3 · filed May 15, 2026Closed upstream on 2026-05-15. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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?
Not yet mapped to any requirement or component.
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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

MT7925U USB Wi-Fi fails after warm reboot on Omarchy kernel 7.0.3; upstream mt76 fix availablerevision 1 · captured 2026-10-04 11:56 UTC via poll

Summary

On Omarchy 3.8.1 / Arch Linux with kernel 7.0.3-arch1-2, a NetGear / MediaTek MT7925U USB Wi-Fi adapter fails to initialize after a warm reboot.

The USB device enumerates, but the mt7925u driver probe fails with -110. The adapter only starts working after a physical unplug/replug.

This matches an upstream mt76 bug fixed by a patch that adds MT7925U-specific USB WFSYS reset handling.

Upstream patch

This appears to be fixed upstream by the following mt76 patch:

The patch description matches this failure mode: after a warm reboot, mt7925u fails WFSYS reset and the driver probe fails with -110. After a physical unplug/replug, the device initializes normally.

Affected system

  • Omarchy: 3.8.1
  • Distribution: Arch Linux / Omarchy
  • Kernel: 7.0.3-arch1-2
  • Kernel package: linux 7.0.3.arch1-2
  • Firmware: linux-firmware 20260410-1, linux-firmware-mediatek 20260410-1
  • Machine: GEEKOM A9 Max
  • CPU/GPU: AMD Ryzen AI 9 HX 370 / Radeon 890M
  • BIOS: American Megatrends LLC. 0.25, date 12/08/2025
  • USB Wi-Fi adapter: NetGear / MediaTek MT7925U
  • USB ID: 0846:9072
  • Driver: mt7925u

The internal PCIe MediaTek Wi-Fi is disabled separately via blacklist mt7925e; this report is only about the external USB adapter using mt7925u.

Current module info

filename: /lib/modules/7.0.3-arch1-2/kernel/drivers/net/wireless/mediatek/mt76/mt7925/mt7925u.ko.zst
description: MediaTek MT7925U (USB) wireless driver
firmware: mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin
firmware: mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin
alias: usb:v0846p9072d*dc*dsc*dp*icFFiscFFipFFin*
depends: mt7925-common,mt792x-usb,mt76-usb,mt76,mt792x-lib,mt76-connac-lib
vermagic: 7.0.3-arch1-2 SMP preempt mod_unload

Failure after warm reboot

After a warm reboot, the adapter enumerates but the driver probe fails:

usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd
usb 4-2: New USB device found, idVendor=0846, idProduct=9072, bcdDevice= 1.00
usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 4-2: Product: Wireless_Device
usb 4-2: Manufacturer: MediaTek Inc.
usb 4-2: SerialNumber: 000000000
usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
mt7925u 4-2:1.0: probe with driver mt7925u failed with error -110
usbcore: registered new interface driver mt7925u

Recovery after physical unplug/replug

After physically unplugging and reconnecting the same USB adapter:

usb 4-2: USB disconnect, device number 2
usb 4-2: new SuperSpeed USB device number 4 using xhci_hcd
usb 4-2: New USB device found, idVendor=0846, idProduct=9072, bcdDevice= 1.00
usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 4-2: Product: Wireless_Device
usb 4-2: Manufacturer: MediaTek Inc.
usb 4-2: SerialNumber: 000000000
usb 4-2: reset SuperSpeed USB device number 4 using xhci_hcd
mt7925u 4-2:1.0: HW/SW Version: 0x8a108a10, Build Time: 20260106153007a
mt7925u 4-2:1.0: WM Firmware Version: ____000000, Build Time: 20260106153120

The interface then appears as expected:

wlan1 UP 28:94:01:bc:a5:a8 <BROADCAST,MULTICAST,UP,LOWER_UP>

Previous related report

I previously reported the same issue against Fedora CachyOS kernel builds:

https://github.com/CachyOS/copr-linux-cachyos/issues/92

After later CachyOS kernel updates on Fedora, the issue stopped reproducing there. The current Omarchy system still reproduces it with Arch linux 7.0.3.arch1-2.

Request

I understand Omarchy may not directly maintain Arch's core/linux package. However, since Omarchy users receive the kernel through the Omarchy/Arch setup and Omarchy also carries some kernel packages in its own repo, could you consider one of these options?

  • Apply/backport upstream commit 56154fef47d104effa9f29ed3db4f805cbc0d640 to any Omarchy-provided kernel package if applicable.
  • Track or provide a kernel build that already includes this mt76/mt7925u WFSYS reset fix.
  • Document this as a known issue for MT7925U USB Wi-Fi users on affected kernels, recommending a fixed kernel version once available.

Thanks.

View raw text
## Summary

On Omarchy 3.8.1 / Arch Linux with kernel `7.0.3-arch1-2`, a NetGear / MediaTek MT7925U USB Wi-Fi adapter fails to initialize after a warm reboot.

The USB device enumerates, but the `mt7925u` driver probe fails with `-110`. The adapter only starts working after a physical unplug/replug.

This matches an upstream mt76 bug fixed by a patch that adds MT7925U-specific USB WFSYS reset handling.

## Upstream patch

This appears to be fixed upstream by the following mt76 patch:

- Commit: `56154fef47d104effa9f29ed3db4f805cbc0d640`
- Subject: `wifi: mt76: mt792x: fix mt7925u USB WFSYS reset handling`
- Patch purpose: add a chip-specific USB WFSYS reset descriptor for `mt7925u`, because `mt7925u` uses different reset/status registers from `mt7921u`
- Stable thread: https://www.spinics.net/lists/stable/msg939362.html
- Linux-mediatek discussion: https://lists.infradead.org/pipermail/linux-mediatek/2026-March/104805.html

The patch description matches this failure mode: after a warm reboot, `mt7925u` fails WFSYS reset and the driver probe fails with `-110`. After a physical unplug/replug, the device initializes normally.

## Affected system

- Omarchy: `3.8.1`
- Distribution: Arch Linux / Omarchy
- Kernel: `7.0.3-arch1-2`
- Kernel package: `linux 7.0.3.arch1-2`
- Firmware: `linux-firmware 20260410-1`, `linux-firmware-mediatek 20260410-1`
- Machine: GEEKOM A9 Max
- CPU/GPU: AMD Ryzen AI 9 HX 370 / Radeon 890M
- BIOS: American Megatrends LLC. `0.25`, date `12/08/2025`
- USB Wi-Fi adapter: NetGear / MediaTek MT7925U
- USB ID: `0846:9072`
- Driver: `mt7925u`

The internal PCIe MediaTek Wi-Fi is disabled separately via `blacklist mt7925e`; this report is only about the external USB adapter using `mt7925u`.

## Current module info

```text
filename: /lib/modules/7.0.3-arch1-2/kernel/drivers/net/wireless/mediatek/mt76/mt7925/mt7925u.ko.zst
description: MediaTek MT7925U (USB) wireless driver
firmware: mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin
firmware: mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin
alias: usb:v0846p9072d*dc*dsc*dp*icFFiscFFipFFin*
depends: mt7925-common,mt792x-usb,mt76-usb,mt76,mt792x-lib,mt76-connac-lib
vermagic: 7.0.3-arch1-2 SMP preempt mod_unload
```

## Failure after warm reboot

After a warm reboot, the adapter enumerates but the driver probe fails:

```text
usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd
usb 4-2: New USB device found, idVendor=0846, idProduct=9072, bcdDevice= 1.00
usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 4-2: Product: Wireless_Device
usb 4-2: Manufacturer: MediaTek Inc.
usb 4-2: SerialNumber: 000000000
usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
mt7925u 4-2:1.0: probe with driver mt7925u failed with error -110
usbcore: registered new interface driver mt7925u
```

## Recovery after physical unplug/replug

After physically unplugging and reconnecting the same USB adapter:

```text
usb 4-2: USB disconnect, device number 2
usb 4-2: new SuperSpeed USB device number 4 using xhci_hcd
usb 4-2: New USB device found, idVendor=0846, idProduct=9072, bcdDevice= 1.00
usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 4-2: Product: Wireless_Device
usb 4-2: Manufacturer: MediaTek Inc.
usb 4-2: SerialNumber: 000000000
usb 4-2: reset SuperSpeed USB device number 4 using xhci_hcd
mt7925u 4-2:1.0: HW/SW Version: 0x8a108a10, Build Time: 20260106153007a
mt7925u 4-2:1.0: WM Firmware Version: ____000000, Build Time: 20260106153120
```

The interface then appears as expected:

```text
wlan1 UP 28:94:01:bc:a5:a8 <BROADCAST,MULTICAST,UP,LOWER_UP>
```

## Previous related report

I previously reported the same issue against Fedora CachyOS kernel builds:

https://github.com/CachyOS/copr-linux-cachyos/issues/92

After later CachyOS kernel updates on Fedora, the issue stopped reproducing there. The current Omarchy system still reproduces it with Arch `linux 7.0.3.arch1-2`.

## Request

I understand Omarchy may not directly maintain Arch's `core/linux` package. However, since Omarchy users receive the kernel through the Omarchy/Arch setup and Omarchy also carries some kernel packages in its own repo, could you consider one of these options?

- Apply/backport upstream commit `56154fef47d104effa9f29ed3db4f805cbc0d640` to any Omarchy-provided kernel package if applicable.
- Track or provide a kernel build that already includes this mt76/mt7925u WFSYS reset fix.
- Document this as a known issue for MT7925U USB Wi-Fi users on affected kernels, recommending a fixed kernel version once available.

Thanks.

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.

No decision has been recorded yet.