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.
Framework Desktop + LG 6K: DSC inactive, stuck at 6K@30 (no 6K@60)
Reported by kvz · filed Dec 8, 2025Closed upstream on 2025-12-11. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Summary
Framework Desktop (AMD Strix Halo iGPU) + LG UltraFine 6K over DisplayPort cannot run 6K@60. DSC is detected but never activates, so Hyprland only works at 6K@30 (or 4K@60). Tried latest Arch linux-git (6.18.0-1-git-12189-g67a454e6b1c6) – it crashes early (BUG in lib/string_helpers), so we fell back to stable. Docs say Omarchy targets 6K “retina 2x”, so this feels like a gap folks will hit on this hardware.
Hardware / Setup
- Machine: Framework Desktop (AMD Ryzen AI Max 300 Series / Strix Halo)
- GPU: iGPU (amdgpu)
- Display: LG UltraFine 6K (6144x3456) via DP
- DE: Hyprland (Omarchy defaults)
- Current working mode: 6K @ 30 Hz, scale 2.0 (fallback); 4K @ 60 Hz also works.
- Desired: 6K @ 60 Hz.
Current state (stable Arch kernel 6.17.9-arch1-1)
$ sudo ./bin/check-dsc.sh
Using debugfs: /sys/kernel/debug/dri/0000:c2:00.0 (DP-1)
== Link settings ==
Current: 4 0x14 0 Verified: 4 0x3e8 16 Reported: 4 0x546 16 Preferred: 0 0x0 0
== BPC ==
max_bpc: 8
output_bpc: Maximum: 10
== DSC ==
dp_dsc_fec_support: FEC_Sink_Support: yes
DSC_Sink_Support: yes
dsc_clock_en: 0
dsc_bits_per_pixel: 0
Summary: DSC supported=no, active=no on DP-1Attempted newer DC via linux-git
- Installed
linux-git(6.18.0-1-git-12189-g67a454e6b1c6) and set Limine to default. - Boot hits a kernel BUG early and never reaches GUI.
- Kernel log excerpt (from
journalctl -b -1 -k):
strnlen: detected buffer overflow: 17 byte read of buffer size 16
WARNING: lib/string_helpers.c:1035 …
…
kernel BUG at lib/string_helpers.c:1043!
Oops: invalid opcode: 0000 [#1] SMP NOPTI
Modules linked in: … amdgpu …
Tainted: G W 6.18.0-1-git-12189-g67a454e6b1c6 …Ask
1) Could the docs mention current AMD DSC limitations on Strix Halo / Framework Desktop and recommend the known-stable fallback (6K@30 or 4K@60) until DSC is active?
2) If you have a known-good kernel config/branch where DC enables DSC on this hardware, I’m happy to test.
3) If there’s a preferred upstream bug to follow (drm/amd), I can file it with these logs.
Why this matters
Omarchy advertises “retina-class 2x displays … 32" 6K” as defaults; Framework actively promoted Omarchy. Users on this exact combo will likely hit the same wall.
Thanks! Happy to provide more logs or try patches.
View raw text
### Summary Framework Desktop (AMD Strix Halo iGPU) + LG UltraFine 6K over DisplayPort cannot run 6K@60. DSC is detected but never activates, so Hyprland only works at 6K@30 (or 4K@60). Tried latest Arch `linux-git` (6.18.0-1-git-12189-g67a454e6b1c6) – it crashes early (BUG in lib/string_helpers), so we fell back to stable. Docs say Omarchy targets 6K “retina 2x”, so this feels like a gap folks will hit on this hardware. ### Hardware / Setup - Machine: Framework Desktop (AMD Ryzen AI Max 300 Series / Strix Halo) - GPU: iGPU (amdgpu) - Display: LG UltraFine 6K (6144x3456) via DP - DE: Hyprland (Omarchy defaults) - Current working mode: 6K @ 30 Hz, scale 2.0 (fallback); 4K @ 60 Hz also works. - Desired: 6K @ 60 Hz. ### Current state (stable Arch kernel 6.17.9-arch1-1) ``` $ sudo ./bin/check-dsc.sh Using debugfs: /sys/kernel/debug/dri/0000:c2:00.0 (DP-1) == Link settings == Current: 4 0x14 0 Verified: 4 0x3e8 16 Reported: 4 0x546 16 Preferred: 0 0x0 0 == BPC == max_bpc: 8 output_bpc: Maximum: 10 == DSC == dp_dsc_fec_support: FEC_Sink_Support: yes DSC_Sink_Support: yes dsc_clock_en: 0 dsc_bits_per_pixel: 0 Summary: DSC supported=no, active=no on DP-1 ``` ### Attempted newer DC via linux-git - Installed `linux-git` (6.18.0-1-git-12189-g67a454e6b1c6) and set Limine to default. - Boot hits a kernel BUG early and never reaches GUI. - Kernel log excerpt (from `journalctl -b -1 -k`): ``` strnlen: detected buffer overflow: 17 byte read of buffer size 16 WARNING: lib/string_helpers.c:1035 … … kernel BUG at lib/string_helpers.c:1043! Oops: invalid opcode: 0000 [#1] SMP NOPTI Modules linked in: … amdgpu … Tainted: G W 6.18.0-1-git-12189-g67a454e6b1c6 … ``` ### Ask 1) Could the docs mention current AMD DSC limitations on Strix Halo / Framework Desktop and recommend the known-stable fallback (6K@30 or 4K@60) until DSC is active? 2) If you have a known-good kernel config/branch where DC enables DSC on this hardware, I’m happy to test. 3) If there’s a preferred upstream bug to follow (drm/amd), I can file it with these logs. ### Why this matters Omarchy advertises “retina-class 2x displays … 32" 6K” as defaults; Framework actively promoted Omarchy. Users on this exact combo will likely hit the same wall. Thanks! Happy to provide more logs or try patches.
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.
No decision has been recorded yet.