Hi guys, after happily using Manjaro for a couple months I encountered a wireless connection problem. A few days ago I updated the system. After reboot, the wireless connection was gone.
Symptom
Output of ip link show
. There is no network interface for the wireless adaptor:
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
2: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether b8:85:84:a0:02:1c brd ff:ff:ff:ff:ff:ff
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:a0:54:06:8e brd ff:ff:ff:ff:ff:ff
rfkill list all
doesn't show the network device:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
System information
Kernel version(output of cat /proc/version
)
Linux version 4.14.78-1-MANJARO (builduser@development) (gcc version 8.2.1 20180831 (GCC)) #1 SMP PREEMPT Sun Oct 21 07:57:51 UTC 2018
Output of lspci -knnvvv | grep -iA2 net
04:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31)
Subsystem: Dell QCA9377 802.11ac Wireless Network Adapter [1028:1810]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
--
05:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E2500 Gigabit Ethernet Controller [1969:e0b1] (rev 10)
Subsystem: Dell Killer E2500 Gigabit Ethernet Controller [1028:0858]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Output of inxi -F
, note there is no IF for the wireless adaptor:
Network: Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter driver: ath10k_pci
Device-2: Qualcomm Atheros Killer E2500 Gigabit Ethernet driver: alx
IF: enp5s0 state: down mac: b8:85:84:a0:02:1c
Device-3: Qualcomm Atheros type: USB driver: btusb
IF-ID-1: docker0 state: down mac: 02:42:a0:54:06:8e
Debugging
I took some suggestions from [Solved] QCA9377 (ath10k) wireless not working and updated my firmware from kvalo/ath10k-firmware. That didn't solve the problem. I gathered some log information below:
Some output of journalctl -b
, from the last line it looks like the firmware was actually loaded successfully, but I'm not sure if the preceeding error is related:
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: AER: Multiple Corrected error received: id=00e2
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e2(Receiver ID)
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: device [8086:a292] error status/mask=00000081/00002000
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: [ 0] Receiver Error (First)
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: [ 7] Bad DLLP
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: AER: Multiple Corrected error received: id=00e2
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: can't find device of ID00e2
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: AER: Multiple Corrected error received: id=00e2
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e2(Receiver ID)
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: device [8086:a292] error status/mask=00000001/00002000
Oct 27 12:10:24 zhengyang-pc kernel: pcieport 0000:00:1c.2: [ 0] Receiver Error (First)
Oct 27 12:10:24 zhengyang-pc kernel: ath10k_pci 0000:04:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:04:00.0.bin failed with error -2
Oct 27 12:10:24 zhengyang-pc kernel: ath10k_pci 0000:04:00.0: Direct firmware load for ath10k/cal-pci-0000:04:00.0.bin failed with error -2
Oct 27 12:10:24 zhengyang-pc kernel: ath10k_pci 0000:04:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 1028:1810
Oct 27 12:10:24 zhengyang-pc kernel: ath10k_pci 0000:04:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Oct 27 12:10:24 zhengyang-pc kernel: ath10k_pci 0000:04:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
Output of dmesg | grep -i error
[ 0.420901] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
[ 0.420910] ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170728/psparse-550)
[ 0.421143] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
[ 0.421149] ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170728/psparse-550)
[ 0.707860] RAS: Correctable Errors collector initialized.
[ 8.257954] pcieport 0000:00:1c.2: AER: Multiple Corrected error received: id=00e2
[ 8.257973] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e2(Receiver ID)
[ 8.258103] pcieport 0000:00:1c.2: device [8086:a292] error status/mask=00000081/00002000
[ 8.258192] pcieport 0000:00:1c.2: [ 0] Receiver Error (First)
[ 8.258298] pcieport 0000:00:1c.2: AER: Multiple Corrected error received: id=00e2
[ 8.291949] pcieport 0000:00:1c.2: AER: Multiple Corrected error received: id=00e2
[ 8.291968] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e2(Receiver ID)
[ 8.292062] pcieport 0000:00:1c.2: device [8086:a292] error status/mask=00000001/00002000
[ 8.292133] pcieport 0000:00:1c.2: [ 0] Receiver Error (First)
[ 8.411251] ath10k_pci 0000:04:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:04:00.0.bin failed with error -2
[ 8.411291] ath10k_pci 0000:04:00.0: Direct firmware load for ath10k/cal-pci-0000:04:00.0.bin failed with error -2
I appreciate very much if anyone can provide advice on fixing/debugging this problem!
2018-10-27 Updates
See @philm 's comments below, downgrading the firmware of the network adaptor solved my issue. Thanks!!