Intel AX210 WiFi - Continuous disconnections and low speed

So, I don’t know if it’s just a fortuitous coincidence or if it’s a consequence of a big upgrade done in the week but since Wednesday I’ve been having consistent network problems.

I have a ROG Zephyrus to which I have long ago replaced the Realtek network card with an Intel AX210, with which on average, I was traveling on 50-60 Mbps and maximum ping 25ms, with a very stable connection, but since precisely Wednesday I experience continuous disconnections, sometimes I have to reboot the computer in order to connect to any wi fi network.
Up until last night the disconnections were periodic every half hour or so, but today the pc connects yes or no 10 minutes and then goes into a “connection on/connection off” loop, going on for even half an hour and then "this network has no internet access (right now I’m using my cell in USB tethering even just to make this topic… and the phone is using wifi, so obviously the network is not the problem).

I know there is already this topic in the forum, but I have already tested several kernels and the situation is the same:

┬─[omar@ROG-book:~]─[14:26:26]
╰─>$ garuda-inxi                                                                                                                                                                    14:26:26
System:
  Kernel: 6.8.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=6edd2000-1e93-4215-8ee2-7e6d4c89d6d1 rw rootflags=subvol=@
    quiet resume=UUID=6e738cf9-74e8-47a5-8011-d188987253a0 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.1.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ROG Zephyrus G14 GA402RJ_GA402RJ
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: GA402RJ v: 1.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends LLC. v: GA402RJ.316
    date: 11/10/2022
Battery:
  ID-1: BAT0 charge: 36.0 Wh (62.9%) condition: 57.2/76.0 Wh (75.3%)
    power: 58.5 W volts: 15.9 min: 15.9 model: ASUSTeK ASUS Battery type: Li-ion
    serial: N/A status: charging
CPU:
  Info: model: AMD Ryzen 9 6900HS with Radeon Graphics bits: 64 type: MT MCP
    arch: Zen 3+ gen: 4 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
    family: 0x19 (25) model-id: 0x44 (68) stepping: 1 microcode: 0xA404102
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 747 high: 1762 min/max: 400/4935 scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 1316 2: 1751 3: 1347
    4: 400 5: 400 6: 400 7: 400 8: 1762 9: 1390 10: 400 11: 400 12: 400
    13: 400 14: 400 15: 400 16: 400 bogomips: 105392
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Navi 23 [Radeon RX 6650 XT / 6700S 6800S] vendor: ASUSTeK
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1
    empty: HDMI-A-1,Writeback-1,eDP-1 bus-ID: 03:00.0 chip-ID: 1002:73ef
    class-ID: 0300
  Device-2: AMD Rembrandt [Radeon 680M] vendor: ASUSTeK driver: amdgpu
    v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22
    pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: eDP-2 empty: DP-2,
    DP-3, DP-4, DP-5, DP-6, DP-7, DP-8, DP-9, Writeback-2 bus-ID: 07:00.0
    chip-ID: 1002:1681 class-ID: 0300 temp: 40.0 C
  Device-3: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:2 chip-ID: 13d3:56eb
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.0.99
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: DP-1 model: VG34VQEL1A serial: <filter> built: 2023
    res: 3440x1440 dpi: 110 gamma: 1.2 size: 794x340mm (31.26x13.39")
    diag: 864mm (34") modes: max: 3440x1440 min: 640x350
  Monitor-2: eDP-2 model: TL140ADXP01 built: 2021 res: 2560x1600 dpi: 216
    gamma: 1.2 size: 301x188mm (11.85x7.4") diag: 355mm (14") ratio: 16:10
    modes: max: 2560x1600 min: 640x480
  API: Vulkan v: 1.3.279 layers: 11 device: 0 type: discrete-gpu
    name: AMD Radeon RX 6700S driver: amd v: 2024.Q1.3 (LLPC)
    device-ID: 1002:73ef surfaces: xcb,xlib,wayland device: 1
    type: integrated-gpu name: AMD Radeon Graphics driver: amd
    v: 2024.Q1.3 (LLPC) device-ID: 1002:1681 surfaces: xcb,xlib,wayland
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1
    chip-ID: 1002:ab28 class-ID: 0403
  Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 07:00.1
    chip-ID: 1002:1640 class-ID: 0403
  Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: ASUSTeK
    driver: snd_pci_acp6x v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x,
    snd_pci_acp5x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 07:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-4: AMD Family 17h/19h HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 07:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.8.9-zen1-1-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0
    chip-ID: 8086:2725 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 3.0 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 10-1.2.4:5
    chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
  IF: enp8s0f4u1u2u4 state: down mac: <filter>
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-1:2 chip-ID: 8087:0032
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.3
    lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 1.62 TiB used: 213.14 GiB (12.9%)
  ID-1: /dev/mmcblk0 maj-min: 179:0 model: SD256 size: 238.3 GiB block-size:
    physical: 512 B logical: 512 B type: Removable tech: SSD serial: <filter>
    scheme: GPT
  SMART Message: Unknown smartctl error. Unable to generate data.
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-2: /dev/nvme0n1 maj-min: 259:0 vendor: Micron model: 2450 MTFDKBA1T0TFK
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: V5MA010 temp: 33.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Kingston model: SNV2S500G
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.2 spd: 10 Gb/s lanes: 1 mode: 3.2 gen-2x1 tech: N/A
    serial: <filter> fw-rev: 1.00 scheme: MBR
Partition:
  ID-1: / raw-size: 928.59 GiB size: 928.59 GiB (100.00%)
    used: 213.14 GiB (23.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 928.59 GiB size: 928.59 GiB (100.00%)
    used: 213.14 GiB (23.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 928.59 GiB size: 928.59 GiB (100.00%)
    used: 213.14 GiB (23.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 928.59 GiB size: 928.59 GiB (100.00%)
    used: 213.14 GiB (23.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 24.98 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
  ID-2: swap-2 type: zram size: 22.71 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 41.2 C mobo: N/A
  Fan Speeds (rpm): cpu: 2500
  GPU: device: amdgpu temp: 40.0 C device: amdgpu temp: 42.0 C mem: 38.0 C
    fan: 0 watts: 4.00
Info:
  Memory: total: 24 GiB note: est. available: 22.71 GiB used: 5.97 GiB (26.3%)
  Processes: 411 Power: uptime: 1h 43m states: freeze,mem,disk
    suspend: s2idle wakeups: 1 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 9.06 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 255 default: graphical tool: systemctl
  Packages: 1916 pm: pacman pkgs: 1891 libs: 510 tools: pacseek,paru
    pm: flatpak pkgs: 25 Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi
    default: fish v: 3.7.1 running-in: kitty inxi: 3.3.34
Garuda (2.6.26-1):
  System install date:     2024-04-01
  Last full system update: 2024-05-06
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:

On the Arch Linux forum I found this related topic, but honestly it was not helpful at all
WRT: Invalid buffer destination

I upload the output that was mentioned in this topic

╰─>$ sudo dmesg | grep iwlwifi                                                                                        18:42:00
[sudo] password di omar:       
[    8.889686] iwlwifi 0000:05:00.0: enabling device (0000 -> 0002)
[    8.909072] iwlwifi 0000:05:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000
[    8.909107] iwlwifi 0000:05:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000
[    8.914721] iwlwifi 0000:05:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41
[    8.915066] iwlwifi 0000:05:00.0: loaded firmware version 86.fb5c9aeb.0 ty-a0-gf-a0-86.ucode op_mode iwlmvm
[    9.630797] iwlwifi 0000:05:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[    9.643329] iwlwifi 0000:05:00.0: WRT: Invalid buffer destination
[    9.798169] iwlwifi 0000:05:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[    9.798232] iwlwifi 0000:05:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    9.798285] iwlwifi 0000:05:00.0: WFPM_AUTH_KEY_0: 0x90
[    9.798338] iwlwifi 0000:05:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[    9.799262] iwlwifi 0000:05:00.0: loaded PNVM version e28bb9d7
[    9.814944] iwlwifi 0000:05:00.0: Detected RF GF, rfid=0x10d000
[    9.885536] iwlwifi 0000:05:00.0: base HW address: c8:15:4e:c8:09:01
[    9.903282] iwlwifi 0000:05:00.0 wlp5s0: renamed from wlan0
[   10.075020] iwlwifi 0000:05:00.0: WRT: Invalid buffer destination
[   10.228378] iwlwifi 0000:05:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   10.228469] iwlwifi 0000:05:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   10.228511] iwlwifi 0000:05:00.0: WFPM_AUTH_KEY_0: 0x90
[   10.228559] iwlwifi 0000:05:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[   10.325579] iwlwifi 0000:05:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0
[   10.379252] iwlwifi 0000:05:00.0: WRT: Invalid buffer destination
[   10.532465] iwlwifi 0000:05:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   10.532506] iwlwifi 0000:05:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   10.532548] iwlwifi 0000:05:00.0: WFPM_AUTH_KEY_0: 0x90
[   10.532591] iwlwifi 0000:05:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0

Just post garuda-inxi, please.

2 Likes

Does rolling back your system to a date before your last update solve your connection issues?

Are you running a VPN? If so be sure to disable it completely.

Have you tested the LTS kernel yet?

Do you have another spare router you could perhaps swap in as a test?

This could be a WiFi power saving issue.

Create a driver configuration file:

/etc/modprobe.d/iwlmvm.conf

Add the line below to the text file:

options iwlmvm power_scheme=1

Save the file and reboot.

if the configuration file above doesn’t improve things. You can delete that configuration file you created if it is of no help.

You could also test other power saving options, see:

Also see:

Also be sure to try disabling MAC address randomization.

1 Like

I have already written the kernels used (three different lts: mainline, cached and real time).

I tried with the phone’s hotspot using the SIM’s gigas, same result… and also with my workplace’s wifi network.

And with snapshots the situation does not change (but it could depend that perhaps due to bad luck the working setting has been lost, older than the 10 snapshots saved).

While regarding the VPN, I’m only using a meshnet (tailscale), but tomorrow I’ll try to deactivate it.

EDIT: this morning I did some testing with the office network where I work–it was working normally (router, a classic ZTE branded by the phone provider)…

That the problem at 'this point stems from the very bad combo “intel AX210 card + Asus ROG AX6000 router”?

You should do as requested.

1 Like

You can edit your first post.

That the problem at 'this point arises from the very bad combo “intel AX210 card + Asus ROG AX6000 router”?

I have done some tests now…and indeed the connection problems only concern when wifi 6 is involved (router at home and smarthone in hotspot), while in the office there is a wifi 5

https://forum.endeavouros.com/t/low-wifi-link-rate/23341/3

The suggestions here proved to be useless

I would like to point out an oddity: the first link, Intermittent Internet Dropout I had already seen and tried: with the zen kernel it was useless, with no change…

I tried a test with another kernel (cachy-bore), and after a reboot it seems to have done something…

This point in the first link

To make disabling the iwlwifi power saving options permanent, run the following command:

echo 'options iwlwifi power_save=0 d0i3_disable=0 uapsd_disable=0' | sudo tee /etc/modprobe.d/iwlwifi.conf

Then, reboot.

in addition to doubling the wifi speed (I’ve done several speedtests and am between 75 and 135 Mbps), it seems to have actually solved the problem–at least for the time being.

If it has indeed resolved, I think it should be pointed out that for some reason that point did not work with the zen kernel, but I couldn’t tell whether because of some specificity of my situation or whether it actually happens like that to others

1 Like

Well, I’m glad I linked those old posts of mine from the EndeavourOS forum for you. It sounds like the power saving tweaks I posted there, combined with a different kernel has helped a lot. Fingers crossed, it stays that way. :crossed_fingers: Unfortunately, any kernel update could unravel your hard work and result in things going downhill again.

I was really hoping that Intel would have worked out all the bugs on their WiFi 5 & 6 adapters by now, but no such luck. The good thing about the iwlwifi driver is that it has so many options that with proper tuning its performance can usually be improved.

If you search the Garuda forum’s networking section for my posts related to the iwlwifi driver you will find many of the best iwldriver driver tweaks posted here. Sadly, all those Intel options are a bit much for new users to figure out on their own and they often just give up as it seems like black magic is required to get some intel adapters working properly.

2 Likes

Unfortunately, any kernel update could unravel your hard work and result in things going downhill again.

On this I emphasize that reverting back to the zen kernel sends everything down the drain again (done by mistake, being the default kernel on reboot it started with that). I balked again, but rebooted with the cachy-bore kernel and re-disabled the wifi power saver seems to be back up and running again…although it didn’t seem like it immediately, beacuse to all this I would like to add a colossal tease: here in italy it is now 10 pm (rush hour as far as traffic is concerned) and although the usual ping for this time slot is between 35 and 45 ms (and it is so if I use the notebook “alone”)… but, if I attach the usb c docking station to connect to the notebook external monitor, keyboard (wired, not bt) and the dongle for in Xbox controller, the ping drops so much (even 150-180 ms) and the connection speed collapses to 1. 5-7.5 MBps…

I keep the dock just for the monitor and connect the rest (keyboard and dongle) with the notebook ports, and the ping goes up 55 ms… with speeds around 45-50 Mbps

To all this I would like to add a colossal tease: probably it is because of the time of day (here in italy it is now 10 pm, rush hour as far as traffic is concerned) and so I have a quite low ping (60-80ms) compared to the usual and today’s best results (22-25 ms) but, if I attach the usb c docking station to connect to the notebook external monitor, keyboard (wired, not bt) and the dongle for in Xbox controller, the ping drops so much (even 150-180 ms) and the connection speed collapses to 1. 5-7.5 MBps…

I keep the dock just for the monitor and connect the rest (keyboard and dongle) with the notebook ports, and the ping goes up 55 ms… with speeds around 45-50 Mbps

At 'this point I would like to check by also connecting the monitor directly to the notebook, but at this time (10 pm in Italy) I don’t feel like moving furniture to retrieve cables :grin: :grin: :grin:

I emphasize that 'til it gave the problem at issue in the topic, it wasn’t like that: I had the same ping and speed (maybe just a slight percentage gap, but negligible) both in stand-alone use and with the docked notebook

Fingers crossed, it stays that way. :crossed_fingers:

We seriously hope…

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.