Tip: You may need to disable Kernel DMA protection in Security -> Virtualization -> Kernel DMA Protection - Set to "Disabled" Firmware issues When disabled, on Linux, power usage appears to be significantly higher because of a substantial number of CPU wakeups during s2idle. Config -> Thunderbolt BIOS Assist Mode - Set to "Enabled".To prevent this, remove the devices or disable bluetooth before suspending. Occasionally your Thinkpad will wake up immediately after suspending with certain bluetooth devices added. The same is true for other modern Thinkpads except for AMD models (as of November 2020). Mark Pearson, a Lenovo employee, recommends using the "Windows" sleep state option as it is better supported on modern Intel processors. One possible benefit to the Windows sleep state is faster wake up time, and one possible drawback is increased power usage. The Windows option is a newer software-based "modern standby" which works on Linux (despite the name). The Linux option is the traditional S3 power state where all hardware components are turned off except for the RAM, and it should work normally. The BIOS has two "Sleep State" options, Windows and Linux, which you can find in at Config -> Power -> Sleep State. The computer will be restarted and the UEFI BIOS will be updated.
#Thinkpad x1 dolby audio drivers install#
#Thinkpad x1 dolby audio drivers driver#
cab files from the Lenovo ThinkPad X1 Carbon (Gen 7) driver website. Lenovo may in the future provide cabinet files that can be directly installed with fwupdmgr.Ĭheck for Linux. If your thunderbolt port is unstable after upgrading with fwupd, you can visit the Lenovo ThinkPad X1 Carbon (Gen 7) driver website and upgrade the thunderbolt firmware manually. In August of 2018 Lenovo has joined the Linux Vendor Firmware Service (LVFS) project, which enables firmware updates from within the OS.īIOS updates (and possibly other firmware such as the Thunderbolt controller) can be queried for and installed through fwupd. Updates Automatic (Linux Vendor Firmware Service) Should the problem persist be sure to consult the UEFI#UEFI variables section. In case your efivars are not properly set it is most likely due to you not being booted into UEFI. For further information have a look at the Secure Boot article. However it is possible to self-sign your kernel and boot with it enabled.
The most convenient way to install Arch Linux is by disabling "Secure Boot" Security -> Secure Boot - Set to "Disabled". Warning: There are reports that enrolling custom Secure Boot keys may brick this machine because of firmware bugs.
0 kommentar(er)
