public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Sunil Naidu <akula2.shark@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.6.20-rc4 - Kernel panic!
Date: Thu, 11 Jan 2007 23:57:06 +0100 (CET)	[thread overview]
Message-ID: <tkrat.f1956029d478404e@s5r6.in-berlin.de> (raw)
In-Reply-To: <8355959a0701111329t506ba4e6g993400ea31d47b3e@mail.gmail.com>

Sunil Naidu wrote:
> I meant to ask choosing (from Xconfig tree)  a driver as module has
> same affect compare to compiling a driver as kernel builtin feature?
> (while loading/booting of kernel)

No, it hasn't quite the same effect:

>> Modules have to be loaded from a filesystem while built-in features are
>> available from the start.

...
> I did check the distro .config file (2.6.18-1.2868.fc6). Even I have
> changed the my .config files according to the distro's. Even after
> that, same error message.

Check if you also built the initrd the same way as the distributed one,
i.e. examine their contents. If it was, try booting an own kernel and
initrd built from FC6's 2.6.18-* sources. If that fails too, build a
kernel with all drivers compiled in which you know you need to access
the root FS. If that kernel still fails to mount the root FS, look for
any earlier error messages in the boot sequence.
-- 
Stefan Richter
-=====-=-=== ---= -=-==
http://arcgraph.de/sr/


  reply	other threads:[~2007-01-11 22:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11 11:00 Linux-2.6.20-rc4 - Kernel panic! Akula2
2007-01-11 18:28 ` Stefan Richter
     [not found]   ` <8355959a0701111211m416e202bx637bca22f8fca826@mail.gmail.com>
2007-01-11 21:08     ` Stefan Richter
2007-01-11 21:29       ` Sunil Naidu
2007-01-11 22:57         ` Stefan Richter [this message]
2007-01-11 18:32 ` Randy Dunlap
2007-01-11 20:25   ` Sunil Naidu
2007-01-11 21:38     ` Randy Dunlap

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=tkrat.f1956029d478404e@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akula2.shark@gmail.com \
    --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