From: Troels Walsted Hansen <troels@thule.no>
To: Andrew McGregor <andrew@indranet.co.nz>
Cc: Tuncer M zayamut Ayaz <tuncer.ayaz@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.69 strange high tone on DELL Inspiron 8100
Date: Tue, 13 May 2003 14:43:49 +0200 [thread overview]
Message-ID: <3EC0E885.9070306@thule.no> (raw)
In-Reply-To: <3191078.1052695705@[192.168.1.249]>
Andrew McGregor wrote:
> Try this (which will make no difference to the effectiveness of APM on
> this machine):
>
>> CONFIG_PM=y
>>
>> CONFIG_APM=y
>> CONFIG_APM_DO_ENABLE=n
>> CONFIG_APM_CPU_IDLE=n
>> CONFIG_APM_DISPLAY_BLANK=y
>> CONFIG_APM_REAL_MODE_POWER_OFF=y
>>
>> CONFIG_CPU_FREQ=n
>> CONFIG_CPU_FREQ_TABLE=n
>>
>> CONFIG_X86_SPEEDSTEP=n
>
>
> Reasoning:
> cpufreq and speedstep don't work on Dell P3 laptops anyway, and the
> *internal power supplies* of the i8x00 series make wierd noises when APM
> tries to idle the CPU. The board will do this anyway, without making
> noise, so linux need not.
My Dell Latitude C600 shows the exact same problem. I noticed it after
upgrading to from RH7.x to RH8 with kernel 2.4.18-27.8.0. I believe this
kernel is customized by RH to use HZ=500 or something in that region.
With your analysis of the problem I was able to remove the noise by
using the "apm=idle-threshold=100" parameter on the kernel commandline.
This turns off APM idle calls without requiring kernel recompilation.
Using the "i8k" kernel module, I have verified that the temperature of
the CPU is unchanged with APM idle turned off. I have not tried to
measure power consumption or battery use.
Thanks for the tip!
--
Troels Walsted Hansen
next prev parent reply other threads:[~2003-05-13 12:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 13:57 2.5.69 strange high tone on DELL Inspiron 8100 Tuncer M zayamut Ayaz
2003-05-10 13:59 ` Alan Cox
2003-05-10 15:07 ` Tuncer M zayamut Ayaz
2003-05-10 15:28 ` Tuncer M zayamut Ayaz
2003-05-10 15:39 ` Ahmed Masud
2003-05-10 15:46 ` Tuncer M zayamut Ayaz
2003-05-10 16:25 ` Jamie Lokier
2003-05-10 16:51 ` Tuncer M zayamut Ayaz
2003-05-10 17:35 ` Tuncer M zayamut Ayaz
2003-05-10 17:47 ` Xavier Bestel
2003-05-10 20:06 ` Tuncer M zayamut Ayaz
2003-05-10 20:23 ` Tuncer M zayamut Ayaz
2003-05-10 21:13 ` Tuncer M zayamut Ayaz
2003-05-11 10:50 ` Dumitru Ciobarcianu
2003-05-11 13:11 ` Tuncer M zayamut Ayaz
2003-05-11 11:28 ` Andrew McGregor
2003-05-11 13:03 ` Tuncer M zayamut Ayaz
2003-05-12 0:34 ` Andrew McGregor
2003-05-12 6:17 ` Tuncer M zayamut Ayaz
[not found] ` <200305120620.h4C6K64j061741@ns.indranet.co.nz>
2003-05-12 20:11 ` Andrew McGregor
2003-05-13 6:20 ` Tuncer M zayamut Ayaz
2003-05-11 20:48 ` Valdis.Kletnieks
2003-05-12 0:41 ` Andrew McGregor
2003-05-13 12:43 ` Troels Walsted Hansen [this message]
2003-05-13 12:50 ` Tuncer M zayamut Ayaz
[not found] <20030510154639.02DDC32C9@marauder.googgun.com>
2003-05-10 15:52 ` Ahmed Masud
2003-05-10 16:04 ` Tuncer M zayamut Ayaz
2003-05-10 18:33 ` Jos Hulzink
2003-05-10 16:46 ` Tuncer M zayamut Ayaz
2003-05-10 19:46 Chuck Ebbert
2003-05-10 20:06 ` Tuncer M zayamut Ayaz
2003-05-11 2:28 Chuck Ebbert
2003-05-11 19:27 ` Tuncer M zayamut Ayaz
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=3EC0E885.9070306@thule.no \
--to=troels@thule.no \
--cc=andrew@indranet.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=tuncer.ayaz@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).