Closed Andrei-Pozolotin closed 8 years ago
/etc/thinkfan.conf
# module: thermal
hwmon /sys/class/thermal/thermal_zone0/temp
# module: x86_pkg_temp_thermal
hwmon /sys/class/thermal/thermal_zone1/temp
# module: thinkpad_acpi
tp_fan /proc/acpi/ibm/fan
# mapping
(0, 0, 45) # 0
(1, 40, 55) # 1900
(2, 50, 60) #
(3, 53, 63) #
(4, 55, 65) #
(5, 60, 70) #
(6, 63, 73) #
(7, 67, 77) # 3600
#(127, 75, 32767) # 5000 # out of range
BTW, config entry
(127, 75, 32767) # 5000 # unlimited rpm
used to work fine before v 1.0, now it reports as invalid value; how can I restore original behavior?
thank you.
Thanks for reporting. Apparently level 127
used to be handled specially in 0.9. Now it's just written to /proc/acpi/ibm/fan
, which is of course invalid.
Workaround: use "level full-speed"
instead of 127
(including the double quotes).
I confirm that full speed entry works:
("level full-speed", 75, 32767) # 5000 rpm
BTW, is it too hard to add RPM logging to current format:
thinkfan[20051]: Temperatures(bias): 49(0), 49(0) -> level 1
for example:
thinkfan[20051]: Temperatures(bias): 49(0), 49(0) -> level 1 [rpm=2345]
?
or even expose log format string in thinkfan.conf
?
with a dozen or so available state variables?
:-)
Well, that would be a nice feature indeed. However there are two caveats:
thank you for considering this. re: 1) "will always take a bunch of seconds" - no need to be exact, current or average is fine re: 2) "migrate to an existing, clean grammar (like YAML) " - yes, please switch to yaml
Alright, tracking the YAML topic as issue #15 now.
The segfault reported in the initial comment is actually the same as in issue #18, which is fixed now, too. So this bug is also done.
package:
system:
journal: