All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Standalone driver for W83677HG-I, NCT6775F,
Date: Mon, 07 Feb 2011 20:35:04 +0000	[thread overview]
Message-ID: <20110207213504.5d7450c9@endymion.delvare> (raw)
In-Reply-To: <20110205175852.GA26672@ericsson.com>

On Mon, 7 Feb 2011 09:44:12 -0800, Guenter Roeck wrote:
> Hi Andrew,
> 
> On Mon, Feb 07, 2011 at 11:50:48AM -0500, Andrew Lutomirski wrote:
> [ ... ]
> > >
> > > So what you'll have to do is to set a minimum speed, and the problem will go away.
> > 
> > I admit I'm a bit confused as to what fan2_min does.  I have a minimum
> > (to warn?) fan speed set in BIOS, which seems to have nothing to do
> > with the initial value of fan2_min.  Changing fan2_min will cause
> > fan2_alarm to become set or unset, when I decrease min below input,
> > alarm stays set until I read it once.
> > 
> Interesting; it means that it works, but the BIOS seems to use another set
> of registers to set the minimum speed.

The BIOS doesn't necessarily use limit registers. It is totally
possible that the speed is simply checked at boot time against the
specified limit, and the hardware monitoring chip isn't even aware of
it.

Motherboard vendors have been under- or even misusing the hardware
monitoring features of the chips they selected for years, and while it
gets slowly better over time, it's still dangerous to assume that they
always know what they are doing and that they always do the right thing.

-- 
Jean Delvare

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

  parent reply	other threads:[~2011-02-07 20:35 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 17:58 [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, NCT6776F Guenter Roeck
2011-02-05 18:04 ` [lm-sensors] Standalone driver for W83677HG-I, NCT6775F, Guenter Roeck
2011-02-05 19:15 ` Guenter Roeck
2011-02-05 21:46 ` Ian Dobson
2011-02-06  1:00 ` Guenter Roeck
2011-02-06  9:36 ` Ian Dobson
2011-02-06  9:56 ` Jean Delvare
2011-02-06 10:00 ` Ian Dobson
2011-02-06 10:00 ` Jean Delvare
2011-02-06 10:14 ` Ian Dobson
2011-02-06 11:59 ` Ian Dobson
2011-02-06 13:37 ` Ian Dobson
2011-02-06 13:55 ` Ian Dobson
2011-02-06 15:45 ` Ian Dobson
2011-02-06 15:53 ` Jean Delvare
2011-02-06 16:03 ` Ian Dobson
2011-02-06 16:04 ` Guenter Roeck
2011-02-06 16:13 ` Guenter Roeck
2011-02-06 16:28 ` Guenter Roeck
2011-02-07  3:50 ` Andy Lutomirski
2011-02-07  4:50 ` Guenter Roeck
2011-02-07  7:33 ` Jean Delvare
2011-02-07  7:40 ` Jean Delvare
2011-02-07 13:56 ` Andrew Lutomirski
2011-02-07 14:39 ` Guenter Roeck
2011-02-07 14:47 ` Guenter Roeck
2011-02-07 14:57 ` Guenter Roeck
2011-02-07 16:03 ` Guenter Roeck
2011-02-07 16:50 ` Andrew Lutomirski
2011-02-07 17:44 ` Guenter Roeck
2011-02-07 17:58 ` Guenter Roeck
2011-02-07 18:20 ` Andrew Lutomirski
2011-02-07 18:48 ` Guenter Roeck
2011-02-07 19:53 ` Andrew Lutomirski
2011-02-07 20:26 ` Guenter Roeck
2011-02-07 20:32 ` Andrew Lutomirski
2011-02-07 20:35 ` Jean Delvare [this message]
2011-02-07 21:27 ` Guenter Roeck
2011-04-10 15:28 ` Ian Pilcher
2011-04-12 16:49 ` Ian Dobson

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=20110207213504.5d7450c9@endymion.delvare \
    --to=khali@linux-fr.org \
    --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.