kernel boot problems

kernel boot problems

[Ryan Hairyes]

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/

Re: kernel boot problems

[Joe deBlaquiere]

A few things come to mind:

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/

Re: kernel boot problems

[Derek Benson]

 Ryan> Hello all,

Hi

 Ryan> I was wondering if someone might be able to help me.  I have
 Ryan> just compiled my kernel and set it up on a floppy to boot off a
 Ryan> disk.  I have it then use an image file to uncompress and get
 Ryan> the filesystem off ,etc.  Well when it boots it says it has
 Ryan> uncompressed the filesystem image and then gives me this:
 Ryan> Mounted Root (ext2 filesystem) readonly Freeing unused kernel
 Ryan> memory: 212K freed Warning: unable to open an initial console
 Ryan> Kernel panic: no init found. Try passing init= option to the
 Ryan> kernel.

 Ryan> I know that I have init on the image, so what could I be doing
 Ryan> wrong.  It is probably something stupid that I am overlooking,
 Ryan> but I thank you in advance.

This is commonly seen when your /etc/fstab is pointing to the wrong partion
for root, or (I believe) on some older kernels where the location of the root
partition is contained within the kernel or on the boot sector somewhere.
(Forgive me for not being more explicit my memory fails me) Try man rdev
for changeing these values. 

Of course as someone else has noted there could be other reasons, but if
you are looking for something 'stupid' (believe me I've done this before 
too) then this could be it.  

Try passing 'root=/dev/hda2' or whatever (without the '') to the kernel
at the boot prompt:

lilo: linux root=/dev/hda1 single

Replace linux above with the alias of your kernel.

If you don't know what partiion root is on you can always cycle through
the partitions consecutively.  (I've done this before when breaking into
linux boxes that I didn't build but had the job of maintaining).

Once you have booted into single mode you can edit /etc/fstab to point to 
the right place.  Or else if thats correct just boot up with linux root=blah
and you'll be up and running!

Hope this helps.

derek
-
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/

Re: kernel boot problems

[Andre Hedrick]

Maybe try enabling ATA/IDE driver as the configuration at compile time has
changed.  Using an old 2.2 '.config' will fail to enable the subsystem.
However using a 2.4'.config' on a 2.2 compile will generally succeed in
90% of the flags.

Cheers,

On Sun, 28 Jan 2001, Derek Benson wrote:

>  Ryan> Hello all,
> 
> Hi
> 
>  Ryan> I was wondering if someone might be able to help me.  I have
>  Ryan> just compiled my kernel and set it up on a floppy to boot off a
>  Ryan> disk.  I have it then use an image file to uncompress and get
>  Ryan> the filesystem off ,etc.  Well when it boots it says it has
>  Ryan> uncompressed the filesystem image and then gives me this:
>  Ryan> Mounted Root (ext2 filesystem) readonly Freeing unused kernel
>  Ryan> memory: 212K freed Warning: unable to open an initial console
>  Ryan> Kernel panic: no init found. Try passing init= option to the
>  Ryan> kernel.
> 
>  Ryan> I know that I have init on the image, so what could I be doing
>  Ryan> wrong.  It is probably something stupid that I am overlooking,
>  Ryan> but I thank you in advance.
> 
> This is commonly seen when your /etc/fstab is pointing to the wrong partion
> for root, or (I believe) on some older kernels where the location of the root
> partition is contained within the kernel or on the boot sector somewhere.
> (Forgive me for not being more explicit my memory fails me) Try man rdev
> for changeing these values. 
> 
> Of course as someone else has noted there could be other reasons, but if
> you are looking for something 'stupid' (believe me I've done this before 
> too) then this could be it.  
> 
> Try passing 'root=/dev/hda2' or whatever (without the '') to the kernel
> at the boot prompt:
> 
> lilo: linux root=/dev/hda1 single
> 
> Replace linux above with the alias of your kernel.
> 
> If you don't know what partiion root is on you can always cycle through
> the partitions consecutively.  (I've done this before when breaking into
> linux boxes that I didn't build but had the job of maintaining).
> 
> Once you have booted into single mode you can edit /etc/fstab to point to 
> the right place.  Or else if thats correct just boot up with linux root=blah
> and you'll be up and running!
> 
> Hope this helps.
> 
> derek
> -
> 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/
> 

Andre Hedrick
Linux ATA Development

-
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/