WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00

WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00

[Alex R]

Trying the latest board-2.bin from https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855 and my wlan0 fails to come up. dmesg: https://pastebin.com/CWHpD0kC

My other X13s system (21BX-0015US) works fine so I am wondering if my new X13s (21BY-S03Y00) product type is unsupported.

Alex

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00

[Kalle Valo]

Alex R <alex@ironrobin.net> writes:

> Trying the latest board-2.bin from
> https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855 and my
> wlan0 fails to come up. dmesg: https://pastebin.com/CWHpD0kC
>
> My other X13s system (21BX-0015US) works fine so I am wondering if my
> new X13s (21BY-S03Y00) product type is unsupported.

For easier tracking can you please file a bug to bugzilla:

https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport

Also adding Johan in case he has any ideas or knows what has changed in
21BY-S03Y00.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00

[Johan Hovold]

On Wed, Sep 06, 2023 at 11:45:14AM +0300, Kalle Valo wrote:
> Alex R <alex@ironrobin.net> writes:
> 
> > Trying the latest board-2.bin from
> > https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855 and my
> > wlan0 fails to come up. dmesg: https://pastebin.com/CWHpD0kC
> >
> > My other X13s system (21BX-0015US) works fine so I am wondering if my
> > new X13s (21BY-S03Y00) product type is unsupported.
> 
> For easier tracking can you please file a bug to bugzilla:
> 
> https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
> 
> Also adding Johan in case he has any ideas or knows what has changed in
> 21BY-S03Y00.

I've asked for some more details from Alex over IRC, but it's currently
not clear why there are problems with this particular machine.

It appears that firmware download fails, but apparently only sometimes.
And it fails before loading board-2.bin so that bit of the report looks
irrelevant:

	[    2.195948] ath11k_pci 0006:01:00.0: wcn6855 hw2.1
	...
	[    2.423948] mhi mhi1: Requested to power ON
	[    2.427589] mhi mhi1: Power on setup success
	...
	[    4.035111] mhi mhi1: Wait for device to enter SBL or Mission mode
	...
	[   23.518986] mhi mhi1: MHI did not load AMSS, ret:-5

IIUC, things got worse with 6.5, possible due to random changes in
timing.

You need to provide a lot more detail, Alex:

For example, did this module ever work, and if so with which kernel
version? How is this module identified when it starts successfully? How
did things change in 6.5? Have you verified that you're using the same
fw on both the working and non-working machine (not just board-2.bin,
which does not seem to be involved here)? You also said something on IRC
about dual-booting Windows making a difference, etc. etc.

Johan

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00

[Jeff Johnson]

On 9/6/2023 2:13 AM, Johan Hovold wrote:
> On Wed, Sep 06, 2023 at 11:45:14AM +0300, Kalle Valo wrote:
>> Alex R <alex@ironrobin.net> writes:
>>
>>> Trying the latest board-2.bin from
>>> https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855 and my
>>> wlan0 fails to come up. dmesg: https://pastebin.com/CWHpD0kC
>>>
>>> My other X13s system (21BX-0015US) works fine so I am wondering if my
>>> new X13s (21BY-S03Y00) product type is unsupported.
>>
>> For easier tracking can you please file a bug to bugzilla:
>>
>> https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
>>
>> Also adding Johan in case he has any ideas or knows what has changed in
>> 21BY-S03Y00.
> 
> I've asked for some more details from Alex over IRC, but it's currently
> not clear why there are problems with this particular machine.
> 
> It appears that firmware download fails, but apparently only sometimes.
> And it fails before loading board-2.bin so that bit of the report looks
> irrelevant:
> 
> 	[    2.195948] ath11k_pci 0006:01:00.0: wcn6855 hw2.1
> 	...
> 	[    2.423948] mhi mhi1: Requested to power ON
> 	[    2.427589] mhi mhi1: Power on setup success
> 	...
> 	[    4.035111] mhi mhi1: Wait for device to enter SBL or Mission mode
> 	...
> 	[   23.518986] mhi mhi1: MHI did not load AMSS, ret:-5
> 
> IIUC, things got worse with 6.5, possible due to random changes in
> timing.
> 
> You need to provide a lot more detail, Alex:
> 
> For example, did this module ever work, and if so with which kernel
> version? How is this module identified when it starts successfully? How
> did things change in 6.5? Have you verified that you're using the same
> fw on both the working and non-working machine (not just board-2.bin,
> which does not seem to be involved here)? You also said something on IRC
> about dual-booting Windows making a difference, etc. etc.
> 
> Johan
> 

Is this using the single MSI interrupt feature? If so, try:
"[PATCH] wifi: ath11k: fix boot failure with one MSI vector"

<https://lore.kernel.org/ath11k/20230601033840.2997-1-quic_bqiang@quicinc.com/T/>


-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00

[Johan Hovold]

On Wed, Sep 06, 2023 at 07:47:17AM -0700, Jeff Johnson wrote:
> On 9/6/2023 2:13 AM, Johan Hovold wrote:

> > I've asked for some more details from Alex over IRC, but it's currently
> > not clear why there are problems with this particular machine.

> Is this using the single MSI interrupt feature? If so, try:
> "[PATCH] wifi: ath11k: fix boot failure with one MSI vector"
> 
> <https://lore.kernel.org/ath11k/20230601033840.2997-1-quic_bqiang@quicinc.com/T/>

No, it's not:

	[    2.195919] ath11k_pci 0006:01:00.0: MSI vectors: 32

Johan

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00

[Alex R]

Q. Did this module ever work, and if so with which kernel version?
A. It seems to work more reliably on my archiso kernel, which is 5.19.0. 
IIRC this is where we were using the wifi hack, before we got the new X13s board file.

Q. How is this module identified when it starts successfully? 
A. Here is the dmesg from a "successful" bootup: https://pastebin.com/1kLDzXSD
(I was able to get the wlan0 device to come up by booting into Windows 11, checking for updates, and then shutting down (not rebooting) 
(fast boot Windows 11 setting is disabled)

Q. How did things change in 6.5?
A. On both 6.4 and 6.5 of those versions, we have the same issue in the dmesg logs. 
Although it seems I am able to get "successful" boots more often with 6.4.
I have no data on this though and could be wrong.

Q. Have you verified that you're using the same fw on both the working and non-working machine (not just board-2.bin, which does not seem to be involved here)?
A. I use my own distro based on Arch Linux ARM project, and use the same x13s-firmware package on both machines, so firmware must be the same.
https://github.com/ironrobin/x13s-alarm/tree/trunk/x13s-firmware

Q. You also said something on IRC about dual-booting Windows making a difference, etc. etc.
A. On my faulty machine, I've tried both dual booting Windows and running linux as the only root partition on a nvme drive.
The only difference I've noticed is that I can more reliably bring back the wlan0 device by booting into Windows 11, connecting to the internet, and then rebooting into Linux.


Alex

------- Original Message -------
On Wednesday, September 6th, 2023 at 9:55 AM, Johan Hovold <johan@kernel.org> wrote:


> 
> 
> On Wed, Sep 06, 2023 at 07:47:17AM -0700, Jeff Johnson wrote:
> 
> > On 9/6/2023 2:13 AM, Johan Hovold wrote:
> 
> > > I've asked for some more details from Alex over IRC, but it's currently
> > > not clear why there are problems with this particular machine.
> 
> > Is this using the single MSI interrupt feature? If so, try:
> > "[PATCH] wifi: ath11k: fix boot failure with one MSI vector"
> > 
> > https://lore.kernel.org/ath11k/20230601033840.2997-1-quic_bqiang@quicinc.com/T/
> 
> 
> No, it's not:
> 
> [ 2.195919] ath11k_pci 0006:01:00.0: MSI vectors: 32
> 
> Johan

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00

[Johan Hovold]

Alex,

You sent an encrypted mail to a public mailing list, which does not
really work.

Please resend your reply unencrypted.

Johan

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00

[Johan Hovold]

On Mon, Sep 11, 2023 at 09:38:57AM +0200, Johan Hovold wrote:

> You sent an encrypted mail to a public mailing list, which does not
> really work.

Apparently it was also sent unencrypted to the list so I'll reply to my
deciphered copy, but please fix your mail setup to only send plain text
when communicating with upstream.

Johan

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: WCN6855: Request: Support ThinkPad X13s 21BY-S03Y00^[

[Johan Hovold]

On Thu, Sep 07, 2023 at 03:16:15PM +0000, Alex R wrote:
> Q. Did this module ever work, and if so with which kernel version?
> A. It seems to work more reliably on my archiso kernel, which is 5.19.0. 
> 
> IIRC this is where we were using the wifi hack, before we got the new
> X13s board file.

Yes, but it seems you never get as far as loading the board file so I
don't think that one's involved here.

> Q. How is this module identified when it starts successfully? 
> 
> A. Here is the dmesg from a "successful" bootup: https://pastebin.com/1kLDzXSD
> (I was able to get the wlan0 device to come up by booting into Windows
> 11, checking for updates, and then shutting down (not rebooting) 
> 
> (fast boot Windows 11 setting is disabled)

Ok, so you do have a different chip_id than I do (0x2 instead of 0x12),
but both ids have an entry in board-2.bin (otherwise it would not work
"sometimes"):

	ath11k_pci 0006:01:00.0: chip_id 0x2 chip_family 0xb board_id 0x8c soc_id 0x400c0210

You could compare it with what the chip in your other machine which does
not have this issue is identified as (compare all the values above).

> Q. How did things change in 6.5?
> A. On both 6.4 and 6.5 of those versions, we have the same issue in
> the dmesg logs. 
> 
> Although it seems I am able to get "successful" boots more often with 6.4.
> I have no data on this though and could be wrong.

Ok, got it. But with 5.19 you never saw this issue at all?

> Q. Have you verified that you're using the same fw on both the working
> and non-working machine (not just board-2.bin, which does not seem to
> be involved here)?
> A. I use my own distro based on Arch Linux ARM project, and use the
> same x13s-firmware package on both machines, so firmware must be the
> same.
> https://github.com/ironrobin/x13s-alarm/tree/trunk/x13s-firmware

Ok, the fw version is also logged on successful probe and you appear to
use the same version as I do:

	ath11k_pci 0006:01:00.0: fw_version 0x110b196e fw_build_timestamp 2022-12-22 12:54 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23

Could you check what fw version you were using with your 5.19 iso image?

> Q. You also said something on IRC about dual-booting Windows making a
> difference, etc. etc.
> A. On my faulty machine, I've tried both dual booting Windows and
> running linux as the only root partition on a nvme drive.
> The only difference I've noticed is that I can more reliably bring
> back the wlan0 device by booting into Windows 11, connecting to the
> internet, and then rebooting into Linux.

Hmm... Not sure what's going on here, and I'm afraid I won't have time
to look at this myself for a while.

Johan

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k