Framework
Laptop 13 with AMD Ryzen AI 300 Series
Thirty-seven exact-model field reports show a capable, repairable Omarchy laptop with well-supported everyday hardware and a more complicated record around sleep, docks and version-specific regressions.
Bottom line
All three Ryzen AI 300 variants have reached a working Omarchy desktop. The ordinary hardware has a strong current Arch baseline, and Omarchy has already fixed its hibernation-offset and Radeon-only Steam-install regressions. The remaining risk is concentrated in state changes: long sleep, hibernation, lid events, docks, external input and biometric authentication. Several reports are isolated to one device, kernel or configuration, so they are reasons to test a workflow rather than proof that every unit fails.
This is a strong candidate for buyers who value CPU performance, socketed memory and long-term repairability. Pick the processor deliberately: the Radeon 840M, 860M and 890M are materially different GPUs. Install with current firmware and a current kernel, keep an encryption-passphrase fallback, and test lid-close sleep, hibernation, fingerprint authentication and every dock or expansion card you plan to use. The 74 Wh battery requires the matching Pro bottom case and input cover, not a battery-only swap.
What is reported
12 findings with cited evidenceInstall and boot
Omarchy owners have installed and run all three processor variants. An older NixOS installer lacked internal-keyboard support until the owner used a newer installer kernel. An attached eGPU can stop early boot, while hot-plugging the same enclosure after boot worked in both Omarchy and Arch reports.
Use current installation media and keep the machine's first boot simple. Attach unusual USB4 or eGPU hardware only after the base system is running.
Desktop and graphics
The Radeon 890M produced a responsive Omarchy desktop and later kernels stopped an early browser-video reset in one CachyOS report. Separate Radeon 840M and 860M owners reported MES ring freezes on 6.17-era kernels, and a multi-monitor Omarchy transition exposed a Quickshell crash that was also seen on other hardware.
Do not generalize one GPU's result across the range. Keep the kernel current, distinguish driver failures from Omarchy shell failures, and retain a known-good kernel for GPU-heavy work.
Internal display and brightness
The internal display works in the direct Omarchy report and the current Arch hardware matrix. One early KDE Wayland corruption report was isolated to the nondefault Prefer Color Accuracy setting; disabling it restored normal output and a later follow-up said the upstream bug was fixed.
The retained record does not show a current general panel problem. The old KDE setting issue remains useful history, not a current warning for every desktop.
Keyboard, hotkeys and backlight
Current Arch documentation lists the internal keyboard as working, and a newer NixOS installer fixed an earlier missing-keyboard installation path. One Omarchy owner reported dropped characters from a specific external 2.4 GHz keyboard dongle after an upgrade.
The evidence supports the built-in keyboard. Treat the external-keyboard report as a device-specific regression until it is reproduced more broadly.
Touchpad and pointing
The current Arch matrix lists the touchpad as working. A Fedora owner found that the touchpad's wake capability caused immediate wake after lid-close suspend and stopped the behavior by disabling that wake source.
Pointer operation is supported. The touchpad can still affect power behavior even when pointing itself works normally.
Fingerprint and biometrics
The current Arch guide lists fingerprint login as working with current device firmware. Two NixOS owners said the reader disappeared after time or suspend, while a Linux Mint owner recovered it by restarting fprintd after resume. Omarchy's combined FIDO2, fingerprint and password authorization flow has a separate open interface bug.
Enrollment is not the only test. Verify the reader after a long suspend and keep password authentication available; a working sensor does not guarantee every Omarchy authorization dialog works.
Wi-Fi and Bluetooth
Current Arch documentation lists Wi-Fi and Bluetooth as working. Earlier owners encountered a 6.14 DHCP regression, a dormant adapter during Omarchy boot and a post-upgrade reconnect failure. The Arch kernel regression was confirmed fixed on 6.14.8; Omarchy later replaced its earlier network stack with NetworkManager and asked for fresh reports if the boot issue returned. The reconnect issue is closed, but the exact Ryzen AI 7 350 owner did not post a resolution.
The current baseline is working, but the history shows why kernel and Omarchy network-stack versions matter. A new failure should be filed as a fresh regression rather than attached to the old stack.
Speakers, microphone and audio
Framework's Fedora guide and the current Arch hardware matrix list the speakers and microphone path as supported. BIOS 4.02 adds the audio table needed for the newer Laptop 13 Pro speaker hardware.
This is a project-documentation baseline, not an exact Omarchy field result. There is no retained exact-model Omarchy audio failure, but that is different from direct verification.
Camera
The current Arch hardware matrix lists the webcam as working, and Framework documents the device for its supported Linux path.
The corpus has documentation but no exact-model Omarchy camera report. Buyers who depend on conferencing should still test camera, microphone and browser permissions together.
Suspend and resume
Short suspend works in several reports, but owners have also seen failed wakes, immediate lid-close wakes, lid events that never fire, heavy overnight drain, lost hibernation offsets and intermittent hibernation failure. Omarchy fixed its empty resume-offset regression in 3.5.1; one Debian owner repeatedly improved hibernation with pm_async=0.
There is no single sleep verdict. Test manual suspend, lid-close suspend, overnight drain, hibernation and resume on power separately; those paths have produced different outcomes on the same model family.
External displays and docks
Normal direct display output works, including a direct Omarchy dock setup. Reported edge cases include an attached-eGPU boot hang, a docked display lost after long sleep, choppy Scratchpad scrolling on a 5K external display and a multi-monitor Quickshell crash. One supposed USB4 failure was traced to a DisplayLink dock rather than native USB4 or DisplayPort Alt Mode.
Record the port position, expansion card, dock protocol, display count and sleep state. 'USB-C dock' is not enough detail to transfer one result to another setup.
Battery, power and thermals
One Fedora owner's two-month snapshot series produced a 6-hour, 20-minute median in a 64 GB, 2.8K configuration. Controlled Windows tests measured about 8.5 to 9 hours on 61 Wh and just over 11 hours after a 74 Wh chassis conversion. Omarchy owners have also reported roughly 2% hourly sleep drain and one measured post-resume CPU clamp that cleared after reconnecting power.
Active runtime and sleeping runtime are separate questions. The larger battery helps in controlled testing, but it does not fix suspend drain or a resume-state fault.
Changes over time
25 dated events- KDE color-setting corruption isolated
An Arch owner narrowed internal-display corruption to KDE's nondefault Prefer Color Accuracy setting and reported normal operation after disabling it. A later follow-up said the upstream bug was fixed.
- Browser-video GPU resets reported
Exact-model Arch and CachyOS owners tied repeated Radeon resets to the video-decoder path on early 6.14 kernels.
- Newer installer kernel restored the keyboard
A NixOS owner whose internal keyboard failed in an older installer reported that the current installer kernel fixed it and the rest of the machine worked.
- Hibernation failure reported
One Arch-based owner could not hibernate the Ryzen AI 300 model on the tested normal or LTS kernels and captured a TTM allocator warning.
- Wi-Fi and GPU fixes reach newer kernels
One Arch owner confirmed Wi-Fi recovery on 6.14.8. A CachyOS owner separately reported that the video-decoder resets stopped on kernel 6.15.
- Frequent Fedora wake failure reported
A separate owner reported that lid-close suspend often left the machine unable to wake.
- Omarchy Wi-Fi boot race reported
An HX 370 owner found the adapter dormant at boot under Omarchy's earlier network stack. The issue was later closed after Omarchy moved to NetworkManager.
- Radeon-only Steam selection fixed
Omarchy's Steam installer offered an NVIDIA package as the default on an AI 5 340 system. The project changed the detection path the same day.
- Fingerprint loss after suspend reported
Two NixOS owners said the fingerprint reader could disappear after time or suspend, with different workaround results.
- eGPU boot hang narrowed to attached startup
Omarchy and Arch owners with different processor and eGPU combinations both reported that attached startup hung while hot-plugging after boot worked.
- Heavy Omarchy suspend drain reported
An Omarchy owner reported an overnight drop from 72% to 18% without a wake event.
- ArchWiki changed audio from untested to working
The page's revision history records the audio matrix changing to working. This is a documentation-state change, not a direct Omarchy audio report.
- 5K Scratchpad scrolling slowdown reported
An AI 5 340 owner saw choppy Scratchpad scrolling on a 5K 60 Hz display; follow-up testing pointed to transparent blur and rendering cost.
- Omarchy 3.5.1 restored hibernation setup
A kernel update left resume_offset empty and broke hibernation. A manual repair worked, and Omarchy 3.5.1 shipped the project fix.
- Radeon 840M and 860M MES freezes reported
Linux Mint and Ubuntu owners reported MES ring freezes. The reports apply to the 840M and 860M variants, not the HX 370's 890M.
- Delayed fprintd restart recovered fingerprint
A Linux Mint owner confirmed that restarting fprintd after resume restored a reader that failed after longer suspends.
- Synchronous hibernation passed repeated A/B tests
A Debian owner repeatedly succeeded with pm_async=0 and reproduced the failure immediately after reverting it. This remains one operator's result.
- BIOS 4.02 added Laptop 13 Pro component support
Framework added support for the haptic touchpad, touch panel, speakers, side LEDs and 74 Wh battery, along with iGPU memory and power fixes.
- Lid events disappeared on one BIOS 4.02 system
A Fedora owner reported that manual s2idle worked for more than 38 hours while lid close generated no event, separating the lid path from suspend itself.
- Custom Secure Boot keys were removed during BIOS update
A Gentoo owner reported that BIOS 4.02 removed enrolled custom keys. Another owner found Secure Boot re-enabled after the update.
- ArchWiki changed TPM from untested to working
The revision history records the matrix change and adds an encrypted-disk unlock path tested with BIOS 4.02. The guide still recommends keeping a passphrase fallback.
- Post-resume CPU clamp measured
One Ubuntu owner measured an approximately 8.5-fold slowdown with CPU frequency stuck near 605 MHz after resume; reconnecting the charger restored performance.
- Omarchy docked-display failure reported after long sleep
Short suspend cycles worked, but a Dell display on a CalDigit dock did not return after roughly 40 minutes or more of closed-lid sleep until the laptop lid was opened.
- Omarchy USB autosuspend setting found ineffective
An owner found that Omarchy's modprobe setting did not apply because usbcore was built into the kernel. This is a distribution configuration issue, not defective Framework hardware.
- Multi-monitor profile change exposed a Quickshell crash
An HX 370 owner reproduced a workspace-widget crash while changing lid and monitor profiles. Reports on other machines point to a shell bug rather than a Framework-only failure.