From: Faye Pearson <faye@clara.net>
To: peter.holmes@fopet-esl.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ACPI] acpi_os_queue_for_execution()
Date: Wed, 8 Jan 2003 09:47:28 +0000 [thread overview]
Message-ID: <20030108094727.GA11860@clara.net> (raw)
In-Reply-To: <3E1AE2C9.13240.1114A3C@localhost>
peter.holmes@fopet-esl.com [peter.holmes@fopet-esl.com] wrote:
> As a relative newcomer to LINUX quite a lot of it is a foreign language,
> (no awful pun intended). I've been around electronics and computers for
> quite a few years now. So would you be so kind as to explain just what
> is "GPE_L00" and "DSDT". And just how we remove the salient part?
> I have a new Acer Aspire 1304LC which I could cook an egg on.
> Windoze(2K & XP Pro) don't generate anything like so much warmth.
These terms have nothing to do with linux, they're ACPI things from
within the BIOS. the GPE is a General Purpose Event I believe. The
_L00 event seems to be an event which is generated if the machine gets
too hot - It may be called something different on a different
manufacturer's BIOS.
What you need to do is run an ACPI enabled kernel and dump the
/proc/acpi/dsdt to a file (cat /proc/acpi/dsdt > mydsdt.aml). You can't
read this directly as it is in a compiled form. You need to disassemble
it and you do that with the iasl assembler/disassembler you can get from
Intel's instantly available technology pages.
(http://www.intel.com/technology/iapc/acpi/downloads.htm)
Once you have it disassembled, try "compiling" it straight away and you
will probably find that there are errors and warnings. Check the acpi
mailing list archives for details on how to fix these.
Once you have it working, compile it into the kernel - how to do this is
covered in the archives as well. Booting with this kernel should make
your acpi work much better. If it doesn't solve your heating problem
then if you put your disassembled and original dsdt on the web somewhere
and post a message asking for help, with links to these files on the
acpi list then you are likely to get some good assistance.
It is definitely worthwhile, my laptop now runs about 99% of the time
with no fan - showing it's much cooler.
The page with my efforts on for the Compaq Presario 2701EA is
http://dude.noc.clara.net/~faye/
Good luck.
Faye
--
Faye Pearson,
Covert Development
ClaraNET Ltd. Tel 020 7903 3000
You don't move to Edina, you achieve Edina.
-- Guindon
next prev parent reply other threads:[~2003-01-08 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 14:23 [ACPI] acpi_os_queue_for_execution() peter.holmes
2003-01-08 9:47 ` Faye Pearson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-03 19:00 Grover, Andrew
2003-01-04 22:44 ` Matthew Wilcox
2003-01-05 12:23 ` Ingo Oeser
2003-01-06 11:12 ` Pavel Machek
2003-01-06 11:44 ` Andrew Morton
2003-01-06 12:58 ` Andrew McGregor
2003-01-06 17:26 ` Faye Pearson
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=20030108094727.GA11860@clara.net \
--to=faye@clara.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.holmes@fopet-esl.com \
/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