Wifi Card fails to keep connection alive and functional

General system Newbie
1

I have issues connecting to our home wifi with my new wifi card. I’m using the “Gigabyte GC-WIFI7” in EndeavourOS. My network uses WPA2/WPA3. Whenever i connect it loads for a few seconds and then immediately drops the connection and it will loop like that forever throwing the messages below. How can i solve this issue?

System Info:

OS: EndeavourOS x86_64
Host: Z390 AORUS ELITE
Kernel: Linux 6.11.2-arch1-1
Shell: bash 5.2.37
Display (24G2W1G4): 1920x1080 @ 144 Hz in 24" [External] *
DE: KDE Plasma 6.1.5
WM: KWin (Wayland)
CPU: Intel(R) Core™ i9-9900K (16) @ 5.00 GHz
GPU: AMD Radeon RX 7900 XT [Discrete]
Memory: 4.21 GiB / 31.28 GiB 4x8GB
Wifi Card: Gigabyte GC-WIFI7 rev.1

lspci -k output:
05:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] (rev 01)
Subsystem: Foxconn International, Inc. Device e0fb
Kernel driver in use: ath12k_pci

dmesg | grep ath12k output:
[ 22.989894] ath12k_pci 0000:05:00.0: BAR 0 [mem 0x50200000-0x503fffff 64bit]: assigned
[ 22.989915] ath12k_pci 0000:05:00.0: enabling device (0000 → 0002)
[ 22.990004] ath12k_pci 0000:05:00.0: MSI vectors: 1
[ 22.990009] ath12k_pci 0000:05:00.0: Hardware name: wcn7850 hw2.0
[ 25.429441] ath12k_pci 0000:05:00.0: qmi dma allocation failed (7077888 B type 1), will try later with small size
[ 25.437366] ath12k_pci 0000:05:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200
[ 25.437369] ath12k_pci 0000:05:00.0: fw_version 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
[ 25.602723] ath12k_pci 0000:05:00.0: leaving PCI ASPM disabled to avoid MHI M2 problems
[ 45.355771] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 12 (-105)
[ 45.355793] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 14 (-105)
[ 45.355801] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 14 (-105)
[ 45.355809] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 45.355815] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 45.355822] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 45.355827] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 15 (-105)
[ 45.355839] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 16 (-105)
[ 54.675041] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 13 (-105)
[ 54.675072] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 59.682639] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 10 (-105)
[ 59.682648] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 11 (-105)
[ 59.682651] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 11 (-105)
[ 59.682658] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 12 (-105)
[ 59.682661] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 12 (-105)
[ 59.682664] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 13 (-105)
[ 59.682665] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 13 (-105)
[ 59.682667] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 13 (-105)
[ 59.682670] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 13 (-105)
[ 59.682672] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 13 (-105)
[ 59.682673] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 13 (-105)
[ 59.682678] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 14 (-105)
[ 59.682680] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 14 (-105)
[ 59.682682] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 14 (-105)
[ 353.148470] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 11 (-105)
[ 353.148500] ath12k_warn: 12 callbacks suppressed
[ 353.148506] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 14 (-105)
[ 353.148516] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 14 (-105)
[ 353.148525] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 353.148530] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 353.148534] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 353.148539] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 353.148544] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 353.148549] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 353.148553] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 15 (-105)
[ 353.148557] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 15 (-105)
[ 353.148567] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 16 (-105)
[ 354.655268] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 12 (-105)
[ 354.655295] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 14 (-105)
[ 354.655313] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE cmd, tid 15 (-105)

journalctl -b | grep wlan0 output:
Oct 08 14:18:24 fluffyarch kernel: wlan0: authenticate with a0:b5:49:9d:24:10 (local address=4c:82:a9:93:51:63)
Oct 08 14:18:24 fluffyarch kernel: wlan0: send auth to a0:b5:49:9d:24:10 (try 1/3)
Oct 08 14:18:24 fluffyarch kernel: wlan0: authenticate with a0:b5:49:9d:24:10 (local address=4c:82:a9:93:51:63)
Oct 08 14:18:24 fluffyarch kernel: wlan0: send auth to a0:b5:49:9d:24:10 (try 1/3)
Oct 08 14:18:24 fluffyarch kernel: wlan0: authenticated
Oct 08 14:18:24 fluffyarch kernel: wlan0: associate with a0:b5:49:9d:24:10 (try 1/3)
Oct 08 14:18:24 fluffyarch kernel: wlan0: RX AssocResp from a0:b5:49:9d:24:10 (capab=0x1011 status=0 aid=22)
Oct 08 14:18:24 fluffyarch kernel: wlan0: associated
Oct 08 14:18:24 fluffyarch kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by a0:b5:49:9d:24:10
Oct 08 14:18:24 fluffyarch NetworkManager[1611]: [1728389904.3799] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to ‘1zoi8sit7’.
Oct 08 14:18:24 fluffyarch NetworkManager[1611]: [1728389904.3802] device (wlan0): state change: config → ip-config (reason ‘none’, sys-iface-state: ‘managed’)
Oct 08 14:18:24 fluffyarch NetworkManager[1611]: [1728389904.4214] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Oct 08 14:18:24 fluffyarch NetworkManager[1611]: [1728389904.4222] device (wlan0): new IWD device state is connected
Oct 08 14:18:28 fluffyarch plasmashell[2134]: org.kde.plasma.nm.libs: Wireless scan on “wlan0” failed: “Scanning not allowed at this time”
Oct 08 14:18:33 fluffyarch kernel: wlan0: deauthenticating from a0:b5:49:9d:24:10 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.5074] device (wlan0): new IWD device state is disconnected
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.5077] device (wlan0): state change: ip-config → failed (reason ‘supplicant-disconnect’, sys-iface-state: ‘managed’)
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.5089] device (wlan0): Activation: failed for connection ‘1zoi8sit7’
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.5096] device (wlan0): state change: failed → disconnected (reason ‘none’, sys-iface-state: ‘managed’)
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.5761] dhcp4 (wlan0): canceled DHCP transaction
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.5762] dhcp4 (wlan0): state changed no lease
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.7422] device (wlan0): new IWD device state is connecting
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.7425] device (wlan0): Activation: starting connection ‘1zoi8sit7’ (34bfd21f-cfa1-4ee8-979f-dbf079673372)
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.7425] device (wlan0): state change: disconnected → prepare (reason ‘none’, sys-iface-state: ‘managed’)
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.7428] device (wlan0): state change: prepare → config (reason ‘none’, sys-iface-state: ‘managed’)
Oct 08 14:18:33 fluffyarch kernel: wlan0: authenticate with a0:b5:49:9d:24:10 (local address=4c:82:a9:93:51:63)
Oct 08 14:18:33 fluffyarch kernel: wlan0: send auth to a0:b5:49:9d:24:10 (try 1/3)
Oct 08 14:18:33 fluffyarch kernel: wlan0: authenticate with a0:b5:49:9d:24:10 (local address=4c:82:a9:93:51:63)
Oct 08 14:18:33 fluffyarch kernel: wlan0: send auth to a0:b5:49:9d:24:10 (try 1/3)
Oct 08 14:18:33 fluffyarch kernel: wlan0: authenticated
Oct 08 14:18:33 fluffyarch kernel: wlan0: associate with a0:b5:49:9d:24:10 (try 1/3)
Oct 08 14:18:33 fluffyarch kernel: wlan0: RX AssocResp from a0:b5:49:9d:24:10 (capab=0x1011 status=0 aid=27)
Oct 08 14:18:33 fluffyarch kernel: wlan0: associated
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.9011] device (wlan0): new IWD device state is connected
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.9015] device (wlan0): state change: config → ip-config (reason ‘none’, sys-iface-state: ‘managed’)
Oct 08 14:18:33 fluffyarch NetworkManager[1611]: [1728389913.9026] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Oct 08 14:18:33 fluffyarch kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by a0:b5:49:9d:24:10
Oct 08 14:18:34 fluffyarch NetworkManager[1611]: [1728389914.6724] device (wlan0): state change: ip-config → deactivating (reason ‘user-requested’, sys-iface-state: ‘managed’)
Oct 08 14:18:34 fluffyarch NetworkManager[1611]: [1728389914.6994] dhcp4 (wlan0): canceled DHCP transaction
Oct 08 14:18:34 fluffyarch NetworkManager[1611]: [1728389914.6995] dhcp4 (wlan0): state changed no lease
Oct 08 14:18:34 fluffyarch NetworkManager[1611]: [1728389914.7020] audit: op=“device-disconnect” interface=“wlan0” ifindex=4 pid=2134 uid=1000 result=“success”
Oct 08 14:18:34 fluffyarch kernel: wlan0: deauthenticating from a0:b5:49:9d:24:10 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 08 14:18:35 fluffyarch NetworkManager[1611]: [1728389915.0002] device (wlan0): new IWD device state is disconnecting
Oct 08 14:18:35 fluffyarch NetworkManager[1611]: [1728389915.0006] device (wlan0): new IWD device state is disconnected
Oct 08 14:18:35 fluffyarch NetworkManager[1611]: [1728389915.0008] device (wlan0): state change: deactivating → disconnected (reason ‘user-requested’, sys-iface-state: ‘managed’)

2

Seems to be something to do with this

leaving PCI ASPM disabled to avoid MHI M2 problems
[ 45.355771] ath12k_pci 0000:05:00.0: failed to send HAL_REO_CMD_FLUSH_CACHE, tid 12 (-105)

(take my advise with grain of salt but may be setting is bios/uefi causing it)

3

Alright thank you i will take a look into the bios then. Anything in particular that might come to mind that could cause this?

4

As I said take my advice here with a grain of salt (don’t look at it too much it is just a basic reference, someone smart should be able to answer more soon hopefully and help you)
But if you have a basic understanding it would hurt to have a look and check for some regular offenders (pretty wasted but the wiki I think references some of this and if not the eos wiki the arch one, at the least you can learn something while waiting for help at worst it is a wall of text (it gets easier to understand with time))

5

:thinking:

6

This thinking face makes it look like that part is self explanatory but i can’t see what it would mean. After i press connect i can take my hands away from my keyboard and mouse and it will do that and keep disconnecting & reconnecting. In no way should any of my actions do a “user requested” deactivation/disconnecting action.

7

I tried some bios changes and disabled the power management thingy called “ASPM” and it didn’t change anything from what it seems.

current output of journalctl -b | grep wlan1:

Oct 08 23:29:37 fluffyarch kernel: wlan1: authenticate with a0:b5:49:9d:24:10 (local address=4c:82:a9:93:51:63)
Oct 08 23:29:37 fluffyarch kernel: wlan1: send auth to a0:b5:49:9d:24:10 (try 1/3)
Oct 08 23:29:37 fluffyarch kernel: wlan1: authenticate with a0:b5:49:9d:24:10 (local address=4c:82:a9:93:51:63)
Oct 08 23:29:37 fluffyarch kernel: wlan1: send auth to a0:b5:49:9d:24:10 (try 1/3)
Oct 08 23:29:37 fluffyarch kernel: wlan1: authenticated
Oct 08 23:29:37 fluffyarch kernel: wlan1: associate with a0:b5:49:9d:24:10 (try 1/3)
Oct 08 23:29:37 fluffyarch kernel: wlan1: RX AssocResp from a0:b5:49:9d:24:10 (capab=0x1011 status=0 aid=24)
Oct 08 23:29:37 fluffyarch kernel: wlan1: associated
Oct 08 23:29:37 fluffyarch kernel: wlan1: Limiting TX power to 30 (30 - 0) dBm as advertised by a0:b5:49:9d:24:10
Oct 08 23:29:37 fluffyarch NetworkManager[1528]: [1728422977.8834] device (wlan1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to ‘1zoi8sit7’.
Oct 08 23:29:37 fluffyarch NetworkManager[1528]: [1728422977.8837] device (wlan1): state change: config → ip-config (reason ‘none’, sys-iface-state: ‘managed’)
Oct 08 23:29:37 fluffyarch NetworkManager[1528]: [1728422977.8847] dhcp4 (wlan1): activation: beginning transaction (timeout in 45 seconds)
Oct 08 23:29:37 fluffyarch NetworkManager[1528]: [1728422977.8854] device (wlan1): new IWD device state is connected
Oct 08 23:29:39 fluffyarch NetworkManager[1528]: [1728422979.0350] device (wlan1): state change: ip-config → deactivating (reason ‘user-requested’, sys-iface-state: ‘managed’)
Oct 08 23:29:39 fluffyarch NetworkManager[1528]: [1728422979.0701] dhcp4 (wlan1): canceled DHCP transaction
Oct 08 23:29:39 fluffyarch NetworkManager[1528]: [1728422979.0702] dhcp4 (wlan1): state changed no lease
Oct 08 23:29:39 fluffyarch NetworkManager[1528]: [1728422979.0724] audit: op=“device-disconnect” interface=“wlan1” ifindex=5 pid=2070 uid=1000 result=“success”
Oct 08 23:29:39 fluffyarch kernel: wlan1: deauthenticating from a0:b5:49:9d:24:10 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 08 23:29:39 fluffyarch NetworkManager[1528]: [1728422979.3541] device (wlan1): new IWD device state is disconnecting
Oct 08 23:29:39 fluffyarch NetworkManager[1528]: [1728422979.3545] device (wlan1): new IWD device state is disconnected
Oct 08 23:29:39 fluffyarch NetworkManager[1528]: [1728422979.3547] device (wlan1): state change: deactivating → disconnected (reason ‘user-requested’, sys-iface-state: ‘managed’)

8

No I’m just thinking seeing it. :person_shrugging:

9

Oh alright, quite a few times when i had issues i had the experience of people telling me to read and figure it out or to just go back to windows if i can’t understand it so i am still expecting that all the time. If something comes to mind that could solve this issue please let me know.

10

As far as i know there was a patch for ath12k that should have been implemented by now. I have read some info where a user switched to wpa_supplicant and got it to connect but i see yours is connecting just not staying connected. Others have tried newer firmware also and had no success. I wish i could be more helpful. You could try also iwd to connect.

https://wiki.archlinux.org/title/Iwd

11

i tried to use wpa_supplicant but i couldn’t get it running. it always failed to connect and properly start or something like that and i didn’t know if it requires systemd-networkd or something like that as i’ve read it conflicts with networkmanager. i think i also looked into iwd but im not sure what the issue was there.

12

I have also read through the following. Not sure if it would be any help for you but maybe? This is back from 2023 when the ath12k wasn’t yet supported.

https://wireless.wiki.kernel.org/en/users/drivers/ath12k/installation

Edit: Also this link

https://bbs.archlinux.org/viewtopic.php?id=291283

13

@gytuzgcgejigxzfxne
Have been looking at this also but have no idea if the firmware makes it work.

14

as far as im aware firmware is already included since it loads something as visible in dmesg. I have decided to just return it since nothing i have read online or tried fixed it.

15

Probably a good move since everything I’ve read shows it not working on amd for whatever reason.

16

I have read that too but i have intel not amd regarding CPU and Motherboard. So that should not be the issue.

17

Well then it should work. The network should use WPA3 since this is WiFi 7.

18

The Network runs on WPA2/WPA3 so both can connect.

1 Like