Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
linux-omarchy 7.2.5: PA32QCV EDID 6K@60, amdgpu only offers 6016x3384@30 (HDMI and DP)
Reported by vertex · filed Sep 19, 2026 · open at source
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
System details
- Omarchy 4.0.4-1
- linux-omarchy 7.2.5-4
- linux-firmware-amdgpu 20260810-2
- mesa / vulkan-radeon 26.2.2
- Hyprland 0.56.2
- Machine: Framework Desktop (AMD Ryzen AI Max 300 Series), BIOS 03.06
- GPU: AMD Strix Halo, Radeon 8060S [1002:1586] rev c1, driver amdgpu
- Display: ASUS ProArt PA32QCV (31.5" 6K, 6016x3384). Also tested with an ASUS PG27UCDM 4K120 on the same GPU.
amdgpu.dcfeaturemask=1026 (0x402 = DC_FRL_MASK|DC_MULTI_MON_PP_MCLK_SWITCH_MASK). FRL is already enabled. dcdebugmask=0.
What's wrong?
The monitor EDID lists native [email protected] as the DisplayID preferred timing (pixel clock 1289.75 MHz). amdgpu never advertises 6016x3384@60. The only 6K mode in DRM/Hyprland is `[email protected]`.
Asking Hyprland for 6K@60 (hl.monitor({ mode = "6016x3384@60" })) succeeds as a request and the kernel runs 6016x3384@30. Same result on:
1. HDMI-A-1 (direct to GPU; Thunderbolt dock not in the path)
2. DP via Thunderbolt
3. HDMI with the 27" unplugged (rules out dual-display DCN budget)
4K@60 on HDMI and DP works. Native 6K@30 works (sharp). 6K@60 never appears.
Expected
6016x3384@60 in the connector mode list on HDMI 2.1 (and/or DP 1.4 DSC), matching the EDID DisplayID preferred DTD.
Repro
- Framework Desktop + PA32QCV.
- HDMI: GPU HDMI-A-1 → PA32 HDMI (Ultra High Speed cable). OSD input = HDMI. Reboot so HDMI actually modesets (first plug can leave the CRTC at 0x0).
hyprctl monitors all— 6K list is only@29.99Hz.hyprctl eval 'hl.monitor({ output = "HDMI-A-1", mode = "6016x3384@60", position = "0x0", scale = 1 })'- Observe [email protected], not 60.
- Repeat on Thunderbolt/DP: same 6K@30-only list.
EDID (serials omitted)
DisplayID preferred:
- 6016x3384 59.992 Hz, 1289.750 MHz
- also 6016x3384 29.994 Hz, 635.750 MHz
HDMI Forum VSDB (when on HDMI-A-1):
- Max TMDS character rate 600 MHz
- SCDC present
- Max FRL: 3 and 6 Gbps × 3 lanes; 6, 8, 10, 12 Gbps × 4 lanes
Base preferred DTD is [email protected] (half of 6K).
DRM advertised high modes (Thunderbolt/DP and HDMI, same set):
- [email protected]
- [email protected] ← only 6K
- 4096x2160@60 and @30
- 3840x2160@60 and @30
No 6016x3384@60.
Extra: HDMI first-plug
Before reboot, HDMI-A-1 stayed 0x0@60 with Hyprland/aquamarine:atomic drm request: failed to commit: Cannot allocate memory and connector HDMI-A-1, has crtc -1.
After reboot, HDMI 3840x2160@60 modeset worked. 6K@60 still did not.
Why this looks like amdgpu, not the dock or Hyprland
- HDMI bypasses the Thunderbolt dock; same 6K@30 cap.
- Single display (27" unplugged); same cap.
- Compositor asked for 60; kernel selected 30.
- FRL bit already set (
dcfeaturemask=0x402).
Likely Linux 7.2 HDMI 2.1 FRL/DSC still not offering the 1289.75 MHz mode on Strix Halo. 7.4 is where FRL-default + VRR/ALLM/DSC are supposed to land.
Related
- #12083 — linux-omarchy 7.2.5 AMD HDMI high-rate instability (4K@120 blanks; 60 Hz is stable). Different symptom (link drop vs missing mode), same kernel/HDMI 2.1 era.
Not requesting
A distro kernel bump to 7.4 before mainline 7.4 exists. This is a hardware/driver report so it is on the radar when linux-omarchy rebases.
View raw text
### System details - Omarchy 4.0.4-1 - linux-omarchy 7.2.5-4 - linux-firmware-amdgpu 20260810-2 - mesa / vulkan-radeon 26.2.2 - Hyprland 0.56.2 - Machine: Framework Desktop (AMD Ryzen AI Max 300 Series), BIOS 03.06 - GPU: AMD Strix Halo, Radeon 8060S [1002:1586] rev c1, driver amdgpu - Display: ASUS ProArt PA32QCV (31.5" 6K, 6016x3384). Also tested with an ASUS PG27UCDM 4K120 on the same GPU. `amdgpu.dcfeaturemask=1026` (`0x402` = `DC_FRL_MASK|DC_MULTI_MON_PP_MCLK_SWITCH_MASK`). FRL is already enabled. `dcdebugmask=0`. ### What's wrong? The monitor EDID lists native **[email protected]** as the DisplayID preferred timing (pixel clock 1289.75 MHz). amdgpu never advertises `6016x3384@60`. The only 6K mode in DRM/Hyprland is **`[email protected]`**. Asking Hyprland for 6K@60 (`hl.monitor({ mode = "6016x3384@60" })`) succeeds as a request and the kernel runs **6016x3384@30**. Same result on: 1. HDMI-A-1 (direct to GPU; Thunderbolt dock not in the path) 2. DP via Thunderbolt 3. HDMI with the 27" unplugged (rules out dual-display DCN budget) 4K@60 on HDMI and DP works. Native 6K@30 works (sharp). 6K@60 never appears. ### Expected `6016x3384@60` in the connector mode list on HDMI 2.1 (and/or DP 1.4 DSC), matching the EDID DisplayID preferred DTD. ### Repro 1. Framework Desktop + PA32QCV. 2. HDMI: GPU HDMI-A-1 → PA32 HDMI (Ultra High Speed cable). OSD input = HDMI. Reboot so HDMI actually modesets (first plug can leave the CRTC at 0x0). 3. `hyprctl monitors all` — 6K list is only `@29.99Hz`. 4. `hyprctl eval 'hl.monitor({ output = "HDMI-A-1", mode = "6016x3384@60", position = "0x0", scale = 1 })'` 5. Observe [email protected], not 60. 6. Repeat on Thunderbolt/DP: same 6K@30-only list. ### EDID (serials omitted) DisplayID preferred: - `6016x3384 59.992 Hz, 1289.750 MHz` - also `6016x3384 29.994 Hz, 635.750 MHz` HDMI Forum VSDB (when on HDMI-A-1): - Max TMDS character rate 600 MHz - SCDC present - Max FRL: 3 and 6 Gbps × 3 lanes; 6, 8, 10, 12 Gbps × 4 lanes Base preferred DTD is `[email protected]` (half of 6K). DRM advertised high modes (Thunderbolt/DP and HDMI, same set): - `[email protected]` - `[email protected]` ← only 6K - `4096x2160@60` and `@30` - `3840x2160@60` and `@30` No `6016x3384@60`. ### Extra: HDMI first-plug Before reboot, HDMI-A-1 stayed `0x0@60` with Hyprland/aquamarine: `atomic drm request: failed to commit: Cannot allocate memory` and `connector HDMI-A-1, has crtc -1`. After reboot, HDMI 3840x2160@60 modeset worked. 6K@60 still did not. ### Why this looks like amdgpu, not the dock or Hyprland - HDMI bypasses the Thunderbolt dock; same 6K@30 cap. - Single display (27" unplugged); same cap. - Compositor asked for 60; kernel selected 30. - FRL bit already set (`dcfeaturemask=0x402`). Likely Linux 7.2 HDMI 2.1 FRL/DSC still not offering the 1289.75 MHz mode on Strix Halo. 7.4 is where FRL-default + VRR/ALLM/DSC are supposed to land. ### Related - #12083 — linux-omarchy 7.2.5 AMD HDMI high-rate instability (4K@120 blanks; 60 Hz is stable). Different symptom (link drop vs missing mode), same kernel/HDMI 2.1 era. ### Not requesting A distro kernel bump to 7.4 before mainline 7.4 exists. This is a hardware/driver report so it is on the radar when `linux-omarchy` rebases.
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
Not linked to any known issue, other report or change yet.
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 16:04 UTC