Your Wifi card is a Qualcomm Atheros Device [168c:0042] (rev 31). There are many bug reports you can review to find similar problem and recommended solution(s):
In addition to the bug reports, there are problems and solutions posted on various forums:
I have a similar card revealed using lspci -nnv
:
3c:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535]
Flags: bus master, fast devsel, latency 0, IRQ 136
Memory at dd200000 (64-bit, non-prefetchable) [size=2M]
Capabilities: <access denied>
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
The same driver ath10k_pci
is used as your card. So "one driver fixes all" approach is used for bugs with your card and mine. The one bug I've been following has been fixed but it took two years to reach upstream:
To narrow down which bug effected me most accurately I used dmesg | grep ath10k
:
[ 3.973278] ath10k_pci 0000:3c:00.0: enabling device (0000 -> 0002)
[ 3.974377] ath10k_pci 0000:3c:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 4.253816] ath10k_pci 0000:3c:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:3c:00.0.bin failed with error -2
[ 4.253822] ath10k_pci 0000:3c:00.0: Direct firmware load for ath10k/cal-pci-0000:3c:00.0.bin failed with error -2
[ 4.254750] ath10k_pci 0000:3c:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[ 4.254752] ath10k_pci 0000:3c:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 4.255179] ath10k_pci 0000:3c:00.0: firmware ver WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 4d458559
[ 4.318661] ath10k_pci 0000:3c:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7
[ 4.885699] ath10k_pci 0000:3c:00.0: Unknown eventid: 90118
[ 4.886304] ath10k_pci 0000:3c:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 4.987424] ath10k_pci 0000:3c:00.0 wlp60s0: renamed from wlan0
[ 5.820647] ath10k_pci 0000:3c:00.0: Unknown eventid: 90118
Believe it or not this is today's dmesg
after the bug is fixed. The log with the bug can be viewed at the bug report just linked.
I wish there was a one-line answer I could have posted for you but at this point I can only point you in the right direction for doing your homework.