Wifi stops working after laptop wakes after unlocking

Ask Fedora
, , , , ,
1

Quite often after coming back to my computer after leaving it for a while and unlocking it the networks widget will say “connected to a network of limited connectivity” or similar and quickly disappears and the wifi works again. Also, often the clock will display the time it locked. As the network works again I wasn’t too concerned.

Today however the network widget said there weren’t any networks available and I needed to reboot, so I would like to get the issue resolved.

ian@192:~$ kinfo
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.4-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i9-12900H
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® Graphics

Not really sure what is relevant but I ran journalctl --since=today and some logs around the time are:

Aug 19 18:28:00 192.168.1.126 wpa_supplicant[1514]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-65 noise=9999 txrate=288200
Aug 19 18:28:17 192.168.1.126 wpa_supplicant[1514]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise=9999 txrate=432300
Aug 19 18:28:55 192.168.1.126 wpa_supplicant[1514]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-66 noise=9999 txrate=432300
Aug 19 18:29:07 192.168.1.126 systemd-resolved[1258]: Grace period over, resuming full feature set (UDP+EDNS0) for DNS server fe80::1%3.
Aug 19 18:29:07 192.168.1.126 systemd-resolved[1258]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server fe80::1%3.
Aug 19 18:29:13 192.168.1.126 wpa_supplicant[1514]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=9999 txrate=432300
Aug 19 18:59:38 192.168.1.126 cupsd[1521]: REQUEST localhost - - "POST / HTTP/1.1" 200 182 Renew-Subscription successful-ok
Aug 19 19:00:15 192.168.1.126 systemd-logind[1307]: The system will suspend now!
Aug 19 19:00:15 192.168.1.126 ModemManager[1408]: <msg> [sleep-monitor-systemd] system is about to suspend
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.3826] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.3834] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.3841] manager: NetworkManager state is now ASLEEP
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.3843] device (wlp0s20f3): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Aug 19 19:00:15 192.168.1.126 kded6[2496]: org.kde.plasma.nm.kded: Unhandled active connection state change:  3
Aug 19 19:00:15 192.168.1.126 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Aug 19 19:00:15 192.168.1.126 systemd[1]: Started dbus-:1.3-org.kde.powerdevil.backlighthelper@9.service.
Aug 19 19:00:15 192.168.1.126 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.3-org.kde.powerdevil.backlighthelper@9 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 19 19:00:15 192.168.1.126 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Aug 19 19:00:15 192.168.1.126 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 19 19:00:15 192.168.1.126 kernel: wlp0s20f3: deauthenticating from 94:28:6f:37:a0:f0 by local choice (Reason: 3=DEAUTH_LEAVING)
Aug 19 19:00:15 192.168.1.126 wpa_supplicant[1514]: nl80211: send_event_marker failed: Source based routing not supported
Aug 19 19:00:15 192.168.1.126 wpa_supplicant[1514]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=94:28:6f:37:a0:f0 reason=3 locally_generated=1
Aug 19 19:00:15 192.168.1.126 wpa_supplicant[1514]: wlp0s20f3: CTRL-EVENT-DSCP-POLICY clear_all
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.4983] device (wlp0s20f3): supplicant interface state: completed -> disconnected
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.4987] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.4994] dhcp4 (wlp0s20f3): canceled DHCP transaction
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.4994] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Withdrawing address record for fd00::dfc1:36c7:9bcf:afb6 on wlp0s20f3.
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.4994] dhcp4 (wlp0s20f3): state changed no lease
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Withdrawing address record for 2a01:4b00:c018:d600:3d25:93d5:1e51:b5ba on wlp0s20f3.
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.4998] dhcp6 (wlp0s20f3): canceled DHCP transaction
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Leaving mDNS multicast group on interface wlp0s20f3.IPv6 with address 2a01:4b00:c018:d600:3d25:93d5:1e51:b5ba.
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.4999] dhcp6 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Joining mDNS multicast group on interface wlp0s20f3.IPv6 with address fe80::652d:d51c:10f7:885f.
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.4999] dhcp6 (wlp0s20f3): state changed no lease
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Registering new address record for fe80::652d:d51c:10f7:885f on wlp0s20f3.*.
Aug 19 19:00:15 192.168.1.126 wpa_supplicant[1514]: wlp0s20f3: PMKSA-CACHE-REMOVED 94:28:6f:37:a0:f0 0
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Withdrawing address record for fe80::652d:d51c:10f7:885f on wlp0s20f3.
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Leaving mDNS multicast group on interface wlp0s20f3.IPv6 with address fe80::652d:d51c:10f7:885f.
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Interface wlp0s20f3.IPv6 no longer relevant for mDNS.
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Interface wlp0s20f3.IPv4 no longer relevant for mDNS.
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Leaving mDNS multicast group on interface wlp0s20f3.IPv4 with address 192.168.1.126.
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Withdrawing address record for 192.168.1.126 on wlp0s20f3.
Aug 19 19:00:15 192.168.1.126 NetworkManager[1436]: <info>  [1724090415.5121] device (wlp0s20f3): set-hw-addr: set MAC address to 5A:49:FE:B6:2C:C7 (scanning)
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Joining mDNS multicast group on interface wlp0s20f3.IPv4 with address 192.168.1.126.
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: New relevant interface wlp0s20f3.IPv4 for mDNS.
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Registering new address record for 192.168.1.126 on wlp0s20f3.IPv4.
Aug 19 19:00:15 192.168.1.126 avahi-daemon[1293]: Withdrawing address record for 192.168.1.126 on wlp0s20f3.
......
Aug 19 19:01:30 fedora kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:480:472
Aug 19 19:01:35 fedora kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:480:472
Aug 19 19:01:40 fedora kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:480:472
Aug 19 19:01:45 fedora kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:480:472
Aug 19 19:01:50 fedora kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:480:472
Aug 19 19:01:55 fedora kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:480:472
Aug 19 19:02:00 fedora kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:480:472
Aug 19 19:02:05 fedora kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:480:472
Aug 19 19:02:10 fedora kernel: nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:480:472
......
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1:   device [10de:228b] error status/mask=00100000/00000000
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1:    [20] UnsupReq               (First)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: AER:   TLP Header: 40000001 0000000f aa000118 f7f7f7f7
Aug 19 19:46:00 fedora kernel: nvidia 0000:01:00.0: AER: can't recover (no error_detected callback)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: AER: can't recover (no error_detected callback)
Aug 19 19:46:00 fedora kernel: pcieport 0000:00:01.0: AER: device recovery failed
Aug 19 19:46:00 fedora kernel: pcieport 0000:00:01.0: AER: Multiple Uncorrectable (Non-Fatal) error message received from 0000:01:00.1
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1:   device [10de:228b] error status/mask=00100000/00000000
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1:    [20] UnsupReq               (First)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: AER:   TLP Header: 40000001 0000000f aa000118 f7f7f7f7
Aug 19 19:46:00 fedora kernel: nvidia 0000:01:00.0: AER: can't recover (no error_detected callback)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: AER: can't recover (no error_detected callback)
Aug 19 19:46:00 fedora kernel: pcieport 0000:00:01.0: AER: device recovery failed
Aug 19 19:46:00 fedora kernel: pcieport 0000:00:01.0: AER: Multiple Uncorrectable (Non-Fatal) error message received from 0000:01:00.1
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1:   device [10de:228b] error status/mask=00100000/00000000
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1:    [20] UnsupReq               (First)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: AER:   TLP Header: 40000001 0000000f aa000118 f7f7f7f7
Aug 19 19:46:00 fedora kernel: nvidia 0000:01:00.0: AER: can't recover (no error_detected callback)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: AER: can't recover (no error_detected callback)
Aug 19 19:46:00 fedora kernel: pcieport 0000:00:01.0: AER: device recovery failed
Aug 19 19:46:00 fedora kernel: pcieport 0000:00:01.0: AER: Multiple Uncorrectable (Non-Fatal) error message received from 0000:01:00.1
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1:   device [10de:228b] error status/mask=00100000/00000000
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1:    [20] UnsupReq               (First)
Aug 19 19:46:00 fedora kernel: snd_hda_intel 0000:01:00.1: AER:   TLP Header: 40000001 0000000f aa000118 f7f7f7f7
1 Like
2

Added wifi and removed kde, server

3

This often appears are unlocking, but generally it does connect to the internet.

image

4

Can you send results for inxi -N.

Also, do you face this issue on battery power specifically? or even after waking laptop while it’s plugged in gives you this error?

In the meantime, please also see Cause #6 and Cause #7 here - https://wiki.archlinux.org/title/Network_configuration/Wireless#Cause_#6

There may be driver specific issues depending on your Network Card. I can help you once you give this inxi response.

1 Like
5

Thanks @hashmartin and sorry not to reply earlier.

ian@192:~$ inxi -N
Network:
  Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB

I didn’t have inxi so used this to install on Kinoite:

rpm-ostree install inxi

I am using wifi and the laptop is always plugged into a dock I use two external screens.

I have a feeling there is power saving thing gone wrong as sometimes one of the two external screens will turn off with “no signal from…” displayed, and after moving the mouse it comes back on after a few seconds.

6

I was facing similar issue, but with WiFi dropping on battery power. Please check this comment -

Basically you have to create /etc/NetworkManager/conf.d/00-wifi-powersave.conf file and have this inside it

[connection]
wifi.powersave=2

I made this change this morning and have found that my WiFi does not disconnect anymore. I’m not sure if you’re allowed to edit files in /etc directory on Kinoite. But this should most probably fix your problem as well.

Since you’re using iwlwifi driver for your Intel WiFi chipset, check logs once if there is any error message.

$ dmesg | grep iwlwifi

Check sections 6.6.6, 6.6.7, and 7.4.2 in this article - https://wiki.archlinux.org/title/Network_configuration/Wireless, and section 3.7.1 here https://wiki.archlinux.org/title/Power_management#Network_interfaces

I think most probably creating/editing /etc/modprobe.d/iwlwifi.conf should work

options iwlwifi power_save=0 # disables power management

These may solve your problem at the network driver level if the previous method didn’t work.

In my case, I made configuration changes in both places because the Realtek drivers really suck.

2 Likes
7

I seem to have solved the issue by disabling sleep while on AC power. The laptop is always plugged into a dock to drive to extra screens anyway, it seems a simpler solution to me.

1 Like