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.
Bug Report: High CPU usage by `[nvidia-modeset/kthread_q]` on Razer Blade Pro 17 (Omarchy Linux)
Reported by 42kiko · filed Oct 18, 2025Closed upstream on 2025-10-25 by ryanrhughes. 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
NVIDIA 580.95.05-1
What's wrong?
Summary:
After running Omarchy Linux (Arch-based) with NVIDIA drivers on my Razer Blade Pro 17 (RTX 3080, Intel i7 10th Gen), I consistently encounter extremely high CPU usage (~99%) caused by the kernel thread [nvidia-modeset/kthread_q]. The issue appears to be related to the nvidia_drm module when Kernel Modesetting (KMS) is enabled (modeset=1).
🧠 System Information
- Device: Razer Blade Pro 17 (2021)
- GPU: NVIDIA GeForce RTX 3080 Laptop GPU
- CPU: Intel Core i7-10875H
- RAM: 32 GB DDR4
- OS: Omarchy Linux (Arch-based, Wayland/Hyprland session)
- Kernel: 6.17.2-arch1-1
- NVIDIA driver version: 580.95.05-1
- Display server: Wayland (Hyprland)
- Desktop environment: None, pure compositor setup
⚙️ Steps to Reproduce
- Boot into Omarchy Linux with
nvidia_drm.modeset=1enabled. - Run Hyprland or any Wayland session.
- Observe system performance using
toporhtop. - The kernel thread
[nvidia-modeset/kthread_q]consumes ~99% CPU constantly.
🧩 Expected Behavior
The NVIDIA kernel threads should remain idle under normal display operation, with CPU usage close to 0%, as seen in other Arch distributions.
🔥 Actual Behavior
[nvidia-modeset/kthread_q]process spikes to 99–100% CPU usage.- GPU functions normally, but power consumption and heat increase drastically.
- Issue persists even after restarting the display manager or compositor.
🔍 Diagnostics
Command output:
ps -p 240 -o pid,ppid,cmd,%cpu,%mem,etime
PID PPID CMD %CPU %MEM ELAPSED
240 2 [nvidia-modeset/kthread_q] 99.3 0.0 02:04:07dmesg (excerpt):
nvidia-modeset: WARNING: GPU:0: multiple event queue timeouts detected
nvidia: module verification failed: signature and/or required key missing🧠 Workarounds Tried
- Setting
options nvidia_drm modeset=0(resolves CPU issue but breaks Wayland/KMS) - Reinstalling NVIDIA and nvidia-utils packages
- Using
sudo rmmod nvidia_drm nvidia_modeset nvidia→ reload → same issue after reboot - Verified kernel version and DKMS rebuild
- Tested with both Xorg and Hyprland — only Wayland+KMS affected
💬 Request
Please investigate possible driver or module interaction issues in the Omarchy build with the current NVIDIA drivers.
A potential fix might involve adjusting the module load order or disabling a conflicting KMS flag in the initramfs.
It would be great if this could be addressed in a future Omarchy update, as this issue severely impacts battery life and thermals on NVIDIA laptops.
Thank you for your incredible work on Omarchy — it’s a fantastic distribution, and I’d be very happy to help test a patched build if needed.
Best regards,
42kiko
View raw text
### System details
NVIDIA 580.95.05-1
### What's wrong?
**Summary:**
After running Omarchy Linux (Arch-based) with NVIDIA drivers on my Razer Blade Pro 17 (RTX 3080, Intel i7 10th Gen), I consistently encounter extremely high CPU usage (~99%) caused by the kernel thread `[nvidia-modeset/kthread_q]`. The issue appears to be related to the `nvidia_drm` module when Kernel Modesetting (KMS) is enabled (`modeset=1`).
---
### 🧠 **System Information**
* **Device:** Razer Blade Pro 17 (2021)
* **GPU:** NVIDIA GeForce RTX 3080 Laptop GPU
* **CPU:** Intel Core i7-10875H
* **RAM:** 32 GB DDR4
* **OS:** Omarchy Linux (Arch-based, Wayland/Hyprland session)
* **Kernel:** 6.17.2-arch1-1
* **NVIDIA driver version:** 580.95.05-1
* **Display server:** Wayland (Hyprland)
* **Desktop environment:** None, pure compositor setup
---
### ⚙️ **Steps to Reproduce**
1. Boot into Omarchy Linux with `nvidia_drm.modeset=1` enabled.
2. Run Hyprland or any Wayland session.
3. Observe system performance using `top` or `htop`.
4. The kernel thread `[nvidia-modeset/kthread_q]` consumes **~99% CPU constantly**.
---
### 🧩 **Expected Behavior**
The NVIDIA kernel threads should remain idle under normal display operation, with CPU usage close to 0%, as seen in other Arch distributions.
---
### 🔥 **Actual Behavior**
* `[nvidia-modeset/kthread_q]` process spikes to 99–100% CPU usage.
* GPU functions normally, but power consumption and heat increase drastically.
* Issue persists even after restarting the display manager or compositor.
---
### 🔍 **Diagnostics**
**Command output:**
```bash
ps -p 240 -o pid,ppid,cmd,%cpu,%mem,etime
PID PPID CMD %CPU %MEM ELAPSED
240 2 [nvidia-modeset/kthread_q] 99.3 0.0 02:04:07
```
**dmesg (excerpt):**
```
nvidia-modeset: WARNING: GPU:0: multiple event queue timeouts detected
nvidia: module verification failed: signature and/or required key missing
```
---
### 🧠 **Workarounds Tried**
* Setting `options nvidia_drm modeset=0` (resolves CPU issue but breaks Wayland/KMS)
* Reinstalling NVIDIA and nvidia-utils packages
* Using `sudo rmmod nvidia_drm nvidia_modeset nvidia` → reload → same issue after reboot
* Verified kernel version and DKMS rebuild
* Tested with both Xorg and Hyprland — only Wayland+KMS affected
---
### 💬 **Request**
Please investigate possible driver or module interaction issues in the Omarchy build with the current NVIDIA drivers.
A potential fix might involve adjusting the module load order or disabling a conflicting KMS flag in the initramfs.
It would be great if this could be addressed in a future Omarchy update, as this issue severely impacts battery life and thermals on NVIDIA laptops.
Thank you for your incredible work on Omarchy — it’s a fantastic distribution, and I’d be very happy to help test a patched build if needed.
---
**Best regards,**
**42kiko**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.