Framework
Laptop 16 AMD Ryzen 7040
Twenty-one exact-model owner accounts include three people running Omarchy. Ordinary hardware works, but released BIOS 4.05 still carries a severe CPU-clamp warning.
Bottom line
Omarchy is running on this first-generation Framework Laptop 16 in three exact-model accounts, and the ordinary desktop, display, keyboard, touchpad, camera and wireless hardware all have positive Linux reports. The unresolved risk is severe CPU clamping: Framework lists the 545 MHz post-resume lock as a known BIOS 4.05 issue, one Ubuntu owner measured a related clamp on that released BIOS both after s2idle and during sustained work, and an Omarchy 4.0.1 owner recorded a separate 7.2-watt collapse without suspending. A private test BIOS reduced the recurrence rate for one other owner but did not eliminate it. USB-C ports also remain reported missing after wake. The older ambient-light report is no longer reproducible for its original owner.
Existing owners have a credible Omarchy path, but should verify delivered CPU speed under sustained load after long sleep, charging changes and discrete-GPU transitions; the configured maximum can look normal while actual performance is clamped. Record the 7040 mainboard, BIOS, charger wattage and whether the RX 7700S is present before comparing results. The integrated-graphics configuration removes one variable but does not avoid the reported BIOS 4.05 post-resume clamp. Buyers should treat the promised EC fix as pending until a public BIOS and exact-model owner retest exist. Do not merge this page's findings with the newer Ryzen AI 300 mainboard merely because both fit the Laptop 16 chassis.
What is reported
12 findings with cited evidenceInstall and boot
Three exact owners report running Omarchy, and three early Arch owners describe a smooth installation or migration into a working desktop. One later Omarchy installer hit a missing qmk-hid package in the Framework-specific step, which the project says it fixed after 3.8.4.
A working installation path is well supported. Keep Secure Boot and disk-layout choices distinct from later hardware behavior, and use current media so the qmk-hid packaging fix is present.
Desktop and graphics
Original Linux testing found both Radeon graphics devices usable with current firmware, Mesa and kernel support. An Arch owner later measured an RX 7700S stuck around 35 to 40 watts under sustained load, while a Kubuntu owner reported freezes when the module woke for an application; the latter was eventually tied to that machine's graphics-module interposer and fan detection.
The integrated GPU is the simpler path. For an RX 7700S system, confirm that the module is detected, remains stable across repeated sleep and wake transitions, and sustains expected power before relying on it for games or compute.
Internal display and brightness
The 165 Hz internal panel works in the Linux reviews and owner reports. A NixOS owner and an Artix owner measured a brightness overflow on Linux 7.1-era kernels; the original owner and another participant reported normal maximum-brightness behavior after moving to Linux 7.2.
The panel has a positive baseline, but brightness behavior changed across kernels. A failing 100% setting on Linux 7.1 should prompt a current-kernel check before a hardware diagnosis.
Keyboard, modules and lighting
Ordinary keyboard input works in multiple owner reports. One Omarchy 3.2.3 owner needed corrected udev rules before keyboard.frame.work could reach the keyboard and numpad, and an exact-device Omarchy change later added QMK-based RGB theme synchronization that survived a sleep-and-wake test.
Typing is not the unresolved part. WebHID configuration and theme-controlled lighting depend on qmk-hid, correct device permissions and the firmware behavior of the installed module.
Touchpad and pointing
The touchpad works in the retained Arch owner reports, and the repositionable module is part of Framework's documented input system. No retained exact-model report isolates a stock Omarchy pointing failure.
There is positive owner evidence for ordinary pointing, not a test of every left, center or right touchpad placement. Reseat the module before treating a missing device as a software regression.
Fingerprint and biometrics
The current ArchWiki matrix records the fingerprint reader as working, and Omarchy added broader Framework 16 Goodix detection. None of the 21 counted owner accounts provides a complete exact-generation Omarchy enrollment and resume test.
There is a supported-looking path but not enough direct evidence for a simple Omarchy verdict. Test enrollment, login and wake separately on the installed reader firmware.
Wi-Fi and Bluetooth
Early Arch owners report working Wi-Fi and Bluetooth. One of those owners later lost Wi-Fi after a resume and recovered only after rebooting, without establishing a recurring failure.
The radio has a strong working baseline, with a limited wake-related caution. Verify both Wi-Fi and Bluetooth after several lid cycles before depending on the machine away from wired networking.
Speakers, microphone and audio
Speakers, microphone and Bluetooth audio are present in early owner accounts and ArchWiki's current matrix. Framework's Linux guide still documents a headphone-buzz workaround, and the retained reports do not establish that speakers, headset output and headset input are equally clean under Omarchy.
A working speaker test is not a complete call or headset result. Check the specific output and microphone path you use, including after resume.
Camera
An exact Arch owner explicitly reports the webcam working alongside the microphone, Bluetooth, Wi-Fi, keyboard and touchpad. No retained report identifies a model-specific camera regression.
The webcam has direct positive owner evidence. Call quality and post-resume behavior remain application-level checks rather than established model problems.
Suspend and resume
Basic s2idle works for several owners, but other exact machines have resumed with missing USB-C ports or a severe CPU power clamp that remained reproducible on BIOS 4.05. One older Arch hibernation report has no current-firmware retest. A separate ambient-light failure stopped reproducing for its original owner without an identifiable update.
Closing the lid and seeing the desktop return is not enough: recheck delivered CPU speed, charging, every occupied port and Wi-Fi after a longer suspend. Framework says it has developed a cross-platform EC/PROCHOT fix, but no public Framework 16 Ryzen 7040 BIOS and owner retest establish delivery yet.
External displays, docks and expansion bays
An Arch owner drove two 4K monitors after increasing integrated-graphics memory, and current Framework guidance removes an older RX 7700S USB-C display workaround. A NixOS owner separately describes left-side ports losing data and charging after resume until a battery-disconnect reset; another thread participant reports the same symptom without a retained distribution.
Port position is part of the configuration. Confirm that the chosen bay supports display or charging, then repeat dock and monitor checks after sleep; the graphics-module rear port is display-only.
Battery, power and thermals
There are two distinct firmware-era stories. A BIOS 3.07 sustained-power reduction has one positive 4.03 beta retest, though the original 65-watt USB-PD case was not retested. The much steeper 544 MHz-class clamp remains current: Framework lists it as a BIOS 4.05 known issue, an Ubuntu owner measured roughly 1 GHz on that release after s2idle and again during a compile without another suspend, and an Omarchy 4.0.1 owner measured about 7.2 watts and 544 MHz without suspending.
Do not treat the private test BIOS as a fix: one owner's recurrence rate improved from roughly daily to three times in three weeks, but the clamp remained. A machine can boot and report a high configured maximum while delivering a fraction of normal performance; verify delivered speed under load and compare only matching BIOS, charger and graphics-module configurations.
Changes over time
18 dated events- Arch owners establish a working baseline
Owners describe smooth installation and working display, keyboard, touchpad, Wi-Fi, Bluetooth, webcam and microphone, with one isolated post-resume Wi-Fi loss.
- Hibernation stops restoring one Arch session
One owner reports that a previously working encrypted hibernation path powers off but no longer resumes on BIOS 3.05 and Linux 6.12 or 6.13. The thread contains no later firmware retest, diagnosis or fix, so it does not establish current-BIOS behavior.
- BIOS 3.06 post-resume clamp reported
An Arch owner reports roughly 544 MHz to 1.1 GHz after longer sleep. Additional exact-generation thread participants corroborate the symptom, but are excluded from the owner count because their Linux distribution is not retained.
- BIOS 3.07 lowers sustained CPU power in one setup
An Arch owner measures a drop from about 60 watts to 40 watts with a 65-watt monitor and restores the earlier behavior by rolling back to BIOS 3.05.
- One owner confirms the BIOS 4.03 beta power-table fix
A second owner from the BIOS 3.07 thread reports that the 4.03 beta restores expected behavior; the original reporter does not supply a retained retest. The confirming account is excluded from the volume count because its distribution is not retained.
- Corrected udev rules restore keyboard configurator access
An Omarchy 3.2.3 owner gets keyboard.frame.work working for the Framework keyboard and numpad after correcting device rules and an invalid Arch group assumption.
- USB-C bays lose power and data after resume
A NixOS owner reports left-side ports disappearing after wake; a BIOS battery-disconnect sequence restores them temporarily, and the owner says the problem persists in June. A second distro-unresolved participant reports the same symptom.
- Omarchy merges Framework 16 RGB theme support
The merged change detects the modular input hardware, installs qmk-hid and applies a theme after a physical-device sleep-and-wake test.
- Longer s2idle leaves two systems in a low-power state
A Fedora owner reproduces the problem across two mainboards, and a second exact-model owner reports that it remains on BIOS 4.05 without the discrete GPU.
- Ambient-light failure stops reproducing
The original Arch owner reports that the post-resume zero readings disappeared without a known kernel or firmware change; downgrading the kernel does not bring the symptom back.
- Ubuntu owner records the 544 MHz failure after overnight sleep
The RX 7700S system resumes after a charger change but remains at very low CPU speed until rebooted; a proposed test BIOS is not followed by a retained owner result.
- Omarchy repairs qmk-hid availability in the installer
The project traces a Framework 16 installation failure to a package missing from the offline mirror and records the fix after Omarchy 3.8.4.
- Framework tests revised EC PROCHOT handling
Framework says a private test BIOS changes how the embedded controller releases PROCHOT during sleep. No public BIOS version or commit is identified.
- Linux 7.1-era kernels overflow the brightness range
Two first-generation owners measure brightness wrapping above 64,267; later reports identify Linux 7.2 as the working boundary.
- Private test BIOS reduces but does not end the clamp
One distro-unresolved Framework 16 owner reports three recurrences in three weeks on the test BIOS, compared with roughly daily failures on earlier firmware.
- Framework plans a broader EC fix
A Framework representative says a cross-platform EC/PROCHOT fix has been developed for affected products and is scheduled for the following quarter. No released Ryzen 7040 BIOS or exact-model retest is identified.
- Released BIOS 4.05 still shows the severe clamp
An Ubuntu owner measures roughly 1 GHz under load on BIOS 4.05 after s2idle and again during a compile without another suspend; a separate Omarchy 4.0.1 owner records about 7.2 watts and 544 MHz without suspending. Reboot is the only reported reliable recovery in both cases.
- One graphics freeze case narrows to the module interposer
The Kubuntu owner links intermittent discrete-GPU freezes to a failing graphics-module interposer and inconsistent fan detection, limiting how far the report should be generalized.