QCA6174 hw2.1?

QCA6174 hw2.1?

[jhihn]

I went through the archives, and the  wiki but I still wasn't sure... 
I have a shiny new Lenovo z70, kernel 4.0-rc1/3.  Dmesg reports failures for loading  firmware in /lib/firmware/ath10k/QCA6174/hw2.1/... 
So I found the firmware Git repo,  but it seems to be missing hw2.1. I even symlinked 2.1 to  3.0, no dice. 

I don't dual boot and this is a laptop  so I'm looking to get  my WiFi working.  Any pointers are appreciated.  Thanks.

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

Re: QCA6174 hw2.1?

[Michal Kazior]

On 13 March 2015 at 04:39,  <jhihn@gmx.com> wrote:
> I went through the archives, and the  wiki but I still wasn't sure...
> I have a shiny new Lenovo z70, kernel 4.0-rc1/3.  Dmesg reports failures for loading  firmware in /lib/firmware/ath10k/QCA6174/hw2.1/...
> So I found the firmware Git repo,  but it seems to be missing hw2.1. I even symlinked 2.1 to  3.0, no dice.

You can't use hw3 firmware for hw2 hardware.

The problem is there's no publicly available ath10k firmware for hw2 hardware..


> I don't dual boot and this is a laptop  so I'm looking to get  my WiFi working.  Any pointers are appreciated.  Thanks.

You could try building hw2 firmware ath10k binary yourself. You need
to fetch athwlan.bin from Windows driver, extract otp image from hw3
firmware ath10k binary and then re-assemble both into hw3 firmware for
ath10k. The ath10k binary blob is a tag-length-value format and can be
understood by looking at ath10k_core_fetch_firmware_api_n().

Nobody seems to have tried this yet though.


Michał

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

Re: QCA6174 hw2.1?

[Jason H]

> On 13 March 2015 at 04:39,  <jhihn@gmx.com> wrote:
> > I went through the archives, and the  wiki but I still wasn't sure...
> > I have a shiny new Lenovo z70, kernel 4.0-rc1/3.  Dmesg reports failures for loading  firmware in /lib/firmware/ath10k/QCA6174/hw2.1/...
> > So I found the firmware Git repo,  but it seems to be missing hw2.1. I even symlinked 2.1 to  3.0, no dice.
> 
> You can't use hw3 firmware for hw2 hardware.
> 
> The problem is there's no publicly available ath10k firmware for hw2 hardware..
> 
> 
> > I don't dual boot and this is a laptop  so I'm looking to get  my WiFi working.  Any pointers are appreciated.  Thanks.
> 
> You could try building hw2 firmware ath10k binary yourself. You need
> to fetch athwlan.bin from Windows driver, extract otp image from hw3
> firmware ath10k binary and then re-assemble both into hw3 firmware for
> ath10k. The ath10k binary blob is a tag-length-value format and can be
> understood by looking at ath10k_core_fetch_firmware_api_n().
> 
> Nobody seems to have tried this yet though.


I installed WINE and attempted to install the driver from lenono on my non-lenovo with working wifi. The install failed (expected) but not before it extracted the actual driver installer images (expected). Parsing through an .inf file, and navigating my way through the sections, I end up at a section specifying eeprom_ar6320_2p1_NFA354xp.bin and qca61x420.bin as the firmware files. I have these files.

However I am now diverging from your instructions considerably. Also I don't know why I would want to reassemble into 3.0 when my system is looking for 2.1? I don't know what an 'otp image' is? I think I understand the part about the ath10k format though.

Could you update your instructions to suit the new information at hand? 


Thanks again


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

Re: QCA6174 hw2.1?

[Michal Kazior]

On 13 March 2015 at 16:28, Jason H <jhihn@gmx.com> wrote:
>
>> On 13 March 2015 at 04:39,  <jhihn@gmx.com> wrote:
>> > I went through the archives, and the  wiki but I still wasn't sure...
>> > I have a shiny new Lenovo z70, kernel 4.0-rc1/3.  Dmesg reports failures for loading  firmware in /lib/firmware/ath10k/QCA6174/hw2.1/...
>> > So I found the firmware Git repo,  but it seems to be missing hw2.1. I even symlinked 2.1 to  3.0, no dice.
>>
>> You can't use hw3 firmware for hw2 hardware.
>>
>> The problem is there's no publicly available ath10k firmware for hw2 hardware..
>>
>>
>> > I don't dual boot and this is a laptop  so I'm looking to get  my WiFi working.  Any pointers are appreciated.  Thanks.
>>
>> You could try building hw2 firmware ath10k binary yourself. You need
>> to fetch athwlan.bin from Windows driver, extract otp image from hw3
>> firmware ath10k binary and then re-assemble both into hw3 firmware for
>> ath10k. The ath10k binary blob is a tag-length-value format and can be
>> understood by looking at ath10k_core_fetch_firmware_api_n().
>>
>> Nobody seems to have tried this yet though.
>
>
> I installed WINE and attempted to install the driver from lenono on my non-lenovo with working wifi. The install failed (expected) but not before it extracted the actual driver installer images (expected). Parsing through an .inf file, and navigating my way through the sections, I end up at a section specifying eeprom_ar6320_2p1_NFA354xp.bin and qca61x420.bin as the firmware files. I have these files.

Awesome.

eeprom_ar6320_2p1_NFA354xp.bin looks like a board.bin.
qca61x420.bin looks like main program binary.


> However I am now diverging from your instructions considerably. Also I don't know why I would want to reassemble into 3.0 when my system is looking for 2.1?

Typo/mind derp :-) I obviously meant 2.1.


> I don't know what an 'otp image' is? I think I understand the part about the ath10k format though.

OTP is a calibration related program which is run on device before
running main program. It's embedded inside ath10k FW API blob.


> Could you update your instructions to suit the new information at hand?

https://gist.github.com/kazikcz/c970cbf3a863ebbc4495
https://gist.github.com/kazikcz/64313b9e2470660faae1

Here are two simple and crude tools I have to deal with ath10k FW API
blobs. Use with care.

You can use the disassemble.py to extract the otp.bin from hw3 ath10k
FW API blob:

  python disassemble.py < /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin

Then you can use the assemble.py to generate hw2.1 ath10k FW ABI blob:

  mkdir -p /lib/firmware/ath10k/QCA6174/hw2.1/
  python assemble.py killer1252-testfw 0 path/to/qca61x420.bin
path/to/otp.bin 4 > /lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin
  cp path/to/eeprom_ar6320_2p1_NFA354xp.bin
/lib/firmware/ath10k/QCA6174/hw2.1/board.bin

(mind the email line wrapping)


Michał

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

Re: QCA6174 hw2.1?

[Gabriele Martino]

Michal Kazior <michal.kazior <at> tieto.com> writes:

> 
> https://gist.github.com/kazikcz/c970cbf3a863ebbc4495
> https://gist.github.com/kazikcz/64313b9e2470660faae1
> 
> Here are two simple and crude tools I have to deal with ath10k FW API
> blobs. Use with care.
> 
> You can use the disassemble.py to extract the otp.bin from hw3 ath10k
> FW API blob:
> 
>   python disassemble.py < /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
> 
> Then you can use the assemble.py to generate hw2.1 ath10k FW ABI blob:
> 
>   mkdir -p /lib/firmware/ath10k/QCA6174/hw2.1/
>   python assemble.py killer1252-testfw 0 path/to/qca61x420.bin
> path/to/otp.bin 4 > /lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin
>   cp path/to/eeprom_ar6320_2p1_NFA354xp.bin
> /lib/firmware/ath10k/QCA6174/hw2.1/board.bin
> 
> (mind the email line wrapping)
> 

I'm trying to generate the blob, but I found two big issues.
The first: I have too many board files, which one should I use?
eeprom_ar6320_2p1_NFA324i_5.bin
eeprom_ar6320_2p1_NFA344i.bin
eeprom_ar6320_2p1_NFA344i_highTX.bin
eeprom_ar6320_2p1_NFA345i.bin
eeprom_ar6320_2p1_NFA345i_highTX.bin
eeprom_ar6320_2p1_NFA354xp.bin
eeprom_ar6320_2p1_NFA355i.bin
eeprom_qca9377_1p0_NFA435_olpc.bin

The controller is a
"Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 20)"
declared as Killer N1525 on Alienware 15.

Whatever, I can try them one by one later.
I picked up the first and built the firmware blob.
But here's the second issue: it wants the calibration data.

[    2.067447] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
[    2.068679] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode
0 reset_mode 0
[    2.215280] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-
0000:03:00.0.bin failed with error -2
[    2.924276] ath3k: probe of 1-9:1.0 failed with error -22
[    2.924299] usbcore: registered new interface driver ath3k
[    3.289023] ath10k_pci 0000:03:00.0: unable to write to the device
[    3.289026] ath10k_pci 0000:03:00.0: failed to download normal firmware: -110
[    3.289052] ath10k_pci 0000:03:00.0: could not init core (-110)
[    3.289099] ath10k_pci 0000:03:00.0: could not probe fw (-110)

How can I generate the cal-pci-0000:03:00.0.bin file?
I'm using the 4.0.0-gentoo kernel on x86_64.

Regards,
Gabriele


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

Re: QCA6174 hw2.1?

[Corin Lawson]

Hi Gabriele,

I have had success with eeprom_ar6320_2p1_NFA344i.bin.

I am also using Gentoo (but v3.19.3) but I have also applied these
patches/commits:

- http://permalink.gmane.org/gmane.linux.kernel.wireless.general/137030
- https://github.com/kvalo/ath/commit/d63955b33b3bee45d784ffdfafeb93076c765660

Also, I didn't use that disassemble.py script, I used:

- https://gist.github.com/kazikcz/8e5845ad84ca251aa295

I also had problems with calibration, I had to pass skip_otp=y to the module:

    $ cat /etc/modprobe.d/ath10k.conf
    options ath10k_core skip_otp=y

FWIW:

    $ lspci -vs 05:00.0
    05:00.0 Network controller: Qualcomm Atheros Device 003e (rev 20)
            Subsystem: Bigfoot Networks, Inc. Device 1525
            Flags: bus master, fast devsel, latency 0, IRQ 31
            Memory at f7800000 (64-bit, non-prefetchable) [size=2M]
            Capabilities: <access denied>
            Kernel driver in use: ath10k_pci
            Kernel modules: ath10k_pci

I give a huge thanks to the individuals on this mailing list for
helping me; I'm just happy to give back where I can :)

I would interested in knowing from where you got your drivers/board
files. I had to download mine from my laptop manufacturer's (MSI)
website.

Note: I understand that ath10k doesn't support encryption yet. But I
haven't successfully been able to connect to my open AP as yet...

Cheers,
Corin

On Sat, Apr 25, 2015 at 11:15 AM, Gabriele Martino <g.martino@gmx.com> wrote:
>
> Michal Kazior <michal.kazior <at> tieto.com> writes:
>
> >
> > https://gist.github.com/kazikcz/c970cbf3a863ebbc4495
> > https://gist.github.com/kazikcz/64313b9e2470660faae1
> >
> > Here are two simple and crude tools I have to deal with ath10k FW API
> > blobs. Use with care.
> >
> > You can use the disassemble.py to extract the otp.bin from hw3 ath10k
> > FW API blob:
> >
> >   python disassemble.py < /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
> >
> > Then you can use the assemble.py to generate hw2.1 ath10k FW ABI blob:
> >
> >   mkdir -p /lib/firmware/ath10k/QCA6174/hw2.1/
> >   python assemble.py killer1252-testfw 0 path/to/qca61x420.bin
> > path/to/otp.bin 4 > /lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin
> >   cp path/to/eeprom_ar6320_2p1_NFA354xp.bin
> > /lib/firmware/ath10k/QCA6174/hw2.1/board.bin
> >
> > (mind the email line wrapping)
> >
>
> I'm trying to generate the blob, but I found two big issues.
> The first: I have too many board files, which one should I use?
> eeprom_ar6320_2p1_NFA324i_5.bin
> eeprom_ar6320_2p1_NFA344i.bin
> eeprom_ar6320_2p1_NFA344i_highTX.bin
> eeprom_ar6320_2p1_NFA345i.bin
> eeprom_ar6320_2p1_NFA345i_highTX.bin
> eeprom_ar6320_2p1_NFA354xp.bin
> eeprom_ar6320_2p1_NFA355i.bin
> eeprom_qca9377_1p0_NFA435_olpc.bin
>
> The controller is a
> "Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 20)"
> declared as Killer N1525 on Alienware 15.
>
> Whatever, I can try them one by one later.
> I picked up the first and built the firmware blob.
> But here's the second issue: it wants the calibration data.
>
> [    2.067447] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
> [    2.068679] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode
> 0 reset_mode 0
> [    2.215280] ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-
> 0000:03:00.0.bin failed with error -2
> [    2.924276] ath3k: probe of 1-9:1.0 failed with error -22
> [    2.924299] usbcore: registered new interface driver ath3k
> [    3.289023] ath10k_pci 0000:03:00.0: unable to write to the device
> [    3.289026] ath10k_pci 0000:03:00.0: failed to download normal firmware: -110
> [    3.289052] ath10k_pci 0000:03:00.0: could not init core (-110)
> [    3.289099] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>
> How can I generate the cal-pci-0000:03:00.0.bin file?
> I'm using the 4.0.0-gentoo kernel on x86_64.
>
> Regards,
> Gabriele
>
>
> _______________________________________________
> 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

Re: QCA6174 hw2.1?

[Corin Lawson]

Hi Gabriele,

I think we have the same card (the vendor and device ids are the
determining factor):

    $ lspci -n -s 05:00.0
    05:00.0 0280: 168c:003e (rev 20)

Without the skip_otp option I get this in dmesg:

    [18396.622576] ath10k_pci 0000:05:00.0: pci irq msi interrupts 1
irq_mode 0 reset_mode 0
    [18396.768593] ath10k_pci 0000:05:00.0: Direct firmware load for
ath10k/cal-pci-0000:05:00.0.bin failed with error -2
    [18396.847975] ath10k_pci 0000:05:00.0: otp calibration failed: 3
    [18396.847977] ath10k_pci 0000:05:00.0: failed to run otp: -22
    [18396.847978] ath10k_pci 0000:05:00.0: could not init core (-22)
    [18396.847995] ath10k_pci 0000:05:00.0: could not probe fw (-22)

Which is different to your messages. I'm taking a guess here, but
those DMAR messages seem to indicate that the firmware is attempting
to write to the wrong part of memory (i.e. wrong firmware).

Using kvalo's kernel fork is probably a good step (it contains those
necessary patches). If you still don't get it working, then my only
other idea is to try that dissect.py gist I mentioned previously. Here
are the commands that worked for me:

    # python dissect.py <
drivers/Production/Windows8.1-x64/k1525w81/qca61x420.bin
    # python assemble.py killer-n1525-fw 0 fw-2.bin fw-1.bin 4 >
/lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin

The dissect.py script produced fw-1.bin which is the otp file and
fw-2.bin which is the correct firmware (don't quote me on that, but it
worked for me). As for your board.bin file, you need to check the .inf
file that comes with your drivers. I'm not sure what the structure of
that file is... for all I know I could be using the wrong board
file...

I hope this helps, otherwise you've reached the limits of my
experience :) Maybe someone else on the list has a better idea?

Cheers,
Corin


On Sat, Apr 25, 2015 at 10:58 PM, Gabriele Martino <g.martino@gmx.com> wrote:
> On 25/04/2015 05:47, Corin Lawson wrote:
>> I also had problems with calibration, I had to pass skip_otp=y to the module:
>>
>>     $ cat /etc/modprobe.d/ath10k.conf
>>     options ath10k_core skip_otp=y
> Hi Corin,
> I removed ath10k_pci, ath10k_core and ath before loading ath10k_core
> with skip_otp=1, but nothing happened:
>
> [ 1808.473874] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0
> [ 1808.618770] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [ 1808.687492] dmar: DRHD: handling fault status reg 2
> [ 1808.687506] dmar: DMAR:[DMA Write] Request device [03:00.0] fault
> addr 7ee00000
>                DMAR:[fault reason 05] PTE Write access is not set
> [ 1809.688015] ath10k_pci 0000:03:00.0: unable to write to the device
> [ 1809.688018] ath10k_pci 0000:03:00.0: failed to download normal
> firmware: -110
> [ 1809.688020] ath10k_pci 0000:03:00.0: could not init core (-110)
> [ 1809.688054] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>
> I assembled the otp.bin with fw.bin to get the blob, so I'm not sure
> skip_otp will fix this...
> Now I'm cloning the kvalo's kernel tree, this should be faster than
> picking the single patches.
>
>> FWIW:
>>
>>     $ lspci -vs 05:00.0
>>     05:00.0 Network controller: Qualcomm Atheros Device 003e (rev 20)
>>             Subsystem: Bigfoot Networks, Inc. Device 1525
>>             Flags: bus master, fast devsel, latency 0, IRQ 31
>>             Memory at f7800000 (64-bit, non-prefetchable) [size=2M]
>>             Capabilities: <access denied>
>>             Kernel driver in use: ath10k_pci
>>             Kernel modules: ath10k_pci
> Well, mine seems a bit different:
>
> 03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
> Network Adapter (rev 20)
>         Subsystem: Bigfoot Networks, Inc. Killer N1525 Wireless-AC
>         Flags: bus master, fast devsel, latency 0, IRQ 32
>         Memory at f6800000 (64-bit, non-prefetchable) [size=2M]
>         Capabilities: [40] Power Management version 3
>         Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
>         Capabilities: [70] Express Endpoint, MSI 00
>         Capabilities: [100] Advanced Error Reporting
>         Capabilities: [148] Virtual Channel
>         Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
>         Capabilities: [178] Latency Tolerance Reporting
>         Capabilities: [180] L1 PM Substates
>         Kernel driver in use: ath10k_pci
>         Kernel modules: ath10k_pci
>
>> I would interested in knowing from where you got your drivers/board
>> files. I had to download mine from my laptop manufacturer's (MSI)
>> website.
> I mounted the preinstalled Windows 8 partition on /mnt and run:
> find /mnt -iname '*.bin'
>
> The same files can be found inside the driver installer on the Alienware
> (Dell) website.
>
> Regards,
> Gabriele
>

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

Re: QCA6174 hw2.1?

[Gabriele Martino]

Hi Corin,
the "dissect.py" script seems to work better than the "disassemble.py":

[ 6483.455435] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
irq_mode 0 reset_mode 0
[ 6483.600747] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[ 6484.772417] ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
[ 6484.772433] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
0x003405ff) fw killer-n1525-fw api 4 htt 0.0 wmi 4 cal otp max_sta 32
[ 6484.772435] ath10k_pci 0000:03:00.0: debug 1 debugfs 0 tracing 0 dfs
0 testmode 0
[ 6484.773333] ath10k_pci 0000:03:00.0: firmware register dump:
[ 6484.773333] ath10k_pci 0000:03:00.0: [00]: 0x05010000 0x000015B3
0x0095186B 0x00955B31
[ 6484.773333] ath10k_pci 0000:03:00.0: [04]: 0x0095186B 0x00060130
0x00000010 0x0040AF04
[ 6484.773333] ath10k_pci 0000:03:00.0: [08]: 0x00000018 0x00000001
0x00000001 0x00412250
[ 6484.773333] ath10k_pci 0000:03:00.0: [12]: 0x00000009 0x00000000
0x0096C09C 0x0096C0A7
[ 6484.773333] ath10k_pci 0000:03:00.0: [16]: 0x0096BDBC 0x009286B6
0x00000000 0x00000000
[ 6484.773333] ath10k_pci 0000:03:00.0: [20]: 0x4095186B 0x0040E160
0x0041F82C 0x00000001
[ 6484.773333] ath10k_pci 0000:03:00.0: [24]: 0x80936238 0x0040E1C0
0x00000000 0xC095186B
[ 6484.773333] ath10k_pci 0000:03:00.0: [28]: 0x80936361 0x0040E1E0
0x00000000 0x0041C8DC
[ 6484.773333] ath10k_pci 0000:03:00.0: [32]: 0x80934A67 0x0040E200
0x00436DF0 0x0040E250
[ 6484.773333] ath10k_pci 0000:03:00.0: [36]: 0x809A5C92 0x0040E250
0x004275B0 0x00000001
[ 6484.773333] ath10k_pci 0000:03:00.0: [40]: 0x809A5CEA 0x0040E290
0x00426F40 0x00000004
[ 6484.773333] ath10k_pci 0000:03:00.0: [44]: 0x809A5DCA 0x0040E2B0
0x00426F40 0x0041C8DC
[ 6484.773333] ath10k_pci 0000:03:00.0: [48]: 0x800A0909 0x0040E2D0
0x00426F40 0x004275A0
[ 6484.773333] ath10k_pci 0000:03:00.0: [52]: 0x800A024A 0x0040E2F0
0x0041ABB0 0x00420440
[ 6484.773333] ath10k_pci 0000:03:00.0: [56]: 0x809287D9 0x0040E310
0x00000000 0x00400000
[ 6485.765040] ath10k_pci 0000:03:00.0: failed to receive control
response completion, polling..
[ 6486.765027] ath10k_pci 0000:03:00.0: ctl_resp never came in (-110)
[ 6486.765032] ath10k_pci 0000:03:00.0: failed to connect to HTC: -110
[ 6486.828658] ath10k_pci 0000:03:00.0: could not init core (-110)
[ 6486.828689] ath10k_pci 0000:03:00.0: could not probe fw (-110)
[ 6486.831175] ath10k_pci 0000:03:00.0: cannot restart a device that
hasn't been started

Well, at least it loads correctly. This should be the firmware crash
fixed in the patches, it's time to test kvalo's kernel sources.


On 26/04/2015 05:51, Corin Lawson wrote:
> Hi Gabriele,
>
> I think we have the same card (the vendor and device ids are the
> determining factor):
>
>     $ lspci -n -s 05:00.0
>     05:00.0 0280: 168c:003e (rev 20)
>
> Without the skip_otp option I get this in dmesg:
>
>     [18396.622576] ath10k_pci 0000:05:00.0: pci irq msi interrupts 1
> irq_mode 0 reset_mode 0
>     [18396.768593] ath10k_pci 0000:05:00.0: Direct firmware load for
> ath10k/cal-pci-0000:05:00.0.bin failed with error -2
>     [18396.847975] ath10k_pci 0000:05:00.0: otp calibration failed: 3
>     [18396.847977] ath10k_pci 0000:05:00.0: failed to run otp: -22
>     [18396.847978] ath10k_pci 0000:05:00.0: could not init core (-22)
>     [18396.847995] ath10k_pci 0000:05:00.0: could not probe fw (-22)
>
> Which is different to your messages. I'm taking a guess here, but
> those DMAR messages seem to indicate that the firmware is attempting
> to write to the wrong part of memory (i.e. wrong firmware).
>
> Using kvalo's kernel fork is probably a good step (it contains those
> necessary patches). If you still don't get it working, then my only
> other idea is to try that dissect.py gist I mentioned previously. Here
> are the commands that worked for me:
>
>     # python dissect.py <
> drivers/Production/Windows8.1-x64/k1525w81/qca61x420.bin
>     # python assemble.py killer-n1525-fw 0 fw-2.bin fw-1.bin 4 >
> /lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin
>
> The dissect.py script produced fw-1.bin which is the otp file and
> fw-2.bin which is the correct firmware (don't quote me on that, but it
> worked for me). As for your board.bin file, you need to check the .inf
> file that comes with your drivers. I'm not sure what the structure of
> that file is... for all I know I could be using the wrong board
> file...
>
> I hope this helps, otherwise you've reached the limits of my
> experience :) Maybe someone else on the list has a better idea?
>
> Cheers,
> Corin
>
>
> On Sat, Apr 25, 2015 at 10:58 PM, Gabriele Martino <g.martino@gmx.com> wrote:
>> On 25/04/2015 05:47, Corin Lawson wrote:
>>> I also had problems with calibration, I had to pass skip_otp=y to the module:
>>>
>>>     $ cat /etc/modprobe.d/ath10k.conf
>>>     options ath10k_core skip_otp=y
>> Hi Corin,
>> I removed ath10k_pci, ath10k_core and ath before loading ath10k_core
>> with skip_otp=1, but nothing happened:
>>
>> [ 1808.473874] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>> irq_mode 0 reset_mode 0
>> [ 1808.618770] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>> [ 1808.687492] dmar: DRHD: handling fault status reg 2
>> [ 1808.687506] dmar: DMAR:[DMA Write] Request device [03:00.0] fault
>> addr 7ee00000
>>                DMAR:[fault reason 05] PTE Write access is not set
>> [ 1809.688015] ath10k_pci 0000:03:00.0: unable to write to the device
>> [ 1809.688018] ath10k_pci 0000:03:00.0: failed to download normal
>> firmware: -110
>> [ 1809.688020] ath10k_pci 0000:03:00.0: could not init core (-110)
>> [ 1809.688054] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>>
>> I assembled the otp.bin with fw.bin to get the blob, so I'm not sure
>> skip_otp will fix this...
>> Now I'm cloning the kvalo's kernel tree, this should be faster than
>> picking the single patches.
>>
>>> FWIW:
>>>
>>>     $ lspci -vs 05:00.0
>>>     05:00.0 Network controller: Qualcomm Atheros Device 003e (rev 20)
>>>             Subsystem: Bigfoot Networks, Inc. Device 1525
>>>             Flags: bus master, fast devsel, latency 0, IRQ 31
>>>             Memory at f7800000 (64-bit, non-prefetchable) [size=2M]
>>>             Capabilities: <access denied>
>>>             Kernel driver in use: ath10k_pci
>>>             Kernel modules: ath10k_pci
>> Well, mine seems a bit different:
>>
>> 03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
>> Network Adapter (rev 20)
>>         Subsystem: Bigfoot Networks, Inc. Killer N1525 Wireless-AC
>>         Flags: bus master, fast devsel, latency 0, IRQ 32
>>         Memory at f6800000 (64-bit, non-prefetchable) [size=2M]
>>         Capabilities: [40] Power Management version 3
>>         Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
>>         Capabilities: [70] Express Endpoint, MSI 00
>>         Capabilities: [100] Advanced Error Reporting
>>         Capabilities: [148] Virtual Channel
>>         Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
>>         Capabilities: [178] Latency Tolerance Reporting
>>         Capabilities: [180] L1 PM Substates
>>         Kernel driver in use: ath10k_pci
>>         Kernel modules: ath10k_pci
>>
>>> I would interested in knowing from where you got your drivers/board
>>> files. I had to download mine from my laptop manufacturer's (MSI)
>>> website.
>> I mounted the preinstalled Windows 8 partition on /mnt and run:
>> find /mnt -iname '*.bin'
>>
>> The same files can be found inside the driver installer on the Alienware
>> (Dell) website.
>>
>> Regards,
>> Gabriele
>>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k

-- 

*Gabriele Martino*

Linux Sysadmin & Web Development

g.martino@gmx.com



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

Re: QCA6174 hw2.1?

[Gabriele Martino]

Just tried the kvalo's kernel.
NetworkManager connected flawlessly at boot to my WPA2 home network on
2.4GHz. Will try 5GHz later.
iwconfig reports a fixed 1Mb/s bitrate, but I can copy files to my nas
(smb share) at about 3.3MB/s.
That's a reasonable speed for b/g wireless.

iwconfig:
wlp3s0    IEEE 802.11abgn  ESSID:"W-I-SEE-YOU-N" 
          Mode:Managed  Frequency:2.412 GHz  Access Point:
40:16:7E:2C:79:90  
          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=59/70  Signal level=-51 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:42   Missed beacon:0

iwlist scan (part of):
wlp3s0    Scan completed :
          Cell 01 - Address: 40:16:7E:2C:79:90
                    Channel:1
                    Frequency:2.412 GHz (Channel 1)
                    Quality=60/70  Signal level=-50 dBm 
                    Encryption key:on
                    ESSID:"W-I-SEE-YOU-N"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=00000005244f5a5d
                    Extra: Last beacon: 33ms ago
                    IE: Unknown: 000D572D492D5345452D594F552D4E
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 030101
                    IE: Unknown: 2A0104
                    IE: Unknown: 2F0104
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : CCMP
                        Pairwise Ciphers (1) : CCMP
                        Authentication Suites (1) : PSK

dmesg output:
[    2.212106] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
[    2.212558] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
irq_mode 0 reset_mode 0
[    2.368318] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[    2.368971] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2
[    2.368974] ath10k_pci 0000:03:00.0: failed to load spec board file,
falling back to generic: -2
[    2.369252] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[    2.369270] ath10k_pci 0000:03:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
[    3.559021] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
3.0 wmi 4 cal otp max_sta 32
[    3.559024] ath10k_pci 0000:03:00.0: debug 1 debugfs 0 tracing 0 dfs
0 testmode 0
[    3.623733] ath: EEPROM regdomain: 0x6c
[    3.623735] ath: EEPROM indicates we should expect a direct regpair map
[    3.623736] ath: Country alpha2 being used: 00
[    3.623737] ath: Regpair used: 0x6c
[    3.638102] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
[    7.523617] ath10k_pci 0000:03:00.0: no channel configured; ignoring
frame(s)!
[    7.627173] ath10k_pci 0000:03:00.0: no channel configured; ignoring
frame(s)!
[   12.149947] wlp3s0: authenticate with 40:16:7e:2c:79:90
[   12.183915] wlp3s0: send auth to 40:16:7e:2c:79:90 (try 1/3)
[   12.185559] wlp3s0: authenticated
[   12.186043] wlp3s0: associate with 40:16:7e:2c:79:90 (try 1/3)
[   12.189402] wlp3s0: RX AssocResp from 40:16:7e:2c:79:90 (capab=0x411
status=0 aid=3)
[   12.192174] wlp3s0: associated
[  313.912952] wlp3s0: AP 40:16:7e:2c:79:90 changed bandwidth, new
config is 2412 MHz, width 1 (2412/0 MHz)
[  313.912955] wlp3s0: AP 40:16:7e:2c:79:90 changed bandwidth in a way
we can't support - disconnect
[  318.709453] wlp3s0: authenticate with 40:16:7e:2c:79:90
[  318.750807] wlp3s0: send auth to 40:16:7e:2c:79:90 (try 1/3)
[  318.752541] wlp3s0: authenticated
[  318.753030] wlp3s0: associate with 40:16:7e:2c:79:90 (try 1/3)
[  318.756524] wlp3s0: RX AssocResp from 40:16:7e:2c:79:90 (capab=0x411
status=0 aid=1)
[  318.759082] wlp3s0: associated

I'm using the board file "eeprom_qca9377_1p0_NFA435_olpc.bin".

Regards,
Gabriele


On 26/04/2015 16:10, Gabriele Martino wrote:
> Hi Corin,
> the "dissect.py" script seems to work better than the "disassemble.py":
>
> [ 6483.455435] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0
> [ 6483.600747] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [ 6484.772417] ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
> [ 6484.772433] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
> 0x003405ff) fw killer-n1525-fw api 4 htt 0.0 wmi 4 cal otp max_sta 32
> [ 6484.772435] ath10k_pci 0000:03:00.0: debug 1 debugfs 0 tracing 0 dfs
> 0 testmode 0
> [ 6484.773333] ath10k_pci 0000:03:00.0: firmware register dump:
> [ 6484.773333] ath10k_pci 0000:03:00.0: [00]: 0x05010000 0x000015B3
> 0x0095186B 0x00955B31
> [ 6484.773333] ath10k_pci 0000:03:00.0: [04]: 0x0095186B 0x00060130
> 0x00000010 0x0040AF04
> [ 6484.773333] ath10k_pci 0000:03:00.0: [08]: 0x00000018 0x00000001
> 0x00000001 0x00412250
> [ 6484.773333] ath10k_pci 0000:03:00.0: [12]: 0x00000009 0x00000000
> 0x0096C09C 0x0096C0A7
> [ 6484.773333] ath10k_pci 0000:03:00.0: [16]: 0x0096BDBC 0x009286B6
> 0x00000000 0x00000000
> [ 6484.773333] ath10k_pci 0000:03:00.0: [20]: 0x4095186B 0x0040E160
> 0x0041F82C 0x00000001
> [ 6484.773333] ath10k_pci 0000:03:00.0: [24]: 0x80936238 0x0040E1C0
> 0x00000000 0xC095186B
> [ 6484.773333] ath10k_pci 0000:03:00.0: [28]: 0x80936361 0x0040E1E0
> 0x00000000 0x0041C8DC
> [ 6484.773333] ath10k_pci 0000:03:00.0: [32]: 0x80934A67 0x0040E200
> 0x00436DF0 0x0040E250
> [ 6484.773333] ath10k_pci 0000:03:00.0: [36]: 0x809A5C92 0x0040E250
> 0x004275B0 0x00000001
> [ 6484.773333] ath10k_pci 0000:03:00.0: [40]: 0x809A5CEA 0x0040E290
> 0x00426F40 0x00000004
> [ 6484.773333] ath10k_pci 0000:03:00.0: [44]: 0x809A5DCA 0x0040E2B0
> 0x00426F40 0x0041C8DC
> [ 6484.773333] ath10k_pci 0000:03:00.0: [48]: 0x800A0909 0x0040E2D0
> 0x00426F40 0x004275A0
> [ 6484.773333] ath10k_pci 0000:03:00.0: [52]: 0x800A024A 0x0040E2F0
> 0x0041ABB0 0x00420440
> [ 6484.773333] ath10k_pci 0000:03:00.0: [56]: 0x809287D9 0x0040E310
> 0x00000000 0x00400000
> [ 6485.765040] ath10k_pci 0000:03:00.0: failed to receive control
> response completion, polling..
> [ 6486.765027] ath10k_pci 0000:03:00.0: ctl_resp never came in (-110)
> [ 6486.765032] ath10k_pci 0000:03:00.0: failed to connect to HTC: -110
> [ 6486.828658] ath10k_pci 0000:03:00.0: could not init core (-110)
> [ 6486.828689] ath10k_pci 0000:03:00.0: could not probe fw (-110)
> [ 6486.831175] ath10k_pci 0000:03:00.0: cannot restart a device that
> hasn't been started
>
> Well, at least it loads correctly. This should be the firmware crash
> fixed in the patches, it's time to test kvalo's kernel sources.
>
>
> On 26/04/2015 05:51, Corin Lawson wrote:
>> Hi Gabriele,
>>
>> I think we have the same card (the vendor and device ids are the
>> determining factor):
>>
>>     $ lspci -n -s 05:00.0
>>     05:00.0 0280: 168c:003e (rev 20)
>>
>> Without the skip_otp option I get this in dmesg:
>>
>>     [18396.622576] ath10k_pci 0000:05:00.0: pci irq msi interrupts 1
>> irq_mode 0 reset_mode 0
>>     [18396.768593] ath10k_pci 0000:05:00.0: Direct firmware load for
>> ath10k/cal-pci-0000:05:00.0.bin failed with error -2
>>     [18396.847975] ath10k_pci 0000:05:00.0: otp calibration failed: 3
>>     [18396.847977] ath10k_pci 0000:05:00.0: failed to run otp: -22
>>     [18396.847978] ath10k_pci 0000:05:00.0: could not init core (-22)
>>     [18396.847995] ath10k_pci 0000:05:00.0: could not probe fw (-22)
>>
>> Which is different to your messages. I'm taking a guess here, but
>> those DMAR messages seem to indicate that the firmware is attempting
>> to write to the wrong part of memory (i.e. wrong firmware).
>>
>> Using kvalo's kernel fork is probably a good step (it contains those
>> necessary patches). If you still don't get it working, then my only
>> other idea is to try that dissect.py gist I mentioned previously. Here
>> are the commands that worked for me:
>>
>>     # python dissect.py <
>> drivers/Production/Windows8.1-x64/k1525w81/qca61x420.bin
>>     # python assemble.py killer-n1525-fw 0 fw-2.bin fw-1.bin 4 >
>> /lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin
>>
>> The dissect.py script produced fw-1.bin which is the otp file and
>> fw-2.bin which is the correct firmware (don't quote me on that, but it
>> worked for me). As for your board.bin file, you need to check the .inf
>> file that comes with your drivers. I'm not sure what the structure of
>> that file is... for all I know I could be using the wrong board
>> file...
>>
>> I hope this helps, otherwise you've reached the limits of my
>> experience :) Maybe someone else on the list has a better idea?
>>
>> Cheers,
>> Corin
>>
>>
>> On Sat, Apr 25, 2015 at 10:58 PM, Gabriele Martino <g.martino@gmx.com> wrote:
>>> On 25/04/2015 05:47, Corin Lawson wrote:
>>>> I also had problems with calibration, I had to pass skip_otp=y to the module:
>>>>
>>>>     $ cat /etc/modprobe.d/ath10k.conf
>>>>     options ath10k_core skip_otp=y
>>> Hi Corin,
>>> I removed ath10k_pci, ath10k_core and ath before loading ath10k_core
>>> with skip_otp=1, but nothing happened:
>>>
>>> [ 1808.473874] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>>> irq_mode 0 reset_mode 0
>>> [ 1808.618770] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>>> [ 1808.687492] dmar: DRHD: handling fault status reg 2
>>> [ 1808.687506] dmar: DMAR:[DMA Write] Request device [03:00.0] fault
>>> addr 7ee00000
>>>                DMAR:[fault reason 05] PTE Write access is not set
>>> [ 1809.688015] ath10k_pci 0000:03:00.0: unable to write to the device
>>> [ 1809.688018] ath10k_pci 0000:03:00.0: failed to download normal
>>> firmware: -110
>>> [ 1809.688020] ath10k_pci 0000:03:00.0: could not init core (-110)
>>> [ 1809.688054] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>>>
>>> I assembled the otp.bin with fw.bin to get the blob, so I'm not sure
>>> skip_otp will fix this...
>>> Now I'm cloning the kvalo's kernel tree, this should be faster than
>>> picking the single patches.
>>>
>>>> FWIW:
>>>>
>>>>     $ lspci -vs 05:00.0
>>>>     05:00.0 Network controller: Qualcomm Atheros Device 003e (rev 20)
>>>>             Subsystem: Bigfoot Networks, Inc. Device 1525
>>>>             Flags: bus master, fast devsel, latency 0, IRQ 31
>>>>             Memory at f7800000 (64-bit, non-prefetchable) [size=2M]
>>>>             Capabilities: <access denied>
>>>>             Kernel driver in use: ath10k_pci
>>>>             Kernel modules: ath10k_pci
>>> Well, mine seems a bit different:
>>>
>>> 03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
>>> Network Adapter (rev 20)
>>>         Subsystem: Bigfoot Networks, Inc. Killer N1525 Wireless-AC
>>>         Flags: bus master, fast devsel, latency 0, IRQ 32
>>>         Memory at f6800000 (64-bit, non-prefetchable) [size=2M]
>>>         Capabilities: [40] Power Management version 3
>>>         Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
>>>         Capabilities: [70] Express Endpoint, MSI 00
>>>         Capabilities: [100] Advanced Error Reporting
>>>         Capabilities: [148] Virtual Channel
>>>         Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
>>>         Capabilities: [178] Latency Tolerance Reporting
>>>         Capabilities: [180] L1 PM Substates
>>>         Kernel driver in use: ath10k_pci
>>>         Kernel modules: ath10k_pci
>>>
>>>> I would interested in knowing from where you got your drivers/board
>>>> files. I had to download mine from my laptop manufacturer's (MSI)
>>>> website.
>>> I mounted the preinstalled Windows 8 partition on /mnt and run:
>>> find /mnt -iname '*.bin'
>>>
>>> The same files can be found inside the driver installer on the Alienware
>>> (Dell) website.
>>>
>>> Regards,
>>> Gabriele
>>>
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k

-- 

*Gabriele Martino*

Linux Sysadmin & Web Development

g.martino@gmx.com



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

Re: QCA6174 hw2.1?

[Moritz Morawietz]

Hi!

I have the same problems with my card (also a Killer N1525). It seems
you've done it, but i can't figure out how.

Do i need to build and use kvalo's kernel, or is it enough to build
the modules ath10k_core & ath10k_pci?
I'm a bit afraid of compiling the whole kernel ^^
output of uname -a:
Linux companion 4.0.0-2-ARCH #1 SMP PREEMPT Tue Apr 14 07:14:46 CEST
2015 x86_64 GNU/Linux

I have the disassembly.py, but cannot find the dissect.py, can you
provide the link? Or, even better, the assembled files?


Many thanks for help!

Moritz

2015-04-27 2:21 GMT+02:00 Gabriele Martino <g.martino@gmx.com>:
> Just tried the kvalo's kernel.
> NetworkManager connected flawlessly at boot to my WPA2 home network on
> 2.4GHz. Will try 5GHz later.
> iwconfig reports a fixed 1Mb/s bitrate, but I can copy files to my nas
> (smb share) at about 3.3MB/s.
> That's a reasonable speed for b/g wireless.
>
> iwconfig:
> wlp3s0    IEEE 802.11abgn  ESSID:"W-I-SEE-YOU-N"
>           Mode:Managed  Frequency:2.412 GHz  Access Point:
> 40:16:7E:2C:79:90
>           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=59/70  Signal level=-51 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:42   Missed beacon:0
>
> iwlist scan (part of):
> wlp3s0    Scan completed :
>           Cell 01 - Address: 40:16:7E:2C:79:90
>                     Channel:1
>                     Frequency:2.412 GHz (Channel 1)
>                     Quality=60/70  Signal level=-50 dBm
>                     Encryption key:on
>                     ESSID:"W-I-SEE-YOU-N"
>                     Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
>                               24 Mb/s; 36 Mb/s; 54 Mb/s
>                     Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
>                     Mode:Master
>                     Extra:tsf=00000005244f5a5d
>                     Extra: Last beacon: 33ms ago
>                     IE: Unknown: 000D572D492D5345452D594F552D4E
>                     IE: Unknown: 010882848B962430486C
>                     IE: Unknown: 030101
>                     IE: Unknown: 2A0104
>                     IE: Unknown: 2F0104
>                     IE: IEEE 802.11i/WPA2 Version 1
>                         Group Cipher : CCMP
>                         Pairwise Ciphers (1) : CCMP
>                         Authentication Suites (1) : PSK
>
> dmesg output:
> [    2.212106] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
> [    2.212558] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0
> [    2.368318] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [    2.368971] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2
> [    2.368974] ath10k_pci 0000:03:00.0: failed to load spec board file,
> falling back to generic: -2
> [    2.369252] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
> [    2.369270] ath10k_pci 0000:03:00.0: could not fetch firmware file
> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
> [    3.559021] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
> 0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
> 3.0 wmi 4 cal otp max_sta 32
> [    3.559024] ath10k_pci 0000:03:00.0: debug 1 debugfs 0 tracing 0 dfs
> 0 testmode 0
> [    3.623733] ath: EEPROM regdomain: 0x6c
> [    3.623735] ath: EEPROM indicates we should expect a direct regpair map
> [    3.623736] ath: Country alpha2 being used: 00
> [    3.623737] ath: Regpair used: 0x6c
> [    3.638102] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
> [    7.523617] ath10k_pci 0000:03:00.0: no channel configured; ignoring
> frame(s)!
> [    7.627173] ath10k_pci 0000:03:00.0: no channel configured; ignoring
> frame(s)!
> [   12.149947] wlp3s0: authenticate with 40:16:7e:2c:79:90
> [   12.183915] wlp3s0: send auth to 40:16:7e:2c:79:90 (try 1/3)
> [   12.185559] wlp3s0: authenticated
> [   12.186043] wlp3s0: associate with 40:16:7e:2c:79:90 (try 1/3)
> [   12.189402] wlp3s0: RX AssocResp from 40:16:7e:2c:79:90 (capab=0x411
> status=0 aid=3)
> [   12.192174] wlp3s0: associated
> [  313.912952] wlp3s0: AP 40:16:7e:2c:79:90 changed bandwidth, new
> config is 2412 MHz, width 1 (2412/0 MHz)
> [  313.912955] wlp3s0: AP 40:16:7e:2c:79:90 changed bandwidth in a way
> we can't support - disconnect
> [  318.709453] wlp3s0: authenticate with 40:16:7e:2c:79:90
> [  318.750807] wlp3s0: send auth to 40:16:7e:2c:79:90 (try 1/3)
> [  318.752541] wlp3s0: authenticated
> [  318.753030] wlp3s0: associate with 40:16:7e:2c:79:90 (try 1/3)
> [  318.756524] wlp3s0: RX AssocResp from 40:16:7e:2c:79:90 (capab=0x411
> status=0 aid=1)
> [  318.759082] wlp3s0: associated
>
> I'm using the board file "eeprom_qca9377_1p0_NFA435_olpc.bin".
>
> Regards,
> Gabriele
>
>
> On 26/04/2015 16:10, Gabriele Martino wrote:
>> Hi Corin,
>> the "dissect.py" script seems to work better than the "disassemble.py":
>>
>> [ 6483.455435] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>> irq_mode 0 reset_mode 0
>> [ 6483.600747] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>> [ 6484.772417] ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
>> [ 6484.772433] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
>> 0x003405ff) fw killer-n1525-fw api 4 htt 0.0 wmi 4 cal otp max_sta 32
>> [ 6484.772435] ath10k_pci 0000:03:00.0: debug 1 debugfs 0 tracing 0 dfs
>> 0 testmode 0
>> [ 6484.773333] ath10k_pci 0000:03:00.0: firmware register dump:
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [00]: 0x05010000 0x000015B3
>> 0x0095186B 0x00955B31
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [04]: 0x0095186B 0x00060130
>> 0x00000010 0x0040AF04
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [08]: 0x00000018 0x00000001
>> 0x00000001 0x00412250
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [12]: 0x00000009 0x00000000
>> 0x0096C09C 0x0096C0A7
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [16]: 0x0096BDBC 0x009286B6
>> 0x00000000 0x00000000
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [20]: 0x4095186B 0x0040E160
>> 0x0041F82C 0x00000001
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [24]: 0x80936238 0x0040E1C0
>> 0x00000000 0xC095186B
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [28]: 0x80936361 0x0040E1E0
>> 0x00000000 0x0041C8DC
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [32]: 0x80934A67 0x0040E200
>> 0x00436DF0 0x0040E250
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [36]: 0x809A5C92 0x0040E250
>> 0x004275B0 0x00000001
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [40]: 0x809A5CEA 0x0040E290
>> 0x00426F40 0x00000004
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [44]: 0x809A5DCA 0x0040E2B0
>> 0x00426F40 0x0041C8DC
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [48]: 0x800A0909 0x0040E2D0
>> 0x00426F40 0x004275A0
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [52]: 0x800A024A 0x0040E2F0
>> 0x0041ABB0 0x00420440
>> [ 6484.773333] ath10k_pci 0000:03:00.0: [56]: 0x809287D9 0x0040E310
>> 0x00000000 0x00400000
>> [ 6485.765040] ath10k_pci 0000:03:00.0: failed to receive control
>> response completion, polling..
>> [ 6486.765027] ath10k_pci 0000:03:00.0: ctl_resp never came in (-110)
>> [ 6486.765032] ath10k_pci 0000:03:00.0: failed to connect to HTC: -110
>> [ 6486.828658] ath10k_pci 0000:03:00.0: could not init core (-110)
>> [ 6486.828689] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>> [ 6486.831175] ath10k_pci 0000:03:00.0: cannot restart a device that
>> hasn't been started
>>
>> Well, at least it loads correctly. This should be the firmware crash
>> fixed in the patches, it's time to test kvalo's kernel sources.
>>
>>
>> On 26/04/2015 05:51, Corin Lawson wrote:
>>> Hi Gabriele,
>>>
>>> I think we have the same card (the vendor and device ids are the
>>> determining factor):
>>>
>>>     $ lspci -n -s 05:00.0
>>>     05:00.0 0280: 168c:003e (rev 20)
>>>
>>> Without the skip_otp option I get this in dmesg:
>>>
>>>     [18396.622576] ath10k_pci 0000:05:00.0: pci irq msi interrupts 1
>>> irq_mode 0 reset_mode 0
>>>     [18396.768593] ath10k_pci 0000:05:00.0: Direct firmware load for
>>> ath10k/cal-pci-0000:05:00.0.bin failed with error -2
>>>     [18396.847975] ath10k_pci 0000:05:00.0: otp calibration failed: 3
>>>     [18396.847977] ath10k_pci 0000:05:00.0: failed to run otp: -22
>>>     [18396.847978] ath10k_pci 0000:05:00.0: could not init core (-22)
>>>     [18396.847995] ath10k_pci 0000:05:00.0: could not probe fw (-22)
>>>
>>> Which is different to your messages. I'm taking a guess here, but
>>> those DMAR messages seem to indicate that the firmware is attempting
>>> to write to the wrong part of memory (i.e. wrong firmware).
>>>
>>> Using kvalo's kernel fork is probably a good step (it contains those
>>> necessary patches). If you still don't get it working, then my only
>>> other idea is to try that dissect.py gist I mentioned previously. Here
>>> are the commands that worked for me:
>>>
>>>     # python dissect.py <
>>> drivers/Production/Windows8.1-x64/k1525w81/qca61x420.bin
>>>     # python assemble.py killer-n1525-fw 0 fw-2.bin fw-1.bin 4 >
>>> /lib/firmware/ath10k/QCA6174/hw2.1/firmware-4.bin
>>>
>>> The dissect.py script produced fw-1.bin which is the otp file and
>>> fw-2.bin which is the correct firmware (don't quote me on that, but it
>>> worked for me). As for your board.bin file, you need to check the .inf
>>> file that comes with your drivers. I'm not sure what the structure of
>>> that file is... for all I know I could be using the wrong board
>>> file...
>>>
>>> I hope this helps, otherwise you've reached the limits of my
>>> experience :) Maybe someone else on the list has a better idea?
>>>
>>> Cheers,
>>> Corin
>>>
>>>
>>> On Sat, Apr 25, 2015 at 10:58 PM, Gabriele Martino <g.martino@gmx.com> wrote:
>>>> On 25/04/2015 05:47, Corin Lawson wrote:
>>>>> I also had problems with calibration, I had to pass skip_otp=y to the module:
>>>>>
>>>>>     $ cat /etc/modprobe.d/ath10k.conf
>>>>>     options ath10k_core skip_otp=y
>>>> Hi Corin,
>>>> I removed ath10k_pci, ath10k_core and ath before loading ath10k_core
>>>> with skip_otp=1, but nothing happened:
>>>>
>>>> [ 1808.473874] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>>>> irq_mode 0 reset_mode 0
>>>> [ 1808.618770] ath10k_pci 0000:03:00.0: Direct firmware load for
>>>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>>>> [ 1808.687492] dmar: DRHD: handling fault status reg 2
>>>> [ 1808.687506] dmar: DMAR:[DMA Write] Request device [03:00.0] fault
>>>> addr 7ee00000
>>>>                DMAR:[fault reason 05] PTE Write access is not set
>>>> [ 1809.688015] ath10k_pci 0000:03:00.0: unable to write to the device
>>>> [ 1809.688018] ath10k_pci 0000:03:00.0: failed to download normal
>>>> firmware: -110
>>>> [ 1809.688020] ath10k_pci 0000:03:00.0: could not init core (-110)
>>>> [ 1809.688054] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>>>>
>>>> I assembled the otp.bin with fw.bin to get the blob, so I'm not sure
>>>> skip_otp will fix this...
>>>> Now I'm cloning the kvalo's kernel tree, this should be faster than
>>>> picking the single patches.
>>>>
>>>>> FWIW:
>>>>>
>>>>>     $ lspci -vs 05:00.0
>>>>>     05:00.0 Network controller: Qualcomm Atheros Device 003e (rev 20)
>>>>>             Subsystem: Bigfoot Networks, Inc. Device 1525
>>>>>             Flags: bus master, fast devsel, latency 0, IRQ 31
>>>>>             Memory at f7800000 (64-bit, non-prefetchable) [size=2M]
>>>>>             Capabilities: <access denied>
>>>>>             Kernel driver in use: ath10k_pci
>>>>>             Kernel modules: ath10k_pci
>>>> Well, mine seems a bit different:
>>>>
>>>> 03:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
>>>> Network Adapter (rev 20)
>>>>         Subsystem: Bigfoot Networks, Inc. Killer N1525 Wireless-AC
>>>>         Flags: bus master, fast devsel, latency 0, IRQ 32
>>>>         Memory at f6800000 (64-bit, non-prefetchable) [size=2M]
>>>>         Capabilities: [40] Power Management version 3
>>>>         Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
>>>>         Capabilities: [70] Express Endpoint, MSI 00
>>>>         Capabilities: [100] Advanced Error Reporting
>>>>         Capabilities: [148] Virtual Channel
>>>>         Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
>>>>         Capabilities: [178] Latency Tolerance Reporting
>>>>         Capabilities: [180] L1 PM Substates
>>>>         Kernel driver in use: ath10k_pci
>>>>         Kernel modules: ath10k_pci
>>>>
>>>>> I would interested in knowing from where you got your drivers/board
>>>>> files. I had to download mine from my laptop manufacturer's (MSI)
>>>>> website.
>>>> I mounted the preinstalled Windows 8 partition on /mnt and run:
>>>> find /mnt -iname '*.bin'
>>>>
>>>> The same files can be found inside the driver installer on the Alienware
>>>> (Dell) website.
>>>>
>>>> Regards,
>>>> Gabriele
>>>>
>>> _______________________________________________
>>> ath10k mailing list
>>> ath10k@lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/ath10k
>
> --
>
> *Gabriele Martino*
>
> Linux Sysadmin & Web Development
>
> g.martino@gmx.com
>
>
>
> _______________________________________________
> 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

Re: QCA6174 hw2.1?

[Gabriele Martino]

On 27/04/2015 16:00, Moritz Morawietz wrote:
> Hi!
>
> I have the same problems with my card (also a Killer N1525). It seems
> you've done it, but i can't figure out how.
>
> Do i need to build and use kvalo's kernel, or is it enough to build
> the modules ath10k_core & ath10k_pci?
> I'm a bit afraid of compiling the whole kernel ^^
> output of uname -a:
> Linux companion 4.0.0-2-ARCH #1 SMP PREEMPT Tue Apr 14 07:14:46 CEST
> 2015 x86_64 GNU/Linux
The modules should be enough. Tell us if it works.
Compiling a whole kernel isn't too hard if you already have a working
configuration.

> I have the disassembly.py, but cannot find the dissect.py, can you
> provide the link? Or, even better, the assembled files?
I won't upload the assembled files now, I don't know if I can get
licensing issues.
You can find the dissect.py script here:
http://lists.infradead.org/pipermail/ath10k/2015-April/005074.html

Good luck!

Regards,
Gabriele


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

Re: QCA6174 hw2.1?

[Moritz Morawietz]

Many thanks for your fast help!

I've made some progress, but ran into other problems.
If i compile ath10_pci, ath10k_core and ath from kvalo's tree and load
them, i get following dmesg output:

[    2.980448] ath10k_pci 0000:06:00.0: enabling device (0000 -> 0002)
[    2.980750] ath10k_pci 0000:06:00.0: pci irq msi-x interrupts 8
irq_mode 0 reset_mode 0
[    3.158860] ath10k_pci 0000:06:00.0: Direct firmware load for
ath10k/cal-pci-0000:06:00.0.bin failed with error -2
[    3.159611] 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
[    3.159613] ath10k_pci 0000:06:00.0: failed to load spec board
file, falling back to generic: -2
[    3.159922] ath10k_pci 0000:06:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[    3.159924] ath10k_pci 0000:06:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
[    4.360946] ath10k_pci 0000:06:00.0: qca6174 hw2.1 (0x05010000,
0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
3.1 wmi 4 cal otp max_sta 32
[    4.360950] ath10k_pci 0000:06:00.0: debug 1 debugfs 1 tracing 1
dfs 0 testmode 0
[    4.430068] ath: EEPROM regdomain: 0x6c
[    4.430070] ath: EEPROM indicates we should expect a direct regpair map
[    4.430072] ath: Country alpha2 being used: 00
[    4.430072] ath: Regpair used: 0x6c
[    4.430078] ath10k_pci 0000:06:00.0: failed to register ieee80211: -22
[    4.430097] ath10k_pci 0000:06:00.0: could not register to mac80211 (-22)

So I compiled mac80211, and tried to load it. What i get is a load of
that messages:

[  226.812494] mac80211: Unknown symbol cfg80211_cqm_rssi_notify (err -22)
[  226.812497] mac80211: disagrees about version of symbol cfg80211_auth_timeout
[  226.812497] mac80211: Unknown symbol cfg80211_auth_timeout (err -22)
[  226.812498] mac80211: disagrees about version of symbol
cfg80211_rx_unprot_mlme_mgmt
[  226.812499] mac80211: Unknown symbol cfg80211_rx_unprot_mlme_mgmt (err -22)

Because mac80211 depends on cfg80211, i compilied and tested it. The
error messages reduced to

[  632.208849] mac80211: Unknown symbol rhashtable_insert_rehash (err 0)
[  632.208881] mac80211: Unknown symbol rhashtable_insert_slow (err 0)

Know I'm stuck. I'll try to compile and use the whole kernel (it's
compiling right now), but would prefer to just change the modules.

The firmware-4.bin is assembled like described in this thread, as
board.bin i used eeprom_qca9377_1p0_NFA435_olpc.bin.

Any Ideas? :)

Happy greetings
Moritz

2015-04-27 23:56 GMT+02:00 Corin Lawson <me@corinlawson.com.au>:
> Gabriele is right it is only the modules that need to be built kvalo's
> kernel
>
> On 28 Apr 2015 1:05 am, "Gabriele Martino" <g.martino@gmx.com> wrote:
>>
>> On 27/04/2015 16:00, Moritz Morawietz wrote:
>> > Hi!
>> >
>> > I have the same problems with my card (also a Killer N1525). It seems
>> > you've done it, but i can't figure out how.
>> >
>> > Do i need to build and use kvalo's kernel, or is it enough to build
>> > the modules ath10k_core & ath10k_pci?
>> > I'm a bit afraid of compiling the whole kernel ^^
>> > output of uname -a:
>> > Linux companion 4.0.0-2-ARCH #1 SMP PREEMPT Tue Apr 14 07:14:46 CEST
>> > 2015 x86_64 GNU/Linux
>> The modules should be enough. Tell us if it works.
>> Compiling a whole kernel isn't too hard if you already have a working
>> configuration.
>>
>> > I have the disassembly.py, but cannot find the dissect.py, can you
>> > provide the link? Or, even better, the assembled files?
>> I won't upload the assembled files now, I don't know if I can get
>> licensing issues.
>> You can find the dissect.py script here:
>> http://lists.infradead.org/pipermail/ath10k/2015-April/005074.html
>>
>> Good luck!
>>
>> Regards,
>> Gabriele
>>
>>
>> _______________________________________________
>> 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

Re: QCA6174 hw2.1?

[Gabriele Martino]

On 28/04/2015 13:55, Moritz Morawietz wrote:
> Many thanks for your fast help!
>
> I've made some progress, but ran into other problems.
> If i compile ath10_pci, ath10k_core and ath from kvalo's tree and load
> them, i get following dmesg output:
>
> [    2.980448] ath10k_pci 0000:06:00.0: enabling device (0000 -> 0002)
> [    2.980750] ath10k_pci 0000:06:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0
> [    3.158860] ath10k_pci 0000:06:00.0: Direct firmware load for
> ath10k/cal-pci-0000:06:00.0.bin failed with error -2
> [    3.159611] 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
> [    3.159613] ath10k_pci 0000:06:00.0: failed to load spec board
> file, falling back to generic: -2
> [    3.159922] ath10k_pci 0000:06:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
> [    3.159924] ath10k_pci 0000:06:00.0: could not fetch firmware file
> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
> [    4.360946] ath10k_pci 0000:06:00.0: qca6174 hw2.1 (0x05010000,
> 0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
> 3.1 wmi 4 cal otp max_sta 32
> [    4.360950] ath10k_pci 0000:06:00.0: debug 1 debugfs 1 tracing 1
> dfs 0 testmode 0
> [    4.430068] ath: EEPROM regdomain: 0x6c
> [    4.430070] ath: EEPROM indicates we should expect a direct regpair map
> [    4.430072] ath: Country alpha2 being used: 00
> [    4.430072] ath: Regpair used: 0x6c
> [    4.430078] ath10k_pci 0000:06:00.0: failed to register ieee80211: -22
> [    4.430097] ath10k_pci 0000:06:00.0: could not register to mac80211 (-22)
>
> So I compiled mac80211, and tried to load it. What i get is a load of
> that messages:
>
> [  226.812494] mac80211: Unknown symbol cfg80211_cqm_rssi_notify (err -22)
> [  226.812497] mac80211: disagrees about version of symbol cfg80211_auth_timeout
> [  226.812497] mac80211: Unknown symbol cfg80211_auth_timeout (err -22)
> [  226.812498] mac80211: disagrees about version of symbol
> cfg80211_rx_unprot_mlme_mgmt
> [  226.812499] mac80211: Unknown symbol cfg80211_rx_unprot_mlme_mgmt (err -22)
>
> Because mac80211 depends on cfg80211, i compilied and tested it. The
> error messages reduced to
>
> [  632.208849] mac80211: Unknown symbol rhashtable_insert_rehash (err 0)
> [  632.208881] mac80211: Unknown symbol rhashtable_insert_slow (err 0)
>
> Know I'm stuck. I'll try to compile and use the whole kernel (it's
> compiling right now), but would prefer to just change the modules.
I could find some references to "rhashtable_insert_rehash" with grep:
/usr/src/linux/lib/rhashtable.c:int rhashtable_insert_rehash(struct
rhashtable *ht)
/usr/src/linux/lib/rhashtable.c:EXPORT_SYMBOL_GPL(rhashtable_insert_rehash);

This file is present in 3.18.11 kernel (I don't have older sources on
this laptop).
Which distribution and kernel are you using?
You are compiling 4.0 (-> 3.20) modules, so you're likely to get strange
issues if your kernel is too old.

Regards,
Gabriele


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

Re: QCA6174 hw2.1?

[Moritz Morawietz]

I used  4.0.0-2. Also i had one kernel build where it worked, but,
because I didn't knew that you have to install nvidia drivers again, I
deletet it. I am not sure how i did it, so I'm currently trying again.
Maybe I need to understand the patching mechanisms, guess that would
help :D I did something with git…

Thank you a lot for your help so far!

2015-04-30 2:07 GMT+02:00 Gabriele Martino <g.martino@gmx.com>:
> On 28/04/2015 13:55, Moritz Morawietz wrote:
>> Many thanks for your fast help!
>>
>> I've made some progress, but ran into other problems.
>> If i compile ath10_pci, ath10k_core and ath from kvalo's tree and load
>> them, i get following dmesg output:
>>
>> [    2.980448] ath10k_pci 0000:06:00.0: enabling device (0000 -> 0002)
>> [    2.980750] ath10k_pci 0000:06:00.0: pci irq msi-x interrupts 8
>> irq_mode 0 reset_mode 0
>> [    3.158860] ath10k_pci 0000:06:00.0: Direct firmware load for
>> ath10k/cal-pci-0000:06:00.0.bin failed with error -2
>> [    3.159611] 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
>> [    3.159613] ath10k_pci 0000:06:00.0: failed to load spec board
>> file, falling back to generic: -2
>> [    3.159922] ath10k_pci 0000:06:00.0: Direct firmware load for
>> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>> [    3.159924] ath10k_pci 0000:06:00.0: could not fetch firmware file
>> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
>> [    4.360946] ath10k_pci 0000:06:00.0: qca6174 hw2.1 (0x05010000,
>> 0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
>> 3.1 wmi 4 cal otp max_sta 32
>> [    4.360950] ath10k_pci 0000:06:00.0: debug 1 debugfs 1 tracing 1
>> dfs 0 testmode 0
>> [    4.430068] ath: EEPROM regdomain: 0x6c
>> [    4.430070] ath: EEPROM indicates we should expect a direct regpair map
>> [    4.430072] ath: Country alpha2 being used: 00
>> [    4.430072] ath: Regpair used: 0x6c
>> [    4.430078] ath10k_pci 0000:06:00.0: failed to register ieee80211: -22
>> [    4.430097] ath10k_pci 0000:06:00.0: could not register to mac80211 (-22)
>>
>> So I compiled mac80211, and tried to load it. What i get is a load of
>> that messages:
>>
>> [  226.812494] mac80211: Unknown symbol cfg80211_cqm_rssi_notify (err -22)
>> [  226.812497] mac80211: disagrees about version of symbol cfg80211_auth_timeout
>> [  226.812497] mac80211: Unknown symbol cfg80211_auth_timeout (err -22)
>> [  226.812498] mac80211: disagrees about version of symbol
>> cfg80211_rx_unprot_mlme_mgmt
>> [  226.812499] mac80211: Unknown symbol cfg80211_rx_unprot_mlme_mgmt (err -22)
>>
>> Because mac80211 depends on cfg80211, i compilied and tested it. The
>> error messages reduced to
>>
>> [  632.208849] mac80211: Unknown symbol rhashtable_insert_rehash (err 0)
>> [  632.208881] mac80211: Unknown symbol rhashtable_insert_slow (err 0)
>>
>> Know I'm stuck. I'll try to compile and use the whole kernel (it's
>> compiling right now), but would prefer to just change the modules.
> I could find some references to "rhashtable_insert_rehash" with grep:
> /usr/src/linux/lib/rhashtable.c:int rhashtable_insert_rehash(struct
> rhashtable *ht)
> /usr/src/linux/lib/rhashtable.c:EXPORT_SYMBOL_GPL(rhashtable_insert_rehash);
>
> This file is present in 3.18.11 kernel (I don't have older sources on
> this laptop).
> Which distribution and kernel are you using?
> You are compiling 4.0 (-> 3.20) modules, so you're likely to get strange
> issues if your kernel is too old.
>
> Regards,
> Gabriele
>
>
> _______________________________________________
> 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

Re: QCA6174 hw2.1?

[Jason H]

I just wanted to check in and see what the status of support was for this hardware. I saw a few messages since I last posted.
I also need Linux 4 kernel for other issues with the hardware. 

Thanks!


> Sent: Thursday, April 30, 2015 at 9:03 AM
> From: "Moritz Morawietz" <moritz.morawietz@informatik.uni-oldenburg.de>
> To: ath10k@lists.infradead.org
> Subject: Re: QCA6174 hw2.1?
>
> I used  4.0.0-2. Also i had one kernel build where it worked, but,
> because I didn't knew that you have to install nvidia drivers again, I
> deletet it. I am not sure how i did it, so I'm currently trying again.
> Maybe I need to understand the patching mechanisms, guess that would
> help :D I did something with git…
> 
> Thank you a lot for your help so far!
> 
> 2015-04-30 2:07 GMT+02:00 Gabriele Martino <g.martino@gmx.com>:
> > On 28/04/2015 13:55, Moritz Morawietz wrote:
> >> Many thanks for your fast help!
> >>
> >> I've made some progress, but ran into other problems.
> >> If i compile ath10_pci, ath10k_core and ath from kvalo's tree and load
> >> them, i get following dmesg output:
> >>
> >> [    2.980448] ath10k_pci 0000:06:00.0: enabling device (0000 -> 0002)
> >> [    2.980750] ath10k_pci 0000:06:00.0: pci irq msi-x interrupts 8
> >> irq_mode 0 reset_mode 0
> >> [    3.158860] ath10k_pci 0000:06:00.0: Direct firmware load for
> >> ath10k/cal-pci-0000:06:00.0.bin failed with error -2
> >> [    3.159611] 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
> >> [    3.159613] ath10k_pci 0000:06:00.0: failed to load spec board
> >> file, falling back to generic: -2
> >> [    3.159922] ath10k_pci 0000:06:00.0: Direct firmware load for
> >> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
> >> [    3.159924] ath10k_pci 0000:06:00.0: could not fetch firmware file
> >> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
> >> [    4.360946] ath10k_pci 0000:06:00.0: qca6174 hw2.1 (0x05010000,
> >> 0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
> >> 3.1 wmi 4 cal otp max_sta 32
> >> [    4.360950] ath10k_pci 0000:06:00.0: debug 1 debugfs 1 tracing 1
> >> dfs 0 testmode 0
> >> [    4.430068] ath: EEPROM regdomain: 0x6c
> >> [    4.430070] ath: EEPROM indicates we should expect a direct regpair map
> >> [    4.430072] ath: Country alpha2 being used: 00
> >> [    4.430072] ath: Regpair used: 0x6c
> >> [    4.430078] ath10k_pci 0000:06:00.0: failed to register ieee80211: -22
> >> [    4.430097] ath10k_pci 0000:06:00.0: could not register to mac80211 (-22)
> >>
> >> So I compiled mac80211, and tried to load it. What i get is a load of
> >> that messages:
> >>
> >> [  226.812494] mac80211: Unknown symbol cfg80211_cqm_rssi_notify (err -22)
> >> [  226.812497] mac80211: disagrees about version of symbol cfg80211_auth_timeout
> >> [  226.812497] mac80211: Unknown symbol cfg80211_auth_timeout (err -22)
> >> [  226.812498] mac80211: disagrees about version of symbol
> >> cfg80211_rx_unprot_mlme_mgmt
> >> [  226.812499] mac80211: Unknown symbol cfg80211_rx_unprot_mlme_mgmt (err -22)
> >>
> >> Because mac80211 depends on cfg80211, i compilied and tested it. The
> >> error messages reduced to
> >>
> >> [  632.208849] mac80211: Unknown symbol rhashtable_insert_rehash (err 0)
> >> [  632.208881] mac80211: Unknown symbol rhashtable_insert_slow (err 0)
> >>
> >> Know I'm stuck. I'll try to compile and use the whole kernel (it's
> >> compiling right now), but would prefer to just change the modules.
> > I could find some references to "rhashtable_insert_rehash" with grep:
> > /usr/src/linux/lib/rhashtable.c:int rhashtable_insert_rehash(struct
> > rhashtable *ht)
> > /usr/src/linux/lib/rhashtable.c:EXPORT_SYMBOL_GPL(rhashtable_insert_rehash);
> >
> > This file is present in 3.18.11 kernel (I don't have older sources on
> > this laptop).
> > Which distribution and kernel are you using?
> > You are compiling 4.0 (-> 3.20) modules, so you're likely to get strange
> > issues if your kernel is too old.
> >
> > Regards,
> > Gabriele
> >
> >
> > _______________________________________________
> > 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
>

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

Re: QCA6174 hw2.1?

[Anton Romanov]

Works fine for me with this patch
https://patchwork.kernel.org/patch/6387631/  at least
I am currently using self-extracted firmware but the one in the pr for
ath10k-firmware worked fine as well iirc.
I'm using that on Alienware 15 laptop with "Killer N1525"

On Wed, May 20, 2015 at 8:17 AM, Jason H <jhihn@gmx.com> wrote:
> I just wanted to check in and see what the status of support was for this hardware. I saw a few messages since I last posted.
> I also need Linux 4 kernel for other issues with the hardware.
>
> Thanks!
>
>
>> Sent: Thursday, April 30, 2015 at 9:03 AM
>> From: "Moritz Morawietz" <moritz.morawietz@informatik.uni-oldenburg.de>
>> To: ath10k@lists.infradead.org
>> Subject: Re: QCA6174 hw2.1?
>>
>> I used  4.0.0-2. Also i had one kernel build where it worked, but,
>> because I didn't knew that you have to install nvidia drivers again, I
>> deletet it. I am not sure how i did it, so I'm currently trying again.
>> Maybe I need to understand the patching mechanisms, guess that would
>> help :D I did something with git…
>>
>> Thank you a lot for your help so far!
>>
>> 2015-04-30 2:07 GMT+02:00 Gabriele Martino <g.martino@gmx.com>:
>> > On 28/04/2015 13:55, Moritz Morawietz wrote:
>> >> Many thanks for your fast help!
>> >>
>> >> I've made some progress, but ran into other problems.
>> >> If i compile ath10_pci, ath10k_core and ath from kvalo's tree and load
>> >> them, i get following dmesg output:
>> >>
>> >> [    2.980448] ath10k_pci 0000:06:00.0: enabling device (0000 -> 0002)
>> >> [    2.980750] ath10k_pci 0000:06:00.0: pci irq msi-x interrupts 8
>> >> irq_mode 0 reset_mode 0
>> >> [    3.158860] ath10k_pci 0000:06:00.0: Direct firmware load for
>> >> ath10k/cal-pci-0000:06:00.0.bin failed with error -2
>> >> [    3.159611] 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
>> >> [    3.159613] ath10k_pci 0000:06:00.0: failed to load spec board
>> >> file, falling back to generic: -2
>> >> [    3.159922] ath10k_pci 0000:06:00.0: Direct firmware load for
>> >> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>> >> [    3.159924] ath10k_pci 0000:06:00.0: could not fetch firmware file
>> >> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
>> >> [    4.360946] ath10k_pci 0000:06:00.0: qca6174 hw2.1 (0x05010000,
>> >> 0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
>> >> 3.1 wmi 4 cal otp max_sta 32
>> >> [    4.360950] ath10k_pci 0000:06:00.0: debug 1 debugfs 1 tracing 1
>> >> dfs 0 testmode 0
>> >> [    4.430068] ath: EEPROM regdomain: 0x6c
>> >> [    4.430070] ath: EEPROM indicates we should expect a direct regpair map
>> >> [    4.430072] ath: Country alpha2 being used: 00
>> >> [    4.430072] ath: Regpair used: 0x6c
>> >> [    4.430078] ath10k_pci 0000:06:00.0: failed to register ieee80211: -22
>> >> [    4.430097] ath10k_pci 0000:06:00.0: could not register to mac80211 (-22)
>> >>
>> >> So I compiled mac80211, and tried to load it. What i get is a load of
>> >> that messages:
>> >>
>> >> [  226.812494] mac80211: Unknown symbol cfg80211_cqm_rssi_notify (err -22)
>> >> [  226.812497] mac80211: disagrees about version of symbol cfg80211_auth_timeout
>> >> [  226.812497] mac80211: Unknown symbol cfg80211_auth_timeout (err -22)
>> >> [  226.812498] mac80211: disagrees about version of symbol
>> >> cfg80211_rx_unprot_mlme_mgmt
>> >> [  226.812499] mac80211: Unknown symbol cfg80211_rx_unprot_mlme_mgmt (err -22)
>> >>
>> >> Because mac80211 depends on cfg80211, i compilied and tested it. The
>> >> error messages reduced to
>> >>
>> >> [  632.208849] mac80211: Unknown symbol rhashtable_insert_rehash (err 0)
>> >> [  632.208881] mac80211: Unknown symbol rhashtable_insert_slow (err 0)
>> >>
>> >> Know I'm stuck. I'll try to compile and use the whole kernel (it's
>> >> compiling right now), but would prefer to just change the modules.
>> > I could find some references to "rhashtable_insert_rehash" with grep:
>> > /usr/src/linux/lib/rhashtable.c:int rhashtable_insert_rehash(struct
>> > rhashtable *ht)
>> > /usr/src/linux/lib/rhashtable.c:EXPORT_SYMBOL_GPL(rhashtable_insert_rehash);
>> >
>> > This file is present in 3.18.11 kernel (I don't have older sources on
>> > this laptop).
>> > Which distribution and kernel are you using?
>> > You are compiling 4.0 (-> 3.20) modules, so you're likely to get strange
>> > issues if your kernel is too old.
>> >
>> > Regards,
>> > Gabriele
>> >
>> >
>> > _______________________________________________
>> > 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
>>
>
> _______________________________________________
> 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

Re: QCA6174 hw2.1?

[Gabriele Martino]

I'm using the kvalo's kernel (4.1-rc3) without the patch, sometimes the
adapter loses connection but it's bearable.
I'll try that patch later. Killer N1525 on Alienware 15.

OT: Anton, does the headphone jack work correctly on your Alienware 15?
I sent a patch to the ALSA team about that.

On 21/05/2015 07:29, Anton Romanov wrote:
> Works fine for me with this patch
> https://patchwork.kernel.org/patch/6387631/  at least
> I am currently using self-extracted firmware but the one in the pr for
> ath10k-firmware worked fine as well iirc.
> I'm using that on Alienware 15 laptop with "Killer N1525"
>
> On Wed, May 20, 2015 at 8:17 AM, Jason H <jhihn@gmx.com> wrote:
>> I just wanted to check in and see what the status of support was for this hardware. I saw a few messages since I last posted.
>> I also need Linux 4 kernel for other issues with the hardware.
>>
>> Thanks!


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