From: Tuncer M "zayamut" Ayaz <tuncer.ayaz@gmx.de>
To: Tuncer M "zayamut" Ayaz <tuncer.ayaz@gmx.de>
Cc: xavier.bestel@free.fr, linux-kernel@vger.kernel.org
Subject: Re: 2.5.69 strange high tone on DELL Inspiron 8100
Date: Sat, 10 May 2003 23:13:41 +0200 [thread overview]
Message-ID: <S264505AbTEJVD1/20030510210327Z+7123@vger.kernel.org> (raw)
In-Reply-To: <S264494AbTEJUMq/20030510201246Z+7104@vger.kernel.org>
On Sat, 10 May 2003 22:23:06 +0200
Tuncer M "zayamut" Ayaz <tuncer.ayaz@gmx.de> wrote:
> On Sat, 10 May 2003 22:06:25 +0200
> Tuncer M "zayamut" Ayaz <tuncer.ayaz@gmx.de> wrote:
>
> > On 10 May 2003 19:47:47 +0200
> > Xavier Bestel <xavier.bestel@free.fr> wrote:
> >
> > > Le sam 10/05/2003 à 19:35, Tuncer M zayamut Ayaz a écrit :
> > >
> > > > rebooted with a reconfigured kernel to assure it's not cpufreq.
> > > > same behaviour without cpufreq.
> > >
> > > You should perhaps try to enable/disable APM idle calls ..
> > >
> > > Xav
> >
> > disabling apm idle calls seem to fix it but on this notebook
> > those calls are necessary so that it doesn't get too hot.
> > or can ACPI be used to accomplish those calls?
> >
> > I'm already running it always on SpeeStep power-saving mode
> > so that it doesn't get REALLY hot. try typing on an Inspiron
> > 8100 in the summer while compiling for a while. it's not
> > healthy for your hands :D
>
> besides fixing the noise issue by disabling a wanted feature,
> somehow pcmcia is borked, it just doesn't work and print
> lots of error messages and one of pcmcia processes (dunno which)
> segfaults.
> may be my fault, who knows. well, we'll see...
well, I actually saw PCMCIA functioning properly after
make clean'ing, recompiling and rebooting.
so no worries about that. now, off to find a replacement
for "APM idle calls".
next prev parent reply other threads:[~2003-05-10 21:03 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 [this message]
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
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=S264505AbTEJVD1/20030510210327Z+7123@vger.kernel.org \
--to=tuncer.ayaz@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xavier.bestel@free.fr \
/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).