Bug reported here patch by Glathe allowed to boot 6.14-rc4. Let me know if I can help in any way.
Oh this one is outdated again 
I got help from Johan Hovold and Stefan Gerhold (?) regarding the retimer issue on the HP Omnibook, and it seems resolved now, with implications for the Yoga 7 I guess. The type-c connectors are not equal, one is 40Gb and one is 10Gb. Only the 40Gb one has the PS8830 retimer, the other one has some other dp mux. I amended the dtb now with this information (and templates from the QCP), and it works without the patch now. Quite well, tbh. Both type-c ports tried to connect with 4k@60 to my display, but it wouldn’t take the high data rates on 2 lanes only. Reduced to 4k@30 this worked. With the usual quirks, but it worked. I will build 6.14.0-17-jg-2 with this and push the updated source. Should be up tomorrow.
1 Like
Updated kernel package 6.14.0-17-jg-2 is up now. Source tree is here.
2 Likes
t14s 64gb: I just had a random crash with blue screen. Using 6.14.0-17-qcom-x1e.
Are there any known issues with this kernel?
I am limiting RAM to 29Gi, double checked.
Hello. I had the same problem before limiting to 32GB, but then I did two changes at once, limiting to 32GB and going back to an older kernel (6.12-something). Will try to check tomorrow if I still get crashes on the 6.14.0-17 kernel.
Same here on t14s 64gb (limited RAM), crashes started with 6.14.x. I’m now back on 6.12.x.
Would like to add that my T14s 64GB with mem=31G has been running vanilla 6.14-rc4 without issues.
I have a T14s 64GB with cutmem 0x8800000000 0x8fffffffff in grub.cfg (to limit to 32GB). Other methods did initially not work for me.
I have never had issues with bluescreens since (currently on 6.14.0-14-qcom-x1e).
I’d really be interested in an actual fix for this, though. Is anybody working on that?
edit: not meant as a demand, obviously. Just curious if something is happening behind the scenes, or whether people don’t expect this be worked on / fixed.
The only party that could possibly work on this is Qualcomm because it seems to be a firmware issue. I think they are aware and have looked into it at some point, but I don’t know what the current state on their side is.
1 Like
t14s 64gb: I just had a random crash with blue screen. Using 6.14.0-17-qcom-x1e.
Are there any known issues with this kernel?
Probably a bug in 6.14, I have also hit one of those recently. I don’t think it is related to the 32GB issue even though the symptoms are similar.
What I did not mention, I’m using a usb-c dock and an external display with alt-mode. I have the impression that there is a correlation between the external display and the crashes.
I did apt update && apt upgrade on my Omnibook 14 X an hour ago. I saw it installed the new kernel and a large group of other firmware packages and more. I rebooted, and after that the screen is just blank.
I guess I will try to make a rescue USB stick on another computer and see if anything can be rescued.
You should be able to just switch to the older kernel from the grub menu (under “Advanced options for Ubuntu” or similar)
1 Like
@ogra yes I realized that. And yes, booting 6.12 works. So it’s a broken kernel version.
But WiFi no longer works now. A broken firmware problem too perhaps.
2 Likes
@ogra yes I realized that. And yes, booting 6.12 works. So it’s a broken kernel version.
But WiFi no longer works now. A broken firmware problem too perhaps.
Wifi might just be a bit flaky, might come back after a reboot.
@glathe has been working on a fix for the 6.14 regression on the Omnibook, I’ll try to get it into the next kernel build.
First of all, thanks to everyone working on Linux Support for this SoC.
I’ve been contemplating getting a Thinkpad T14s Gen 6 with Snapdragon X and perhaps it can be my gateway into Linux kernel development. However, I don’t want to throw such a substantial amount of money into a laptop if its unlikely we will get full Linux support anytime soon. Reading this blog post gives me the impression that a small team at Qualcomm is working on this, but there’s a lot more to be done.
So, if I may be so rude and ask: Is there any realism in getting this fully supported at all in the foreseeable future? Including the NPU, proper power management, USB4, camera, etc, or is it more likely we will end up in a similar state to Asahi where we get the basics working but struggle with the more complex components?
1 Like
I too get random (?) crashes on the 6.14.0-17-qcom-x1e kernel during work today. Switching back to 6.12 just in time for a meeting presentation and it was stable (phew).
EDIT: Using the cutmem fix on my T14s (64GB originally). So likely not related to that.
I think it might be a bug in ath12k that was introduced in 6.14. Looks like a fix is already being worked on upstream.
Do you have a link to that? I tried to find but failed.
I’ve been using my T14s all day, running 6.14-rc4 and connected to wifi roaming different networks. 
There is some discussion about it here https://oftc.irclog.whitequark.org/aarch64-laptops/search?q=ath12k
1 Like