Framework
Laptop 13 with Intel Core Ultra Series 1
Twenty-seven exact-model Linux owners cover boot, graphics, sleep, power, ports and input. Three run Omarchy; four others run Arch Linux.
Bottom line
Three exact-model owners report using Omarchy: a 125H owner recovered Wi-Fi after a 3.3.3 update problem, a Series 1 owner stabilized an AX210 by keeping it on 5 GHz, and a 165H owner ran three displays on Omarchy 4.0.1 but found the stock screensaver could cause thermal throttling. Together they establish a real Omarchy desktop path, not a clean-install verdict or component-by-component validation. Firmware, graphics, wake and power behavior remain configuration-sensitive.
For an existing machine, use Linux 6.12 or newer, check the BIOS before diagnosing graphics or boot problems, and test suspend with the exact SSD and expansion cards you use. BIOS 3.07 requires 3.04 or newer and Framework says it fixes a Linux GPU hang. On a HiDPI or multi-display setup, disable the terminal screensaver or make the lock screen follow it quickly until a lower-frame-rate path ships and is retested. For a purchase, the replaceable memory, storage, wireless card and display reduce configuration risk, but the retained Omarchy reports do not establish a clean current installation path.
What is reported
12 findings with cited evidenceInstall and boot
Owners reached working Arch Linux, Fedora, Ubuntu, NixOS and Mint systems. Other reports found a two-DIMM no-POST state, intermittent unplugged boot loops, a no-POST failure after retimer work, Secure Boot setup failures and Mint NVMe timeouts after BIOS 3.06.
Framework lists Linux 6.8 as the minimum kernel and 6.12 or newer as recommended. A working installation does not prove that a later BIOS, retimer or Secure Boot change will preserve the same boot path.
Desktop and graphics
One Arch report shows direct rendering through i915 and Mesa on the internal display, and one Ubuntu owner reported months without display trouble. Other owners reported intermittent artifacts, full-screen freezes on Fedora and Ubuntu, and a graphics board replacement after support review.
The graphics stack can support an ordinary Linux desktop, but the result is not uniform across kernels, display servers and individual boards. The freeze report did not establish a single software cause.
Internal display and brightness
The 2256-by-1504 internal panel was active at 60 Hz in one Arch configuration. Separate Fedora and Ubuntu reports describe a black display after wake, intermittent wrong-color pixels and graphics freezes while the system continued running.
A working internal panel is directly reported, but so are intermittent failures that require a reboot. No retained report isolates whether the 2.8K panel changes the Linux risk.
Keyboard and backlight
The exact-model ArchWiki lists the keyboard as working. None of the retained owner reports separately tests keyboard backlighting or the full function-key row.
Ordinary keyboard input has current project-documentation support. Treat the backlight and specialty keys as unreported here rather than assuming the hardware specification proves Linux control.
Touchpad and pointing
One Fedora owner temporarily lost scrolling, right-click and multitouch gestures after shutdown on BIOS 3.01, then reported that updating to BIOS 3.03 restored the touchpad. The current ArchWiki lists the touchpad as working.
The failure and same-owner recovery are both retained. This supports current touchpad use but does not establish every gesture across every desktop environment.
Fingerprint and biometrics
The exact-model ArchWiki lists the Goodix 27c6:609c fingerprint reader as working and directs owners to fprint for authentication.
This is current Arch project documentation, not a retained owner account or an Omarchy enrollment test. Desktop integration and resume behavior remain unreported here.
Wi-Fi and Bluetooth
One Arch owner identified working AX210 Wi-Fi and Bluetooth. A 125H Omarchy owner temporarily lost the Wi-Fi device after updating to 3.3.3 and explicitly reported recovery after another update and reboot. A separate Series 1 Omarchy owner found the AX210 repeatedly chase an unusable 6 GHz radio after the NetworkManager migration, then stabilized the link by forcing the connection to the 5 GHz band.
The replaceable AX210 has a working path, but update state and a mixed-band access point can change the result. Forcing 5 GHz is a one-owner, one-router workaround, not a general reason to disable 6 GHz.
Speakers, microphone and audio
The Intel audio driver and PipeWire were active in an Arch report. A Fedora 43 owner stopped Bluetooth-headphone crashes by replacing WirePlumber, while an Ubuntu standalone-mainboard report found HDMI video but no audio after boot until reconnecting the adapter or suspending and resuming.
The retained evidence covers the audio stack, Bluetooth output and HDMI output; it does not explicitly test the internal speakers or microphone under Linux.
Camera
The second-generation Framework webcam enumerated through the Linux uvcvideo driver in one Arch system report, and the exact-model ArchWiki lists the 32ac:001c webcam as working.
That establishes a current camera path, but not video-call image quality, microphone behavior or privacy-switch behavior.
Suspend and resume
Hibernate and resume completed in one NixOS report, and one 125H Arch owner reported no sleep problems in ordinary use but did not test long battery-only sleep. Other owners reported intermittent failed wake, a black screen after wake and loss of deep idle after hibernation.
Closing the lid is not a binary compatibility result on this model. Short sleep, overnight drain and device recovery remain separate questions, and the dock, storage controller and graphics-driver path can change the result.
External displays and docks
One Omarchy owner used the internal 2.8K panel with 5K and 1440p external displays. HDMI video also worked after cold boot on one Ubuntu standalone mainboard, while an Arch owner found that several detected displays remained blank and earlier owners reported USB-C retimer-update failures.
A practical three-display Omarchy setup is directly reported, but display detection does not guarantee an image and working video does not guarantee HDMI audio. Test the exact expansion card, bay, monitor and wake path.
Battery, power and thermals
With the power-saving profile active, one 125H Arch owner observed 3 to 4 watts while reading static PDFs and no more than 10 watts during light scrolling. Separately, the stock Omarchy screensaver drove one 165H machine to about 531% CPU, 97 C and thermal throttling across three HiDPI displays. Other reports show SSD- and graphics-dependent sleep draw, battery-only crashes and persistent 200 MHz throttling.
The 61 Wh battery is only part of the mobile-use result. Workload, storage firmware, graphics initialization, BIOS state and sleep history can change draw or stability. The Omarchy thermal report isolates a software-rendering workload rather than a general chassis defect.
Changes over time
21 dated events- Two-DIMM no-POST failure reported
After BIOS 03.04, the laptop started with either memory module alone but not with both installed.
- SSD swap cuts s2idle draw
Replacing a Geil P4P drive with a Solidigm P44 Pro reduced one owner's measured s2idle draw from 5-6 watts to less than 1 watt.
- Secure Boot setup breaks EFI tools
Clearing all Secure Boot settings removed EFI-variable state expected by NixOS tools on one exact-model machine.
- Display artifacts and lost touchpad gestures reported
Separate Ubuntu and Fedora owners reported intermittent wrong-color pixels and a touchpad exposed as a generic mouse after shutdown.
- BIOS update restores touchpad gestures
The Fedora owner reported normal touchpad behavior after updating the machine from BIOS 3.01 to 3.03.
- Wake reliability problems reported
One Ubuntu owner reported an intermittent wake crash while docked, and one Fedora owner saw the internal display turn black after wake.
- Xe driver restores post-hibernate idle behavior
A NixOS owner reported that forcing the Xe driver instead of i915 stopped the reproducible rise in idle and suspend draw after hibernation.
- Unplugged boot loop reported
A charged Fedora machine intermittently looped through an adapter warning when started without the charger.
- BIOS 3.06 storage and update failures reported
Separate owners reported an EFI-variable update failure and Linux Mint NVMe timeouts after moving to BIOS 3.06.
- Core Ultra 5 owners report opposite graphics results
One Fedora and Ubuntu owner reported intermittent freezes requiring a hard reboot, while another 125H owner reported months of Ubuntu use without display trouble.
- Persistent 200 MHz throttling reported
One Core Ultra 7 155H machine stayed throttled across Fedora, Windows and Linux live systems until Intel SpeedStep was disabled in BIOS.
- Later Omarchy update restores missing Wi-Fi
After Omarchy 3.3.3 left one 125H owner's Wi-Fi device unavailable, another Omarchy update and reboot restored it.
- Bluetooth audio logout fixed in software
Replacing WirePlumber with pipewire-media-session stopped GNOME from crashing when Bluetooth headphones connected on one Fedora 43 installation.
- Arch detects HDMI displays but leaves them blank
Multiple monitors appeared at 1024 by 768 yet showed no image in one Arch i3 and KDE report.
- UEFI dbx update conflicts with owner-controlled Secure Boot
One owner found that enrolling custom keys and applying the revocation-database update left Secure Boot state unrecognized regardless of operation order.
- Battery stability reports diverge
One Fedora machine crashed within minutes of unplugging, while another 125H owner reported stable Ubuntu use after updating Samsung 990 Pro firmware.
- BIOS 3.07 becomes stable
Framework says the release fixes a Linux GPU hang, partially locked self-encrypting-drive boot and incorrect Battery Extender state after reboot, hibernation or shutdown.
- HDMI audio stays silent after cold boot
Video worked on an Ubuntu standalone mainboard, but audio required an adapter reconnect or a suspend-resume cycle after each boot.
- Forcing 5 GHz stops AX210 roaming loop
After the NetworkManager migration, one Omarchy owner's AX210 repeatedly left 5 GHz for an unusable 6 GHz radio. Restricting that connection to 5 GHz stabilized it on the owner's access point.
- Screensaver frame-rate changes open for review
One Omarchy proposal would cap the terminal screensaver at the focused display's refresh rate and another would let owners set a lower rate. Both remain unmerged.
- Three-display screensaver load causes thermal throttling
An exact 165H Omarchy owner measured about 531% CPU, a rise from 60 C to 97 C and repeated package throttling while the default screensaver rendered across three displays.