Same recommendation as above, also try the linux-generic 7.0.0-12.12 kernel from the archive to help us test that the version that will land in the actual release doesn’t cause any regressions!
[ASUS Zenbook A14 UX3407QA w/ x126100]
Hi All. I’m running with wifi, display, touchpad running. Some Fn keys not doing what they should (e.g., keyboard backlight). My big concern is verifying that the temperature control is working. I did download lm-sensors and fancontrol. Not sure where to go.
Here are some other (partial) error messages from dmesg, but I’m not sure if these are bad or not. I assume the ALSA message has to do with sound not working for people.
supply vdda* not found, using dummy regulator
Fixed dependency cycle(s) with /soc...
Direct firmware load for qcom/gen71500_sqe.fw failed with error -2
qcom-spmi-adc5-gen3 c42d000.spmi:pmic@0:adc@9000: error -EINVAL: No ADC channels found
qcom-spmi-adc5-gen3 c42d000.spmi:pmic@0:adc@9000: probe with driver qcom-spmi-adc5-gen3 failed with error -22
ALSA: Control name 'stream0.vol_ctrl0 MultiMedia1 Playback Volume' truncated to 'stream0.vol_ctrl0 MultiMedia1 Playback Volu'
I’d sure like to know if any of the above should cause concern for hardware health.
Thanks.
Oh, yea. kernel 7.0.0-31-qcom-x1e
2 Likes
one more item: I’m running sway and getting the following output:
00:00:17.621 [ERROR] [wlr] [libinput] event2 - hid-over-i2c 04F3:3315 Touchpad: client bug: event processing lagging behind by 30ms, your system is too slow
00:00:23.143 [ERROR] [wlr] [libinput] event2 - hid-over-i2c 04F3:3315 Touchpad: kernel bug: Touch jump detected and discarded.
See https://wayland.freedesktop.org/libinput/doc/1.31.0/touchpad-jumping-cursors.html for details
In addition, in emacs, switching windows in a frame (C-x-o keystroke) seems sluggish.
EDIT: I have touchpad output from libinput record. It’s about 800 KB: too big to post inline.
Linux defiant 7.0.0-12-qcom-x1e
No difference for me. tlp not really working, cam not working.
There is a new BIOS version 2.26 released 10th of March: https://pcsupport.lenovo.com/nl/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14s-gen-6-type-21n1-21n2/downloads/ds569693
Lenovo only provides a .exe, so Windows only.
@eric.molitor You are running 2.26. Do you notice any improvement? Will this enable 64GB with systemd-boot? There is not much information in the release history https://download.lenovo.com/pccbbs/mobiles/n42uj18w.html
How does a Lenovo BIOS update relate to Linux Vendor Firmware Service updates such as https://fwupd.org/lvfs/devices/com.lenovo.ThinkPadN4ISGXXW.NonVproNew4.firmware and https://fwupd.org/lvfs/devices/com.lenovo.ThinkPadN4ISGXXW.VproNew3.firmware ? (and what is the difference between these two anyhow 
)
Is there a procedure for Linux-only users to upgrade the BIOS? I thought about recovering Windows to perform the upgrade but there is no recovery media for a T14s Snapdragon according to https://pcsupport.lenovo.com/nl/en/lenovorecovery
There is a recovery Media for the Snapdragon T14s, but the procedure is tedious. You have to register the Device into your account, request the Media thing, use a windows tool to download it and write it to a USB device. Really really annoying, but works int the end.
2 Likes
I’m running the latest concept build on my Slim 7x and it runs pretty good, only issues are the camera not working (only works in qcam), suspend drains 5-6% an hour, and weird graphical glitches after waking up from suspend.
Does this build have big fixes not available in the concepts build or Or should I just do regular apt update to get the latest fixes?
I’m also planning on testing the linux-generic kernel but I’m not super familiar with how to install it.
Edit: Also anyone know how to enable Microsoft 3rd party eufi ca on the Slim 7x bios, can’t find it, so I can run Ubuntu with secure boot.
hey,
fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update
should work on the t14s
installed acpi and ran acpi -c which showed 44 cooling devices, for which 43 reported no state information available
$ fwupdmgr refresh --force
Updating lvfs
Downloading… [ - ]
Successfully downloaded new metadata:
• 14 devices are updatable
• 0 devices are supported in the enabled remotes (an update has been published)
$ fwupdmgr get-updates
Devices with no available firmware updates:
• hid-over-i2c 04F3:3195
• KEK CA
• KEK CA
• System Firmware
• TPM
• ThinkPad Product CA
• UEFI CA
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI dbx
• WD PC SN740 SDDQMQD-1T00-1201
• Windows UEFI CA
No updatable devices
$ fwupdmgr update
Devices with no available firmware updates:
• hid-over-i2c 04F3:3195
• KEK CA
• KEK CA
• System Firmware
• TPM
• ThinkPad Product CA
• UEFI CA
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI dbx
• WD PC SN740 SDDQMQD-1T00-1201
• Windows UEFI CA
No updatable devices
(tried with sudo as well)
according to journalctl -b -g BIOS and hostnamectl status I’m still at:
Firmware Version: N42ET85W (2.15 )
Firmware Date: Fri 2024-11-22
Are you sure you are able to update the bios of your T14s with fwupdmgr ?
Hey,
i did some diging and fwupdmgr are defintely the right way to do it. I am already on 2.26, I received the update through windows before I switched to Ununtu resolute.
Lenovo almost always release bios updates to windows first. It usually takes a few weeks maybe months before they opload those same files to the LVFS (the serivce fwupdmgr uses)
Update on this, so looks like i’m able to crash GNOME at the login screen, the GPU driver fails to load properly, and then
here’s overview:
Page flip failed: drmModeAtomicCommit: Invalid argument — this is the primary failure. GNOME Shell (Mutter) starts on Wayland but every frame flip is rejected by the MSM DRM kernel driver, so nothing renders and you’re stuck at a TTY.
There are two compounding issues:
-
DP link training failure — Your external Dell U2723QE (DP-1, 4K) shows as “connected” with valid EDID, but the actual DisplayPort link training times out (ret=-110). Mutter sees the display, tries to commit frames to it, and the driver rejects them. (tried again with no monitor, no PD) still crashing
-
MSM DPU atomic modesetting bug — The Qualcomm X1E80100 DRM driver is rejecting Mutter’s atomic commits. This is a known area of active development for Snapdragon X Elite on Linux.
(I saw this is problematic but didn’t cause issues in the past
I tired adding this to GRUB boot command line:
drm.atomic=0
but no luck… does anyone have a link to the google drive of the pre-build kernal packages? e.g @glathe 
Thinkpad T14s G6 LCD
=== Ubuntu version ===
PRETTY_NAME=“Ubuntu 25.10”
VERSION_ID=“25.10”
=== GNOME Shell version ===
GNOME Shell 49.0
=== Mutter version ===
ii mutter-common 49.0-2ubuntu5.3 all shared files for the Mutter window manager
=== linux-firmware version ===
ii linux-firmware 20250901.git993ff19b-0ubuntu1.10 all Firmware for Linux kernel drivers
Machine: Dell XPS 13 9345
Kernel: 7.0.0-31-qcom-x1e
ISO: https://people.canonical.com/~platform/images/ubuntu-concept/questing-desktop-arm64+x1e.iso
Hi there!
I’ve got my Dell a few days ago and I’m really happy how well Ubuntu works on this machine. Thanks to everyone involved! I appreciate your work dearly!
Now my issue:
I can’t get external displays to work properly.
Scenario 1 - Connect via USB-C to my Dell Monitor:
I get an image but it won’t disable the internal display if I close it. If I try to disable the internal display everything freezes until the “Keep Changes” timer runs out.
Scenario 2 Connect via USB-C hub and HDMI (Anker or UGreen) to my Samsung TV:
At first it seemed to work until I increased the refresh rate to 60Hz and increased the scale to 150%. Afterwards it freezes everything or shows nothing if I attach it after login. If I boot with the hub connected everything works until I login and then it freezes on one of the last frames of gdm (mouse still works).
Where would I have a look to start trouble shooting this?
PS: I read somewhere in this thread speakers should/might work but mine does not 
For me the biggest issue with dual monitor setups is that the screens get messed up almost everytime I turn off the screen/turn it back on or if I start the session with both screens plugged on or while unplugging/replugging. The only way to fix the issue is to reboot with screens unplugged, login and plug the screens back in.
Dmesg logs: gist:aaa9f5e26a18450384c1e4e9b4731684 · GitHub
Relevant parts seem to be:
[80790.337973] [drm:msm_dp_bridge_get_modes [msm]] *ERROR* failed to get DP sink modes, rc=0
Although I don’t see it now, I remember seeing EDID failure earlier in dmesg logs.
Laptop: Lenovo Yoga 7x
Wondering if someone knows what’s wrong and with which component.
HI @tobhe , does this include Samsung kernel and devicetree ? Sorry to keep asking at each release, i hope I am not annoying you 
I wish there was some kind of changelog posted with each release to avoid such questions
I’m thinking of getting the Yoga Slim 7x can someone tell me if audio is working on these devices running Ubuntu yet?
I can confirm. I have a Marhsall Stanmore II.
It works with 6.x but it doesn’t work with 7.x .
1 Like
This image still has the problem with hard resetting due to Grub being in console output mode instead of gfxterm. This is on the X1P + 5G + LCD version of the Surface Pro 11.
Suspend Issues:
I noticed that 26.04 Concept is failing to properly suspend on my T14s 64GB OLED WWAN:
[ 9988.432585] wlP4p1s0: deauthenticating from 62:22:32:16:ff:4b by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9989.998702] PM: suspend entry (s2idle)
[ 9990.005520] Filesystems sync: 0.006 seconds
[ 9990.184253] Freezing user space processes
[ 9990.186780] Freezing user space processes completed (elapsed 0.002 seconds)
[ 9990.186791] OOM killer disabled.
[ 9990.186797] Freezing remaining freezable tasks
[ 9990.190815] Freezing remaining freezable tasks completed (elapsed 0.004 seconds)
[ 9990.190827] printk: Suspending console(s) (use no_console_suspend to debug)
[ 9990.520866] mhi mhi1: Requested to power ON
[ 9990.520896] mhi mhi1: Power on setup success
[ 9990.618579] mhi mhi1: Wait for device to enter SBL or Mission mode
[ 9991.021710] ath12k_wifi7_pci 0004:01:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200
[ 9991.021724] ath12k_wifi7_pci 0004:01:00.0: fw_version 0x1103006c fw_build_timestamp 2026-03-06 09:10 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_UPSTREAM-3
[ 9991.279062] OOM killer enabled.
[ 9991.279073] Restarting tasks: Starting
[ 9991.281016] Restarting tasks: Done
[ 9991.281039] efivarfs: resyncing variable state
[ 9991.559673] efivarfs: finished resyncing variable state
[ 9991.559769] random: crng reseeded on system resumption
[ 9991.572457] PM: suspend exit
[ 9991.754631] tlp: vm.laptop_mode is deprecated. Ignoring setting.
[ 9998.067074] usb 5-1: reset full-speed USB device number 2 using xhci-hcd
[10007.989415] wlP4p1s0: authenticate with 62:22:32:16:ff:4b (local address=ec:91:61:26:b3:af)
[10007.989435] wlP4p1s0: send auth to 62:22:32:16:ff:4b (try 1/3)
[10007.993785] wlP4p1s0: authenticated
[10007.994459] wlP4p1s0: associate with 62:22:32:16:ff:4b (try 1/3)
[10007.997758] wlP4p1s0: RX AssocResp from 62:22:32:16:ff:4b (capab=0x1111 status=0 aid=27)
[10008.021638] wlP4p1s0: associated
[10008.021854] wlP4p1s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 62:22:32:16:ff:4b
[ 9989.998702] PM: suspend entry (s2idle)→This is when I closed the lid and the system attempted to enter “s2idle” (Software Suspend/Modern Standby).[ 9991.572457] PM: suspend exit→ This is when the system “woke up.”
Is there anything I can tweak to actually make suspend work?
thanks in advance
Hello. I am on 2.26 as well on mt T14s. I am sorry to say that I don’t recall how though (I haven’t booted into windows since December 2024). Probably I did use fwupdmgr.