Lenovo ThinkPad E14 Gen 2 (Intel)

Hardware	PCI/USB ID	Working?
TrackPoint		Yes
Touchpad		Yes
GPU (Intel)	`8086:9a49`	Yes
GPU (NVIDIA)	`10de:1f97`	Yes
Webcam	`04f2:b6c2`	Yes
Ethernet	`10ec:8168`	Yes
Bluetooth	`8087:0026`	Yes
Audio	`8086:a0c8`	Yes
Wireless	`8086:a0f0`	Yes
TPM 2.0		Yes

Installation

Disable Secure Boot during the installation.

Install intel-ucode for the microcode and xf86-video-intel for the Intel graphics.

If you want to use NVIDIA graphics, try nouveau.

Accessibility

The BIOS system has got two modes, Quick and Diagnostics. Both can install and boot Arch Linux correctly.

Quick mode

The appearance of the BIOS is simple, not very colorful, but more modern and smooth, so it might work well with OCR software. However, it requires the user to use a mouse. Also, Before booting system, it shows the logo of Lenovo in the middle.

Note: Blind users should request the help of a sighted person to change BIOS settings

Diagnostics

The appearance will be traditionally blue and white using fonts with sawtooth, but you don't need a mouse, keyboard only. Also, Before booting system, it shows the black-and-white screen of computer information using fonts with sawtooth.

The service manual also contains shortcuts which are needed to trigger certain features, such as the boot menu and settings (Enter).

Use F1 to enter BIOS and F12 to enter boot menu.

Firmware

Note:

This device does not have a BIOS speaker and uses the built-in speakers instead. Beeps can be louder than expected.
To disable this quickly turn off FnLock and press F1 before booting.

You are able to use TPM 2.0 BIOS>Security>Secure Chip.

Secure Boot

You are able to configure

BIOS>Security>Secure boot

after the Arch Linux installation.

Firmware data path

This article or section needs expansion.

Reason: Untested. (Discuss in Talk:Lenovo ThinkPad E14 Gen 2 (Intel))

Logs

This article or section needs expansion.

Reason: Untested. (Discuss in Talk:Lenovo ThinkPad E14 Gen 2 (Intel))

Audio

Install sof-firmware from the extra repository.

Follow ALSA for additional details.

Bluetooth

After installation, follow Bluetooth.

Power management

No known issues.

Power buttons

This device has one detected power button and one sleep button.

$ loginctl seat-status

seat0
        Sessions: *3
         Devices:
                  ├─/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9
                  │ input:input9 "Video Bus"
                  ├─/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:45/LNXVIDEO:01/input/input10
                  │ input:input10 "Video Bus"
                  ├─/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
                  │ input:input0 "Power Button"
                  ├─/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
                  │ input:input2 "Lid Switch"
                  ├─/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
                  │ input:input1 "Sleep Button"
                  ├─/sys/devices/pci0000:00/0000:00:02.0/drm/card0
                  [...]

In this case, PNP0C0C:00 (/dev/input/event0) is a physical power button. You can verify this by inhibiting the handling of the power button.

# systemd-inhibit --what=handle-power-key sleep 1h

This article or section needs expansion.

Reason: Tested DE list need to be expanded (Discuss in Talk:Lenovo ThinkPad E14 Gen 2 (Intel))

Note:

If you are using DE, this command may be invalid to you.
Tested DE list: KDE Plasma, Gnome.
This is because the DE takes over the event of handle-power-key.
To change this, find power management in certain desktop environment's settings, then disable the reaction to power button.

and recording the events:

# stdbuf -o0 evemu-record /dev/input/event0

If evemu-record does not exist, Install evemu.

Pressing the power button should log an event.

The firmware will send many power button presses, so your machine will most likely only take a few seconds to power off because systemd kills the process/unit it is waiting for when the power button is pressed.

See logind.conf(5) for more information on handling specific keys.

Sleep & Wake up

You can use a USB keyboard with a Sleep button.

There is also a sleep button/suspend key. It is a virtual, firmware-handled key and will be triggered when using one of the #Unmarked keybinds, which would suspend your device. Use this to inhibit the handling of the suspend key.

# systemd-inhibit --what=sleep sleep 1h

Note:

handle-suspend-key is also taken over by DE, check #Power buttons.
But sleep is not.

According to xev test, every key has function of XF86WakeUp.

So after making the device Sleep, you may press any key to resume.

Function keys

Key	Visible?¹	Marked?²	Effect
`Fn+Esc`	No	Yes	Enables FnLock
`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	`XF86Display`
`Fn+F8`	Yes	Yes	`XF86WLAN`
`Fn+F9`	No	Yes	Notification Center (Windows only)
`Fn+F10`	No	Yes	Answer the call (Windows only)
`Fn+F11`	No	Yes	Ring off(Windows only)
`Fn+F12`	Yes	Yes	`XF86Favorites`
`Fn+Print`	No	Yes	Select areas for screenshot (Windows only)

The key is visible to xev and similar tools
The physical key has a symbol on it, which describes its function

Unmarked keybinds

This article or section needs expansion.

Reason: unfinished (Discuss in Talk:Lenovo ThinkPad E14 Gen 2 (Intel))

Intel Wi-Fi 6 AX201

For models with the Intel AX201 Wi-Fi adapter, the interface can engage in power saving when running on battery which increases network latency.

To avoid this issue, you can disable power saving by following the instructions in Power management#Network interfaces.