# Framework Laptop 12 on Omarchy
Framework Laptop 12 on Omarchy 4.0.4: Intel Raptor Lake runs out of the box, but tablet mode is half done. Rotation, on-screen keyboard, touch gaps.
> **Short answer:** Buy it as a laptop, not as a tablet. The Framework Laptop 12 runs Omarchy 4.0.4 on the generic Intel path with no model specific setup, and owners including DHH use one. Touch input works, but Omarchy has no auto rotation and no on-screen keyboard, and the screensaver still will not dismiss on touch. Prefer the 13th Gen Intel board over the new Wildcat Lake one for now.
- Applies to Omarchy: 3.x and later
- Status: partial
- Last verified: 2026-09-16
- Canonical: https://omarchylinux.org/hardware/framework-laptop-12/
_Unofficial community page. Not affiliated with 37signals or the Omacom Foundation. Omarchy is a registered trademark of 37signals LLC._

## Verdict

Silver. The Framework Laptop 12 is a plain Intel laptop as far as Omarchy is concerned, and plain Intel laptops are the easiest hardware this distro runs on. Nothing in the v4.0.4 tree is written for this machine, and nothing needs to be. The half that is not solved is the half you bought it for if you bought it as a convertible: touch works as a pointer, but Omarchy has no screen rotation, no on-screen keyboard, and an open bug where touching the screen will not wake it.

Owners are real and vocal. DHH mentioned his own new Framework 12 in issue #1422 in October 2025, and ColtonIdle, who filed most of the Framework 12 reports in the tracker, called it a delight to use Omarchy with in issue #2361. In discussion #834, inffy noted that people have made Omarchy work nicely on this machine. That is the accurate summary: it works, with a tablet shaped hole.

We checked this against the v4.0.4 source tree and against the issue tracker on 2026-09-16. Three issues name the Framework 12 in their own body, and four more carry Framework 12 owner reports inside someone else's thread.

## What works

The silicon is unremarkable, which is the point. The 13th Gen board is Raptor Lake U with Intel integrated graphics, and Omarchy's generic Intel path covers all of it.

Wi-Fi works, with one 3.x era caveat covered below. Framework's spec sheet lists an Intel AX211 Wi-Fi 6E module on the 13th Gen board, driven by iwlwifi with firmware from linux-firmware. It is not in the BE200 and BE211 list that Omarchy's Wi-Fi 7 workaround targets, so that script leaves it alone. The Omarchy evidence is issue #1422, where the card connected and browsed on a fresh 3.0.2 install before the iwd problem described below showed up.

Graphics work. Framework lists both 13th Gen chips as Intel UHD Graphics, and `intel/video-acceleration.sh` installs `intel-media-driver`, `libvpl` and `vpl-gpu-rt` when the lspci string contains HD Graphics, UHD Graphics, Xe or Iris. That was not always true. Issue #296 is the history: Framework's own eclecticc pointed out in August 2025 that Intel Framework laptops, the Laptop 12 included, needed `intel-media-driver` installed by hand before screen recording worked. He then wrote the detector himself in PR #1368, merged 2025-09-09, and the v2.1.1 release notes carry it as "Fix video acceleration on Intel GPUs". We have not seen a Framework 12 `lspci` dump in any Omarchy thread, so if `vainfo` comes up empty on yours, install those three packages by hand and file it.

Touch and the keyboard work as input devices. The reporter in issue #2361 describes scrolling working, the machine running fast, and the physical keyboard going quiet when folded into tablet mode, and devteapot's reproduction in issue #7762 has keyboard input dismissing the screensaver where touch does not. Nobody has written a word about the touchpad either way, so it reads unknown below, though no touchpad bug has been filed against this model.

## What breaks

The screensaver does not dismiss on touch. This is the live one. Issue #7762 is open against Quattro, and devteapot reproduced it on Framework Laptop 12 hardware specifically: touching the screen does nothing, moving the mouse does nothing, clicking does nothing, only a keypress works. The analysis in that thread pins it on `bin/omarchy-screensaver`, which waits for a byte on its terminal's stdin, and touch never becomes one. Worse, the lock timer is never cancelled, so the session can lock while you are actively tapping. Two pull requests that dismiss it on any input are open, #7780 and #8048, and the maintainer has not picked one. On a convertible this is the difference between a tablet and a brick, so flip the keyboard back, turn the screensaver off under _Trigger > Toggle > Screensaver_, or raise the `idle.screensaver` seconds in `~/.config/omarchy/shell.json` until it lands. The same request was filed for this machine much earlier as issue #3069. Mouse and click dismissal did ship for the 3.x screensaver in PR #3723 (v3.2.3, 2025-12-15), then v3.3.0 removed it again because it broke the screensaver with Bluetooth mice, and touch dismissal never existed. Issue #3069 was closed in February 2026 with nothing shipped for touch.

There is no screen rotation. Omarchy reads no accelerometer anywhere in v4.0.4, and `iio-sensor-proxy`, which Framework's own Arch guide for this machine says you must install before the sensor is usable at all, is not in the package set. `~/.config/hypr/monitors.lua` takes a static `transform` value and stops there, which the [monitors chapter](https://omarchy.org/manual/monitors/) documents. 2disbetter wrote the first working workaround in discussion #848, a shell loop around `monitor-sensor` that calls `hyprctl keyword monitor` on each orientation change, and later packaged it as FW12Rotate. In August 2026, mechanicsunlocked posted Gimbal in discussion #4431: an Omarchy 4 plugin that adds auto rotation, an on-screen keyboard laid out like the machine's own, two on-screen gesture knobs and a lock screen keypad. Neither is shipped or reviewed by Omarchy. Treat both as third party code you are choosing to run.

There is no on-screen keyboard. Nothing in the tree provides one. That was request item one in issue #2361, which was closed in February 2026 with no feature.

Three older reports have aged out but are worth knowing if you find an old thread. Issue #1422 is the Wi-Fi that comes up connected but routes nothing until `sudo rfkill unblock all`; ColtonIdle hit it on a brand new Framework 12 on 3.0.2, and DHH replied that he had seen the same on his own new Framework 12, though he thought his case was a different problem. DHH closed it in July 2026 on the grounds that Quattro replaced the iwd, Impala and systemd-networkd stack with NetworkManager, and asked for a fresh issue if it reproduces. Issue #2215 is an install failure on this machine caused by pulling the USB stick out at the reboot prompt instead of after the reboot. Issue #2308 is the 3.0.2 Chromium keyring password prompt, which jon-munoz also saw on a fresh Framework 12 install. All three are 3.x era. If you hit any of them on 4.0.4, file it.

## What Omarchy does for this model

Nothing by name. `bin/omarchy-hw-match` greps `/sys/class/dmi/id/product_name` and `product_family`, and the only Framework caller is `omarchy-hw-framework16`, which checks that `sys_vendor` is Framework and then matches the literal string `Laptop 16`. A Laptop 12 fails that test, so `framework16.sh` and the `qmk-hid` udev rule never run on it. You lose nothing: both exist for the Laptop 16 input module.

For reference when you want to write your own match, Framework's own `framework-system` tool maps two DMI product names for this machine: `Laptop 12 (13th Gen Intel Core)` and `Laptop 12 (Intel Core Series 3)`. Check yours with `cat /sys/class/dmi/id/product_name`.

What actually runs on a Laptop 12 install is the Intel set: `video-acceleration.sh` for VA-API, `sof-firmware.sh` for the audio DSP when lspci shows an Intel audio device, `thermald.sh` on Sandy Bridge or newer Intel with a battery, and `lpmd.sh`, which installs and enables `intel-lpmd` when `/proc/cpuinfo` reports a CPU model in its list. Raptor Lake's 183, 186 and 191 are in that list, so the 13th Gen board gets it. `fred.sh` and `fix-wifi7-eht.sh` are gated to Panther Lake and to BE200 and BE211 cards, so neither fires here.

## Variants

Two boards now share the chassis, and they are not equally proven.

The 13th Gen Intel Core board, with the i3-1315U or the i5-1334U, is the one every report on this page was written on. Prefer it if you want the boring outcome.

The Core Series 3 board, announced by Framework on 2026-08-18, is Intel Wildcat Lake with Core 3 304, Core 5 320 and Core 7 350 options, Thunderbolt 4, and an Intel BE213 Wi-Fi 7 module. Phoronix reported the first batch shipping in October 2026. It already has one confirmed Omarchy gap that is not model specific but will bite it: issue #11958, filed on 2026-09-15 against 4.0.3 and still open, shows that the Wildcat Lake GPU reports as `Wildcat Lake [Intel Graphics]`, which matches none of the patterns in `video-acceleration.sh`, so no VA-API driver is installed at all. Installing `intel-media-driver libvpl vpl-gpu-rt libva-utils` by hand fixes it. We have no Omarchy report on the BE213 Wi-Fi module or on suspend behaviour on that board at all. If you buy it, expect to be the first.

The 13th Gen board has no fingerprint reader at all; Framework's spec sheet lists it as none. On the Core Series 3 board it is built into the power button on the Core 5 and Core 7 configurations, and the backlit keyboard is an option on DIY units. We have no Framework 12 fingerprint report either way, so see [fingerprint readers](/hardware/fingerprint/) for the general picture rather than assuming.

## Before you install

Pick the 13th Gen board unless you want to test Wildcat Lake yourself.

Leave the USB stick in until the machine has actually rebooted and shown the vendor logo. That is what issue #2215 is about.

Expect to run without rotation on day one. Decide in advance whether you want to run FW12Rotate or Gimbal, both third party, or live with a static landscape screen.

Turn the screensaver off or raise its timeout, or plan to keep a keyboard reachable, until issue #7762 closes. The [toggles and screensaver chapter](https://omarchy.org/manual/toggles-idle-screensaver/) covers where those settings live.

If video decode looks wrong after install on any board, check `vainfo` before changing anything else.

We have no verified data on suspend, hibernate, battery life, audio, bluetooth, the touchpad or the webcam on this model under 4.0.4. An earlier hand written prototype of this site claimed all of those worked, and we could not source any of it, so those rows read unknown here. If you run one, [send us your results](/hardware/submit/).

## Related

[Intel graphics](/hardware/intel-gpu/) covers the VA-API detector and the Wildcat Lake gap in full. [Framework Laptop 13](/hardware/framework-laptop-13/) is the better documented sibling. [Touchpad and input](/hardware/touchpad-input/), [Wi-Fi](/hardware/wifi/) and [suspend and sleep](/hardware/suspend-sleep/) cover the subsystems we could not verify here. If you are moving a 3.x install forward, read [3 to 4 Quattro](/upgrade/3-to-4-quattro/) first.

## Sources

- [Issue #7762: [Quattro] Screensaver only exits on a keypress inside its own terminal](https://github.com/omacom/omarchy/issues/7762)
- [Issue #2361: Better framework laptop 12 support?](https://github.com/omacom/omarchy/issues/2361)
- [Discussion #4431: Better framework laptop 12 support?](https://github.com/omacom/omarchy/discussions/4431)
- [Discussion #834: Arch + Omarchy in Touchscreen laptops](https://github.com/omacom/omarchy/discussions/834)
- [Discussion #848: Omarchy + Rotation on Framework 12](https://github.com/omacom/omarchy/discussions/848)
- [Issue #2215: Removing USB installer when prompted results in error on framework 12](https://github.com/omacom/omarchy/issues/2215)
- [Issue #1422: Wifi sometimes stops working and requires rfkill or restarting iwd to work](https://github.com/omacom/omarchy/issues/1422)
- [Issue #296: intel-media-driver required for screen recording to work on intel integrated graphics](https://github.com/omacom/omarchy/issues/296)
- [Issue #11958: intel/video-acceleration.sh doesn't match Intel Wildcat Lake GPU, skips installing intel-media-driver](https://github.com/omacom/omarchy/issues/11958)
- [Issue #3069: Exit screen saver on touch screen or power button.](https://github.com/omacom/omarchy/issues/3069)
- [Issue #2308: Chromium asks for keyring password on every startup](https://github.com/omacom/omarchy/issues/2308)
- [framework-system: SMBIOS product name to platform table](https://github.com/FrameworkComputer/framework-system/blob/main/framework_lib/src/smbios.rs)
- [Framework Laptop 12 Updated For Intel Wildcat Lake, Shipping Starts In October](https://www.phoronix.com/news/Framework-Laptop-12-WCL)
- [Framework Laptop 12, now with Core Series 3](https://frame.work/blog/framework-laptop-12-now-with-core-series-3)
- [PR #1368: Install video acceleration for intel GPUs](https://github.com/omacom/omarchy/pull/1368)
- [PR #3723: Exit screensaver when mouse moves or clicks](https://github.com/omacom/omarchy/pull/3723)
- [Framework Laptop 12 specifications](https://frame.work/laptop12?tab=specs)
- [Framework linux-docs: Framework Laptop 12 Arch and CachyOS setup](https://github.com/FrameworkComputer/linux-docs/blob/main/framework12/Arch-CachyOS-Setup.md)
- [Omarchy manual: Toggles, idle and screensaver](https://omarchy.org/manual/toggles-idle-screensaver/)
- [Omarchy manual: Monitors](https://omarchy.org/manual/monitors/)