6.14.0-30 should hopefully solve your issues
1 Like
and it does thanks a lot @tobhe
1 Like
Based on discussions in #aarch64-laptops I have included this wifi fix in 6.14.0-30.30. I think there is a chance that it also fixes your issues.
I just tried to install 6.14.0-30 and I still get a black screen after grub. My last working image is 6.14.0-20, but my wifi does bluescreen on that version. I have a ASUS Vivobook S15 S5507QA_S5507QAD
1 Like
I just tried to install 6.14.0-30 and I still get a black screen after grub. My last working image is 6.14.0-20, but my wifi does bluescreen on that version. I have a ASUS Vivobook S15 S5507QA_S5507QAD
That could be related to the issue we saw on HP laptops. Can you try booting with this patched dtb. That has a recent upstream change reverted.
That worked, thank you! I was able to boot but I still have the bluescreen wifi issue. If I try to change or disconnect the wifi I get a bluescreen and the pc restarts.
1 Like
64 GB Ram model? You could try what was recommended in Ubuntu 24.10 Concept ♥️ Snapdragon X Elite - #741 by jokkeholmberg
32GB model, can it still help? Reduce it to 16?
32GB model, can it still help? Reduce it to 16?
Probably not no. That means it must be another bug.
Just to be clear, cjpalm listed like 4 problems with wifi and his Yoga7 slim, but this fix on 6.14.0-30.30 from the changelog:
[ Johan Hovold ]
- UBUNTU: SAUCE: wifi: ath12k: fix ring-buffer corruption
- UBUNTU: SAUCE: wifi: ath11k: fix ring-buffer corruption
Is meant to fix:
if I change wifi or turn wifi off the computer crashes.
Right?
On my T14s, ath12k driver, Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] (rev 01)
6.14.0-30-qcom-x1e kernel from, yesterday! and the matching DTB that came in the same update, I totally get the exact same eerie bluescreen crash when manually disconnecting wifi or trying to change APs.
Suggest anything, I am more than happy to crash this thing repeatedly for funsies.
Also, thank you for the rapid fire kernel build releases to try and get these things working. This is kind of awesome!
2 Likes
Not sure, but I’m running these patches on the Snapdragon DevKit and on the ThinkBook 16. Apparrently it will crash your box if you try to change the network / AP. Deauthentication / Reauthentication seems to work. So, as I expected, these are not enough.
T14s 32GB here… same problem as above, doing almost anything with wifi bluescreens.
It auto-connects (saved connection) to one of my SSIDs, disconnecting or selecting another SSID almost always produces a bluescreen.
I was able to open “All networks” (gnome settings) and forget the currently-connected network there and it disconnected without problem. Selecting another SSID and deleting it in Settings again (while connected) bluescreened. So no consistency.
I checked the journal and it does not seem there is anything in the logs. Is there another way I can get something, maybe with a serial port dongle and logging to that?
What exactly is this blue screen without text? I haven’t seen it before on Linux, is this something qcom-related? it’s not systemd’s bsod or at least not what it should be (haven’t seen that one on the wild either 
What exactly is this blue screen without text? I haven’t seen it before on Linux, is this something qcom-related? it’s not systemd’s bsod or at least not what it should be (haven’t seen that one on the wild either
I think it is usually a sign of a crash somewhere in the firmware/gunyah. Maybe a page fault somewhere in the hypervisor.
Hmm I did some poking with @thobhe 's help… as a wild shot I did rebase a lot of the ath-next tree onto my tree, and it actually built 
Initial testing on the TB16 with WCN7850 showed no crashes when changing networks, looks good enough to be worth a test. 6.14-rc7-2 can be downloaded now. The tree is also up on github. I will try to bisect to the actually fixing patch, but $dayjob first.
Thanks @tobhe for looking into the problem - and its good to know that I was not alone, for a while I thought I had overlooked something simple.
@glathe - I tried your 6.14-rc7-2 today and at the first boot the system seemed to crash at the login window (starting wifi?) After that I tried to start in recovery mode but nothing happened, there was just a black screen.
I did a hard reset (holding the start-button for a long time) and tried 6.14-rc7-2 again, and this time I could login .
And it seems to work!
Wifi connected and I can change/turn off without problems
2 Likes
And btw, looking through dmesg I see that sound is not that far off either
@Yoga-Slim-7:~$ sudo dmesg | grep qcom-soundwire
[ 7.820635] qcom-soundwire 6ab0000.soundwire: Qualcomm Soundwire controller v2.0.0 Registered
[ 7.932570] qcom-soundwire 6ad0000.soundwire: Qualcomm Soundwire controller v2.0.0 Registered
[ 7.939618] qcom-soundwire 6b10000.soundwire: Qualcomm Soundwire controller v2.0.0 Registered
[ 8.052431] qcom-soundwire 6d30000.soundwire: Qualcomm Soundwire controller v2.0.0 Registered
[ 7.943410] wcd938x_codec audio-codec: bound sdw:2:0:0217:010d:00:4 (ops wcd938x_sdw_component_ops [snd_soc_wcd938x_sdw])
[ 7.943422] wcd938x_codec audio-codec: bound sdw:3:0:0217:010d:00:3 (ops wcd938x_sdw_component_ops [snd_soc_wcd938x_sdw])
[ 11.659197] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0x4e00c00f, flushing fifo
[ 11.671221] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0xe00c000, flushing fifo
[ 11.682914] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0xe00c000, flushing fifo
[ 11.694585] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0xe00c000, flushing fifo
[ 11.706206] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0xe00c000, flushing fifo
[ 11.717871] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0xe00c000, flushing fifo
[ 11.729685] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0xe00c000, flushing fifo
[ 11.741373] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0xe00c000, flushing fifo
[ 11.753039] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0xe00c000, flushing fifo
[ 11.765034] qcom-soundwire 6d30000.soundwire: qcom_swrm_irq_handler: SWR CMD error, fifo status 0xe00c000, flushing fifo
Can confirm, seems to fix this issue on t14s w/ WCN7850.
However I lose screen brightness control with the included DT, using the one from 6.14.0-30 works. I don’t actually know which screen type I have, it’s the one with higher resolution (2880x1800)
Can confirm, seems to fix this issue on t14s w/ WCN7850.
Great! If we can narrow it down I’ll make sure the fix makes it into 25.04.
However I lose screen brightness control with the included DT, using the one from 6.14.0-30 works. I don’t actually know which screen type I have, it’s the one with higher resolution (2880x1800)
That means you probably have the OLED
Just my 5c: The 6.14.0-30.30 kernel gets past the “blackscreen” init issue on my Omnibook x14 16GB (thanks!). However my WiFi still doesn’t work with any kernel version and BlueTooth hangs after 20s connection. This could possibly be a hardware failure on my laptop.
I bought a “Asus AX-55 Nano” Wifi USB dongle to get a network connection and it has worked perfectly fine with 6.12.0-28 but interestingly with 6.14.0-30 this WiFi dongle driver hangs the system. So the WiFi problems in 6.14 is perhaps not specifically with the built-in WiFi driver or firmware. (The AX-55 Nano required a third party driver rtl8852bu which I built and installed using DKMS.)
I can try to do some bisecting, I haven’t actually built a kernel in decades
@glathe just tell me if you’ve already started so we don’t both work on this.
What’s the temp situation at the moment, can I run make -j 12 (or something to that effect) and it’ll throttle as needed or will that overheat and shutdown the machine? This was an issue IIRC.
1 Like