On Mon, Feb 25, 2008 at 5:50 PM, Matthew <[EMAIL PROTECTED]> wrote:
>
> Pavel Roskin wrote:
> > "kernel" is "multiboot" in GRUB 2, not "linux", but "module" is still
> > "module". Also, you may want to try uncompressed images and modules.
> >
> The multiboot hint was very usefull, thanks...
> But strange undeterministic things happen now... :(
>
> snippet from my grub.cfg:
>
> menuentry "xen" {
> multiboot /boot/xen-3.0.gz dom0_mem=512M
> module /boot/vmlinuz-2.6.22-14-xen root=/dev/mapper/mainVG-rootLV ro
> module /boot/initrd.img-2.6.22-14-xen
> }
>
>
> when I try to boot this directly, it says:
> "error: you need to load multiboot kernel first"
>
> When I type manually (go to the grub command line after bios boot)
> multiboot /boot/xen-3.0.gz dom0_mem=512M
> it loads the xen and complains about not having any xenlinux
> kernel specified
>
> When I type:
> multiboot /boot/xen-3.0.gz dom0_mem=512M
> module /boot/vmlinuz-2.6.22-14-xen
> It starts booting, but complains about the root device (which is
> obvious)
>
> But when I type:
> multiboot /boot/xen-3.0.gz dom0_mem=512M
> module /boot/vmlinuz-2.6.22-14-xen root=/dev/mapper/mainVG-rootLV ro
> It starts booting but sometimes the error message is same as
> previous one (like there is no root option), sometimes there is wierd
> characters in root=....
> It looks like grub is not passing the arguments after file in
> module command correctly to the kernel. (But take it just as my guess)
>
>
> Has anybody some hints what to do/try next?
The old multiboot loader doesn't set the boot device, perhaps you can
try my patch and see if it works:
--
Bean
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
