![]() ![]() Select a temperature that matches your CPU temp (usually the same number as the fan number, but check and double check!). ![]() Now press 5 to look at the configuration file. Let the script run until you see "Select fan output to configure, or other action:" (all default options are fine, you can basically enter you way through the script). I set the interval to 5 seconds, just to be safe, but 10 should be fine too. ![]() Pwmconfig will write a config file in /etc. One by one, all fans will be tested for 'speedcontrol' (Pulse Width Modulation, actually). You just turned the if/else around! Now pwmconfig should work. $ sudo cp /usr/sbin/pwmconfig /usr/sbin/pwmconfig_originalĪnd go to line 68. Well, maybe a lot of this questions a notes are trivial, for the ones that knows the answer, write and explain this in the docs I think can helps a lot to understand how the program works, how to use it and get the best result./usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed When we try to se a MINSTOP less than MINPWD there is a error that says it must be higher, but, MINSTOP is speed, MINPWD energy, so why MINSTOP must be higher? we are comparing apple with oranges.ĪVERAGE: We can read an average of n readings of data, but., how is razonable here? how mane reading we get per second?, without a dimension we can't know if is 2, 50, or 1000.Ībout algorithm: FCTEMPS and FCFANS talk about recording data to fancontrol can works with it, but this does not means the algorithm will only affect the pwd based in the relation, actually I don't have very clear how the algorithm works. MINSTOP/MINSTART: How can we know the safe values? even if is checking the manual tell plis, there can be a lot of times we can't know this value, there ideally tell safe values we can use or some way to set it. No idea the behavior of this line, but I think is great can know if we can or we can't do this, I think the best would be analyze with data instead set this manually. =hwmon2/pwm1=hwmon0/temp1_input hwmon2/pwm1=hwmon0/temp2_input This I thing, can be recorded in a 3d table with fans/temp/pwd, and deduce from the data the relations instead write them manually.Ĭan we set more than 1 pair? like a relation between pwm1 and two inputs? PWD: Not defined, I know is about how motors works, with pulses, but at least a link and a brief description can helps to understand.įCTEMPS/FCFANS: Oks, pairs of PWD with fan speed and temp, the major point here, how can we know what temp belongs to what fans? I'm working with a PC with 2 CPUs, obvs there is at least 2 fans, so there is 4 vars, temp1, temp2, fan1, fan2, set the pairs arbitrary is not really good or easy to know what cpu is what. In the last steps, when we choose if config a fan or save and exit, I know literally the text says Select fan output to configure, or other action:, is just after all the tests and previuous runs we don't know, if we have "optional" configs or they are mandatory, this happens to me too, we just click to save and the config file is empty, maybe change it to: Step to collect data of fans completed, now step to configure the fans, or in case a fan is not configured or the config file is empty, put a warning and a way to go an step back to configure it. Pwmconfig last step to write and set eh config file, seems common: Particularly the last table is great, helps a lot to understand concepts. The best doc I found to describe, not the procedure of installation with pwmconfig is: Hi all, I think would be great have better doc about fancontrol, the program is great, but the lack of doc really do this things hard, I want take advantage of this, I'm starting trying to use it, so I want to write what is hard to understand. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |