Dell XPS 13 2-in-1 (7390)

From Gentoo Wiki
Jump to:navigation Jump to:search

The Dell XPS 13 2-in-1 (7390, 2019) is an Intel Ice Lake (10th gen Core i processor, 10nm lithography) convertible, ultra portable laptop.

Hardware highlights

  • Up to Core i7-1065G7 CPU, 15W TDP
  • 11th Gen GPU, up to Iris Plus graphics
  • Up to 32GB of LPDDR4 RAM, clocked at 3773MHz
  • Up to 1TB NVMe SSD storage
  • Up to a 4K (3840x2400), 16:10 aspect ratio touchscreen with Wacom Active ES 2.0 Pen support
  • UEFI boot only

Hardware not working

  • Fingerprint reader (Goodix)
  • Camera (Intel IPU4)

Target setup

My personal system boots Gentoo as the only operating system (the included Windows 10 installation was wiped). Using Secure Boot and systemd-boot and full-disk (except ESP) LUKS encryption, with the sway window manager. My keyboard layout is United Kingdom (82-key).


FILE /etc/portage/make.conf
COMMON_FLAGS="-O2 -pipe -march=icelake-client"



Model is Intel (Killer Wireless) AX1650i and requires firmware from sys-kernel/linux-firmware. Because of the firmware, build the driver as a module, or include the firmware in your kernel build.

  • Wifi firmware: iwlwifi-Qu-c0-hr-b0-59.ucode
  • Bluetooth firmware intel/ibt-19-32-4.sfi, intel/ibt-19-32-4.ddc
[*] Networking support  --->
      [*] Wireless  --->
        [*] cfg80211 - wireless configuration API
        [*] Generic IEEE 802.11 Networking Stack (mac80211)
    Device Drivers  --->
      [*] Network device support  --->
        [*] Wireless LAN  --->
          [*] Intel devices
            <M> Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
              <M> Intel Wireless WiFi MVM Firmware support


FILE /etc/portage/make.conf
VIDEO_CARDS="i965 intel iris"
USE="$USE vulkan"

You'll also need firmware from sys-kernel/linux-firmware in order to use the GPU. It is not recommended to build the GPU firmware into the kernel.

Firmware: i915/icl_dmc_ver1_09.bin

See also: Intel


In kernels before 5.5, the Linux kernel may crash when loading the intel-lpss-pci module. When booting live media, pass the kernel parameter modprobe.blacklist=intel-lpss-pci. This will disable the touchscreen and pen input.

The patches to fix this are included in kernel versions after 5.5.0-rc1 and should be released into the stable 5.5.

If you're using sources from git, you can fetch the patches from the mfd tree, ib-mfd-doc-sparc-libdevres-5.5 branch


Need to enable CONFIG_I2C_HID_ACPI, CONFIG_HID_WACOM and CONFIG_PINCTRL_ICELAKE to get a Wacom Active ES 2.0 pen to work.

KERNEL Kernel 5.12 and later
Device Drivers  --->
  [*] Pin controllers  --->
    <M> Intel Ice Lake PCH pinctrl and GPIO driver
  HID support  --->
    Special HID drivers  --->
      <M> Wacom Intuos/Graphire tablet support (USB)
    I2C HID support  --->
      <M> HID over I2C transport layer ACPI driver

Before kernel 5.12, CONFIG_I2C_HID_ACPI was called CONFIG_I2C_HID.

KERNEL Kernel 5.11 and before
Device Drivers  --->
  [*] Pin controllers  --->
    <M> Intel Ice Lake PCH pinctrl and GPIO driver
  HID support  --->
    Special HID drivers  --->
      <M> Wacom Intuos/Graphire tablet support (USB)
    I2C HID support  --->
      <M> HID over I2C transport layer

If using Xorg, set INPUT_DEVICES="wacom" in make.conf. In wayland, the pen is handled by libinput.

Bluetooth Buttons

Some active pens support a bluetooth to the laptop to start up applications. Currently, the bluetooth stack only reports that the device has connected and disconnected, not the type of button press (single, double, and long presses). See xf86-input-wacom "Bluetooth Button" for more info.


import sys
import dbus
from dbus.mainloop.glib import DBusGMainLoop
from gi.repository import GLib

import subprocess

# ID of the device we care about
DEV_ID = sys.argv[1].replace(":", "_")

dbus_loop = DBusGMainLoop()
bus = dbus.SystemBus(mainloop=dbus_loop)

sender = "org.bluez"
adapterPath = '/org/bluez/hci0'
path = adapterPath + '/dev_' + DEV_ID
proxy = bus.get_object(sender, path)

def cb(*args, **kwargs):
    # 0: interface
    # 1: entry dict
    # 2: signature
    if args[0] != "org.bluez.Device1":

    g = args[1].get
    is_connected = g("Connected")
    if isinstance(is_connected, dbus.Boolean) and is_connected:
        # start your pen app, as a systemd user service so we only launch one'systemctl --user start mypaint.service'.split(' '))
    elif isinstance(is_connected, dbus.Boolean) and not is_connected:
        # Dim the backlight'xbacklight -set 5'.split(' '))

proxy.connect_to_signal("PropertiesChanged", cb)

    loop = GLib.MainLoop()
except KeyboardInterrupt:
CODE systemd/user/wacom-bluetooth-pen@.service
Description=Watch for Wacom Pen BlueTooth connections

ExecStart=/path/to/ %I

CODE systemd/user/mypaint.service
Description=MyPaint drawing software


(Almost) Flicker-free boot

sys-boot/plymouth supports "flicker-free" boot, but with a couple of noticeable flickers. Set the plymouth theme to bgrt. The i915.fastboot=1 parameter might not required.

root #emerge --ask plymouth
root #plymouth-set-default-theme bgrt

Intel GVT

iGVT-g is not supported by the i915 driver for Ice Lake. Other modes (iGVT-d, iGVT-s) have not been tested.

The developers (Intel) previously indicated that Ice Lake would be supported in the future, however no work enabling Ice Lake has been seen.

Experimental GuC/HuC

This was broken by this patch included in linux-5.14.

Since iGVT is disabled, it may be possible to get the performance/power-saving benefits of GuC/HuC since it would otherwise be incompatible with iGVT.

Set i915.enable_guc=-1 in your kernel command line to enable GuC/HuC firmware loading.

Firmware files: i915/icl_guc_33.0.0.bin, i915/icl_huc_ver9.0.0.bin

VA-API (Video Acceleration API)

Set USE="vaapi" in make.conf and run:

root #emerge --ask media-libs/libva-intel-media-driver

See bug #692244 if libva-intel-media-driver has compile errors.

Then set vaapi to use the intel-media-driver, instead of the regular intel-driver:

FILE /etc/env.d/11libva-media-driver

Applications like mpv, vlc and ffmpeg can then use hardware acceleration via vaapi. Check that the GPU is being used for video with x11-apps/igt-gpu-tools' intel_gpu_top. Firefox supports vaapi from version 78 on Wayland[1] and on X11 since release 80[2].

See Wikipedia article for more information.

Disable keyboard in tablet/tent/stand mode

Device Drivers  --->
      HID support  --->
        Intel ISH HID support  --->
          <M> Intel Integrated Sensor Hub
  <M> Industrial I/O support  --->
    Accelerometers  --->
      <M> HID Accelerometers 3D

Other sensors are available (e.g. Ambient Light Sensor, Gyroscope, Inclination and Rotation) in the system, they are not required to disable the keyboard in tablet mode.

Automatic rotation

You can use rot8 or iio-sensor-proxy to automatically rotate your screen. Note, these apps will rotate your screen even in laptop mode, when you may not want it to.

Finger and Pen rotates with screen

Rotating the screen won't automatically rotate the touch and pen input.

Add this to your sway config to fix touch (the pen/"tablet_tool" has issues when rotated, see below):

FILE ~/.config/sway/config
input type:touch map_to_output eDP-1
# input type:tablet_tool map_to_output eDP-1 # has issues, see below

Issue: Wacom Pen jitter

If the screen has been rotated 90 degrees, you cannot draw straight vertical or horizontal lines with a pen. There isn't a workaround yet.

Sway issue:

Secure Boot

app-crypt/efitools' efi-updatevar can update the 4 secure boot variables when in setup mode. When in user mode, I copied the public databases onto the ESP and loaded them through the UEFI Setup GUI. Tip: systemctl reboot --firmware-setup reboots directly to setup without having to press the Setup key on boot (F2).

Signed UEFI executable by dracut

Once your Secure Boot keys are in /etc/efikeys, pop the following into a dracut configuration file:

FILE /etc/dracut.conf.d/uefi-secureboot.conf

Then when updating your kernel, run (replace where necessary):

root #make modules_install
root #dracut --uefi --kernel-image arch/x86/boot/bzImage --kernel-cmdline "$cmdline" -f /path/to/output.efi $kernel_version


OpenSSL engine

Emerge app-crypt/tpm2-tss-engine to use the TPM as an OpenSSL engine. To use the tpm resource manager as an unprivileged user, add the user to the tss group.

user $openssl engine -t -c tpm2tss
user $tpm2tss-genkey myTpmKey.keyfile
user $openssl req -engine tpm2tss -keyform engine -new -x509 -nodes -sha256 -days 365 -key myTpmKey.keyfile -out self-signed-cert.crt

Optional configuration

The engine should not require further configuration, but if you need to you can add the following configuration to /etc/ssl/openssl.cnf and modify to taste.

FILE /etc/ssl/openssl.cnf
openssl_conf = openssl_init

engines = engine_section

tpm2tss = tpm2tss_section

engine_id = tpm2tss
dynamic_path = /usr/lib64/engines-1.1/

TOTP measured boot

root #emerge --ask app-crypt/tpm2-totp

Add the tpm2-totp module to dracut's config files:

FILE /etc/dracut.conf.d/tpm2-totp.conf
add_dracutmodules+=" tpm2-totp "

By default tpm2-totp uses PCR banks 0, 2, 4 and 6. PCR4 contains a hash of the kernel binary you are running, which will change on every kernel update. If you update often, this will cause the TOTP to break each time. Check your PCR banks with app-crypt/tpm2-tools' tpm2_pcrlist. Adjust which PCR banks are used with the tpm2-totp generate -p flag.

PCR bank (Suspected) Use
0 UEFI code
1 UEFI configuration
2 Option ROMs
3 Option ROM configuration
4 Initial program loader code
5 Initial program loader code configuration
6 State transitions and wake events (Dell Configuration Information 1/2)
7 Platform manufacturer specific measurements (combined hash of the PK+KEK+db(+dbx) databases)
8 kernel command line
9 None (zeros)
10 Unknown use (in concert with IMA)


By default, closing the lid will activate S2 sleep (s2idle), which uses a lot of battery while asleep (~20% overnight).

You can try S3/deep sleep by writing deep into /sys/power/mem_sleep and try suspending again, however there may be issues with the internal display or the touchscreen failing to work on resume. Try disabling BIOS Setup -> POST Behaviour -> "Sign of Life" -> "Early Dell Logo Display".

Discover which sleep modes are available to the system:

FILE /sys/power/disk
[platform] shutdown reboot suspend test_resume
FILE /sys/power/mem_sleep
[s2idle] deep
FILE /sys/power/state
freeze mem disk

Check the defaults in /etc/systemd/sleep.conf.

For instance, it's really easy to press the power button when holding in tablet mode, so I selected 's2idle'/'freeze' for the power key (I repurposed hybrid sleep for it). I then use S3 suspend-to-RAM (deep sleep) on lid close, after which a short timeout to suspend-to-disk (S4), to do a full resume through the bootloader:

FILE /etc/systemd/sleep.conf

FILE /etc/systemd/logind.conf
FILE /etc/kernel/cmdline
... mem_sleep_default=deep

Note, when the power button is pressed and the system goes into s2idle, it still responds to the lid closing and going into suspend.

Read more about kernel sleep states

LUKS/resume timeout

If you use hibernation with encrypted swap (with dracut/systemd, but maybe other systems too), the systemd-hibernate-resume service will time out after 90 seconds, and entering your password after that will cause hibernation data loss. Upcoming systemd versions will contain a patch that increases the timeout to infinity, but it'd rather turn the laptop off to save battery power.

Add this to your kernel command line to power off the laptop at the 90 second mark:

FILE /etc/kernel/cmdline
rd.emergency=poweroff rd.timeout=90

See also: Bug report & systemd-hibernate-resume pull request

USB-C PD charging

Plugging in a USB-C PD battery may not do the right thing (i.e. the laptop charges the battery) without the Type-C UCSI driver.

Device Drivers  --->
  [*] USB support  --->
    <M> USB Type-C Support  --->
      <M> USB Type-C Connector System Software Interface driver
        <M> UCSI ACPI Interface Driver

The driver exposes /sys/class/typec which configures the ports to pull power, and it can be further configured as a power source or sink.

Dell SMBios tools

Device Drivers  --->
  [*] X86 Platform Specific Device Drivers  --->
    <M> Dell Systems Management Base Driver
    <M>   Dell SMBIOS driver
    <M>    Dell SMBIOS driver WMI backend
    <M>    Dell Laptop Extras
root #emerge libsmbios[python]

Fan Thermal Profile

root #smbios-thermal-ctl -i
Libsmbios version : 2.4.2
smbios-thermal-ctl version : 2.4.2

 Print all the Available Thermal Information of your system:

Supported Thermal Modes:
	 Cool Bottom

Supported Active Acoustic Controller (AAC) modes:

Supported AAC Configuration type:
	Global (AAC enable/disable applies to all supported USTT modes)
root #smbios-thermal-ctl -g
Helper function to Get current Thermal Mode settings

 Print Current Status of Thermal Information:

Current Thermal Modes:

Current Active Acoustic Controller (AAC) Mode:
	 AAC mode Disabled

Current Active Acoustic Controller (AAC) Mode:
	Global (AAC enable/disable applies to all supported USTT modes)

Current Fan Failure Mode:

It's pretty self-explanatory except that the 'Cool Bottom' (with a space) mode should be passed as 'cool-bottom' (with a dash):

root #smbios-thermal-ctl --set-thermal-mode=cool-bottom
Helper function to Set Thermal Mode
Thermal Information Set successfully to: cool-bottom

Filtered calls

You may get some errors while running the smbios tools:

root #smbios-token-ctl
ERROR: Could not execute SMI.

Common problems are:

    -- 'SMM Mitigations' is enabled in BIOS setup.
        Run kernel 4.15 or later with
        dell-smbios-wmi enabled.
        Disable 'SMM mitigations' in BIOS setup.

    -- Insufficient permissions to perform operation.
       Try running as a more privileged account.
          Linux  : run as 'root' user
          Windows: run as 'administrator' user

    -- dell-smbios-wmi driver not loaded
       Try loading the dell-smbios-wmi driver
          Linux : modprobe dell-smbios-wmi

    -- Call filtered by Linux kernel
       Some functionality is natively supported
       by the Linux kernel

    -- dcdbas device driver not loaded.
       Try loading the dcdbas driver
          Linux  : modprobe dcdbas

Check dmesg for 'Invalid call'. These calls are filtered by the dell-smbios driver. For some tools, like smbios-token-ctl, the filtered calls can be blacklisted so that the tool can continue running (skipping those filtered calls).


Due to vulnerability fixes in newer CPU microcodes, undervolting capabilities may have been removed.

All but the 'System Agent' can be undervolted. I experienced GPU glitches below -40mV, and the Tjunction offset goes down to -40°C (100°C-40°C=60°C).

root #emerge --ask sys-power/intel-undervolt
FILE /etc/intel-undervolt.conf
undervolt 0 'CPU' -80
undervolt 1 'GPU' -40
undervolt 2 'CPU Cache' -80
undervolt 3 'System Agent' 0
undervolt 4 'Analog I/O' -80
power package 15/0.002:disabled 10/600
tjoffset -40
hwphint force load:multi:4.0 power balance_power

The intel-undervolt.service will re-apply itself after suspend and hibernation, but not on suspend-then-hibernate. Add this to your service override:

FILE /etc/systemd/system/intel-undervolt.service.d/override.conf


BIOS Recovery 3

For more information, see Dell's How to Recover the BIOS page.


To configure BIOS Recovery 3 with Auto-Recovery, download the System BIOS file from the Dell support website. Once downloaded, check the integrity with the provided checksums; the .exe files are the exact same as the .rcv files.

user $md5sum XPS_13_7390_2-in-1_*.{exe,rcv}
user $sha1sum XPS_13_7390_2-in-1_*.{exe,rcv}
user $sha256sum XPS_13_7390_2-in-1_*.{exe,rcv}

Once verified, copy the file to the root of your EFI System Partition (ESP), renaming it "BIOS_IMG.rcv" (FAT32 is case-insensitive, although the documentation insists on this case).

root #cp XPS_13_7390_2-in-1_*.exe /efi/BIOS_IMG.rcv || cp XPS_13_7390_2-in-1_*.rcv /efi/BIOS_IMG.rcv

Force a recovery

To verify the correct setup, shut down the laptop and unplug any power supply cables. Once off, press and hold the Ctrl and Esc keys and plug in the vendor provided power supply (60W). The laptop should turn on automatically.

If the recovery preparations have been completed correctly, you'll be shown the recovery prompt screen. It is possible to exit and reboot if there is no need to recover the BIOS.

If the recovery file has not been found, the battery status bar should provide a diagnostic code, as listed in the XPS 13 7390 2-in-1 Service Manual - System diagnostic lights.

See also