Omarchy Hardware

ASUS

ROG Zephyrus G16 GU605CR

Eleven exact-model owners include four running Omarchy and trace working hybrid NVIDIA, Wi-Fi and speaker paths, but brightness, OLED HDR and repeated suspend remain qualified.

11exact-model reportsReport mix: four Omarchy · one Arch-based · six other Linux

Bottom line

Omarchy is running on four exact GU605CR systems, including two reports on Omarchy 4.0.0. One owner reached a useful hybrid setup in which the RTX 5070 Ti entered D3cold, ordinary applications stayed on Intel graphics and games launched through PRIME offload. That result required substantial configuration. Omarchy later added native hybrid controls, fixed an Integrated-mode menu failure and hardened the control path against a stalled service, although the retained evidence does not include a complete exact-owner retest of the current path. The broader Linux record has improved over time: later kernels restored BE201 Wi-Fi, BIOS 310 restored the full speaker array for one owner, and the NixOS brightness reporter corrected the original failure after targeting the Intel backlight device. The remaining cautions are mode-specific brightness setup, incomplete OLED HDR and an NVIDIA suspend failure that appeared only after repeated sleep cycles.

An existing owner has a credible route if the machine is updated before troubleshooting and GPU modes are treated as separate configurations. Check Wi-Fi in the installer environment, update the BIOS before judging the speakers, and test brightness in Integrated, Hybrid and discrete-only modes. Repeated overnight suspend cycles with and without an external display matter more than a single successful wake. Buyers should verify the full GU605CR suffix and memory and storage configuration; the 32 GB memory ceiling is permanent, while the two M.2 slots leave room for storage expansion.

What is reported

12 findings with cited evidence
  • Install and boot

    Four independently attributable owners report running Omarchy on the exact model, from Omarchy 3.2.2 through 4.0.0. Other owners reached working NixOS, Fedora and CachyOS systems.

    The basic installation path is established. Older installation media can still lack working BE201 Wi-Fi, so a USB network path may be needed before the first kernel update.

  • Desktop and graphics

    One Omarchy owner configured Intel graphics as the default, reached NVIDIA D3cold at idle and launched Steam games on the RTX 5070 Ti through PRIME offload. A later owner found that Omarchy's menu entry disappeared after switching to Integrated mode, although the terminal command still switched the machine back.

    Both GPUs can be useful, but the result is not automatic across modes. Omarchy 4.0.2 checks supergfxctl before falling back to visible PCI devices and bounds a stalled query; there is no retained exact-owner retest of that complete current path.

  • Internal display and brightness

    A NixOS owner initially reported brightness stuck at 100% in Hybrid mode, then corrected the result: targeting the intel_backlight device restored control, with the model-specific kernel parameters still required. A CachyOS owner later found that the ordinary slider did nothing; a DPCD backlight setting enabled adjustment but left maximum brightness below the Windows result, while KWin reported the panel as incapable of HDR.

    Brightness has owner-confirmed working paths, but they are mode- and device-specific and HDR is not at clean parity. Test the panel in every GPU mode you expect to use rather than treating one working slider as a complete result.

    Mixed resultsSource 1, Source 2, Source 3
  • Keyboard lighting and ASUS controls

    asusctl 6.1.12 exposed keyboard-brightness levels, fan curves, platform controls, a charge threshold and throttle policy on the exact model, but only Static Aura lighting. A direct Omarchy owner separately found all SUPER keybindings wedged by the default fcitx5 process and restored them by removing fcitx5.

    Basic lighting and ASUS control interfaces are present, while dynamic lighting depends on newer project support. The Omarchy keybinding failure was a software interaction rather than evidence of a defective keyboard.

    Mixed resultsSource 1, Source 2
  • Touchpad and pointing

    ASUS lists a touchpad, and the measured Windows review describes it as large and responsive. No retained exact-model Linux report tests gestures, palm rejection or edge behavior.

    This is missing compatibility coverage, not a report of a touchpad problem.

    Not coveredSource 1, Source 2
  • Fingerprint and biometrics

    The Howdy compatibility list contains an exact GU605CR result on CachyOS, using the infrared camera at /dev/video2 with a model-specific confidence threshold.

    There is evidence for third-party infrared face recognition. It does not establish that Omarchy configures biometric login by default, and the machine has no listed fingerprint reader.

    Working reportsSource 1, Source 2
  • Wi-Fi and Bluetooth

    Three exact-model owners reported that the Intel BE201 was detected but could not connect on kernels through 6.15.1. One later confirmed normal connections with a patched 6.15.6 kernel, and a separate Fedora owner reported that Linux 6.16.7 fixed the Wi-Fi problems. Bluetooth worked in one of the earlier failure reports.

    Current kernels have positive Wi-Fi evidence, but older installers can reproduce the original failure. Update before assuming the radio itself is defective.

    Working reportsSource 1, Source 2
  • Speakers, microphone and audio

    A NixOS owner initially heard only the tweeters while the CS35L56-driven woofers remained silent. The same owner applied a temporary ACPI path and later reported that BIOS 310 resolved the problem.

    The full speaker path has a positive firmware-era result. The retained reports do not separately verify the three-microphone array or 3.5 mm headset path.

    Working reportsSource 1, Source 2
  • Camera

    An exact-model entry in the Howdy compatibility list verifies the infrared camera on CachyOS.

    The infrared stream has a working application-level result. Ordinary RGB video quality and every videoconferencing application remain untested in the retained exact-model Linux evidence.

    Working reportsSource 1, Source 2
  • Suspend and resume

    A Fedora owner restored reliable sleep and wake by changing the BIOS display setting from discrete-only to Dynamic. A later NixOS owner reproduced a hard freeze after multiple s2idle cycles over one to two days with the open NVIDIA driver, requiring a hard reset.

    A successful single wake is not enough to clear this model. Test repeated cycles in the intended GPU mode, including cycles with an external display attached.

    Mixed resultsSource 1, Source 2, Source 3
  • External displays, docks and ports

    The NixOS suspend report used the internal panel and a Dell DisplayPort monitor routed through the RTX 5070 Ti, then recorded display-link warnings around resume. No retained exact-model report isolates HDMI, both USB-C display paths, Thunderbolt docking or the SD reader.

    An external DisplayPort path is present in a working configuration, but dock and port coverage remains too thin for a broader verdict.

    Evidence, no verdictSource 1, Source 2
  • Battery, power and thermals

    One Omarchy owner measured about 20 watts when Hybrid mode still held the RTX GPU active, about 11 to 13 watts after reaching D3cold in Hybrid mode and about 10 watts in Integrated mode with the same two applications open. A measured Windows review recorded 7 hours, 37 minutes in an office workload, a 51.7 C exterior hot spot and 47.8 dB near the reviewer under load.

    GPU state can materially change unplugged use, but the Omarchy figures are one owner's observations rather than a controlled endurance test. The Windows battery, heat and noise measurements describe chassis capacity, not Omarchy runtime.

Changes over time

17 dated events
  1. Owner finds only Static Aura lighting

    asusctl exposed keyboard brightness and the main ASUS platform interfaces, but not the built-in dynamic lighting modes.

  2. Exact owners report unusable BE201 Wi-Fi

    Three GU605CR owners found the radio detected but unable to connect across several Linux distributions and kernels through 6.15.1.

  3. Patched kernel restores Wi-Fi

    One of the affected owners confirmed normal network connections on a patched Linux 6.15.6 build. A later Fedora report found the path working in Linux 6.16.7.

  4. Dynamic display mode restores wake

    A Fedora owner changed the BIOS display setting from discrete-only to Dynamic and reported reliable sleep and wake afterward.

  5. Hybrid brightness and woofer failures reported

    One NixOS owner found the panel stuck at full brightness in Hybrid mode and heard only the tweeters from the six-speaker array.

  6. Owner corrects the Hybrid brightness result

    The same NixOS owner reported that brightness control worked after specifying the intel_backlight device. The model-specific kernel parameters were still required.

  7. Omarchy owner reaches hybrid D3cold

    The exact-model owner kept the desktop on Intel graphics, launched games on NVIDIA and reduced observed draw from about 20 watts to 11 to 13 watts in Hybrid mode.

  8. GU605CR power-limit data enters kernel review

    A Linux platform-driver patch added exact-model AC and battery power-limit data. Review acceptance is project evidence, not proof that every distribution shipped it.

  9. BIOS 310 resolves the speaker failure

    The same owner who documented silent woofers reported that the firmware update removed the need for the temporary ACPI path.

  10. Omarchy adds a supergfxctl hybrid toggle

    The project introduced native switching support and later described broad G14 and G16 compatibility. This is project delivery, not an exact GU605CR owner retest.

  11. Integrated mode hides Omarchy's GPU toggle

    After the discrete GPU disappeared from the PCI bus, Omarchy no longer recognized the machine as hybrid and removed the menu entry needed to switch back. The terminal command remained usable.

  12. Project changes hybrid-capability detection

    Omarchy changed the detector to ask supergfxctl which modes the machine supports even when the dGPU is absent from PCI enumeration. The first containing release was v3.7.0; no exact-owner menu retest is retained.

  13. Removing an unused input method restores SUPER shortcuts

    One Omarchy owner isolated a complete SUPER-keybinding failure to fcitx5 and reported that uninstalling the unused input-method packages prevented recurrence.

  14. Current CachyOS report finds limited OLED brightness and no HDR

    A DPCD setting enabled brightness adjustment but left the panel dimmer than Windows, while KWin reported the internal OLED as incapable of HDR.

  15. Repeated s2idle cycles end in a hard freeze

    A NixOS owner documented an unrecoverable NVIDIA lockup after multiple sleep cycles over one to two days, including a 44-hour run with eight cycles.

  16. Linux control project adds a GU605CR sleep reset

    The g-helper-linux 1.0.89 changelog names the exact model in its synchronized sleep-reset data. This is a software landing, not a complete owner retest.

  17. Omarchy bounds stalled hybrid-mode queries

    Omarchy 4.0.0 added timeouts and fallback handling so a wedged supergfxd cannot hang the toggle or make the menu wait indefinitely.