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.
Cannot boot with AMD eGPU attached – system hangs before Plymouth (Framework 13 + RX 9070 XT)
Reported by hngrdev · filed Jan 1, 2026Closed upstream on 2026-02-01. 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
System details
Framework Laptop 13 (AMD Ryzen AI 300 Series) CPU: AMD Ryzen AI 9 HX 370 iGPU: AMD Radeon 890M eGPU: AMD Radeon RX 9070 XT eGPU enclosure: Aoostar AG02 (Thunderbolt)
What's wrong?
Cannot boot with AMD eGPU attached – system hangs before Plymouth (Framework 13 + RX 9070 XT)
System details
Hardware
- Framework Laptop 13 (AMD Ryzen AI 300 Series)
- CPU: AMD Ryzen AI 9 HX 370
- iGPU: AMD Radeon 890M
- eGPU: AMD Radeon RX 9070 XT
- eGPU enclosure: Aoostar AG02 (Thunderbolt)
- Internal display: 2880×1920 @ 120 Hz
- External display: 3440×1440 @ 100 Hz
Software
- Omarchy 3.2.3
- Kernel: Linux 6.17.9-arch1-1
- Desktop: Hyprland 0.52.2 (Wayland)
- Boot mode: UEFI
- GPU driver: amdgpu (default)
What’s wrong?
When booting with the eGPU connected, the system hangs before Plymouth appears. No splash screen, no TTY, and no visible progress. The machine appears stuck in early boot.
Booting without the eGPU works reliably.
If I boot without the eGPU and then hot-plug it after login, the eGPU works correctly and delivers full performance.
This suggests the failure happens during early kernel initialization, likely around PCIe/Thunderbolt enumeration or early amdgpu KMS, before userspace starts.
Steps to reproduce
- Power off the laptop
- Connect the Aoostar AG02 eGPU enclosure (RX 9070 XT)
- Power on the laptop
- System hangs before Plymouth / graphical boot
Expected behavior
System should reach Plymouth and continue booting normally with the eGPU attached.
Actual behavior
System hangs before Plymouth. Requires hard power-off.
Workarounds that currently work
- Boot without the eGPU
- Plug in the eGPU after login
- Manually rescan PCI
- Restart the Wayland session
Once hot-plugged, the eGPU works correctly with good performance, but the UX of having to stop sddm, go to another TTY, and restart sddm kinda sucks
Additional notes
- This appears related to early amdgpu modesetting (KMS) + Thunderbolt eGPU
- Likely a kernel / firmware / early-boot interaction rather than a userspace Omarchy issue, but reporting in case others hit the same setup
Happy to provide logs or test kernel parameters if helpful.
View raw text
### System details Framework Laptop 13 (AMD Ryzen AI 300 Series) CPU: AMD Ryzen AI 9 HX 370 iGPU: AMD Radeon 890M eGPU: AMD Radeon RX 9070 XT eGPU enclosure: Aoostar AG02 (Thunderbolt) ### What's wrong? ## Cannot boot with AMD eGPU attached – system hangs before Plymouth (Framework 13 + RX 9070 XT) ### System details **Hardware** - Framework Laptop 13 (AMD Ryzen AI 300 Series) - CPU: AMD Ryzen AI 9 HX 370 - iGPU: AMD Radeon 890M - eGPU: AMD Radeon RX 9070 XT - eGPU enclosure: Aoostar AG02 (Thunderbolt) - Internal display: 2880×1920 @ 120 Hz - External display: 3440×1440 @ 100 Hz **Software** - Omarchy 3.2.3 - Kernel: Linux 6.17.9-arch1-1 - Desktop: Hyprland 0.52.2 (Wayland) - Boot mode: UEFI - GPU driver: amdgpu (default) --- ### What’s wrong? When booting **with the eGPU connected**, the system hangs **before Plymouth appears**. No splash screen, no TTY, and no visible progress. The machine appears stuck in early boot. Booting **without** the eGPU works reliably. If I boot without the eGPU and then hot-plug it after login, the eGPU works correctly and delivers full performance. This suggests the failure happens during **early kernel initialization**, likely around PCIe/Thunderbolt enumeration or early amdgpu KMS, before userspace starts. --- ### Steps to reproduce 1. Power off the laptop 2. Connect the Aoostar AG02 eGPU enclosure (RX 9070 XT) 3. Power on the laptop 4. System hangs before Plymouth / graphical boot --- ### Expected behavior System should reach Plymouth and continue booting normally with the eGPU attached. --- ### Actual behavior System hangs before Plymouth. Requires hard power-off. --- ### Workarounds that currently work - Boot **without** the eGPU - Plug in the eGPU after login - Manually rescan PCI - Restart the Wayland session Once hot-plugged, the eGPU works correctly with good performance, but the UX of having to stop sddm, go to another TTY, and restart sddm kinda sucks --- ### Additional notes - This appears related to **early amdgpu modesetting (KMS) + Thunderbolt eGPU** - Likely a kernel / firmware / early-boot interaction rather than a userspace Omarchy issue, but reporting in case others hit the same setup Happy to provide logs or test kernel parameters if helpful.
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.