From: Fawad Lateef <fawadlateef@gmail.com>
To: "porranenhuma@globo.com" <porranenhuma@globo.com>
Cc: Norbert van Nobelen <norbert@edusupport.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel Panic: VFS cannot open a root device
Date: Mon, 18 Jul 2005 07:46:32 +0500 [thread overview]
Message-ID: <1e62d13705071719462d437a21@mail.gmail.com> (raw)
In-Reply-To: <428C48BA000CBFCB@riosf03.globoi.com>
On 7/18/05, porranenhuma@globo.com <porranenhuma@globo.com> wrote:
> I already done that things , and I still getting these errors ... I dont
> no what to do , and I'm getting desesperated...
>
> '>'
> '>'You should compile in the filesystem (reiserfs?) into the kernel (*
> instead
> '>'of
> '>'M), or put the correct module in initrd (usually done by mkinitrd).
>
> '>'After that run lilo, and it should boot just fine.
> '>'
> '>'Norbert
> '>'
> '>'Op zaterdag 16 juli 2005 20:57, schreef u:
> '>'> > Hi , i have kernel 2.4.29 at slack 10.1 and when I upgrade my kernel
> '>'to
> '>'> > 2.6.11 I get these erros on booting
> '>'> >
> '>'> > VFS: Cannot open a root device "301" or unknow block
> '>'> > please append a correct "root" boot option
> '>'> > KERNEL PANIC : not syncing; VFS; Unable to mount root fs on
> '>'> > unknown-block (3,1)
> '>'> >
> '>'> > I have compiled my kernel with my IDE support and also with my file
> '>'> > system support with built-in option.
> '>'> >
> '>'> > My LILO.CONF
> '>'> > image = /boot/vmlinuz-2.6.11
> '>'> > root = /dev/hda1
> '>'> > label = 2.6.11
> '>'> > initrd = /boot/initrd.gz
> '>'> > read-only
> '>'> >
I saw this prob when my boot device/partition in the bootloader config
was wrong or the filesystem of my root partition is not compiled as a
kernel image rather compiled as module, so plz try to solve this prob
by selecting your desired filesystem in kernel configuration as Y
rather than M ...... I hope this will work
> '>'> > I'm booting with my image of kernel 2.4.29..... i'm 5 days tryng
> to solve
> '>'> > this problem ...
Upgrading from 2.4.xx kernel series to 2.6.xx series what I found is
that the filesystem must be compiled into the kernel image not as a
module b/c in 2.4.xx filesystem compiled as module also work ........
And another thing is that I never succedded in booting the 2.6.xx
kernel __successfully__ compiled from 2.4.xx series (distribution with
default 2.4.xx series kernel like Fedora Core 1 or Redhat Linux 9) and
found that my mouse won't work on 2.6.xx series kernel, but the
distribution with 2.6.xx kernel series by default works fine .....
--
Fawad Lateef
next prev parent reply other threads:[~2005-07-18 2:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200507171016.37940.norbert@edusupport.nl>
2005-07-18 0:27 ` Kernel Panic: VFS cannot open a root device porranenhuma
2005-07-18 2:46 ` Fawad Lateef [this message]
2005-07-18 11:14 ` Ed Tomlinson
2005-07-16 20:57 GlupFire
-- strict thread matches above, loose matches on Subject: below --
2005-07-16 8:41 GlupFire
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=1e62d13705071719462d437a21@mail.gmail.com \
--to=fawadlateef@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=norbert@edusupport.nl \
--cc=porranenhuma@globo.com \
/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