From: Leonardo Macchia <macchia-oqfuaKpTAUu4UacQti+wdA@public.gmane.org>
To: Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Error overriding DSDT table
Date: Thu, 12 Sep 2002 10:18:03 +0200 [thread overview]
Message-ID: <20020912081803.GA1785@leo.anemos.org> (raw)
Hello.
I'm trying to patch the DSDT table in 2.4.19's ACPI but I get some
errors. I have a Compaq Evo N600c.
I applied acpi-20020821-2.4.19.diff patch (and if I stop here the kernel
works... but I can't see any battery nor fan resources) and
linux-2.4.18-acpi-20020709-dsdt.patch.
With acpidump I got the original DSDT table where I changed the wrong
entries
Name(_HID, "*PNP....")
into
Name(_HID, "PNP....")
so I used iasm to create the hex file from the patched table... I got
some errors ("Object does not exist" and similar) but I've heard to
ignore them... so I moved this hex file into
drivers/acpi/tables/acpi_dsdt.c and compiled the kernel.
After starting the kernel, ACPI results disabled (no /proc/acpi) and the
kernel - during boot - says:
[...]
ACPI: Subsystem revision 20020815
PCI: PCI BIOS revision 2.10 entry at 0xf04dd, last bus=4
PCI: Using configuration type 1 Sep 11 13:24:45 eniac kernel:
ACPI-0272: *** Info: Table [DSDT] replaced by host OS
ACPI-0107: *** Error: Acpi_load_tables: Could not load namespace: AE_AML_BAD_NAME
ACPI-0116: *** Error: Acpi_load_tables: Could not load tables: AE_AML_BAD_NAME
ACPI: Unable to load the System Description Tables
PCI: Probing PCI hardware
PCI: ACPI tables contain no PCI IRQ routing entries
[...]
Any suggestion? I think the trouble is dumping/compiling the DSDT
tables. :(
Thank you, Leonardo.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
reply other threads:[~2002-09-12 8:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020912081803.GA1785@leo.anemos.org \
--to=macchia-oqfuakptauu4uacqti+wda@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