Nicolas <[EMAIL PROTECTED]> writes: > hello, > > - I almost manage to boot my system with ramdisk but I still have an > error :
Hmm. Do you have initrd support compiled into your kernel? Without the rest of the kernel boot messages it is hard to see if the initial ramdisk was seen. > > Kernel command line: root=/dev/rd/0 init=linuxrc console=ttyS0,115200 > > . > . > . > > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > Floppy drive(s): fd0 is 1.44M > FDC 0 is a post-1991 82077 > VFS: Cannot open root device "rd/0" or 01:00 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 01:00 > > I guess I don't tell the kernel to use initrd or maybe I don't use good > options to launch mkelfimage : > > > mkelfimage --kernel=/usr/src/linux/vmlinux --ramdisk=initrd.gz > --output=myelf > > > Do I need to add options ? What is wrong ? > ( In fact, I don't exactly know how to tell the kernel to use initrd > through mkelfimage ). That should work. I usually provide a command line as well. It looks like you have specified that somewhere else. Hmm. root=/dev/ram0 may be a better specification for root. I don't know that I have ever used /dev/rd/0. > - Another question : I don't manage to make an elf image with a bzImage > ( when I burn my elf image, when linuxbios jump to kernel, but nothing > ...), only a vmlinux image boots. is bzImage supported ? Hmm. Which version are you using? bzImage should work with 1.6 though I don't test it often. Most often I use: arch/i386/boot/compressed/bvmlinux Which is just the bzImage in ELF format before it is fully processed with a boot sector and other pieces. Eric
