I have a Lenovo Z70. Looks like it is using the Atheros QCA6174 and the ath10k drivers.
dmesg | grep ath10k
[ 9.683379] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
[ 9.941660] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[ 9.945437] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
[ 9.945441] ath10k_pci 0000:03:00.0: failed to load spec board file, falling back to generic: -2
[ 11.236163] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff, 168c:003e:17aa:3044 fallback) fw WLAN.RM.1.1-00141 api 5 htt 3.1 wmi 4 cal otp max_sta 32
[ 11.236166] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 11.317749] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
I do get a wireless connection but it is weak and very slow. It’s usable, except for uploading, so I don’t want to do anything to make it stop working completely. I was looking here - https://wireless.wiki.kernel.org/en/users/drivers/ath10k/firmware and it looks like there is a firmware update for the QCA6174. Would this help? Like I said, I don’t want to make the problem worse, not knowing what I’m doing.
I may have done it wrong but after putting those files in the ath10k folder, I lost my wifi completely. I put the old ones back and got the slow wifi again. This is with the files I downloaded:
p, li { white-space: pre-wrap; }
~$ dmesg | grep ath10k
[ 4.563912] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
[ 4.768814] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[ 4.772831] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
[ 4.772837] ath10k_pci 0000:03:00.0: failed to load spec board file, falling back to generic: -2
[ 4.775041] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[ 4.775045] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
[ 4.775052] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-4.bin failed with error -2
[ 4.775053] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-4.bin': -2
[ 4.775058] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-3.bin failed with error -2
[ 4.775059] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-3.bin': -2
[ 4.775064] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware-2.bin failed with error -2
[ 4.775065] ath10k_pci 0000:03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw2.1/firmware-2.bin': -2
[ 4.775070] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/firmware.bin failed with error -2
[ 4.775072] ath10k_pci 0000:03:00.0: could not fetch firmware (-2)
[ 4.775076] ath10k_pci 0000:03:00.0: could not fetch firmware files (-2)
[ 4.775077] ath10k_pci 0000:03:00.0: could not probe fw (-2)
and this is when I put the old ones back (just curious, why is is renaming wlan0? :
~$ dmesg | grep ath10k
[ 4.600500] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
[ 4.810707] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[ 4.822338] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
[ 4.822344] ath10k_pci 0000:03:00.0: failed to load spec board file, falling back to generic: -2
[ 6.385179] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff, 168c:003e:17aa:3044 fallback) fw WLAN.RM.1.1-00141 api 5 htt 3.1 wmi 4 cal otp max_sta 32
[ 6.385184] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 6.476809] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
I’ve seen a lot of people having trouble with this on Lenovos but I thought it was supposed to be working in the 4.2 kernel.