Hi David, On Thu, 21 Oct 2010 11:05:39 -0700, David Mathog wrote: > Hi Jean, > > > Did you run "sensors -s"? > > > > Do you have any "set fan#_div" statement in this chip section? If you > > do, it is important that these come before the "set fan#_min" > > statements. > > Set up the fan related lines in the two sensors3.conf blocks like this: > > chip "w83782d-*" > label fan1 "Ch Fan 1" > label fan2 "Ch Fan 2" > label fan3 "Ch Fan 3" > set fan1_div 4 > set fan2_div 4 > set fan3_div 4 > set fan1_min 3000 > set fan2_min 3000 > set fan3_min 3000 > chip "w83627hf-*" > label fan1 "CPU1 Fan" > label fan2 "CPU0 Fan" > ignore fan3 > compute fan1 2*@,@/2 > compute fan2 2*@,@/2 > set fan1_div 4 > set fan2_div 4 > set fan1_min 3000 > set fan2_min 3000 > > % sensors -s > % sensors | grep RPM > CPU1 Fan: 0 RPM (min = 3000 RPM, div = 4) ALARM > CPU0 Fan: 6552 RPM (min = 3000 RPM, div = 4) > Ch Fan 1: 0 RPM (min = 2986 RPM, div = 4) ALARM > Ch Fan 2: 4500 RPM (min = 2986 RPM, div = 4) > Ch Fan 3: 4383 RPM (min = 2986 RPM, div = 4) > > which is fine. Note: you can set the limit to 0 if you want to disable the ALARM flag for missing fans. > Tried different dividers (2,4,8,16) and the values moved around a > little, but these were always within a few percent of 3000, so > arbitrarily used a divisor of 4 everywhere. You probably want to read: http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/fan-divisors For the w83782d, as you are setting fan_min to 3000, you probably want to go with fan_div = 2, as it will yield a better accuracy at 4000-7000 RPM than fan_div = 4. For the w836727hf, fan_div = 4 is fine (due to the compute statements, fan_div = 2 would prevent you from setting limits below ~5300 RPM.) -- Jean Delvare http://khali.linux-fr.org/wishlist.html _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
