Discussion:
i3status core temps path changes every reboot
(too old to reply)
Andreas Radke
2016-07-02 08:20:42 UTC
Permalink
I'm reading coretemp from an Intel core i7 2600k quad core cpu using
this:

cpu_temperature 0 {
format = "%degrees°C"
# grep "" /sys/devices/platform/coretemp.?/hwmon/hwmon?/temp?_label
# path = "/sys/devices/platform/coretemp.0/hwmon/hwmon2/temp1_input"
path = "/sys/devices/platform/coretemp.0/hwmon/hwmon3/temp1_input"
}

That "hwmonX" variabe is randomly different on every reboot (1,2,3).

Is there any way to read the temp directly from the kernel from a fixed path
other than using lm_sensors?

Kernel is 4.4.x LTS or 4.x.x main tree.

-Andy
Michael Stapelberg
2016-07-05 06:34:56 UTC
Permalink
The recommended solution for your issue is to have some custom logic (e.g.
in a shell script, or program in your favorite programming language) which
determines the correct path and then modifies your i3status.conf
accordingly.

As a side note, we’ve realized after the fact that the CPU temperature
module isn’t a good fit for i3status’s philosophy (the temperature of your
CPU is an implementation detail, and for stress-testing a new cooling setup
there are much better tools), and that we shouldn’t have added it in the
first place. Therefore, please don’t send any pull requests regarding
changes in the CPU temperature module :).
Post by Andreas Radke
I'm reading coretemp from an Intel core i7 2600k quad core cpu using
cpu_temperature 0 {
format = "%degrees°C"
# grep "" /sys/devices/platform/coretemp.?/hwmon/hwmon?/temp?_label
# path = "/sys/devices/platform/coretemp.0/hwmon/hwmon2/temp1_input"
path = "/sys/devices/platform/coretemp.0/hwmon/hwmon3/temp1_input"
}
That "hwmonX" variabe is randomly different on every reboot (1,2,3).
Is there any way to read the temp directly from the kernel from a fixed path
other than using lm_sensors?
Kernel is 4.4.x LTS or 4.x.x main tree.
-Andy
--
Best regards,
Michael
Loading...