hi, sorry I thought I had snapdragon x pro. It turn out I have snapdragon x plus which is not supported. but thank you for answering
1 Like
That depends what you mean with “not supported”. There is x1 and x1p42 support for Lenovo Thinkbook 16, Asus Vivobook 15, Asus Zenbook 14, but not (completely?) in the ISO. Missing is HP Omnibook, Lenovo Yoga for x1p. But this will come in time.
1 Like
I have thinkbook 16 g7, I don’t know if it changes my situation
1 Like
That’s what I have 
It is my test platform for the x1plus stuff. The support is not yet in Ubuntu Concept (?), I made a bootable image for it that is pre-installed desktop. This can boot from USB type-a stick or SSD, works reasonably well. The newer kernels I occasionally publish all carry the x1p patches, so you could also try newer ones.
Mine is currently running with plucky development branch (25.04) on X11, with 6.15-rc1. And sound. There is also a discussion thread on my repo regarding this model.
This might not be the right place to ask, but: The current plucky puffin beta images are without Wifi.
My 3 week old plucky daily build runs really good. No screen dimming, no sound, but mostly good.
Did they remove some of the drivers in the linux kernel? Any idea why this happens in the latest images from the last 1 week?
txh, I booted it but after a short while and a wall of propts it gave me a prompt:
ALERT! UUID=(uuid number) does not exist. dropping to a shell
then it just gives continuously prompt:
task kworker/… blocked for more that x seconds
I tried to do something in grub but it also didn’t work.
I suggest you switch to the mentioned discussion. A few questions.
- did you decrypt your Windows partition? The image does odd things when not.
- did you boot from type-a USB? type-c with firmwares loaded are problematic, like root file system not accessible.
Hi ! I’m new to this bandwagon. I am test-driving an Elitebook Ultra G1Q. So far, by reading the thread I managed to get both sound, wifi and of course the battery icon working by extracting the firmware from windows.
Now, I was wondering if anyone had the hotkeys working ? I’d like to use the Fn key for dimming and adjusting the volume.
1 Like
Hi, welcome No, not yet, haven’t tried in that direction. KB lighting (for the Omnibook X14) and the Fn keys appear to be controlled by the EC. On the Yoga Slim 7x there is a definition for EC controller, and also a driver AFAIK.
Yes, the keyboard buttons for dimming has always worked on the Yoga slim 7x 
During the recent time of using 6.14.0-30 and 6.14.0-32, I have encountered the following regressions:
External screens
External screen handling has become much less reliable. It used to be the case that rarely the external screen (USB-C) was not recognised as such and only showed 640x480. Re-attaching the usb-cable always fixed this.
Now, I sometimes have the situation that it is not detected at all (i.e. it stays black and re-attaching the cable does not work). This happens in particular after device powersaving (screensaver) turns off the screens. Only switching to another USB-C port gets the screen back on. This happens often enough for sometimes both USB-C ports to become unusable and me having to restart the computer.
Unintended reboots
Leaving the device idle and returning after a while, I often find it having rebooted. This does not happen while I actively use it, so it is likely related to powersaving, as well.
Firefox hwdec not working anymore
I used to have this working, now it’s back to software again. about:support reports FEATURE_FAILURE_VIDEO_DECODING_TEST_FAILED
I am not sure at which kernel version this happened exactly.
Would there be any benefit to me [T14s] switching to @glathe 's 6.15-rc1 image?
I’ve experienced unintended reboots as well, unfortunately.
Regarding Firefox and video acceleration:
% vainfo
Trying display: wayland
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib/aarch64-linux-gnu/dri/msm_drv_video.so
libva info: va_openDriver() returns -1
The mentioned file does not exist. But then again, we aren’t even using vaapi, are we?
I have also tried mpv --hwdec=v4l2m2m-copy, but it fails with
[ffmpeg/video] h264_v4l2m2m: Could not find a valid device
[ffmpeg/video] h264_v4l2m2m: can't configure decoder
Could not open codec.
Regarding the screen problems. I just had them again. After unlocking, the screen did not come back on, and dmesg reports:
[43322.405184] [drm:msm_dp_ctrl_link_train_1_2 [msm]] *ERROR* link training #2 on phy 1 failed. ret=-110
[43322.407074] [drm:msm_dp_ctrl_link_train [msm]] *ERROR* link training of LTTPR(s) failed. ret=-110
[45473.559309] [drm:msm_dp_ctrl_link_train_1_2 [msm]] *ERROR* link training #2 on phy 1 failed. ret=-110
[45473.561746] [drm:msm_dp_ctrl_link_train [msm]] *ERROR* link training of LTTPR(s) failed. ret=-110
However, swaymsg -t get_outputs still reports the screen as regular:
Output DP-2 'Philips Consumer Electronics Company PHL 279P1 UK82111000137'
Current mode: 3840x2160 @ 59.997 Hz
Power: on
Position: 1599,0
Scale factor: 1.400000
Scale filter: linear
Subpixel hinting: unknown
Transform: normal
Workspace: 1 www
Max render time: off
Adaptive sync: disabled
Available modes:
3840x2160 @ 59.997 Hz
3840x2160 @ 29.981 Hz
1920x2160 @ 59.988 Hz
[...]
And I can still move the mouse to the (invisible) screen area.
After unplugging and replugging, the external screen comes back on, but with resolutions 640x480. Dmesg reports:
[45602.182511] [drm:msm_dp_bridge_get_modes [msm]] *ERROR* failed to get DP sink modes, rc=0
And sway now also lack the proper infos:
Output DP-2 'Unknown Unknown Unknown'
Current mode: 640x480 @ 59.940 Hz
Power: on
Position: 1599,0
Scale factor: 1.000000
Scale filter: nearest
Subpixel hinting: unknown
Transform: normal
Workspace: 6
Max render time: off
Adaptive sync: disabled
Available modes:
640x480 @ 59.940 Hz
1024x768 @ 60.004 Hz
800x600 @ 60.317 Hz
800x600 @ 56.250 Hz
848x480 @ 60.000 Hz
Unplugging and replugging again, yielded a working desktop again.
Not that in all of the above instances, mouse+keyboard attached to the screen were still usable.
If there is a better place to report these things than here, please let me know.
Slim 7x has a bios update going out to facilitate signed qualcomm drivers (has improved adreno drivers). I was able to install and ubuntu concept is still working fine (although during the update secure boot was re-enabled). This took me from NHCN55WW to NHCN57WW - dmidecode states a release date of 01/03/2025.
Details → https://www.reddit.com/r/snapdragon/comments/1imx4qb/comment/mmbaryd/
3 Likes
hi!
I am using an acer swift 14 go ai with the snapdragon x plus. The issue i am facing is that after the installer image starts booting up it restarts the system every time. I disabled quiet splash in grub and it happens approx when starting systemd. I am not sure how to proceed, any help would be really appreciated!
1 Like
I haven’t tried @glathe 's 6.15-rc1 yet. May do it. But at the moment I am stying on the 6.14-rc7-3-qcom-x1e because everything is really stable for me. External video via usb-c works fine for example. Used my T14s in class today.
2 Likes
I tried @glathe 's 6.15-rc1 image with my t14s oled. I can only tell that the brightness control of the screen does not work. Same with the 6.14 kernel shipped with the Ubuntu 25.04 beta. For the time being I will stay on 6.14.0-32-qcom-x1e from the Concept, with which I can also observe the instabilities, likely due to the Wi-Fi bug and issues with a (Lenovo) USB-c docking station as you described.
1 Like
Since I don’t have these, does it load the right dtb? There’s one dedicated to OLED, no idea if it gets selected automatically. The file name would be x1e78100-lenovo-thinkpad-t14s-oled.dtb. You can copy it into your /boot/dtbs//qcom/ directory and symlink it from /boot like the original one was.
And there we go again, X Plus is x1p64100 or x1p42100? Qualcomm didn’t exactly make our lives easier with 2 SoCs with overlapping naming conditions, abut at least there’s support for it. The x1p64*/x1e* is already supported, the x1p42 variant… not. This will make at least 3 more x1p42 variants where the X1 Elite Version is supported by the Ubuntu Concept ISO… Something that is hard to keep up with.