From: "J.A. Magallon" <jamagallon@able.es>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Strange problem with sensors: 0 RPMs ?
Date: Fri, 04 Feb 2005 02:04:28 +0000 [thread overview]
Message-ID: <1107482668l.6500l.0l@werewolf.able.es> (raw)
In-Reply-To: <1107479698l.5691l.0l@werewolf.able.es> (from jamagallon@able.es on Fri Feb 4 02:14:58 2005)
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On 2005.02.04, J.A. Magallon wrote:
> Hi all...
>
> I have a dual Xeon box. I got tired of the noise of the Intel boxed
> fans and bought a couple of Swiftech 'hedegehogs' and two ThemalTake
> fans.
> Board is an Asus PCDL and sensors chip is a w83627hf (heavily modified by
> Asus, I suppose, because it has 5! fan sensors). With the Intel fans,
> I got both rpm measures OK. With the new fans, the CPU0 fan insists
> it is stopped at 0 RPM. And I see it spinning. It is correctly plugged
> and the Xeon temperature stays nicely at 32º C.
> And the more strange thing is that the hardware monitor in the BIOS
> tells me it is spinning at about 2500 RPM !!! And the own BIOS says
> at boot that my CPU FAN IS STOPPED.
>
Sorry for the noise. Some google results I have not found before and
fanN_div did the trick.
Thanks.
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.10-jam7 (gcc 3.4.3 (Mandrakelinux 10.2 3.4.3-3mdk)) #3
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-02-04 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 1:14 Strange problem with sensors: 0 RPMs ? J.A. Magallon
2005-02-04 2:04 ` J.A. Magallon [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=1107482668l.6500l.0l@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox