From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Ryan Underwood <nemesis-lists-RBwgCYbvQ+vk1uMJSBkQmQ@public.gmane.org>
Cc: Luming Yu <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Shuttle HOT-591P fails ACPI on 2.4.23
Date: 10 Dec 2003 13:33:03 -0500 [thread overview]
Message-ID: <1071081182.2543.68.camel@dhcppc4> (raw)
In-Reply-To: <20031210104157.GC31759-eRi7t0xs5gloIlNlpBNreQ@public.gmane.org>
On Wed, 2003-12-10 at 05:41, Ryan Underwood wrote:
> Hi,
>
> attached acpidump output. btw, acpidump makefile needs to be fixed to
> -I/usr/src/linux/include, otherwise it takes the userspace headers and
> fails to build. also, I tried running the output through acpidisasm to
> understand it, but acpidisasm produced no output:
> # ../../acpidump/acpidmp | ./acpidisasm
> #
I've updated pmtools with the -I you need, updated the README, deleted
acpidisasm and added madt. Let me know if you have any trouble with the
udpated version:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20031210.tar.gz
Note that when I asked for acpidmp output, I simply meant
# acpidmp > acpidmp.out
without any post-processing.
> This machine has never ran windows so I don't know whether it would work
> or not. If it is critical to understanding why it doesn't work, I can
> try installing it on a different disk.
That would be helpful.
Frankly if Windows (2K or XP) can't get into ACPI mode, It is probably
only of academic importantce that Linux also can't.
thanks,
-Len
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-12-10 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 2:40 Shuttle HOT-591P fails ACPI on 2.4.23 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C14-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-10 10:41 ` Ryan Underwood
[not found] ` <20031210104157.GC31759-eRi7t0xs5gloIlNlpBNreQ@public.gmane.org>
2003-12-10 18:33 ` Len Brown [this message]
[not found] ` <1071081182.2543.68.camel-D2Zvc0uNKG8@public.gmane.org>
2003-12-10 20:55 ` Ryan Underwood
[not found] <BF1FE1855350A0479097B3A0D2A80EE0CC88E1@hdsmsx402.hd.intel.com>
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC88E1-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-12-10 21:11 ` Ryan Underwood
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 16:26 Brown, Len
2003-12-08 12:24 Ryan Underwood
[not found] ` <20031208122424.GA18539-eRi7t0xs5gloIlNlpBNreQ@public.gmane.org>
2003-12-08 15:14 ` Len Brown
[not found] ` <1070896460.2407.15.camel-D2Zvc0uNKG8@public.gmane.org>
2003-12-09 4:50 ` Ryan Underwood
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=1071081182.2543.68.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=nemesis-lists-RBwgCYbvQ+vk1uMJSBkQmQ@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