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] "echo 0 > pwm2" does NOT stop fan
Date: Wed, 14 Jan 2009 20:28:00 +0000	[thread overview]
Message-ID: <20090114212800.68e5bb44@hyperion.delvare> (raw)
In-Reply-To: <676459746@web.de>

On Wed, 14 Jan 2009 11:22:59 -0700, David Hubbard wrote:
> > What does this have to do with 4-pin fans? This is indeed what I have,
> > but I can't see the relation. I thought that the 4th pin was simply
> > there to get proper speeds reported even when low PWM duty cycles were
> > used. If there more to it than that?
> >
> > This is the only 4-pin fan I have and, as far as I know, the only
> > mainboard I have that support a 4-pin fan, so I can't do that many
> > tests.
> 
> I've seen it on a motherboard with an it87 driving an intel 4-pin fan
> that came with the CPU. It seems to be circuitry inside the fan. (So,
> replacing the fan might work, no guarantees.)

Ah, I get the idea now. On 4-pin fans, PWM is only a signal, not a
power source. This explains why the PWM response curve is very
different from what you get with a 3-pin fan: it's almost linear and
has a non-zero minimum, while usually you get a non-linear response
(upper half of PWM values has little effect) and PWM=0 stops the fan.

This indeed suggests some embedded electronics in the fan itself. And
it also means that each 4-pin fan can have its own max _and min_ speed
limit. I'll make sure to pay attention to this next time I must buy a
CPU fan.

-- 
Jean Delvare

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

      parent reply	other threads:[~2009-01-14 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 20:44 [lm-sensors] "echo 0 > pwm2" does NOT stop fan Jens Gottstein
2009-01-12  5:59 ` David Hubbard
2009-01-14 16:41 ` Jean Delvare
2009-01-14 18:22 ` David Hubbard
2009-01-14 20:28 ` Jean Delvare [this message]

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=20090114212800.68e5bb44@hyperion.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.