1. Is your init statically linked or linked with shared libraries? If
it's shared, do you have all the shared objects on your disk image in a
place where they can be found (/lib, I hope)? You might try linking it
statically (but stripped) just to make sure.
2. Is it in the path that the kernel is looking in? check init/main.c to
see what your kernel is looking for (it's some educational reading anyway).
3. Even if 'init' isn't found, it should try to run /bin/sh as a last
resort. I can't imagine you don't have one of those.
4. Is init executable?
5. "unable to open an initial console" probably means you don't have the
necesary device nodes (refer to init/main.c)
6. If this doesn't help, there is a ramdisk FAQ that is well written...
Good luck with it!
Joe
Ryan Hairyes wrote:
> Hello all,
>
> I was wondering if someone might be able to help me.
> I have just compiled my kernel and set it up on a floppy
> to boot off a disk. I have it then use an image file to uncompress
> and get the filesystem off ,etc. Well when it boots it says it has
> uncompressed the filesystem image and then gives me this:
> Mounted Root (ext2 filesystem) readonly
> Freeing unused kernel memory: 212K freed
> Warning: unable to open an initial console
> Kernel panic: no init found. Try passing init= option to the kernel.
>
> I know that I have init on the image, so what could I be doing wrong.
> It is probably something stupid that I am overlooking, but I thank you in
> advance.
>
> Ryan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/