Omarchy Hardware

Framework Desktop with Ryzen AI Max+ 395 and Omarchy

Thirteen exact-model owner accounts include eight people running Omarchy, two on Arch Linux and three on other Linux distributions, with direct evidence on GPU stability, local AI, displays, firmware and sustained performance.

Compiled from 13 exact-model owner accounts: 11 on GitHub and two on Framework Community. Report mix: eight Omarchy · two Arch Linux · three other Linux Updated

This page covers the Framework Desktop with the 16-core Ryzen AI Max+ 395, Radeon 8060S and either 64GB or 128GB of soldered memory. The 32GB Ryzen AI Max 385 and Radeon 8050S configuration is a different performance tier and is not included in the exact-model count.

Bottom line

The Framework Desktop is a credible, unusually powerful Omarchy machine, but the retained reports do not support an unqualified stability claim. Exact owners have run Omarchy from 3.0.1 through 4.0.0 and used the Radeon 8060S for the desktop and local inference. The local-AI setup was not consistent: one 128GB owner found that LM Studio detected the GPU on Fedora but not Omarchy, while another reached GPU inference through a manual ROCm path. The first owner later returned a likely faulty unit after loud power-supply noise, rear-port failures and sleep-related peripheral loss across three distributions. A separate cluster of 3.5-to-3.7 reports documents Chromium and video-triggered GPU lockups. No retained exact owner has retested that failure on 4.0.2.

Should you use or buy it?

For a general workstation, the 64GB and 128GB versions have the same CPU, GPU and memory bandwidth; buy 128GB for model capacity, large virtual-machine sets or unusually memory-heavy work, not for higher frame rates. Existing owners should update to the current BIOS and kernel before debugging peripherals or ROCm. New buyers should use the return window to test power-supply noise, every rear port and repeated suspend with the intended peripherals; the one owner who failed those checks was offered a board swap, so that result is serious but not a family-wide verdict. If the Chromium hard lock recurs, increased BIOS graphics memory and software video decoding are owner-tested mitigations, not universal fixes. Buyers focused on CUDA, OptiX, maximum gaming value or a conventional GPU upgrade path should choose a different system.

Framework Desktop with black side panels and multicolor front tiles
Photo: Framework
Release
Available August 2025Source
Launch price
$1,999Ryzen AI Max+ 395 with 128GB, DIY EditionFramework Desktop announcement and launch price
Current new price
$1,959–$3,449Ryzen AI Max+ 395 DIY Edition with 64GB or 128GB, before storage and operating system · observed Sept. 2, 2026Current Framework Desktop configurator

Current figures are dated asking prices, not completed sales or appraisals.

Compatibility

  • Working reports
  • Mixed results
  • Evidence, no verdict
  • Not covered
  • Not applicable
Install and boot
Desktop and graphics
Internal display and brightness
Keyboard, hotkeys and backlight
Touchpad and pointing
Fingerprint and biometrics
Wi-Fi and Bluetooth
Speakers, microphone and audio
Camera
Suspend and resume
External displays and docks
Battery, power and thermals

Before you buy

Check this exact model after Prime Big Deal Days: configuration, seller, orderability, returns and retained Linux evidence. A newer listing check does not refresh the compatibility findings above.

Match the seller's exact model and configuration to the findings above. Check the return period, condition, included charger and delivered price before ordering.

These are the sources behind the dated asking prices, not a live stock check. Searches and catalogs may include other configurations. We have not tested or endorsed individual listings.

These links are untagged; Omarchy Hardware earns no referral commission from them. How we handle commercial links.

Detailed findings

Install and boot

Working reports

Eight exact owners report installed Omarchy systems across releases from 3.0.1 through 4.0.0. An exact Arch owner initially lost video during the live installer with an Apple Studio Display, then booted the same ISO and display after intervening firmware updates.

In practice A normal installation has a positive owner baseline. With an unusual USB-C display, keep HDMI or a simpler monitor available for setup and update the BIOS before treating a black screen as an installer failure.

Sources Framework Desktop power-button wake report, Framework Desktop workspace timing report, Framework Desktop LM Studio and owner follow-ups, Framework Desktop Omarchy 3.2.0 report, Framework Desktop Arch installer and Apple Studio Display, Arch Linux on the Framework Desktop

Desktop and graphics

Mixed results

The Radeon 8060S drives ordinary desktop use, Arch gaming and local inference, but exact Omarchy owners reported hard GPU lockups around Chromium and video on 3.5 through 3.7. Removing Omarchy's default VA-API enables helped some owners; another exact owner still needed a 32GB BIOS graphics-memory setting. There is no exact 4.0.2 retest of the original failure.

In practice Do not read the closed issue as proof that the lower-level AMD failure is gone. Test hardware-accelerated video under the intended BIOS memory setting before relying on the machine, especially with several high-resolution displays.

Omarchy removed its default VA-API feature enables in May 2026. That global change shipped; a stronger Ryzen-395-specific software-decoding migration was later closed without merging. Project source

Sources Framework Desktop Chromium and amdgpu lockup reports, Omarchy removes default Chromium VA-API enables, Closed Ryzen AI Max 395 browser workaround, Framework Desktop Arch gaming report, Framework Desktop measured review

Wi-Fi and Bluetooth

Evidence, no verdict

Framework's current matrix lists Wi-Fi and Bluetooth as requiring setup on Arch and rates the distribution as carrying some stability risk. The retained exact Omarchy accounts do not isolate either radio well enough for a working verdict.

In practice Plan to follow the Framework Arch package guidance and verify both radios separately. This is official transfer guidance, not an exact Omarchy owner result.

Sources Framework Desktop Linux compatibility matrix, Arch Linux on the Framework Desktop

Suspend and resume

Mixed results

One exact Omarchy owner reported that waking with the power button also delivered the power-key action after unlock, while keyboard wake was normal. A second 128GB owner reported that every sleep crashed or disabled peripherals across Omarchy, Fedora and Ubuntu and returned the unit after Framework offered a board swap. The broader Linux record ties some rear-USB resume failures to an upstream xHCI and GPU ordering race whose fix reached current Arch kernels.

In practice Use a current kernel, then test wake by keyboard and power button plus every occupied rear USB port. A successful short suspend does not establish a heavily configured display and peripheral setup; repeated cross-distribution failure on one unit may justify hardware support rather than more operating-system changes.

Sources Framework Desktop power-button wake report, Framework Desktop LM Studio and owner follow-ups, Framework Desktop rear-USB resume investigation, AMD RDNA 3.5 Linux and memory guidance

External displays and docks

Mixed results

An exact Arch owner recovered an Apple Studio Display installation path after firmware updates. On Omarchy 4.0.0, an exact three-monitor owner documented a screensaver focus race that prevents the normal idle and display-power sequence. Framework also continues to track intermittent USB-C Power Delivery and DisplayPort Alt Mode handshakes.

In practice One or two conventional displays have the stronger baseline. Treat three-monitor idle behavior and USB-C display chains as separate acceptance tests, including sleep, wake and DPMS rather than initial picture alone.

Sources Framework Desktop Arch installer and Apple Studio Display, Framework Desktop three-monitor idle report, Framework AMD USB-C Power Delivery investigation, Framework Desktop BIOS 3.06

Battery, power and thermals

Mixed results

Independent Windows and Ubuntu measurements describe a quiet, thermally controlled 120-watt system with roughly 10-to-12-watt idle draw and strong sustained CPU performance. One exact 128GB owner instead returned a unit after finding the power supply unacceptably loud alongside rear-port and resume failures; Framework offered a board swap.

In practice The controlled reviews provide the stronger family baseline, while the return report defines a practical defect check. Listen to the power supply at idle and load during the return window instead of assuming every loud unit is normal for the chassis.

Sources Framework Desktop LM Studio and owner follow-ups, Framework Desktop measured review, Framework Desktop Linux measured review, Framework Desktop 128GB measured review

Daily use

Browser stability is the first acceptance test

A shipped mitigation helped, but the defect is not closed by evidence

The strongest failure cluster is a full amdgpu and SMU lock rather than an ordinary browser crash. Exact-owner outcomes diverged after Omarchy removed two VA-API feature enables, and the stronger per-processor workaround never shipped.

Sources Framework Desktop Chromium and amdgpu lockup reports, Omarchy removes default Chromium VA-API enables, Closed Ryzen AI Max 395 browser workaround

Local AI works, but not as one-click Omarchy hardware

Strong inference capacity with a version-sensitive ROCm path

One exact 128GB owner found that LM Studio detected the GPU on Fedora but not Omarchy. Another exact Omarchy owner reached GPU inference after installing the graphics and ROCm stack and using a gfx1151 override. Exact Debian and Ubuntu reports show that memory pressure and runtime versions can still change correctness or initialization.

Sources Framework Desktop LM Studio and owner follow-ups, Framework Desktop ROCm memory-pressure corruption report, Framework Desktop ROCm runtime comparison, AMD RDNA 3.5 Linux and memory guidance

A bad unit can look like a Linux problem

One owner returned the machine after the same failures crossed three distributions

The owner who also hit the LM Studio setup gap reported loud power-supply noise, rear-port failures and unusable resume behavior on Omarchy, Fedora and Ubuntu. Framework offered a board swap, which makes this a return-window hardware check rather than evidence that every Framework Desktop behaves this way.

Sources Framework Desktop LM Studio and owner follow-ups

Firmware, kernel and peripherals interact

Update first; reproduce with the complete desk attached

The retained record includes a firmware-dependent installer display, a BIOS slow-boot regression, USB resume ordering and an open Power Delivery umbrella. Testing the bare computer alone can miss the failure that matters at a desk.

Sources Framework Desktop Arch installer and Apple Studio Display, Framework Desktop BIOS 3.04 slow-boot report, Framework Desktop rear-USB resume investigation, Framework AMD USB-C Power Delivery investigation, Framework Desktop BIOS 3.06

Performance

Linux gaming

Strong 1080p and useful 1440p integrated graphics

One exact Arch owner reports more than 60 frames per second at 1440p medium-to-high settings in several named games, while controlled Windows tests place demanding modern games around a 1080p-high to 1440p range. This is not an Omarchy gaming benchmark.

Sources Framework Desktop Arch gaming report, Framework Desktop measured review

Changes over time

  1. Problem reportedSuspendOmarchy

    Power-button wake also opens the system menu

    An exact Omarchy 3.0.1 owner separates the bad power-button path from normal keyboard wake.

    Sources Framework Desktop power-button wake report

  2. Mixed resultDesktopOmarchy

    Owners split on LM Studio GPU detection

    One 128GB owner reports that Fedora detects the GPU while Omarchy does not; another exact owner reaches working Omarchy inference through Mesa, Vulkan, ROCm and a gfx1151 override.

    Sources Framework Desktop LM Studio and owner follow-ups

  3. Problem reportedSuspend, Power and thermalsOmarchy

    One owner returns a likely faulty unit

    After failures across Omarchy, Fedora and Ubuntu, the 128GB owner reports loud power-supply noise, nonworking rear ports and peripherals lost on wake. Framework offers a board swap; the owner returns the machine instead.

    Sources Framework Desktop LM Studio and owner follow-ups

  4. Regression reportedInstallother Linux

    BIOS 3.04 adds a long boot handoff

    An exact Fedora owner measures a greater-than-two-minute GRUB-to-kernel delay after the firmware update.

    Sources Framework Desktop BIOS 3.04 slow-boot report

  5. Workaround confirmedInstallother Linux

    Framework Desktop owners confirm the 3.05 boot recovery

    Exact and corroborating Desktop reports say the slow handoff is gone after moving to BIOS 3.05.

    Sources Framework Desktop BIOS 3.04 slow-boot report

  6. Regression reportedDesktopOmarchy

    Exact owners reproduce hard GPU lockups

    Framework 395 owners place the failure on Omarchy 3.5 and 3.6, often during Chromium video, after several kernel, firmware, Mesa and browser experiments fail to isolate a universal fix.

    Sources Framework Desktop Chromium and amdgpu lockup reports

  7. Project changeDesktopProject code

    Omarchy removes its default VA-API feature enables

    The shipped migration removes two browser feature flags after seven-hour clean owner testing and closes the original issue.

    Sources Omarchy removes default Chromium VA-API enables

  8. Mixed resultDesktopOmarchy

    Later crash outcomes remain configuration-dependent

    One exact owner still reports two crashes a day at the default graphics-memory setting with stronger software-decoding flags, while a 32GB BIOS setting remains stable for that machine.

    Sources Framework Desktop Chromium and amdgpu lockup reports

  9. Project changeDesktopProject code

    The processor-specific browser workaround closes unmerged

    The proposed migration does not ship; the maintainer favors a BIOS memory change while waiting for an AMD fix.

    Sources Closed Ryzen AI Max 395 browser workaround

  10. Problem reportedDesktopother Linux

    An exact Debian report finds ROCm output corruption under memory pressure

    The open report binds repeating invalid tokens to the 8060S, ROCm 7.2 and a reproducible multi-model memory-pressure condition.

    Sources Framework Desktop ROCm memory-pressure corruption report

  11. Problem reportedDocks and displays, SuspendOmarchy

    Three monitors expose an Omarchy screensaver race

    On 4.0.0, the screensaver terminates during sequential launch and prevents the normal idle lock and display-power sequence; the same configuration works with two monitors.

    Sources Framework Desktop three-monitor idle report

  12. Project changeInstall, DesktopRelease record + Project code

    Omarchy 4.0.2 becomes the current release boundary

    The audit checks the tagged release and current browser defaults, but finds no exact Framework owner retest of the original Chromium lockup on 4.0.2.

    Sources Omarchy 4.0.2 release, Omarchy 4.0.2 Chromium defaults

Sources

Omarchy reports are direct results. Arch, Arch-based and other Linux reports are labeled separately and used only as evidence of hardware or driver behavior that may carry over. Shared-identifier and related-model reports are context and do not enter the exact-model count.

  • Framework Desktop power-button wake report

    Field report on GitHub · Omarchy · Sept. 28, 2025

    Exact 395 owner on Omarchy 3.0.1 distinguishes power-button wake from a working keyboard-wake path.

    Open source
  • Framework Desktop workspace timing report

    Field report on GitHub · Omarchy · Oct. 31, 2025

    Exact 395/128GB owner report provides an installed desktop baseline; the workspace bug was software-level rather than a component failure.

    Open source
  • Framework Desktop LM Studio and owner follow-ups

    Field report on GitHub · Omarchy · Nov. 12, 2025

    Complete open, unanswered Discussion with two exact owners. One 128GB owner finds that Fedora detects the GPU when Omarchy does not, then reports cross-distribution sleep, rear-port and power-supply problems before returning a unit that Framework offered to swap. A second 395/8060S owner reaches GPU inference on Omarchy 3.1.7 through a manual package and runtime path.

    Open source
  • Framework Desktop Omarchy 3.2.0 report

    Field report on GitHub · Omarchy · Dec. 11, 2025

    Exact 395/8060S report provides another installed-system baseline; the reported popup was traced to local styling rather than hardware.

    Open source
  • Framework Desktop Chromium and amdgpu lockup reports

    Field report on GitHub · Omarchy · April 29, 2026

    Two conservatively exact 395 owners after excluding model-unspecified and cross-artifact replies; their repeated configuration tests remain mixed after issue closure.

    Open source
  • Framework Desktop three-monitor idle report

    Field report on GitHub · Omarchy · Aug. 24, 2026

    Exact 395/8060S owner reproduces the Omarchy 4.0.0 screensaver race with three monitors but not two.

    Open source
  • Framework Desktop Arch installer and Apple Studio Display

    Field report on Framework Community · Arch Linux · Nov. 24, 2025

    Exact 395/64GB owner reports the same Arch ISO and display working after intervening BIOS updates; the owner cannot isolate which update changed the result.

    Open source
  • Framework Desktop Arch gaming report

    Field report on Framework Community · Arch Linux · Aug. 22, 2026

    The exact 128GB configuration identifies the 395; the owner names several games running above 60 fps at 1440p medium-to-high settings.

    Open source
  • Framework Desktop BIOS 3.04 slow-boot report

    Field report on GitHub · other Linux · Dec. 10, 2025

    Exact 395/128GB Fedora owner measures the regression; the thread records later Framework Desktop confirmation that BIOS 3.05 removes it.

    Open source
  • Framework Desktop ROCm memory-pressure corruption report

    Field report on GitHub · other Linux · Aug. 17, 2026

    Exact 395/128GB Debian report with a reproducible multi-model condition; it remains open and is not treated as a general graphics failure.

    Open source
  • Framework Desktop ROCm runtime comparison

    Field report on GitHub · other Linux · June 19, 2026

    Exact 395/128GB Ubuntu owner reports a nightly HSA runtime segfault while the distribution's ROCm 7.1 packages work on the same host.

    Open source
  • Framework Desktop specifications

    Manufacturer specification on Framework · Sept. 2, 2026

    Manufacturer configurations, ports, dimensions and serviceability; not independent performance evidence.

    Open source
  • Ryzen AI Max+ 395 specifications

    Manufacturer specification on AMD · Sept. 2, 2026

    Processor, graphics and memory-interface specifications; vendor performance claims are not used as field results.

    Open source
  • Framework Desktop Linux compatibility matrix

    Official compatibility record on Framework · Sept. 2, 2026

    Framework lists kernel 6.11 minimum, recommends 6.15 or later and labels Arch community-supported with setup and stability qualifications; this is not Omarchy validation.

    Open source
  • Arch Linux on the Framework Desktop

    Project documentation on Framework · Sept. 2, 2026

    Manufacturer-published Arch installation and package path used as transfer guidance, not an exact Omarchy result.

    Open source
  • Framework Desktop BIOS 3.06

    Release record on Framework Community · Aug. 31, 2026

    Current stable firmware release and known-issue record; a release note does not establish an owner outcome.

    Open source
  • Framework AMD USB-C Power Delivery investigation

    Hardware support project on GitHub · Sept. 1, 2026

    Open manufacturer investigation that includes Framework Desktop USB-C display and Thunderbolt-device cases; family scope is kept separate from exact-owner counts.

    Open source
  • Framework Desktop rear-USB resume investigation

    Hardware support project on GitHub · Aug. 25, 2026

    Project thread documents the upstream xHCI and GPU resume-order fix and current kernel delivery; it is not counted as a retained exact-owner account.

    Open source
  • AMD RDNA 3.5 Linux and memory guidance

    Project documentation on AMD · Sept. 2, 2026

    Current gfx1151 kernel and shared-memory requirements; official compute-stack guidance rather than an Omarchy result.

    Open source
  • Omarchy removes default Chromium VA-API enables

    Project code on GitHub · May 8, 2026

    Merged global browser-config change and migration; owner results after the commit remain the evidence for hardware behavior.

    Open source
  • Closed Ryzen AI Max 395 browser workaround

    Project code on GitHub · July 19, 2026

    Closed, unmerged processor-specific migration; the proposed stronger software-decode flags did not ship.

    Open source
  • Omarchy 4.0.2 Chromium defaults

    Project code on GitHub · Aug. 31, 2026

    Tagged current defaults confirm that the older VA-API feature enables are absent; code state is not a crash retest.

    Open source
  • Omarchy 4.0.2 release

    Release record on GitHub · Aug. 31, 2026

    Current release boundary for this audit; it does not itself establish Framework compatibility.

    Open source
  • Framework Desktop measured review

    Original measured review on Notebookcheck · Sept. 15, 2025

    Independent production 64GB measurements for games, power, noise and thermals under Windows; hardware capacity, not Omarchy performance.

    Open source
  • Framework Desktop 128GB measured review

    Original measured review on ServeTheHome · Sept. 20, 2025

    Independent purchased-machine local-inference and memory-allocation measurements; not an Omarchy benchmark.

    Open source
  • Framework Desktop Linux measured review

    Original measured review on Phoronix · Aug. 7, 2025

    Independent production 128GB testing on Ubuntu 25.04 across CPU, graphics, creator and compilation workloads; not Omarchy.

    Open source
  • Ryzen AI Max+ 395 local-LLM benchmark sweep

    Original measured review on Framework Community · July 15, 2025

    Reproducible five-run llama-bench sweeps on 128GB preproduction Framework hardware with Arch kernels and linked raw data; the preproduction boundary remains explicit.

    Open source
  • Framework Desktop announcement and launch price

    Manufacturer specification on Framework · Feb. 25, 2025

    Official announcement, original 128GB Ryzen AI Max+ 395 price and product photography; not an owner result.

    Open source
  • Framework Desktop first-shipment update

    Release record on Framework · Aug. 7, 2025

    Framework said first-batch shipments would start in August 2025; the month is used as the availability date rather than treating the announcement as the release.

    Open source
  • Current Framework Desktop configurator

    Dated market snapshot on Framework · Sept. 2, 2026

    Dated manufacturer asking prices for new 64GB and 128GB Ryzen AI Max+ 395 DIY configurations before storage, operating system and optional parts.

    Open source

Related guides