[SOLVED] Wifi turns off after some time

nacho_varga77 · 2025-01-31 13:02:48

I installed Arch 2 days ago and faced a problem, wifi disconnects after some time. Sometimes it can happen right after turning on the laptop, sometimes it may not disconnect at all. Before arch I used windows 10, so network adapter works fine.
I am using Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)

nmcli --version

nmcli tool, version 1.50.2-1

ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether 28:3a:4d:5c:10:2f brd ff:ff:ff:ff:ff:ff

sudo ip link set wlan0 up

RTNETLINK answers: Input/output error

dmesg | grep ath10k

   15.419556] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x0003a028: -110
[   15.830472] ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00000039 at 0x0003543c: -110

rfkill

 ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked

sudo pacman -Q | grep "linux"

archlinux-keyring 20250123-1
linux 6.12.10.arch1-1
linux-api-headers 6.10-1
linux-firmware 20250109.7673dffd-1
linux-firmware-whence 20250109.7673dffd-1
linux-headers 6.12.10.arch1-1
util-linux 2.40.4-1
util-linux-libs 2.40.4-1

I found a solution, but it didn't help.
sudo modprobe -r ath10k_pci
sudo modprobe ath10k_pci

Last edited by nacho_varga77 (2025-02-02 09:12:12)

V1del · 2025-01-31 16:16:29

What do you get from

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

nacho_varga77 · 2025-01-31 17:45:09

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

dbus-fi.w1.wpa_supplicant1.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wpa_supplicant.service                   | multi-user.target.wants

Head_on_a_Stick · 2025-01-31 17:47:25

Disable wpa_supplicant.service, NM will call that itself and the two instances might conflict or race each other.

nacho_varga77 · 2025-01-31 17:59:47

Head_on_a_Stick wrote:

Disable wpa_supplicant.service, NM will call that itself and the two instances might conflict or race each other.

I did this

sudo systemctl disable wpa_supplicant.service

Hope this will help. I'll wait a couple of days, if the internet is stable, I'll change the title solved

● wpa_supplicant.service - WPA supplicant
     Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; preset: disabled)
     Active: active (running) since Fri 2025-01-31 21:42:51 +04; 11min ago
 Invocation: 3eb969a333064d8289d0b3c6bc3ccd7a
   Main PID: 361 (wpa_supplicant)
      Tasks: 1 (limit: 9231)
     Memory: 8M (peak: 8.4M)
        CPU: 80ms
     CGroup: /system.slice/wpa_supplicant.service
             └─361 /usr/bin/wpa_supplicant -u -s -O /run/wpa_supplicant

Don't I need to stop also wpa_supplicant.service?

Head_on_a_Stick · 2025-01-31 18:02:33

Yes, I think that's best.

Perhaps also restart NM. Or just reboot to be sure of a completely clean slate.

nacho_varga77 · 2025-01-31 18:21:39

Unfortunately it didn't help.

dmesg

[   45.946265] warning: `wrapper-2.0' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[  280.423343] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x0003a028: -110
[  280.465558] ath10k_pci 0000:01:00.0: failed to wake target for read32 at 0x0003a028: -110
[  280.560750] ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000172b at 0x0003543c: -110
[  280.604396] ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000172d at 0x0003543c: -110
[  280.856556] ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000172f at 0x0003543c: -110
[  281.157994] ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001731 at 0x0003543c: -110
[  281.496847] ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001733 at 0x0003543c: -110
[  281.539700] ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001735 at 0x0003543c: -110
[  281.608019] ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001737 at 0x0003543c: -110
[  281.848210] ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001739 at 0x0003543c: -110

Networkmanager still working , but shows this

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: disabled)
     Active: active (running) since Fri 2025-01-31 22:07:07 +04; 13min ago
 Invocation: 23abb396748a491b9a5c8be29e7de866
       Docs: man:NetworkManager(8)
   Main PID: 348 (NetworkManager)
      Tasks: 4 (limit: 9231)
     Memory: 25.4M (peak: 26.1M)
        CPU: 10.365s
     CGroup: /system.slice/NetworkManager.service
             └─348 /usr/bin/NetworkManager --no-daemon

Jan 31 22:19:42 archlinux NetworkManager[348]: <info>  [1738347582.6568] device (wlan0): set-hw-addr: set MAC address to F2:B7:52:68:1E:E8 (scanning)
Jan 31 22:19:46 archlinux NetworkManager[348]: <warn>  [1738347586.4819] platform-linux: do-change-link[2]: failure 5 (Input/output error)
Jan 31 22:19:46 archlinux NetworkManager[348]: <info>  [1738347586.4833] device (p2p-dev-wlan0): state change: disconnected -> unavailable (reason 'supplicant-failed', managed-type: 'full')
Jan 31 22:19:51 archlinux NetworkManager[348]: <error> [1738347591.6795] device (wlan0): Couldn't initialize supplicant interface: Timeout was reached
Jan 31 22:20:01 archlinux NetworkManager[348]: <warn>  [1738347601.5641] device (wlan0): re-acquiring supplicant interface (#1).
Jan 31 22:20:06 archlinux NetworkManager[348]: <error> [1738347606.6846] device (wlan0): Couldn't initialize supplicant interface: Timeout was reached
Jan 31 22:20:16 archlinux NetworkManager[348]: <warn>  [1738347616.5632] device (wlan0): re-acquiring supplicant interface (#2).
Jan 31 22:20:21 archlinux NetworkManager[348]: <error> [1738347621.6831] device (wlan0): Couldn't initialize supplicant interface: Timeout was reached
Jan 31 22:20:31 archlinux NetworkManager[348]: <warn>  [1738347631.5699] device (wlan0): re-acquiring supplicant interface (#3).
Jan 31 22:20:36 archlinux NetworkManager[348]: <error> [1738347636.5754] device (wlan0): Couldn't initialize supplicant interface: Timeout was reached

Head_on_a_Stick · 2025-01-31 18:52:32

Try setting the cryptmode parameter on the ath10k_core driver to "1".

https://wiki.archlinux.org/title/Kernel … le_options

nacho_varga77 · 2025-01-31 19:16:03

Head_on_a_Stick wrote:

Try setting the cryptmode parameter on the ath10k_core driver to "1".

Here is how my /etc/modprobe.d/ath10k_core.conf file looks like

options ath10k_core skip_otp=y
options ath10k_core cryptmode=1

dmesg

[   23.425175] ath10k_pci 0000:01:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 1028:1810
[   23.425186] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
[   23.425774] ath10k_pci 0000:01:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
[   23.496262] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 8aedfa4a
[   23.496275] ath10k_pci 0000:01:00.0: cryptmode > 0 requires raw mode support from firmware
[   23.496278] ath10k_pci 0000:01:00.0: fatal problem with firmware features: -22
[   23.496302] ath10k_pci 0000:01:00.0: could not probe fw (-22)

Head_on_a_Stick · 2025-01-31 19:27:43

That sounds familiar...

Does the global power management option help at all:

# iw dev wlan0 set power_save off

I've linked to a udev rule that can be modified to endisable that on boot, see the other thread for details.

Last edited by Head_on_a_Stick (2025-01-31 19:29:35)

nacho_varga77 · 2025-02-02 09:14:01

This helped me, thank you very much.

The solution is

 iw dev wlan0 set power_save off

Head_on_a_Stick · 2025-02-02 10:32:39

Fantastic, glad I could help.

Remember to create a udev rule to make the change permanent, it will be lost on reboot otherwise.

Arch Linux

#1 2025-01-31 13:02:48

[SOLVED] Wifi turns off after some time

#2 2025-01-31 16:16:29

Re: [SOLVED] Wifi turns off after some time

#3 2025-01-31 17:45:09

Re: [SOLVED] Wifi turns off after some time

#4 2025-01-31 17:47:25

Re: [SOLVED] Wifi turns off after some time

#5 2025-01-31 17:59:47

Re: [SOLVED] Wifi turns off after some time

#6 2025-01-31 18:02:33

Re: [SOLVED] Wifi turns off after some time

#7 2025-01-31 18:21:39

Re: [SOLVED] Wifi turns off after some time

#8 2025-01-31 18:52:32

Re: [SOLVED] Wifi turns off after some time

#9 2025-01-31 19:16:03

Re: [SOLVED] Wifi turns off after some time

#10 2025-01-31 19:27:43

Re: [SOLVED] Wifi turns off after some time

#11 2025-02-02 09:14:01

Re: [SOLVED] Wifi turns off after some time

#12 2025-02-02 10:32:39

Re: [SOLVED] Wifi turns off after some time

Board footer