Hi,
I have a problem with Clearlinux concerning my internet connection. When I got Appimages running on my laptop and the device enters the suspens mode, I do have to restart the computer in order to regain a internet connection. When only native apps are open during a suspense period, wifi is still working.
I don’t know, if the issue is related, but every now and then Clearlinux is super slow after a start and there is no internet connection. Restarting device solves the problem.
Thats not super problematic stuff but still annoying…
Greetings
It would help if you can include info about devices that are affected, and possibly relevant output from journalctl after suspend. There may be an indication as to what devices are giving problems.
I will run journalctl the next time the issue comes up and send you the information. Thanks
Here comes the result toJournalctl:
-- Logs begin at Tue 2019-10-08 12:59:54 CEST, end at Tue 2019-10-08 13:31:55 C>
Okt 08 12:59:54 heikos tallow[431]: Journal was rotated, resetting
Okt 08 13:00:06 heikos pkexec[53383]: heiko: Executing command [USER=root] [TTY>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: firmware crashed! (guid>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: board_file api 2 bmi_id>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 h>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: firmware register dump:
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [00]: 0x05030000 0x0000>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [04]: 0x009F6377 0x0006>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [08]: 0x00000001 0x00F8>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [12]: 0x00000009 0x0000>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [16]: 0x00952CC4 0x0091>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [20]: 0x409F6377 0x0040>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [24]: 0x809FC9F4 0x0040>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [28]: 0x809F6121 0x0040>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [32]: 0x809E2601 0x0040>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [36]: 0x809DDC77 0x0040>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [40]: 0x809E6F21 0x0040>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [44]: 0x809F5C2D 0x0040>
Okt 08 13:04:05 heikos kernel: ath10k_pci 0000:02:00.0: [48]: 0x809143A7 0x0040>
I had a system with this card and it drove me nuts. Random drop disassociation with the AP and no resume from suspend. I would have to up/down the NIC and restart wpa_supplicant all the time. In short, the firmware is not well supported and problematic on Linux if you search around.
You can try getting the latest copy of the firmware: en:users:drivers:ath10k:firmware [Linux Wireless]
You can try disabling powersaving on the NIC: 16.04 - WiFi DELL XPS 13 9360 keeps disconnecting with QCA6174 802.11ac Wireless Network Adapter - Ask Ubuntu
And reviewing the file/comments in this PR: https://github.com/kvalo/ath10k-firmware/pull/3
I ended up running an Ethernet wire 
I will think about, what to do. Thanks for your help
Seems either the card is failing, or a kernel driver/firmware bug. I would check upstream (kernel) reported issues and see if they’re being worked on or not, or possibly replacing the device, if possible.
Since you advice to change the device - are there any devices clearlinux is specifically running well on?
I’m listing it as an option - in general my experiences with Atheros based wifi cards is actually really positive, they have had a long history of making decent Linux drivers and as far back as I can remember (2008) we had no issues using them.
Actually most wifi devices are nowadays well supported, with the exception being broadcom based devices due many of their cards requiring a closed-source driver.