Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
CPU temperature stuff for cpufreqd, from the Debian forum
Posted 09-17-2019 at 12:03 PM by the dsc
Just to compile my "findings" here
Right now I've just added the "coretemp-isa" section to the default sensors3.conf. Maybe cpufreqd is getting something else from there, besides temperature.
Quote:
http://forums.debian.net/viewtopic.php?f=5&t=71723
[...]
[SOLVED] - it turns out that the driver I thought I needed to use, it8718, was only one of the drivers detected by sensors-detect (or detect-sensors, whatever), other one I've missed was actually called just "coretemp". I thought it was a label, not an actual driver. My sensors.conf hadn't a section for such driver though. I've googled a little bit and found a sensors.conf or /etc/sensors.d/custom-conf example file at the arch linux forums. Based on that I've made my /etc/sensors.d/cores.conf, and I've pointed the "sensors plugin" section on cpufreqd.conf directly to it. The file is just this:
I've skipped the numbers 0 and 1 for the labels because there's still this acpitz-whatever bogus reading that is labelled temp1. I don't know how to get rid of it, so I just started from 2. And it seems that these labels can't be totally arbitrary, I've tried "core0" and "core1", but the sensors_get part of the cpufreqd output wouldn't appear. It's so weird that it has to be labelled "temp#" that I think I may have forgot to make the correspondent changes in cpufreqd.conf, but I'm almost sure I did. I could have just failed to find "sensors_get" amidst all that output though.
On cpufreqd.conf the syntax is:
sensor=sensorlabel:##-###
in actual terms:
sensor=temp2:55-70
[...]
[SOLVED] - it turns out that the driver I thought I needed to use, it8718, was only one of the drivers detected by sensors-detect (or detect-sensors, whatever), other one I've missed was actually called just "coretemp". I thought it was a label, not an actual driver. My sensors.conf hadn't a section for such driver though. I've googled a little bit and found a sensors.conf or /etc/sensors.d/custom-conf example file at the arch linux forums. Based on that I've made my /etc/sensors.d/cores.conf, and I've pointed the "sensors plugin" section on cpufreqd.conf directly to it. The file is just this:
Code:
chip "coretemp-isa-0000" label temp2 "Core 0" label temp3 "Core 1"
On cpufreqd.conf the syntax is:
sensor=sensorlabel:##-###
in actual terms:
sensor=temp2:55-70
Total Comments 0
