Syslinux - Mar 2002 - Syslinux & DiskonChip 2000 boo error.

Good afternoon.

I am trying to make a 32M DiskonChip2000 boot Linux (kernel version 2.2.20)
but I'm having difficulty.

It begins fine, loading most of the kernel, but halts immediately after the
"Freeing unused kernel memory: 52K freed." step.  The implication
seems to
be that my ramdisk is not being mounted/executed properly.

My syslinux.cfg file is as follows:

timeout=0
default=vmlinuz
append initrd=initrd.gz root=/dev/ram ramdisk_size=8192 boot=/dev/msys/fla1

I'd appreciate any assistance you could give me on the matter.

Mario Di Giacomo
Anteon, Inc.

Hi, I'm using syslinux to boot an embedded Linux system. I've just
started
working on this and am having a problem with the kernel I'm using not
being able to mount the root device. I'm using a 2.4.17 kernel and running
off a small hardisk with msdos filesystem. I'm trying to boot the system
into a ram disk and run out of ram.

My syslinux.cfg file is:

timeout 0
default vmlinuz
append "load_ramdisk=1 initrd=initrd.gz initrd_archive=minix
                           ramdisk_size=8192 root=/dev/ram0"


where the append line is all one line.

I compile the kernel on a machine in which the root disk is /dev/hda1.
When I examine the kernel I'm using with rdev, it shows the root device as
/dev/hda1. I was expecting that the append line with "root=/dev/ram0"
in
the syslinux.cfg file would override the root device in the kernel, but
this apparently isn't happening. When I set the root device in the kernel
to '/dev/ram0', then the kernel finds the root device and my system
boots
normally. Do I have to set the root device in the kernel with rdev when
using syslinux as the boot loader?

Thanks...