Framework Laptop 13 on Omarchy

Verdict

Silver. The Framework Laptop 13 is a safe Omarchy machine, and it is clearly a popular one: 80 issues in the Omarchy tracker come from Framework 13 owners, the highest count of any single model in the dataset, just ahead of the MacBook Pro. Most of those reports are not about the laptop. They are quickshell, clipboard, reminder and update bugs that happen to be filed from a Framework 13.

It is not gold because of sleep. Three separate open issues describe things that do not come back correctly after resume: the fingerprint reader, the lock screen itself, and external displays behind a Thunderbolt dock. None of them stop you using the machine, and none of them are Framework faults, but you will meet at least one of them in normal laptop use.

Checked against v4.0.4 (2026-09-15) and the 4.0.x issue history. Where a report predates Quattro it is called out below.

What works

Wi-Fi, Bluetooth, the internal panel, the battery gauge and the Goodix fingerprint reader all come up with no manual setup. Journals attached to issue #6637 show a Framework 13 AMD 7040 associating on wlan0, loading Intel Bluetooth firmware and enumerating the Goodix MOC reader on a single boot, all without extra packages.

Audio works, including the internal microphones, because Omarchy ships a fix for them. See the next section.

Graphics are uneventful. AMD 760M, 780M and 890M run on amdgpu, and the Intel boards run on i915 or Xe. Omarchy installs vulkan-radeon or vulkan-intel through its generic GPU scripts and nothing Framework-specific is needed. Power is genuinely good: the v3.6.0 release notes cite 2 W idle on the Framework 13 Pro with the IPS panel.

Fingerprint enrollment has worked since at least August 2025. Issue #908 opens with a user saying the reader works well after setting it up from the Omarchy menu, and complains only that cancelling out of the prompt was unreliable.

What breaks

Fingerprint unlock after suspend (4.0.3, open). Issue #11412, on a Ryzen 5 7640U board, shows fprintd left with a busy device when the machine suspends mid-verify. After resume every retry fails instantly and the shell re-tries four times a second until you type your password. Workaround: type the password. A ThinkPad owner in the same thread saw the stuck fprintd survive three suspend cycles and only recover once it idled out after a password unlock, so expect it again after the next suspend that lands mid-verify.

Lock screen blanks 5 seconds after waking (4.0.3, open). Issue #11411, same reporter, same laptop. A timer frozen across suspend fires on resume and turns the displays off under you. A keypress normally brings them back, but the reporter measured a 10 second window on a Thunderbolt dock where keystrokes went nowhere until the DisplayPort link retrained.

External display dark after a long clamshell sleep (4.0.0, open). Issue #7328 is the best-measured Framework 13 bug in the tracker. On a Ryzen AI 9 HX 370 behind a CalDigit TS3 Plus, sleeps under about 12 minutes always came back; a 40 minute sleep with the lid still closed never did. The cause is that amdgpu drops hotplug interrupts raised inside the resume window, so nothing re-probes the connector when the dock fails to re-assert HPD. Opening the lid forces the rescan. The reporter’s fix, PR #7329, was still open at 4.0.4.

USB-C dock video on 11th gen Intel (open). Issue #9513 reports that on a Tiger Lake Framework 13, kernel 7.1.9 stopped binding ucsi_acpi to the USBC000 device, leaving /sys/class/typec empty and DisplayPort Alt Mode dead while USB and Ethernet on the same hub kept working. The reporter’s escape hatch was linux-lts. A commenter later argued the timeout variant of this bug is fixed in kernel 7.2.4 but that the never-binds variant is separate and has no known upstream fix. Omarchy’s stable channel now carries linux-omarchy 7.2.5, so this is worth re-testing before you downgrade anything.

Pro screen module plus AMD 7040 lockups (3.8.4, open). Issue #6637 describes hard freezes with kernel page faults and soft lockups when using the volume or brightness function keys, starting after a display module upgrade. Later in the thread the reporter says disabling hibernation kept the machine stable for four days.

Hibernate menu entry can be a silent no-op. Issue #7730, filed on a Framework 13 Pro Intel, shows the Hibernate menu entry appearing and doing nothing when the kernel has hibernation disabled, because omarchy-hibernation-available never asks the kernel. The reporter later traced the disabled state on that machine to Bitwarden Desktop holding memfd_secret memory, not to the laptop. The check fix, PR #7779, was still open at 4.0.4.

eGPU attached at boot hangs the machine. Issue #4047, Framework 13 plus RX 9070 XT over Thunderbolt: boot hangs before Plymouth. Hot-plugging the enclosure after login works fine. Closed with no Omarchy-side fix, since it fails before userspace exists.

Keyboard backlight off after unlock. Issue #7650, Framework 13 Pro Intel X7: the brightness helper saves 0 over the good value when the screen blanks twice, so the backlight never comes back. Four PRs proposing fixes were still open at 4.0.4.

What Omarchy does for this model

Less than you might expect, and that is a good sign.

There is exactly one Framework 13 quirk script in the tree at v4.0.4: install/user/hardware/framework/fix-f13-amd-audio-input.sh. It looks for an AMD Family 17h/19h audio card in pactl list cards and sets its profile to HiFi (Mic1, Mic2, Speaker), which is what exposes the internal microphones. It runs unconditionally on every install, so it is harmless on non-Framework machines. This landed as “Fix Framework Laptop 13 audio input was misconfigured” in v2.1.0 and has survived every release since.

There is no DMI matcher for the Framework 13. omarchy-hw-framework16 checks sys_vendor equals Framework and then matches “Laptop 16” against product_name or product_family via omarchy-hw-match, and the qmk-hid udev rule for RGB keyboards is gated behind it. Nothing in the tree keys on a Framework 13 product string. Owners report DMI product names of the form Laptop 13 (AMD Ryzen AI 300 Series), Laptop 13 (AMD Ryzen 7040Series) and Laptop 13 Pro (Intel Core Ultra Series 3), but those come from issue reports, not from a matcher you can read in the repo.

Intel Framework 13s pick up Omarchy’s generic Intel enablement instead: sof-firmware for the audio DSP, thermald, intel-lpmd on Alder Lake and newer hybrid CPUs, intel-media-driver for video acceleration, and on Panther Lake boards a fred=on kernel command line and the IPU7 camera driver when the ACPI camera OVTI08F4 is present. All of those match on CPU or PCI IDs, not on the Framework name.

Variants

AMD Ryzen 7040 and Ryzen AI 300. The best-represented boards in the tracker and the ones the audio fix targets. Nothing generation-specific is broken on them.

Intel Core Ultra Series 3, the “13 Pro” board. DHH said in issue #6637 that he runs a 13 Pro on Quattro himself, and it is the machine the v3.6.0 notes cite for 2 W idle. Two of the issues cited on this page come from Pro Intel owners, both small: the hibernation availability check and the keyboard backlight.

Intel 11th generation, Tiger Lake. The one variant with a real generation-specific problem, issue #9513. Buy it used and cheap if you want, but test your dock before you commit.

Ryzen AI 9 HX 370 with 64 GB: the installer may not boot. Issue #8629 reports the Omarchy 4.0.1 installer ISO dying with a GRUB out-of-memory error before or at its boot menu on an HX 370 Framework with 64 GB, with Secure Boot, UMA size and TPM settings all ruled out. The reporter did not say whether the chassis was a 13 or a 16, and the issue had no replies at 4.0.4. The installed system boots with Limine, so this is an ISO-only problem.

Before you install

• Update the Framework BIOS from Windows or the EFI updater first. Reports in the tracker name BIOS 3.05, 3.20 and 4.02, and firmware is the one layer Omarchy cannot patch for you.
• On 11th gen Intel, plug in your USB-C dock and confirm DisplayPort Alt Mode works before wiping anything.
• If you rely on hibernation, test it early. The one AMD report of lockups after hibernation resume is still open, and the Hibernate menu entry can silently do nothing if something on the system has hibernation disabled in the kernel.
• Do not attach an eGPU before first boot.
• After install, check your microphone in a call. If it is missing, the AMD profile fix did not take and you can run it by hand.
• If you game, watch the driver prompt. Issue #3585 reported the Steam installer auto-selecting nvidia-utils on an all-AMD Framework 13; that was fixed on dev the same day, but it is worth a glance.

Related

• Suspend and sleep on Omarchy for the resume failures above
• Thunderbolt docks for the clamshell display problem
• Fingerprint readers for enrollment and PAM behaviour
• Framework Laptop 16 and the Framework Desktop
• Still broken in the latest release
• Manual chapters: System sleep, Monitors, Hardware authentication
• Own one? Submit a hardware report