Omarchy Hardware

Lenovo

ThinkPad X1 Carbon Gen 9

Nineteen retained owner reports show a mature Arch-era ultraportable with a credible Omarchy path, but audio, fingerprint after resume, WWAN suspend behavior and USB-C charging deserve configuration-specific checks.

19exact-model reportsReport mix: four Omarchy · eight Arch Linux · four Arch-based · three other Linux

Bottom line

The X1 Carbon Gen 9 has a broad Linux record and four direct Omarchy component reports, but no retained report establishes a clean current Omarchy install and a complete pass across every component. Arch is the closest transfer evidence. Manjaro, CachyOS, NixOS, Pop!_OS and Debian results are labeled separately. The ordinary desktop path is credible; audio, fingerprint after resume, WWAN-equipped suspend and both USB-C charging ports are the areas to test rather than assume.

For a used machine, confirm type 20XW or 20XX, buy enough soldered memory, and favor the 1920×1200 low-power display if battery life matters more than resolution. Identify any WWAN modem before relying on suspend. Update the BIOS and embedded controller, then test each USB-C port separately for charging, data and video. Check every speaker group, microphone capture, fingerprint login and sudo before and after repeated suspend cycles during the return window.

What is reported

12 findings with cited evidence
  • Install and boot

    Three Manjaro owners and later Arch and CachyOS owners establish successful Linux installation and use. One Manjaro owner had to turn off Secure Boot. The direct Omarchy reports begin after installation, so they do not establish a current clean-install path.

    The machine is not an experimental Linux target, but an installer should still confirm Secure Boot state and keep recovery media. A working Arch-family install is supporting evidence, not a current Omarchy installation test.

    Working reportsSource 1, Source 2, Source 3
  • Desktop and graphics

    Owners use Iris Xe on Arch-family Wayland desktops, including browser video and external displays. Separate exact-model reports document green-tinted Chromium acceleration, repeated Sway fullscreen-video freezes and a current Omarchy Chromium popup that collapses at very wide logical window sizes.

    The integrated graphics support normal desktop work, but browser behavior should be tested at the intended display scale and compositor. These reports describe application paths, not a general failure of the internal desktop.

  • Internal display and brightness

    Exact-model owners use the internal display across several Linux distributions, including the 3840×2400 panel in a current Omarchy report. No retained owner identifies a basic internal-panel failure.

    Panel choice is principally a scaling, glare and battery decision in this corpus. It is not evidence that every brightness or Privacy Guard path has been tested.

  • Keyboard, hotkeys and backlight

    Owners clearly use the keyboard, and one suspend failure visibly flickered its backlight, but the retained reports do not test the full hotkey or backlight contract.

    Ordinary use without a complaint is not the same as a checked result. Test brightness, volume, microphone mute, keyboard lighting and lid behavior on the exact unit.

    Evidence, no verdictSource 1, Source 2
  • Touchpad and pointing

    A Pop!_OS owner found the touchpad smooth after boot but laggy after every suspend while the TrackPoint remained responsive. A Manjaro owner could not reproduce the gesture behavior of earlier X1 Carbon models.

    Basic pointing works, but resume and desktop gesture behavior can change the experience. Test the touchpad after sleep, not only after startup.

    Mixed resultsSource 1, Source 2
  • Fingerprint and biometrics

    Fingerprint enrollment worked for some Arch and Manjaro owners and differed between two otherwise similar Gen 9 units. Two current Omarchy reports document fingerprint loss after resume through different daemon and USB re-enumeration paths. An Arch owner made the infrared camera and fingerprint reader usable by assigning separate authentication jobs to each.

    The hardware can work, but reader ID, login stack and suspend state matter. Test login and sudo after several sleep cycles. Open Omarchy fingerprint changes are not treated as shipped fixes.

  • Wi-Fi and Bluetooth

    Basic Intel AX201 Wi-Fi is widely represented, but one NixOS owner lost Wi-Fi after resume on kernels 5.17 through 5.19 and restored it by restarting iwd; iwd 1.27 on kernel 5.15 had previously worked. An Arch owner found that the optional internal LTE driver's failure prevented suspend.

    Wi-Fi is credible for normal use, but resume behavior is version-sensitive. WWAN-equipped machines have a separate risk that cannot be inferred from Wi-Fi results.

    Mixed resultsSource 1, Source 2, Source 3
  • Speakers, microphone and audio

    One Manjaro owner restored sound with sof-firmware and another had working speakers but no microphone. Other exact owners report low or poor output, volume control that requires an update-overwritten configuration change and a current Debian top-speaker failure.

    A working codec is not a complete audio result. Test the upper and lower speakers, volume steps, microphone, headset routing and behavior after package updates.

  • Camera

    One Arch owner used the infrared camera for face authentication after adding infrared-light control, forcing OpenCV's V4L2 backend and separating PAM consumers. That is a successful exact-model result with substantial local configuration, not an Omarchy default.

    The camera hardware can be useful, but this corpus does not establish plug-and-play infrared authentication or a broad current Omarchy webcam result.

    Mixed resultsSource 1, Source 2
  • Suspend and resume

    An Arch kernel 5.17 immediate-wake regression was confirmed fixed by 5.19.2 for one owner. Other reports separate Wi-Fi loss, touchpad lag, an internal LTE driver blocking suspend and two current Omarchy fingerprint failures after otherwise successful resume.

    There is no single suspend verdict. Test sleep repeatedly with the fitted modem and all biometric devices enabled, then check Wi-Fi, touchpad and fingerprint after wake.

  • External displays and docks

    A CachyOS owner used a 34-inch display for browser-heavy work, and an Arch owner retained USB data plus two DisplayPort daisy-chained monitors on a USB-C port that no longer accepted power. A direct Omarchy owner reproduced a Chromium popup failure only when the external 4K window became very wide.

    External video can work even when another USB-C function does not. Test charging, data, DisplayPort and the intended browser scale as separate paths on both Thunderbolt ports.

    Mixed resultsSource 1, Source 2, Source 3
  • Battery, power and thermals

    A CachyOS owner found a quiet operating point near 60% of maximum performance while driving an external display and using about 20GB of memory. Measured Windows reviews found a large panel-dependent endurance gap: roughly 11 hours 40 minutes for the 1920×1200 unit and 7 hours 22 minutes for the 3840×2400 unit. A later Arch owner reported one USB-C port no longer negotiating power despite current firmware.

    Panel, workload, tuning and port health materially change mobile use. Review runtimes show hardware capacity, not expected Omarchy battery life; the USB-C report makes both charging ports a used-buyer test.

Changes over time

14 dated events
  1. Two Gen 9 units produce different fingerprint results

    One Arch owner reports that fingerprint enrollment worked on an earlier unit but failed after two fresh installs on a replacement running the same kernel-era packages.

  2. Touchpad lag appears after resume

    A Pop!_OS owner reports a smooth touchpad after reboot and repeatable lag after suspend, while the TrackPoint remains responsive.

  3. Manjaro owners establish a working base with component caveats

    Three exact owners report successful use while separating sof-firmware, microphone, fingerprint, Chromium acceleration and touchpad-gesture behavior.

  4. Linux 5.17 causes immediate wake

    One Arch owner traces immediate wake to the 5.17 kernel series and uses a 5.16 downgrade or two firmware toggles as temporary workarounds.

  5. Wi-Fi recovery becomes kernel-sensitive

    A NixOS owner reports that iwd 1.27 restored Wi-Fi after resume on kernel 5.15, with the failure returning on kernels 5.17 through 5.19.

  6. Kernel 5.19.2 fixes the immediate-wake report

    The original Arch report is closed after the owner confirms the suspend regression is fixed in 5.19.2.

  7. Sway fullscreen video freezes while audio continues

    An exact Arch owner repeatedly recovers Chromium playback by leaving and re-entering the browser's fullscreen mode.

  8. Volume workaround is overwritten by updates

    An Arch owner reports that an ALSA profile edit restores volume control but is repeatedly replaced by package updates.

  9. Omarchy update breaks Proton Pass clipboard action

    One Gen 9 owner reports that clicking Proton Pass fields stopped copying values after an Omarchy update while manual selection and copy still worked.

  10. Internal LTE driver identified as a suspend blocker

    An Arch owner restores suspend by blacklisting mhi-pci-generic, accepting loss of the internal modem.

  11. One USB-C port stops accepting power

    A Type 20XX owner reports that the port still carries USB data and two DisplayPort monitors but no longer negotiates charging, despite firmware newer than Lenovo's preventive minimum.

  12. Wide 4K Chromium windows expose an Omarchy UI bug

    A direct Omarchy 4.0.0-1 report narrows a clipped profile popup to logical window width rather than fractional scaling or the monitor alone.

  13. Fingerprint availability fails across suspend

    Two exact Omarchy owners document different post-resume failure paths involving the lock-screen probe, fprintd and reader recovery.

  14. Fingerprint fix remains under development

    Open and closed Omarchy pull requests continue to change fingerprint handling. No stable release plus exact-model owner retest has yet closed the finding.