Then running make again will build filo.elf, the ELF boot image of FILO.

+

−

$ make

+

−

Use filo.elf as your payload of coreboot, or a boot image for

+

Before you can build FILO, you have to build libpayload. If your filo directory is located inside the coreboot/payloads directory, you don't have to do anything special. If for some reason you want to compile FILO of the coreboot/payloads directory, you will need to tell the makefile where libpayload is. Open filo/Makefile in your favorite text editor and change this line

−

[[Etherboot]].

+

−

If you enable MULTIBOOT_IMAGE option in Config, you can

+

export LIBCONFIG_PATH := $(src)/../libpayload

−

also boot filo.elf from GNU GRUB or other Multiboot bootloader.

+

−

This feature is intended for testing or development purpose.

+

−

== Credits ==

+

to match the location of the libpayload directory on your system:

−

This software was originally developed by SONE Takeshi <ts1@tsn.or.jp> and is now maintained by [mailto:stepan@coresystems.de Stefan Reinauer].

This is a quick guide for getting coreboot up and running on the Arima HDAMA dual Opteron mainboard. If there are blanks to be filled in, go ahead and either ask on the [[Mailinglist|coreboot mailing list]] or you can reach me at cro_marmot_at_comcast.net. -- David Hendricks

+

−

Quick coreboot install guide for HDAMA,

+

$ make menuconfig

−

David W. Hendricks, May 13 2004

+

−

Requirement: Kernel with framebuffering either in an initrd or compiled

+

This will run menuconfig twice -- the first time for libpayload, the second time for FILO.

To boot a CD-ROM or DVD you only need to specify the drive '''without a partition number'''. For example to boot to the primary drive on the secondary IDE channel you would use '''hdc''' and not '''hdc1''' in FILO.

To boot a CD-ROM or DVD you only need to specify the drive '''without a partition number'''. For example to boot to the primary drive on the secondary IDE channel you would use '''hdc''' and not '''hdc1''' in FILO.

−

If you are using FILO with '''USE_GRUB = 1''', and want to boot to your Linux install disk you have to do a mixture of GRUB and FILO commands.

+

=== Grub-like Interface ===

+

If you are using FILO with '''CONFIG_USE_GRUB''', and want to boot to your Linux install disk you have to do a mixture of GRUB and FILO commands.

Like GRUB you have to append a kernel (and parameters), then an initrd, and give a boot command.

Like GRUB you have to append a kernel (and parameters), then an initrd, and give a boot command.

Requirements

Only the x86 (x64) architecture is currently supported. Some efforts have
been made to get FILO running on PPC. Contact the coreboot mailinglist
for more information.

Recent version of GNU toolchain is required to build.

We have tested with Debian/woody (gcc 2.95.4, binutils 2.12.90.0.1,
make 3.79.1), Debian/sid (gcc 3.3.2, binutils 2.14.90.0.6,
make 3.80) and different versions of SUSE Linux from 9.0 to 11.0.

FILO will use the coreboot crossgcc if you have it built and it can be found.

FILO uses coreboot's libpayload. It is easiest to locate and build FILO in the coreboot/payloads directory.

Building on 64-bit OS specifics

If you will be building FILO on AMD64 platform for Debian install the gcc-multilib package.

x64/AMD64 machines work fine when compiling FILO in 32-bit mode.
(coreboot uses 32-bit mode and Linux kernel does the transition to 64-bit mode)

Preparation

Before you can build FILO, you have to build libpayload. If your filo directory is located inside the coreboot/payloads directory, you don't have to do anything special. If for some reason you want to compile FILO of the coreboot/payloads directory, you will need to tell the makefile where libpayload is. Open filo/Makefile in your favorite text editor and change this line