All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Derek Benson <derek@borogoves.yi.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel boot problems
Date: Sat, 27 Jan 2001 16:49:25 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10101271646210.25130-100000@master.linux-ide.org> (raw)
In-Reply-To: <200101280014.f0S0E4702435@borogoves.yi.org>


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/

  reply	other threads:[~2001-01-28  0:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-28  0:14 kernel boot problems Derek Benson
2001-01-28  0:49 ` Andre Hedrick [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-28  2:20 Kernel " Bernard Mentink
2011-07-28 11:22 ` Gary Thomas
2011-07-28 12:51   ` Andrea Adami
2011-07-28 20:51   ` Bernard Mentink
2011-07-28 21:39     ` Gary Thomas
2011-07-28 22:10       ` Bernard Mentink
2011-07-28 22:41         ` Gary Thomas
2011-07-28 23:03           ` Bernard Mentink
2011-07-29  1:18           ` Bernard Mentink
2011-07-29  1:41             ` Bernard Mentink
2011-07-29  4:07               ` Charles Manning
2011-07-31 20:57                 ` Bernard Mentink
2011-07-28 15:47 ` Daniel Smith
2001-01-27 20:58 kernel " Ryan Hairyes
2001-01-27 21:46 ` Joe deBlaquiere

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.10.10101271646210.25130-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=derek@borogoves.yi.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.