Lenovo
ThinkPad X1 Carbon Gen 13
Twenty-seven exact-model owners show a capable, unusually light Linux laptop with a real Omarchy path, but the answer changes with its processor platform, camera, audio codec and fingerprint reader.
Bottom line
Omarchy is usable on documented X1 Carbon Gen 13 configurations, but there is no honest family-wide clean bill of health. Direct owners have installed it and used graphics acceleration. The retained 4 TB partition and invisible encrypted-prompt blockers each have an owner-confirmed workaround, though neither is proven unnecessary in the current installer. Other direct reports identify long-sleep lag, mute-indicator gaps and a fingerprint service that can go stale after resume. A second exact owner reproduced the sleep lag on Debian and reported substantial improvement on kernel 7.0.4-1, which points toward the Linux stack without establishing an Omarchy fix. Lunar Lake has the stronger mobile graphics and efficiency case; Arrow Lake is the route to 64 GB, optional cellular configurations and more CPU cores. Camera, audio and firmware findings do not transfer safely between those branches.
For a machine you already own, start with the four-character machine type and component IDs, then test the internal camera, headset jack, fingerprint reader, battery-only suspend and dock reconnect separately. A shopper should favor Lunar Lake for portability and integrated graphics, or Arrow Lake for 64 GB and CPU-heavy work. The 32 GB Lunar Lake configuration can run a 12-billion-parameter Gemma 4 model through LiteRT on its integrated GPU, but one Debian owner had to reduce the context allocation; do not mistake shared memory capacity for an unlimited GPU budget. An underspecified used listing is a real risk: ask for the machine type, processor, memory, panel and camera before buying.
What is reported
12 findings with cited evidenceInstall and boot
One owner completed Omarchy installation on a 4 TB drive after limiting the Omarchy partition to 2 TB. Two Arrow Lake owners reached a black screen at the encrypted-volume prompt when early KMS loaded Xe; one supplied the workaround and the original reporter confirmed that removing the mkinitcpio kms hook restored the visible prompt.
Installation is demonstrated and each retained blocker has an owner-confirmed recovery path, but neither workaround is established as unnecessary in the current installer. Match the fix to the processor branch, storage layout and actual boot stage rather than applying it broadly.
Desktop and graphics
Owners reached accelerated desktops on both Linux and Omarchy, and current Linux reviews show working Xe2 graphics. A Lunar Lake owner separately logged repeated hard resets across Linux 7.1.2 through 7.1.8 and maintains an exact-model Xe patch while upstream work continues.
A working desktop does not settle long-run GPU stability. The local patch is evidence of an active fix path, not a released Omarchy fix.
Internal display and brightness
Most owners report the internal panel and brightness controls working. One Fedora owner saw full-screen flicker when the pointer moved, while later Arch and Linux reports did not reproduce that behavior.
Panel type, kernel date and graphics stack matter. Test full-screen video, variable refresh and external-screen handoff on the actual configuration.
Keyboard, hotkeys and backlight
Keyboard input and backlighting are broadly reported working, but the speaker-mute indicator has varied by software state. One Arch owner saw it begin working after updates; another still needed a sysfs workaround, and an Omarchy pull request remains open.
The laptop remains usable, but the light can disagree with the real mute state. Treat the open Omarchy watcher as a workaround under review, not shipped support.
Touchpad and pointing
ArchWiki and exact-model owners report working touchpad and TrackPoint input. Retained reports do not identify a recurring model-specific pointing failure.
That supports ordinary pointing and scrolling. It does not establish identical behavior between the haptic and mechanical touchpad options.
Fingerprint and biometrics
Owners and ArchWiki report working fingerprint enrollment and use on some configurations. On a Synaptics 06cb:0123 unit, the reader re-enumerated after resume while fprintd kept the stale device; restarting service activation restored it.
Identify the reader before applying guidance. A working fresh-boot login does not establish repeated resume behavior.
Wi-Fi and Bluetooth
Current reports support working Wi-Fi and Bluetooth. Earlier Fedora setup required manual Bluetooth firmware, and one Arch owner found Bluetooth working on mainline Linux 6.16.5 and 6.17-rc5 but not the contemporary 6.12 LTS branch.
The hardware has a working path, but kernel and firmware age can decide Bluetooth support. Lunar Lake and Arrow Lake use different wireless hardware.
Speakers, microphone and audio
Speakers work for many owners, but the Lunar Lake SoundWire path has produced missing cards, a no-DMIC topology mismatch and a firmware regression. One exact owner had working speakers and jack detection but no 3.5 mm output while USB-C audio worked.
Test speakers, internal microphone, 3.5 mm output and resume separately. A result from Arrow Lake's HD Audio codec does not resolve Lunar Lake SoundWire behavior.
Camera
USB-camera configurations are reported working. MIPI/IPU7 units initially lacked a usable Arch path; a later owner needed Linux 6.18 or newer, an out-of-tree vision driver, current libcamera and PipeWire integration, and still saw a green cast.
The camera option is a purchase-level distinction. Ubuntu's certified MIPI stack uses OEM packages that do not automatically transfer to Omarchy.
Suspend and resume
One owner estimated roughly 0.3 watt in s2idle, while a direct Omarchy owner saw about 30 seconds of lag after several hours asleep on battery. A second exact owner reproduced that lag on Debian 6.19.14 and said it became much better on kernel 7.0.4-1, without claiming complete resolution. Other owners report an external-display resume hang, a stale fingerprint service and kernel panics around dock attach or detach.
Short sleep, overnight battery loss, post-wake responsiveness, device recovery and dock reconnection are separate tests. Plugged-in success does not settle battery-only suspend, and the Debian improvement is a useful kernel signal rather than an Omarchy fix.
External displays and docks
An exact owner reports successful multi-monitor use through a Thunderbolt 4 dock. Another reports semi-frequent kernel panics associated with dock attachment or removal, and one resume hang involved an external display.
The ports can drive a practical desk setup, but repeated hot-plug and suspend cycles remain the important reliability test. Lunar Lake supports two external displays with the internal panel; Arrow Lake supports three.
Battery, power and thermals
Lunar Lake owners report strong light-load efficiency, and measured reviews show excellent hardware capacity. Several Linux owners also saw balanced mode pin the CPU near 400 MHz; firmware or profile changes helped some but not all reports. Another Arch owner traced high idle activity to an ACPI interrupt whose workaround delayed brightness changes.
Awake runtime, performance profiles, suspend drain and firmware behavior must be judged separately. Windows battery measurements show capacity, not expected Omarchy endurance.
Changes over time
14 dated events- Early owners isolate a 400 MHz profile failure
Owners on several Linux distributions found the processor stuck near its minimum clock in balanced mode; profile and firmware changes produced mixed later results.
- Arch owner reports the speaker-mute light does not track state
A later update fixed the indicator for that owner, while another exact owner continued to need manual control.
- First retained Arch MIPI-camera report has no usable image
Later kernels and an out-of-tree IPU7 stack produced an image on the same machine, but color remained wrong.
- Post-install black screen reported on a 4 TB drive
The exact-model owner completed the installer but reached a black screen after reboot on the original full-drive layout.
- Original 4 TB owner completes installation
The exact-model owner reported that Omarchy worked after reducing the target partition to 2 TB. Later unrelated-machine comments in the same issue are not transferred to this model.
- Arrow Lake owners find an invisible encrypted-volume prompt
Two exact-model owners could boot by typing the encrypted-volume password blind, but the early unlock screen itself remained black.
- No-DMIC Lunar Lake configuration exposes a topology mismatch
The exact 21NS configuration helped the SOF project correct a topology assumption; it does not cover every Gen 13 audio branch.
- Original Arrow Lake owner confirms visible unlock prompt
The reporter confirmed that removing the mkinitcpio kms hook restored the encrypted-volume prompt while normal graphics still loaded after unlock.
- Omarchy owner reports lag after long battery-only sleep
The roughly 30-second lag did not appear on AC, and a reply reported similar behavior on a Lunar Lake machine running plain Arch.
- Current SOF firmware removes the sound card on one Lunar Lake unit
The owner restored the card with an older firmware release, establishing a regression rather than a permanently unsupported codec.
- A newer Debian kernel improves the same lag
A second exact X1 Carbon Gen 13 owner reproduces the long-sleep lag on Debian kernel 6.19.14, then says it is much better on 7.0.4-1 without declaring it fully resolved.
- Owner runs Gemma 4 12B after reducing its token allocation
The same Debian owner used LiteRT's Vulkan backend on the Lunar Lake integrated GPU. Gemma 4 E2B ran directly; the 12B model ran with a 9,000-token maximum and failed at 10,000 with an out-of-memory error.
- Exact-model Omarchy mute-light watcher opens for review
The proposed user-space change is tested on one owner's machine but remains unmerged.
- Fingerprint resume workaround opens for review
The proposal restarts stale service state after the Synaptics reader re-enumerates; it is not yet a released fix.