Disable Secure Boot during the installation.
The BIOS system has got two modes, Quick and Diagnostics. Both can install and boot Arch Linux correctly.
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.
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 (
F1 to enter BIOS and
F12 to enter boot menu.
- 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
You are able to use TPM 2.0
You are able to configure
after the Arch Linux installation.
Firmware data path
Follow ALSA for further steps.
After installation, follow Bluetooth.
No known issues.
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,
/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
- 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
evemu-record does not exist, Install .
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.
Seefor 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
- handle-suspend-key is also taken over by DE, check #Power buttons.
- But sleep is not.
xev test, every key has function of
So after making the device Sleep, you may press any key to resume.
||No||Yes||Notification Center (Windows only)|
||No||Yes||Answer the call (Windows only)|
||No||Yes||Ring off(Windows only)|
||No||Yes||Select areas for screenshot (Windows only)|
- The key is visible to
xevand similar tools
- The physical key has a symbol on it, which describes its function
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.