Hi,
I am trying to build coreboot for AMD DB800 and that the Linux Kernel is never started but I see a prompt on the serial terminal "grub" and when I issue the boot command it complains of "Unsupported boot format". Has any body seen this before.
I have a HDD which has SLES 10 SP1 installed on it I have got four partitions one of them been a extended partition.
/dev/hda1 --> boot (ext2) /dev/hda2 --> swap /dev/hda3 --> Root file system (resierfs) /dev/.... ....
Based on this I have given the following options for FILO, do you think this is where the problem is....
MENULST_FILE = "hda1:/grub/menu.lst"
AUTOBOOT_FILE = "hda1:/vmlinuz initrd hda1:/initrd root=/dev/hda3 vga=0x317 console=tty0 console=ttyS0,115200"
Regards, Phani
On Fri, Feb 29, 2008 at 09:47:16AM -0800, Phani Babu Giddi wrote:
MENULST_FILE = "hda1:/grub/menu.lst"
AUTOBOOT_FILE = "hda1:/vmlinuz initrd hda1:/initrd root=/dev/hda3 vga=0x317 console=tty0 console=ttyS0,115200"
As far as I know these two are mutually exclusive. If using the grub compatibility stuff in FILO then AUTOBOOT_FILE will never be used.
I don't like grub and thus always stick to only using AUTOBOOT_FILE.
In your case the line looks fine if the kernel is stored in /boot/vmlinuz, if it's /vmlinuz then change to hda3 instead of hda1 in the first argument.
Oh, and make sure you build FILO with reiserfs support if the kernel is on your root partition.
//Peter
Hi Peter,
Yes I have turned on resierfs and ext2 too because /boot is and ext2 partition. From your description it looks like the AUTOBOOT options are good but not sure why it reports of Unsupported image format. Let me first get rid of GRUB. Do yout know if FILO works for all versions of GRUB boot loaders or there are some specific boot loaders that it supports.
Regards, Phani
On Fri, Feb 29, 2008 at 6:54 PM, Peter Stuge peter@stuge.se wrote:
On Fri, Feb 29, 2008 at 09:47:16AM -0800, Phani Babu Giddi wrote:
MENULST_FILE = "hda1:/grub/menu.lst"
AUTOBOOT_FILE = "hda1:/vmlinuz initrd hda1:/initrd root=/dev/hda3 vga=0x317 console=tty0 console=ttyS0,115200"
As far as I know these two are mutually exclusive. If using the grub compatibility stuff in FILO then AUTOBOOT_FILE will never be used.
I don't like grub and thus always stick to only using AUTOBOOT_FILE.
In your case the line looks fine if the kernel is stored in /boot/vmlinuz, if it's /vmlinuz then change to hda3 instead of hda1 in the first argument.
Oh, and make sure you build FILO with reiserfs support if the kernel is on your root partition.
//Peter
-- coreboot mailing list coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot