I have an ASUS UX430UNR laptop running Linux Mint 19.1 MATE. I've been using Linux Mint as my daily driver since purchasing this laptop in mid 2018. Recently, I started encountering WIFI "slow downs", which occur intermittently some 20 minutes or so (or sometimes hours) after booting or re-booting the laptop. None of the five other Linux Mint powered computers on my LAN are experiencing the same WIFI slowdowns, so I'm assuming that it is not a router (an ASUS RT-AC88U) related problem.
Specifically, file transfers on the LAN between Linux Mint devices typically download at ~ 67 MB/sec. Broadband download speeds are typically ~20 Mb/Sec (which is just below the plan speed for the broadband service). After the laptop has been running for some time the WIFI link becomes very slow - typically under ~0.5Mb/Sec for both LAN and broadband connections. Disconnecting and reconnecting the WIFI device in Lan Manager does not fix the problem. Rebooting the laptop fixes the problem and gives me normal LAN and Broadband speeds - until it decides to fail next time.
I've looked at the output of dmesg when the fault is occurring, but don't see any errors related to the WIFI system.
I've checked the output of ifconfig for the wifi device when the fault is occurring, and there are no RX or TX errors.
I've checked the output of lspci (grep'ing for "wireless" devices, and the following info is reported for hardware and kernel driver:
- Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
- Kernel driver in use: iwlwifi
As a way of working out whether the problem was related to Linux Mint or was a hardware fault, I tried two other distros to see if the problem still existed. Ubuntu 19.04 MATE reproduced exactly the same error, as did Manjaro MATE 18.04. Based on the results of testing those other two distros, I thought that I'd worked out that it was a hardware problem .......... until I realised that the two other distros were using the same (or similar versions) of the iwlwifi kernal driver. So, now I'm back to not knowing whether it is a software, configuration, or a hardware problem.
So, can anyone provide me with some logical fault finding steps that will help to identify the cause of this problem ?