You are not logged in.
Hey there, I have some troubles in connecting to wireless network during archlinux installation.
# uname -a
Linux archiso 5.11.2-arch1-1 #1 SMP PREEMPT Fri, 26 Feb 2021 18:26:41 +0000 x86_64 GNU/Linux
So, the problem is, that iwctl shows no devises in device list output. However there are wlan0 device in ip link output:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 10:63:c8:d3:91:3d brd ff:ff:ff:ff:ff:ff
My lspci -k output for network configuration is:
01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
Subsystem: Lite-On Communications Inc Device 0847
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci, wl
I guess, that is something wrong with aht10k driver. When I tried
ip link set wlan0 up
I received this:
[ 554.394780] ath10k_pci 0000:01:00.0: failed to setup htt: -110
[ 554.467320] ath10k_pci 0000:01:00.0: Could not init core: -110
There also were these messages in dmesg output after system boot:
# dmesg | grep ath10k
[ 12.436565] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 12.780496] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 11ad:0847
[ 12.780502] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
[ 12.780842] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 90eebefb
[ 12.862568] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=11ad,subsystem-device=0847 from ath10k/QCA6174/hw3.0/board-2.bin
[ 12.864035] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a
[ 12.955954] ath10k_pci 0000:01:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 16.154468] ath10k_pci 0000:01:00.0: wmi command 16389 timeout, restarting hardware
[ 19.354468] ath10k_pci 0000:01:00.0: wmi command 69633 timeout, restarting hardware
[ 19.354473] ath10k_pci 0000:01:00.0: already restarting
[ 19.354475] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 19.428642] ath10k_pci 0000:01:00.0: cannot restart a device that hasn't been started
[ 22.981132] ath10k_pci 0000:01:00.0: wmi command 16387 timeout, restarting hardware
[ 22.981137] ath10k_pci 0000:01:00.0: already restarting
[ 22.981139] ath10k_pci 0000:01:00.0: failed to enable PMF QOS: -11
[ 26.181153] ath10k_pci 0000:01:00.0: wmi command 16389 timeout, restarting hardware
[ 26.181163] ath10k_pci 0000:01:00.0: already restarting
[ 29.381147] ath10k_pci 0000:01:00.0: wmi command 69633 timeout, restarting hardware
[ 29.381153] ath10k_pci 0000:01:00.0: already restarting
[ 29.381155] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 32.794951] ath10k_pci 0000:01:00.0: wmi command 16387 timeout, restarting hardware
[ 32.794961] ath10k_pci 0000:01:00.0: already restarting
[ 32.794965] ath10k_pci 0000:01:00.0: failed to enable PMF QOS: -11
[ 35.994900] ath10k_pci 0000:01:00.0: wmi command 16389 timeout, restarting hardware
[ 35.994911] ath10k_pci 0000:01:00.0: already restarting
[ 39.194911] ath10k_pci 0000:01:00.0: wmi command 69633 timeout, restarting hardware
[ 39.194925] ath10k_pci 0000:01:00.0: already restarting
[ 39.194928] ath10k_pci 0000:01:00.0: could not suspend target (-11)
Do you have any ideas how to fix it?
Last edited by Roma004 (2021-05-10 11:28:02)
Offline
The same situation with already installed system (boot with another ssd). In other two laptops network works correctly. It seems to me, it is only a driver issue.
Offline
Try
iwctl
station wlan0 scan
station wlan0 get-networks
and see if you can still connect to a Network.
Else there might be an issue with your iso boot device. Are you using a verified signature?
Offline
Try
iwctl station wlan0 scan station wlan0 get-networks
and see if you can still connect to a Network.
Else there might be an issue with your iso boot device. Are you using a verified signature?
Thank you for your reply!
However, It seems to me, I've found a solution (at least temporary) to this problem on this page: https://bbs.archlinux.org/viewtopic.php?id=208874
I guess, that is something wrong with the driver for only that wifi card. So I've just ovewrited board.bin and firmware-4.bin files, as it was suggested there, and, WOW, it works now!
I will mark this topic as solved, in a nearest time.
Thank you again!
Offline