trevor wrote:

> i agree with what Mirko has to say on this.
>
> the boot device is described to the kernel in the form of a number. if you
> look in the file $KERNEL_SOURCE/init/main.c you'll see a listing of these
> numbers and the devices they represent; search for the variable
> "root_dev_names". for example "/dev/hda" is 0x0300, "/dev/hda1" would be
> 0x0301, and so forth. nfs is actually 0x00ff. 0x0100 is ram0 so my assumption
> is that 0x0101 is ram1.

Yes, you are right.

> did you enable ram disk support and initrd (under block devices) in your
> kernel?

Yes, both are marked "y"

> at the very end of compiling a kernel, the build system will usually tell you
> what root device has been set as the default in the kernel. also, look in the
> kernel's top-level "Makefile", search for the variable "ROOT_DEV". the
> comments in the instructions above that variable tell you what you can do
> with it.

now it is "current"

> smarter boot loaders (like lilo) will allow you to specify the root device
> which it can then pass on to the kernel as it boots. consult your boot loader
> documentation (i.e. lilo documentation) if that's what you're using. the
> simple "linux loader" boot loader that i'm using which comes with my zflinux
> system only knows how to tell the kernel that the disk is a ramdisk, ram0.
> this is the only device that can be used with this bootloader and i don't
> have any way to change it.

Lilo is used with kernel 2.4.2-3


The system is Redhat 7.1 with kernel 2.4.2-3.
And the lilo.conf is :

boot=/dev/hda
map=/mnt/flash/boot/map
install=/mnt/flash/boot/boot.b
image=/mnt/flash/boot/vmlinuz-2.4.2-3
              ramdisk=40000
              label=flash
              root=/dev/ram
              initrd=/mnt/flash/boot/initrd.img.gz
image=/mnt/flash/boot/vmlinuz-2.4.2-3
              ramdisk=40000
              label=normal
              root=/dev/hdb7
              read-only




My system works well when I choose the normal mode in lilo.conf.
Only "flash mode" using ramdisk does not work.
I found this kernel panic problem and there are few answers.

One funny thing, I do not have this error and my system load linux well a few
times.
I do not know why I did not have.

Please help me.

Regards,
Bokyun Na



--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.

Reply via email to