"init not found" after booting GRUB on DOC
Dear all,
I followed Karim's book to put the kernel, modules, root filesystem (including busybox and tinylogin) and GRUB on a DOC and tried booting it. The kernel loaded successfully but it ended with a kernel panic of "no init found". I use this statements in my menu.lst:
title DiskOnChip 2000
kernel (dc0,0)/boot/vmlinuz-2.4.21-5x86 ro root=/dev/nftla1
I have busybox's init in /sbin and I also tried adding "init=/sbin/init" to the above statement but with the same result.
The NFTL driver is built-in and it correctly detects my DOC. The kernel also successfully mounts the root filesystem (ext3).
How should I configure GRUB in order to load the busybox's init?
advTHANKSance!
Selwyn
Quoted 8 lines · Selwyn Tang
The kernel loaded successfully but it ended with a kernel panic of
"no init found".I have busybox's init in /sbin and I also tried adding "init=/sbin/init" to the above statement but with the same result.
The NFTL driver is built-in and it correctly detects my DOC. The kernel also successfully mounts the root filesystem (ext3).
Sounds like a problem with the _contents_ of your file system. Does it boot if you use 'init=/bin/sh', and if so, can you then run /sbin/init?
Signature · 1 line
dwmw2
Quoted 2 lines · David Woodhouse
Sounds like a problem with the _contents_ of your file system. Does it boot if you use 'init=/bin/sh', and if so, can you then run
/sbin/init?
I figured out what's the problem: Since I wanted to try out booting with DOC first, I didn't prepare the C library. But my busybox was compiled with dynamically linking, it's init could not be started and resulted in the kernel panic.
Now I compiled busybox with static linking and it works.
Thanks for your help!
Selwyn