On Feb 20, 2008 1:09 PM, tomy <tomy@xxxxxxxxxxxx> wrote:
It seems that your third partition, which is supposed to have the root filesystem image, is not properly configured for the bootloader to see it .
"No init found" is a typical error which occurs when , after the kernel is loaded, it tries to enter userspace through the first process, viz. init.
Another thought that comes to mind is where for some reason the root filestsytem is mounted read-only.
Thanks,
Raseel
www.opensourcedeal.com
Hello,
I have written this file
system on a particular sector in the NAND flash. I have made three
partitions in Linux , and the third partition is starting from where i
wrote the JFFS2 file system. I have given the kernel parameter as
*mem=64M console=ttyS0,115200 noinitrd root=/dev/mtdblock3 rw
rootfstype=jffs2. *During Linux kernel boot up, it is creating 3
partitions ,but at the end it is giving a kernel panic. The boot process
is given below
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option to
kernel.
Please give me workaround to solve this..
It seems that your third partition, which is supposed to have the root filesystem image, is not properly configured for the bootloader to see it .
"No init found" is a typical error which occurs when , after the kernel is loaded, it tries to enter userspace through the first process, viz. init.
Another thought that comes to mind is where for some reason the root filestsytem is mounted read-only.
Thanks,
Raseel
www.opensourcedeal.com
