MT7925 crashes in AP mode

Installing and Using OpenWrt Network and Wireless Configuration
1

MT7925 runs in AP mode on Openwrt running in Proxmox VM

Fri May 9 16:39:55 2025 daemon.notice hostapd: phy1-ap0: ACS-COMPLETED freq=5180 channel=36
Fri May 9 16:39:55 2025 daemon.notice hostapd: phy1-ap0: interface state ACS->HT_SCAN
Fri May 9 16:39:56 2025 daemon.notice netifd: Network device 'phy1-ap0' link is up
Fri May 9 16:39:56 2025 kern.info kernel: [ 19.691718] br-wifi: port 2(phy1-ap0) entered blocking state
Fri May 9 16:39:56 2025 kern.info kernel: [ 19.692173] br-wifi: port 2(phy1-ap0) entered forwarding state
Fri May 9 16:39:56 2025 daemon.notice hostapd: phy1-ap0: interface state HT_SCAN->ENABLED
Fri May 9 16:39:56 2025 daemon.notice hostapd: phy1-ap0: AP-ENABLED

it runs from 1 minute to 6 hours and an error occurs

Fri May 9 17:08:59 2025 kern.err kernel: [ 1763.455660] mt7925e 0000:01:00.0: Message 00020002 (seq 12) timeout
Fri May 9 17:09:00 2025 kern.info kernel: [ 1763.548292] mt7925e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20250425072955a
Fri May 9 17:09:00 2025 kern.info kernel: [ 1763.548292]
Fri May 9 17:09:00 2025 kern.info kernel: [ 1763.889211] mt7925e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20250425073109

But in openwrt, it looks like wifi is running, but no Wifi client sees it. According to the logs, all clients are disconnected

Fri May 9 17:13:55 2025 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED xxxxxx
Fri May 9 17:13:55 2025 daemon.info hostapd: phy1-ap0: STA xxxxxxx IEEE 802.11: disassociated due to inactivity
Fri May 9 17:13:56 2025 daemon.info hostapd: phy1-ap0: STA xxxxxxx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

2

Can the issue be reproduced on bare metal?

2 Likes
3

There is a difficulty, I will try. But at the same time, the MT7922 passthrough to openwrt also works perfectly.

4

Given these posts, can you clarify what regarding "the MT7922 passthrough to openwrt also works perfectly"?

5

The openwrt VM has 2 modules in AP mode at the same time: MT7925 and MT7922. 7922 - works perfectly, 7925 - crashes. Since the 7922 works perfectly, I thought the problem wasn't with proxmox and PCI(e) Passthrough.

1 Like
6

mt7925, as an 802.11BE/ wifi 7 device, has much higher requirements on the hardware, both physical (power delivery, cooling) and latencies and other (potential) side effects stemming from virtualization and pass-through methods (e.g. even on real -bare-iron- hardware, the Intel BE200 cards can be veeery picky about the host's CPU, the BIOS(-settings) and the chosen PCIe slot), aside from the more general topic that mt7925 driver support is still quite early (and yes, neither mt7922 nor mt7925 are AP-oriented chipsets to begin with).

1 Like
7

In the end, changing mt7922 and mt7925 helped me. Initially, mt7925 was installed to m2 "for wifi", and 7922 via an adapter to nvme 2280. When I installed the 7925 to the 2280 adapter, the failures stopped. I don't know what the problem was, but it works. Additionally, 7925 was no longer defined as Generic MAC80211, and became MediaTek MT7925E. 7922 - defined as Generic MAC80211