From: "Adachi, Kenichi" <aileenja-dTzOdQ2U+/YAvxtiuMwx3w@public.gmane.org>
To: dom-K271P2BsTd0@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RE: Re: IBM Thinkpad A31 | ACPI problems
Date: Fri, 3 Jan 2003 02:29:42 +0900 [thread overview]
Message-ID: <000301c2b284$8a15d8f0$232202d3@sayonara> (raw)
In-Reply-To: <200301011555.06058.dom-K271P2BsTd0@public.gmane.org>
> I browsed the mailing list archives (December 2002, November 2002) and
> encountered several postings from Sandro (PSI-Systems
<psi-systems-8XqT/MH+8ao@public.gmane.org>)
> who is having the same problem with his Thinkpad A31 laptop:
> ACPI: Found ECDT
> ACPI: Could not use ECDT
> evxfevnt-0119 [06] Acpi_disable : ACPI mode disabled
>
> ACPI is completely disabled for IBM Thinkpad A31. Is there a
> solution for that
> problem available? How can I be of any help to the ACPI developers?
>
Did you also read Andy Grover's reply to Sandro?
Subject: RE: [ACPI] ACPI does not work since
acpi-20021022-2.4.20-pre11.di
From: "Grover, Andrew" <andrew.grover () intel ! com>
Date: 2002-11-04 18:19:30
http://marc.theaimsgroup.com/?l=acpi4linux&m=103643408113691&w=2
In short, ECDT -> EC_ID is supposed to be the full path name of your EC
device in ACPI Namespace like "\_SB.PCI0.LPC.EC", but __NOT__ in your
BIOS.
You can work around your problem by adding hack code, but it makes OS
code dirty to save broken BIOSes and it allows BIOS vendor not to fix
their problem.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-01-02 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 14:55 IBM Thinkpad A31 | ACPI problems Dom
[not found] ` <200301011555.06058.dom-K271P2BsTd0@public.gmane.org>
2003-01-02 17:29 ` Adachi, Kenichi [this message]
[not found] ` <000301c2b284$8a15d8f0$232202d3-F8JvWDuGsZU@public.gmane.org>
2003-01-02 20:25 ` Dom
2003-01-02 21:31 ` PSI-Systems
[not found] ` <004701c2b2a6$434732d0$0201a8c0-kjWjS56XVej+Hn7q9Vec/7NAH6kLmebB@public.gmane.org>
2003-01-02 21:54 ` Dom
[not found] ` <200301022254.55856.dom-K271P2BsTd0@public.gmane.org>
2002-02-02 22:20 ` AW: " Jörg Hänsel
2003-01-04 10:53 ` Dom
[not found] ` <200301041153.42326.dom-K271P2BsTd0@public.gmane.org>
2003-01-04 15:51 ` Arndt Schoenewald
2003-01-02 20:27 ` Thomas Geiger
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='000301c2b284$8a15d8f0$232202d3@sayonara' \
--to=aileenja-dtzodq2u+/yavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=dom-K271P2BsTd0@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