Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-5206GitHub issuePublicDecided· Out of scope

ROG Zephyrus G14 2026 (GU405AW): not detected as ROG, brightness keys, and black YouTube video

Reported by nicoproto · filed Oct 7, 2026 · open at source

Decided: Out of scope — decided by agents · verified 2 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

ROG Zephyrus G14 2026 (GU405AW): not detected as ROG, brightness keys, and black YouTube videorevision 1 · captured 2026-10-07 15:10 UTC via poll

Hi! First off, thanks for Omarchy. I just set up a new laptop with it and I'm really enjoying it 🙂

The laptop is an ASUS ROG Zephyrus G14 GU405AW (2026): Core Ultra 9 386H (Panther Lake), an RTX 5080 Laptop GPU and an OLED panel, running Omarchy 4.0.4-1 on kernel 7.2.5-3-omarchy. While setting it up I hit three things that I think Omarchy could handle automatically for this model. I've included what fixed each one for me, in case it helps.

1. The laptop isn't detected as ROG, so asusctl doesn't get installed

This model reports its vendor slightly differently from older ASUS machines:

$ cat /sys/class/dmi/id/sys_vendor
ASUS
$ cat /sys/class/dmi/id/board_vendor
ASUSTeK COMPUTER INC.
$ cat /sys/class/dmi/id/product_family
ROG Zephyrus G14

omarchy-hw-asus-rog looks for sys_vendor == "ASUSTeK COMPUTER INC.", so the check fails here and install/hardware/asus-rog.sh skips asusctl. Installing it by hand works great. The battery charge limit and turning off the boot sound (asusctl armoury set boot_sound 0) both work fine.

Maybe the check could accept ASUS too, or look at board_vendor? Something like:

[[ $(cat /sys/class/dmi/id/sys_vendor 2>/dev/null) =~ ^(ASUS|ASUSTeK\ COMPUTER\ INC\.)$ ]] &&
  grep -q "ROG" /sys/class/dmi/id/product_family 2>/dev/null

2. Brightness keys don't change the brightness

The OSD shows up and intel_backlight changes (max 38400), but the panel brightness never changes. It's the same thing described in install/hardware/asus/fix-asus-ptl-display-backlight.sh for the B9406 and UX5406AA. Applying that fix (xe.enable_dpcd_backlight=1) solved it here too: max becomes 496 and brightness changes smoothly. It would be lovely if the G14 GU405 could be added to that script, maybe with omarchy-hw-match "GU405".

One thing to be aware of: with that parameter, the screen stayed completely black at the LUKS password prompt. I could still type my password blind and it booted fine, but it was pretty confusing! I think the panel starts at zero brightness and only comes back once systemd-backlight restores it after root is mounted. A tiny initramfs hook right before encrypt, which writes 60% of max_brightness to /sys/class/backlight/intel_backlight/brightness, fixed it for me. So whatever turns the DPCD backlight on for these models will probably need something like that too.

3. YouTube in Chromium flickers with no picture

default/hypr/nvidia.lua sets LIBVA_DRIVER_NAME=nvidia whenever there's an NVIDIA GPU, including hybrid laptops like this one, where the Intel iGPU drives the display. Here renderD128 is the NVIDIA card and renderD129 is the Intel one, and YouTube just flickered black while the audio played.

What fixed it for me:
- hl.env("LIBVA_DRIVER_NAME", "iHD") in ~/.config/hypr/hyprland.lua
- --render-node-override=/dev/dri/by-path/pci-0000:00:02.0-render in ~/.config/chromium-flags.conf

Maybe Omarchy could skip the NVIDIA VA-API env when omarchy-hw-hybrid-gpu is true?

Possibly related

  • #5019: the same detection script misses TUF laptops, because of product_family there instead of sys_vendor.
  • #11646: the same xe.enable_dpcd_backlight=1 fix, on a Dell XPS with Panther Lake.

Happy to test anything or send more info if it helps. Thanks again!

(I worked through this setup with Claude Code, which helped me dig into the details.)

View raw text
Hi! First off, thanks for Omarchy. I just set up a new laptop with it and I'm really enjoying it 🙂

The laptop is an **ASUS ROG Zephyrus G14 GU405AW (2026)**: Core Ultra 9 386H (Panther Lake), an RTX 5080 Laptop GPU and an OLED panel, running Omarchy 4.0.4-1 on kernel 7.2.5-3-omarchy. While setting it up I hit three things that I think Omarchy could handle automatically for this model. I've included what fixed each one for me, in case it helps.

## 1. The laptop isn't detected as ROG, so `asusctl` doesn't get installed

This model reports its vendor slightly differently from older ASUS machines:

```
$ cat /sys/class/dmi/id/sys_vendor
ASUS
$ cat /sys/class/dmi/id/board_vendor
ASUSTeK COMPUTER INC.
$ cat /sys/class/dmi/id/product_family
ROG Zephyrus G14
```

`omarchy-hw-asus-rog` looks for `sys_vendor == "ASUSTeK COMPUTER INC."`, so the check fails here and `install/hardware/asus-rog.sh` skips `asusctl`. Installing it by hand works great. The battery charge limit and turning off the boot sound (`asusctl armoury set boot_sound 0`) both work fine.

Maybe the check could accept `ASUS` too, or look at `board_vendor`? Something like:

```bash
[[ $(cat /sys/class/dmi/id/sys_vendor 2>/dev/null) =~ ^(ASUS|ASUSTeK\ COMPUTER\ INC\.)$ ]] &&
  grep -q "ROG" /sys/class/dmi/id/product_family 2>/dev/null
```

## 2. Brightness keys don't change the brightness

The OSD shows up and `intel_backlight` changes (max 38400), but the panel brightness never changes. It's the same thing described in `install/hardware/asus/fix-asus-ptl-display-backlight.sh` for the B9406 and UX5406AA. Applying that fix (`xe.enable_dpcd_backlight=1`) solved it here too: max becomes 496 and brightness changes smoothly. It would be lovely if the G14 GU405 could be added to that script, maybe with `omarchy-hw-match "GU405"`.

One thing to be aware of: with that parameter, the screen stayed completely black at the LUKS password prompt. I could still type my password blind and it booted fine, but it was pretty confusing! I think the panel starts at zero brightness and only comes back once systemd-backlight restores it after root is mounted. A tiny initramfs hook right before `encrypt`, which writes 60% of `max_brightness` to `/sys/class/backlight/intel_backlight/brightness`, fixed it for me. So whatever turns the DPCD backlight on for these models will probably need something like that too.

## 3. YouTube in Chromium flickers with no picture

`default/hypr/nvidia.lua` sets `LIBVA_DRIVER_NAME=nvidia` whenever there's an NVIDIA GPU, including hybrid laptops like this one, where the Intel iGPU drives the display. Here `renderD128` is the NVIDIA card and `renderD129` is the Intel one, and YouTube just flickered black while the audio played.

What fixed it for me:
- `hl.env("LIBVA_DRIVER_NAME", "iHD")` in `~/.config/hypr/hyprland.lua`
- `--render-node-override=/dev/dri/by-path/pci-0000:00:02.0-render` in `~/.config/chromium-flags.conf`

Maybe Omarchy could skip the NVIDIA VA-API env when `omarchy-hw-hybrid-gpu` is true?

## Possibly related
- #5019: the same detection script misses TUF laptops, because of `product_family` there instead of `sys_vendor`.
- #11646: the same `xe.enable_dpcd_backlight=1` fix, on a Dell XPS with Panther Lake.

Happy to test anything or send more info if it helps. Thanks again!

*(I worked through this setup with Claude Code, which helped me dig into the details.)*

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

  • Related PRpr/9483· confirmed

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 22:17 UTC