[X1E] Request: Add support for Lenovo Thinkpad T14s

Bug #2084178 reported by Tobias Heider
82
This bug affects 11 people
Affects Status Importance Assigned to Milestone
ubuntu-concept
Confirmed
Wishlist
Unassigned

Bug Description

Add support for the Snapdragon X Elite powered Lenovo Thinkpad T14s.

=== Device Information ===

Linux output:

user@user-ThinkPad-T14s-Gen-6:~$ sudo dmidecode -t 1
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x000A, DMI type 1, 27 bytes
System Information
 Manufacturer: LENOVO
 Product Name: 21N2ZC5QUS
 Version: ThinkPad T14s Gen 6
 Serial Number: XXXXXXX
 UUID: d4c111cc-2ec2-11b2-a85c-85e3f350d21c
 Wake-up Type: Power Switch
 SKU Number: LENOVO_MT_21N2_BU_Think_FM_ThinkPad T14s Gen 6
 Family: ThinkPad T14s Gen 6

user@user-ThinkPad-T14s-Gen-6:~$ cat /sys/devices/virtual/dmi/id/modalias
dmi:bvnLENOVO:bvrN42ET59W(1.33):bd09/12/2024:br1.33:efr1.24:svnLENOVO:pn21N2ZC5QUS:pvrThinkPadT14sGen6:rvnLENOVO:rn21N2ZC5QUS:rvrSDK0T76576WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21N2_BU_Think_FM_ThinkPadT14sGen6:

Alternatively from Windows:

PS C:\Users\user> Get-WmiObject Win32_ComputerSystemProduct

IdentifyingNumber : XXXXXXXX
Name : 21N2ZC5QUS
Vendor : LENOVO
Version : ThinkPad T14s Gen 6
Caption : Computer System Product

=== Kernel Support ===

Works with linux-qcom-x1e from the ppa

- No additional patches needed
- No additional modules needed in initrd

=== Device Tree ===

x1e78100-lenovo-thinkpad-t14s.dts from the linux-qcom-x1e package in the ppa, link: https://git.launchpad.net/~ubuntu-concept/ubuntu/+source/linux/+git/oracular/tree/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dts?h=qcom-x1e

Tags: t14s x1e
Tobias Heider (tobhe)
description: updated
Tobias Heider (tobhe)
Changed in ubuntu-concept:
importance: Undecided → Wishlist
Tobias Heider (tobhe)
description: updated
Tobias Heider (tobhe)
description: updated
information type: Public → Private
Tobias Heider (tobhe)
information type: Private → Public
Tobias Heider (tobhe)
Changed in ubuntu-concept:
status: New → Confirmed
Tobias Heider (tobhe)
tags: added: x1e
Revision history for this message
Tobias Heider (tobhe) wrote :

Latest kernel update (-35) enables bluetooth. Works on my machine.

Tobias Heider (tobhe)
tags: added: t14s
Revision history for this message
larsk (lars-karlslund) wrote :

Here's 'dmidecode -t system -u' output from a T14s Gen6 64GB OLED non-WWAN EU model with DK backlight keyboard

# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
 Header and Data:
  01 1B 09 00 01 02 03 04 4C 24 15 33 4E 27 B2 11
  A8 5C A8 07 0D F0 11 A7 06 05 06
 Strings:
  4C 45 4E 4F 56 4F 00
  LENOVO
  32 31 4E 31 43 54 4F 31 57 57 00
  21N1CTO1WW
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6
  50 57 30 30 30 30 30 30 00
  PW000000
  4C 45 4E 4F 56 4F 5F 4D 54 5F 32 31 4E 31 5F 42
  55 5F 54 68 69 6E 6B 5F 46 4D 5F 54 68 69 6E 6B
  50 61 64 20 54 31 34 73 20 47 65 6E 20 36 00
  LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6

Handle 0x001D, DMI type 12, 5 bytes
 Header and Data:
  0C 05 1D 00 00

Revision history for this message
sander (ookhoi) wrote :

ThinkPad T14s Gen 6 32GB LCD touch non-WWAN EU English backlit keyboard.

```
sudo nix run -- nixpkgs#dmidecode -t system -u
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
        Header and Data:
                01 1B 09 00 01 02 03 04 CC CB B8 91 3C 28 B2 11
                A8 5C A8 07 0D F0 11 A7 06 05 06
        Strings:
                4C 45 4E 4F 56 4F 00
                LENOVO
                32 31 4E 31 43 54 4F 31 57 57 00
                21N1CTO1WW
                54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
                6E 20 36 00
                ThinkPad T14s Gen 6
                50 57 30 44 47 4C 56 30 00
                <redacted>
                4C 45 4E 4F 56 4F 5F 4D 54 5F 32 31 4E 31 5F 42
                55 5F 54 68 69 6E 6B 5F 46 4D 5F 54 68 69 6E 6B
                50 61 64 20 54 31 34 73 20 47 65 6E 20 36 00
                LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
                54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
                6E 20 36 00
                ThinkPad T14s Gen 6

Handle 0x001D, DMI type 12, 5 bytes
        Header and Data:
                0C 05 1D 00 00
```

Revision history for this message
Jens Glathe (glathe) wrote :

Oof. Different configs same DMI?

Revision history for this message
Marc Lasch (mlasch) wrote :

T14s Gen 6, 64GB, OLED, non-WWAN, English EU Keyboard

`$ sudo dmidecode -t system -u`

# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
 Header and Data:
  01 1B 09 00 01 02 03 04 CC A7 F9 3A FF 26 B2 11
  A8 5C A8 07 0D F0 11 A7 06 05 06
 Strings:
  4C 45 4E 4F 56 4F 00
  LENOVO
  32 31 4E 31 43 54 4F 31 57 57 00
  21N1CTO1WW
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6
  50 57 30 45 4D 30 4C 4E 00
  PW0EM0LN
  4C 45 4E 4F 56 4F 5F 4D 54 5F 32 31 4E 31 5F 42
  55 5F 54 68 69 6E 6B 5F 46 4D 5F 54 68 69 6E 6B
  50 61 64 20 54 31 34 73 20 47 65 6E 20 36 00
  LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6

Handle 0x001D, DMI type 12, 5 bytes
 Header and Data:
  0C 05 1D 00 00

Revision history for this message
Arrigo Triulzi (arrigo) wrote :

T14s Gen 6, 64GB, OLED (2880x1800) non-WWAN, English US Keyboard

# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
 Header and Data:
  01 1B 09 00 01 02 03 04 4C A6 15 CD 27 27 B2 11
  A8 5C A8 07 0D F0 11 A7 06 05 06
 Strings:
  4C 45 4E 4F 56 4F 00
  LENOVO
  32 31 4E 31 43 54 4F 31 57 57 00
  21N1CTO1WW
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6
  50 57 30 45 4D 37 48 32 00
  <redacted>
  4C 45 4E 4F 56 4F 5F 4D 54 5F 32 31 4E 31 5F 42
  55 5F 54 68 69 6E 6B 5F 46 4D 5F 54 68 69 6E 6B
  50 61 64 20 54 31 34 73 20 47 65 6E 20 36 00
  LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6

Handle 0x001D, DMI type 12, 5 bytes
 Header and Data:
  0C 05 1D 00 00

Paulo Matos (pmatos)
information type: Public → Public Security
information type: Public Security → Public
Revision history for this message
RussianE39 (russiane39) wrote :

Adding quirks depending on ThinkPad Machine Type is not reliable, there is way too many of those, also some of those Machine Types would basically mean that laptop were custom ordered (so called CTO M/T) you can clearly see it in reports people posted before - as an example 21N1CTO1WW. Absolutely any possible configuration of T14s Gen6 could have that machine type if it was custom ordered.
Anyway, another report:
Its T14s Gen6 FullHD non Touch 32Gb 1Gb US keyboard:

Name : 21N10004CD
Vendor : LENOVO
Version : ThinkPad T14s Gen 6 Snapdragon
Caption : Computer System Product

BTW, none of the Ubuntu Concept images boots on this machine type (tried all of them from first to last). OpenBSD 7.6 and FreeBSD 15 boots on that M/T.

Revision history for this message
Tobias Heider (tobhe) wrote :

Interesting, I wasn't aware that there are T14s that don't boot. How far do you get? Boots up into a black screen? What if you remove splash quiet from the command line, any relevant output?

Revision history for this message
Kazuaki Ishiguro (gurokazu) wrote :

I have a similar T14s Gen6 Snapdragon OLED 16Gb US keyboard and encountered a same issue. Boots up into a black screen so I generated a log with the —verbose text option, and the following line caused a crash:

qcom-ice 1d90000.crypto: Unsupported ICE version: v0.0.0
qcom-ice 1d90000.crypto: probe with driver qcom-ice failed with error -95

Revision history for this message
Tobias Heider (tobhe) wrote :

Huh, interesting. Have you updated your firmware recently? I wonder why this only affects SOME machines. does adding qcom-ice.blacklist=yes to the kernel command line fix boot?

Revision history for this message
RussianE39 (russiane39) wrote :

Yes, there was Qualcomm Firmware Integration Package update recently. I was able to boot mine T14s only with manual edition of kernel cmdline in grub and adding proper devicetree.

Revision history for this message
Kazuaki Ishiguro (gurokazu) wrote :

I updated Qualcomm Firmware as well. But I could not still boot mine(shut down) with the following error:

Code: 52800400 8b214093 aa1303e1 97e80865 (b9400275)
---[ end trace 0000000000000000 ]---

Here is my setparams after hit e on "Try or Install Ubuntu":

set gfxpayload=keep
linux /casper/vmlinuz $cmdline --- splash qcom-ice.blacklist=yes console=tty0
initrd /casper/initrd
$dtb

Perhaps this information is pertinent:
https://<email address hidden>/T/

Revision history for this message
Tobias Heider (tobhe) wrote :

Kazuaki: Thanks for the info! I just published a new kernel with the fix applied and will let you know once there is an image with that kernel available!

Revision history for this message
Kazuaki Ishiguro (gurokazu) wrote :

Tobias: Thanks for the quick turnaround. Looking forward to the updated image with the new kernel. Let me know if you need anything else from my side.

Revision history for this message
Kazuaki Ishiguro (gurokazu) wrote :

I was also wondering if my chip is compatible or not, since mine is x-plus so the parts number should be either : x1p46100, or x1p62100?

I cannot find the list here:https://git.launchpad.net/~ubuntu-concept/ubuntu/+source/linux/+git/oracular/tree/arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dts?h=qcom-x1e#n18

model = "Lenovo ThinkPad T14s Gen 6";
compatible = "lenovo,thinkpad-t14s", "qcom,x1e78100", "qcom,x1e80100";

Revision history for this message
Kazuaki Ishiguro (gurokazu) wrote :

Correction of SKU:
either : x1p46100, or x1p42100

(btw, mine is x1p42100)

Revision history for this message
Tobias Heider (tobhe) wrote :

Probably not, Linux does not have any support for Purwa (8-core) chips yet. The only X1P chips that work are the 10-core Hamoa ones, so X1P-66-100 and X1P-64-100.

Revision history for this message
Kazuaki Ishiguro (gurokazu) wrote :

Understood. Is x1e-78-100 also supported? Additionally, will the Purwa chips be supported in the near future? I apologize for the numerous inquiries.

Revision history for this message
Tobias Heider (tobhe) wrote :

Yes, all the x1e (elite) are Hamoa and should work, I have an x1e78100 T14s myself and that works fine!

Revision history for this message
Tobias Heider (tobhe) wrote :

New image is up now and should contain the qcom-ice fix!

Revision history for this message
RussianE39 (russiane39) wrote :

Latest kernel dmesg attached. Battery gauge still not working and no sound. Probably it could be related to very latest bios/qcom firmware integration package?

Revision history for this message
Tobias Heider (tobhe) wrote :

> Latest kernel dmesg attached. Battery gauge still not working and no sound. Probably it could be related > to very latest bios/qcom firmware integration package?

Battery should work after you run qcom-firmware-extract on the installed system and reboot. Audio is expected to not work yet.

Looks like your error was actually fixed with the ice cherry-pick:
[ 0.567425] qcom-ice 1d90000.crypto: Unsupported ICE version: v0.0.0
[ 0.567428] qcom-ice 1d90000.crypto: probe with driver qcom-ice failed with error -95

Revision history for this message
RussianE39 (russiane39) wrote :

Updated to the very latest kernel, battery gauge finally works now, thanks a lot. Also, I have strong suspicion that very latest Win11 + latest qcom firmware integration package have different fw names. Latest kernel dmesg attached. Firmware extraction script log:
Mounting Windows partition nvme0n1p3...
Extracting firmware
    adsp_dtbs.elf
    adspr.jsn
    adsps.jsn
    adspua.jsn
    battmgr.jsn
    cdsp_dtbs.elf
    cdspr.jsn
    qcadsp8380.mbn
    qccdsp8380.mbn
    qcdxkmsuc8380.mbn
Building package qcom-x1e-firmware-extracted_20241214_arm64...
Installing qcom-x1e-firmware-extracted_20241214_arm64...
Done! Reboot to load the added firmware files.
umount: /tmp/fwfetch.UO9ScOWU/dislocker: not mounted

Revision history for this message
Riccardo Palombo (riccardopp) wrote :

T14s Gen 6, 32GB, IPS, non-touch, non-WWAN, Italian IT Keyboard

# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
 Header and Data:
  01 1B 09 00 01 02 03 04 4C BF 61 C1 BE 31 B2 11
  A8 5C 85 E3 F3 50 D2 1C 06 05 06
 Strings:
  4C 45 4E 4F 56 4F 00
  LENOVO
  32 31 4E 31 30 30 30 38 55 4B 00
  21N10008UK
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6
  50 57 30 43 39 37 4E 46 00
  PW0C97NF
  4C 45 4E 4F 56 4F 5F 4D 54 5F 32 31 4E 31 5F 42
  55 5F 54 68 69 6E 6B 5F 46 4D 5F 54 68 69 6E 6B
  50 61 64 20 54 31 34 73 20 47 65 6E 20 36 00
  LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6

Handle 0x001D, DMI type 12, 5 bytes
 Header and Data:
  0C 05 1D 00 00

Revision history for this message
Paulo Matos (pmatos) wrote :

Is the way to try this out through the installer image at:
https://people.canonical.com/~platform/images/ubuntu-concept/oracular-desktop-arm64+x1e.iso
?

Revision history for this message
Paulo Matos (pmatos) wrote :

When I try: https://people.canonical.com/~platform/images/ubuntu-concept/oracular-desktop-arm64+x1e.iso

I start it and press Try Ubuntu, I get into the graphical display but already have some graphical artifacts where some parts of dialogs don't disappear - they seem to get 'glued' to this initial ubuntu setup dialog which doesn't completely render.

Wifi looks fine, battery indicator doesn't work. This is the OLED version with 32Gb of RAM.

Revision history for this message
RussianE39 (russiane39) wrote :

Paulo, you need to adjust scaling of UI and then re-run installer again. It's a know issue with OLED verison

Revision history for this message
Joakim Holmberg (jokkeholmberg) wrote :

Here's 'dmidecode -t system -u' output from a T14s Gen6 64GB non-touch IPS non-WWAN EU model with SE backlight keyboard. Downloaded and installed the oracular-desktop-arm64+x1e.iso with kernel 6.12.0-20-qcom-x1e on 2024-12-17.

jokke@jokke-ThinkPad-T14s-Gen-6:~$ sudo dmidecode -t system -u
[sudo] lösenord för jokke:
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
 Header and Data:
  01 1B 09 00 01 02 03 04 4C 98 FF B6 41 2E B2 11
  A8 5C A8 07 0D F0 11 A7 06 05 06
 Strings:
  4C 45 4E 4F 56 4F 00
  LENOVO
  32 31 4E 32 53 30 52 51 30 30 00
  21N2S0RQ00
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6
  50 57 30 45 52 58 4C 33 00
  PW0ERXL3
  4C 45 4E 4F 56 4F 5F 4D 54 5F 32 31 4E 32 5F 42
  55 5F 54 68 69 6E 6B 5F 46 4D 5F 54 68 69 6E 6B
  50 61 64 20 54 31 34 73 20 47 65 6E 20 36 00
  LENOVO_MT_21N2_BU_Think_FM_ThinkPad T14s Gen 6
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6

Handle 0x001D, DMI type 12, 5 bytes
 Header and Data:
  0C 05 1D 00 00

Revision history for this message
Oleg (lgr498) wrote :

T14s/64G ram. I've loaded the firmware blobs using qcom-firmware-extract and running 6.12.0-20-qcom-x1e

It seems to work, except for:

- Battery level is not working
- Screen brightness stuck at max, does not change despite indicated brightness value changing.
- HDMI port

From previous reports, it looks like battery level indicator should work. Any ideas how to debug this?

Is the screen brightness adjustment supposed to work?

Thanks

dmidecode -t system -u
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
        Header and Data:
                01 1B 09 00 01 02 03 04 4C 68 AF 25 55 27 B2 11
                A8 5C A8 07 0D F0 11 A7 06 05 06
        Strings:
                4C 45 4E 4F 56 4F 00
                LENOVO
                32 31 4E 31 43 54 4F 31 57 57 00
                21N1CTO1WW
                54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
                6E 20 36 00
                ThinkPad T14s Gen 6
                50 57 30 45 4D 37 47 51 00
                PW0EM7GQ
                4C 45 4E 4F 56 4F 5F 4D 54 5F 32 31 4E 31 5F 42
                55 5F 54 68 69 6E 6B 5F 46 4D 5F 54 68 69 6E 6B
                50 61 64 20 54 31 34 73 20 47 65 6E 20 36 00
                LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
                54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
                6E 20 36 00
                ThinkPad T14s Gen 6

Handle 0x001D, DMI type 12, 5 bytes
        Header and Data:
                0C 05 1D 00 00

Revision history for this message
Oleg (lgr498) wrote :

Battery level works after I ran `sudo update-initramfs -u` (it was not using the correct dtb?)

Neither LCD brightness nor HDMI out work though.

Revision history for this message
Thomas Lundquist (thomasez) wrote (last edit ):

In case it's useful. T14s 32G Elite with touch. Norwegian backlit keyboard.

Battery indicator works with newest update, screen brightness does not, neither suspend.

 dmidecode -t system -u
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
 Header and Data:
  01 1B 09 00 01 02 03 04 CC B9 82 02 51 27 B2 11
  A8 5C A8 07 0D F0 11 A7 06 05 06
 Strings:
  4C 45 4E 4F 56 4F 00
  LENOVO
  32 31 4E 31 43 54 4F 31 57 57 00
  21N1CTO1WW
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6
  50 57 30 46 36 4E 43 59 00
  PW0F6NCY
  4C 45 4E 4F 56 4F 5F 4D 54 5F 32 31 4E 31 5F 42
  55 5F 54 68 69 6E 6B 5F 46 4D 5F 54 68 69 6E 6B
  50 61 64 20 54 31 34 73 20 47 65 6E 20 36 00
  LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
  54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
  6E 20 36 00
  ThinkPad T14s Gen 6

Handle 0x001D, DMI type 12, 5 bytes
 Header and Data:
  0C 05 1D 00 00

$ dmidecode -t 1
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
System Information
 Manufacturer: LENOVO
 Product Name: 21N1CTO1WW
 Version: ThinkPad T14s Gen 6
 Serial Number: PW0F6NCY
 UUID: 0282b9cc-2751-11b2-a85c-a8070df011a7
 Wake-up Type: Power Switch
 SKU Number: LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
 Family: ThinkPad T14s Gen 6

From lshw:
       description: Motherboard
       product: 21N1CTO1WW
       vendor: LENOVO
       physical id: 0
       version: SDK0T76574 WINptal
     *-firmware
          description: BIOS
          vendor: LENOVO
          physical id: 8
          version: N42ET85W (2.15 )
          date: 11/22/2024
          size: 128KiB
          capacity: 32MiB

Interesting,

     *-cpu:0
          description: CPU
          product: ARM (446)
          vendor: Qualcomm Technologies Inc
          physical id: 6
          bus info: cpu@0
          version: Snapdragon(R) X Elite - X1E78100 - Qualcomm(R) Oryon(TM) CPU
          serial: None
          slot: Qualcomm
          size: 2515MHz
          capacity: 3417MHz
          capabilities: lm cpufreq
          configuration: cores=12 enabledcores=12 threads=12

this is cpu 1:

     *-cpu:1 DISABLED
          description: CPU
          product: cpu
          physical id: 5
          bus info: cpu@0

2 to 15:

     *-cpu:2 DISABLED
          description: CPU
          product: cpu
          physical id: 7
          bus info: cpu@1
          size: 2515MHz
          capacity: 3417MHz
          capabilities: cpufreq

Revision history for this message
Dmitry Bilunov (dbilunov) wrote :

T14s 64G with touch, UK backlit keyboard.

Battery indicator works, backlight control does not.

% sudo nix run -- 'nixpkgs#dmidecode' -t system -u
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0009, DMI type 1, 27 bytes
        Header and Data:
                01 1B 09 00 01 02 03 04 4C E3 57 6D 99 27 B2 11
                A8 5C A8 07 0D F0 11 A7 06 05 06
        Strings:
                4C 45 4E 4F 56 4F 00
                LENOVO
                32 31 4E 31 43 54 4F 31 57 57 00
                21N1CTO1WW
                54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
                6E 20 36 00
                ThinkPad T14s Gen 6
                50 57 30 46 36 4E 43 58 00
                PW0F6NCX
                4C 45 4E 4F 56 4F 5F 4D 54 5F 32 31 4E 31 5F 42
                55 5F 54 68 69 6E 6B 5F 46 4D 5F 54 68 69 6E 6B
                50 61 64 20 54 31 34 73 20 47 65 6E 20 36 00
                LENOVO_MT_21N1_BU_Think_FM_ThinkPad T14s Gen 6
                54 68 69 6E 6B 50 61 64 20 54 31 34 73 20 47 65
                6E 20 36 00
                ThinkPad T14s Gen 6

Handle 0x001D, DMI type 12, 5 bytes
        Header and Data:
                0C 05 1D 00 00

% dmesg| grep panel-simple-dp-aux
[ 10.725132] panel-simple-dp-aux aux-aea0000.displayport-controller: Unknown panel AUO 0x37ac, using conservative timings
[ 10.725602] panel-simple-dp-aux aux-aea0000.displayport-controller: [drm:drm_panel_dp_aux_backlight [drm_display_helper]] DP AUX backlight is not supported

% hexdump -C /sys/class/drm/card0-eDP-1/edid
00000000 00 ff ff ff ff ff ff 00 06 af ac 37 00 00 00 00 |...........7....|
00000010 14 21 01 04 a5 1e 13 78 03 fd 25 99 59 53 92 26 |.!.....x..%.YS.&|
00000020 25 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 |%PT.............|
00000030 01 01 01 01 01 01 26 3d 80 b8 70 b0 28 40 10 10 |......&=..p.(@..|
00000040 3e 00 2d bc 10 00 00 18 00 00 00 fd 00 28 3c 4b |>.-..........(<K|
00000050 4b 10 01 0a 20 20 20 20 20 20 00 00 00 fe 00 41 |K... .....A|
00000060 55 4f 0a 20 20 20 20 20 20 20 20 20 00 00 00 fe |UO. ....|
00000070 00 42 31 34 30 55 41 4b 30 31 2e 33 20 0a 00 d8 |.B140UAK01.3 ...|
00000080

Revision history for this message
Dmitry Bilunov (dbilunov) wrote :
Revision history for this message
Oleg (lgr498) wrote :

Oh, just a dts change. Thanks for pointing it out. Tobias mentioned something on discourse, about removing the support because it broke other things, but having an actual commit is great.

@Dimitry, did you find it by searching the mailing list or is there another bug for the T14s changes?

Revision history for this message
Dmitry Bilunov (dbilunov) wrote :

@Oleg, I found it by looking at the kernel repository commit log (~ubuntu-concept/ubuntu/+source/linux/+git/oracular/log at launchpad) and trying out various kernels and dtbs on my T14s. This is the only bug I know for T14s changes.

Revision history for this message
Oleg (lgr498) wrote :

I can confirm that using a dtb with reverted https://git.launchpad.net/~ubuntu-concept/ubuntu/+source/linux/+git/oracular/commit/?h=x1e-6.12/200-t14s&id=dce657f91da932d9b2f4069b1c866c80cbd7503b makes brightness control work on my t14s with non-OLED display.

@Dmitry ack, thanks again for the comment about reverting the change.

Revision history for this message
Detzi88 (detzi88) wrote :

i can install an run ubuntu on my T14s G6 but as soon as i try to copy data from a usb disk (or sometimes even just open the drive in nautilus), i get a blue screen. I then have to force the session to shutdown long pressing the power button and after that the install wont boot any more. Grub does still appear to be working but fails to boot the install. Anyone else had these issues?

Revision history for this message
Oleg (lgr498) wrote :

I have the same issues with copying data. It happened with a USB drive, but once even while copying from a remote host (sshfs) to a local disk on T14. Then after the crash, the first attempt to boot up will fail and I need to power cycle. Then it boots ok.

Revision history for this message
Dmitry Bilunov (dbilunov) wrote :

@Detzi88, I have the same issue with the system crashing while copying files.

I have never experienced that issue with small files but I can reliably reproduce this with a Windows recovery image on a USB 2.0 thumb drive: if I mount it, then run md5sum over a large file (~750MB) then the system crashes and reboots.

Revision history for this message
Tobias Heider (tobhe) wrote :

@dbilunov: this is a known firmware issue. You can work around it by running `cutmem 0x8800000000 0x8fffffffff` from the grub command line before booting (or adding it to your grub.cfg). We should probably do that by default. Downside is you will only be able to use 32GB of memory.

29 comments hidden view all 109 comments
Revision history for this message
Tobias Heider (tobhe) wrote :

ookhoi: Could be. My current hypothesis is that it might be related to the ath12k issues people have been seeing on 6.14. Blue screens have previously been caused by the firmware if the OS did something it shoudln't.

We don't have a huge delta for the T14s, I'll push another update later and see if I can figure out what's going on.

Revision history for this message
Paulo Matos (pmatos) wrote :

Interesting - my machine now with 6.14.0-32-qcom-x1e started restarting under load. Has anyone seen this before? There's nothing obvious in journalctl from borked boots.

Any ideas what I could check to understand what's going on?

Revision history for this message
Paulo Matos (pmatos) wrote :

Actually it might not be load related but wifi related. I was just pointed to https://bugzilla.kernel.org/show_bug.cgi?id=219796 in a pvt discussion.

Revision history for this message
sander (ookhoi) wrote :

You mention "restarting under load". The wifi bug says "system hang".

Could it be your T14s restarts due to overheating?

During compiles I run: for i in $(seq 1000); do sleep 3; find /sys/devices/ -type f -name temp -exec cat '{}' ';' | sort | uniq | tail -1; done

Revision history for this message
Paulo Matos (pmatos) wrote :

Still get the reboot with wifi off so not wifi. It's due to load while compiling a large project. Temps are interesting:

95500
96000
96000
95100
95100
95100
95600
95900
95100
95200
95500
95100
95500
94700
95200

Are these normal temps? I don't know what I had before temp-wise.
I have been building this project for awhile and this didn't happen with a previous kernel so it makes me wonder what changed.

Revision history for this message
sander (ookhoi) wrote :

Above 95 degrees for more than a few seconds could definitely cause instant reboots. We are still missing thermal control on our X1E cpu.

I limit my builds to three cores (out of 12) which keeps it around 90 degrees.

Revision history for this message
Paulo Matos (pmatos) wrote :

Yeah, I think that's the issue. Warmer weather with the build in all cores is causing those reboots. Building for the last hour with `make -j1` (-j1 just in case) is working. :)

Revision history for this message
Tobias Heider (tobhe) wrote :

Interesting. I do not limit my builds and it still seems to max out at ~89 degC.

As I understand it the firmware should also throttle the CPU automatically, see https://lore.<email address hidden>/

In our qcom-x1e kernel we also do have support for cpufreq enabled.

Revision history for this message
sander (ookhoi) wrote :

I wasn't aware we have cpu throttling these days. I'll test when building 6.15 (currently running vanilla 6.14-rc7).

It seems for @pmatos cpu throttling is not working though.

Revision history for this message
Tobias Heider (tobhe) wrote :

It does sound like it doesn't yes. @pmatos maybe check if you can update your firmware?

Revision history for this message
Oleg (lgr498) wrote :

I'm also seeing temperatures >95 when using all cores. And this is with the latest firmware installed a few days ago from windows.

It does not crash always crash and perhaps it is the wifi issue. Often I'd let the machine just do its thing for a while (keyboard becomes uncomfortable to type on!) to come back to the LUKS unlock prompt later.

I wonder why that is different from @tobhe's experience. This is also on 6.14.0-32-qcom-x1e.

Revision history for this message
Detzi88 (detzi88) wrote (last edit ):

TLDR: I suspect its the same crappy controller FW as on my P!4s. It rather shuts down the whole system than setting the fan to full-speed. Maybe not only related to the T14s with ARM.

Regarding the high temps i think it is totally possible that it is just a bug in the fan controller firmware. I have a P14s G5 AMD that behaves much the same and kills itself on a quite reproducible basis with temps breaking 85°C even with moderate loads (12%ish). Windows seems to apply some "protection" and limits load to 80% after a few seconds which of course mitigates that problem but even pinning cpu and gpu to 100% (using wsl seems to "skip" the protection) does not lead to the system shuting down because it seems to set the fan to "full-speed" at some point which does not happen when using Ubuntu. thats why i now use thinkfan to set the fan to "full-speed" when any temp goes above 90°C. That said i did not test that its the same on the T14.

Revision history for this message
Paulo Matos (pmatos) wrote :

Tobias: I installed the firmware when I first installed ubuntu towards end of 2024. What's the procedure for updating the firmware these days?

Revision history for this message
Tobias Heider (tobhe) wrote (last edit ):

To be clear I am talking about the boot firmware, not device specific firmware. It can be updated from Windows with the Lenovo Vantage client or the installer from https://support.lenovo.com/uu/en/downloads/ds569777-qualcomm-integrated-system-software-and-firmware-package-for-windows-11-arm-version-24h2-or-later-thinkpad-t14s-gen-6-type-21n1-21n2

Device firmware is now shipped upstream in the linux-firmware package.

Revision history for this message
sander (ookhoi) wrote :

Do you happen to know if the Lenovo uefi firmware update can be applied from Linux?

Revision history for this message
Oleg (lgr498) wrote :

I'm using the fw from March 11 linked above, but still get system crashes with sustained high load. It restarted while building the linux kernel 2 out of 5 times I tried. The temperature was around 95 and was stable for over 10-20 minutes before the crash, so I've no idea what exactly triggered the crash.

Also I noticed that perhaps half a second before the crash, fans would suddenly start spinning faster.

Revision history for this message
Paulo Matos (pmatos) wrote :

Don't have windows at the moment, is there a way to update boot firmware from Linux?

Revision history for this message
Oleg (lgr498) wrote :

I noticed something strange with the PD charger on the t14. When the system gets hot/loaded for >20-30s the charging current would drop to a level below the power consumption, so the battery would be slowly draining.

This happens with the stock charger and any of the PD-capable chargers I have lying around. When I used a PD analyzer it seems that the laptop simply drops the current it is pulling from the power supply, voltage is kept at 20v.

However if I connect the charger through one of these [sharkoon multi port dongles](https://en.sharkoon.com/product/TypeCCombo) then it suddenly starts charging!

But if I reboot and don't unplug+plug the dongle, then we're not charging anymore.

`dmesg | grep battmgr` shows:
- Without the dongle:

[ 476.914139] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: unknown notification: 0x283
[ 476.992812] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: unknown notification: 0x483

- With dongle:

[ 488.930930] qcom_battmgr.pmic_glink_power_supply pmic_glink.power-supply.0: unknown notification: 0x283

Revision history for this message
Paulo Matos (pmatos) wrote :

Should we be updating to 25.04?

Revision history for this message
Paulo Matos (pmatos) wrote :

An apt update shows:

Suggested packages:
  linux-qcom-x1e-tools

but then:
~ sudo apt install linux-qcom-x1e-tools
Package linux-qcom-x1e-tools is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Error: Package 'linux-qcom-x1e-tools' has no installation candidate

Revision history for this message
Tobias Heider (tobhe) wrote :

Thanks Paulo, let me check that.

Revision history for this message
Ingo Komorowski (gaston69) wrote :

I have various problems running 24.10 or installing 25.05 on my T14s Gen6

N42ET85W (2.15)
64GB
Adreno X1-85
14" WUXGA (1920 x 1200), multitouch

Install with 24.10. concept works. But camera and touch (screen) do not.
Whenever I try to connect external storage (usb-A/c), the computer crashes in the moment i try to mount.

I have tried to upgrade via ubuntu-25.04-desktop-arm64.iso also via questing-desktop-arm64.iso. But both live-cds could not be booted. There is no error message, crash/reboot before grub is loaded.
Is there any chance to track what is going wrong there (why)?

Thanks for all support.

Revision history for this message
Marc Lasch (mlasch) wrote :

I can also observe issues with USB-A/c on my t14s gen6 oled. My impression is it got worse with recent kernel versions, 6.14 as well as with 6.15. Crashes/reboots are much more frequent than they used to be like two or three month ago. Apart from kernel updates there have also been one or two firmware updates made by Windows to the EC/BIOS. This might have also an impact, hard to tell.

Revision history for this message
Hannes (h-a-n-n-e-s) wrote :

> I noticed something strange with the PD charger on the t14. When the system gets hot/loaded for >20-30s the charging current would drop to a level below the power consumption, so the battery would be slowly draining.

I can confirm this.

Revision history for this message
christopher fujino (christopherfujino) wrote :

Has anyone successfully upgraded to 25.04? I noticed that the prebuilt images at https://people.canonical.com/~platform/images/ubuntu-concept/ are all still for oracular, so I wanted to check that if I upgrade the repos won't be missing certain packages or something like that.

Revision history for this message
Jens Glathe (glathe) wrote :

Running 25.04 on ~all boxes, one is currently upgrading. Most of them with do-release-upgrade, one with direct ISO install (HP Omnibook X 14 x1e7800 variant)

Revision history for this message
christopher fujino (christopherfujino) wrote :

> Running 25.04 on ~all boxes, one is currently upgrading. Most of them with do-release-upgrade, one with direct ISO install (HP Omnibook X 14 x1e7800 variant)

Thanks!

Revision history for this message
3DRaven (3draven) wrote :

dmidecode output

Revision history for this message
3DRaven (3draven) wrote :

I have the same issues with random reboots/bluescreens. Setting mem=32G, 31G, and 16G didn’t help, so I’ll try using cutmem. The reboots happen at random times, but more often when I try to download a lot of files. However, it’s definitely not only related to that, since it also reboots at other times.

Revision history for this message
3DRaven (3draven) wrote :

And on my laptop
1. used last firmwares from windows with qcom-firmware-extract
2. upgraded 24.10 concept to latest ubuntu 25.04 arm64

Revision history for this message
3DRaven (3draven) wrote :

sudo dmesg output log

Revision history for this message
P (pablothedeveloper) wrote :

Has anyone gotten the brightness controls to work?

I swear I was able to control it when I was installing the Ubuntu Concept 24.10 ISO but right after I upgraded it to Ubuntu 25.04 it stopped controlling the brightness.

Anyway I can help? I really wanna see snapdragon on T14 work perfectly!

Revision history for this message
Paulo Matos (pmatos) wrote :

@pablothedeveloper On 25.04 the brightness slider works but not control through the keyboard. For me, one of the most essentials things is audio which unfortunately does not work yet.

Revision history for this message
P (pablothedeveloper) wrote :

The slider works as in it shows a UI slider but the brightness remains the same.
If the brightness can be lowered that would be great.

For me the audio isn't as important as I'm not using this device for video calls or any audio content.

Oleg (lgr498) wrote on 2025-01-03 #36 a comment that says he got the brightness to work, is that something I can try?

I would really not want to break what I have working, is there a way to revert if whatever he did does cause an issue? I'm down to try it if someone can provide some basic instructions. I'm pretty unfamiliar with this.

Revision history for this message
Jens Glathe (glathe) wrote (last edit ):

There are 2 dtb variants, one for the OLED model (x1e78100-lenovo-thinkpad-t14s-oled.dtb) and the ips model (x1e78100-lenovo-thinkpad-t14s.dtb). The selection is (not yet) automatic, you need to select it yourself according to what you have.

I wrote about this here: https://discourse.ubuntu.com/t/ubuntu-24-10-concept-snapdragon-x-elite/48800/962

Revision history for this message
Tobias Heider (tobhe) wrote :

^ This is the correct answer. One minor addition: The latest flash-kernel update ships with the db changes.

If you have the OLED version you can add a file /etc/flash-kernel/machine with "Lenovo ThinkPad T14s Gen 6 (OLED)", run flash-kernel and reboot and it should work.
Please don't do this on the LCD version.

I am working on a way to migrate machines automatically to the correct dtb after the recent split but that might take a while to be released.

Revision history for this message
Jens Glathe (glathe) wrote :

I actually did just that after booting without any mods from the 250703 ISO on my new T14s 64GB OLED. The ISO correctly chose OLED, but the install didn't. After a look into the db I decided for machine entry as least invasive, worked well.
Overall, quite impressed with the smoothness of the install via the ISO. Well done.

Revision history for this message
Paulo Matos (pmatos) wrote :

Has anyone managed sound on the T14s, either through the builtin speakers or via wired headphones? This is one of the main blockers for me atm.

Revision history for this message
Jens Glathe (glathe) wrote :

Hi @pmatos,

yes I have activated sound on my T14s. Working nicely, as long as you have the adsp firmware loaded. I have made a wiki entry for it: https://github.com/jglathe/linux_ms_dev_kit/wiki/Enabling-sound-on-the-HP-Omnibook-X14,-Lenovo-Thinkbook-16
I guess I need to update some details eventually, but with this it is doable.

Revision history for this message
Faré (fahree) wrote :

I have a Lenovo Thinkpad T14s Gen6 21N1CTO1WW with 32GB, touchscreen.

Touchscreen, sound, camera do not work.

The WiFi, Bluetooth sometimes does not start properly—only cold reboot fixes it.

WiFi, bluetooth, trackpoint, do not restart properly after suspend—only cold reboot fixes it.

Bluetooth headset gets disconnected after a short time. WiFi may or may not—if so it reconnects automatically. USB headset has flaky sound, maybe also to having to disconnect/reconnect. Sometimes USB disk is fully disconnected while mounted and the filesystem becomes unavailable (remounted read-only, any read is an error).

USB seems to work again after suspend, but again, working state is lost along the way and devices disconnected.

Is there anything I can do to help with development?

Displaying first 40 and last 40 comments. View all 109 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.