Thanks @glathe, very useful info.
I tried to bodgy up a device tree for the x1p42100 by using device-tree-compiler to convert the devicetree blob at /casper/dtbs/x1e80100-asus-vivobook-s15.dtb to its equivalent text file .dts and then editing out the third cluster of CPU cores (and associated third cluster entry itself and their respective power domains and top and bottom thermals). Converted it back to a .dtb blob which I slipped in via dd to the 20241212 install iso (with some trailing zeros to pad out to the old dtb file’s length).
The good news is that my amateurish meddling didn’t result in a thermal runaway event that ignited my laptop. The bad news is that my bodgy devicetree blob was no more successful than all the other failed dtbs.
Don’t try this at home, kids.
I was afraid I smoked my T14s - compiling stuff with sensors showing a CPU temp of 96 degrees (Celsius), then it suddenly tuned OFF. But it seems like there was another issue, just a coincidence, since the syslog was showing nothing suspicious.
Just like the battery status: I was afraid that maybe the CPU temp is not dogwatched properly 
I did some more digging, but no success on actually booting the laptop. The BIOS (for the HP Omnibook, but I suspect others, too) contains fdts for Hamoa (X1E, 12/10 cores) and Purwa (X1P, 8 cores) variants. Comparing them you can see that there is a cluster of sensors that is not there in Purwa, but that’s not all that is different. The ACPI dsdt of the ThinkBook looks pretty familiar. Still need to wait for an x1p dtsi. There’s also a Purwa variant of the CRD, so it should come eventually.
For now its WSL2 and Windows fun. Could be worse.
I didn’t have time the last two weeks to work on this, but gave it another try again today with my T14s. As previously noted, I installed a setup with FDE that got stuck on a black screen after grub.
I have now chrooted into the installation and did an upgrade of the entire system. It complained that it couldn’t find an entry in the crypttab, but it looked like everything went fine. Did a reboot… and now I do get a regular Ubuntu loading splash after a brief black screen… but then I am dropped into the shell of the initramfs. My expertise is mostly in *BSD so I don’t really know what to do from the initram. Any advice?
Curiously, starting the recovery mode from Grub still yields only the black screen of nothingness.
edit: where there changes in the meantime that are supposed to fix FDE or should I try to patch the DT like previously suggested? If yes, did my chroot-upgrade break anything else?
edit: where there changes in the meantime that are supposed to fix FDE or should I try to patch the DT like previously suggested? If yes, did my chroot-upgrade break anything else?
In theory yes but I have not seen any confirmation yet that it worked. Might also depend on your exact hardware model. Is that the OLED t14s or the full-hd one?
Hi,
I’ve installed the image on my T14s 32gb oled. The most things are working well 
but I also have some issues.
The battery indicator is not working for me even after executing the qcom-firmware-extract script.
The most important issue for me is that I can’t use external displays via the lenovo dock.
If I can provide any information please let me know
Thx for your work 
Hi,
Is there anywhere I can find a device tree for x1p42100? It’s a snapdragon x plus, running on Asus ProArt PZ13. The question is a little off-topic, I know, please go easy
Unfortunately, not yet. I gave up my own shot at it, waiting for qc/linaro to publish something.
Just got my T14s gen6 64GB non-touch low power IPS display. Everything went smooth installing Ubuntu by just following the instructions at top of this page. However, I have the same problem: battery indicator not working.
Is there more to do presently?
I was pleasantly surprised that Bluetooth headset works (not tried the mic yet). A soon as the camera works in TEAMS/Zoom I can daily drive this machine. Right now mainly a glorified typewriter.
I was trying to update from jelly and I have found myself joyfully on 24.10 instead of 24.04.
No big deal, kinda works on a 2013 macbook pro to my surprise
The challenge I’m facing is that trying to open setting to increase trackpad speed. Clicking Mouse & Trackpad just crashes the setting program.
Anybody got some thoughts?
@tobhe do you know if Lenovo pushed a fix in their December bios upgrade for T14s? I’ve not had a GRUB issue since upgrading to the latest UEFI update.
Update on the T14s/1080p-LowPower/64GB with FDE:
I managed to fix the initrd from within the chroot of the live-system and upgrade the system. After a reboot, I now get the FDE password prompt!! But then there is a blue screen without text (never had this on linux), and then the system hard resets.
Although regular booting gets to after the password prompt, the recovery still doesn’t reach it (black screen, no password prompt).
I also realised in the chroot that /boot does not contain dts files for the current kernel (6.12.0-20), only for the originally installed one (6.12.0.17). Does the regular update process (apt update && apt upgrade) not generate these files for new kernels?
Same on my Vivobook S 15. I had to modify the qcom-firmware-extract script to find my unbitlocker’ed NTFS partition. Once I did that it mounted and extracted firmware and says that it installed it. Didn’t seem to change the battery indicator, nor the lack of sound. Anything else to try?
Thanks!
Lenovo Slim 7x. Seems mostly good except the reported issues (camera, hardware video decoding). Firefox snap seems to crash, so using Chromium snap for now. Lid open/close not detected, but the kernel patch seems to have just been sent in today. Battery indicator not working.
Battery indicator is biggest bugbear for me, and the fact the lid close doesn’t work. I’m curious when the next build will be available as it sounds like there are already fixes?
Note there is a lot of model specific details in launchpad here → Bug #2084191 " [X1E] Request: Add support for Lenovo Yoga Slim 7... : Bugs : ubuntu-concept
@pgratz @halmoni100 @thornley the battery indicator issue after qcom-firmware-extract was a bug and should hopefully be fixed after the next package upgrade. I have not built a new image yet but if you have a working installation apt update && apt upgrade is all you need.
Sound is WIP and will not be enabled by default soon because there is a high risk of permanent hardware damage (we don’t have active speaker protection at this point).
Is the display brightness adjustment known to work on a T14s 1920x1200 screens? It does not for me.
We had it working for a while but that broke something different. Once that is fixed we can bring it back
Some notes:
-
The regular expression in /usr/sbin/qcom-firmware-extract (l56) detects partitions like this:
(^nvme[0-9]n[0-9]p[0-9][[:space:]]ntfs$)
but there are multiple spaces between partition and type, therefore it fails for me. Changing it to
(^nvme[0-9]n[0-9]p[0-9][[:space:]]+ntfs$)
makes the script run through for me. -
Apt recommends I install
linux-qcom-x1e-toolsbut the package doesnt exist (but is referenced). Instead there islinux-tools-qcom-x1e, but it is empty…
Success: with the -21 kernel I again do not see the FDE prompt (that I could see with -20). However, if I now enter the passwort blind and press enter, the device pushes through and I can login 
What works so far:
- bluetooth + sound (Airpods)
- Youtube on Firefox (no crash, but looks like cpu decode)
- Wifi
- External 4k screen via DP via USB-C
- USB-hub in screen
- battery monitor seems to work
- external webcam
What doesn’t work so far:
- screen brightness control
- integrated speakers
- integrated webcam
I will test a bunch of packages next, and especially try with Firefox from the Mozilla PPA.