Hi there,
I have just installed dietpi and updated to 6.16, but I have noticed that my C2 is running significantly hotter (52-64C) then on armbian (42-50C). Iis it something that I am missing from the setting (I am on ondemand without any changes).
Cheers
Can you verify that the ARM is correctly clocking down when on idle, e.g. by using “cpu” command?
We had some kernel setting on RPi in the past that should only push full clocks for 20 seconds on boot, but this prevented clocking down afterwards as well, at least on the current RPi firmware that time.
Perhaps there is some similar issue on Odroid C2.
But also check for e.g. hang processes via “htop”.
Cpu command is giving me max speed only 1536MHz, I have never seen the lower clock, so might be it.
Mine runs at 51c while at 500mhz conservative
While idle using ondemand I’m at 52C, if it does anything ‘play music’ its at about 54c
So yeah it seems to be quite warm, when I’m using now armbian is at 43-52C max with a few tasks open like music, streaming. So it definitely something here. On diepi my seems to never go do to lower clock (I tried to switch on conservative temp were the same). Question is why is it not going down with clock when not in use?
Hi,
The DietPi cpu script, will cause a spike in CPU usage due to the processing require to run the script.
To check the current CPU frequency, please use:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
The above is in Hz.
When idle, my system is 250/500MHz:
root@DietPi:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
250000
root@DietPi:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
500000
CPU temps are 41’c idle.
Ideally check htop to see which program is using the most CPU.
If problems persist, when idle, it could be either one of: