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.
nvidia.sh fails on Pascal GPUs (MX150): nvidia-580xx-dkms and lib32-nvidia-580xx-utils not found
Reported by gtech-pedrol · filed Aug 23, 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
- Laptop: Lenovo Ideapad 330-15IKB (model 81FE) - CPU: Intel Core i7-8550U - GPU: NVIDIA GeForce MX150 (Pascal / GP108) - Omarchy version: 4.0 (Quattro) — also reproduced on 3.8.x - Install method: Official ISO, full disk + LUKS encryption
What's wrong?
During the "Configuring system" / hardware phase, nvidia.sh correctly detects the MX150 as a Maxwell/Pascal/Volta GPU and attempts to install the legacy 580xx driver stack:
error: target not found: nvidia-580xx-dkms
error: target not found: lib32-nvidia-580xx-utils
[Failed]: /usr/share/omarchy/install/hardware/nvidia.sh (exit code: 1)This aborts the entire installation.
The same failure occurs even after working around the known offline mirror issues (by forcing online mirrors or skipping other hardware scripts). The 580xx packages simply are not available in the repositories the installer is using at that point.
Expected behavior:
- Successfully install nvidia-580xx-dkms + nvidia-580xx-utils + lib32-nvidia-580xx-utils from the correct source, or
- Gracefully skip the proprietary driver for legacy GPUs when the packages cannot be found, and continue the installation with a clear warning.
Workaround used:
Manually edited /mnt/usr/share/omarchy/install/hardware/nvidia.sh and added exit 0 at the top, then resumed the install with omarchy-apply-system.
Happy to provide full logs or test any proposed fix.
View raw text
### System details - Laptop: Lenovo Ideapad 330-15IKB (model 81FE) - CPU: Intel Core i7-8550U - GPU: NVIDIA GeForce MX150 (Pascal / GP108) - Omarchy version: 4.0 (Quattro) — also reproduced on 3.8.x - Install method: Official ISO, full disk + LUKS encryption ### What's wrong? During the "Configuring system" / hardware phase, `nvidia.sh` correctly detects the MX150 as a Maxwell/Pascal/Volta GPU and attempts to install the legacy 580xx driver stack: ``` error: target not found: nvidia-580xx-dkms error: target not found: lib32-nvidia-580xx-utils [Failed]: /usr/share/omarchy/install/hardware/nvidia.sh (exit code: 1) ``` This aborts the entire installation. The same failure occurs even after working around the known offline mirror issues (by forcing online mirrors or skipping other hardware scripts). The 580xx packages simply are not available in the repositories the installer is using at that point. **Expected behavior:** - Successfully install `nvidia-580xx-dkms` + `nvidia-580xx-utils` + `lib32-nvidia-580xx-utils` from the correct source, **or** - Gracefully skip the proprietary driver for legacy GPUs when the packages cannot be found, and continue the installation with a clear warning. **Workaround used:** Manually edited `/mnt/usr/share/omarchy/install/hardware/nvidia.sh` and added `exit 0` at the top, then resumed the install with `omarchy-apply-system`. Happy to provide full logs or test any proposed fix.
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 08:32 UTC