setfans=[,][,mode] Set fans boost level (0..100 - in percent) with selected mode
Thus there are THREE options, with the first being mandatory and the second two optional. I run the following command, which I HOPE (see below on undertainties with documentation) will set fan 3 (my 4th fan) to a manual speed of 100% of it's maxrpm:
alienfan-cli setfans=100,3,0
I get the following response:
AlienFan-CLI v8.5.1
Supported hardware (4800) detected, 4 fans, 2 sensors, 7 power states.
setfans: Incorrect arguments count (AT LEAST 4 NEEDED)
note, the emphasis is mine
Per the documentation therer are only THREE listed options. What am I missing/doing wrong - or is this a bug?
ADDITIONALLY: I am uncertain about what the first two options are supposed to represent. I assume that one of the two is the BOOST level and the other is the optional ID of the fan you want boosted. But I have no idea which. I am also uncertain what will happen if NO mode is provided. I suggest the following help change:
setfans=[,][,mode] Set fans boost level (0..100 - in percent), for all fans(??) - or the optionally provided fanN, for all modes(??) - or the optionally provided mode.
As an aside, I was trying to do this because AlienFan Control has yet again decided to completely stop responding to any temperature changes and is leaving all fan speeds at a low and unchanging value despite the cpu/gpu and entire computer temperatures continuing to rise unchecked. And this time it happened while under normal operations, not while coming out from a Sleep state (which seemed to be the only cause of this the multiple other times it has happened to me). I had 8.5.0 when I first noted this, so after a reboot (which failed to correct the broken state of fan control) I updated to the latest 8.5.1 build. No change after that installation. I note that I did not restart the computer after the install, and will try that now and report back.
I really hope you can come up with a cause for this and build a box around it. Or failing that at least come up with a way to detect this issue (which is trivial by simply tracking temps and fan speeds over time). Once detection is made figure out how to either return the system to a functional fan control with AFC active, or with AFC disabled.
Help for the setfans option is as follows:
setfans=[,][,mode] Set fans boost level (0..100 - in percent) with selected mode
Thus there are THREE options, with the first being mandatory and the second two optional. I run the following command, which I HOPE (see below on undertainties with documentation) will set fan 3 (my 4th fan) to a manual speed of 100% of it's maxrpm:
alienfan-cli setfans=100,3,0
I get the following response:
AlienFan-CLI v8.5.1 Supported hardware (4800) detected, 4 fans, 2 sensors, 7 power states. setfans: Incorrect arguments count (AT LEAST 4 NEEDED)
note, the emphasis is mine
Per the documentation therer are only THREE listed options. What am I missing/doing wrong - or is this a bug?
ADDITIONALLY: I am uncertain about what the first two options are supposed to represent. I assume that one of the two is the BOOST level and the other is the optional ID of the fan you want boosted. But I have no idea which. I am also uncertain what will happen if NO mode is provided. I suggest the following help change:
setfans=[,][,mode] Set fans boost level (0..100 - in percent), for all fans(??) - or the optionally provided fanN, for all modes(??) - or the optionally provided mode.
As an aside, I was trying to do this because AlienFan Control has yet again decided to completely stop responding to any temperature changes and is leaving all fan speeds at a low and unchanging value despite the cpu/gpu and entire computer temperatures continuing to rise unchecked. And this time it happened while under normal operations, not while coming out from a Sleep state (which seemed to be the only cause of this the multiple other times it has happened to me). I had 8.5.0 when I first noted this, so after a reboot (which failed to correct the broken state of fan control) I updated to the latest 8.5.1 build. No change after that installation. I note that I did not restart the computer after the install, and will try that now and report back.
I really hope you can come up with a cause for this and build a box around it. Or failing that at least come up with a way to detect this issue (which is trivial by simply tracking temps and fan speeds over time). Once detection is made figure out how to either return the system to a functional fan control with AFC active, or with AFC disabled.