Hi,
after comparing your grub.cfg to mine, the main difference is the filename of
the kernel and the initrd ... so I copied my vmlinuz-2.6.15-25-686 to vmlinuz
and my initrd-2.6.15-25-386 to initrd
Adding this entry to grub.cfg as default entry with
menuentry "Kubunutu" {
linux /v
Am Dienstag, 27. Juni 2006 08:36 schrieb Yoshinori K. Okuji:
> On Sunday 25 June 2006 22:23, Christian Demmer wrote:
> > uups ... sorry, while copy&pasting my grub.cfg it seems, I have lost some
> > lines
>
> OK. Can you try the CVS version? I've already fixed some initrd issues.
Sorry, for j
On Sunday 25 June 2006 22:23, Christian Demmer wrote:
> uups ... sorry, while copy&pasting my grub.cfg it seems, I have lost some
> lines
OK. Can you try the CVS version? I've already fixed some initrd issues.
Thanks,
Okuji
___
Grub-devel mailing
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
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 c
Hi,
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:
Athlon XP with 1 GB memory booting of the first IDE drive, /dev/hda1 aka. hd0,0
is grub's root and linux /boot,
