What is strange is, once Ubuntu is installed, grub comes up without issue. I only need Ventoy to install. Never again after that. tbh, I havent tried to boot directly from usb with any of the new images since Ventoy works fine every time.
Does anyone know how to disable rfkill via the device tree? My wifi is recognized and loaded but hard blocked by rfkill. I cannot unblock it nor can i use any wifi adaptors when the firmware for athk12 is loaded. I have to rename the files in /lib/firmware/athk12 and reboot. Then i can use an external wifi adaptor. Appears Dwinham also had this issue and solved it with a kernel hack. I read his submission to the kernel and he mentioned disabling rfkill via device tree.
Hey, thinking of purchasing the Lenovo IdeaPad Slim 5 14Q8X9, with the Snapdragon® X Plus
X1P-42-100 CPU. I can only find 2 posts on this laptop online, one from nov 2024, and one from July 2025, both saying unsupported for linux. Has this changed? thanks.
Thanks @tobhe I tried this latest build but I guess Samsung Galaxy book is still not included? it just reboots the laptop after selecting Ubuntu from boot screen menu
I have the exact same laptop. I have dual boot using grub for WIndows11 and Linux. I have managed to install “plucky-desktop-arm64+x1e-20250827_extended_jg_7.iso” and then upgrade to questing. I haven’t been able to upgrade to resolute. I installed a dtb in the boot directory (x1p42100-lenovo-ideapad-slim5x.dtb). I also have a script, from qcom-firmware-extract, with a modification for the IdeaPad Slim 5.
Things that don’t work are HDMI and sound through the built-in speakers. I use bluetooth for sound and a microphone. Some software doesn’t work that well: Firefox, I ended up doing the manual install. Thunderbird only works with snap, but there are issues with the mouse.
in my bios setting i found ubuntu as boot option and the first one but it just cant boot i see my ssd led flashing like its read it and the restart to try to boot again and yes ventoy is the only way to boot to those iso files without grub menu freeze so is there any way to put my boot efi from the usb ssd in ventoy just to test it, ok i did this stupid test but me efi in ventoy as iso file but its just restart when i choose it
What device do you have? Do you have Secure Boot turned off? It needs to be off for this to work.
The latest Ubuntu 26.04 also crashes on the Thinkpad T14s 64G. I carelessly formatted the UEFI partition and lost access to Windows 
However, the installer itself works flawlessly and starts without any combinations.
From the perspective of a long time, ARM is a big mistake and a dead end
Just fixed that in an update. The 7.0 kernel exposed a firmware issue on 64 GB machines that wasn’t so easily triggered in previous versions.
1 Like
Yesterday’s version doesn’t work. Meaning, the next ones should work?
The fix is currently in resolute-proposed, see ubuntu-x1e-settings package : Ubuntu
Your options are:
- Wait a day for it to migrate
- Install from the concept ISO at https://people.canonical.com/~platform/images/ubuntu-concept/resolute-desktop-arm64+x1e.iso instead
- Fix it manually by entering the grub shell by pressing
cin the grub boot selection menu, runcutmem 0x8800000000 0x8fffffffff, pressESCto get back to the boot selection and then boot the default entry. Once booted addGRUB_BADRAM="0x8800000000,0xf800000000"to/etc/default/gruband runupdate-grub.
2 Likes
Do you happen to have a reference to that issue?
surface pro 11 and yes secure boot turn off, did you successfully install it on usb stick or you internal ssd ?
Installed to the internal nvme drive.
Dolby Audio for the Lenovo Slim 7x
I have implemented Dolby Speaker Tuning (FIR + Multiband Compressor + Limiter) and Asahi Linux Bankstown Bass Enhancement on the Slim 7x using the original Dolby tuning files on the Windows partition. I also added a speaker volume cap adapting some code written for the Thinkpad.
Note: I have not added any extra tuning of my own - the aim is to replicate the Dolby tuning as closely as possible using native Linux audio plugins.
Audio now sounds really good! Let me know if you have feedback.
Hi All,
Continuing to work on the Surface Pro 11 touchscreen, I am now able to get the spi-hid to finish probing correctly, this is the latest dmesg log:
Mar 28 10:25:26 SP11 kernel: spi-hid spi0.0: spi-hid probe called for device spi0.0
Mar 28 10:25:27 SP11 kernel: spi-hid spi0.0: spi_hid_probe: d3 → d0
Mar 28 10:25:27 SP11 kernel: spi-hid spi0.0: SPI transfer timed out
Mar 28 10:25:27 SP11 kernel: spi-hid spi0.0: error reading header, resetting -110
Mar 28 10:25:27 SP11 kernel: spi-hid spi0.0: Error Handler
Mar 28 10:25:27 SP11 kernel: spi-hid spi0.0: SPI transfer timed out
Mar 28 10:25:27 SP11 kernel: spi-hid spi0.0: error reading header, resetting -110
Mar 28 10:25:27 SP11 kernel: spi-hid spi0.0: Error Handler
Mar 28 10:25:28 SP11 kernel: spi-hid spi0.0: SPI transfer timed out
Mar 28 10:25:28 SP11 kernel: spi-hid spi0.0: error reading header, resetting -110
Mar 28 10:25:28 SP11 kernel: spi-hid spi0.0: Error Handler
Mar 28 10:25:28 SP11 kernel: spi-hid spi0.0: SPI transfer timed out
Mar 28 10:25:28 SP11 kernel: spi-hid spi0.0: error reading header, resetting -110
Mar 28 10:25:28 SP11 kernel: spi-hid spi0.0: Error Handler
Mar 28 10:25:28 SP11 kernel: spi-hid spi0.0: unresponsive device, aborting.
Mar 28 10:25:28 SP11 kernel: spi-hid spi0.0: spi_hid_error_work: error handler failed
I modified the spi-geni-qcom and dma/gsi.c driver to support QSPI mode by backporting the necessary modification from android driver spi-msm-geni.c
The modified dts is as follow:
/ {
compatible = “microsoft,denali”, “qcom,x1e80100”;/* Fixed regulator node at root level */ vreg_ts_5p0: ts-5p0-regulator { compatible = "regulator-fixed"; regulator-name = "vreg_ts_5p0"; regulator-min-microvolt = <5000000>; regulator-max-microvolt = <5000000>; gpio = <&tlmm 64 GPIO_ACTIVE_HIGH>; enable-active-high; pinctrl-names = "default"; pinctrl-0 = <&ts_5v_en_default_state>; };};
&spi10 {
status = “okay”;
hid@0 {
compatible = “hid-over-spi”;reg = <0>; spi-max-frequency = <50000000>; interrupts-extended = <&tlmm 51 IRQ_TYPE_EDGE_FALLING>; reset-gpios = <&tlmm 48 GPIO_ACTIVE_HIGH>; pinctrl-names = "active", "sleep", "reset"; pinctrl-0 = <&spi10_hid0_reset_deassert &spi10_hid0_int_bias>; pinctrl-1 = <&spi10_hid0_reset_assert &spi10_hid0_int_unbias>; pinctrl-2 = <&spi10_hid0_reset_assert &spi10_hid0_int_bias>; vdd-supply = <&vreg_ts_5p0>; spi-tx-bus-width = <4>; spi-rx-bus-width = <4>; hid-descr-addr = <1>; };};
&tlmm {
spi10_hid0_reset_deassert: spi10-hid1-reset-deassert {
pins = “gpio48”;
function = “gpio”;drive-strength = <2>; bias-disable; output-high; }; spi10_hid0_reset_assert: spi10-hid1-reset-assert { pins = "gpio48"; function = "gpio"; drive-strength = <2>; bias-disable; output-low; }; spi10_hid0_int_bias: spi10-hid1-int-bias { pins = "gpio51"; function = "gpio"; input-enable; bias-pull-up; }; spi10_hid0_int_unbias: spi10-hid1-int-unbias { pins = "gpio51"; function = "gpio"; input-enable; bias-disable; }; ts_5v_en_default_state: ts-5v-en-default-state { pins = "gpio64"; function = "gpio"; };};
Now need to figure out what is not working in the message sending process.
3 Likes
i installed it on my internal ssd and now its boot normally i think its issue with the usb 4 boot in surface but are you able to make the wifi, bluetooth and graphics working ? i installed the qcom-firmware extract but still no luck
Yes bluetooth, wifi and graphics are working.
The qualcomm firmware extract do not work with sp11 yet, I did a mix of this extract and the one from dwhinam.
I will post later all the changes I made as I am using a custom kernel and need to check what is available in qcom kernel
2 Likes
oh cant wait its really good almost stable if those three works i dont really care about touch screen
If you have a diff for qcom-firmware-extract I’d be happy to merge it!
1 Like