public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Getting the initrd dsdt table running
Date: Tue, 18 Nov 2003 16:09:34 +0100	[thread overview]
Message-ID: <20031118150934.GA1715@enigma.daemon.sh> (raw)
In-Reply-To: <0HOB00CMINOCSC-PYEadblV/CkRaffoSZVBSIdd74u8MsAO@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

hi...

* Brian Peyton <bpeyton-DUV0O6k01bo@public.gmane.org> [2003-11-15 09:42 +0100]:
> I've got a Dell Inspirion 5100.
> 
> I'm trying to get 2.6.0-test9 working with the initrd dsdt table patch.  I
> normally don't use an initrd, and on his page it says that if I don't use an
> initrd I can just set the initrd to the binary lookingish .aml file that
> iasl produces.  So in my grub.conf file I have the line:
> Initrd /boot/initrd
> 
> Where the contents of initrd is the .aml file.  From dmesg it still says not
> detected.  How can I fix this?

the contents of the initrd is not the AML only, it also contains a magic
signature:

echo "INITRDDSDT123DSDT123" >> /boot/initrd # magic signature
cat DSDT.aml >> /boot/initrd


otherwise, you are sure that the patch is included in the kernel? what
is the exact output (dmesg)?

cheers,
 sebastian

-- 
::: .O.
::: ..O
::: OOO
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-11-18 15:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14  3:20 Getting the initrd dsdt table running Brian Peyton
     [not found] ` <0HOB00CMINOCSC-PYEadblV/CkRaffoSZVBSIdd74u8MsAO@public.gmane.org>
2003-11-18 15:09   ` Sebastian Henschel [this message]

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=20031118150934.GA1715@enigma.daemon.sh \
    --to=acpi-1rjuzeeg9oeb1svskn2v4q@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