jhovold:

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.


let me know if you'd like me to post that to the mailing list as well.