public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Gunter Ohrner <G.Ohrner-6V9naDJErT6662+jY7v6MhvVK+yQ3ZXh@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Patch] DSDT in initrd v0.2
Date: Tue, 6 May 2003 19:56:52 +0200	[thread overview]
Message-ID: <200305061957.00037@mail.CustomCDROM.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0305061444120.1274-qopfHk9/S+VQK2oVCIMtW7NldLUNz+W/@public.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Dienstag, 6. Mai 2003 14:51 schrieb Markus Gaugusch:
> * Feature: Get DSDT from initrd without signature, if it starts with
>   "DSDT". This way one can just copy the DSDT.aml file and use it as
>   initrd

This doesn't work for me. How can I troubleshoot the problem? I've never used 
an initrd before.
I fetched the patch and it applied cleanly. Then I compiled RAM disk support 
into the kernel and enabled initrd and ACPI initrd support. Next I copied my 
DSDT.aml file, which starts with the string "DSDT" to /boot/initrd, added 
"initrd=/boot/initrd" to my kernel append line, installed the new kernel and 
re-ran lilo. The new kernel works but it uses the BIOS' buggy DSDT and not my 
just-being-fixed altered dump of it... :-(
dmesg does not seem to show any traces of something with initrd at all...

Greetings,

  Gunter

- -- 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+                   PGP-verschlüsselte Mails bevorzugt!                 +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- - "What is it that a man may call the greatest things in life?"
- - "Hot water, good dentishtry and shoft lavatory paper."
        -- Cohen the Barbarian (about 90 years old) in conversation with 
Discworld nomads           (Terry Pratchett, The Light Fantastic)
+-+-+-+-+-+-+-+-+-+-+-+-+ http://www.lspace.org +-+-+-+-+-+-+-+-+-+-+-+-+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+t/dr0ORHvREo8l8RApU5AJ0Zq0Ab69ZaVjjZHzCFSr2B4q7nhQCfVxmX
JTvz+KRxZId4uoVJ2NoXuns=
=tWjY
-----END PGP SIGNATURE-----



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

  parent reply	other threads:[~2003-05-06 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 12:51 [Patch] DSDT in initrd v0.2 Markus Gaugusch
     [not found] ` <Pine.LNX.4.53.0305061444120.1274-qopfHk9/S+VQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2003-05-06 17:56   ` Gunter Ohrner [this message]
     [not found]     ` <200305061957.00037-GfAVBl5OxjxchHfdsNF8vBvVK+yQ3ZXh@public.gmane.org>
2003-05-07  9:44       ` Markus Gaugusch
2003-05-08 21:24   ` Pavel Machek
     [not found] <A3C83F41488BD61195C3000802252FC135C3A8@dubim07742.ie.ml.com>
     [not found] ` <A3C83F41488BD61195C3000802252FC135C3A8-SI4JNLCqwGbcq19Bq1crS1aTQe2KTcn/@public.gmane.org>
2003-05-08 10:02   ` Markus Gaugusch
2003-05-08 12:11     ` Derek Broughton
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 10:11 Breathnach, Proinnsias (Dublin)

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=200305061957.00037@mail.CustomCDROM.de \
    --to=g.ohrner-6v9nadjert6662+jy7v6mhvvk+yq3zxh@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