For AX210 on FW16 (not officially supported), using my script, captured two drops and the time stamps with video chatting for a full hour. Going to compare this with the dmesg/journal now.
For AX210, using the above script, captured two drops and the time stamps. Going to compare this with the dmesg/journal now. Below are the details of one of them.
Without my script, I’d missed this as I am multitasking and these drops were only 10 seconds.
This was during a video call. Using a fake SSID for these posts.
Here is the clipped area my script caught for iw_logfile, giving me a time stamp.
---------------------------
Thu May 16 01:54:45 PM PDT 2024:
Connected to d8:8e:d4:7d:2e:c8 (on wlp5s0)
SSID: MEH
freq: 6135.0
RX: 1338030973 bytes (974265 packets)
TX: 804649852 bytes (812745 packets)
signal: -51 dBm
rx bitrate: 1921.5 MBit/s 160MHz HE-MCS 9 HE-NSS 2 HE-GI 0 HE-DCM 0
tx bitrate: 1729.6 MBit/s 160MHz HE-MCS 8 HE-NSS 2 HE-GI 0 HE-DCM 0
bss flags: short-slot-time
dtim period: 2
beacon int: 100
---------------------------
Thu May 16 01:54:55 PM PDT 2024:
Not connected.
---------------------------
Thu May 16 01:55:05 PM PDT 2024:
Connected to e8:d3:eb:b8:d2:c7 (on wlp5s0)
SSID: MEH
freq: 5180.0
RX: 682332 bytes (894 packets)
TX: 550518 bytes (751 packets)
signal: -64 dBm
rx bitrate: 432.4 MBit/s 80MHz HE-MCS 8 HE-NSS 1 HE-GI 0 HE-DCM 0
tx bitrate: 576.4 MBit/s 80MHz HE-MCS 5 HE-NSS 2 HE-GI 0 HE-DCM 0
bss flags: short-slot-time
dtim period: 2
beacon int: 100
journalctl --since "2024-05-16 13:50:00" --until "2024-05-16 13:58:00"
And with this and a little journal action:
journalctl --since "2024-05-16 13:50:00" --until "2024-05-16 13:58:00"
May 16 13:54:48 fedora kernel: wlp5s0: Connection to AP d8:8e:d4:7d:2e:c8 lost
May 16 13:54:48 fedora wpa_supplicant[2341]: wlp5s0: CTRL-EVENT-DISCONNECTED bssid=d8:8e:d4:7d:2e:c8 reason=4 locally_generated=1
May 16 13:54:48 fedora wpa_supplicant[2341]: BSSID d8:8e:d4:7d:2e:c8 ignore list count incremented to 2, ignoring for 10 seconds
May 16 13:54:48 fedora NetworkManager[2272]: <info> [1715892888.9478] device (wlp5s0): supplicant interface state: completed ->>
May 16 13:54:48 fedora NetworkManager[2272]: <info> [1715892888.9479] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:49 fedora NetworkManager[2272]: <info> [1715892889.0391] device (wlp5s0): supplicant interface state: disconnected>
May 16 13:54:49 fedora NetworkManager[2272]: <info> [1715892889.0391] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:49 fedora wpa_supplicant[2341]: wlp5s0: SME: Trying to authenticate with d8:8e:d4:7d:2e:c7 (SSID='MEH' freq=5180>
May 16 13:54:49 fedora kernel: wlp5s0: authenticate with d8:8e:d4:7d:2e:c7 (local address=9a:25:6c:43:ef:61)
May 16 13:54:49 fedora kernel: wlp5s0: send auth to d8:8e:d4:7d:2e:c7 (try 1/3)
May 16 13:54:49 fedora NetworkManager[2272]: <info> [1715892889.2763] device (wlp5s0): supplicant interface state: scanning -> >
May 16 13:54:49 fedora NetworkManager[2272]: <info> [1715892889.2764] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:50 fedora kernel: iwlwifi 0000:05:00.0: Not associated and the session protection is over already...
May 16 13:54:50 fedora kernel: wlp5s0: Connection to AP d8:8e:d4:7d:2e:c7 lost
May 16 13:54:51 fedora kernel: wlp5s0: send auth to d8:8e:d4:7d:2e:c7 (try 2/3)
May 16 13:54:52 fedora kernel: iwlwifi 0000:05:00.0: Not associated and the session protection is over already...
May 16 13:54:52 fedora kernel: wlp5s0: Connection to AP d8:8e:d4:7d:2e:c7 lost
May 16 13:54:53 fedora kernel: wlp5s0: send auth to d8:8e:d4:7d:2e:c7 (try 3/3)
May 16 13:54:53 fedora geoclue[5751]: Failed to query location: Could not connect to location.services.mozilla.com: No route to >
May 16 13:54:54 fedora kernel: iwlwifi 0000:05:00.0: Not associated and the session protection is over already...
May 16 13:54:54 fedora kernel: wlp5s0: Connection to AP d8:8e:d4:7d:2e:c7 lost
May 16 13:54:54 fedora kernel: wlp5s0: aborting authentication with d8:8e:d4:7d:2e:c7 by local choice (Reason: 3=DEAUTH_LEAVING)
May 16 13:54:54 fedora wpa_supplicant[2341]: BSSID d8:8e:d4:7d:2e:c7 ignore list count incremented to 2, ignoring for 10 seconds
May 16 13:54:54 fedora NetworkManager[2272]: <info> [1715892894.3034] device (wlp5s0): supplicant interface state: authenticati>
May 16 13:54:54 fedora NetworkManager[2272]: <info> [1715892894.3035] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:54 fedora NetworkManager[2272]: <info> [1715892894.8079] device (wlp5s0): supplicant interface state: disconnected>
May 16 13:54:54 fedora NetworkManager[2272]: <info> [1715892894.8080] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:55 fedora wpa_supplicant[2341]: wlp5s0: SME: Trying to authenticate with e8:d3:eb:b8:d2:c7 (SSID='MEH' freq=5180>
May 16 13:54:55 fedora kernel: wlp5s0: authenticate with e8:d3:eb:b8:d2:c7 (local address=9a:25:6c:43:ef:61)
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.0422] device (wlp5s0): supplicant interface state: scanning -> >
May 16 13:54:55 fedora kernel: wlp5s0: send auth to e8:d3:eb:b8:d2:c7 (try 1/3)
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.0422] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:55 fedora wpa_supplicant[2341]: wlp5s0: Trying to associate with e8:d3:eb:b8:d2:c7 (SSID='MEH' freq=5180 MHz)
May 16 13:54:55 fedora kernel: wlp5s0: authenticated
May 16 13:54:55 fedora kernel: wlp5s0: associate with e8:d3:eb:b8:d2:c7 (try 1/3)
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.0813] device (wlp5s0): supplicant interface state: authenticati>
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.0814] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:55 fedora kernel: wlp5s0: RX AssocResp from e8:d3:eb:b8:d2:c7 (capab=0x1111 status=0 aid=4)
May 16 13:54:55 fedora wpa_supplicant[2341]: wlp5s0: Associated with e8:d3:eb:b8:d2:c7
May 16 13:54:55 fedora wpa_supplicant[2341]: wlp5s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May 16 13:54:55 fedora kernel: wlp5s0: associated
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1092] device (wlp5s0): supplicant interface state: associating >
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1092] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:55 fedora kernel: wlp5s0: Limiting TX power to 30 (30 - 0) dBm as advertised by e8:d3:eb:b8:d2:c7
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1255] device (wlp5s0): supplicant interface state: associated ->
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1256] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:55 fedora wpa_supplicant[2341]: wlp5s0: WPA: Key negotiation completed with e8:d3:eb:b8:d2:c7 [PTK=CCMP GTK=CCMP]
May 16 13:54:55 fedora wpa_supplicant[2341]: wlp5s0: CTRL-EVENT-CONNECTED - Connection to e8:d3:eb:b8:d2:c7 completed [id=0 id_s>
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1738] device (wlp5s0): supplicant interface state: 4way_handsha>
May 16 13:54:55 fedora wpa_supplicant[2341]: wlp5s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=245000
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1745] device (wlp5s0): ip:dhcp4: restarting
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1746] dhcp4 (wlp5s0): canceled DHCP transaction
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1746] dhcp4 (wlp5s0): activation: beginning transaction (timeou>
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1746] dhcp4 (wlp5s0): state changed no lease
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1746] dhcp4 (wlp5s0): activation: beginning transaction (timeou>
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.1749] device (p2p-dev-wlp5s0): supplicant management interface >
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.2098] dhcp4 (wlp5s0): state changed new lease, address=192.168.>
May 16 13:54:55 fedora NetworkManager[2272]: <info> [1715892895.2099] dhcp4 (wlp5s0): state changed new lease, address=192.168.>
From the logs, this screams firmware to me (Intel AX210 in this case)
In this case, historically, we would disable power savings. This is for AX210 and is likely a linux-firmware package issue, not us specifically. Regression.
To determine if power save is on (and it likely is):
iw dev | grep Interface | awk '{print $2}' | xargs -I {} iw dev {} get power_save
If this returns: Power save: on
Run this script:
echo -e "[connection]\nwifi.powersave = 2" | sudo tee /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf && sleep 1 && echo -e "\033[1;33mProcess is complete"
and then
sudo systemctl restart NetworkManager
Check again:
iw dev | grep Interface | awk '{print $2}' | xargs -I {} iw dev {} get power_save
Should output: Power save: off
Completed testing of AX210 with power saving OFF.
Flawless, no issues whatsoever, no drops. Script and journal confirmed it.
Suggestion for anyone using AX210, continue with this:
To determine if power save is on (and it likely is):
iw dev | grep Interface | awk '{print $2}' | xargs -I {} iw dev {} get power_save
If this returns: Power save: on
Run this script:
echo -e "[connection]\nwifi.powersave = 2" | sudo tee /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf && sleep 1 && echo -e "\033[1;33mProcess is complete"
and then
sudo systemctl restart NetworkManager
Check again:
iw dev | grep Interface | awk '{print $2}' | xargs -I {} iw dev {} get power_save
Should output: Power save: off
Final Results
Intel AX210 on FW 16 does indeed see drops for 10 seconds at a time when a drop occurs.
Repeated this, with power saving for wifi disabled and did not see the drop offs.
Noticed something here - see the jump happening here:
Thu May 16 01:54:45 PM PDT 2024:
Connected to d8:8e:d4:7d:2e:c8 (on wlp5s0)
SSID: (fake)
freq: 6135.0
Thu May 16 01:54:55 PM PDT 2024:
Not connected.
Thu May 16 01:55:05 PM PDT 2024:
Connected to e8:d3:eb:b8:d2:c7 (on wlp5s0)
SSID: (fake)
freq: 5180.0
MediaTek card on FW 16 did not see any drop off, even with the defaults of having power save on.
Wi-Fi 6E.
WPA3 enabled.
No QoS or “client steering” enabled on the router. <—this is important
Bluetooth on, Bluetooth off.
3.03 FW 16 BIOS.
