Arch Linux

karm235

Member

Registered: 2025-04-18

Posts: 1

Struggling to Connect to WiFi Using Mediatek MT7922 Chip

Something I have been struggling with the past couple of days is getting WiFi to work reliably on a relatively fresh installation of Arch using KDE Plasma using iwd as a backend for NetworkManager. The issue at hand is that connecting to any WiFi network (tried two home networks on 2.4 and 5GHz bands, and phone hotspot on 5GHz) fails, reporting supplicant-disconnect by NetworkManager (desktop notification "Authorization Supplicant Disconnected" appears as well).

Journalctl snippet example showing this failure:

Apr 18 13:40:19 karm-archv2 NetworkManager[906]: <info>  [1745001619.3397] audit: op="statistics" interface="enp11s0u1" ifindex=6 args="2000" pid=1740 uid=1000 result="success"
Apr 18 13:40:21 karm-archv2 iwd[954]: invalid HE capabilities for c0:94:35:b0:23:f0
Apr 18 13:40:31 karm-archv2 iwd[954]: invalid HE capabilities for c0:94:35:b0:23:f0
Apr 18 13:40:31 karm-archv2 iwd[954]: invalid HE capabilities for ce:94:35:b0:23:f0
Apr 18 13:40:31 karm-archv2 iwd[954]: invalid HE capabilities for d6:94:35:b0:23:f0
Apr 18 13:40:35 karm-archv2 iwd[954]: event: connect-info, ssid: Tankernet-5.0, bss: e2:db:d1:1d:f4:46, signal: -47, load: 42/255
Apr 18 13:40:35 karm-archv2 iwd[954]: event: state, old: autoconnect_full, new: connecting
Apr 18 13:40:35 karm-archv2 NetworkManager[906]: <info>  [1745001635.1988] device (wlan0): new IWD device state is connecting
Apr 18 13:40:35 karm-archv2 NetworkManager[906]: <info>  [1745001635.1992] device (wlan0): Activation: starting connection 'Tankernet-5.0' (d6c91ca9-2967-471d-b278-cf8c8a7d684c)
Apr 18 13:40:35 karm-archv2 NetworkManager[906]: <info>  [1745001635.1993] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Apr 18 13:40:35 karm-archv2 NetworkManager[906]: <info>  [1745001635.1994] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Apr 18 13:40:35 karm-archv2 iwd[954]: event: connect-timeout, reason: 0
Apr 18 13:40:35 karm-archv2 iwd[954]: event: connect-failed, status: 1
Apr 18 13:40:35 karm-archv2 iwd[954]: event: state, old: connecting, new: disconnected
Apr 18 13:40:35 karm-archv2 iwd[954]: event: state, old: disconnected, new: autoconnect_quick
Apr 18 13:40:35 karm-archv2 NetworkManager[906]: <info>  [1745001635.4063] device (wlan0): new IWD device state is disconnected
Apr 18 13:40:35 karm-archv2 NetworkManager[906]: <info>  [1745001635.4064] device (wlan0): state change: config -> failed (reason 'supplicant-disconnect', managed-type: 'full')
Apr 18 13:40:35 karm-archv2 NetworkManager[906]: <warn>  [1745001635.4065] device (wlan0): Activation: failed for connection 'Tankernet-5.0'
Apr 18 13:40:35 karm-archv2 NetworkManager[906]: <info>  [1745001635.4066] device (wlan0): state change: failed -> disconnected (reason 'none', managed-type: 'full')

From the get go I opted to use iwd and at a time I had managed to get it work after doing a combination of the following:

* Setting EnableNetworkConfiguration=true in /etc/iwd/main.conf to use its built-in network configs
* Setting wifi.backend=iwd in /etc/NetworkManager/conf.d/wifi_backend.conf
* Ensuring wpa_supplicant is never in use
* Ensuring that wlan is not blocked through rfkill and subsequently manually blocking and unblocking it for sanity
* Ensuring iwd is not enabled (if not mistaken, not a good idea to enable with NetworkManager using it)
* Manually setting the passphrase for the WiFi network in question by making a file in /var/lib/iwd/ (in my case: /var/lib/iwd/Tankernet-5.0.psk)
* Updated the Mediatek drivers in /lib/firmware/mediatek/

At some point, doing all of this did make it work, but I am unsure as to why it has resorted to not doing so after a day.

Journalctl: https://0x0.st/8O1E.txt
Dmesg: https://0x0.st/8O1I.txt

Specs (if they matter):
- Mobo: ASRock B650M Pro RS WiFi
- CPU: AMD Ryzen 9 9950X
- RAM: 64GB DDR5 6000MHz

lspci -v:

05:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
        Subsystem: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
        Flags: bus master, fast devsel, latency 0, IRQ 173, IOMMU group 16
        Memory at f5800000 (64-bit, prefetchable) [size=1M]
        Memory at f5900000 (64-bit, non-prefetchable) [size=32K]
        Capabilities: [80] Express Endpoint, IntMsgNum 0
        Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
        Capabilities: [f8] Power Management version 3
        Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
        Capabilities: [108] Latency Tolerance Reporting
        Capabilities: [110] L1 PM Substates
        Capabilities: [200] Advanced Error Reporting
        Kernel driver in use: mt7921e
        Kernel modules: mt7921e

Apologies if I am missing anything that would help find the problem; this has sent me running in circles.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,315

Re: Struggling to Connect to WiFi Using Mediatek MT7922 Chip

Setting EnableNetworkConfiguration=true in /etc/iwd/main.conf to use its built-in network configs

will make iwd collide w/ NM for sure. Don't.

Apr 18 13:38:37 karm-archv2 NetworkManager[906]: <info>  [1745001517.6265] device (enp11s0u1): carrier: link connected
Apr 18 13:38:37 karm-archv2 NetworkManager[906]: <info>  [1745001517.6266] device (enp11s0u1): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Apr 18 13:38:37 karm-archv2 NetworkManager[906]: <info>  [1745001517.6269] device (enp11s0u1): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Apr 18 13:38:39 karm-archv2 NetworkManager[906]: <info>  [1745001519.9938] manager: NetworkManager state is now CONNECTED_SITE
Apr 18 13:38:40 karm-archv2 NetworkManager[906]: <info>  [1745001520.3342] manager: NetworkManager state is now CONNECTED_GLOBAL

You've a connection on enp11s0u1 - I'm not even sure why NM would try to establish a wireless one?
On top of that there's an active tailscale service, you might want to disabled that until you figured the network works w/o VPN.

Apr 18 13:40:35 karm-archv2 iwd[954]: event: connect-info, ssid: Tankernet-5.0, bss: e2:db:d1:1d:f4:46, signal: -47, load: 42/255
Apr 18 13:41:45 karm-archv2 iwd[954]: event: connect-info, ssid: Tankernet-5.0, bss: e2:db:d1:1d:f4:46, signal: -46, load: 32/255
Apr 18 13:42:48 karm-archv2 iwd[954]: event: connect-info, ssid: Tankernet-5.0, bss: e2:db:d1:1d:f4:46, signal: -45, load: 56/255
Apr 18 13:42:48 karm-archv2 kernel: wlan0: authenticate with e2:db:d1:1d:f4:46 (local address=3c:0a:f3:ba:86:3b)
Apr 18 13:42:49 karm-archv2 kernel: wlan0: send auth to e2:db:d1:1d:f4:46 (try 1/3)
Apr 18 13:42:49 karm-archv2 kernel: wlan0: send auth to e2:db:d1:1d:f4:46 (try 2/3)
Apr 18 13:42:49 karm-archv2 kernel: wlan0: send auth to e2:db:d1:1d:f4:46 (try 3/3)
Apr 18 13:42:49 karm-archv2 kernel: wlan0: authentication with e2:db:d1:1d:f4:46 timed out
Apr 18 13:44:04 karm-archv2 iwd[954]: event: connect-info, ssid: Tankernet-5.0, bss: e2:db:d1:1d:f4:46, signal: -46, load: 33/255
Apr 18 13:46:59 karm-archv2 iwd[954]: event: connect-info, ssid: Tankernet-5.0, bss: e2:db:d1:1d:f4:46, signal: -48, load: 45/255
Apr 18 13:46:59 karm-archv2 kernel: wlan0: authenticate with e2:db:d1:1d:f4:46 (local address=3c:0a:f3:ba:86:3b)
Apr 18 13:46:59 karm-archv2 kernel: wlan0: send auth to e2:db:d1:1d:f4:46 (try 1/3)
Apr 18 13:46:59 karm-archv2 kernel: wlan0: send auth to e2:db:d1:1d:f4:46 (try 2/3)
Apr 18 13:46:59 karm-archv2 kernel: wlan0: send auth to e2:db:d1:1d:f4:46 (try 3/3)
Apr 18 13:46:59 karm-archv2 kernel: wlan0: authentication with e2:db:d1:1d:f4:46 timed out

Signal is good, there's no indication of hardware/firmware/module failure but the authentication repeatedly times out.
Disable https://wiki.archlinux.org/title/Networ … domization - some APs consider that malicious and stop talking to you in repsonse.

Ceterum censeo: is there a parallel windows installation?
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc