Filo Error Help
daubin at actuality-systems.com
Fri Jul 9 06:57:00 CEST 2004
Both his kernel and my kernel work, it is the initrd that fails.
Also, note that my same elf image works fine in etherboot. So
this disproves your /etc/fstab & vt support theory.
I think it is a configuration problem with filo, but I do not know
what to change. I have the filo drop off of etherboot 5.2.4.
Do I need to modify ram storage for filo someplace?
Here is my filo config:
# !!! NOTE !!!
# Do NOT add spaces or comments at the end of option lines.
# It confuses some versions of make.
# Image filename for automatic boot and optional command line parameter
#AUTOBOOT_FILE = "hda3:/boot/vmlinuz root=/dev/hda3 console=tty0
#AUTOBOOT_FILE = "hda2:/boot/vmlinuz initrd=/boot/initrd ro
root=/dev/hda2 console=tty0 console=ttyS0,115200"
#AUTOBOOT_FILE = "mem at 0xfff80000"
#AUTOBOOT_FILE = "hde1 at 0"
AUTOBOOT_FILE = "uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf"
# Time in second before booting AUTOBOOT_FILE
AUTOBOOT_DELAY = 2
# Driver for hard disk, CompactFlash, and CD-ROM on IDE bus
IDE_DISK = 1
# Driver for USB disk
USB_DISK = 1
# To make filo.zelf < 32 k, You may not enable JFS, MINIX, XFS
# Is anyone still using these file system? BY LYH
FSYS_EXT2FS = 1
FSYS_FAT = 1
#FSYS_JFS = 1
#FSYS_MINIX = 1
FSYS_REISERFS = 1
#FSYS_XFS = 1
FSYS_ISO9660 = 1
# Support for boot disk image in bootable CD-ROM (El Torito)
ELTORITO = 1
# PCI support
SUPPORT_PCI = 1
#DEBUG_ALL = 1
#DEBUG_ELFBOOT = 1
#DEBUG_ELFNOTE = 1
#DEBUG_LINUXBIOS = 1
#DEBUG_MALLOC = 1
#DEBUG_MULTIBOOT = 1
#DEBUG_SEGMENT = 1
#DEBUG_SYS_INFO = 1
#DEBUG_TIMER = 1
#DEBUG_BLOCKDEV = 1
#DEBUG_PCI = 1
#DEBUG_LINUXLOAD = 1
#DEBUG_IDE = 1
#DEBUG_USB = 1
#DEBUG_ELTORITO = 1
# i386 options
# Loader for standard Linux kernel image, a.k.a. /vmlinuz
LINUX_LOADER = 1
# Boot FILO from Multiboot loader (eg. GRUB)
# You need to modify i386/multiboot.c to use it. change mmrange to
# By LYH
#MULTIBOOT_IMAGE = 1
# Use PCI Configuration Mechanism #1 (most boards)
PCI_CONFIG_1 = 1
On Thu, 2004-07-08 at 19:05, Hendricks David W. wrote:
> Looks more like a Linux config problem. Double check your /etc/fstab and
> make sure the root partition entry is correct and that you have virtual
> terminal (VT) support enabled in your kernel.
> On Thu, 8 Jul 2004, David Aubin wrote:
> > Hi,
> > With your elf I get the following:
> > boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
> > LinuxLabs USB bootloader
> > New USB device, setting address 2
> > 00000008:00000006:00000050
> > Manufacturor: Kingston
> > Product: DataTraveler2.0
> > Serial: 07B1F140E000617B
> > Found USB block device 2
> > Mounted reiserfs
> > errnum=15
> > boot: uda1:/ram.elf
> > Loading Linux version 2.6.5 (root at tst288xsuse9) #11 SMP Mon May 10
> > 14:58:17 PDT 2004...
> > Jumping to entry point...
> > DFA Just before C's xstart32
> > Firmware type: LinuxBIOS
> > old bootloader convention, maybe loadlin?
> > Bootdata ok (command line is root=/dev/ram0 rw console=tty0
> > console=ttyS0,115200n8)
> > .
> > .
> > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> > loop: loaded (max 8 devices)
> > .
> > .
> > usb 2-3: new full speed USB device using address 2
> > scsi4 : SCSI emulation for USB Mass Storage devices
> > Vendor: Kingston Model: DataTraveler2.0 Rev: 4.70
> > Type: Direct-Access ANSI SCSI revision: 02
> > SCSI device sda: 1019392 512-byte hdwr sectors (522 MB)
> > sda: assuming Write Enabled
> > sda: assuming drive cache: write through
> > sda: sda1
> > Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0
> > NET: Registered protocol family 2
> > IP: routing cache hash table of 2048 buckets, 32Kbytes
> > TCP: Hash tables configured (established 65536 bind 65536)
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > RAMDISK: Compressed image found at block 0
> > RAMDISK: incomplete write (-28 != 1) 16777216
> > crc error
> > EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
> > VFS: Mounted root (ext2 filesystem).
> > Freeing unused kernel memory: 472k freed
> > Kernel panic: No init found. Try passing init= option to kernel.
> > This makes me feel a little better as it appears it is something
> > in my etherboot-filo configuration perhaps?
> > On Thu, 2004-07-08 at 17:53, YhLu wrote:
> > > I wonder if it is after gzip or before gzip.
> > >
> > > -----Original Message-----
> > > From: ron minnich [mailto:rminnich at lanl.gov]
> > > Sent: Thursday, July 08, 2004 2:44 PM
> > > To: David Aubin
> > > Cc: YhLu; LinuxBIOS
> > > Subject: RE: Filo Error Help
> > >
> > > On Thu, 8 Jul 2004, David Aubin wrote:
> > >
> > > > If so could it be a size issue? My initrd is 8Meg.
> > >
> > > oh!
> > >
> > > did you config the kernel for that? default is 4M.
> > >
> > > ron
> > _______________________________________________
> > Linuxbios mailing list
> > Linuxbios at clustermatic.org
> > http://www.clustermatic.org/mailman/listinfo/linuxbios
More information about the coreboot