From: Ronald Hitz <Ronald.Hitz-1NtEGJHV5g0@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Fwd: Re: 2.6.8 using 2.6.7 dsdt in initrd patch won't load dsdt
Date: Wed, 15 Sep 2004 15:50:36 +0200 [thread overview]
Message-ID: <E1C7aB8-0008Gh-00@mail1.isc.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2813 bytes --]
----- Forwarded message from Ronald Hitz <Ronald.Hitz-1NtEGJHV5g0@public.gmane.org> -----
Date: Wed, 15 Sep 2004 07:58:04 +0200
From: Ronald Hitz <Ronald.Hitz-1NtEGJHV5g0@public.gmane.org>
User-Agent: Mutt/1.5.6+20040722i
To: Oisín Mac Fhearaí <destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Reply-To: Ronald.Hitz-1NtEGJHV5g0@public.gmane.org
Subject: Re: [ACPI] 2.6.8 using 2.6.7 dsdt in initrd patch won't load dsdt
Hi Oisin,
since I've compiled my DSDT yesterday and load successfully,
I tell You, that with 2.6.8.1 there is an option in the kernel to load
an custom dsdt, where have to tell exactly( full path), where the dsdt
is and it was loaded successfully.
Maybe that helps You.
Regards
Ronald Hitz
On Tue, Aug 31, 2004 at 09:55:28AM +0100, Oisín Mac Fhearaí wrote:
> Hi all, sorry to bring more mundanity to the list, but this has been really
> annoying me for the last day or two.
>
> I (probably) fixed my DSDT, compiled it successfully, and have tried numerous
> ways of loading it at boot through an initrd patch (I couldn't find a 2.6.8
> patch, but the 2.6.7 patch I found seemed to apply well enough, without much
> fuzzing...).
> The machine appears to find it, but it doesn't actually load it.
> If anyone knows why not, or if I did something obviously wrong, please let me
> know.
>
> thanks,
> Oisín
>
> here's the relevant output in dmesg - I believe if it had loaded the tables
> from the custom DSDT, it would have said so just after the "ACPI: Subsystem
> revision nnnn" line (and I can tell that it hasn't, as it refers to an error
> in the DSDT I had fixed, by changing both references to Z00D to Z00C):
>
> ACPI: Looking for DSDT in initrd ... found (at offset 26218)!
> found customized DSDT with 16040 bytes!
> Freeing initrd memory: 41k freed
> NET: Registered protocol family 16
> PCI: PCI BIOS revision 2.10 entry at 0xfd9c6, last bus=1
> PCI: Using configuration type 1
> mtrr: v2.0 (20020519)
> ACPI: Subsystem revision 20040816
> evgpeblk-0980 [07] ev_create_gpe_block : GPE 00 to 0F [_GPE] 2 regs at
> 0000000000008020 on int 0x9
> evgpeblk-0989 [07] ev_create_gpe_block : Found 5 Wake, Enabled 0 Runtime
> GPEs in this block
> evgpeblk-0980 [07] ev_create_gpe_block : GPE 10 to 1F [_GPE] 2 regs at
> 0000000000008030 on int 0x9
> evgpeblk-0989 [07] ev_create_gpe_block : Found 1 Wake, Enabled 1 Runtime
> GPEs in this block
> Completing Region/Field/Buffer/Package
> initialization:..................................................
> psargs-0352: *** Error: Looking up [Z00D] in namespace, AE_NOT_FOUND
-----------> search_node dfda3228 start_node dfda3228 return_node 00000000
---------------
snip
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-09-15 13:50 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=E1C7aB8-0008Gh-00@mail1.isc.de \
--to=ronald.hitz-1ntegjhv5g0@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