Closed okanisis closed 7 years ago
Looks like maybe it has something to do with the % symbol seen in the output of cat.
The other temp links don't have it:
% cat /tmp/asus-fan-shm/gfx_temp
37000%
cat /tmp/asus-fan-shm/core1_temp
32000
% cat /tmp/asus-fan-shm/core2_temp
33000
% cat /tmp/asus-fan-shm/die_temp
39000
% cat /tmp/asus-fan-shm/tz1_temp
38000
% cat /tmp/asus-fan-shm/tz2_temp
38000
Fans can be manually controlled with:
$ echo 1 > fan_{cpu,gfx}_manual_mode
$ echo 20 > fan_{cpu,gfx}_speed
$ echo 255 > fan_{cpu,gfx}_speed
mmmh for me there is no "%" at the end of gfx_temp, can you confirm that this problem still exists?
Just re-installed with kernel 4.9.6 and the % is still in the gfx_temp file.
you might try a recent git build, applied a rather dirty hack to work around your problem ...
Looks like the same issue is still there. Running linux 4.9.9 on Arch Linux and built latest asus-fan (v0.9.1.r49.gb8a358f)
fancontrol is running successfully now after updating to latest kernel 4.10.8-1 on arch linux, and asus-fan is v0.9.1.r51.g5517472
Fancontrol is failing to start because it can't read the value for gfx_temp even though the asus_fan module is loaded and fresh links created with the asus-fan-create-symlinks.sh script.
gfx_temp has a value, that looks like it should work...:
And sensors at first glance has a readable output showing the asus_fan module has loaded correctly, but after a minute or two and checking sensors again the GFX Fa value shows -1 RPM!:
This is on Arch Linux kernel 4.8.12
Tried reloading the asus_fan module with modprobe and then recreating the links with asus-fan-create-symlinks.sh but that results in the same behaviour as above.