Hi,
There are a few bugs on the linux bug tracker relating to this. Just
thought I would post this to the list as they all look quite alike. I am
hoping someone on this list understands the nature of the issue.
https://bugzilla.kernel.org/show_bug.cgi?id=193141
This file uses the new format which contains multiple board files for various
boards.
Signed-off-by: Kalle Valo <kv...@qca.qualcomm.com>
---
WHENCE |1 +
ath10k/QCA6174/hw2.1/board-2.bin | Bin
2 files changed, 1 insertion(+)
create mode 100644 ath10k/Q
m>
An: "Roman Bange" <mofasofa...@gmx.de>
Cc: ath10k <ath10k@lists.infradead.org>
Betreff: Re: QCA6174 hw2.1 Firmware crash when connecting to a 5GHz network
On 18 November 2015 at 16:28, Roman Bange <mofasofa...@gmx.de> wrote:
> Hey,
>
> im getting a firmwa
On 18 November 2015 at 16:28, Roman Bange wrote:
> Hey,
>
> im getting a firmware crash when i try to connect to a 5GHz network.
> I tested the older firmware WLAN.RM.1.1-00141, which is now provided in
> linux-firmware, and SW_RM.1.1.1-00157-QCARMSWPZ-1, which is provided by
000:03:00.0: boot qca6174 chip reset complete
>> (cold)
>> [ 16.369195] ath10k_pci :03:00.0: boot init ce src ring id 0
>> entries 16 base_addr 88003f00a000
>> [ 16.369212] ath10k_pci :03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr 88003f3c800
On 26 August 2015 at 12:05, Lapo Calamandrei calamand...@gmail.com wrote:
2015-08-26 7:01 GMT+02:00 Michal Kazior michal.kaz...@tieto.com:
On 25 August 2015 at 16:04, Lapo Calamandrei calamand...@gmail.com wrote:
[...]
Yep, the previous crash was without your patch applied, the following
is
2015-08-26 7:01 GMT+02:00 Michal Kazior michal.kaz...@tieto.com:
On 25 August 2015 at 16:04, Lapo Calamandrei calamand...@gmail.com wrote:
[...]
Yep, the previous crash was without your patch applied, the following
is with the patch applied though.
iw list output:
[...]
Band 2:
GMT+02:00 Kalle Valo kv...@qca.qualcomm.com:
Hi,
I just pushed the first qca6174 hw2.1 firmware to ath10k-firmware.git:
https://github.com/kvalo/ath10k-firmware/commit/7f7e7dda33676ced293de477b03711199ffe5256
Please test and provide feedback.
--
Kalle Valo
Loads w/o skip_otp and works
On 25 August 2015 at 16:04, Lapo Calamandrei calamand...@gmail.com wrote:
[...]
Yep, the previous crash was without your patch applied, the following
is with the patch applied though.
iw list output:
[...]
Band 2:
Capabilities: 0x19e3
RX LDPC
HT20/HT40
2015-08-17 7:52 GMT+02:00 Michal Kazior michal.kaz...@tieto.com:
On 13 August 2015 at 16:00, Lapo Calamandrei calamand...@gmail.com wrote:
2015-08-13 12:31 GMT+02:00 Kalle Valo kv...@qca.qualcomm.com:
Hi,
I just pushed the first qca6174 hw2.1 firmware to ath10k-firmware.git:
https
the first qca6174 hw2.1 firmware to ath10k-firmware.git:
https://github.com/kvalo/ath10k-firmware/commit/7f7e7dda33676ced293de477b03711199ffe5256
Please test and provide feedback.
--
Kalle Valo
Loads w/o skip_otp and works fine here (qca6174), except it crashes on
5GHz network
2015-08-13 12:31 GMT+02:00 Kalle Valo kv...@qca.qualcomm.com:
Hi,
I just pushed the first qca6174 hw2.1 firmware to ath10k-firmware.git:
https://github.com/kvalo/ath10k-firmware/commit/7f7e7dda33676ced293de477b03711199ffe5256
Please test and provide feedback.
--
Kalle Valo
Loads w/o
2015-08-07 6:46 GMT+02:00 Michal Kazior michal.kaz...@tieto.com:
On 6 August 2015 at 16:42, Lapo Calamandrei calamand...@gmail.com wrote:
Hi Michal, first of all thank you for your time. So, looks like the
patch provided makes no difference [to me], attached the dmesg output
with and without
On 6 August 2015 at 16:42, Lapo Calamandrei calamand...@gmail.com wrote:
Hi Michal, first of all thank you for your time. So, looks like the
patch provided makes no difference [to me], attached the dmesg output
with and without the patch applied against a fresh checkout.
This is weird. I'm
Hi Michal, first of all thank you for your time. So, looks like the
patch provided makes no difference [to me], attached the dmesg output
with and without the patch applied against a fresh checkout.
Ciao
Lapo
2015-08-06 7:03 GMT+02:00 Michal Kazior michal.kaz...@tieto.com:
On 5 August 2015 at
...and this is the dmesg output with yesterday's build with the patch applied.
2015-08-06 15:52 GMT+02:00 Lapo Calamandrei calamand...@gmail.com:
Hi Michal, first of all thank you for your time. So, looks like the
patch provided makes no difference [to me], attached the dmesg output
with and
: ath10k_pci :03:00.0: Direct
firmware load for ath10k/cal-pci-:03:00.0.bin failed with error -2
ago 05 14:42:26 localhost.localdomain kernel: ath10k_pci :03:00.0: Direct
firmware load for ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed
with error -2
ago 05 14:42:26
On 5 August 2015 at 15:25, Lapo Calamandrei calamand...@gmail.com wrote:
Hi,
I have an alienware 17 r2 with a fedora 22 installed, I'm using kvalo
ath kernel master branch from today, built with fedora rawhide
4.2.0-rc4 kernel config. The firmware is made following the
instructions on the
Enrico Tagliavini enrico.tagliav...@gmail.com writes:
Yeah that's what I meant. My idea was to first bisect only the ath10k
directory, so restricting the bisect on the commits touching stuff
there. I guess if the issue is more broad it will come up somewhere
else as well, so this is a good
Yeah that's what I meant. My idea was to first bisect only the ath10k
directory, so restricting the bisect on the commits touching stuff
there. I guess if the issue is more broad it will come up somewhere
else as well, so this is a good starting point, I hope. Thank you for
pointing it out though,
Michal Kazior michal.kaz...@tieto.com writes:
This wont work for bisecting. I have to setup something else. Is
it ok if I restrict the bisect on the ath10k tree? That has enough
commit already to begin with, plus I'm going to be on the road in less
than two weeks.
As long as you establish a
Sound! I'll keep a copy of the log then. If the bisect on ath10k
folder will lead nowhere I'll see if I can make it over the whole
tree. At least by doing it on the ath10k tree I hope to narrow down
the number of commit.
Ok then I'll use Linus' master, no problem with this.
I hope to at least
with error -2
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: qca6174 hw2.1 (0x0501, 0x003405ff) fw
killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0
alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: Direct firmware load for ath10k/cal-pci-:03:00.0.bin
failed with error -2
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: qca6174 hw2.1 (0x0501, 0x003405ff) fw
killer-n1525-fw api 4 htt 3.0 wmi 4 cal
:00.0.bin
failed with error -2
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: qca6174 hw2.1 (0x0501, 0x003405ff) fw
killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: debug 0 debugfs 1
msi-x interrupts 8 irq_mode 0 reset_mode 0
Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: Direct firmware load for ath10k/cal-pci-:03:00.0.bin
failed with error -2
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: qca6174 hw2.1 (0x0501
:44 alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: qca6174 hw2.1 (0x0501, 0x003405ff) fw
killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Jul 26 10:07
On 28 July 2015 at 16:57, Enrico Tagliavini enrico.tagliav...@gmail.com wrote:
I was testing the kernel from Fedora rawhide to test some issue
related to the sound card. So this is 4.2 rc3 as released by Linus
plus some Fedora patch. Nothing related to ath10k as far as I can see.
Bisecting
On 28 July 2015 at 17:12, Alexandre Maloteaux a.malote...@gmail.com wrote:
[...]
It works on my archlinux system but firmware loading take 1 minute
between each retry, so it takes 2 minutes to get the card up and
running. I have not yet found a solution to this issue.
Go ask on the arch forum
: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
error -2
[ 21.278109] ath10k_pci :03:00.0: failed to load spec board
file, falling back to generic: -2
[ 21.279048] ath10k_pci :03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin
[ 315.661406] ath10k_pci :06:00.0: Falling back to user helper
[ 375.755105] ath10k_pci :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 :06:00.0: Falling back to user helper
[ 435.850288] ath10k_pci
Alexandre Maloteaux a.malote...@gmail.com writes:
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
\xff80\xffd4\xffa8\xfff9\xff88\x\x
What's happening with the features string here?
What's happening with the features string here? What might cause that?
I used the sumdog binaries from github,maybe this is related. I ll try
with my own firmware-4.bin from dissect/assemble and board.bin from
clevo driver and i ll report if i get the same string
On 07/23/2015 03:03 PM, Kalle
)
[ 17.152101] ath10k_pci :06:00.0: qca6174 hw2.1 (0x0501,
0x003405ff) fw killer-n1525-fw api 4 htt 0.0 wmi 4 cal otp max_sta 32
[ 17.152103] ath10k_pci :06:00.0: debug 0 debugfs 1 tracing 0 dfs
0 testmode 0
[ 17.154123] ath10k_pci :06:00.0: firmware register dump:
[ 17.154124
[ 256.174560] ath10k_pci :06:00.0: Direct firmware load for
ath10k/cal-pci-:06:00.0.bin failed with error -2
[ 256.174562] ath10k_pci :06:00.0: Falling back to user helper
[ 316.269053] ath10k_pci :06:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin
[ 12.822158] ath10k_pci :06:00.0: Falling back to user helper
[ 72.915990] ath10k_pci :06:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2
[ 72.915993] ath10k_pci :06:00.0: Falling back to user helper
[ 133.010331
[ 12.822155] ath10k_pci :06:00.0: Direct firmware load for
ath10k/cal-pci-:06:00.0.bin failed with error -2
[ 12.822158] ath10k_pci :06:00.0: Falling back to user helper
[ 72.915990] ath10k_pci :06:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56
On 23 July 2015 at 11:33, Alexandre Maloteaux a.malote...@gmail.com wrote:
Hi
What is the head commit id (kvalo/master) that you've used? You might
be missing a patches[1][2] that fixed a recent breakage in the dev
tree.
I m getting this issue only with kvalo-qca branch.
With kvalo master
-:06:00.0.bin failed with error -2
[ 12.822158] ath10k_pci :06:00.0: Falling back to user helper
[ 72.915990] ath10k_pci :06:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2
[ 72.915993] ath10k_pci :06:00.0: Falling back
/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with error -2
[ 72.915993] ath10k_pci :06:00.0: Falling back to user helper
[ 133.010331] ath10k_pci :06:00.0: failed to load spec board file,
falling back to generic: -11
[ 133.010647] ath10k_pci :06:00.0: Direct firmware load
Hi Kalle,
thank you very much. Hope to also see the firmware out soon :).
Best regards
On 21 July 2015 at 11:23, Kalle Valo kv...@qca.qualcomm.com wrote:
Enrico Tagliavini enrico.tagliav...@gmail.com writes:
Mhm seems like I assumed the backport missing from 4.0 was merged for
4.1 but
Enrico Tagliavini enrico.tagliav...@gmail.com writes:
Mhm seems like I assumed the backport missing from 4.0 was merged for
4.1 but it is not, it's in 4.2 only. Any chance you'll ask for a
backport of this 4 lines patch?
: invalid firmware magic
[ 18.668791] ath10k_pci :03:00.0: invalid firmware magic
[ 18.670086] ath10k_pci :03:00.0: invalid firmware magic
[ 18.670265] ath10k_pci :03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware.bin failed with error -2
[ 18.670267] ath10k_pci
To: ath10k@lists.infradead.org
Subject: Re: QCA6174 hw2.1 firmware, take two?
Hi again,
ok this was dumb I forgot to assemble back the firmware and I
realized it just after sending out the previous email (that's why the
driver was complaining about the invalid magic).
Sorry
at 1:22 PM
From: Enrico Tagliavini enrico.tagliav...@gmail.com
To: ath10k@lists.infradead.org
Subject: Re: QCA6174 hw2.1 firmware, take two?
Hi again,
ok this was dumb I forgot to assemble back the firmware and I
realized it just after sending out the previous email (that's why
firmware magic
[ 18.668791] ath10k_pci :03:00.0: invalid firmware magic
[ 18.670086] ath10k_pci :03:00.0: invalid firmware magic
[ 18.670265] ath10k_pci :03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware.bin failed with error -2
[ 18.670267] ath10k_pci :03
: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware.bin failed with error -2
[ 18.670267] ath10k_pci :03:00.0: could not fetch firmware (-2)
[ 18.670269] ath10k_pci :03:00.0: could not fetch firmware files (-2)
[ 18.670271] ath10k_pci :03:00.0: could not probe fw (-2
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
moritz.morawi...@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
/cal-pci-:06:00.0.bin failed with error -2
[3.159611] ath10k_pci :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 :06:00.0: failed to load spec board
file, falling back to generic: -2
:00.0: pci irq msi-x interrupts 8
irq_mode 0 reset_mode 0
[3.158860] ath10k_pci :06:00.0: Direct firmware load for
ath10k/cal-pci-:06:00.0.bin failed with error -2
[3.159611] ath10k_pci :06:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin
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
[ 6484.772417] ath10k_pci :03:00.0: firmware crashed! (uuid n/a)
[ 6484.772433] ath10k_pci :03:00.0: qca6174 hw2.1 (0x0501,
0x003405ff) fw killer-n1525-fw api 4 htt 0.0 wmi 4 cal otp max_sta 32
[ 6484.772435] ath10k_pci :03:00.0: debug 1 debugfs 0 tracing 0 dfs
0 testmode 0
[ 6484.77
-pci-:03:00.0.bin failed with error -2
[2.368971] ath10k_pci :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 :03:00.0: failed to load spec board file,
falling back to generic: -2
[2.369252
/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
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
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
Subject: Re: Re: QCA6174 hw2.1?
Just checking in. Any updates for the QCA6174?
Sent: Monday, March 23, 2015 at 9:57 AM
From: Jason H jh...@gmx.com
To: Michal Kazior michal.kaz...@tieto.com
Cc: ath10k@lists.infradead.org ath10k@lists.infradead.org
Subject: Re: Re: QCA6174 hw2.1
Just checking in. Any updates for the QCA6174?
Sent: Monday, March 23, 2015 at 9:57 AM
From: Jason H jh...@gmx.com
To: Michal Kazior michal.kaz...@tieto.com
Cc: ath10k@lists.infradead.org ath10k@lists.infradead.org
Subject: Re: Re: QCA6174 hw2.1?
Sent: Monday, March 23, 2015 at 4:23
Sent: Monday, March 23, 2015 at 4:23 AM
From: Michal Kazior michal.kaz...@tieto.com
To: Jason H jh...@gmx.com
Cc: ath10k@lists.infradead.org ath10k@lists.infradead.org
Subject: Re: Re: QCA6174 hw2.1?
On 21 March 2015 at 21:31, jh...@gmx.com wrote:
is there anyway you could process
On 21 March 2015 at 21:31, jh...@gmx.com wrote:
is there anyway you could process these files for me?. I would be willing to
send you the files and go through some back and forth of feedback and
whatnot. The issue is I just don't think I have the time or the expertise to
devote to this.
:05:20
From: Michal Kazior michal.kaz...@tieto.com
To: Jason H jh...@gmx.com
Subject: Re: QCA6174 hw2.1?
On 13 March 2015 at 16:28, Jason H jh...@gmx.com wrote:
On 13 March 2015 at 04:39, jh...@gmx.com wrote:
I went through the archives, and the wiki but I still wasn't sure...
I have a shiny
On 13 March 2015 at 04:39, jh...@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
On 13 March 2015 at 04:39, jh...@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
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
65 matches
Mail list logo