Dell Latitude 3500

From ArchWiki
Jump to navigation Jump to search
Hardware PCI/USB ID Status
Touchpad Working
Keyboard Working
Video 8086:3ea0 Working
Webcam 1bcf:2b98 Working
Ethernet 10ec:8168 Working
Bluetooth 8087:0aaa Working
Power management Working
USB Ports 8086:9ded Working
SD-Card slot 8086:9dc4 Working
HDMI Working
VGA Working
Audio 8086:9dc8 Working
Wireless 8086:9df0 Working
Fingerprint reader 27c6:530c Not working
TPM Untested


RAID mode is enabled by default. AHCI mode must be used, otherwise the disks will be invisible[1]. Using RAID mode will trigger a relevant log message in the journal.


fwupd does not support this device yet.


The BIOS accepts .auth files.

Note: This device does not have a BIOS speaker and uses the built-in speakers instead. Beeps can be louder than expected.

Firmware data path

The BIOS stores logs and recovery images in esp/EFI/dell. Recovery images are stored in esp/EFI/dell/bios/recovery and are 14 MB in size. It appears that there will only be two images at the same time, BIOS_CUR.rcv and BIOS_PRE.rcv. Those files will be created when the BIOS was updated.


esp/EFI/dell/logs contains XML files which contain diagnostics data (SupportAssist). It appears that there will only be two logs at the same time, diags_previous.xml and diags_current.xml. Those files will be created when an error happened.

Example log (diags_previous.xml):

<?xml version="1.0" encoding="UTF-8"?>
    <LogTimeStamp>02/05/2020 00:06:43</LogTimeStamp>
      <Result>Not Reported</Result>
      <ErrorMessage><![CDATA[Time-of-day not set - please run SETUP program.

Another example log (diags_current.xml):

<?xml version="1.0" encoding="UTF-8"?>
    <LogTimeStamp>04/17/2020 09:41:58</LogTimeStamp>
      <DevicesTested>Memory, Hard Drive</DevicesTested>
      <ErrorMessage><![CDATA[No bootable devices found.

Fingerprint reader

The fingerprint reader requires a proprietary driver and has to be obtained from one of Dells Ubuntu images first[2]. If you do not have an Ubuntu image for your device, you could try to obtain a vendor image for a device that contains the same fingerprint reader[3]


Bluetooth works out of the box. Append --plugin=* to bluetoothd's arguments to fix some problems with headset buttons.

ExecStart=/usr/lib/bluetooth/bluetoothd --plugin=*

After suspending, especially when using #Unmarked keybinds, Bluetooth may stop working. Restart Bluetooth to fix it.

# systemctl restart bluetooth

Power management

After waking up the device from suspend, input lag will occur for approximately 5-10 seconds. Sometimes it will even repeat a key press for up to 32 times but only within this timespan. There is no known fix for this.

Function keys

Key Visible? Marked? Effect
Fn+Esc No Yes Enables Fn lock
Fn+F1 Yes Yes XF86AudioMute
Fn+F2 Yes Yes XF86AudioLowerVolume
Fn+F3 Yes Yes XF86AudioRaiseVolume
Fn+F4 Yes Yes XF86AudioPrev
Fn+F5 Yes Yes XF86AudioPlay
Fn+F6 Yes Yes XF86AudioNext
Fn+F7 No No See #Unmarked keybinds
Fn+F8 No Yes Seems to disable the display if another monitor is connected. Inputs p when pressed
Fn+F9 Yes Yes XF86Search
Fn+F10 No Yes Enables/disables keyboard backlight
Fn+F11 Yes Yes XF86MonBrightnessDown
Fn+F12 Yes Yes XF86MonBrightnessUp
Fn+Print Yes Yes XF86RFKill, will hard-block wifi and soft-block Bluetooth. Press again to disable
Fn+Ins No No See #Unmarked keybinds

Unmarked keybinds

There are several keybinds handled by the BIOS

Key Effect
Fn+F7 Unobtrusive mode. Has to be enabled in the BIOS in order to work. Deactivates all LEDs and turns off display. Press again to disable. It may also disable sound, but this is untested.
Fn+Ins Suspends device. systemd-logind will log Suspend key pressed.. Can not be disabled/configured
Fn+NumPad0 Same as Fn+Ins[4]. May be an unintended feature

See also