On Fri, Jan 27, 2012 at 6:34 PM, CC <ccomren@xxxxxxxxx> wrote:
> On Fri, Jan 27, 2012 at 5:54 PM, CC <ccomren@xxxxxxxxx> wrote:
>> On Fri, Jan 27, 2012 at 3:54 PM, Guenter Roeck
>> <guenter.roeck@xxxxxxxxxxxx> wrote:
>>> Forwarding to lm-sensors to keep the group in the loop.
>>>
>>> ----- Forwarded message from ccom <reply+i-2970830-11e203ec4162e4680a3e2c999f2bba9b513a1927-1030448@xxxxxxxxxxxxxxxx> -----
>>>
>>> Date: Fri, 27 Jan 2012 09:29:45 -0500
>>> From: ccom <reply+i-2970830-11e203ec4162e4680a3e2c999f2bba9b513a1927-1030448@xxxxxxxxxxxxxxxx>
>>> To: Guenter Roeck <guenter.roeck@xxxxxxxxxxxx>
>>> Subject: Re: [w83627ehf] Not all fans are shown (#3)
>>>
>>> Note that I adapted /etc/sensors3.conf. The output is:
>>>
>>> nct6776-isa-0290
>>> Adapter: ISA adapter
>>> VCore: +0.76 V (min = +0.00 V, max = +1.74 V)
>>> +12V: +12.36 V (min = +0.00 V, max = +0.00 V) ALARM
>>> AVCC: +3.38 V (min = +0.00 V, max = +0.00 V) ALARM
>>> +3.3V: +3.36 V (min = +0.00 V, max = +0.00 V) ALARM
>>> in4: +0.02 V (min = +0.00 V, max = +0.00 V) ALARM
>>> +5V: +5.04 V (min = +0.00 V, max = +0.00 V) ALARM
>>> 3VSB: +3.46 V (min = +0.00 V, max = +0.00 V) ALARM
>>> VBat: +3.30 V (min = +0.00 V, max = +0.00 V) ALARM
>>> fan1: 0 RPM (min = 0 RPM) ALARM
>>> fan2: 570 RPM (min = 0 RPM) ALARM
>>> fan3: 0 RPM (min = 0 RPM) ALARM
>>> fan4: 1867 RPM (min = 0 RPM) ALARM
>>> fan5: 0 RPM (min = 0 RPM) ALARM
>>> SYSTIN: +35.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor
>>> CPUTIN: +33.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
>>> AUXTIN: +35.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
>>> PECI Agent 0: +36.0°C
>>> cpu0_vid: +2.050 V
>>> intrusion0: ALARM
>>> intrusion1: ALARM
>>>
>>> There's one more thing missing, though. I cannot find a way to set the fan speed in the sys-dir.
>>>
>>> ---
>>>
>>> You might also want to set min-max values to get rid of the warnings. Fan speeds are set through pwm[1-3].
>>> Did you try to set those ? Chances are that one controls fan2 and another fan4; there does not
>>> have to be a direct mapping.
>>>
>>> Thanks,
>>> Guenter
>>
>> Oh, I forgot to start the daemon since trying out the patch. I did set
>> the min and max values.
>>
>> The correct mapping (triple-checked with the BIOS) for the AsRock Z68
>> Pro3-M mainboard, and quite possibly for others -- the +12V
>> calculation is done as an example in the manual of the chip -- is
>> given by
>>
>> label in1 "+12V"
>> compute in1 @*6.6,@/6.6
>>
>> label in5 "+5V"
>> compute in5 @*3,@/3
>>
>> Best, CC
>
> I tested all three fan outputs. Another thing is weird: pwm1_mode has
> its meaning reversed (it's a 3-pin connector and the value 1 is DC
> mode, in contrast to pwm2 and the documentation).
>
> fan1 is controlled by pwm1, which is labelled as CHA_FAN (3-pin connector)
> fan2 is controlled by pwm2, which is labelled as CPU_FAN (4-pin connector)
> fan3 does not exist
> fan4 is not yet controlled, but is labelled PWR_FAN (3-pin connector)
> fan5 does not exist
>
> Best, CC
I tested against the BIOS; it cannot control fan4 either. Then I
noticed that I have a fourth fan connector, which the BIOS actually
can control and the driver can, too.
The updated info for the mainboard AsRock Z68 Pro3-M:
label in1 "+12V"
compute in1 @*6.6,@/6.6
set in1_min 12*0.9
set in1_max 12*1.1
label in5 "+5V"
compute in5 @*3,@/3
set in5_min 5*0.9
set in5_max 5*1.1
labal fan1 "CHA_FAN1"
label fan2 "CPU_FAN"
label fan3 "CHA_FAN2"
label fan4 "PWR_FAN"
The mapping is fan1<>pwm1, fan2<>pwm2, fan3<>pwm3. The meaning of
pmw[1,3]_mode is reversed.
It's a bit weird that the chip apparently supports the control of four
fans, but AsRock didn't connect it to it (according to the BIOS). But
I guess everything is working now.
Thanks, CC
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
