QCA6174 hw2.1 on Clevo P750ZM

[Alexandre Maloteaux]

Hi Michal

It is finally working with irq_mode=1 and kvalo-master . The output is
below; However it takes a lot of time to load/unload the device with
successive firmwares. I ll try to find a solution for this on my own.
Is it better to blacklist some module as you said earlier or create a
modprobe.d rule with irq_mode=1 ?
Thanks a lot for knowledge and time shared !!!!!!

output :

[  315.417575] ath10k_pci 0000:06:00.0: pci irq legacy interrupts 0
irq_mode 1 reset_mode 0
[  315.661404] ath10k_pci 0000:06:00.0: Direct firmware load for
ath10k/cal-pci-0000:06:00.0.bin failed with error -2
[  315.661406] ath10k_pci 0000:06:00.0: Falling back to user helper
[  375.755105] ath10k_pci 0000:06:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2
[  375.755107] ath10k_pci 0000:06:00.0: Falling back to user helper
[  435.850288] ath10k_pci 0000:06:00.0: failed to load spec board file,
falling back to generic: -11
[  435.850328] ath10k_pci 0000:06:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[  435.850330] ath10k_pci 0000:06:00.0: Falling back to user helper
[  495.945454] ath10k_pci 0000:06:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-5.bin': -11
[  497.140018] ath10k_pci 0000:06:00.0: qca6174 hw2.1 (0x05010000,
0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4
htt-ver 3.0 wmi-op 4 htt-op 3 cal otp max-sta 32 features
\xffffff80\xffffffd4\xffffffa8\xfffffff9\xffffff88\xffffffff\xffffffff
[  497.140021] ath10k_pci 0000:06:00.0: debug 1 debugfs 1 tracing 1 dfs
0 testmode 0
[  497.218423] ath: EEPROM regdomain: 0x6c
[  497.218426] ath: EEPROM indicates we should expect a direct regpair map
[  497.218427] ath: Country alpha2 being used: 00
[  497.218427] ath: Regpair used: 0x6c
[  497.222363] ath10k_pci 0000:06:00.0 wlp6s0: renamed from wlan0
[ 1349.087696] ath10k_pci 0000:06:00.0: no channel configured; ignoring
frame(s)!

Best Regards


On 07/23/2015 11:38 AM, Alexandre Maloteaux wrote:
> Yes sorry i reposted on the mailing list as soon as  i noticed the
> mistake :)
>
> On 07/23/2015 11:29 AM, Michal Kazior wrote:
>> Try not to email me privately when discussing in public unless there's
>> a good reason to do so, please.
>>
>>
>> On 23 July 2015 at 12:11, Alexandre Maloteaux <a.maloteaux at gmail.com> wrote:
>>> Hi Michal
>>>
>>> With latest kvalo-master. I m getting this error on boot and after
>>> irq_mode=1
>>> I used sumdog firmwares from github :
>>>
>>> [ 255.996373] ath10k_pci 0000:06:00.0: enabling device (0000 -> 0002)
>>> [  255.997129] ath10k_pci 0000:06:00.0: pci irq msi-x interrupts 8
>>> irq_mode 0 reset_mode 0
>>> [  256.174560] ath10k_pci 0000:06:00.0: Direct firmware load for
>>> ath10k/cal-pci-0000:06:00.0.bin failed with error -2
>>> [ 256.174562] ath10k_pci 0000:06:00.0: Falling back to user helper
>>> [  316.269053] ath10k_pci 0000:06:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2
>>> [  316.269061] ath10k_pci 0000:06:00.0: Falling back to user helper
>>> [  376.362848] ath10k_pci 0000:06:00.0: failed to load spec board file,
>>> falling back to generic: -11
>>> [  376.363326] ath10k_pci 0000:06:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>>> [  376.363333] ath10k_pci 0000:06:00.0: Falling back to user helper
>>> [  436.458041] ath10k_pci 0000:06:00.0: could not fetch firmware file
>>> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -11
>>> [  437.634407] ath10k_pci 0000:06:00.0: received unsolicited fw crash
>>> interrupt
>>> [  437.634415] ath10k_pci 0000:06:00.0: received unsolicited fw crash
>>> interrupt
>>> [  438.634688] ath10k_pci 0000:06:00.0: failed to receive control
>>> response completion, polling..
>>> [  438.634767] ath10k_pci 0000:06:00.0: received unsolicited fw crash
>>> interrupt
>>> [  438.634790] ath10k_pci 0000:06:00.0: received unsolicited fw crash
>>> interrupt
>>> [  439.636320] ath10k_pci 0000:06:00.0: Service connect timeout
>>> [  439.636325] ath10k_pci 0000:06:00.0: failed to connect htt (-110)
>>> [  439.706905] ath10k_pci 0000:06:00.0: could not init core (-110)
>>> [  439.706929] ath10k_pci 0000:06:00.0: could not probe fw (-110)
>> The above is previous attempt without irq_mode being set so can be ignored.
>>
>>
>>> [  515.965549] ath10k_pci 0000:06:00.0: limiting irq mode to: 1
>>>
>>> [  515.965557] ath10k_pci 0000:06:00.0: pci irq legacy interrupts 0
>>> irq_mode 1 reset_mode 0
>>> [  516.202334] ath10k_pci 0000:06:00.0: Direct firmware load for
>>> ath10k/cal-pci-0000:06:00.0.bin failed with error -2
>>> [ 516.202335] ath10k_pci 0000:06:00.0: Falling back to user helper
>>> [ 576.296201] ath10k_pci 0000:06:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2
>>> [ 576.296210] ath10k_pci 0000:06:00.0: Falling back to user helper
>> You seem to be having really long timeouts when probing fw files. This
>> shouldn't be a problem as far as functionality is concerned but can be
>> really painful to wait all these delays.. I don't know why your system
>> does that. I suspect your udev is broken and misconfigured.
>>
>>
>>> [ 636.391328] ath10k_pci 0000:06:00.0: failed to load spec board file,
>>> falling back to generic: -11
>>> [ 636.391402] ath10k_pci 0000:06:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>>> [ 636.391405] ath10k_pci 0000:06:00.0: Falling back to user helper
>> I don't see fatal failure here. Everything up until this line is mere
>> warnings. There should be more prints following this.
>>
>>
>> Michał
>>