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. 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. Slight delay of a few seconds for wireless to come back after logging back in, but it seems to works. PROPER SYSTEMD SERVICE UNITS DIRS are /usr/lib/systemd/* and after enabling them these creating symling to /etc/systemd/*Īfter reviewing several other examples I have adapted and are using the following and seems to work.
UPDATE WORKAROUND for crashing driver after RESUME from suspend based on post WORKAROUND CRASH FIRMWARE sudo rmmod ath10k_core ath10k_pci & sudo modprobe ath10k_core ath10k_pci ath10k_pci 0000:03:00.0: device successfully recovered ieee80211 phy0: Hardware restart was requested
ath10k_pci 0000:03:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0 wlp3s0: deauthenticating from f4:bf:80:67:e4:b6 by local choice (Reason: 3=DEAUTH_LEAVING) I recently LOGOUT from current session SDDM and after while LOGIN again. If you using TLP be sure that RUNTIME_PM_DRIVER_BLACKLIST is uncommented. Sample results: ath10k_pci 0000:03:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877ĭetails about skip_otp parm: skip_otp:Skip otp failure for calibration in testmode (bool)įlag pcie_aspm=off disabled power saving for all PCIE against issues with it.
There are available simple workaround solutions for now. Sadly firmware developers did not resolved all minor/major issues for Linux and sometimes WLAN just does not works, or in dmesg report lots of pcieport errors. Most new brand notebooks have IOT chip modules branded Qualcomm/Atheros or sub brand Killer Networks.