Re: Support for QCA6174 [168c:003e]

[Michael Krupp <michaelkrupp@gmx.net>]

Hello,


I managed to get it (sort of) working with the eeprom extracted from the 
windows
driversand thefirmware from kvalo's ath10k-repo on GitHub.See more details
below.

Unfortunately I only get a bandwidth of about 2Mb/s connected to a 
54Mb/s AP.Is
this a known limitation to ath10k right now, or may there be a way to get it
working at full speed?


Also, thank You Michał for pointing me the right direction and helping 
make it
usable, at least.

--

Loading the kernel modules:

[ 1399.912769] cfg80211: World regulatory domain updated:
[ 1399.912772] cfg80211:  DFS Master region: unset
[ 1399.912772] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1399.912774] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), 
(N/A, 2000 mBm), (N/A)
[ 1399.912775] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), 
(N/A, 2000 mBm), (N/A)
[ 1399.912776] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), 
(N/A, 2000 mBm), (N/A)
[ 1399.912777] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 
160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1399.912778] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 
160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1399.912779] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), 
(N/A, 2000 mBm), (0 s)
[ 1399.912780] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), 
(N/A, 2000 mBm), (N/A)
[ 1399.912781] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), 
(N/A, 0 mBm), (N/A)
[ 1399.914523] ath10k_pci 0000:07:00.0: pci irq msi-x interrupts 8 
irq_mode 0 reset_mode 0
[ 1400.101020] ath10k_pci 0000:07:00.0: firmware: failed to load 
ath10k/cal-pci-0000:07:00.0.bin (-2)
[ 1400.101029] ath10k_pci 0000:07:00.0: Direct firmware load for 
ath10k/cal-pci-0000:07:00.0.bin failed with error -2
[ 1400.101047] ath10k_pci 0000:07:00.0: firmware: failed to load 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin (-2)
[ 1400.101051] ath10k_pci 0000:07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
[ 1400.101055] ath10k_pci 0000:07:00.0: failed to load spec board file, 
falling back to generic: -2
[ 1400.101109] ath10k_pci 0000:07:00.0: firmware: direct-loading 
firmware ath10k/QCA6174/hw3.0/board.bin
[ 1400.101125] ath10k_pci 0000:07:00.0: firmware: failed to load 
ath10k/QCA6174/hw3.0/firmware-5.bin (-2)
[ 1400.101129] ath10k_pci 0000:07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[ 1400.101133] ath10k_pci 0000:07:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[ 1400.101409] ath10k_pci 0000:07:00.0: firmware: direct-loading 
firmware ath10k/QCA6174/hw3.0/firmware-4.bin
[ 1402.218360] ath10k_pci 0000:07:00.0: qca6174 hw3.2 (0x05030000, 
0x00340aff, 168c:003e:11ad:0807 fallback) fw 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32
[ 1402.218364] ath10k_pci 0000:07:00.0: debug 0 debugfs 0 tracing 0 dfs 
0 testmode 0
[ 1402.293000] ath: EEPROM regdomain: 0x6c
[ 1402.293005] ath: EEPROM indicates we should expect a direct regpair map
[ 1402.293009] ath: Country alpha2 being used: 00
[ 1402.293011] ath: Regpair used: 0x6c
[ 1402.295714] ath10k_pci 0000:07:00.0 wlp7s0: renamed from wlan0

And connecting via wpa_supplicant:

[ 1473.897941] wlp7s0: authenticate with 00:24:fe:a8:2c:55
[ 1473.961257] wlp7s0: send auth to 00:24:fe:a8:2c:55 (try 1/3)
[ 1473.963499] wlp7s0: authenticated
[ 1473.963841] wlp7s0: associate with 00:24:fe:a8:2c:55 (try 1/3)
[ 1473.971386] wlp7s0: RX AssocResp from 00:24:fe:a8:2c:55 (capab=0x411 
status=0 aid=2)
[ 1473.974978] wlp7s0: associated
[ 1473.975015] IPv6: ADDRCONF(NETDEV_CHANGE): wlp7s0: link becomes ready

Firmware used:
     * eeprom_ar6320_3p0_NFA344a.bin
         - extracte from Windows 10 Driver via InstallShield/UniExtract
         - MD5: 956bec86376ef28615dd8493048fafb1
     * firmware-4.bin
         - 
https://github.com/kvalo/ath10k-firmware/blob/master/ath10k/QCA6174/hw3.0/firmware-4.bin

# iwconfig wlp7s0:

wlp7s0    IEEE 802.11abgn  ESSID:"[REMOVED]"
           Mode:Managed  Frequency:2.457 GHz  Access Point: 
00:24:FE:A8:2C:55
           Bit Rate=1 Mb/s   Tx-Power=20 dBm
           Retry short limit:7   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:on
           Link Quality=69/70  Signal level=-41 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:32 Missed beacon:0

# uname -a:
Linux debian 4.2.0-1-amd64 #1 SMP Debian 4.2.3-2 (2015-10-14) x86_64 
GNU/Linux


Michael

On 2015-10-26 08:20, Michal Kazior wrote:
> On 25 October 2015 at 04:57, Michael Krupp <michaelkrupp@gmx.net> wrote:
>> Hello,
>>
>> I just bought a Aspire VN7-792G, but so far I was not able to get wireless
>> working.
>> The chip reports as QCA6174 [168c:003e] and it looks like the board.bin
>> cannot be loaded:
>>
>>      Oct 25 04:27:05 debian kernel: [ 4833.902454] ath10k_pci 0000:07:00.0:
>> limiting irq mode to: 1
>>      Oct 25 04:27:05 debian kernel: [ 4833.902461] ath10k_pci 0000:07:00.0:
>> pci irq legacy interrupts 0 irq_mode 1 reset_mode 0
>>      Oct 25 04:27:05 debian kernel: [ 4834.162236] ath10k_pci 0000:07:00.0:
>> Direct firmware load for ath10k/cal-pci-0000:07:00.0.bin failed with error
>> -2
>>      Oct 25 04:27:05 debian kernel: [ 4834.162250] ath10k_pci 0000:07:00.0:
>> Direct firmware load for
>> ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
>>      Oct 25 04:27:05 debian kernel: [ 4834.162253] ath10k_pci 0000:07:00.0:
>> failed to load spec board file, falling back to generic: -2
>>      Oct 25 04:27:05 debian kernel: [ 4834.162283] ath10k_pci 0000:07:00.0:
>> Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with
>> error -2
>>      Oct 25 04:27:05 debian kernel: [ 4834.162286] ath10k_pci 0000:07:00.0:
>> could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
>>      Oct 25 04:27:07 debian kernel: [ 4836.280409] ath10k_pci 0000:07:00.0:
>> qca6174 hw3.2 (0x05030000, 0x00340aff, 168c:003e:11ad:0807 fallback) fw
>> WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32
>>      Oct 25 04:27:07 debian kernel: [ 4836.280413] ath10k_pci 0000:07:00.0:
>> debug 0 debugfs 0 tracing 0 dfs 0 testmode 0
>>      Oct 25 04:27:08 debian kernel: [ 4837.278508] ath10k_pci 0000:07:00.0:
>> suspend timed out - target pause event never came
>>      Oct 25 04:27:08 debian systemd[1]: Starting Load/Save RF Kill Switch
>> Status...
>>      Oct 25 04:27:08 debian kernel: [ 4837.367302] ath: EEPROM regdomain:
>> 0x6c
>>      Oct 25 04:27:08 debian kernel: [ 4837.367304] ath: EEPROM indicates we
>> should expect a direct regpair map
>>      Oct 25 04:27:08 debian kernel: [ 4837.367306] ath: Country alpha2 being
>> used: 00
>>      Oct 25 04:27:08 debian kernel: [ 4837.367307] ath: Regpair used: 0x6c
>>      Oct 25 04:27:08 debian kernel: [ 4837.369008] ath10k_pci 0000:07:00.0
>> wlp7s0: renamed from wlan0
>>      Oct 25 04:27:08 debian systemd[1]: Started Load/Save RF Kill Switch
>> Status.
>>
>>
>> I also tried renaming / symlinking the firmware-4.bin to firmware-5.bin, but
>> that does not seem to have any effect,
>> other than getting rid of the error message on lines 6 and 7.
> ath10k keeps backward compatibility with userspace and it has a
> fallback mechanism when trying to find firmware files. That why you
> see these "error" messages.
>
> It does load the board.bin. If it didn't find any board.bin it would
> not register a wiphy and you would not see a wireless interface on
> your system.
>
>
>> Also followed the 'qca6164 support' discussion, but still could not get it
>> working:
>>   * http://lists.infradead.org/pipermail/ath10k/2015-August/005752.html
>>
>>
>> I tried several kernel versions, starting from 4.2.0 (debian) up to latest
>> 4.2.4 (kernel.org).
>> All of them seem to include the patch mentioned in the thread i linked
>> erlier:
>> * http://lists.infradead.org/pipermail/ath10k/2015-August/005775.html
>>
>>
>> When trying to 'up' the device via 'ifconfig wlp7s0 up':
>>
>>      Oct 25 04:31:36 debian kernel: [ 5104.570092] ath10k_pci 0000:07:00.0:
>> failed to enable adaptive qcs: -11
>>      Oct 25 04:31:39 debian kernel: [ 5107.569748] ath10k_pci 0000:07:00.0:
>> could not suspend target (-11)
> This suggests you have an invalid board.bin. From the logs it looks
> like you have one of the newer qca6174 chips (hw3.2 instead of hw2.x).
> If you want it to get it working asap you'll need to look into windows
> driver for the device and extract an adequate eeprom/board file which
> matches your device's subsystem product/vendor ids.
>
>
> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k


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