From: Samuel Rydh <samuel@ibrium.se>
To: Giuliano Pochini <pochini@denise.shiny.it>
Cc: linux-kernel@vger.kernel.org, Micha? Roszka <michal@roszka.pl>
Subject: Re: [.config] CONFIG_THERM_WINDTUNNEL
Date: Thu, 18 Mar 2004 13:03:11 +0100 [thread overview]
Message-ID: <20040318120311.GD3686@ibrium.se> (raw)
In-Reply-To: <Pine.LNX.4.58.0403181221580.1392@denise.shiny.it>
On Thu, Mar 18, 2004 at 12:27:28PM +0100, Giuliano Pochini wrote:
> On Thu, 18 Mar 2004, Samuel Rydh wrote:
>
> > Btw, I would like to get reports about how well this driver works
> > with respect to noise reduction. I'm in particular interested
> > in the dual 1.4 GHz model...
>
> The author has a dual-1.2 and I tested it on another dual-1.2. I don't
> know if it has been tested on other mathines. The driver writes in
> the system logs the temperature and the fan speed every time they change,
> so you can check what it's doing (and you can unload the module if you
> see it does something wrong).
Yes I know... I wrote it :-)
It should be perfectly safe to use. It contains a (very conservative)
fail safe; if the temperature exceeds the working point by a few
degrees, the hardware overheat protection is programmed to turn
on the fans 100%. This works even if the kernel has locked up
solidly.
I'm mostly concerned that the working point is set too low for
the 1.4 Ghz machine. If it is, then there might be some unnecessary
noise. When the temperature is going down towards the working point,
the fan speed is increased to remove the last extra heat.
The assumption is that some temporary heat generating operation
has finished (like a CPU intensive calculation or heavy usage of
the graphics card). This is a good strategy if the working point
is correct but not-so-good if the working point is higher than
expected (cyclic fan behavior might occur).
In all cases, it should be an improvement compared to the firmware
setting which is incredibly noisy and usually causes short period
fan speed cycling.
/Samuel
next prev parent reply other threads:[~2004-03-18 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 7:21 [.config] CONFIG_THERM_WINDTUNNEL Michał Roszka
2004-03-18 9:16 ` Giuliano Pochini
2004-03-18 11:20 ` Samuel Rydh
2004-03-18 11:27 ` Giuliano Pochini
2004-03-18 11:36 ` Michał Roszka
2004-03-18 12:03 ` Samuel Rydh [this message]
2004-03-24 0:18 ` Pavel Machek
2004-03-26 18:30 ` Samuel Rydh
2004-03-26 22:32 ` Pavel Machek
2004-03-18 16:17 ` Michał Roszka
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=20040318120311.GD3686@ibrium.se \
--to=samuel@ibrium.se \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@roszka.pl \
--cc=pochini@denise.shiny.it \
/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