I’ve just reinstalled Manjaro i3 on my XPS 9560 after having to replace the SSD. I have a problem with wifi connectivity, that was not present before I changed the SSD and reinstalled everything.
The wifi connects right away upon load, however, after a short time, say one minute, nothing loads: no web pages, can’t check emails, the vpn doesn’t connect, etc etc. However network-manager shows that the connection is still up and running. If I manually reconnect, then everything works for some time, could be a minute again or an hour, I haven’t figured out what’s the trigger, and then nothing loads again — but the wifi connection is nominally working.
I tried adding the line options ath10k_core skip_otp=y to modprobe.conf (this should be the same as adding this in /etc/default/grub as in the previous point)
blacklist a bunch of stuff, following an older discussion about the same wifi chip here — in particular, I tried blacklisting: dell_wmi mxm_wmi wmi cfg80211 mac80211 dell_laptop
disabling power save from grub (my iwconfig now shows powersave is off)
disabling IPv6 in grub
reinstalling the firmware
disabling MAC address randomization as suggested here
All of this to no avail. I have another dell with the same Manjaro i3 (same kernel, etc) but with an Intel wifi card and the wifi works just fine, so I know it’s not the wifi, although with another router the problem is less severe, i.e., the “disconnections” don’t happen so often — they still happen though.
I haven’t noticed anything special in dmesg when I look for ath10k (which is the wifi module). Any help is greatly appreciated, thanks!
You should add pcie_aspm=off in /etc/default/grub inline. file too. Next be sure that tlp have whitelisted modules:
/etc/tlp.conf
# Exclude PCI(e) devices assigned to the listed drivers from Runtime PM.
# Default when unconfigured is "amdgpu nouveau nvidia radeon" which
# prevents accidential power-on of dGPU in hybrid graphics setups.
# Separate multiple drivers with spaces.
# Default: "amdgpu mei_me nouveau nvidia pcieport radeon", use "" to disable
# completely.
RUNTIME_PM_DRIVER_BLACKLIST="mei_me nvidia pcieport "
Thanks for the reply. I have pcie_aspm=off already in /etc/default/grub together with ath10k_core.skip_otp=y. I have tried uncommenting the RUNTIME_PM_DRIVER_BLACKLIST line in /etc/tlp.conf and now it reads:
RUNTIME_PM_DRIVER_BLACKLIST=“amdgpu mei_me nouveau nvidia pcieport radeon”
===============================================================
After reviewing several other examples I have adapted and are using the following and seems to work. Slight delay of a few seconds for wireless to come back after logging back in, but it seems to works.
To adapt to other systems or drivers you will need to find the drivers module equivalents for ath10k_pci && ath10k_core and the device name wlp3s0 . @seeip link .
Opinion
This seems to work as a workaround , but for me feel like it should be unnecessary as this was working out the box and I believe is still a regression in the drivers power management.
I cant remember when setting up the machine but I think I was on ath9k and have not tried going back to it.
Okay I have switched to suspend everywhere instead of hibernate.
I don’t understand the other suggestion (WORKAROUND for crashing driver after RESUME from suspend): the problem I have is happening after fresh boot and reboot, not only after resume. Or did I misunderstand you? Thanks.
A quick update: a perfect example of this behaviour occurs when I try to update the system: pacman starts retrieving the packages but at some point in the download it freezes because, although network manager claims there is a connection, in fact nothing is being tranferred.
Another example is when I’m downloading something for example with a torrent client: the connection doesn’t last more than a few seconds — then it shows it’s connected, but nothing is being downloaded.
Thanks for the tip. I have replaced the firmware with those in the page you linked and it seems like the connection is more stable (though not as stable as that on the other laptop with the Intel chipset). I will keep testing for a few days and let you know how it goes. In the meantime any further hint or tips will be appreciated