[coreboot] Filo Issues on LX-800

mark wolfe markw at wolfenet.org
Thu Jan 17 17:53:29 CET 2008

Ok, experiencing a couple issues with Filo.

This is on a Kino LX-800 mini ATX board.
Which is basically a PB800 with ALI/ULI sata raid on board.

First is where it runs through the devices.

pci_init: 00:01.0 1022:2080 0600 00
pci_init: 00:01.1 1022:2081 0300 00
pci_init: 00:01.2 1022:2082 1010 00
pci_init: 00:0e.0 10ec:8139 0200 00
pci_init: 00:0f.0 1022:2090 0601 00
pci_init: 00:0f.2 1022:209a 0101 80
pci_init: 00:0f.3 1022:2093 0401 00
pci_init: 00:0f.4 1022:2094 0c03 10
pci_init: 00:0f.5 1022:2095 0c03 20
pci_init: 00:10.0 10ec:8139 0200 00
pci_init: 00:11.0 10b9:5281 0180 85
pci_init: 00:11.1 10b9:5228 0180 85

Device 0f.0 is the 5536 IDE.
Device 11.0 is the Sata controller.

Filo wants to treat the Sata controller as IDE 0, while I was trying to 
get this thing to run off the 5536 and ignore the Sata drives.  Since 
the 5536 is found first, you'd think it'd boot off the 5536.

Second is once I setup a sata drive with a debian minimal install, all 
one EXT2/3 partition with filo pointing at hda1:/boot/grub/menu.lst
Filo reads the menu.lst and goes after the kernel, which tells me the 
drive was ready.

The stock kernel refuses to load though.  Here's the output I'm getting.

Mounted ext2fs
malloc_diag: alloc: 192 bytes (3 blocks), free: 16184 bytes (1 blocks)
malloc_diag: alloc: 288 bytes (4 blocks), free: 16088 bytes (1 blocks)
malloc_diag: alloc: 304 bytes (5 blocks), free: 16072 bytes (1 blocks)
file_open: dev=hda1, path=/boot/vmlinuz-2.6.18-4-486
devopen: already open
malloc_diag: alloc: 288 bytes (4 blocks), free: 16088 bytes (1 blocks)
elf_load: Not a bootable ELF image
Unsupported image format

Here's the grub menu.lst from a default debian 4.0 base install.

## ## End Default Options ##

title           Debian GNU/Linux, kernel 2.6.18-4-486
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.18-4-486 root=/dev/sda1 ro
initrd          /boot/initrd.img-2.6.18-4-486

title           Debian GNU/Linux, kernel 2.6.18-4-486 (single-user mode)
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.18-4-486 root=/dev/sda1 ro single
initrd          /boot/initrd.img-2.6.18-4-486


The guys on IRC were saying that the stock kernel should load, yet filo 
doesn't think it's valid.   Any help would be appriciated.   I'd like to 
have it booting off the 5536 so I could use a compact flash, and then 
I'd also like to know why filo thinks the stock kernel is an invalid 
image.   It's pointing right at the kernel, no symlinks or anything.

Mark Wolfe

More information about the coreboot mailing list