Lenovo ThinkPad X13 Gen 3
| Hardware | PCI/USB ID | Working? |
|---|---|---|
| Touchpad | 04f3:3195 |
Yes |
| GPU | 8086:46a6 |
Yes |
| Webcam | 5986:2142 |
Yes |
| Bluetooth | 8087:0033 |
Yes |
| Audio | 8086:51c8 |
Yes |
| Wi-Fi | 8086:51f0 |
Yes |
| TPM | Untested |
| Hardware | PCI/USB ID | Working? |
|---|---|---|
| Touchpad | 06cb:ce68 |
Yes |
| TrackPoint | 0002:000a |
Yes |
| GPU | 1002:1681 |
Yes |
| Webcam | 174f:1812 |
Yes |
| Audio | 1022:15e3 |
Yes |
| Wi-Fi | 17cb:1103 |
Yes |
| Bluetooth | 10ab:9309 |
Yes |
| Fingerprint reader | 27c6:6594 |
Yes |
| Smartcard reader | 058f:9540 |
Yes |
| TPM | Yes |
The Lenovo ThinkPad X13 Gen 3 laptop was released in 2022. It is available with an Intel or AMD Ryzen CPU. Some models include a fingerprint reader, a Smartcard reader, and a WWAN card.
To figure out which model you are using, run dmidecode -t system as root: the Product Name field starts with 21BN or 21BQ on Intel models and with 21CM or 21CN on AMD models.
Accessibility
The BIOS offers two modes of operation, GUI and Simple Text.
The GUI can be navigated to some degree via the keyboard. Use the arrow keys to move the selection and Space to activate.
Switching to Simple Text can be accomplished by:
- Pressing
Leftto select the sidebar, thenDownto select Config, thenSpaceto activate it - Holding
Downfor two seconds to select the drop-down menu at the very bottom - Pressing
Leftto change it from Graphical to Simple Text - Pressing
F10, thenEnterto save and exit
Firmware
Firmware can be updated using fwupd. The UEFI BIOS can also be updated manually: download the ISO from Lenovo's support page for Intel or AMD models and use geteltoritoAUR to flash the BIOS from Linux. To check the BIOS version, run
$ cat /sys/class/dmi/id/bios_version
Sound
This laptop requires Sound Open Firmware in order for the sound card to work.
Function keys
| Key | Visible?1 | Marked?2 | Effect |
|---|---|---|---|
Fn |
Yes | No |
XF86WakeUp
|
Fn+Esc |
No | Yes | Enables Fn lock |
F1 |
Yes | Yes |
XF86AudioMute
|
F2 |
Yes | Yes |
XF86AudioLowerVolume
|
F3 |
Yes | Yes |
XF86AudioRaiseVolume
|
F4 |
Yes | Yes |
XF86AudioMicMute
|
F5 |
Yes | Yes |
XF86MonBrightnessDown
|
F6 |
Yes | Yes |
XF86MonBrightnessUp
|
F7 |
Yes | Yes |
XF86Display
|
F8 |
Yes | Yes |
XF86WLAN3
|
F9 |
Yes | Yes |
XF86Messenger
|
F10 |
Yes | Yes |
XF86Go
|
F11 |
Yes | Yes |
Cancel
|
F12 |
Yes | Yes |
XF86Favorites
|
Fn+Space |
No | Yes | Enables/disables keyboard backlight |
Fn+4 |
Yes | No |
XF86Sleep3
|
Fn+B |
Yes | No |
Ctrl_L+Break
|
Fn+P |
Yes | No |
Pause
|
Fn+K |
Yes | No |
Scroll Lock
|
Fn+Left |
Yes | No |
Home
|
Fn+Right |
Yes | No |
End
|
Fn+S |
Yes | No |
Alt_L+Sys_Req
|
Fn+End |
Yes | Yes |
Ins
|
Fn+L |
No | No | Set power profile to "low-power" (low)4 |
Fn+M |
No | No | Set power profile to "balanced" (medium)4 |
Fn+H |
No | No | Set power profile to "performance" (high)4 |
- The key is visible via
xevand similar tools - The physical key has a symbol on it, which describes its function
- systemd-logind handles this by default
- To see which profile is active run
cat /sys/firmware/acpi/platform_profile
Thunderbolt 4 Dock
The following issues were observed on AMD models with the Lenovo ThinkPad Thunderbolt 4 Dock (40B0).
Kernel crash on 7.2.x
On kernel 7.2.x, a NULL pointer dereference in dp_get_panel_mode (called from link_set_dpms_off) can occur when a display stream on the dock's DisplayPort/MST link is torn down, e.g. at boot, on monitor hotplug or when the external monitor flickers. It happens more often on linux-hardened, but has also been seen on linux. The fix, 8fa813b7fd1e ("drm/amd/display: Remove sink usage from DPMS"), is part of 7.3; a backport to 7.2.y has been proposed in drm/amd#5875. linux-lts is not affected.
Kernel crash on dock disconnect
A NULL pointer dereference in tb_dp_dprx_work can occur when the dock is disconnected, including during reboot, while a DisplayPort tunnel is still waiting for the monitor. The thunderbolt.dprx_timeout=-1 kernel parameter makes this much more likely, so avoid it. Fixes are queued for 7.3.
External monitors flicker
A monitor connected to the dock's DisplayPort output goes through the dock's cascaded MST hub even when it is the only monitor on the dock, and may flicker. Setting the kernel parameter amdgpu.dcdebugmask=0x16 fixed it in testing (2560x1440 at 144 Hz, with a second monitor on the laptop's own HDMI port): it disables DSC (0x4) and PSR (0x10), and additionally display stutter (0x2), without which flickering could still be triggered after a period of full CPU load. Disabling stutter slightly increases idle power consumption.
Wrong EDID after a cold boot
After a cold boot, the dock's MST hub may report its own EDID (NOVATEK, 1920x1080) instead of the monitor's, resulting in a mirrored low-resolution output. Unplugging the dock from power for about a minute restores the correct EDID.
See also
- Specifications: Intel, AMD
- Official service manual
- Ubuntu certification: Intel, AMD
- Hardware probes