Re: ath10k-firmware: QCA6174A hw3.2: Add Killer Networking/Surface Go specific board

Blaž Hrastnik blaz at mxxn.io
Fri Aug 21 03:17:52 EDT 2020


Hi Kalle, are you still taking board file submissions? I saw that no newly submitted board files were merged in 2020.

Blaž

On Thu, 2 Apr 2020, at 04:49, Blaž Hrastnik wrote:
> * description for what hardware this is:
> 
>   - it is a QCA6174A based radio used for wi-fi in Surface Go and 
> various other laptops
> 
> * origin of the board file (did you create it yourself or where you
>   downloaded)
> 
>   - Taken from Killer Networking's website:
>     
> https://support.killernetworking.com/knowledge-base/installing-the-killer-wireless-ac-1535-in-steamos/
> 
>     https://support.killernetworking.com/K1535_Debian/board.bin
> 
> * ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
> 
>   - QCA6174 hw3.2
> 
>     + 
> bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370
>       sha256sum:
>       e79b80e2243c62f41fbaf1cc92845cefb11019b0a6d1c91488cf43fd63dcf85c
> 
> Some more information:
> 
> It's been a very common workaround that's spread out by word of mouth. I'm not
> sure why nobody upstreamed it yet.
> 
> https://github.com/linux-surface/linux-surface/wiki/Surface-Go
> 
> Here's the output from the driver without the board:
> 
> [ 28.517788] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 
> irq_mode 0 reset_mode 0
> [ 28.797409] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 
> chip_id 0x00340aff sub 168c:3370
> [ 28.797414] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 
> 1 dfs 0 testmode 0
> [ 28.798350] ath10k_pci 0000:01:00.0: firmware ver 
> WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 
> fd869beb
> [ 28.869124] 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
> [ 28.869475] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 
> ed5f849a
> [ 28.948849] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
> [ 28.967687] ath10k_pci 0000:01:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 
> cal otp max-sta 32 raw 0 hwcrypto 1
> [ 32.111815] ath10k_pci 0000:01:00.0: wmi command 16389 timeout, 
> restarting hardware
> [ 35.183798] ath10k_pci 0000:01:00.0: wmi command 69633 timeout, 
> restarting hardware
> [ 35.183803] ath10k_pci 0000:01:00.0: could not suspend target (-11)
> [ 35.287491] ath10k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
> [ 35.303832] ath10k_pci 0000:01:00.0: cannot restart a device that 
> hasn't been started
> [ 35.579498] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
> [ 38.767832] ath10k_pci 0000:01:00.0: wmi command 16387 timeout, 
> restarting hardware
> [ 38.767840] ath10k_pci 0000:01:00.0: failed to enable PMF QOS: -11
> [ 38.768373] ath10k_pci 0000:01:00.0: could not suspend target (-108)
> [ 38.849525] ath10k_pci 0000:01:00.0: cannot restart a device that 
> hasn't been started
> [ 39.090593] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
> [ 42.351960] ath10k_pci 0000:01:00.0: htt version request timed out
> [ 42.351966] ath10k_pci 0000:01:00.0: failed to setup htt: -110
> [ 42.433909] ath10k_pci 0000:01:00.0: Could not init core: -110
> [ 42.662892] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
> [ 45.935887] ath10k_pci 0000:01:00.0: failed to ping firmware: -110
> [ 45.935896] ath10k_pci 0000:01:00.0: failed to reset rx filter: -110
> [ 46.016938] ath10k_pci 0000:01:00.0: Could not init core: -110
> [ 56.238713] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
> [ 59.503838] ath10k_pci 0000:01:00.0: wmi command 16387 timeout, 
> restarting hardware
> [ 59.503845] ath10k_pci 0000:01:00.0: failed to enable PMF QOS: -11
> [ 59.504257] ath10k_pci 0000:01:00.0: could not suspend target (-108)
> [ 59.584865] ath10k_pci 0000:01:00.0: cannot restart a device that 
> hasn't been started
> [ 59.810940] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
> [ 62.831868] ath10k_pci 0000:01:00.0: htt version request timed out
> [ 62.831874] ath10k_pci 0000:01:00.0: failed to setup htt: -110
> [ 62.914010] ath10k_pci 0000:01:00.0: Could not init core: -110
> 
> Here's the output after the board files are swapped:
> 
> [ 22.265640] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 
> irq_mode 0 reset_mode 0
> [ 22.556869] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 
> chip_id 0x00340aff sub 168c:3370
> [ 22.556875] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 
> 1 dfs 0 testmode 0
> [ 22.557773] ath10k_pci 0000:01:00.0: firmware ver 
> WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 
> fd869beb
> [ 22.630144] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 
> 70c38a29
> [ 22.722890] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
> [ 22.742657] ath10k_pci 0000:01:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 
> cal otp max-sta 32 raw 0 hwcrypto 1
> [ 22.996371] ath10k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
> [ 24.535624] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
> 
> Here's some more discussion on how the Killer board was found:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1651779#c1
> 
> It's likely that this also fixes wifi on Surface Laptop 3 AMD since users have
> been using an identical workaround.
> 
> Note: It's also recommended to enable ignore-otp for this board. Not sure if it
> actually helps or not though.
> 
> Attachments:
> * board.bin



More information about the ath10k mailing list