# Microsoft Surface on Omarchy Linux
Microsoft Surface Laptop and Surface Pro on Omarchy 4.0.4: the keyboard works after boot but often dies at the LUKS prompt, and touch needs linux-surface.
> **Short answer:** Rate the Surface family bronze. Omarchy does detect Surface hardware and installs Marvell firmware plus an initramfs keyboard module list, but that list is only written when a pinctrl module is found, so AMD Surfaces get nothing and the built-in keyboard is dead at the LUKS prompt. Touch and stylus on most IPTS models still need the third-party linux-surface kernel. Prefer an Intel Surface Laptop 3.
- Applies to Omarchy: 3.x and later
- Status: partial
- Last verified: 2026-09-16
- Canonical: https://omarchylinux.org/hardware/microsoft-surface/
_Unofficial community page. Not affiliated with 37signals or the Omacom Foundation. Omarchy is a registered trademark of 37signals LLC._

## Verdict

Bronze. A Microsoft Surface will run Omarchy, and the desktop session is mostly ordinary once you are logged in, but you should expect to do real work before and after the install. Omarchy carries exactly three Surface-specific files: a detection helper, a one-line firmware installer and a keyboard module drop-in writer. Nothing in the tree is about touch, pen or the multi-battery machines.

The two problems that define this family are pre-boot input and touch. The built-in keyboard often does not exist yet at the LUKS passphrase prompt, because the Surface Aggregator modules are not in the initramfs. And on the IPTS-era models the touchscreen and stylus can need a kernel Omarchy does not ship.

Checked against Omarchy 4.0.4 source, with the v3.8.4 tree compared for what changed. `Surface Laptop 3` is the only product name the keyboard script treats as tested, and the one Surface Laptop 3 keyboard recipe in the tracker uses the Intel `pinctrl_icelake` module, so an Intel Laptop 3 is the best documented case here.

## What works

Wi-Fi is fine on the reported machines. Omarchy has installed `linux-firmware-marvell` on any detected Surface since [v3.4.0](https://github.com/omacom/omarchy/releases/tag/v3.4.0), whose notes list "Surface laptops should have driver kit installed by default", and the debug dump in [issue #11128](https://github.com/omacom/omarchy/issues/11128) shows a Qualcomm Atheros QCA6174 bound to `ath10k_pci` on a Surface Laptop 3 running 4.0.3. No Surface Wi-Fi failure has been filed.

The internal display works, including high-resolution panels. [Issue #9537](https://github.com/omacom/omarchy/issues/9537) shows a Surface Pro 10 driving a 2880x1920 panel, though that reporter was running the third-party linux-surface kernel rather than Omarchy's own. The Surface Laptop Studio 2 in [issue #12136](https://github.com/omacom/omarchy/issues/12136) was on stock `linux-omarchy` with a working desktop.

The built-in keyboard works normally inside the Hyprland session. The reporter in [issue #729](https://github.com/omacom/omarchy/issues/729) traced it stage by stage: the Surface keyboard selects entries in the boot menu and works after login, and only the encryption prompt is dead. The touchpad is the same story, with one exception: the Surface Laptop Studio 2, covered below, is the only model anyone has reported a dead pointer on inside the desktop.

There is no Surface-specific audio, Bluetooth or suspend issue in the data set. That is weak evidence, not good evidence. It means nobody filed one, not that somebody verified it. Those subsystems are marked unknown here on purpose.

## What breaks

**Keyboard and touchpad dead at the LUKS prompt.** This is the headline bug. On AMD Surface models, `install/hardware/fix-surface-keyboard.sh` never writes its module drop-in, so the initramfs has no `surface_aggregator` chain and you must plug in a USB keyboard to unlock the disk. Greg Baker filed [issue #11128](https://github.com/omacom/omarchy/issues/11128) on 2026-09-10 with the full chain and a confirmed workaround. The script looks for a `pinctrl_` module in `lsmod`, which exists on Intel Surfaces and not on AMD ones, and on failure it simply does nothing.

This is a regression between 3.x and 4.x, and it is not stated in the issue. In v3.8.4 the script lived at `install/config/hardware/fix-surface-keyboard.sh` and its `MODULES=(...)` line sat outside the pinctrl branch, so it was written either way, with an empty first entry when autodetect failed. In v4.0.0 the write moved inside the `else`, and v4.0.4 is byte-identical to v4.0.0 there, so a failed pinctrl autodetect now means no drop-in at all. The keyboard fix itself first shipped in [v3.1.4](https://github.com/omacom/omarchy/releases/tag/v3.1.4), credited there as "Fix Surface keyboard compatibility with decryption screen".

The problem predates the regression. [Issue #729](https://github.com/omacom/omarchy/issues/729) covers a Surface Laptop Studio with no keyboard at the Plymouth screen, back on Omarchy 1.13.0 before the script existed. [Issue #2092](https://github.com/omacom/omarchy/issues/2092) is filed as a Surface Laptop 4 that could not type a password at all on 3.0.2 and was closed after switching keyboards, but read it with care: the title says Surface Laptop 4 while the system details line reports a desktop Ryzen 5 5600X, so it may not be Surface hardware at all. See [/fix/luks-passphrase-not-accepted-at-boot/](/fix/luks-passphrase-not-accepted-at-boot/) for the general shape of that failure.

**Touchscreen and pen can be dead on the stock kernel.** Surfaces from the Pro 4 era onwards use Intel Precise Touch and Stylus. Alex Jessup found no `ipts` module and no touch input node on a Surface Book 2 in [issue #9484](https://github.com/omacom/omarchy/issues/9484), and got touch working by installing the third-party `linux-surface` kernel, `iptsd` and `surface-ipts-firmware`. [PR #7857](https://github.com/omacom/omarchy/pull/7857) would add that as an opt-in install step, tested by its author on a Surface Pro 7, keeping the stock kernel as the default boot entry and skipping when Secure Boot is on. It is still open as of 2026-09-16.

That PR scopes the touch problem to the Surface Pro 4 and newer, the Laptop Studio and the Go 3 and 4, and says touch already works with mainline on the Surface Laptop 1 to 5, Go 1 and 2, and Surface 3. Treat the boundary as untested rather than settled: the Surface Laptop Studio 2 in [issue #12136](https://github.com/omacom/omarchy/issues/12136) had a working touchscreen and stylus on stock `linux-omarchy`, which the PR's list would not predict.

**Surface Laptop Studio 2 touchpad does not work at all.** In [issue #12136](https://github.com/omacom/omarchy/issues/12136), the haptic touchpad produces no pointer events on 4.0.4 with `linux-omarchy 7.2.5-3`. The reporter's working setup was the linux-surface kernel plus `iptsd` and an ITHC DKMS driver for the `8086:51d1` controller.

**NVIDIA early KMS gets stripped.** On a Surface Book 2 or Laptop Studio, the Surface drop-in sorts after `nvidia.conf` and resets `MODULES` instead of appending, so the NVIDIA modules are dropped from initramfs images generated afterwards. That is [issue #7111](https://github.com/omacom/omarchy/issues/7111), filed by an automated QA pass and proven in source rather than reproduced. It only bites when the drop-in was actually written, which means an Intel Surface where the pinctrl autodetect succeeded. The Omarchy tree already documents the hazard in its own `mkinitcpio.conf.d/omarchy_hooks.conf`, which keeps the `kms` hook alive for the Intel iGPU but does not put the NVIDIA modules back. See [/hardware/nvidia/](/hardware/nvidia/).

**Battery percentage is wrong on Surface Book.** `omarchy-battery-status` picks the first `BAT*` device, which on a Surface Book is the small tablet pack, so the panel can read 0% while the bar icon reads the truth. Filed twice, in [issue #8504](https://github.com/omacom/omarchy/issues/8504) and [issue #11990](https://github.com/omacom/omarchy/issues/11990). More at [/hardware/battery-power/](/hardware/battery-power/).

**The webcam may work everywhere except your browser.** On a Surface Pro running 4.0.1, `qcam` and WirePlumber saw the camera but Chromium-based browsers never did, with the GTK portal logging an unhandled parent window type. That is [issue #8843](https://github.com/omacom/omarchy/issues/8843). Nothing in that report is Surface-specific: the camera hardware itself works, and the fault sits in the desktop portal stack. See [/hardware/webcam/](/hardware/webcam/).

**Internal panel defaults to 60 Hz.** Omarchy's shipped `config/hypr/monitors.lua` sets one wildcard rule with `mode = "preferred"`. On a Surface Pro 10 that panel advertises 60 Hz as preferred even though 120 Hz is available, so the desktop runs at half the panel's rate. [Issue #9537](https://github.com/omacom/omarchy/issues/9537) was closed by the reporter as acceptable behavior. Naming `eDP-1` in your own `~/.config/hypr/monitors.lua` and asking Hyprland for `highrr` instead is what fixed it there. See [the Omarchy manual's monitors chapter](https://omarchy.org/manual/monitors/) for how that file is meant to be edited.

## What Omarchy does for this model

Detection is `bin/omarchy-hw-surface`: DMI `sys_vendor` must be exactly `Microsoft Corporation`, and `omarchy-hw-match "Surface"` must find the substring in `product_name` or `product_family`, case-insensitively. That catches every Surface line, including ones nobody has tested.

Two install-time leaves then run, both from `install/hardware/all.sh`:

- `surface.sh` installs `linux-firmware-marvell`. That is its entire body. The package is also listed in `install/omarchy-other.packages` under a "Surface laptop support packages" comment.
- `fix-surface-keyboard.sh` writes `/etc/mkinitcpio.conf.d/surface_device_modules.conf` containing the detected pinctrl module plus `surface_aggregator`, `surface_aggregator_registry`, `surface_aggregator_hub`, `surface_hid_core`, `surface_hid`, `surface_kbd`, `intel_lpss_pci` and `8250_dw`. The module list comes from Chris McLeod's Surface Laptop Studio install write-up, credited in the file. If `product_name` is not literally `Surface Laptop 3` the script prints "Untested Surface Device" and carries on anyway.

Both are install-time scripts. `omarchy-update` does not re-run them, so a machine that came up from 3.x through [the Quattro upgrade](/upgrade/3-to-4-quattro/) keeps whatever drop-in it already had. Check the file yourself rather than assuming.

There is no Surface entry in the Omarchy speaker tuning set, no Surface touch package, and no Surface power profile.

## Variants

Prefer the **Intel Surface Laptop 3**. It is the only product name the keyboard script treats as tested, the Intel pinctrl path is the one that actually fires, and it is the model with a published working module list in the tracker. The Surface Laptop 4 has no clean report either way.

Avoid or treat as a project: **AMD Surface Laptop 3 and 4**, where the keyboard drop-in is never written; **Surface Book 2 and Laptop Studio**, which add the NVIDIA initramfs bug on top of dead touch; and **Surface Laptop Studio 2**, where the touchpad itself needs an out-of-tree driver.

The **Surface Go 2** has one open report, [issue #6079](https://github.com/omacom/omarchy/issues/6079): the machine goes black on shutdown but keeps running and drains the battery. Do not read that as Surface hardware. Commenters tie it to `omarchy-system-shutdown` scheduling the poweroff inside the user session scope, which systemd then kills during teardown, and that is a general Omarchy bug rather than anything about the Go.

Do not buy an **ARM Surface** for this. Omarchy ships x86_64 only.

Machines with two batteries, meaning the Surface Book family, will show wrong numbers in the power panel until one of the open battery PRs lands.

## Before you install

- Have a USB keyboard on hand. You may need it to type the LUKS passphrase on first boot, and you will need it if you land in a text console. See [/fix/stuck-at-tty-or-cannot-switch-tty/](/fix/stuck-at-tty-or-cannot-switch-tty/).
- Decide about disk encryption up front. Skipping LUKS sidesteps the whole pre-boot keyboard problem, at the obvious cost.
- After install, check that `/etc/mkinitcpio.conf.d/surface_device_modules.conf` exists. If it does not, and you are on an AMD Surface, write the module list from issue #11128 and rebuild the initramfs. Reporters used both `mkinitcpio -P` and `limine-mkinitcpio` depending on their boot setup; see [/hardware/boot-limine/](/hardware/boot-limine/).
- If you have a discrete NVIDIA GPU, check that the drop-in did not wipe your NVIDIA modules, per issue #7111.
- Treat touch and pen as not working until you decide whether to run the third-party linux-surface kernel. That kernel is unsigned for Microsoft Secure Boot keys, so plan for firmware changes.
- Turn off Secure Boot if you intend to use linux-surface at all.
- Report what you find at [/hardware/submit/](/hardware/submit/). This family has thin, mostly negative evidence, and the tracker only ever proves what is broken.

## Related

- [/hardware/touchpad-input/](/hardware/touchpad-input/)
- [/hardware/boot-limine/](/hardware/boot-limine/)
- [/hardware/webcam/](/hardware/webcam/)
- [/hardware/battery-power/](/hardware/battery-power/)
- [/hardware/nvidia/](/hardware/nvidia/)
- [/fix/luks-passphrase-not-accepted-at-boot/](/fix/luks-passphrase-not-accepted-at-boot/)
- [/releases/v4.0.4/](/releases/v4.0.4/)

## Sources

- [Issue #11128: Keyboard/touchpad dead at LUKS prompt on AMD Surface devices (fix-surface-keyboard.sh only handles pinctrl/Intel)](https://github.com/omacom/omarchy/issues/11128)
- [Issue #7111: fix-surface-keyboard.sh resets MODULES instead of appending, stripping NVIDIA early KMS on Surface devices](https://github.com/omacom/omarchy/issues/7111)
- [Issue #729: Surface Laptop Studio keyboard not working during Plymouth boot screen](https://github.com/omacom/omarchy/issues/729)
- [Issue #2092: [Microsoft Surface Laptop 4] - Can't type/login](https://github.com/omacom/omarchy/issues/2092)
- [Issue #9484: Surface Book 2 touchscreen dead on stock kernel (needs linux-surface/IPTS)](https://github.com/omacom/omarchy/issues/9484)
- [Issue #12136: Surface Laptop Studio 2: offer an opt-in linux-surface touchpad profile](https://github.com/omacom/omarchy/issues/12136)
- [PR #7857: feat(surface-touch): add touchscreen support for Surface devices via linux-surface kernel as boot option](https://github.com/omacom/omarchy/pull/7857)
- [Issue #8504: Battery percentage shows 0% on multi-battery systems (e.g. Surface Book)](https://github.com/omacom/omarchy/issues/8504)
- [Issue #11990: omarchy-battery-status reports only the first battery on multi-battery machines](https://github.com/omacom/omarchy/issues/11990)
- [Issue #9537: Surface internal display defaults to 60 Hz when 120 Hz is available](https://github.com/omacom/omarchy/issues/9537)
- [Issue #8843: Browser cannot access built-in camera even when libcamera, pipewire-libcamera, and qcam all work](https://github.com/omacom/omarchy/issues/8843)
- [Issue #6079: System still running after shutdown](https://github.com/omacom/omarchy/issues/6079)
- [install/hardware/fix-surface-keyboard.sh at v4.0.4](https://github.com/omacom/omarchy/blob/v4.0.4/install/hardware/fix-surface-keyboard.sh)
- [Release v3.1.4: Fix Surface keyboard compatibility with decryption screen](https://github.com/omacom/omarchy/releases/tag/v3.1.4)
- [Release v3.4.0: Fix Surface laptops should have driver kit installed by default](https://github.com/omacom/omarchy/releases/tag/v3.4.0)
- [Release v4.0.4 release notes](https://github.com/omacom/omarchy/releases/tag/v4.0.4)