You are not logged in.
After updating to kernel 6.0.1 the following issue sometimes occurs:
$ journalctl -b -x -p err..alert
ath10k_pci 0000:01:00.0: could not init core (-110)
ath10k_pci 0000:01:00.0: could not probe fw (-110)These errors entail not being able to use Wifi - the system does not see the network adapter.
This driver is for the following network adapter:
$ lspci -k -s 01:00.0
01:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
Subsystem: Lenovo Qualcomm Atheros QCA9377 Wireless Network Adapter
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pciThis issue may occur after several reboots in a row.
I would be grateful for your help in resolving this issue!
Last edited by ostap (2022-10-20 11:21:09)
Offline
You may try newer kernel 6.0.2 and/or lts kernel.
Offline
Next to that: do you have a parallel windows installation? Do you use iwd?
In doubt post a complete system journal (and no "-x", it's useless spam), the timeouts (110) indicate "something went wrong for sure", but cannot hint at what went wrong.
Offline
You may try newer kernel 6.0.2 and/or lts kernel.
I am constantly updating the system, so I already have a 6.0.2 kernel, but unfortunately this did not solve the problem.
Last edited by ostap (2022-10-20 09:29:39)
Offline
Next to that: do you have a parallel windows installation? Do you use iwd?
No, I don't have a parallel Windows installation.
Yes, I am using iwd with systemd-networkd.service and systemd-resolved.service.
In doubt post a complete system journal (and no "-x", it's useless spam), the timeouts (110) indicate "something went wrong for sure", but cannot hint at what went wrong.
Unfortunately, I was not able to repeat this error again, so I can only provide the full dmesg output that I received a few days ago when I noticed this error: https://pastebin.com/iETy7AZP
Last edited by ostap (2022-10-20 10:01:09)
Offline
https://wiki.archlinux.org/title/Iwd#Re … after_boot is known to cause this.
Offline
https://wiki.archlinux.org/title/Iwd#Re … after_boot is known to cause this.
Edited iwd.service and executed daemon-reload. I hope this will solve this problem.
Thanks for the help!
Offline