Re: qca6164 support

From: Ben Greear <greearb@candelatech.com>
To: Anish Tondwalkar <twilightrook@gmail.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: qca6164 support
Date: Mon, 10 Aug 2015 16:43:37 -0700	[thread overview]
Message-ID: <55C93729.90100@candelatech.com> (raw)
In-Reply-To: <CALZPV0CNE8XzV5NKjv4s+f21WguB6EOQ2WMMteAEMfJKW2caRQ@mail.gmail.com>

On 08/10/2015 04:05 PM, Anish Tondwalkar wrote:
> 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'.

You have a bad supplicant config file.  This is not directly related to any
problems you might be having with the firmware.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k