i know it’s old but i found a ITX Mini-PC and installed x64 Image. It is equiped with 4 NICs, 4 GB RAM and CF and SATA Port with Intel Atom 525 1,8 GHz.
It has more RAM and hopefully more performance for Pihole, Open/PiVPN and Nextcloud then my RPI3.
I also want to use 2 NICs for routing between my internal and my guest-wifi net for managing house-automation.
After installing the (very old 6.x IMG, please refresh that), the first thing I saw is, that the temperature is not read correctly so i think powermanagement features won’t work too.
Did some googling…this might help or point you in the right direction (if maybe you want to respin the latest .iso to run more cleanly on ATOM processors)
If you mean the temperature shown in the DietPi-Banner, this has no influence on power management or anything like that, it just read the temperature from a known list of sysfs files, and since every board has the CPU temperature on a different file, there are some cases where the wrong is picket.
To check the usually available sysfs temperature files and their content, please run:
for i in /sys/class/thermal/thermal_zone[0-9]/temp /sys/class/hwmon/hwmon[0-9]/temp[0-9]_input /sys/devices/platform/coretemp.[0-9]/hwmon/hwmon[0-9]/temp[0-9]_input
do
[[ -e $i ]] && echo "$i : $(<$i)"
done
If powermanagement is not affected, everything is fine. I will ignore the “freezer” warnings
I have to find out a temp offset for myself and it will be fine.
Don’t want a melting fanless case in my basement.
Okay those temperatures all do not seem to be the real CPU temperature. Not sure what those 2/3 temps refer to, as I guess ambient temperature is way above 15/16 degree Celsius?
It more looks like static values that never change, like there was no sensor.
Can you also check:
ls -l /sys/devices/virtual/thermal
ls -l /sys/class/thermal
ls -l /sys/class/hwmon
WarHawk
Why would lm-sensors not work?
apt install lm-sensors
sensors
The CPU temperature should usually be available without any additional tool, but worth to give it a shot when we cannot find any functional sysfs file for that.
EDIT: Ah, a way to possibly check which sysfs temperature means what:
for i in /sys/class/thermal/thermal_zone[0-9]/type /sys/class/hwmon/hwmon[0-9]/name /sys/devices/platform/coretemp.[0-9]/hwmon/hwmon[0-9]/name
do
[[ -e $i ]] && echo "$i : $(<$i)"
done
Sorry for the late reply.
Those temperatures aren’t static values.
The values rise from 0 and that is even to low for the basement.
In fact there are about 20°C
dietpi@DietPi:~$ ls -l /sys/devices/virtual/thermal
total 0
drwxr-xr-x 4 root root 0 Jun 20 14:54 cooling_device0
drwxr-xr-x 4 root root 0 Jun 20 14:54 cooling_device1
drwxr-xr-x 4 root root 0 Jun 20 14:54 cooling_device2
drwxr-xr-x 4 root root 0 Jun 20 14:54 cooling_device3
drwxr-xr-x 4 root root 0 Jun 20 14:54 cooling_device4
drwxr-xr-x 4 root root 0 Jun 20 14:54 thermal_zone0
dietpi@DietPi:~$ ls -l /sys/class/thermal
total 0
lrwxrwxrwx 1 root root 0 Jun 20 14:54 cooling_device0 -> ../../devices/virtual/thermal/cooling_device0
lrwxrwxrwx 1 root root 0 Jun 20 14:54 cooling_device1 -> ../../devices/virtual/thermal/cooling_device1
lrwxrwxrwx 1 root root 0 Jun 20 14:54 cooling_device2 -> ../../devices/virtual/thermal/cooling_device2
lrwxrwxrwx 1 root root 0 Jun 20 14:54 cooling_device3 -> ../../devices/virtual/thermal/cooling_device3
lrwxrwxrwx 1 root root 0 Jun 19 23:03 cooling_device4 -> ../../devices/virtual/thermal/cooling_device4
lrwxrwxrwx 1 root root 0 Jun 19 23:03 thermal_zone0 -> ../../devices/virtual/thermal/thermal_zone0
dietpi@DietPi:~$ ls -l /sys/class/hwmon
total 0
lrwxrwxrwx 1 root root 0 Jun 19 23:03 hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
lrwxrwxrwx 1 root root 0 Jun 25 21:49 hwmon1 -> ../../devices/platform/coretemp.0/hwmon/hwmon1
and everything else is only symlinks to those, which is pretty normal.
Also lm-sensors detects these three, matching the device names as well. The first is a generic ACPI thermal zone sensor, which is usually interpreted as CPU or nearby CPU temperature. The other two are identified and named as individual CPU core temperatures. But all of them do not show values anywhere expected. I’m afraid then there is nothing we can do about it, script-wise.
What you can try is:
Upgrade the systems BIOS/firmware, if updates are available.
Upgrade the kernel to buster-backports Linux 5.10:
