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.
Bundle nct6687d-dkms so MSI Nuvoton NCT6687-R boards have working hwmon
Reported by GekkeTovie · filed May 12, 2026Closed upstream on 2026-05-15. 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
What do you need?
On AM4/AM5 motherboards using the Nuvoton NCT6687D-R Super-I/O chip (very common across the MSI X570 / B550 / X670 / B650 lineup), the mainline Linux kernel doesn't ship a driver. Without the out-of-tree `nct6687d` module, lm_sensors, fancontrol, CoolerControl, and DMS's hardware widgets see no motherboard temps and no fan RPMs — so users get a working desktop but no way to monitor or control case/CPU fans.
This isn't a request for fan-control logic (BIOS handles that fine). It's a request for the kernel module that makes the existing hwmon stack actually report anything on these boards.
Current state on a fresh Omarchy install (MSI AM5, NCT6687D-R detected)
coolercontrold: Nuvoton NCT6687D-R eSIO (driver: nct6687, status: failed:
modprobe: FATAL: Module nct6687 not found in directory /lib/modules/<kernel>)/sys/class/hwmon/ only shows nvme, amdgpu, k10temp — nothing from the motherboard.
Suggested options
- Bundle `nct6687d-dkms-git` as part of the default install (and pull in
dkms+ matchinglinux-headers). Pro: zero-config for affected users. Con: adds DKMS overhead for everyone. - Optional setup step —
omarchy install hardware msi-sensors(or similar), parallel to other hardware-specific helpers. Pro: opt-in, no overhead for non-MSI users. Probably the right fit for Omarchy's philosophy. - Documentation only — a note in setup/troubleshooting that points users at
nct6687d-dkms-git. Lower-effort, but most users won't know to look.
Option 2 feels closest to how Omarchy already handles omarchy install extras.
Why this is different from prior closed fan-control issues (#1677, #2207, #2719)
Those asked Omarchy to implement fan control across diverse hardware. This is narrower: just shipping the kernel driver that makes a single, very common Super-I/O chip readable. Once the module is loaded, the user picks whichever userspace tool they want (CoolerControl, fancontrol, plain sensors) — Omarchy doesn't take on any fan-control opinion.
Hardware reference
- Affected chip: Nuvoton NCT6687D-R (eSIO)
- Driver project: https://github.com/Fred78290/nct6687d
- AUR package:
nct6687d-dkms-git - Motherboards typically affected: MSI B550/X570/B650/X670 and several PRO/MAG/MEG variants
View raw text
### What do you need?
On AM4/AM5 motherboards using the **Nuvoton NCT6687D-R** Super-I/O chip (very common across the MSI X570 / B550 / X670 / B650 lineup), the mainline Linux kernel doesn't ship a driver. Without the out-of-tree [`nct6687d`](https://github.com/Fred78290/nct6687d) module, `lm_sensors`, `fancontrol`, CoolerControl, and DMS's hardware widgets see no motherboard temps and no fan RPMs — so users get a working desktop but no way to monitor or control case/CPU fans.
This isn't a request for fan-control *logic* (BIOS handles that fine). It's a request for the **kernel module** that makes the existing hwmon stack actually report anything on these boards.
### Current state on a fresh Omarchy install (MSI AM5, NCT6687D-R detected)
```
coolercontrold: Nuvoton NCT6687D-R eSIO (driver: nct6687, status: failed:
modprobe: FATAL: Module nct6687 not found in directory /lib/modules/<kernel>)
```
`/sys/class/hwmon/` only shows `nvme`, `amdgpu`, `k10temp` — nothing from the motherboard.
### Suggested options
1. **Bundle `nct6687d-dkms-git` as part of the default install** (and pull in `dkms` + matching `linux-headers`). Pro: zero-config for affected users. Con: adds DKMS overhead for everyone.
2. **Optional setup step** — `omarchy install hardware msi-sensors` (or similar), parallel to other hardware-specific helpers. Pro: opt-in, no overhead for non-MSI users. Probably the right fit for Omarchy's philosophy.
3. **Documentation only** — a note in setup/troubleshooting that points users at `nct6687d-dkms-git`. Lower-effort, but most users won't know to look.
Option 2 feels closest to how Omarchy already handles `omarchy install` extras.
### Why this is different from prior closed fan-control issues (#1677, #2207, #2719)
Those asked Omarchy to *implement* fan control across diverse hardware. This is narrower: just shipping the kernel driver that makes a single, very common Super-I/O chip readable. Once the module is loaded, the *user* picks whichever userspace tool they want (CoolerControl, fancontrol, plain `sensors`) — Omarchy doesn't take on any fan-control opinion.
### Hardware reference
- Affected chip: Nuvoton NCT6687D-R (eSIO)
- Driver project: https://github.com/Fred78290/nct6687d
- AUR package: `nct6687d-dkms-git`
- Motherboards typically affected: MSI B550/X570/B650/X670 and several PRO/MAG/MEG variantsValidation
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.