OpenHardwareOS v0.1.5 — 读数可核对

OpenHardwareOS v0.1.5 makes the Linux preview's readings checkable against the machine itself, and fixes a desktop control that could lose what you typed. Existing v0.1.0 – v0.1.4 tags and downloads remain available.

Changes

Readings you can check, not take on trust

• ohm-cli status --json and ohm-cli doctor --json print one JSON object and nothing else: every provider with its status and reason, every device with its readings, and the reason for each reading that is missing. It is the same snapshot the desktop renders from, so the two cannot disagree about what the runtime reported.
• scripts/verify-linux-readings.sh compares each reading with the platform's own answer on the same host and prints one line per reading: AGREE, DIFFER (exit code 1), NO-SOURCE (with the reason), NOT-CHECKED (no independent source exists). Memory against /proc/meminfo, fan tachometers and PWM against the very hwmon file the reading came from, temperatures against the range the platform reports, free space against df for the same mount point.
• The install page gained a section you can run yourself: which system file or command corresponds to each reading, and what a mismatch would mean. It says plainly that "this machine has no fan speed to read" is a normal outcome — and that cpu.load and cpu.frequency cannot be checked from a single sample, rather than pretending otherwise.
• The check runs in CI and in the release pipeline on a real kernel. On ubuntu-latest in this release: memory.total equals /proc/meminfo exactly, three mount points agree with df to 0/0/16384 bytes, the temperature reading sits inside the platform's own range, and the hwmon line reports NO-SOURCE because that runner has no fan driver.

The duty field no longer loses an uncommitted value

A refresh can unmount and re-mount a control — the device dropping out of one snapshot and coming back in the next, which a discovery cycle, a disable or a blip can do. The value being typed lived inside that control, so the edit died with it and the field came back showing the device's own duty; clicking Apply then wrote the device's old value. It happened in two consecutive release builds before the assertion was made to say what the field actually contained. The draft now lives on the screen and the field is derived from it (your edit ?? the reading), so re-creating the control changes nothing.

Install

• Windows: PowerShell instructions for this version
• Linux: CLI, Debian package and AppImage instructions

The Windows desktop installer and the optional PowerShell script are unsigned, and so are the Linux packages. LibreHardwareMonitor is a separate prerequisite for supported motherboard channels on Windows and is not bundled.