Community Solution

ZimaOS Shows 0°C or 0W on AMD: Sensor Checks First

An AMD A6-5200 user reported that CPU temperature fell to 0°C after ZimaOS 1.5.1 while power detection had long shown 0W.

The thread does not prove that the AMD A6-5200 hardware sensor was broken. The user said temperature worked on ZimaOS 1.5.0 and stopped after upgrading to 1.5.1, which makes a kernel/driver or monitoring-backend regression plausible.

The explanation about a newer kernel dropping the required sensor path came from another community member, not from IceWhale engineering, so it should remain a hypothesis rather than an official diagnosis.

What Changed Between 1.5.0 and 1.5.1

ZimaOS dashboard showing CPU temperature at zero degrees Celsius
After the 1.5.1 update, the AMD A6-5200 system showed 0°C in the dashboard while CPU usage and RAM still displayed. Source: IceWhale Community Forum.

The user reported two metrics: CPU temperature became 0°C after the update, while power had already remained at 0W in older builds. Those may be separate sensor limitations.

Check the Sensor Layer Outside the Dashboard

Use terminal tools such as sensors or the relevant /sys/class/hwmon entries to see whether Linux itself exposes the temperature. If command-line sensor data is correct but the dashboard is 0, the UI/backend parser is the more likely fault.

A 2026 community report on another AMD system also noted that AMD package power is not exposed through the same Intel RAPL path and may require different hwmon support. A related AMD sensor discussion shows IceWhale was tracking similar AMD telemetry gaps. That reinforces the need to distinguish temperature from power measurement.

Do Not Install Random Kernel Drivers on an Appliance NAS

The original user was correctly cautious about injecting an incompatible sensor driver into a storage server. ZimaOS is not intended to be modified like a general-purpose Debian host.

The NAS power guide is useful when you need reliable power numbers rather than UI telemetry.

Compare Current ZimaOS Before Rolling Back

The report is tied to 1.5.1. Current ZimaOS is much newer, so reproduce the sensor issue on the current stable release before treating the old regression as permanent.

For hardware temperature safety, BIOS/hardware-monitor readings and a direct sensor tool are better validation sources than one dashboard widget.

Bottom Line

The source thread supports “a regression may have occurred after 1.5.1,” not “the AMD A6-5200 is unsupported.” Check whether the kernel still exposes the sensor, separate temperature from power telemetry, and avoid manual driver injection unless IceWhale documents it for your exact platform.