From: Christian Demmer <cdemmer@web.de>
To: grub-devel@gnu.org
Subject: Re: initrd in menu and command line
Date: Sun, 25 Jun 2006 22:23:11 +0200 [thread overview]
Message-ID: <623379195@web.de> (raw)
Hi,
uups ... sorry, while copy&pasting my grub.cfg it seems, I have lost some lines ....
here is my full grub.cfg (this time completely)
set timeout=3
set default=0
insmod font
insmod terminal
insmod vbe
menuentry "Kubuntu 2.6.15" {
linux /vmlinuz-2.6.15-25-386 root=/dev/hda2 splash=silent quiet
initrd /initrd-2.6.15-25-386
boot
}
menuentry "Kubuntu Rescue" {
linux /vmlinuz-2.6.15-25-386 root=/dev/hda2 splash=silent quiet rescue
initrd /initrd-2.6.15-25-386
boot
}
Bye,
Christian
> On Sunday 25 June 2006 14:48, Christian Demmer wrote:
>> I have the same problem as mentioned earlier regarding initrd:
>>
>> If I place initrd in the grub.cfg file, it will not be loaded. Using the
>> command line, I can easily boot my system:
>
>It is not the same problem, if you can boot it from the command line.
>
>> Athlon XP with 1 GB memory booting of the first IDE drive, /dev/hda1 aka.
>> hd0,0 is grub's root and linux /boot, /dev/hda2 aka. hd0,1 is linux root
>>
>> My grub.cfg:
>>
>> set timeout=3
>> set default
>
>Here is an error. You should put "set default=0". Currently, the scripting
>engine is very fragile with an error.
>
>> menuentry "Linux" {
>> linux /vmlinuz quiet root=/dev/hda2
>> initrd /initrd
>> }
>
>Okuji
>
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000071
next reply other threads:[~2006-06-25 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 20:23 Christian Demmer [this message]
2006-06-27 6:36 ` initrd in menu and command line Yoshinori K. Okuji
2006-06-27 7:02 ` Anes Lihovac
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 7:36 Christian Demmer
2006-06-25 12:48 Christian Demmer
2006-06-25 13:36 ` Yoshinori K. Okuji
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=623379195@web.de \
--to=cdemmer@web.de \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.