Oh I just reread your description. I think that might be a known firmware issue and not actually kernel related. Try unplugging all periperals, reboot a few times. There is a race condition somewhere in the EFI boot parts, see Bug #2086540 “[T14s] (sometimes) unbootable system” : Bugs : ubuntu-concept and https://lore.kernel.org/lkml/Z0gn1N3IsP8r3gTA@hovoldconsulting.com/
I emailed the author of the blog post to try and figure out whether I’d missed anything, and far as I can tell, my machine is just unable to play nice with the bootstrap app for whatever reason. Whenever the install image tobhe mentioned earlier today is posted, I’ll try it out, but I worry I may simply be cursed 
.
The next installer build has an updated 6.14 kernel, I am slightly hopeful that it might work better on your machine. I already uploaded it at https://people.canonical.com/~platform/images/ubuntu-concept/oracular-desktop-arm64+x1e-20250215.iso but haven’t made it the default yet because I haven’t had time to test (and there seem to be problems with the Dell XPS).
2 Likes
Some of the bugs I encountered before kept popping up, but I persevered and finally made it to the screen that shows when it’s actually installing, and then… nothing. It just sits there, and nothing ever appears in the log.
6.12 DTS with 6.14 kernel still same errors on XPS. I’ve opened a bug report:
1 Like
I think I’m seeing some page cache corruption with 6.14 when compiling things. Perhaps -rc2 was a little early to switch to a new kernel, but hopefully whatever bug I’m hitting is found and fixed soon. (Only 32 GB of RAM here, so it’s not the 64 GB issue.)
1 Like
I have been running my 64GB-limited-to-31GB T14s with 6.14.0-rc2 for two full working days without issues. Compiling libreoffice and libreoffice-fresh for hours (and failing at tests, known issue for NixOS (Build failure: libreoffice-fresh (on aarch64-linux) · Issue #339942 · NixOS/nixpkgs · GitHub)).
How do you notice the page corruption?
1 Like
I’ve spent some time trying to reproduce it and haven’t managed to, so it’s probably pretty rare.
For trying to detect it happening again, I’ve kept a large file in RAM and used sha256sum every so often to check it hasn’t been corrupted.
Cannot Confirm
I do not get this error message described in the bug. It just freezes the second time grub appears.
That sounds very much like the symptoms I saw when I hit this though. Another one I have seen before is the firmware adding a broken UEFI boot entry. If you enter the UEFI boot setup (F12 I think) is there only one Ubuntu entry?
I’ve been having my t14s with 6.12.0-22-qcom-x1e crashing out of the blue lately. The screen just goes blank and it starts from the BIOS. Happens maybe once or twice a week using the system daily.
This is not 64gb ram issue, I’ve set up the 31g cutmem. Does not seem to be related to anything like heavy load.
I was not able to find any logs of what happened, would appreciate any pointers.
Haven’t seen anything like that but I think the best way forward would be updating to 6.14 to see if the problem is already fixed there
Did bluetooth break in 6.14? No longer seeing the adapter. Wifi seems to work still.
Bluetooth + WiFi is still working for me on 6.14 (yoga7x).
1 Like
Bluetooth and Wifi are working me for me too (yoga7x) in 6.14 (new iso from here) but if I turn Wifi off I get a “Black screen of death” and the laptop reboots.
Still have a empty screen at LVM encryption password and for some reason I can never use qcom-firmware-extract anymore since it always says “cant read windows partition” even after several reinstalls of windows and ubuntu. But I get the necessary files to install in other ways.
1 Like
On my t14 there is no BT when running the latest kernel, 6.14.0-5-qcom-x1e.
Rebooting to kernel 6.12 makes BT work again.
1 Like
I have a simple question: in what the X Plus differs from X Elite in terms of kernel support? Thanks 
1 Like
Same here! Bluetooth missing since upgrade. Also, internal sound does not work, although it was suggested that it might.
1 Like
YogaSlim7 @ 6.14.0-5-qcom-x1e: Bluetooth works properly.
No Bluetooth as well here on on my t14s since 6.14.0-5-qcom-x1e, worked seamless before with 6.12.x.
@lgr498 I also observed some crashes as you describe since one of the later 6.12.x kernel builds (not the ram issue, limit is set to 32g). Display turned dark and the system rebooted. My impression was that it happened only when connected to a USB-C dock with an external display. Do you have a display connected as well? No crashes since 6.14.0-5-qcom-x1e though.
Also I got (still) no sound with 6.14.0-5-qcom-x1e, not sure if it should have worked.