Bug 108791 - [ath10k_pci] Killer 1535 card doesn't initalise
Summary: [ath10k_pci] Killer 1535 card doesn't initalise
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-02 18:50 UTC by Mike Lothian
Modified: 2016-06-28 13:30 UTC (History)
3 users (show)

See Also:
Kernel Version: 4.4-rc2
Tree: Mainline
Regression: No


Attachments
dmesg (479.62 KB, application/octet-stream)
2015-12-02 18:50 UTC, Mike Lothian
Details
save as board-2.bin (7.93 KB, application/octet-stream)
2015-12-04 16:57 UTC, Mike Lothian
Details

Description Mike Lothian 2015-12-02 18:50:10 UTC
Created attachment 196351 [details]
dmesg

My card doesn't initialise I've used the recommended firmware from:

http://www.killernetworking.com/support/knowledge-base/17-linux/20-killer-wireless-ac-in-linux-ubuntu-debian

and I've also tried the firmware from:

https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0

I'm attaching the dmesg of both loads

3c:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
Comment 1 Mike Lothian 2015-12-04 16:54:33 UTC
I managed to get it working on linux-next using the firmware bin from Windows, I guess it needs adding to linux-firmware
Comment 2 Mike Lothian 2015-12-04 16:57:41 UTC
Created attachment 196391 [details]
save as board-2.bin
Comment 3 Mike Lothian 2015-12-04 16:58:39 UTC
I still had issues getting this to work on Linus's tree & amdgpu-powerplay branch
Comment 4 hawking 2015-12-26 17:33:51 UTC
Just confirming the same problem:

lspci -v

    01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
            Subsystem: Foxconn International, Inc. Device e09d
            Flags: bus master, fast devsel, latency 0, IRQ 125
            Memory at a1000000 (64-bit, non-prefetchable) [size=2M]
            Capabilities: <access denied>
            Kernel driver in use: ath10k_pci
            Kernel modules: ath10k_pci

lspci -nn

    01:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)


dmesg | grep ath10k

    [   14.321291] ath10k_pci 0000:01:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
    [   14.480823] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2
    [   14.481732] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:105b:e09d.bin failed with error -2
    [   14.481735] ath10k_pci 0000:01:00.0: failed to load spec board file, falling back to generic: -2
    [   14.482301] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
    [   14.482304] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
    [   16.616042] ath10k_pci 0000:01:00.0: qca6174 hw3.2 (0x05030000, 0x00340aff, 168c:003e:105b:e09d fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32
    [   16.616045] ath10k_pci 0000:01:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
    [   18.777065] ath10k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
    [   24.006346] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
    [   27.005853] ath10k_pci 0000:01:00.0: could not suspend target (-11)
    [   35.262376] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
    [   38.261964] ath10k_pci 0000:01:00.0: could not suspend target (-11)
Comment 5 hawking 2015-12-31 23:54:19 UTC
Thanks to the comment by Mike Lothian above, the the windows bin linked in comment 2 appears to make the wireless work in Fedora-23 with kernel version 4.2.8 Release 300.fc23, though it required replacing /lib/firmware/ath10k/QCA6174/hw3.0/board.bin itself.
Comment 6 Mike Lothian 2016-06-28 13:30:34 UTC
The default firmware in linux-firmware works now

Note You need to log in before you can comment on or make changes to this bug.