From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Daniel Nofftz <nofftz@castor.uni-trier.de>
Cc: Norbert Preining <preining@logic.at>, linux-kernel@vger.kernel.org
Subject: Re: amd athlon cooling on kt266/266a chipset
Date: 24 Jan 2002 07:19:09 -0500 [thread overview]
Message-ID: <1011874755.22707.17.camel@psuedomode> (raw)
In-Reply-To: <Pine.LNX.4.40.0201241212250.7304-100000@infcip10.uni-trier.de>
In-Reply-To: <Pine.LNX.4.40.0201241212250.7304-100000@infcip10.uni-trier.de>
On Thu, 2002-01-24 at 06:19, Daniel Nofftz wrote:
> On Thu, 24 Jan 2002, Norbert Preining wrote:
>
> > Hi Daniel!
> >
> > You wrote:
> > > 2. enable generel-setup -> acpi , acpi-bus-maager , prozessor
> > > in the kernel config
> >
> > Why is it necessary to activate acpi which makes apm not working,
> > and therefor poweroff etc. acpi is long from working/stable and
> > the support for various actions too are missing.
> >
> > >From the patch I do not see why it is specific to acpi?
> >
> > Best wishes
>
> hi norbert!
>
> ok ... i tested it:
> patch activted:
> apm activated -> prozessor idle calls : 42°C when idle
> acpi activated -> prozessor c1/c2 states: 35°C when idle
>
> under load:
> apm activated -> 47°C kernel compiling after 2 min
> acpi activated -> 43°C kernel compiling after 2 min
>
> (kernel compiling only lasts about 3 min ... so no larger load intervalls
> are avaible at the moment ... )
>
> so ... you could use apm ... but acpi proofs to be better in power saveing
> with the "disconnectenable when STPGNT detected" bit set ...
> maybe apm is not working at all .. .cause at the moment i see that the
> temperature does not drop at all after finishing the kernel ... it looks
> like that the 42°C only where cause it was fresh rebooted from the acpi
> power saving mode
You should check your /var/log/messages directly for this nifty little
message.
kernel: ACPI: APM is already active, exiting
If you compiled in apm at the time you did that test, acpi wasn't even
active and thus the special athlon disconnect patch wasn't even
working. So all of that better cooling would be psychoschomatic.
Wouldn't be the first time better cooling/performance was all in the
head of the person using the hardware...although if you didn't have apm
compiled in then none of this matters and it was all working. But i
doubt that is true due to the 42C idle after some use no matter which
kernel was being used.
Furthermore, I haven't heard of anyone where the patch actually makes an
improvement in temp with the patch. But i have heard of people saying
it affected performance detrimentally. If it is helping and the cpu fans
decrease due to the lower temp, add fan speeds in different loads/temps
to reflect this.
lowering the fan speed and thus noise is more than a welcome change.
next prev parent reply other threads:[~2002-01-24 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 8:40 Norbert Preining
2002-01-24 11:19 ` Daniel Nofftz
2002-01-24 12:19 ` Ed Sweetman [this message]
2002-01-24 12:36 ` Norbert Preining
2002-01-24 21:00 ` Daniel Nofftz
2002-01-24 16:05 Dieter Nützel
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=1011874755.22707.17.camel@psuedomode \
--to=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nofftz@castor.uni-trier.de \
--cc=preining@logic.at \
/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
all inboxes | Powered by JetHome®