hey,
i got this router today and im a bit worried about some kernel messages:
[ 9.772366] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/fwcfg-ahb-a000000.wifi.txt failed with error -2
[ 9.772410] ath10k_ahb a000000.wifi: Falling back to user helper
[ 9.818720] firmware ath10k!fwcfg-ahb-a000000.wifi.txt: firmware_loading_store: map pages failed
[ 9.824623] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/ct-firmware-5.bin failed with error -2
[ 9.826609] ath10k_ahb a000000.wifi: Falling back to user helper
[ 9.902183] firmware ath10k!QCA4019!hw1.0!ct-firmware-5.bin: firmware_loading_store: map pages failed
[ 9.902641] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/ct-firmware-2.bin failed with error -2
[ 9.910423] ath10k_ahb a000000.wifi: Falling back to user helper
[ 9.965281] firmware ath10k!QCA4019!hw1.0!ct-firmware-2.bin: firmware_loading_store: map pages failed
[ 9.965618] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/firmware-6.bin failed with error -2
[ 9.973572] ath10k_ahb a000000.wifi: Falling back to user helper
[ 10.044663] firmware ath10k!QCA4019!hw1.0!firmware-6.bin: firmware_loading_store: map pages failed
should i be worried? because wlan seems to work... haven't tested the speed so far.
No, don't worry about these messages. The ath10k-ct driver is trying to load it own "preferred" -ct firmwares first. However the driver uses the recommended request_firmware_*() method and is very verbose.
This could be caused by a special device on your network and your network configuration.
From what I can tell, it's because of this check:
At first glance, it looks like there is no entry for the IPQ4019/QCA4019 device in the list. But there is a the twist: The QCA4019 dev-id is "0" (which is shared with WCN3990), so this is getting confusing.
Ignore the rate-override warning, you don't need to override rates for any normal use case anyway. I'll comment out that warning from my driver in upcoming releases.
Please do report the crashes on the ath10k-ct project page so I can track them. I should be releasing new firmware images for openwrt soon and hopefully that will resolve some of it at least.