From: Bernd Schubert <bernd-schubert-Mmb7MZpHnFY@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Frank <hugelmopf-S0/GAf8tV78@public.gmane.org>
Subject: Re: S3 test
Date: Fri, 15 Jul 2005 16:29:36 +0200 [thread overview]
Message-ID: <200507151629.36606.bernd-schubert@gmx.de> (raw)
In-Reply-To: <200507151536.21857.hugelmopf-S0/GAf8tV78@public.gmane.org>
Hello Frank,
> Is there anybody on this list, who has tried this initramfs yet and can give
a
> short list of the steps involved? I have never before built a kernel for use
> with initram, but I would like to test it on my S3-broken laptop.
I'm planning to do it over the weekend (there was just too much to do
over the week). So far I have never used an initramfs myself, but I'm
rather experienced with initrd's. I guess you only need to specify a
line 'initrd = /path_to_initramfs/initramfs' in lilo, so something similar to
this:
# a rescue image that calls a shell in the initrd
image=/boot/linux-2.6.9-tc5
label=2.6.9_rescue
read-only
initrd=/boot/initrd-lvm-2.6.-amd64-lvm2_32_shell.gz
Recent kernels seem to first check if its an initramfs or initrd and I hope
they will do the proper thing themselves. I'm not sure if the kernel needs
ramdisk support, but I guess it needs it.
Better DON'T do it globally for all kernels, you might have problems to boot a
normal kernel again ;-)
About grub I don't know how to use/configure it.
Hope it helps,
Bernd
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-07-15 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 9:22 S3 test Shaohua Li
[not found] ` <1121160149.20699.6.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-07-12 13:08 ` Pavel Machek
2005-07-15 13:36 ` Frank
[not found] ` <200507151536.21857.hugelmopf-S0/GAf8tV78@public.gmane.org>
2005-07-15 14:29 ` Bernd Schubert [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-18 2:36 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD3057502B653B0-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-07-20 18:59 ` Frank
[not found] ` <200507202059.28860.hugelmopf-S0/GAf8tV78@public.gmane.org>
2005-07-21 10:55 ` Sebastian Kärgel
2005-07-25 1:55 ` Shaohua Li
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=200507151629.36606.bernd-schubert@gmx.de \
--to=bernd-schubert-mmb7mzphnfy@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=hugelmopf-S0/GAf8tV78@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