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-3: amdgpu GPU reset failure causes black screen after login on MacBookPro11,5 (Radeon R9 M370X)
Reported by greyraven · filed Sep 20, 2026Closed upstream on 2026-09-20 by its own reporter greyraven, as a duplicate of #12550 (R-312). GitHub close reason: completed.
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
What happened
After updating to linux-omarchy 7.2.5-3 on 2026-09-18, every boot into that
kernel produced a black screen shortly after logging in through SDDM/Hyprland:
the login greeter appears and accepts credentials, but the session never
becomes visible — the screen just stays dark. This reproduced on 3 consecutive
boot attempts.
Journal shows the AMD dGPU hitting a ring timeout as soon as Hyprland starts
issuing GPU work, then failing to recover:
amdgpu 0000:01:00.0: ring gfx timeout, signaled seq=2, emitted seq=4
amdgpu 0000:01:00.0: Process Hyprland pid 1389 thread Hyprland:cs0 pid 1451
amdgpu 0000:01:00.0: GPU reset begin!. Source: 1
amdgpu 0000:01:00.0: GPU reset succeeded, trying to resume
amdgpu 0000:01:00.0: VRAM is lost due to GPU reset!
amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] ERROR ring gfx test failed (-110)
amdgpu 0000:01:00.0: resume of IP block <gfx_v6_0> failed -110
amdgpu 0000:01:00.0: GPU reset end with ret = -110
amdgpu 0000:01:00.0: GPU Recovery Failed: -110
This then loops (repeated timeout -> failed reset) indefinitely. The Intel
iGPU on this machine also fails to find a display path on the same boot
([drm] Cannot find any crtc or sizes, disabling eDP), so the AMD card is
the only thing that can drive the panel, and once it wedges the screen has
no way to recover.
What was expected
Login to complete and Hyprland to render normally, as it does on `linux
7.2.3-arch1-3 on the same machine — zero ring gfx timeout` / GPU reset
messages appear anywhere in three separate boots of that kernel.
Steps to reproduce
- Hardware: MacBookPro11,5 (dual GPU: Intel Haswell iGPU (i915) + AMD Radeon
R9 M370X / "Venus XT", Southern Islands/GCN1, driven by amdgpu).
2. Update to linux-omarchy 7.2.5-3 (linux-omarchy-headers also installed).
3. Reboot into it, log in via SDDM/Hyprland.
4. Screen goes black within ~5-8 seconds of the Hyprland session starting and
never recovers.
System details
- Omarchy version: 4.0.4-1
- Failing kernel:
linux-omarchy 7.2.5-3(7.2.5-3-omarchy) - Working kernel on the same machine/config:
linux 7.2.3-arch1-3 - GPU: AMD Radeon R9 M370X (Venus XT, gfx_v6_0 / Southern Islands,
amdgpudriver) - mesa was upgraded to 1:26.2.2-1 on 2026-09-09, prior to the kernel update,
so the kernel update on 2026-09-18 is the only change that lines up with
the regression's onset.
Diagnosed by comparing journalctl -k output for the three failing boots on7.2.5-3-omarchy against the working boot on 7.2.3-arch1-3 — the timeout/
reset sequence above appears only on the former (0 occurrences on the
latter).
Filed by Claude Sonnet 5 via Claude Code.
View raw text
### What happened
After updating to `linux-omarchy 7.2.5-3` on 2026-09-18, every boot into that
kernel produced a black screen shortly after logging in through SDDM/Hyprland:
the login greeter appears and accepts credentials, but the session never
becomes visible — the screen just stays dark. This reproduced on 3 consecutive
boot attempts.
Journal shows the AMD dGPU hitting a ring timeout as soon as Hyprland starts
issuing GPU work, then failing to recover:
amdgpu 0000:01:00.0: ring gfx timeout, signaled seq=2, emitted seq=4
amdgpu 0000:01:00.0: Process Hyprland pid 1389 thread Hyprland:cs0 pid 1451
amdgpu 0000:01:00.0: GPU reset begin!. Source: 1
amdgpu 0000:01:00.0: GPU reset succeeded, trying to resume
amdgpu 0000:01:00.0: VRAM is lost due to GPU reset!
amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110)
amdgpu 0000:01:00.0: resume of IP block <gfx_v6_0> failed -110
amdgpu 0000:01:00.0: GPU reset end with ret = -110
amdgpu 0000:01:00.0: GPU Recovery Failed: -110
This then loops (repeated timeout -> failed reset) indefinitely. The Intel
iGPU on this machine also fails to find a display path on the same boot
(`[drm] Cannot find any crtc or sizes`, `disabling eDP`), so the AMD card is
the only thing that can drive the panel, and once it wedges the screen has
no way to recover.
### What was expected
Login to complete and Hyprland to render normally, as it does on `linux
7.2.3-arch1-3` on the same machine — zero `ring gfx timeout` / GPU reset
messages appear anywhere in three separate boots of that kernel.
### Steps to reproduce
1. Hardware: MacBookPro11,5 (dual GPU: Intel Haswell iGPU (i915) + AMD Radeon
R9 M370X / "Venus XT", Southern Islands/GCN1, driven by `amdgpu`).
2. Update to `linux-omarchy 7.2.5-3` (`linux-omarchy-headers` also installed).
3. Reboot into it, log in via SDDM/Hyprland.
4. Screen goes black within ~5-8 seconds of the Hyprland session starting and
never recovers.
### System details
- Omarchy version: 4.0.4-1
- Failing kernel: `linux-omarchy 7.2.5-3` (`7.2.5-3-omarchy`)
- Working kernel on the same machine/config: `linux 7.2.3-arch1-3`
- GPU: AMD Radeon R9 M370X (Venus XT, gfx_v6_0 / Southern Islands, `amdgpu` driver)
- mesa was upgraded to 1:26.2.2-1 on 2026-09-09, prior to the kernel update,
so the kernel update on 2026-09-18 is the only change that lines up with
the regression's onset.
Diagnosed by comparing `journalctl -k` output for the three failing boots on
`7.2.5-3-omarchy` against the working boot on `7.2.3-arch1-3` — the timeout/
reset sequence above appears only on the former (0 occurrences on the
latter).
---
Filed by Claude Sonnet 5 via Claude Code.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.