mt7921 "Tx excessive retries" gets to a high number really quick

dybbuk · 2025-03-17 11:52:21

issue: "Tx excessive retries" gets to a high number really quick and "Tx-Power" is stuck at 3 dBm
specs:

6.14.0-rc6-1-mainline (i tried zen, lts, stock) but all had the same issue
ASUS TUF Gaming F15 FX506HF_FX506HF
CPU: 11th Gen Intel(R) Core(TM) i5-11400H (12) @ 4.50 GHz
GPU 1: NVIDIA GeForce RTX 2050 [Discrete]
GPU 2: Intel UHD Graphics @ 1.45 GHz [Integrated]

~$ lspci | grep -i mt

0000:2d:00.0 Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter

dmesg

 ~$ iwconfig 
lo        no wireless extensions.

enp46s0   no wireless extensions.

wlan0     IEEE 802.11  ESSID:"shikonokonoko"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 34:DA:B7:AC:A1:53   
          Bit Rate=78 Mb/s   Tx-Power=3 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=70/70  Signal level=-38 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1173  Invalid misc:0   Missed beacon:0

also i don't wanna use the kenel parameter "pcie_aspm=off" becuase it makes batter usage way too high when not on charger

 ~$ rfkill 
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0     blocked unblocked
 1 wlan      phy0   unblocked unblocked

i'am on a 2.4GHz wifi (can't use 5GHz cus my router dones't support it)
i dual boot win11 and arch but fastboot is disabled from windows

seth · 2025-03-17 14:29:53

i don't wanna use the kenel parameter "pcie_aspm=off" becuase it makes batter usage way too high

Is the implication that you get a *significantly* more reliable connection when disabling ASPM?

[   88.992353] wlan0: deauthenticating from 34:da:b7:ac:a1:53 by local choice (Reason: 3=DEAUTH_LEAVING)
[  363.673198] wlan0: deauthenticating from 34:da:b7:ac:a1:53 by local choice (Reason: 3=DEAUTH_LEAVING)
[  373.288281] wlan0: deauthenticating from 34:da:b7:ac:a1:53 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1110.984157] wlan0: deauthenticating from 34:da:b7:ac:a1:53 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1159.090319] wlan0: deauthenticating from 34:da:b7:ac:a1:53 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1182.784471] wlan0: deauthenticating from 34:da:b7:ac:a1:53 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1212.081082] wlan0: deauthenticating from 34:da:b7:ac:a1:53 by local choice (Reason: 3=DEAUTH_LEAVING)

is that all you going for manual reconnects?

Your signal seems stellar.
Please post the output of

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

Also you're using some BT headset?
WHat if you rfkill BT?

dybbuk · 2025-03-17 15:34:43

seth wrote:

Is the implication that you get a *significantly* more reliable connection when disabling ASPM?

well it was said in the archwiki that "There are some high latency problems with these MediaTek chipsets. To fix this, the only solution is to disable ASPM: /etc/modprobe.d/wifi.conf: options mt7921e disable_aspm=1" but i get [ 2.097079] mt7921e 0000:2d:00.0: can't disable ASPM; OS doesn't have ASPM control
then i found out i have to use pcie_aspm=off as a kernel paratemer, but no it doesn't help with the issue

and yes that's me turning my wifi on and off to get connection back temporarily

seth wrote:

Also you're using some BT headset?
WHat if you rfkill BT?

do you mean hard block? it's soft blocked already

~$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.network1.service    | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
getty@tty1.service                       | getty.target.wants
iwd.service                              | multi-user.target.wants
nvidia-hibernate.service                 | systemd-hibernate.service.wants
nvidia-persistenced.service              | multi-user.target.wants
nvidia-powerd.service                    | multi-user.target.wants
nvidia-resume.service                    | systemd-hibernate.service.wants
nvidia-resume.service                    | systemd-suspend.service.wants
nvidia-suspend.service                   | systemd-suspend.service.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
power-profiles-daemon.service            | graphical.target.wants
remote-fs.target                         | multi-user.target.wants
supergfxd.service                        | getty.target.wants
switcheroo-control.service               | graphical.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-networkd-wait-online.service     | network-online.target.wants
systemd-network-generator.service        | sysinit.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

seth · 2025-03-17 16:11:43

https://wiki.archlinux.org/title/Networ … ess#mt7921 actually advises "mt7921e.disable_aspm=1", have you tried to add that to the kernel parameters and does it also not help?
Also the latency issues do not necessarily equate to

issue: "Tx excessive retries" gets to a high number really quick and "Tx-Power" is stuck at 3 dBm

and the latter is also not indicated by your dmesg, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Have you tried how wpa_supplicant compares to iwd?

Finally disable power-profiles-daemon.service and see whether the issue maybe stems from there.

dybbuk · 2025-03-17 16:54:58

yeh i remember having the issue before switching from wpa_supplicant to iwd
journalctl

seth · 2025-03-17 17:14:45

Mar 17 18:50:03 dyb1b0k kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it

Neither pcie_aspm=off nor mt7921e disable_aspm=1 will do *anything* - including not cause more battery drain.

The journal spans only 2 minutes, but there's no indication of any excessive retries, TX limitations etc.
What's your verbatim metric for the problem?

Mar 17 18:50:07 dyb1b0k asusd[728]: [INFO  asusd]        daemon v6.1.10

Consider disabling that for a test, also you're running the xanmod kernel - same issue w/ the main or lts kernels?

dybbuk · Today 06:32:45

seth wrote:

Neither pcie_aspm=off nor mt7921e disable_aspm=1 will do *anything* - including not cause more battery drain.

no i tried pcie_aspm=off and it did increase battery drain by alot but no it didn't fix the issue

rn connection is very stable but it's very random and unstable most of the times

btw here's an old log

~$ sudo dmesg | grep mt7921
[    4.995396] mt7921e 0000:2d:00.0: enabling device (0000 -> 0002)
[    5.000630] mt7921e 0000:2d:00.0: ASIC revision: 79610010
[    5.074804] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
[    5.086381] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
[  470.341863] mt7921e 0000:2d:00.0: Message 00020003 (seq 10) timeout
[  473.348906] mt7921e 0000:2d:00.0: Message 00020003 (seq 11) timeout
[  473.428898] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
[  473.441689] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
[  596.864861] mt7921e 0000:2d:00.0: Message 00020003 (seq 10) timeout
[  599.872718] mt7921e 0000:2d:00.0: Message 00020003 (seq 11) timeout
[  599.951630] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
[  599.964210] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
[  702.780953] mt7921e 0000:2d:00.0: Message 00020003 (seq 3) timeout
[  705.788968] mt7921e 0000:2d:00.0: Message 00020003 (seq 4) timeout
[  705.875745] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
[  705.888960] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
[  744.634998] mt7921e 0000:2d:00.0: Message 00020003 (seq 1) timeout
[  747.644010] mt7921e 0000:2d:00.0: Message 00020003 (seq 2) timeout
[  747.723349] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
[  747.737289] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
[  846.649303] mt7921e 0000:2d:00.0: Message 00020003 (seq 1) timeout
[  849.657245] mt7921e 0000:2d:00.0: Message 00020003 (seq 2) timeout
[  849.736948] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
[  849.750760] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
[ 1137.909886] mt7921e 0000:2d:00.0: Message 00020003 (seq 8) timeout
[ 1140.918856] mt7921e 0000:2d:00.0: Message 00020003 (seq 9) timeout
[ 1140.998841] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
[ 1141.011874] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045
[ 1336.819652] mt7921e 0000:2d:00.0: Message 00020003 (seq 7) timeout
[ 1339.827667] mt7921e 0000:2d:00.0: Message 00020003 (seq 8) timeout
[ 1339.904646] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20241106151007a
[ 1339.916098] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20241106151045

i will try to remove anything related to asus-linux and report again

seth · Today 07:39:09

https://bbs.archlinux.org/viewtopic.php?id=300490 - 3dBm might be a misreport.

no i tried pcie_aspm=off and it did increase battery drain by alot

That is not possible. Period. The system doesn't provide pcie aspm or at least does not allow the OS to control that.
You might have experienced high battery drain while coincidentally adding that parameter, but it cannot do *anything*

Please post the comeplete journal for that boot - looks like firmware crashes?
But might also just be indicating some S2/S3 cycles.

Arch Linux

#1 2025-03-17 11:52:21

mt7921 "Tx excessive retries" gets to a high number really quick

#2 2025-03-17 14:29:53

Re: mt7921 "Tx excessive retries" gets to a high number really quick

#3 2025-03-17 15:34:43

Re: mt7921 "Tx excessive retries" gets to a high number really quick

#4 2025-03-17 16:11:43

Re: mt7921 "Tx excessive retries" gets to a high number really quick

#5 2025-03-17 16:54:58

Re: mt7921 "Tx excessive retries" gets to a high number really quick

#6 2025-03-17 17:14:45

Re: mt7921 "Tx excessive retries" gets to a high number really quick

#7 Today 06:32:45

Re: mt7921 "Tx excessive retries" gets to a high number really quick

#8 Today 07:39:09

Re: mt7921 "Tx excessive retries" gets to a high number really quick

Board footer