On boot I get the following error message on my Acer Swift 3 with Arch Linux x64 Kernel 4.10-rc1: [ 12.334746] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 This file indeed doesn't exist and is not in the current git of linux-firmware. However, the wireless works perfectly fine, so I'm not sure if this file maybe shouldn't be loaded in the first place or if the log message should be downgraded to info. I tried copying the firmware-5.bin from the hw2.1 directory but then the driver fails to load completely. Hardware (from lspci): 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) complete output from "dmesg | grep ath10k": [ 11.798974] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 12.076426] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2 [ 12.076468] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2 [ 12.077509] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [ 12.077519] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [ 12.092601] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 11ad:0807 [ 12.092609] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0 [ 12.094929] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 12.161235] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 14.321986] ath10k_pci 0000:02:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 14.414396] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
This should be now fixed starting from v4.11-rc1: ath10k: silence firmware file probing warnings https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f5bcfe93315d75da4cc46bd30b536966559359a
yep, the warning is gone in 4.11.2, thanks.