NetworkManager Failing to Connect to WiFi after System Update

rojo · 2023-02-03 15:49:55

I recently purchased a new WiFi 6 router & also updated my Linux devices. I dual-boot Windows 11 & Arch Linux on a Desktop and Laptop with roughly the same configuration. After upgrading to the WiFi 6 router, my wireless has stopped working on both devices. Ethernet works perfectly on the desktop, however. The router is not the issue since the Windows 11 side runs fine on wireless. I have booted arch off a USB on each device and iwctl is able to connect to wireless with no issues.

My router is set to run WPA2/WPA3.

I am not running any other DHCP client or network configuration package. I am only using NetworkManager. I have checked many other threads with no fix. Any help is appreciated.

Here is my error log from Network Manager

Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.5711] policy: auto-activating connection 'Hubbard' (d267ce62-1660-4595-a5e4-f0ae73c59493)
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.5722] device (wlp4s0): Activation: starting connection 'Hubbard' (d267ce62-1660-4595-a5e4-f0ae73c59493)
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.5724] device (wlp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.5980] device (wlp4s0): set-hw-addr: reset MAC address to E8:D1:1B:5D:4C:74 (preserve)
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6042] device (wlp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6047] device (wlp4s0): Activation: (wifi) access point 'Hubbard' has security, but secrets are required.
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6048] device (wlp4s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6052] sup-iface[15af3c993ac31579,2,wlp4s0]: wps: type pbc start...
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6059] device (wlp4s0): supplicant interface state: inactive -> interface_disabled
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6060] device (p2p-dev-wlp4s0): supplicant management interface state: inactive -> interface_disabled
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6077] device (wlp4s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6086] device (wlp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6092] device (wlp4s0): Activation: (wifi) connection 'Hubbard' has security, and secrets exist.  No new secrets needed.
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6093] Config: added 'ssid' value 'Hubbard'
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6093] Config: added 'scan_ssid' value '1'
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6093] Config: added 'bgscan' value 'simple:30:-70:86400'
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6094] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6094] Config: added 'auth_alg' value 'OPEN'
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6095] Config: added 'psk' value '<hidden>'
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6375] device (wlp4s0): supplicant interface state: interface_disabled -> inactive
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6375] device (p2p-dev-wlp4s0): supplicant management interface state: interface_disabled -> inactive
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6779] device (wlp4s0): supplicant interface state: inactive -> authenticating
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.6780] device (p2p-dev-wlp4s0): supplicant management interface state: inactive -> authenticating
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.7249] device (wlp4s0): supplicant interface state: authenticating -> disconnected
Feb 03 10:02:45 pc NetworkManager[476]: <info>  [1675440165.7250] device (p2p-dev-wlp4s0): supplicant management interface state: authenticating -> disconnected
Feb 03 10:02:55 pc NetworkManager[476]: <info>  [1675440175.7299] device (wlp4s0): supplicant interface state: disconnected -> scanning
Feb 03 10:02:55 pc NetworkManager[476]: <info>  [1675440175.7300] device (p2p-dev-wlp4s0): supplicant management interface state: disconnected -> scanning
Feb 03 10:02:55 pc NetworkManager[476]: <info>  [1675440175.8458] device (wlp4s0): supplicant interface state: scanning -> authenticating
Feb 03 10:02:55 pc NetworkManager[476]: <info>  [1675440175.8458] device (p2p-dev-wlp4s0): supplicant management interface state: scanning -> authenticating
Feb 03 10:02:55 pc NetworkManager[476]: <info>  [1675440175.9213] device (wlp4s0): supplicant interface state: authenticating -> disconnected
Feb 03 10:02:55 pc NetworkManager[476]: <info>  [1675440175.9214] device (p2p-dev-wlp4s0): supplicant management interface state: authenticating -> disconnected
Feb 03 10:03:05 pc NetworkManager[476]: <info>  [1675440185.9279] device (wlp4s0): supplicant interface state: disconnected -> scanning
Feb 03 10:03:05 pc NetworkManager[476]: <info>  [1675440185.9280] device (p2p-dev-wlp4s0): supplicant management interface state: disconnected -> scanning
Feb 03 10:03:11 pc NetworkManager[476]: <warn>  [1675440191.1358] device (wlp4s0): Activation: (wifi) association took too long, failing activation
Feb 03 10:03:11 pc NetworkManager[476]: <info>  [1675440191.1359] device (wlp4s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Feb 03 10:03:11 pc NetworkManager[476]: <info>  [1675440191.1632] device (wlp4s0): set-hw-addr: set MAC address to 96:18:B7:61:06:65 (scanning)
Feb 03 10:03:11 pc NetworkManager[476]: <warn>  [1675440191.1660] device (wlp4s0): Activation: failed for connection 'Hubbard'
Feb 03 10:03:11 pc NetworkManager[476]: <info>  [1675440191.1661] device (wlp4s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 03 10:03:11 pc NetworkManager[476]: <info>  [1675440191.1909] device (wlp4s0): supplicant interface state: scanning -> disconnected
Feb 03 10:03:11 pc NetworkManager[476]: <info>  [1675440191.1910] device (p2p-dev-wlp4s0): supplicant management interface state: scanning -> disconnected
Feb 03 10:03:11 pc NetworkManager[476]: <info>  [1675440191.1962] device (wlp4s0): supplicant interface state: disconnected -> inactive

Here are my network interfaces

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 60:45:cb:74:eb:14 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.54/24 brd 192.168.0.255 scope global dynamic noprefixroute enp0s31f6
       valid_lft 6220sec preferred_lft 6220sec
3: wlp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether e8:d1:1b:5d:4c:74 brd ff:ff:ff:ff:ff:ff

Last edited by rojo (2023-02-03 19:35:49)

seth · 2023-02-03 17:19:18

I dual-boot Windows 11 & Arch

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I am not running any other DHCP client or network configuration package. I am only using NetworkManager.

We'll still have a brief look at

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

Here is my error log from Network Manager

Please post your complete system journal for the boot:

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

The problems will be w/ wpa_supplicant or iwd to provide the carrier.
Incidentally you may try https://wiki.archlinux.org/title/Networ … Fi_backend

rojo · 2023-02-03 17:43:30

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Done. It was on by default. Rebooted into Windows again and rebooted in Linux twice (for voodoo reasons).

We'll still have a brief look at

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

Here is my service log

bluetooth.service                        | bluetooth.target.wants
ckb-next-daemon.service                  | multi-user.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
xdg-user-dirs-update.service             | default.target.wants

Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/oCQA.txt

The problems will be w/ wpa_supplicant or iwd to provide the carrier.
Incidentally you may try https://wiki.archlinux.org/title/Networ … Fi_backend

My NM log using iwd as the backend

Feb 03 11:50:58 pc NetworkManager[3265]: <info>  [1675446658.0729] manager: NetworkManager state is now CONNECTING
Feb 03 11:50:58 pc NetworkManager[3265]: <info>  [1675446658.0738] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Feb 03 11:50:58 pc NetworkManager[3265]: <info>  [1675446658.0773] device (wlan0): state change: config -> need-auth (reason 'no-secrets', sys-iface-state: 'managed')
Feb 03 11:50:58 pc NetworkManager[3265]: <info>  [1675446658.9917] device (wlan0): state change: need-auth -> config (reason 'none', sys-iface-state: 'managed')
Feb 03 11:50:58 pc NetworkManager[3265]: <info>  [1675446658.9955] device (wlan0): new IWD device state is connecting
Feb 03 11:51:01 pc NetworkManager[3265]: <error> [1675446661.0438] device (wlan0): Activation: (wifi) Network.Connect failed: GDBus.Error:net.connman.iwd.Failed: Operation failed
Feb 03 11:51:01 pc NetworkManager[3265]: <info>  [1675446661.0442] device (wlan0): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Feb 03 11:51:01 pc NetworkManager[3265]: <info>  [1675446661.0448] manager: NetworkManager state is now DISCONNECTED
Feb 03 11:51:01 pc NetworkManager[3265]: <warn>  [1675446661.0454] device (wlan0): Activation: failed for connection 'Hubbard 1'
Feb 03 11:51:01 pc NetworkManager[3265]: <info>  [1675446661.0456] device (wlan0): new IWD device state is disconnected
Feb 03 11:51:01 pc NetworkManager[3265]: <info>  [1675446661.0462] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Feb 03 11:52:47 pc NetworkManager[3265]: <info>  [1675446767.0979] device (wlan0): Activation: starting connection 'Hubbard 1' (8089b761-8961-478b-a53c-3375641f457d)
Feb 03 11:52:47 pc NetworkManager[3265]: <info>  [1675446767.0980] audit: op="connection-activate" uuid="8089b761-8961-478b-a53c-3375641f457d" name="Hubbard 1" pid=1080 uid=1000 result="success"
Feb 03 11:52:47 pc NetworkManager[3265]: <info>  [1675446767.0980] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')

Thank you for your help Seth

Last edited by rojo (2023-02-03 17:55:24)

seth · 2023-02-03 17:59:57

No extra services, so that's great.
You might also want to reboot the router, as the authentication attempt simply times out (the router might hold some stale leases from the previously concurrent windows/linux runs and ignore you)

The NIC seems to be a QCA6174 802.11ac
Not checked, but just fyi wrt "also updated my Linux devices": the name doesn't suggest that it'll actually be AX capable.
(This would of course not prohibit authenticating w/ the AP, given the latter is configured to support AC as well and we can infer this as windows works)

Edit:

My NM log using iwd as the backend

Again: the interesting information will be around NM, not from NM itself.

Last edited by seth (2023-02-03 18:00:54)

rojo · 2023-02-03 18:17:16

seth wrote:

No extra services, so that's great.
You might also want to reboot the router, as the authentication attempt simply times out (the router might hold some stale leases from the previously concurrent windows/linux runs and ignore you)
The NIC seems to be a QCA6174 802.11ac
Not checked, but just fyi wrt "also updated my Linux devices": the name doesn't suggest that it'll actually be AX capable.
(This would of course not prohibit authenticating w/ the AP, given the latter is configured to support AC as well and we can infer this as windows works)
Edit:
My NM log using iwd as the backend
Again: the interesting information will be around NM, not from NM itself.

Rebooted modem, router, and my Linux desktop. No luck. I tried to connect to the network using WPS but my desktop doesn't even see that I'm pressing the WPS button.

I'm at a loss here. I'll keep trying to figure this out.

rojo · 2023-02-03 19:07:44

I tried many solutions with no luck. On my laptop, I reverted back to an image (1/29/23) before the system update and now the WiFi is working perfectly. No idea what has changed. Also, it appears I am running the dhcpcd service with NM with no issues.

bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dhcpcd.service                           | multi-user.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
NetworkManager.service                   | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants

After I reverted to the previous image, I updated my system again, and the WiFi is still working with no issues. Most likely, I will do the same for my desktop to fix the problem.

So the issue is still not solved, but at least mitigated for now. Please let me know if the mods would like me to mark this as solved. Thanks again Seth.

Last edited by rojo (2023-02-03 19:33:06)

seth · 2023-02-03 22:19:44

Did you reboot after the update?
Otherwise the issue is the kernel update.
Ideally post an updated journal to contrast it w/ the "bad" one.

Arch Linux

#1 2023-02-03 15:49:55

NetworkManager Failing to Connect to WiFi after System Update

#2 2023-02-03 17:19:18

Re: NetworkManager Failing to Connect to WiFi after System Update

#3 2023-02-03 17:43:30

Re: NetworkManager Failing to Connect to WiFi after System Update

#4 2023-02-03 17:59:57

Re: NetworkManager Failing to Connect to WiFi after System Update

#5 2023-02-03 18:17:16

Re: NetworkManager Failing to Connect to WiFi after System Update

#6 2023-02-03 19:07:44

Re: NetworkManager Failing to Connect to WiFi after System Update

#7 2023-02-03 22:19:44

Re: NetworkManager Failing to Connect to WiFi after System Update

Board footer