# Dell Latitude on Omarchy Linux
Dell Latitude on Omarchy 4.x: Intel graphics and iwlwifi work, ControlVault fingerprint readers go undetected, and turning Bluetooth off can drop the radio.
> **Short answer:** Most Latitudes run Omarchy fine on the generic Intel path. Rate it silver. Intel graphics and the iwlwifi driver work, though a 3.x upgrade can leave NetworkManager pointed at iwd; the fingerprint reader does not if your Latitude has a Broadcom ControlVault 3, because Omarchy never looks for vendor 0a5c. Turning Bluetooth off can remove the radio from the bus. Omarchy ships no Latitude-specific enablement at all.
- Applies to Omarchy: 3.x and later
- Status: partial
- Last verified: 2026-09-16
- Canonical: https://omarchylinux.org/hardware/dell-latitude/
_Unofficial community page. Not affiliated with 37signals or the Omacom Foundation. Omarchy is a registered trademark of 37signals LLC._

## Verdict

Silver. A Dell Latitude installs and runs Omarchy on the generic Intel laptop path, and the tracker shows machines from a 2016 E5470 up to a 7450 doing exactly that. Nothing in the Omarchy tree is written for this line, so what you get is whatever the kernel and the generic Intel enablement give you. That is usually enough.

Two things pull it off gold. Fingerprint readers on ControlVault models are not detected at all, and turning Bluetooth off through the shell can take the radio off the bus entirely. Both are open on 4.0.4.

Evidence here is broader than it is deep. Twenty-two tracker issues name a Latitude, from a 2.1 install failure to 4.0.x bugs, but most are generic Omarchy bugs that happened to be filed from one. The Latitude-specific findings below are the ones where the reporter's hardware is actually the cause.

## What works

Intel graphics. Latitudes running 4.0.0 with an internal panel plus an external HDMI display show up in bug reports doing ordinary Hyprland work, including the E5470 with HD 530 in [#7326](https://github.com/omacom/omarchy/issues/7326). An older performance complaint about Iris Xe on a 7420 ([#1610](https://github.com/omacom/omarchy/issues/1610)) was closed the same day and never established a defect.

Intel Wi-Fi. The kernel side is clean. The E5470 report in [#7323](https://github.com/omacom/omarchy/issues/7323) includes the `iwlwifi` boot log for a Dual Band Wireless-AC 8260, and the driver side of it is unremarkable: the firmware loads, the adapter enumerates, nothing is rfkill-blocked and the driver logs no errors. When Wi-Fi breaks on a Latitude it has so far been NetworkManager configuration, not the radio.

Installation. The reports come from installed, updated systems, which is itself evidence that the installer handles these machines.

Everything else on the checklist is unknown rather than confirmed. No one has filed a Latitude audio, webcam, battery, hibernate or keyboard bug, and an empty tracker is not a test result. Treat audio and webcam as untested here, not as working.

## What breaks

**Fingerprint on ControlVault models.** This is the clearest Latitude problem. `omarchy-hw-fingerprint` matches a USB product string or a vendor allowlist. In 4.0.4 that list is `27c6 138a 06cb 08ff 1c7a 147e`. A Dell ControlVault 3 is Broadcom `0a5c:5843` and reports its product string as just `58200`, so it matches neither test and `Setup > Security > Fingerprint` bails out before it installs anything. Reported independently by bartcho in [#7662](https://github.com/omacom/omarchy/issues/7662) and by JeronimoColon on a Latitude 5420 in [#9507](https://github.com/omacom/omarchy/issues/9507). Two competing pull requests are open and unmerged, [#9524](https://github.com/omacom/omarchy/pull/9524) (match the exact USB ID) and [#8486](https://github.com/omacom/omarchy/pull/8486) (allowlist the vendor).

There is a second trap behind it. Since 4.0.3 the setup script installs `libfprint-git`, which conflicts with `libfprint`, and it passes `--ask 4` so pacman accepts the conflict without prompting. ControlVault readers need `libfprint-tod` plus Dell's `libfprint-2-tod1-broadcom` driver, which also provides `libfprint`. JeronimoColon's follow-up notes that fixing detection alone would let the wizard swap the working TOD stack for an upstream build with no driver for the reader. Do not run the fingerprint wizard on a ControlVault machine even after detection is fixed, unless you have checked what it will do to your packages.

**Bluetooth off removes the radio.** `omarchy-bluetooth-power off` issues a type-wide `rfkill block bluetooth`. On a Dell that block also lands on the `dell-laptop` platform switch, and firmware responds by pulling power from the USB-attached module, so the kernel loses `hci0` outright instead of holding it in a soft block. DrakeMorrison traced the mechanism in [#7936](https://github.com/omacom/omarchy/issues/7936) on ThinkPads; the Dell evidence is oren's Latitude 7440 (AX211, Omarchy 4.0.0) on [#6956](https://github.com/omacom/omarchy/issues/6956), which describes hardware where even `rfkill unblock bluetooth` does not bring the radio back, and only a suspend and resume cycle or a reboot does. The bar widget vanishes with the adapter, so there is no UI route back. Open on 4.0.4.

**Wi-Fi dead after upgrading to Quattro.** On skoom21's E5470, the 4.0.0 upgrade removed the `iwd` package but left `/etc/NetworkManager/conf.d/wifi_backend.conf` still selecting `wifi.backend=iwd`. NetworkManager keeps asking for a daemon that is no longer installed, so `nmcli` shows the card stuck at `unavailable` and the shell gives no hint why. The one migration aimed at iwd-era breakage, `migrations/1786567036.sh`, only acts when `wpa_supplicant.service` is masked; on this machine it was merely disabled, so the migration did nothing. Check that file before you blame the card.

**Monitor layout does not stick.** Also from the E5470: give the internal panel a fixed position and both the clamshell watcher and the Display panel's scaling path overwrite it with `position = "auto"` within about a second ([#7326](https://github.com/omacom/omarchy/issues/7326)). This is not Latitude-specific, it affects any laptop with an external monitor, but it is what a docked Latitude owner hits first.

**Live ISO freeze on i915.** One report, [#2947](https://github.com/omacom/omarchy/issues/2947), from a Latitude E7490 with an i7-8650U: the live ISO freezes in early boot, which the reporter attributes to i915 power saving. It is open, has no comments, and no one has reproduced it. Thin evidence, but worth knowing if your install stalls at the same point.

## What Omarchy does for this model

Nothing specific. As of 4.0.4 no shipped script calls `omarchy-hw-match` with a Latitude or a Dell-family pattern. The only Dell matches in the tree are `XPS` (OLED handling and haptic touchpad) and the `DX13260` product name behind the 2026 XPS 13 text-scaling tweak; the XPS 14 and 16 speaker tuning keys on DMI SKUs `0DB9` and `0DBA`. There is no `install/hardware/dell/` directory at all. The Dell-specific files are `install/hardware/dell-xps-touchpad-haptics.sh` and `install/user/hardware/dell/xps13-text-scaling.sh`, and there is no Latitude speaker tuning.

What a Latitude actually gets is the generic run in `install/hardware/all.sh`: Intel video acceleration, `lpmd`, `thermald`, SOF firmware, the wireless regdom, the F-key fix, the Synaptics touchpad fix and the Bluetooth setup. `omarchy-hw-laptop` picks the machine up from its ACPI lid switch, and `omarchy-hw-intel` from the CPU vendor string. That is the whole of it.

## Variants

Most of the 4.x reports come from 5000 and 7000 series units from 2021 onward: the 5420, 5430, 5431, 5521, 7420, 7430, 7440 and 7450. All of them are Intel-graphics machines that were running Omarchy when the report was filed, which is the strongest "it boots and works" evidence this page has. Only the 7440 report names its wireless card (Intel AX211).

Check the fingerprint reader before you count on it. Run `lsusb` on the machine and look for `0a5c`. If it is a Broadcom ControlVault, the Omarchy wizard will not see it on 4.0.4. Latitudes with a Goodix (`27c6`) or Validity/Synaptics (`138a`, `06cb`) reader are inside the allowlist, though no Latitude report confirms enrollment on one.

Older E-series units (E5470, E7490) are usable, and the E5470 is the best-documented Latitude in the tracker, but the E7490 is also the machine behind the unreproduced ISO freeze. A 1366x768 panel also fights Omarchy's default assumption of a 2x, retina-class display; set `omarchy_monitor_scale` and `omarchy_gdk_scale` to 1 in `monitors.lua` as the [Monitors chapter](https://omarchy.org/manual/monitors/) describes.

No Latitude with an AMD processor appears in the data. The only AMD part on record is the Radeon Topaz XT discrete chip in the E5470, and that report says nothing about whether it is used. Both configurations are untested here.

## Before you install

- Run `lsusb | grep -i 0a5c` from the live ISO. A hit means the fingerprint reader will not be detected.
- Check `/etc/NetworkManager/conf.d/` after any 3.x to 4.x upgrade and remove a `wifi_backend.conf` that still names iwd.
- Leave Bluetooth on rather than toggling it off from the bar, until [#7936](https://github.com/omacom/omarchy/issues/7936) lands.
- Have a wired connection or a phone tether available for the first boot after upgrading.
- If the live ISO freezes early, that is [#2947](https://github.com/omacom/omarchy/issues/2947) and not your disk.

## Related

- [Fingerprint enrollment fails](/fix/fingerprint-enrollment-fails/)
- [Bluetooth stops after resume](/fix/bluetooth-stops-after-resume/)
- [Multi-monitor layout not saved](/fix/multi-monitor-layout-not-saved/)
- [Fingerprint readers](/hardware/fingerprint/) and [Bluetooth](/hardware/bluetooth/)
- [Upgrading 3 to 4 (Quattro)](/upgrade/3-to-4-quattro/)
- [Submit your hardware report](/hardware/submit/)

## Sources

- [Issue #9507: omarchy-hw-fingerprint doesn't detect Dell ControlVault 3 (Broadcom BCM58200, vendor 0a5c)](https://github.com/omacom/omarchy/issues/9507)
- [Issue #7662: Fingerprint setup misses Broadcom BCM58200 ControlVault 3 (vendor 0a5c not in detection list)](https://github.com/omacom/omarchy/issues/7662)
- [PR #9524: Detect Broadcom ControlVault 3 fingerprint readers](https://github.com/omacom/omarchy/pull/9524)
- [PR #8486: Detect Broadcom fingerprint readers by vendor ID](https://github.com/omacom/omarchy/pull/8486)
- [Issue #7323: Quattro upgrade removes iwd but leaves wifi.backend=iwd in NetworkManager conf.d](https://github.com/omacom/omarchy/issues/7323)
- [Issue #7326: Internal monitor position cannot be made to stick](https://github.com/omacom/omarchy/issues/7326)
- [Issue #7936: omarchy-bluetooth-power off: type-wide rfkill block trips platform switches and removes the radio from the USB bus (ThinkPad/Dell)](https://github.com/omacom/omarchy/issues/7936)
- [Issue #6956: Bluetooth widget disappears from shell when turned off](https://github.com/omacom/omarchy/issues/6956)
- [Issue #2947: Live ISO freezes on systems with Intel i915 GPU](https://github.com/omacom/omarchy/issues/2947)
- [Issue #3644: Omarchy can't connect to different wifi networks](https://github.com/omacom/omarchy/issues/3644)
- [Issue #2619: Omarchy takes long time during boot except hammering keyboard randomly](https://github.com/omacom/omarchy/issues/2619)
- [Issue #1610: Intel Iris Xe on Arch feels laggy](https://github.com/omacom/omarchy/issues/1610)
- [Omarchy Manual: Hardware authentication](https://omarchy.org/manual/hardware-authentication/)