public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Todor Todorov <ttodorov@web.de>
To: "Drew P. Vogel" <dvogel@intercarve.net>
Cc: "J.S.S" <jss@pacbell.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel reboot problem
Date: Thu, 07 Feb 2002 06:05:44 +0100	[thread overview]
Message-ID: <3C620B28.6010902@web.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0202062344120.32081-100000@northface.intercarve.net>

Drew P. Vogel wrote:

>What does the initrd= line do, and how does initrd-2.4.17-10.img get in
>/boot?
>
It's a compressed file containing the compiled modules which is needed 
if a driver should be initialized before mounting the root file system, 
eg a driver for the root system. As it is in the 2.4.7 image section it 
refers only to the 2.4.7 kernel and not 2.4.18 (or whatever he tries to 
compile).

And speaking of it - J.S.S., did you take the options from the Red Hat's 
stock kernel as an example to choose your options? (From your mail I 
recon that this is one of your first attempts to compile an own kernel, 
am I correct?) If you did that, you rpobably included the fs driver for 
your root system as a module and not hardlinked in the kernel - just as 
Red Hat does? In such case you would need either to provide an initrd 
image too (`man initrd`), or recompile your kernel with the driver for 
the root filesystem ( ext2 or/and ext3 or reiserfs, don't know how you 
formated your linux partition(s) ) with <y> as option for it instead of 
<m>.....

Stupid me for not suggesting to check that in the first mail :-/

Hope you will locate the error quickliy.

Cheers 

-- 

Todor Todorov           <ttodorov@web.de>
Networkadministration   <todor.todorov@skr-skr.de>
SKR GmbH & Co. KG       http://www.skr-skr.de

-----------------
"Only two things are infinite, the universe and the
 human stupidity, and I'm not sure about the former"
                               - Einstein




  reply	other threads:[~2002-02-07  5:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 22:27 Kernel reboot problem J.S.S.
2002-02-07  1:21 ` Todor Todorov
2002-02-07  4:44 ` Drew P. Vogel
2002-02-07  5:05   ` Todor Todorov [this message]
2002-02-07 15:13     ` Drew P. Vogel
2002-02-07 15:41       ` Drew P. Vogel
2002-02-21 17:53         ` Kernel reboot problem [solved] J.S.S.
2002-02-21 15:56       ` Kernel reboot problem J.S.S.

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=3C620B28.6010902@web.de \
    --to=ttodorov@web.de \
    --cc=dvogel@intercarve.net \
    --cc=jss@pacbell.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox