A different topic:
I have seen quite a few people report that suspend & resume works for them. For me, it appears like it works (at least when not connected to a screen), but there is no actual power-saving, i.e. after a night in “suspend”, half of the battery is drained. This is significantly worse than my AMD laptop.
Is this the same for everyone / just not implemented? Or am I doing something wrong?
Hmm no idea. I can close it, pull power, reopen it after the night. There’s some percentage of power used up, but not half IMO. May be different with external display plugged in. Do you use HDMI connector?
Using my T14s daily as main non-work console, and in the evenings. Except for dev reboots (trying to get shared interrupt handling on i2c-hid) no crashes, great uptime.
I meant, “disconnect everything and close lid” (no usb-c, no hdmi). Next morning (~after 12 hours), I am down to 40-50% of battery.
Also, I thought HDMI doesn’t even work, yet? And leaving the USB-C screen plugged makes the device immediately wake up again.
I am also on T14s (64GB IPS).
6.16-el2-jg-5-qcom-x1e has working HDMI.
linux-qcom-x1e (6.16-el2-jg-5) plucky; urgency=medium
* add HDMI support for T14s V1 https://lore.kernel.org/all/20250821-topic-x1e80100-hdmi-v1-0-f14ad9430e88@linaro.org/
* add Lenovo Ideapad Slim 3
-- Jens Glathe <jens.glathe@oldschoololutions.biz> Thu, 18 Sep 2025 19:37:29 +0200
I have working HDMI on 6.17.0-8-qcom-x1e (T14s IPS 64 [downsized to 32]). I use the device just fine when my teaching demands a laptop and a huge external display.
No power savings what so ever when closing the lid.
I haven’t had the time to properly try the tricks (slbounce etc) to use 64 GB RAM yet.
Assuming you have a working slbounce boot on the T14s, could you clarify which steps are required to make it happen? Could I switch back to booting a regular kernel if something doesn’t work? Then at least the system doesn’t become unbootable if an upgrade breaks something.
Thank you! 
Ubuntu 25.10 has Released now. I downloaded Ubuntu 25.10 arm64. I read the grub.cfg, its code doesn’t refer dtb files now. Maybe it can search device auto now(maybe ACPI?). But it doesn’t support Surface Pro11(X1E-80100) now. I still can’t load Ubuntu. Grub still keep restarting by the watchdog. Set timeout=0, can’t load kernel now, because it still keep restarting. I could load the kernel but couldn’t load graphics and text mode before(by refer surface laptop 7’s dtb file). But now, I even can’t load the kernel.
This is the grub.cfg now:
set timeout=30
loadfont unicode
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
set cmdline=
smbios --type 4 --get-string 5 --set proc_version
regexp “Snapdragon.*” “$proc_version”
if [ $? = 0 ]; then
if [ $lockdown != “y” ]; then
cutmem 0x8800000000 0x8fffffffff
fi
cmdline=“clk_ignore_unused pd_ignore_unused arm64.nopauth”
fi
menuentry “Try or Install Ubuntu” {
set gfxpayload=keep
linux /casper/vmlinuz $cmdline — quiet splash console=tty0
initrd /casper/initrd
}
menuentry ‘Boot from next volume’ {
exit 1
}
menuentry ‘UEFI Firmware Settings’ {
fwsetup
}
I can’t find any dtb files in the ISO now, too.
I have updated to 25.10 and with 6.17.0-8-qcom-x1e, I also have working HDMI now. However, something is slightly off with colours/contrast. It’s not immediately visible, but it’s a bit annoying because low contrast differences become invisible, e.g. grey high-lighting on white background.
Anyone tried Ubuntu 25.10 with Snapdragon X Plus?
Working fine here, 2 devices. Actually using the 6.17.0-8 kernel as is on the Ideapad 5 2in1. 25.10 has the advantage of having a new enough Mesa to get GPU acceleration if all firmwares are there.
Tried it with the Samsung Galaxy Book 4 Edge with the X-Plus. Doesn’t boot.
Tried to install the official Ubuntu 25.10 arm64 iso onto ASUS Vivobook S15 X1P42100 - gets initial grub menu but then fails after outputting a line of text (too transient to read) and reboots.
Tried on Lenovo Yoga Air 14s Q8x9, everything works fine except camera and audio.
Thanks for the reminder. Need to upstream that one
How to hack the official Ubuntu 25.10 arm64 iso so it will boot on an ASUS Vivobook S15 X1P42100:
Mount the iso and copy the /boot/grub/grub.cfg to ~/grub.cfg and edit it to append the line
devicetree /casper/x1p42100-asus-vivobook-s15.dtb
after the initrd line.
Dismount iso.
Copy the device tree file x1p42100-asus-vivobook-s15.dtb to home directory
apt install xorriso
Then create new iso (4.6GB) with grub.cfg changed and the dtb added:
xorriso -indev ~/Downloads/ubuntu-25.10-desktop-arm64.iso -outdev ~/Downloads/ubuntu-25.10-desktop-arm64_x1p42100-asus-vivobook-s15.iso -boot_image any replay -update ~/grub.cfg /boot/grub/grub.cfg -update ~/x1p42100-asus-vivobook-s15.dtb /casper/x1p42100-asus-vivobook-s15.dtb -commit
This will let you install Ubuntu 25.10 but you won’t be able to reboot the target until you make similar changes to the target - append a “devicetree /boot/x1p42100-asus-vivobook-s15.dtb” line after all the initrd lines in /boot/grub/grub.cfg and put the .dtb file in /boot. Or if using LUKS/LVM encrypted root disk, which has a separate /boot file system, append “devicetree /x1p42100-asus-vivobook-s15.dtb”. Make a copy of this grub.cfg file as it will be overwritten when new kernels are generated and you’ll need to make similar changes to a new grub.cfg.
Installed on Asus Zenbook A14, installation went just fine.System boots successfully. But sill no Wi-fi and GPU acceleration.
Did it automatically grab the firmware from the Windows partition on your system? It didn’t on mine (I have the UX3407Q version). I had to use a USB Wi-Fi adapter and install+run qcom-firmware-extract manually.
The Wi-Fi doesn’t work for me, I get the following in dmesg:
[ 3.919457] ath11k_pci 0004:01:00.0: failed to fetch board data for bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=950a,qmi-chip-id=18,qmi-board-id=255,variant=UX3407Q from ath11k/WCN6855/hw2.1/board-2.bin
[ 3.919468] ath11k_pci 0004:01:00.0: failed to fetch board data for bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=950a,qmi-chip-id=18,qmi-board-id=255 from ath11k/WCN6855/hw2.1/board-2.bin
[ 3.919471] ath11k_pci 0004:01:00.0: failed to fetch board data for bus=pci,qmi-chip-id=18 from ath11k/WCN6855/hw2.1/board-2.bin
[ 3.919472] ath11k_pci 0004:01:00.0: failed to fetch board.bin from WCN6855/hw2.1
[ 3.919475] ath11k_pci 0004:01:00.0: qmi failed to fetch board file: -2
[ 3.919477] ath11k_pci 0004:01:00.0: failed to load board data file: -2
Which is the problem described, with a fix, here. I had to do that to get Wi-Fi working on 25.04. I’ve not yet tried it on 25.10.
I’ve no idea about getting GPU accelleration working. @glathe mentioned using the 6.17.0-8 kernel above when mentioning GPU acceleration. Is this perhaps significant?
ath11k needs an extra patched board file I’m afraid, having a similar situation on the Ideapad Slim 3. Also, fetching firmware needs to be initiated by the user in every case IMO. And you can get surprised sometimes, like today on my T14s with 25.10 (installed from 24.05 Concept a few months ago) - qcom-firmware-extract said to me “Hardware is currently not supported” - what?
I used my own script to fetch them then.
I’ve done a fresh install without my Wi-Fi stick and implemented the Wi-Fi fix I mentioned in my previous post before installing anything else so I could be sure the fix wasn’t dependent on anything I might have installed previously. The idea is that once you’ve got networking going it’s much easier to install other fixes - such as the qcom-firmware-extract package. I can confirm it doesn’t need anything other than the ath11k-bdencoder file it tells you do download and copy onto your system.
The addition I made to the board-2.json file is:
"names": [
"bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=950a,qmi-chip-id=18,qmi-board-id=255,variant=UX3407Q"
],
"data": "bus=pci,vendor=17cb,device=1103,subsystem-vendor=14cd,subsystem-device=950a,qmi-chip-id=18,qmi-board-id=255,variant=UX3407Q.bin"
},
This is suitable for the Asus Zenbook A14 UX3407Q version only and even if you have one, check the details against the dmesg errors on your system just to be sure.
@glathe Any suggestions for getting the GPU working?