Dell XPS 17 (9710)
| Hardware | PCI/USB ID | Working? |
|---|---|---|
| Bluetooth | Yes | |
| Webcam | Yes | |
| Wi-Fi | 8086:43f0 | Yes |
| GPU (Intel) | 8086:9a60 | Yes |
| GPU (NVIDIA) | 10de:2520 | Yes |
| Touchpad | Partial | |
| Keyboard | Yes | |
| Fingerprint reader | Yes | |
| SD-card reader | Yes | |
| Speakers | Yes | |
| Microphone | Yes | |
| Infrared camera | Partial | |
| Ambient light sensor | Untested | |
| Fan-control | Partial |
Installation
Before installing it is necessary to modify some UEFI Settings. They can be accessed by pressing the F12 key repeatedly when booting.
- Change the SATA Mode from the default "RAID" to "AHCI". This will allow Linux to detect the NVMe SSD.
- Disable Secure Boot to allow Linux to boot. This may be re-enabled at a later point. See Secure Boot#Using a signed boot loader
Dual boot
Please note that changing from "RAID" to "AHCI" can break the default Windows installation and require a complete reinstall. Usually running windows own startup repair utility however fixes this issue in most cases. Another alternative is to follow this guide.
The reinstall can be done through the Dell recovery in the BIOS if needed.
Once you used the startup repair utility or have reinstalled, Windows should boot normally in AHCI mode and without error. Then one can proceed with typical dual boot setup.
Accessibility
The appearance of the BIOS is simple, being mostly made up of a plain white background and clear, black text. It might work with OCR software. The graphical BIOS setup program can be navigated with the keyboard (see Entering BIOS setup program).
GPU
The GPU does not work properly with bbswitch, make sure to uninstall it and install only primus and bumblebee to start GPU driven applications with optirun or primusrun.
Firmware
fwupd supports this device.
Thunderbolt
The following thunderbolt devices have been tested:
| Device | Working? | Comments |
|---|---|---|
| Dell WD19TBS 180W | Yes | – |
Touchpad
Some users find the touchpad are sluggish or sticky occasionally. There is a tracking bug https://gitlab.freedesktop.org/libinput/libinput/-/issues/618 but it is not root-caused yet.
Wireless
The wireless card seems to be rather weak compared to other laptops, users noticed that using the laptop while the lid is closed impacts the Wi-Fi signal (5GHz) negatively by about 36%.
Fan control
The dell-smm-hwmon currently does not work, since it does not have any access to the fans and cannot read or write to them. The bios has to regulate and take care. However fans are very silent usually.
BIOS Thermal Modes / Fan profiles
Currently the only choice are the BIOS controlled fans, which means you have to control the bios thermal parameters. This is done within a terminal with the libsmbios package, or alternatively via plasma5-applets-plasma-pstateAUR[broken link: package not found]:
To find out what thermal mode is set type:
# smbios-thermal-ctl -g
To find all available thermal modes type:
# smbios-thermal-ctl -i
And finally to set the desired thermal mode that you identified with the command before type:
# smbios-thermal-ctl --set-thermal-mode=THERMAL_MODE
- "Quiet" and "Cool Bottom" profiles limit CPU power and thus reduces overall system performance.
- "Balanced" and "Performance" profiles remove this limit.
Performance throttling
There is a problem with performance throttling currently. Which can be fixed by executing the following:
# rmmod intel_rapl_msr # rmmod processor_thermal_device_pci_legacy # rmmod processor_thermal_device # rmmod processor_thermal_rapl # rmmod intel_rapl_common # rmmod intel_powerclamp # modprobe intel_powerclamp # modprobe intel_rapl_common # modprobe processor_thermal_rapl # modprobe processor_thermal_device # modprobe intel_rapl_msr
The underlying issue is yet unknown and has to be tracked down.
Hardware acceleration
The dell ships with Gen12 Intel CPUs. Those only work with intel-media-driver. Firefox tabs will crash currently, which is related to the following bug.
There is no real fix but to disable the sandbox, which can be done via about:config by setting security.sandbox.content.level to 0. This however is an impact security wise, so the recommendation is to wait for the bug to be fixed and disable the hardware acceleration instead.