Lenovo
ThinkPad X1 Carbon Gen 11
Compiled from 22 attributable exact-model owners, including three direct Omarchy reports. The corpus contains successful everyday Linux use alongside recurring MIPI-camera problems, WWAN-related suspend failures and one unresolved Omarchy reboot report.
Bottom line
Three exact-model owners report directly on Omarchy: one broad positive report without component checks, one working-speaker report with a locally tested but unmerged tuning, and one i7-1370P report of unexplained hard reboots on two Omarchy kernels while Ubuntu remained stable on the same machine. Separate Arch, Ubuntu, Fedora, Debian and openSUSE reports include successful development, docking, Wi-Fi and fingerprint use, but do not establish those results under Omarchy. MIPI-camera and WWAN configurations carry the clearest repeated risks.
The lowest-risk choices in the current corpus are a U-series processor, 400-nit low-power IPS display, standard USB webcam and no WWAN. No owner tested that exact combination under Omarchy. The 64 GB option is paired with the i7-1370P; one measured review found weak sustained CPU scaling, while separate battery reviews of OLED/P-series and WUXGA/U-series configurations used different protocols. Existing owners should test repeated suspend, camera startup, direct HDMI, microphone capture and sustained load before moving their main environment.
What is reported
12 findings with cited evidenceInstall and boot
Ubuntu and Arch owners establish successful Linux use, and Ubuntu certifies one i7-1360P configuration with a custom 22.04 image. Another owner could not make the firmware recognize either Arch or Ubuntu installation media despite testing several ports, images and Secure Boot settings.
Linux installation succeeded for several owners. One exact owner could not get the firmware to list tested Arch or Ubuntu media, but the report did not identify the firmware state or a model-wide cause. Ubuntu certification applies to its tested custom 22.04 image, not every standard image.
Desktop and graphics
An Ubuntu owner used the machine for development, video calls and light gaming; an Arch owner reached a usable desktop; and one Omarchy owner gave a broad positive verdict. Another Omarchy owner confirmed VA-API with Intel's iHD driver but experienced hard reboots that continued after browser acceleration was disabled.
These reports support a working Intel graphics path, not quantified graphics performance or long-term Omarchy stability. The reboot report does not identify graphics as the cause.
Internal display and brightness
Linux owners used both touch IPS and 2.8K OLED panels. The Arch OLED owner needed desktop scaling; Notebookcheck separately measured 363 Hz PWM on its OLED review unit. The retained battery reviews used different processors, panels and protocols.
Panel choice changes resolution, touch support, color and PWM behavior. The corpus contains no controlled Linux or Omarchy comparison that isolates the panel's effect on battery life.
Keyboard, hotkeys and backlight
An Ubuntu owner and both measured reviews found the keyboard comfortable, while one new Arch installation initially would not accept keyboard input in desktop text boxes.
The hardware has strong positive evidence, but the Arch result shows that a working keyboard at boot does not guarantee a correctly configured desktop input stack.
Touchpad and pointing
Reviewers found the TrackPoint and touchpad effective, but the Arch OLED owner initially lacked tap-to-click and gestures and still lacked pinch-to-zoom after other setup problems were resolved.
Basic pointing hardware is usable; gesture behavior depends on the desktop and input configuration rather than the model name alone.
Fingerprint and biometrics
One Ubuntu owner reports using the optional fingerprint reader for login. Lenovo's Linux guide documents enrollment through GNOME Settings.
This supports fingerprint use on an equipped Linux configuration, not every reader, desktop or Omarchy setup.
Wi-Fi and Bluetooth
Wi-Fi worked in everyday Ubuntu use and could be brought up from the command line on a fresh Arch install. The optional MediaTek 5G modem is the sharper concern: two owners found that its mtk_t7xx driver prevented suspend, and Ubuntu's certification record says GSM did not work properly on its tested configuration.
The AX211 Wi-Fi path has positive evidence. Buyers who need WWAN should verify both mobile broadband and suspend; disabling or blacklisting the modem driver restored sleep for two owners but removes modem access.
Speakers, microphone and audio
Playback was working when one Arch owner retested after using fwupd, but the report did not identify which change restored it. An exact-model Omarchy contributor confirms that the raw internal speakers work but sound bass-light and top-heavy. That owner locally validated a PipeWire tuning, while an openSUSE owner needed a UCM path correction before PipeWire exposed the digital microphones.
Speaker playback has direct Omarchy evidence, but the proposed tuning is still open and unmerged. Test microphone capture separately because working speakers do not establish the input profile.
Camera
The standard USB webcam has one positive and one negative owner report. Across the retained MIPI threads, owners reported intermittent startup, custom-patch recoveries, later packaged paths and fresh regressions after kernel or distribution updates. Five Gen 11 owners in the Fedora thread moved the evidence beyond its opening failure; two later confirmed reliable starts with custom patches, while other owners continued to need relay restarts or lost video after updates.
Camera type and software version are more useful than a model-wide yes or no. The kernel fixes tested by owners entered upstream and stable-kernel work, but no retained Gen 11 owner confirms that a current Omarchy installation provides a durable MIPI video-call path. No retained report establishes the infrared path under Omarchy.
Suspend and resume
Two owners found that the optional MediaTek 5G driver's suspend error caused immediate wake or about 50% battery loss over six hours. Disabling or blacklisting mtk_t7xx restored suspend on those machines, but one owner still could not resume from hibernation and another found only s2idle available.
Suspend can work, but WWAN-equipped systems need a specific test. The workaround exchanges mobile broadband for sleep, and no retained report establishes reliable hibernation.
External displays and docks
One Ubuntu owner used the laptop docked with multiple monitors. A different owner could not use the built-in HDMI port with a monitor that worked on another Lenovo; that failure persisted across Ubuntu and Windows after firmware and settings checks.
One unspecified docked display path worked; one machine's built-in HDMI path did not across Ubuntu and Windows. The reports do not establish whether that HDMI failure was hardware-specific or model-wide.
Battery, power and thermals
Linux owners report about 1.5 hours under heavy use and five to six hours under a full workload. In separate Windows review protocols, the i7-1370P OLED model lasted about 6.5 hours in a Wi-Fi test and the i7-1355U WUXGA IPS model lasted 13 hours 45 minutes. The i7-1370P review unit also fell to roughly 15 watts under sustained multicore work.
Runtime varies widely across the reported configurations and workloads, but this corpus cannot assign the difference to panel, processor, workload or sleep behavior individually. The Windows results use different hardware and protocols and are not an Omarchy benchmark or controlled panel comparison.
Changes over time
22 dated events- UEFI and management-engine update failures reported
The capsules staged in Fedora but failed during the reboot updater.
- Correcting the EFI partition restores both updates
The same owner found that the disk's EFI System Partition flag was missing. Setting it allowed both UEFI and management-engine updates to complete, and the issue closed.
- WWAN driver identified as a suspend blocker
Two Linux owners traced immediate wake or severe standby drain to mtk_t7xx. Disabling or blacklisting the MediaTek modem driver restored suspend, although one still lacked working hibernation.
- Arch OLED setup exposes desktop configuration gaps
The exact-model owner reached the desktop but initially encountered scaling, input, gesture, Wi-Fi and sound problems. Sound was working when the owner retested after firmware updates, without identifying which change restored it; pinch-to-zoom remained absent.
- Intermittent MIPI camera startup reported on Fedora
The camera started successfully on roughly three of 10 attempts on an exact 21HM configuration.
- Two owners report opposite webcam results
A Pop!_OS owner had a working standard webcam, while another exact-model Linux owner could not use the webcam. The thread does not establish identical camera modules.
- Arch and Ubuntu installation media go unrecognized
The owner tried multiple images, ports and Secure Boot settings but never reached an installer and returned the machine.
- Two owners reach reliable starts with custom patches
Gen 11 owners reported reliable MIPI-camera starts after manually applying kernel-module patches on Manjaro 6.6.27 and Fedora 6.8.8. These were owner-built stacks, not a standard distribution or Omarchy path.
- Debian owner loses camera while moving from Linux 6.6 to 6.8
An owner whose MIPI camera had worked for three months on Linux 6.6 lost it after moving to 6.8; rolling the kernel and camera repositories back did not immediately recover it.
- Packaged Ubuntu camera path remains inconsistent
The original owner still found the camera unreliable on Ubuntu 24.04, while another Gen 11 owner called a related setup mostly usable but still needed relay restarts and occasional module reinstalls.
- Debian owner rebuilds the camera stack
The same owner restored video on Linux 6.11.2 with pinned driver, firmware, camera HAL, GStreamer and relay components. This was a custom stack, not an out-of-box fix.
- Ubuntu owner reports intermittent MIPI initialization
Camera modules failed to configure on roughly half of boots; unloading and reloading the sensor module sometimes restored the video path.
- Ubuntu and Debian owners validate the proposed fixes
One owner completed five successful boots and repeated tests in Zoom, VLC and a browser after building a patched Ubuntu 6.11 OEM kernel. A second Gen 11 owner reported working video with the same patches on Debian sid. Both results required owner-built kernels.
- Patch author reports upstream inclusion and expected backports
A patch author reported the fixes in Linux 6.13 release-candidate code and expected them in the 6.12 and 6.11 stable series. The retained Gen 11 reports do not contain a later packaged-kernel retest that clears every MIPI configuration.
- Ubuntu owner reports a packaged camera path
A second owner reported working video on Linux 6.8.0-51 with Ubuntu's HWE packages and the Somerville camera HAL repository.
- Ubuntu owner loses camera after moving to Linux 6.14
An owner returned to Linux 6.11.0-29 after 6.14.0-24 stopped the MIPI camera and the usual relay restart no longer recovered it.
- The same owner restores video on Linux 6.14
The owner reported working video again on 6.14.0-32 after correcting the kernel and user-space package combination, followed by one manual relay restart.
- Camera stops working after a Kubuntu 25.10 upgrade
A third owner reported that an internal camera which had worked earlier no longer produced video after the distribution upgrade.
- Internal microphone mapping failure documented
A local UCM path correction made both digital microphone sources visible.
- One i7-1370P owner reports hard reboots under Omarchy
The owner reproduced resets on two Omarchy kernels and did not observe them under Ubuntu on the same hardware. The open report does not identify Omarchy, graphics, thermals or power delivery as the cause.
- A second owner reports a broadly successful Omarchy system
The owner gives a broad positive verdict on Omarchy on an X1 Carbon Gen 11 but supplies no version, configuration, duration or component-level checks.
- Omarchy owner validates speaker playback and local tuning
The raw internal speakers worked, and the owner reported the best Linux sound they had achieved after applying a model-specific PipeWire tuning. The pull request remained open and unmerged on Sept. 3.