You are not logged in.
while connected to wifi i randomly get no internet even though iam still connected, to get connection back i have to restart iwd.service
i don't think the problem is related to iwd because i had the same issue with wpa_supplicant and thought it caused the problem but appearntly not
i tried to open wireshark to see what is happening and only that i could see are uncomplete arp resolution messages something looked like this:
who has 192.168.1.1? tell 192.168.1.24
another problem is that "Tx-Power" is stuck at 3 dBm which i think is really low
also "Tx excessive retries" gets to a high number really quick i looked into some solution and some suggest that i move to AP channel to another (non over lapping one), i did so and i'am not even in an area that is crowded with APs
~$ arp -a
? (192.168.1.1) at <incomplete> on wlan0
~$ uname -a
Linux dyb1b0k 6.11.3-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Thu, 10 Oct 2024 20:11:02 +0000 x86_64 GNU/Linux
~$ sudo dmesg | grep mt7921
[sudo] password for dy:
[ 3.916244] mt7921e 0000:2d:00.0: enabling device (0000 -> 0002)
[ 3.916447] mt7921e 0000:2d:00.0: disabling ASPM L1
[ 3.920616] mt7921e 0000:2d:00.0: ASIC revision: 79610010
[ 3.995874] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240826150948a
[ 4.255209] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20240826151030
[ 224.778017] mt7921e 0000:2d:00.0 wlan0: entered promiscuous mode
[ 233.219861] mt7921e 0000:2d:00.0 wlan0: left promiscuous mode
[ 243.953509] mt7921e 0000:2d:00.0: Message 00020003 (seq 9) timeout
[ 246.961600] mt7921e 0000:2d:00.0: Message 00020003 (seq 10) timeout
[ 247.036074] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240826150948a
[ 247.047556] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20240826151030
[ 637.282728] mt7921e 0000:2d:00.0: Message 00020003 (seq 5) timeout
[ 637.358442] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240826150948a
[ 637.370064] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20240826151030
[ 960.364793] mt7921e 0000:2d:00.0: Message 00020003 (seq 3) timeout
[ 960.440466] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240826150948a
[ 960.452161] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20240826151030
other laptop specs: rtx 2050, intel core i5-11400H, ASUS TUF Gaming F15 FX506HF_FX506HF
thanks in advance <3
Last edited by dybbuk (2024-10-18 13:50:07)
Offline
"mt7921e.disable_aspm=Y", https://wiki.archlinux.org/title/Kernel_parameters
https://bbs.archlinux.org/viewtopic.php?id=299987&p=3
Edit, also sanity check:
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
Last edited by seth (2024-10-18 11:56:36)
Online
i did some research before and had added "pcie_aspm=off" and it was working, now i tried "mt7921e.disable_aspm=Y" then:
~$ sudo dmesg | grep mt7921
[sudo] password for dy:
[ 0.000000] Command line: initrd=initramfs-linux-zen.img root=UUID=272650fe-23dc-44c1-8077-243988a23843 nvidia.NVreg_PreserveVideoMemoryAllocations=1 mt7921e.disable_aspm=Y
[ 0.035415] Kernel command line: initrd=initramfs-linux-zen.img root=UUID=272650fe-23dc-44c1-8077-243988a23843 nvidia.NVreg_PreserveVideoMemoryAllocations=1 mt7921e.disable_aspm=Y
[ 4.773283] mt7921e 0000:2d:00.0: enabling device (0000 -> 0002)
[ 4.773544] mt7921e 0000:2d:00.0: disabling ASPM L1
[ 4.773545] mt7921e 0000:2d:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 4.777596] mt7921e 0000:2d:00.0: ASIC revision: 79610010
[ 4.852899] mt7921e 0000:2d:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240826150948a
[ 4.864352] mt7921e 0000:2d:00.0: WM Firmware Version: ____010000, Build Time: 20240826151030
also:
~$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
blueman-mechanism.service | multi-user.target.wants
bluetooth.service | bluetooth.target.wants
dbus-org.bluez.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-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-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
Offline
If the OS doesn't have ASPM control and that's not because of pcie_aspm=off (doesn't seem to be there), pcie_aspm=off should™ have been inert.
Regardless, did the network stabilize?
Online
thenks for your replies, i will post again if it happens
also what about the fact that Tx-Power is stuck at 3 dBm i looked everywhere and tried many solutions but it's stull stuck at the same value
Offline
Is it right now?
I'd attribute that to power saving issues unless the AP explicitly requests that.
Online
i disabled power saving a while ago, anyway i looked into it and i think the 3 tx power is just a visual bug and the driver can't report the real value
but another issue is that "Tx excessive retries" gets to a really high number really quick
Offline
Please post your complete system journal for an affected boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
for the current one.
Online
the same problem just happend a min ago and i got no internet again
here's the output of journalctl
Offline
Oct 19 11:22:46 dyb1b0k su[5316]: pam_unix(su:session): session opened for user root(uid=0) by dy(uid=1000)
Oct 19 11:25:31 dyb1b0k su[5316]: pam_unix(su:session): session closed for user root
Oct 19 11:25:40 dyb1b0k sudo[5461]: pam_systemd_home(sudo:auth): New sd-bus connection (system-bus-pam-systemd-home-5461) opened.
Oct 19 11:25:41 dyb1b0k sudo[5461]: dy : TTY=pts/0 ; PWD=/home/dy ; USER=root ; COMMAND=/usr/bin/systemctl restart iwd.service
Oct 19 11:25:41 dyb1b0k sudo[5461]: pam_unix(sudo:session): session opened for user root(uid=0) by dy(uid=1000)
Oct 19 11:25:41 dyb1b0k iwd[578]: Terminate
Oct 19 11:25:41 dyb1b0k systemd[1]: Stopping Wireless service...
Oct 19 11:25:41 dyb1b0k iwd[578]: Removing scan context for wdev 2
This is you restarting iwd, I guess as consequence of the problem?
There're no obvious issues prior to that, the only thing in proximity is
Oct 19 11:16:22 dyb1b0k wireplumber[791]: pw.node: (bluez_output.08_E4_DF_D9_E1_26.1-71) graph xrun not-triggered (0 suppressed)
Oct 19 11:16:22 dyb1b0k wireplumber[791]: pw.node: (-71) xrun state:0x7d1298cb8008 pending:1/2 s:2982889279954 a:2982889427456 f:2982889447581 waiting:147502 process:20125 status:triggered
Are you connecting to a 2.4GHz AP?
Can you move to 5GHz? Might simply be BT interference. The signal is very good, though.
Online
yes, the only was to get connection back is to restart iwd
my AP does not support 5GH, and i don't even thinks it's the interference because i'am not in an area that is crowded with APs, something that i forgot to mention is that i dual boot with win11 (i extremely rarely open it tho) and it doesn't get interruptet there
Offline
something that i forgot to mention is that i dual boot with win11
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
i don't even thinks it's the interference because i'am not in an area that is crowded with APs
No, the interference would come from *your* bluetooth device (BT operates on the same 2.4GHz band as your wifi)
Online
ok, i disabled faststart and executing
(GP "HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Power")."HiberbootEnabled"
gives
0
but the same problem happend again a min ago, restarted iwd to get connection back
and i disabled bluetooth but "Tx excessive retries" still gets high quickly
Offline
but "Tx excessive retries" still gets high quickly
Disabled or rfkill'd BT?
Do you also still get conneciton losses/issues?
Same problem w/ the LTS kernel or 6.10.9?
(6.11 has quite some issues, both reg. radio and drm…)
Online
disabled
i think switching to LTS solved both issues, thanks so much <3
Last edited by dybbuk (2024-10-22 04:41:43)
Offline
It's more a workaround than a solution, you want to keep an eye on the situation of the main kernel and esp. checl whether rfkill'ing BT helps (since the BT stack ha multiple bugs in 6.11 - at least one should be addressed in the latest kernel update)
Online
nope i rushed, it didn't solve my issue
sorry
Offline
nb. that the recent LTS kernels have picked up a bunch of bogus BT commits, so this might have re-broken w/ an update of the lts kernel?
It would be useful if you can narrow down the offending version, ie. eg. 6.6.53 works but 6.6.54 is broken or so.
Online
i think the issue been solved by either upgrading to 6.11.5-zen1-1-zen or turning off "Allow the computer to turn off this device" in windows from Device Manager
(both issues random interrupts and high Tx excessive retries)
Last edited by dybbuk (2024-11-02 13:12:12)
Offline
If the windows setting had any impact on the situation, fast-start or any kind of other hibernation was/is still/again in place.
Online
uuuuhhhhh the issue is back idk what changed beside upgrading to 6.11.9-zen1-1-zen
Offline
Does downgrading the kernel restore the status quo ante?
Is BT (still) rfkill'd?
Also see https://wiki.archlinux.org/title/Blueto … ot_pairing
If the windows setting had any impact on the situation, fast-start or any kind of other hibernation was/is still/again in place.
In doubt reset the BIOS cmos.
Online
its way more stable than before but still happens from time to time, and after some trying i found out doing "rfkill toggle wlan" few times fixes it (6.12.1-zen1-1-zen)
Offline