Lenovo Yoga 9 14ITL5

From ArchWiki
Jump to navigation Jump to search
Hardware PCI/USB ID Working?
Touchpad Yes
Keyboard Yes
Touchscreen Yes
Stylus Yes
Video 8086:9a49 Yes
Webcam (Chicony) 04f2:b61e Yes
Bluetooth 8087:0026 Yes
Audio 8086:a0c8 Yes
Wireless 8086:a0f0 Yes
Accelerometer 8086:a0fc Yes
Tablet mode trigger No
Fingerprint reader 0bda:5812 No

Installation

Use F2 to enter BIOS. You must disable Secure Boot to be able to boot from the installation media. UEFI boot mode (OS Optimized Defaults) is working fine and can be used.

Should you have enabled the VMD controller in the BIOS, you must add vmd to the mkinitcpio.conf MODULES array before you regenerate the initramfs. See also [1].

Firmware

Support for firmware updates through fwupd is supported. But Lenovo so far only provides firmware updates for devices where Linux is officially supported (Thinkpad/ThinkCentre series). As this is not a device of these series, do not expect firmware updates through fwupd.

Firmware updates through fwupd are available for the following components:

  • System firmware (Lenovo)
  • UEFI (Lenovo)
  • NVM Express Solid State Drive (Sandisk)

Patched kernel

There is a custom kernel for the Yoga 9 that provides patches for the #Lid switch and #Charging bugs discussed in this article. The kernel is based on the Linux Mainline Kernel v5.14 and will be upgraded to v5.15 once it is released.

The kernel is provided by the package linux-yoga9AUR.

After installing the kernel, make sure to update the configuration of your specific bootloader. For example, see GRUB#Generate the main configuration file for GRUB.

Suspend

The important System Sleep State S3 for suspending the device is not available. Forcibly suspending the device to S3 leads to it locking up. If this happens, you can restore your device to working order via a hard reset. To hard reset the Yoga 9, press the power button for at least 15 seconds.

For now if you suspend this laptop it will enter S2idle mode by default. This mode will not decrease power consumption by much. It is therefore recommended to use hibernation as the action when the lid is closed.

Lid switch

The handling of the lid switch is broken. After waking from hibernation, the lid is reported as closed. Once closing the lid and reopening restores the correct state. This bug can only be solved within the Linux kernel. An appropriate patch will be available in Kernel v5.15.

For now you may use the custom kernel as described in #Patched kernel.

Accelerometer

You must use iio-sensor-proxy-gitAUR instead of iio-sensor-proxy for the accelerometer to work. It is important to note, that the trigger for tablet mode does currently not work. At least within KDE you can enable automatic screen rotation only globally.

Sound

This laptop requires firmware in order for the soundcard to work. See Advanced Linux Sound Architecture#ALSA firmware.

Thermals

It is recommended to enable OS Optimized Defaults in the BIOS settings. Enabling this option improves the thermal properties of the system tremendously. Without it, thermald will not throttle the system before it is near its critical temperature. You may want to select the appropriate cooling strategy in the BIOS (intelligent/performance/power saving).

Power management

Tools like tp_smapi or tpacpi-bat do not work with this device.

To set the Battery Conservation Mode see Laptop/Lenovo#Battery Conservation Mode on IdeaPad laptops.

Charging

Whether the charging cable is connected, is not determined reliably with the current stable kernel (5.13.12). On some occasions, upower -d reports the system as being plugged in even though it is not. This is because the UCSI driver is broken in this kernel. Kernel 5.14-rc7 improves the situation but breaks the UCSI driver even more.

A patch series is in the works that will fix the UCSI driver again. For now, you may use the custom kernel as described in #Patched kernel, that includes the current state of this series.

Wireless devices

Rfkill reports two additional devices (ideapad_wlan, ideapad_bluetooth). Blocking or unblocking these devices has no effect. Instead use the devices:

  • phy0 for Wireless LAN
  • hci0 for Bluetooth

Function keys

Fn lock only locks for F1 to F12. The Ins and the PrintScreen buttons still require the use of Fn even with Fn lock enabled.

Key Visible?1 Marked?2 Effect
Fn+Esc No Yes Toggles Fn lock
Fn+F1 Yes Yes XF86AudioMute
Fn+F2 Yes Yes XF86AudioLowerVolume
Fn+F3 Yes Yes XF86AudioRaiseVolume
Fn+F4 Yes Yes XF86AudioMicMute
Fn+F5 Yes Yes XF86MonBrightnessDown
Fn+F6 Yes Yes XF86MonBrightnessUp
Fn+F7 Yes Yes Super+p
Fn+F8 Yes Yes XF86RFKill
Fn+F9 Yes Yes Super+i
Fn+F10 Yes Yes Super+l
Fn+F11 Yes Yes Ctrl+Alt+Tab
Fn+F12 Yes Yes XF86Calculator
Fn+Ins No Yes Starts Lenovo Vantage on Windows
Fn+PrintScreen No Yes Starts the Snippig tool on Windows
Fn+Space No Yes Cycles states of keyboard backlight
Fn+Up Yes Yes PageUp (in xev Prior)
Fn+Down Yes Yes PageDown (in xev Next)
Fn+Left Yes Yes Home
Fn+Right Yes Yes End
  1. The key is visible to xev and similar tools.
  2. The physical key has a symbol on it, which describes its function.
  3. systemd-logind handles this by default.