[RESOLVED] WiFi adapter randomly decides to not connect to networks

citrusyummer · 2025-10-30 02:51:45

I have a TP-Link Archer T2U PLUS and after updating my system it randomly wants to not connect to any of my networks.
It appears through NetworkManager, I connect to any network (Madhouse 5Ghz in this example) and KDE says "Configuring interface". It stays on this for about 15-30 seconds then disconnects and tries the same or another network. Sometimes prompts me for a new password as the last one was "wrong", journal says that I didn't provide any secrets though.

Oct 30 02:26:44 granite iwd[493]: event: state, old: disconnected, new: autoconnect_quick
Oct 30 02:26:44 granite NetworkManager[489]: <warn>  [1761791204.3039] device (wlan0): Activation: failed for connection 'Madhouse 5Ghz'
Oct 30 02:26:44 granite NetworkManager[489]: <info>  [1761791204.3041] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Oct 30 02:26:44 granite NetworkManager[489]: <info>  [1761791204.3042] device (wlan0): state change: failed -> disconnected (reason 'none', managed-type: 'full')
Oct 30 02:26:44 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16
Oct 30 02:26:44 granite NetworkManager[489]: <info>  [1761791204.5421] device (wlan0): supplicant interface state: interface_disabled -> inactive
Oct 30 02:26:44 granite iwd[493]: event: connect-info, ssid: Madhouse 5Ghz, bss: a4:22:49:ed:df:55, signal: -60, load: 3/255
Oct 30 02:26:44 granite iwd[493]: event: state, old: autoconnect_quick, new: connecting (auto)
Oct 30 02:26:45 granite NetworkManager[489]: <info>  [1761791205.0423] policy: auto-activating connection 'Madhouse 5Ghz' (3cebe250-89c5-4818-a524-8530b6a348a8)
Oct 30 02:26:45 granite NetworkManager[489]: <info>  [1761791205.0425] device (wlan0): Activation: starting connection 'Madhouse 5Ghz' (3cebe250-89c5-4818-a524-8530b6a348a8)
Oct 30 02:26:45 granite NetworkManager[489]: <info>  [1761791205.0426] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Oct 30 02:26:45 granite NetworkManager[489]: <info>  [1761791205.0427] manager: NetworkManager state is now CONNECTING
Oct 30 02:26:45 granite kernel: wlan0: authenticate with a4:22:49:ed:df:55 (local address=66:04:cb:77:05:42)
Oct 30 02:26:45 granite kernel: wlan0: send auth to a4:22:49:ed:df:55 (try 1/3)
Oct 30 02:26:45 granite kernel: wlan0: aborting authentication with a4:22:49:ed:df:55 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 30 02:26:45 granite NetworkManager[489]: <info>  [1761791205.3980] device (wlan0): set-hw-addr: reset MAC address to B4:B0:24:9B:06:B7 (preserve)
Oct 30 02:26:45 granite NetworkManager[489]: <info>  [1761791205.6332] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Oct 30 02:26:45 granite NetworkManager[489]: <info>  [1761791205.6333] device (wlan0): Activation: (wifi) access point 'Madhouse 5Ghz' has security, but secrets are required.
Oct 30 02:26:45 granite NetworkManager[489]: <info>  [1761791205.6333] device (wlan0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Oct 30 02:26:45 granite iwd[493]: event: state, old: disconnected, new: autoconnect_quick

It keeps doing this until it RANDOMLY decides to actually connect. Journal outputs this

Oct 30 02:37:57 granite iwd[493]: event: connect-info, ssid: Madhouse 5Ghz, bss: a4:22:49:ed:df:55, signal: -66, load: 3/255
Oct 30 02:37:57 granite iwd[493]: event: state, old: autoconnect_quick, new: connecting (auto)
Oct 30 02:37:57 granite iwd[493]: event: connect-failed, status: 1
Oct 30 02:37:57 granite iwd[493]: event: state, old: connecting (auto), new: disconnected
Oct 30 02:37:57 granite iwd[493]: event: connect-info, ssid: Madhouse 2.4Ghz, bss: a4:22:49:ed:df:54, signal: -60, load: 47/255
Oct 30 02:37:57 granite iwd[493]: event: state, old: disconnected, new: connecting (auto)
Oct 30 02:37:57 granite NetworkManager[489]: <info>  [1761791877.4830] device (wlan0): supplicant interface state: authenticating -> associating
Oct 30 02:37:57 granite iwd[493]: event: connect-failed, status: 1
Oct 30 02:37:57 granite iwd[493]: event: state, old: connecting (auto), new: disconnected
Oct 30 02:37:57 granite iwd[493]: event: state, old: disconnected, new: autoconnect_full
Oct 30 02:37:57 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 30 02:37:57 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5180 max_tx_power=2000 no_ir=1
Oct 30 02:37:57 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5180 max_tx_power=2000
Oct 30 02:37:57 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 30 02:37:57 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5200 max_tx_power=2000 no_ir=1
Oct 30 02:37:57 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5200 max_tx_power=2000
Oct 30 02:37:57 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 30 02:37:57 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=5220 max_tx_power=2000 no_ir=1
Oct 30 02:37:57 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=5220 max_tx_power=2000
Oct 30 02:38:02 granite iwd[493]: wiphy_estimate_data_rate() failed
Oct 30 02:38:02 granite iwd[493]: wiphy_estimate_data_rate() failed
Oct 30 02:38:02 granite kernel: wlan0: associate with a4:22:49:ed:df:54 (try 1/3)
Oct 30 02:38:02 granite kernel: wlan0: RX AssocResp from a4:22:49:ed:df:54 (capab=0x1411 status=0 aid=17)
Oct 30 02:38:02 granite iwd[493]: Unexpected connection related event -- is another supplicant running?
Oct 30 02:38:02 granite wpa_supplicant[614]: wlan0: Associated with a4:22:49:ed:df:54
Oct 30 02:38:02 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct 30 02:38:02 granite kernel: wlan0: associated
Oct 30 02:38:02 granite NetworkManager[489]: <info>  [1761791882.1793] device (wlan0): supplicant interface state: associating -> associated
Oct 30 02:38:02 granite wpa_supplicant[614]: wlan0: WPA: Key negotiation completed with a4:22:49:ed:df:54 [PTK=CCMP GTK=CCMP]
Oct 30 02:38:02 granite wpa_supplicant[614]: wlan0: CTRL-EVENT-CONNECTED - Connection to a4:22:49:ed:df:54 completed [id=1 id_str=]
Oct 30 02:38:02 granite NetworkManager[489]: <info>  [1761791882.1929] device (wlan0): supplicant interface state: associated -> completed

I have downgraded the kernel to 6.17.2 (what i used 2 updates before this one) and it hasn't fixed my problem. I have tried (tried as in unsure if I actually did, i'm a dkms newb ) to install both the rtw88 and 8821au driver, and that hasn't solved my problem.
USB tethering through my iPhone works perfectly fine, so I suspect it's a bad driver.
If you think it's just a buggy package I should downgrade (KDE 6.5 and I think the latest linux-firmware was in that system upgrade) please let me know

Last edited by citrusyummer (2025-10-31 16:24:26)

mmy8x · 2025-10-30 17:09:27

Usually such things are due to the kernel or firmware.
Probably not KDE. Maybe wpa_supplicant or NetworkManager, but see usual suspects above.

seth · 2025-10-30 17:55:40

Oct 30 02:38:02 granite iwd[493]: Unexpected connection related event -- is another supplicant running?
Oct 30 02:38:02 granite wpa_supplicant[614]: wlan0: Associated with a4:22:49:ed:df:54

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

citrusyummer · 2025-10-30 20:07:38

seth wrote:

Oct 30 02:38:02 granite iwd[493]: Unexpected connection related event -- is another supplicant running?
Oct 30 02:38:02 granite wpa_supplicant[614]: wlan0: Associated with a4:22:49:ed:df:54

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
containerd.service                       | multi-user.target.wants
cpupower.service                         | multi-user.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.ratbag1.service     | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
fstrim.timer                             | timers.target.wants
getty@tty1.service                       | getty.target.wants
iwd.service                              | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
nvidia-hibernate.service                 | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-suspend.service.wants
nvidia-resume.service                    | systemd-suspend-then-hibernate.service.wants
nvidia-suspend.service                   | systemd-suspend.service.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-resolved-monitor.socket          | sockets.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-resolved-varlink.socket          | sockets.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs.service                    | graphical-session-pre.target.wants

seth · 2025-10-30 20:11:21

Disable iwd, if you want to use it as NM backend, see https://wiki.archlinux.org/title/Networ … Fi_backend
Also (unrelated) replace pulseaudio w/ pipewire-pulse

If the connection problems remain, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Otherwise please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

citrusyummer · 2025-10-30 20:35:56

seth wrote:

Disable iwd, if you want to use it as NM backend, see https://wiki.archlinux.org/title/Networ … Fi_backend
Also (unrelated) replace pulseaudio w/ pipewire-pulse
If the connection problems remain, please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Otherwise please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

setting iwd as the backend seems to work so far, will update and edit subject if it keeps working.
while i'm here, may i ask why you recommend that i replace pulseaudio with pipewire-pulse?

seth · 2025-10-30 20:38:26

Because otherwise you're running two sound daemons - which is also not good.

citrusyummer · 2025-10-31 16:22:54

seems to be working. i'll mark this as resolved. for other people with this problem try disabling iwd.service and configuring NetworkManager to use iwd as a backend

Arch Linux

#1 2025-10-30 02:51:45

[RESOLVED] WiFi adapter randomly decides to not connect to networks

#2 2025-10-30 17:09:27

Re: [RESOLVED] WiFi adapter randomly decides to not connect to networks

#3 2025-10-30 17:55:40

Re: [RESOLVED] WiFi adapter randomly decides to not connect to networks

#4 2025-10-30 20:07:38

Re: [RESOLVED] WiFi adapter randomly decides to not connect to networks

#5 2025-10-30 20:11:21

Re: [RESOLVED] WiFi adapter randomly decides to not connect to networks

#6 2025-10-30 20:35:56

Re: [RESOLVED] WiFi adapter randomly decides to not connect to networks

#7 2025-10-30 20:38:26

Re: [RESOLVED] WiFi adapter randomly decides to not connect to networks

#8 2025-10-31 16:22:54

Re: [RESOLVED] WiFi adapter randomly decides to not connect to networks

Board footer