From: Kalle Valo <kvalo@kernel.org>
To: Matthew Schwartz <njtransit215@gmail.com>
Cc: ath11k@lists.infradead.org, cristian.ciocaltea@collabora.com
Subject: Re: question regarding qca2066 and qca206x (Steam Deck OLED/Galileo) on upstream kernels
Date: Tue, 21 May 2024 14:33:36 +0300 [thread overview]
Message-ID: <874jarcsbz.fsf@kernel.org> (raw)
In-Reply-To: <CAFKu21b_4fbP3Oku_CLBOYi7wfwmYWUXoG5H1gknvFit-wc4Rw@mail.gmail.com> (Matthew Schwartz's message of "Mon, 20 May 2024 13:41:10 -0700")
Matthew Schwartz <njtransit215@gmail.com> writes:
> On Mon, May 20, 2024 at 3:21 AM Kalle Valo <kvalo@kernel.org> wrote:
>
>> For me a major problem here is that there are several hacks and another
>> firmware release used. My recommendation is to take a step back and do
>> one thing at a time, for example something like this:
>>
>> 1. Install linux 6.9 without any modifications.
>>
>
> Done, compiled the v6.9 release from git without any issues.
>
>> 2. Remove the old ath11k firmware.
>>
>
> Easy, I ran sudo rm -r /lib/firmware/ath11k
>
>> 3. Install new firmware from
>> https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware
>>
>
> For this step, this was my exact process:
> copied QCA206X from my current kernel's firmware into the upstream
> ath11k firmware folder retrieved from
> https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware
> sudo cp -r /home/matt/Downloads/Warpinator/ath11k /lib/firmware/ath11k
I forgot to mention that you you need to use 'make install' to install
the firmware or run ath11k-fw-repo manually. See README for more:
https://git.codelinaro.org/clo/ath-firmware/ath11k-firmware/-/blob/main/README.md?ref_type=heads
If you need to create symlinks or copy files manually then something is
wrong in our installation process. Please do report if you see such cases.
>> 4. Most likely our ath11k-firmware does not contain the correct board
>> file so that might need to be copied from the old firmware package.
>>
>
> For this step, this was my exact process:
> Rebooted after 6.9 kernel install
>
> I get no wifi and this is my dmesg:
> May 20 12:49:21 steamdeck-oled kernel: mhi mhi0: Direct firmware load
> for ath11k/QCA2066/hw2.1/amss.bin failed with error -2
> May 20 12:49:21 steamdeck-oled kernel: mhi mhi0: Error loading firmware: -2
> May 20 12:49:21 steamdeck-oled kernel: ath11k_pci 0000:03:00.0: failed
> to power up mhi: -110
> May 20 12:49:21 steamdeck-oled kernel: ath11k_pci 0000:03:00.0: failed
> to start mhi: -110
> May 20 12:49:21 steamdeck-oled kernel: ath11k_pci 0000:03:00.0: failed
> to power up :-110
> May 20 12:49:21 steamdeck-oled kernel: ath11k_pci 0000:03:00.0: failed
> to create soc core: -110
> May 20 12:49:21 steamdeck-oled kernel: ath11k_pci 0000:03:00.0: failed
> to init core: -110
> May 20 12:49:21 steamdeck-oled kernel: ------------[ cut here ]------------
> May 20 12:49:21 steamdeck-oled kernel: WARNING: CPU: 0 PID: 745 at
> kernel/irq/manage.c:1925 free_irq+0x2d3/0x300
Oh man, clearly ath11k is buggy if any firmware files are missing. I
thought I fixed at some point but I guess it has regressed.
> I rebooted one final time, and now I have functional Wi-Fi and this
> dmesg:
>
> matt@steamdeck-oled:/lib/firmware/ath11k$ journalctl -k -b | grep ath11k
> May 20 12:58:15 steamdeck-oled kernel: ath11k_pci 0000:03:00.0: BAR 0
> [mem 0x80000000-0x801fffff 64bit]: assigned
> May 20 12:58:15 steamdeck-oled kernel: ath11k_pci 0000:03:00.0:
> enabling device (0000 -> 0002)
> May 20 12:58:15 steamdeck-oled kernel: ath11k_pci 0000:03:00.0: MSI vectors: 1
> May 20 12:58:15 steamdeck-oled kernel: ath11k_pci 0000:03:00.0: qca2066 hw2.1
> May 20 12:58:16 steamdeck-oled kernel: ath11k_pci 0000:03:00.0:
> chip_id 0x2 chip_family 0xb board_id 0x309 soc_id 0x400c0210
> May 20 12:58:16 steamdeck-oled kernel: ath11k_pci 0000:03:00.0:
> fw_version 0x11058f56 fw_build_timestamp 2023-10-11 08:46 fw_build_id
> CI_WLAN.HSP.1.1-03926.9.1-QCAHSPSWPL_V2_SILICON
> Z_CE-15
> May 20 12:58:16 steamdeck-oled kernel: ath11k_pci 0000:03:00.0:
> leaving PCI ASPM disabled to avoid MHI M2 problems
> May 20 12:58:17 steamdeck-oled kernel: ath11k_pci 0000:03:00.0 wlo1:
> renamed from wlan0
Nice. At least it looks like the ath11k firmware is booting which is
most important. But based on the firmware string
(CI_WLAN.HSP.1.1-03926.9.1-QCAHSPSWPL_V2_SILICONZ_CE-15) it looks like
that this is not the firmware from ath11k-firmware.git.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-05-21 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 22:14 question regarding qca2066 and qca206x (Steam Deck OLED/Galileo) on upstream kernels Matthew Schwartz
2024-05-20 10:21 ` Kalle Valo
2024-05-20 20:41 ` Matthew Schwartz
2024-05-20 20:52 ` Matthew Schwartz
2024-05-21 11:49 ` Kalle Valo
2024-05-21 15:51 ` Matthew Schwartz
2024-05-21 11:33 ` Kalle Valo [this message]
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=874jarcsbz.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=njtransit215@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.