From: Pavel Procopiuc <pavel.procopiuc@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: PROBLEM: unable to get QCA6390 to work
Date: Mon, 2 Nov 2020 19:21:10 +0100 [thread overview]
Message-ID: <fa338986-8de4-fde1-6805-d46793c947e4@gmail.com> (raw)
In-Reply-To: <87lffjodu7.fsf@codeaurora.org>
Ah, my bad, I've now renamed the board-2.bin file, the md5's match yours. But it doesn't seem to have a positive effect.
After a reboot I'm still getting the same error messages:
# journalctl -b | grep -iP '05:00|ath11k'
Nov 02 18:52:58 razor kernel: pci 0000:05:00.0: [17cb:1101] type 00 class 0x028000
Nov 02 18:52:58 razor kernel: pci 0000:05:00.0: reg 0x10: [mem 0xd2100000-0xd21fffff 64bit]
Nov 02 18:52:58 razor kernel: pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov 02 18:52:58 razor kernel: pci 0000:05:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at
0000:00:1c.1 (capable of 7.876 Gb/s with 8.0 GT/s PCIe x1 link)
Nov 02 18:52:58 razor kernel: pci 0000:05:00.0: Adding to iommu group 21
Nov 02 18:53:20 razor dbus-daemon[743]: [system] Activating via systemd: service name='net.reactivated.Fprint'
unit='fprintd.service' requested by ':1.73' (uid=0 pid=2476 comm="sudo modprobe ath11k_pci ")
Nov 02 18:53:23 razor sudo[2476]: pro : TTY=pts/1 ; PWD=/home/pro ; USER=root ; COMMAND=/sbin/modprobe ath11k_pci
Nov 02 18:53:23 razor kernel: ath11k_pci 0000:05:00.0: WARNING: ath11k PCI support is experimental!
Nov 02 18:53:23 razor kernel: ath11k_pci 0000:05:00.0: BAR 0: assigned [mem 0xd2100000-0xd21fffff 64bit]
Nov 02 18:53:23 razor kernel: ath11k_pci 0000:05:00.0: enabling device (0000 -> 0002)
Nov 02 18:53:23 razor kernel: mhi 0000:05:00.0: Requested to power ON
Nov 02 18:53:23 razor kernel: mhi 0000:05:00.0: Power on setup success
Nov 02 18:53:23 razor kernel: ath11k_pci 0000:05:00.0: Respond mem req failed, result: 1, err: 0
Nov 02 18:53:23 razor kernel: ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-22
Nov 02 18:53:29 razor kernel: ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
Nov 02 18:53:29 razor kernel: ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
Nov 02 18:54:54 razor kernel: mhi 0000:05:00.0: Device failed to exit MHI Reset state
# md5sum /lib/firmware/ath11k/QCA6390/hw2.0/*
a101dc90f8e876f39383b60c9da64ec4 /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
4c0781f659d2b7d6bef10a2e3d457728 /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
d4c912a3501a3694a3f460d13de06d28 /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin
Op 02.11.2020 om 18:42 schreef Kalle Valo:
> Pavel Procopiuc <pavel.procopiuc@gmail.com> writes:
>
>> Hi,
>>
>> I'm unable to get QCA6390 to work on kernel 5.10-rc2.
>>
>> I have a Dell XPS 17 laptop with the QCA6390 device and I'm trying to
>> get it to work using 5.10-rc2 kernel. So far I'm getting firmware
>> errors in the log. For the kernel setup and firmware files I was
>> following the guide from
>> https://www.spinics.net/lists/linux-wireless/msg203111.html.
>>
>> * The current firmware repo structure is a bit different so I'm using:
>> QCA6390/hw2.0/board-2.bin -> /lib/firmware/ath11k/QCA6390/hw2.0/board.bin
>> QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/amss.bin
>> -> /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
>> QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/m3.bin
>> -> /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin
>
> Can you do 'md5sum /lib/firmware/ath11k/QCA6390/hw2.0/*' and send the
> output? Currently ath11k does not check the firmware files in any way
> and I want to make sure they are not corrupted.
>
> I have:
>
> a101dc90f8e876f39383b60c9da64ec4 amss.bin
> d4c912a3501a3694a3f460d13de06d28 m3.bin
> 4c0781f659d2b7d6bef10a2e3d457728 board-2.bin
>
> Ah, now I noticed that you renamed board-2.bin to board.bin. But you
> need to keep the file as board-2.bin, board-2.bin and board.bin are not
> compatible. I need to send new instructions with the new board-2.bin
> file.
>
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-11-02 18:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 10:32 PROBLEM: unable to get QCA6390 to work Pavel Procopiuc
2020-11-02 17:42 ` Kalle Valo
2020-11-02 18:21 ` Pavel Procopiuc [this message]
2020-11-02 21:14 ` Pavel Procopiuc
2020-11-03 6:56 ` Kalle Valo
2020-11-03 13:12 ` Pavel Procopiuc
2020-11-04 9:32 ` Pavel Procopiuc
2020-11-03 14:23 ` Kalle Valo
2020-11-03 21:01 ` Pavel Procopiuc
2020-11-04 9:12 ` Kalle Valo
2020-11-04 22:15 ` Pavel Procopiuc
2020-11-05 9:04 ` Regression: QCA6390 fails with "mm/page_alloc: place pages to tail in __free_pages_core()" Kalle Valo
2020-11-05 9:47 ` Pavel Procopiuc
2020-11-05 10:42 ` Vlastimil Babka
2020-11-05 10:45 ` Pavel Procopiuc
2020-11-05 11:13 ` David Hildenbrand
2020-11-05 12:55 ` Pavel Procopiuc
2020-11-05 20:23 ` David Hildenbrand
2020-11-06 17:32 ` Pavel Procopiuc
2020-11-06 20:41 ` David Hildenbrand
2020-11-11 19:23 ` Kalle Valo
2020-11-11 20:41 ` Pavel Procopiuc
2020-11-12 10:48 ` David Hildenbrand
2020-11-13 8:17 ` Pavel Procopiuc
2020-11-13 11:08 ` Carl Huang
2020-11-13 11:44 ` Carl Huang
2020-11-13 12:52 ` Pavel Procopiuc
2020-11-13 13:36 ` wi nk
2020-11-13 13:56 ` David Hildenbrand
2020-11-13 15:49 ` wi nk
2020-11-03 8:42 ` PROBLEM: unable to get QCA6390 to work Carl Huang
2020-11-03 14:12 ` Pavel Procopiuc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa338986-8de4-fde1-6805-d46793c947e4@gmail.com \
--to=pavel.procopiuc@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).