All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Soeren D. Schulze" <soeren.d.schulze@gmx.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Something wrong with support for NCT6776F in
Date: Mon, 31 Oct 2011 07:46:43 +0000	[thread overview]
Message-ID: <4EAE5263.3040309@gmx.de> (raw)
In-Reply-To: <4EA9CECA.4050007@gmx.de>

On 31.10.2011 05:57, Guenter Roeck wrote:
>> I have an ASRock H67M-ITX motherboard.
>>
>> The w83626ehf driver detects:
>>
>> [ 3904.608693] w83627ehf: Found NCT6776F chip at 0x290
>>
>> "sensors" shows me:
>>
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Physical id 0:  +46.0°C  (high = +80.0°C, crit = +98.0°C)
>> Core 0:         +46.0°C  (high = +80.0°C, crit = +98.0°C)
>> Core 1:         +45.0°C  (high = +80.0°C, crit = +98.0°C)
>> Core 2:         +46.0°C  (high = +80.0°C, crit = +98.0°C)
>> Core 3:         +46.0°C  (high = +80.0°C, crit = +98.0°C)
>>
>> nct6776-isa-0290
>> Adapter: ISA adapter
>> Vcore:         +0.96 V  (min =  +0.00 V, max =  +1.74 V)
>> in1:           +0.18 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
>> AVCC:          +3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
>> +3.3V:         +3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
>> in4:           +0.54 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
>> in5:           +1.69 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
>> 3VSB:          +3.41 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
>> Vbat:          +3.31 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
>> fan1:            0 RPM  (min =    0 RPM)  ALARM
>> fan2:         2180 RPM  (min =    0 RPM)  ALARM
>> SYSTIN:        +42.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor
>> = thermistor
>> CPUTIN:       +127.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor
>> = thermistor
>> AUXTIN:        -24.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor =
>> thermistor
>> PECI Agent 0:  +46.5°C
>> cpu0_vid:     +2.050 V
>> intrusion0:   ALARM
>> intrusion1:   ALARM
>>
>>
>> Here, CPUTIN and AUXTIN (whatever it is) are obviously wrong.  CPUTIN
>> *decreases* towards 17°C when the CPU gets hot (non-linearly, though).
>>
> Odd. No idea what is going on, though. The registers are quite straightforward,
> and the same for NCT6775F and NCT6776F. And it works on my system with NCT6775F.

Is there the option that auto-detection was wrong and I have a 
completely different chip?

>> This was the first problem.  The second problem occurs when I try to
>> control fan2 manually.  The "pwm2" file in sysfs is 255 for anything
>> above 2000 RPM, but as you can see above, the fan can do more (I've been
>> at 2600 RPM -- maybe it can do even more), but pwm2 stays at 255.
>>
> Looking through the datasheet, I did not find anything obvious. It might
> be possible that the PWM output frequency (register 2 bank 0) somehow affects
> the fan speed as well. What causes the fan speed to go higher in your system ?

High temperature in Temperature Cruise mode.

My firmware setup interface actually provides me with both the options 
"Target fan speed" and "Target temperature", but I have the impression 
that while the driver reports that I'm in Temperature Cruise mode, the 
fan speed does not vary that much, but it rather tries to keep the fan 
speed constant unless temperature is completely out of range.

The fan speeds up only when I'm above 60°C, and even that with a certain 
delay, so under full load, I get above 70°C when my fans are 
firmware-controlled...  That's basically the reason why I want software 
control.

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2011-10-31  7:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 21:36 [lm-sensors] Something wrong with support for NCT6776F in w83627ehf Soeren D. Schulze
2011-10-31  4:57 ` [lm-sensors] Something wrong with support for NCT6776F in Guenter Roeck
2011-10-31  5:07 ` Guenter Roeck
2011-10-31  7:46 ` Soeren D. Schulze [this message]
2011-10-31 15:50 ` Guenter Roeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EAE5263.3040309@gmx.de \
    --to=soeren.d.schulze@gmx.de \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.