From: Andrew McGregor <andrew@indranet.co.nz>
To: Tuncer M zayamut Ayaz <tuncer.ayaz@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.69 strange high tone on DELL Inspiron 8100
Date: Mon, 12 May 2003 12:34:36 +1200 [thread overview]
Message-ID: <443147.1052742876@[192.168.1.249]> (raw)
In-Reply-To: <17308.1052658225@www4.gmx.net>
Hi there...
--On Sunday, 11 May 2003 3:03 p.m. +0200 Tuncer M zayamut Ayaz
<tuncer.ayaz@gmx.de> wrote:
>> 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
>
> hmm, at least now I know where that strange sound comes from.
> I'm not quite sure that SpeedStep does not work,
> with SpeedStep disabled in the BIOS the fans turned on again with
> cpu load. this doesn't happen with SpeedStep. so I suppose it works
> to some extent, right?
Sounds like it to me. It certainly does not work on my i8000, but the 8100
is possibly different.
>
>> noise, so linux need not.
>
> so what options should I set?
> as I've already stated it's not bearable to do coding (incl. compiling)
> on this box without "Battery Optimized Mode" as SpeedStep calls it.
> on Linux I did that with a simple tool called speedstep.
> I've seen autospeedstep from Fritz Ganter which seems to use ACPI,
> dunno how that compares to cpufreqd.
Hmm. Maybe the 8100 has working speedstep, then. I'd suggest you see if
disabling just the APM idle calls, but leaving speedstep and cpufreq on
makes the noise.
I have had no success whatever with ACPI on an i8000, but again an 8100 may
be different.
>
> anyway, this laptop is not-so-nice anyway, I'm just happy I didn't
> buy it but my employer did ;)
Same here, and I mostly agree. Good price for such a nice screen, though
(I have the 1600x1200 15" screen).
Andrew
next prev parent reply other threads:[~2003-05-12 0:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 13:57 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 [this message]
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
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='443147.1052742876@[192.168.1.249]' \
--to=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
all inboxes | Powered by JetHome®