Output of "sudo journalctl | grep ath10k" after getting version 20190114-1 via 
packetmanager into Buster.

Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: firmware: 
failed to load ath10k/pre-cal-pci-0000:01:00.0.bin (-2)
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: firmware: 
failed to load ath10k/cal-pci-0000:01:00.0.bin (-2)
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: firmware: 
direct-loading firmware ath10k/QCA6174/hw3.0/firmware-6.bin
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: qca6174 
hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3370
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: kconfig 
debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: firmware ver 
RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features 
wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: firmware: 
direct-loading firmware ath10k/QCA6174/hw3.0/board-2.bin
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: failed to 
fetch board data for 
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370 
from ath10k/QCA6174/hw3.0/board-2.bin
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: firmware: 
direct-loading firmware ath10k/QCA6174/hw3.0/board.bin
Jan 21 16:59:19 debian-surface-go kernel: ath10k_pci 0000:01:00.0: board_file 
api 1 bmi_id N/A crc32 ed5f849a
Jan 21 16:59:20 debian-surface-go kernel: ath10k_pci 0000:01:00.0: Unknown 
eventid: 118809
Jan 21 16:59:20 debian-surface-go kernel: ath10k_pci 0000:01:00.0: htt-ver 3.56 
wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Jan 21 16:59:20 debian-surface-go NetworkManager[466]: <info>  
[1548086360.8720] rfkill1: found Wi
...

Version 12.0.0.722 of eeprom_ar6320_3p0_TX8_clpc.bin fixed the issue again.

best regards

Reply via email to