You are not logged in.
Till 5.14, i was able to connect to my wifi connection which was around 9% signal strength without any drops in between but after 5.15, I'm literally not able to connect to it at all, it just disappears from the list cause of low strength. Even if i miraculously do connect to it, it barely lasts for a minute or 2 before getting disconnected.
This is certainly a kernel problem cause i tried 5.10lts and i was able to connect in that normally, same with 5.14. Any suggestions? I use NetworkManager. My chipset is intel AX200 (rev 1a), i'm basically not able to use the wifi now at all unless i switch on hotspot in my mobile. My current kernel is 5.16.0-rc3-1-mainline BUT I did try the latest 5.15.7-arch1-1 too, the issue exists in both the versions. If i revert back to 5.14 or use the 5.10 lts, the issue does not exist. Not sure if it's of any relevance but the network which i want to connect to is a 5ghz one.
Last edited by jessepinkman2802 (2021-12-12 18:19:56)
Offline
https://wiki.archlinux.org/title/Kernel … egressions
TMy current kernel is 5.16.0-rc3-1-mainline
That's the old version:
archie:~$ uname -r
5.16.0-rc4-1-mainline
archie:~$Jin, Jîyan, Azadî
Offline
https://wiki.archlinux.org/title/Kernel … egressions
jessepinkman2802 wrote:TMy current kernel is 5.16.0-rc3-1-mainline
That's the old version:
archie:~$ uname -r 5.16.0-rc4-1-mainline archie:~$
It's marked out of date in aur, how did you install rc4?
Offline
I changed the _tag & pkgver.
Jin, Jîyan, Azadî
Offline
You might consider waiting a few hours for rc5 to be released.
Offline
In the meantime:
systool -vm iwlwifi
iw dev wlp_redictable_my_ass_lennart set power_save offSee https://wiki.archlinux.org/title/Power_ … interfaces
Also
Even if i miraculously do connect to it, it barely lasts for a minute or 2 before getting disconnected … I use NetworkManager.
Please post a complete system journal. Are you always able to scan the AP but then fail the connection or does it randomly not show up in scans?
I'd also try to stop/disable NM and attempt a connection w/ eg. wifi-menu or at least disable https://wiki.archlinux.org/title/Networ … domization
Online
In the meantime:
systool -vm iwlwifi iw dev wlp_redictable_my_ass_lennart set power_save offSee https://wiki.archlinux.org/title/Power_ … interfaces
Also
Even if i miraculously do connect to it, it barely lasts for a minute or 2 before getting disconnected … I use NetworkManager.
Please post a complete system journal. Are you always able to scan the AP but then fail the connection or does it randomly not show up in scans?
I'd also try to stop/disable NM and attempt a connection w/ eg. wifi-menu or at least disable https://wiki.archlinux.org/title/Networ … domization
Actually both, it doesn't show up in the scans and even if it does show up very rarely i am unable to connect to it. I tried connecting to it via other methods too such as nmtui, iwctl, same issue.
Offline
In the meantime:
systool -vm iwlwifi iw dev wlp_redictable_my_ass_lennart set power_save offSee https://wiki.archlinux.org/title/Power_ … interfaces
Also
Even if i miraculously do connect to it, it barely lasts for a minute or 2 before getting disconnected … I use NetworkManager.
Please post a complete system journal. Are you always able to scan the AP but then fail the connection or does it randomly not show up in scans?
I'd also try to stop/disable NM and attempt a connection w/ eg. wifi-menu or at least disable https://wiki.archlinux.org/title/Networ … domization
https://pastebin.com/VvC691wa for the journal
Offline
I tried connecting to it via other methods too such as nmtui, iwctl, same issue.
Did you stop networkmaanger before? Because you're actually associating to the AP w/ high frequency and then immediately deauthenticate
Dec 13 10:25:33 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:25:33 sepia kernel: wlan0: associated
Dec 13 10:25:36 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:25:36 sepia kernel: wlan0: associated
Dec 13 10:25:42 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:25:42 sepia kernel: wlan0: associated
Dec 13 10:25:44 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:25:44 sepia kernel: wlan0: associated
Dec 13 10:25:46 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:25:46 sepia kernel: wlan0: associated
Dec 13 10:25:48 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:25:48 sepia kernel: wlan0: associated
Dec 13 10:26:55 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:26:55 sepia kernel: wlan0: associated
Dec 13 10:27:22 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:27:22 sepia kernel: wlan0: associated
Dec 13 10:27:25 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:27:25 sepia kernel: wlan0: associated
Dec 13 10:27:32 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:27:32 sepia kernel: wlan0: associated
Dec 13 10:27:44 sepia wpa_supplicant[608]: wlan0: Associated with 26:6b:df:3b:cf:d7
Dec 13 10:27:44 sepia kernel: wlan0: associated
Dec 13 10:28:04 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:04 sepia kernel: wlan0: associated
Dec 13 10:28:06 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:06 sepia kernel: wlan0: associated
Dec 13 10:28:09 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:09 sepia kernel: wlan0: associated
Dec 13 10:28:13 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:13 sepia kernel: wlan0: associated
Dec 13 10:28:17 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:17 sepia kernel: wlan0: associated
Dec 13 10:28:22 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:22 sepia kernel: wlan0: associated
Dec 13 10:28:24 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:24 sepia kernel: wlan0: associated
Dec 13 10:28:27 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:27 sepia kernel: wlan0: associated
Dec 13 10:28:31 sepia kernel: wlan0: associated
Dec 13 10:28:31 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:32 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:32 sepia kernel: wlan0: associated
Dec 13 10:28:34 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:34 sepia kernel: wlan0: associated
Dec 13 10:28:37 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:37 sepia kernel: wlan0: associated
Dec 13 10:28:41 sepia wpa_supplicant[608]: wlan0: Associated with 24:0b:88:64:2f:3d
Dec 13 10:28:41 sepia kernel: wlan0: associated
Dec 13 10:28:46 sepia systemd-journald[286]: Journal stoppedWhat's the average signal strength on a "good" boot (grep the journal for "signal=")?
Also please avoid quoting entire posts and if nobody has replied, don't bump but edit your prvious post.
Thanks.
Online
Did you stop networkmaanger before? Because you're actually associating to the AP w/ high frequency and then immediately deauthenticate
What's the average signal strength on a "good" boot (grep the journal for "signal=")?
Yes, i did stop nm before trying those other methods, by good boot do you mean when i was able to connect properly to the wifi? like when i boot with 5.10 lts for example (wifi works fine in that one)
Offline
by good boot do you mean when i was able to connect properly to the wifi?
Yes, and the signal strength there (notably whether it's more than on a "bad" boot; unfortunately we lost the journal paste but iirc. it was around -90?)
Online
@seth
this is the journal i got when the wifi connects to makmay-5ghz (using 5.10 lts) [journalctl -b | grep -A 2 signal=]
Dec 30 11:14:27 sepia wpa_supplicant[576]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-80 noise=9999 txrate=26000
Dec 30 11:14:27 sepia NetworkManager[487]: <info> [1640843067.2462] device (wlan0): supplicant interface state: associated -> completed
Dec 30 11:14:27 sepia NetworkManager[487]: <info> [1640843067.2463] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "makmay_5ghz"
--
Dec 30 11:14:27 sepia wpa_supplicant[576]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-80 noise=9999 txrate=26000
Dec 30 11:14:27 sepia NetworkManager[487]: <info> [1640843067.3178] dhcp4 (wlan0): state changed unknown -> bound, address=192.168.1.95
Dec 30 11:14:27 sepia NetworkManager[487]: <info> [1640843067.3198] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
--
Dec 30 11:14:38 sepia wpa_supplicant[576]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-86 noise=9999 txrate=26000
Dec 30 11:14:45 sepia systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Dec 30 11:14:45 sepia audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
No issues what so ever, it shows the signal strength as 7% when connected to makmay_5ghz but connects perfectly fine.
This is the journal i got when using 5.16.0-rc7-1-mainline kernel,
Dec 30 11:24:28 sepia wpa_supplicant[662]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=9999 txrate=26000
Dec 30 11:24:28 sepia NetworkManager[575]: <info> [1640843668.8513] device (wlan0): supplicant interface state: 4way_handshake -> completed
Dec 30 11:24:28 sepia NetworkManager[575]: <info> [1640843668.8514] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "makmay"
--
Dec 30 11:24:42 sepia wpa_supplicant[662]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-71 noise=9999 txrate=26000
Dec 30 11:24:42 sepia NetworkManager[575]: <info> [1640843682.9341] device (wlan0): disconnecting for new activation request.
Dec 30 11:24:42 sepia NetworkManager[575]: <info> [1640843682.9342] device (wlan0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
--
Dec 30 11:25:21 sepia wpa_supplicant[662]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-74 noise=9999 txrate=26000
Dec 30 11:25:21 sepia NetworkManager[575]: <info> [1640843721.0256] device (wlan0): supplicant interface state: 4way_handshake -> completed
Dec 30 11:25:21 sepia NetworkManager[575]: <info> [1640843721.0257] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "makmay"
I am literally unable to connect to makmay_5ghz network, I am not able to find it in the list of wifi networks most of the times but even when it appears and i try connecting to it, it just doesn't connect.
Offline
Do you have the signal strength when connected to the 2.4GHz network on the lts kernel (the 2.4GHz strength on the 5.16 kernel is already bad… and the 5GHz signal is on the low end of being usable)
Online
Do you have the signal strength when connected to the 2.4GHz network on the lts kernel (the 2.4GHz strength on the 5.16 kernel is already bad… and the 5GHz signal is on the low end of being usable)
yes, the signal strength seems to be the same in both the kernels, although the signal level is very bad in the lts kernel it connects and wors perfectly fine with no drops whatsoever
Offline
Did you ever post the output of "systool -vm iwlwifi" and try to deactivate the power saving feature in iw (see #6, you might have to enable the feature in the iwlwifi parameters to get the control to actively disable it afterwards)
Also does the 5GHz actually solidly connect if you move closer to the AP for a better signal? (so we're not chasing ghosts here…)
Last edited by seth (2022-01-01 16:08:49)
Online
Did you ever post the output of "systool -vm iwlwifi" and try to deactivate the power saving feature in iw
here's the output of the command
Module = "iwlwifi"
Attributes:
coresize = "466944"
initsize = "0"
initstate = "live"
refcnt = "1"
srcversion = "8CDEE66460989943E39B43A"
taint = ""
uevent = <store method only>
Parameters:
11n_disable = "0"
amsdu_size = "0"
bt_coex_active = "Y"
debug = "0"
disable_11ac = "N"
disable_11ax = "N"
enable_ini = "Y"
fw_restart = "Y"
led_mode = "0"
nvm_file = "(null)"
power_level = "0"
power_save = "N"
remove_when_gone = "N"
swcrypto = "0"
uapsd_disable = "3"
Sections:looks like the powersave feature isn't enabled and also i am facing this another issue since 5.15 with bluetooth disconneccting frequently and the recconnecting automatically (if not i have to reboot) not sure if both are related but the common factor is the chipset AX200 and 5.15 kernel (happens in 5.16 too)
oh yes, if i move the laptop closer to ap it connects normally with no issues
Last edited by jessepinkman2802 (2022-01-02 07:16:20)
Offline
So try to pass "power_save=1" to iwlwifi so you can effectively run "iw dev wlp_whatever_the_nic set power_save off"
Another thing to try might be "disable_11ax=1"
https://wiki.archlinux.org/title/Kernel … le_options - the kernel commandline allows transient changes that will also apply if the module is copied in the initramfs.
Bluetooth operates on 2.4GHz - do the disconnects happen when connecting on that band or entirely regardless of the wifi?
Online