From: Manuel J.Galan <mjgalan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACER Aspire 5000
Date: Tue, 30 Aug 2005 14:36:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20050830T163344-565@post.gmane.org> (raw)
In-Reply-To: 20050829180845.98096.qmail@web81605.mail.yahoo.com
Matt R Hall <mhall@...> writes:
>
> I am having some problems with ACPI battery support on an ACER Aspire
> 5000. I am unable to read the battery state, which makes this laptop
> nearly useless. I suspect the DSDT code was missing a variable
> declaration or something and this was not caught by Microsoft's
> compiler, but I'm nowhere near expert with the DSDT programming
> language, so some help would be greatly appreciated.
>
> Relevant ASCII information is included inline. The /proc/acpi/dsdt file
> is attached.
>
try to patch your dsdt.dsl with the following
================================================
--- dstd.dsl.old 2005-08-30 15:26:55.000000000 +0100
+++ dstd.dsl 2005-08-30 15:26:35.000000000 +0100
@@ -2,7 +2,7 @@
* Intel ACPI Component Architecture
* AML Disassembler version 20050624
*
- * Disassembly of dstd, Tue Aug 30 15:26:55 2005
+ * Disassembly of dstd, Tue Aug 30 15:12:42 2005
*/
DefinitionBlock ("DSDT.aml", "DSDT", 1, "PTLTD ", "755", 100925440)
{
@@ -144,7 +144,10 @@
Scope (_PR)
{
- Processor (CPU0, 0x00, 0x00008010, 0x06) {}
+ Processor (CPU0, 0x00, 0x00008010, 0x06)
+ {
+ External (_PPC) // added. mjgalan
+ }
}
Scope (\_SB)
@@ -3007,8 +3010,8 @@
Name (PBST, Package (0x04)
{
0x00,
- Z007,
- Z007,
+ Z006, // changed from Z007. mjgalan
+ Z006, // changed from Z007. mjgalan
0x2710
})
Name (ERRC, 0x00)
@@ -3399,6 +3402,7 @@
{
\_SB.PHSR (0x03, 0x00)
}
+ Return(Package(0x02){0x00, 0x00}) // added. mjgalan
}
Method (_PTS, 1, NotSerialized)
========================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-30 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 18:08 ACER Aspire 5000 Matt R Hall
2005-08-30 14:36 ` Manuel J.Galan [this message]
[not found] ` <loom.20050830T163344-565-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2005-08-31 8:01 ` Re: ACER Aspire 5000 <- Will these bios bugs ever be fixed? Hans Kristian Rosbach
2005-08-31 8:52 ` Erik Slagter
[not found] ` <1125478354.20251.5.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-08-31 10:15 ` Carl-Daniel Hailfinger
[not found] ` <4315832E.6040005-hi6Y0CQ0nG0@public.gmane.org>
2005-08-31 10:22 ` Erik Slagter
2005-08-31 13:10 ` Alan Cox
[not found] ` <1125493848.3355.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-08-31 13:26 ` Carl-Daniel Hailfinger
[not found] ` <4315B00F.1080805-hi6Y0CQ0nG0@public.gmane.org>
2005-08-31 17:51 ` Janosch Machowinski
2005-08-31 13:09 ` Alan Cox
[not found] ` <20050829180845.98096.qmail-ZDCUxwME616A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2005-08-29 22:30 ` ACER Aspire 5000 Andreas Domfors
2005-08-31 20:19 ` Matt R Hall
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=loom.20050830T163344-565@post.gmane.org \
--to=mjgalan-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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