qca6174 missing firmware or subsystem id?

qca6174 missing firmware or subsystem id?

[Jiří Prchal]

Hi,
I've got this miniPCIe wifi module which comes with Asus motherboard:

$lspci -vnn
02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
	Subsystem: ASUSTeK Computer Inc. QCA6174 802.11ac Wireless Network Adapter [1043:86cd]
	Flags: bus master, fast devsel, latency 0, IRQ 125
	Memory at f7000000 (64-bit, non-prefetchable) [size=2M]
	Capabilities: <access denied>
	Kernel driver in use: ath10k_pci
	Kernel modules: ath10k_pci

But I have problem to get it working. It look that wlan is there, but doesn't receive any SSID.

$ip a
4: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
     link/ether c8:ff:28:0e:5e:e1 brd ff:ff:ff:ff:ff:ff

$iw dev wlp2s0 scan
  returns nothing.

I have Ubuntu 16.04 with this kernel:
$uname -a
Linux dole 4.4.0-42-generic #62-Ubuntu SMP Fri Oct 7 23:11:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I've tried both distro and git FW (probably the same), but it still complies about firmware-5.bin. I thing there is 
missing subsystem ID in board-2.bin as I mentioned there was added some other subID 2 months ago.

$dmesg | grep ath
[    1.997246] ath10k_pci 0000:02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0
[    2.252840] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[    2.260813] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[    2.260816] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[    4.461429] ath10k_pci 0000:02:00.0: qca6174 hw3.2 (0x05030000, 0x00340aff sub 1043:86cd) fw 
WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4 bdapi 2 htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 
features wowlan,ignore-otp,no-4addr-pad
[    4.461432] ath10k_pci 0000:02:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[    4.538049] ath: EEPROM regdomain: 0x6c
[    4.538051] ath: EEPROM indicates we should expect a direct regpair map
[    4.538053] ath: Country alpha2 being used: 00
[    4.538053] ath: Regpair used: 0x6c
[    4.545712] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0

Can anybody help me, please? I'm totally new in this binaries so I don't know how to add it.
Thanks Jiri

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

Re: qca6174 missing firmware or subsystem id?

[Valo, Kalle]

Jiří Prchal <jiri.prchal@aksignal.cz> writes:

> Hi,
> I've got this miniPCIe wifi module which comes with Asus motherboard:
>
> $lspci -vnn
> 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
> 	Subsystem: ASUSTeK Computer Inc. QCA6174 802.11ac Wireless Network Adapter [1043:86cd]
> 	Flags: bus master, fast devsel, latency 0, IRQ 125
> 	Memory at f7000000 (64-bit, non-prefetchable) [size=2M]
> 	Capabilities: <access denied>
> 	Kernel driver in use: ath10k_pci
> 	Kernel modules: ath10k_pci
>
> But I have problem to get it working. It look that wlan is there, but doesn't receive any SSID.
>
> $ip a
> 4: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
>     link/ether c8:ff:28:0e:5e:e1 brd ff:ff:ff:ff:ff:ff
>
> $iw dev wlp2s0 scan
>  returns nothing.
>
> I have Ubuntu 16.04 with this kernel:
> $uname -a
> Linux dole 4.4.0-42-generic #62-Ubuntu SMP Fri Oct 7 23:11:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> I've tried both distro and git FW (probably the same), but it still
> complies about firmware-5.bin. I thing there is missing subsystem ID
> in board-2.bin as I mentioned there was added some other subID 2
> months ago.
>
> $dmesg | grep ath
> [    1.997246] ath10k_pci 0000:02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0
> [    2.252840] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
> [    2.260813] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
> [    2.260816] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2

So ignore this firmware-5.bin warning, ath10k will automatically fall
back to using firmware-4.bin. I know it's confusing, we just haven't
found a good enough way to silence this warning yet.

> [    4.461429] ath10k_pci 0000:02:00.0: qca6174 hw3.2 (0x05030000,
> 0x00340aff sub 1043:86cd) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4
> bdapi 2 htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0
> hwcrypto 1 features wowlan,ignore-otp,no-4addr-pad

Your ath10k is too old so that it doesn't print the crc32 checksum of
the board file you have so I don't know what version of the board file
you exactly have. But I just checked, the latest one from
ath10k-firmware.git should support your board with subsystem id
1043:86cd:

$ strings QCA6174/hw3.0/board-2.bin | grep 86cd
bus=pci,vendor=168c,device=003e,subsystem-vendor=1043,subsystem-device=86cdm

The checksums of the latest board file are:

FileCRC32: 6fc88fe7
FileMD5: 4807903c956dbd8b87f5d83c559c2211

You can check what you are using like this:

md5sum /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin

(Unless I made a typo in the path, but you should be able to find it
easily.)

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

Re: qca6174 missing firmware or subsystem id?

[Jiří Prchal]

On 13.10.2016 15:00, Valo, Kalle wrote:
> Jiří Prchal <jiri.prchal@aksignal.cz> writes:
>
>> Hi,
>> I've got this miniPCIe wifi module which comes with Asus motherboard:
>>
>> $lspci -vnn
>> 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
>> 	Subsystem: ASUSTeK Computer Inc. QCA6174 802.11ac Wireless Network Adapter [1043:86cd]
>> 	Flags: bus master, fast devsel, latency 0, IRQ 125
>> 	Memory at f7000000 (64-bit, non-prefetchable) [size=2M]
>> 	Capabilities: <access denied>
>> 	Kernel driver in use: ath10k_pci
>> 	Kernel modules: ath10k_pci
>>
>> But I have problem to get it working. It look that wlan is there, but doesn't receive any SSID.
>>
>> $ip a
>> 4: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
>>     link/ether c8:ff:28:0e:5e:e1 brd ff:ff:ff:ff:ff:ff
>>
>> $iw dev wlp2s0 scan
>>  returns nothing.
>>
>> I have Ubuntu 16.04 with this kernel:
>> $uname -a
>> Linux dole 4.4.0-42-generic #62-Ubuntu SMP Fri Oct 7 23:11:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>>
>> I've tried both distro and git FW (probably the same), but it still
>> complies about firmware-5.bin. I thing there is missing subsystem ID
>> in board-2.bin as I mentioned there was added some other subID 2
>> months ago.
>>
>> $dmesg | grep ath
>> [    1.997246] ath10k_pci 0000:02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0
>> [    2.252840] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
>> [    2.260813] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
>> [    2.260816] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
>
> So ignore this firmware-5.bin warning, ath10k will automatically fall
> back to using firmware-4.bin. I know it's confusing, we just haven't
> found a good enough way to silence this warning yet.

OK. Maybe temporary fix: write info message what firmware is finally loaded?

>
>> [    4.461429] ath10k_pci 0000:02:00.0: qca6174 hw3.2 (0x05030000,
>> 0x00340aff sub 1043:86cd) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4
>> bdapi 2 htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0
>> hwcrypto 1 features wowlan,ignore-otp,no-4addr-pad
>
> Your ath10k is too old so that it doesn't print the crc32 checksum of
> the board file you have so I don't know what version of the board file
> you exactly have. But I just checked, the latest one from
> ath10k-firmware.git should support your board with subsystem id
> 1043:86cd:

Should I try the newest kernel?

>
> $ strings QCA6174/hw3.0/board-2.bin | grep 86cd
> bus=pci,vendor=168c,device=003e,subsystem-vendor=1043,subsystem-device=86cdm
>
> The checksums of the latest board file are:
>
> FileCRC32: 6fc88fe7
> FileMD5: 4807903c956dbd8b87f5d83c559c2211
>
> You can check what you are using like this:
>
> md5sum /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin

Yes, I have the newest: 4807903c956dbd8b87f5d83c559c2211.

>
> (Unless I made a typo in the path, but you should be able to find it
> easily.)
>

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

Re: qca6174 missing firmware or subsystem id?

[Valo, Kalle]

Jiří Prchal <jiri.prchal@aksignal.cz> writes:

> On 13.10.2016 15:00, Valo, Kalle wrote:
>> Jiří Prchal <jiri.prchal@aksignal.cz> writes:
>>
>>> $dmesg | grep ath
>>> [    1.997246] ath10k_pci 0000:02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0
>>> [    2.252840] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
>>> [    2.260813] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
>>> [    2.260816] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
>>
>> So ignore this firmware-5.bin warning, ath10k will automatically fall
>> back to using firmware-4.bin. I know it's confusing, we just haven't
>> found a good enough way to silence this warning yet.
>
> OK. Maybe temporary fix: write info message what firmware is finally
> loaded?

That's a good idea. Developers can already see that from the "fwapi 4"
print but somekind of explanation in english should reduce the confusion
with normal users.

>>> [    4.461429] ath10k_pci 0000:02:00.0: qca6174 hw3.2 (0x05030000,
>>> 0x00340aff sub 1043:86cd) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4
>>> bdapi 2 htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0
>>> hwcrypto 1 features wowlan,ignore-otp,no-4addr-pad
>>
>> Your ath10k is too old so that it doesn't print the crc32 checksum of
>> the board file you have so I don't know what version of the board file
>> you exactly have. But I just checked, the latest one from
>> ath10k-firmware.git should support your board with subsystem id
>> 1043:86cd:
>
> Should I try the newest kernel?

That's always a good idea, for example you could try just released v4.8.
Does ubuntu still provide .debs for upstream kernels?

Or you can try backports:

https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports

>> $ strings QCA6174/hw3.0/board-2.bin | grep 86cd
>> bus=pci,vendor=168c,device=003e,subsystem-vendor=1043,subsystem-device=86cdm
>>
>> The checksums of the latest board file are:
>>
>> FileCRC32: 6fc88fe7
>> FileMD5: 4807903c956dbd8b87f5d83c559c2211
>>
>> You can check what you are using like this:
>>
>> md5sum /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
>
> Yes, I have the newest: 4807903c956dbd8b87f5d83c559c2211.

Then I suspect this is something else than board file related, but of
course I can't be 100% sure. You could also try enabling debug messages
and see if they reveal anything, for example debug_mask=0x00000432 is a
good start:

https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug

Have you verified that this is not a hardware problem? For example, does
the board work on Windows?

Also make sure that you have killed wpasupplicant, network-manager or
any other entity which might control the wireless device (very unlikely
that would cause this but better to be sure).

What channel is your AP in? Are there multiple APs in the area? This
could be also a channel problem, 'iw list' helps to investigate that (or
changing the channel on AP).

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

Re: qca6174 missing firmware or subsystem id?

[Jiří Prchal]

On 13.10.2016 16:20, Valo, Kalle wrote:
> Jiří Prchal <jiri.prchal@aksignal.cz> writes:
>
>> On 13.10.2016 15:00, Valo, Kalle wrote:
>>> Jiří Prchal <jiri.prchal@aksignal.cz> writes:
>>>
>>>> $dmesg | grep ath
>>>> [    1.997246] ath10k_pci 0000:02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0
>>>> [    2.252840] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
>>>> [    2.260813] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
>>>> [    2.260816] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
>>>
>>> So ignore this firmware-5.bin warning, ath10k will automatically fall
>>> back to using firmware-4.bin. I know it's confusing, we just haven't
>>> found a good enough way to silence this warning yet.
>>
>> OK. Maybe temporary fix: write info message what firmware is finally
>> loaded?
>
> That's a good idea. Developers can already see that from the "fwapi 4"
> print but somekind of explanation in english should reduce the confusion
> with normal users.
>
>>>> [    4.461429] ath10k_pci 0000:02:00.0: qca6174 hw3.2 (0x05030000,
>>>> 0x00340aff sub 1043:86cd) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4
>>>> bdapi 2 htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0
>>>> hwcrypto 1 features wowlan,ignore-otp,no-4addr-pad
>>>
>>> Your ath10k is too old so that it doesn't print the crc32 checksum of
>>> the board file you have so I don't know what version of the board file
>>> you exactly have. But I just checked, the latest one from
>>> ath10k-firmware.git should support your board with subsystem id
>>> 1043:86cd:
>>
>> Should I try the newest kernel?
>
> That's always a good idea, for example you could try just released v4.8.
> Does ubuntu still provide .debs for upstream kernels?

I tried 4.8.1 and it works now, but probably it worked before, because I set AP to channel 13 and it was the problem.

>
> Or you can try backports:
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports

Backports are up to 4.2.

>
>>> $ strings QCA6174/hw3.0/board-2.bin | grep 86cd
>>> bus=pci,vendor=168c,device=003e,subsystem-vendor=1043,subsystem-device=86cdm
>>>
>>> The checksums of the latest board file are:
>>>
>>> FileCRC32: 6fc88fe7
>>> FileMD5: 4807903c956dbd8b87f5d83c559c2211
>>>
>>> You can check what you are using like this:
>>>
>>> md5sum /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
>>
>> Yes, I have the newest: 4807903c956dbd8b87f5d83c559c2211.
>
> Then I suspect this is something else than board file related, but of
> course I can't be 100% sure. You could also try enabling debug messages
> and see if they reveal anything, for example debug_mask=0x00000432 is a
> good start:
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug
>
> Have you verified that this is not a hardware problem? For example, does
> the board work on Windows?
>
> Also make sure that you have killed wpasupplicant, network-manager or
> any other entity which might control the wireless device (very unlikely
> that would cause this but better to be sure).
>
> What channel is your AP in? Are there multiple APs in the area? This
> could be also a channel problem, 'iw list' helps to investigate that (or
> changing the channel on AP).
>

As I wrote the problem was channel. However it should work cause I set country to CZ.
May be I should open new thread?

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

Re: qca6174 missing firmware or subsystem id?

[Michal Kazior]

On 14 October 2016 at 10:05, Jiří Prchal <jiri.prchal@aksignal.cz> wrote:
[...]
>> What channel is your AP in? Are there multiple APs in the area? This
>> could be also a channel problem, 'iw list' helps to investigate that (or
>> changing the channel on AP).
>>
>
> As I wrote the problem was channel. However it should work cause I set
> country to CZ.
> May be I should open new thread?

You typically need to do an intersection between 2 regulatory domains:
the one that the chip was certified/calibrated (baked into eeprom)
against and the one of your system (which is supposed to be tied to
your current geolocation).

If the chip's eeprom implies you can't use ch13 and your system says
you can then you still can't use ch13.

`iw list` will output list of channels that are available and their
flags (e.g. "disabled", or "no-ir").


Michał

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

Re: qca6174 missing firmware or subsystem id?

[Jiří Prchal]

On 14.10.2016 10:25, Michal Kazior wrote:
> On 14 October 2016 at 10:05, Jiří Prchal <jiri.prchal@aksignal.cz> wrote:
> [...]
>>> What channel is your AP in? Are there multiple APs in the area? This
>>> could be also a channel problem, 'iw list' helps to investigate that (or
>>> changing the channel on AP).
>>>
>>
>> As I wrote the problem was channel. However it should work cause I set
>> country to CZ.
>> May be I should open new thread?
>
> You typically need to do an intersection between 2 regulatory domains:
> the one that the chip was certified/calibrated (baked into eeprom)
> against and the one of your system (which is supposed to be tied to
> your current geolocation).
>
> If the chip's eeprom implies you can't use ch13 and your system says
> you can then you still can't use ch13.
>
> `iw list` will output list of channels that are available and their
> flags (e.g. "disabled", or "no-ir").
>

			* 2467 MHz [12] (20.0 dBm) (no IR)
			* 2472 MHz [13] (20.0 dBm) (no IR)
I find out "no IR" means no AP mode, and I like to use it as AP. So I'm not happy cause the only free channel in my 
location is 13. The probably sold me non EU distribution. Is there any way to bake to eeprom right region?

>
> Michał
>

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