Got it working! Sort of! I asked vvanpo for his firmware, and with
that I can see the wireless device after I boot. But I still can't
connect to any networks or see them.
Here's the firmware:
https://github.com/atondwal/ath10k-firmware/commit/88fca85ef59d708b9874e5b7885416b58aef9ee7
[ 66.267355] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:0041:17aa:3545.bin failed with
error -2
[ 66.267358] ath10k_pci 0000:03:00.0: Falling back to user helper
[ 126.315169] ath10k_pci 0000:03:00.0: failed to load spec board
file, falling back to generic: -11
[ 126.349113] This the patched kernel -Anish
[ 127.514569] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
0x003405ff, 168c:0041:17aa:3545 fallback) fw atheros-12.0.0.102-fw api
5 htt-ver 3.25 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
features
[ 127.514574] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 0
dfs 0 testmode 0
[ 127.593699] ath: EEPROM regdomain: 0x6c
[ 127.593702] ath: EEPROM indicates we should expect a direct regpair map
[ 127.593703] ath: Country alpha2 being used: 00
[ 127.593704] ath: Regpair used: 0x6c
[ 127.605414] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
~ ❯❯❯ sudo iwconfig wlp3s0 essid wahoo ap any
~ ❯❯❯ sudo iwconfig wlp3s0
wlp3s0 IEEE 802.11abgn ESSID:"wahoo"
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
~ ❯❯❯ sudo iwconfig wlp3s0 essid wahoo ap any
~ ❯❯❯ sudo dhcpcd wlp3s0
wlp3s0: adding address fe80::1851:cd3e:2790:ed4f
wlp3s0: starting wpa_supplicant
wlp3s0: failed to start wpa_supplicant
wlp3s0: Successfully initialized wpa_supplicant
Line 1182: unknown EAP method 'SIM'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1182: failed to parse eap 'SIM'.
Line 1185: failed to parse network block.
Line 1192: unknown EAP method 'PSK'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1192: failed to parse eap 'PSK'.
Line 1196: failed to parse network block.
Line 1228: unknown EAP method 'IKEV2'
You may need to add support for this EAP method during wpa_supplicant
build time configuration.
See README for more information.
Line 1228: failed to parse eap 'IKEV2'.
Line 1231: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant/wpa_supplicant.conf'.
wlp3s0: if_up: Operation not possible due to RF-kill
wlp3s0: waiting for carrier
timed out
dhcpcd exited
On Mon, Aug 10, 2015 at 12:04 PM, Anish Tondwalkar
<twilightrook at gmail.com> wrote:
> kernel is definitely patched...
>
>
> [ 5.544894] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [ 5.544897] ath10k_pci 0000:03:00.0: Falling back to user helper
>
>
> [...]
>
> [ 59.341227] r8169 0000:02:00.0 enp2s0: link down
> [ 65.621229] This the patched kernel -Anish
> [ 66.765815] ath10k_pci 0000:03:00.0: firmware crashed! (uuid
> 68f55675-f554-45a8-8c9f-eecac09a5cb9)
> [ 66.765868] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
> 0x003405ff, 168c:0041:17aa:3545) fw killer-n1525-fw api 5 htt-ver 0.0
> wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features
> [ 66.765871] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 0
> dfs 0 testmode 0
> [ 66.767894] ath10k_pci 0000:03:00.0: firmware register dump:
> [ 66.767920] ath10k_pci 0000:03:00.0: [00]: 0x05010000 0x000015B3
> 0x000A012D 0x00955B31
> [ 66.767942] ath10k_pci 0000:03:00.0: [04]: 0x000A012D 0x00060330
> 0x00000016 0x84785006
> [ 66.767966] ath10k_pci 0000:03:00.0: [08]: 0x00000000 0x00400000
> 0x00400600 0x00000001
> [ 66.767989] ath10k_pci 0000:03:00.0: [12]: 0x00000009 0x00000000
> 0x00931C61 0x00931C7D
> [ 66.768010] ath10k_pci 0000:03:00.0: [16]: 0x0096BDBC 0x009286B6
> 0x00931E74 0x00000000
> [ 66.768032] ath10k_pci 0000:03:00.0: [20]: 0x400A012D 0x0040E2B0
> 0x00955A00 0x00404590
> [ 66.768054] ath10k_pci 0000:03:00.0: [24]: 0x809287D9 0x0040E310
> 0x7A508DF8 0xC00A012D
> [ 66.768076] ath10k_pci 0000:03:00.0: [28]: 0x809288D7 0x0040E340
> 0x00000000 0xFFF08040
> [ 66.768098] ath10k_pci 0000:03:00.0: [32]: 0x809290FE 0x0040E360
> 0x00400000 0x00400600
> [ 66.768120] ath10k_pci 0000:03:00.0: [36]: 0x80929205 0x0040E380
> 0x00000000 0x00400600
> [ 66.768144] ath10k_pci 0000:03:00.0: [40]: 0x40928024 0x0040E3B0
> 0x0040D3D0 0x0040D3D0
> [ 66.768166] ath10k_pci 0000:03:00.0: [44]: 0x00000000 0x0040E3D0
> 0x009BB001 0x00040020
> [ 66.768188] ath10k_pci 0000:03:00.0: [48]: 0x00401BF0 0x00000001
> 0x00404B9C 0x00400000
> [ 66.768211] ath10k_pci 0000:03:00.0: [52]: 0x40928024 0x0040E3B0
> 0x0040D3D0 0x0040D3D0
> [ 66.768233] ath10k_pci 0000:03:00.0: [56]: 0xF2D10700 0xE4B458C2
> 0x85CC6B13 0xE8728F30
> [ 67.764773] ath10k_pci 0000:03:00.0: failed to receive control
> response completion, polling..
> [ 68.765592] ath10k_pci 0000:03:00.0: ctl_resp never came in (-110)
> [ 68.765667] ath10k_pci 0000:03:00.0: failed to connect to HTC: -110
> [ 68.846102] ath10k_pci 0000:03:00.0: could not init core (-110)
> [ 68.846156] ath10k_pci 0000:03:00.0: could not probe fw (-110)
> [ 68.858977] ath10k_pci 0000:03:00.0: cannot restart a device that
> hasn't been started
--
Anish
Q: Why is this email two sentences or less?
A: http://two.sentenc.es