public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Kyle Harris <kharris@nexus-tech•net>
Cc: LinuxPPC-embedded list <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: initrd problems
Date: Mon, 22 Jan 2001 14:24:01 -0500	[thread overview]
Message-ID: <3A6C88D1.39BC0E9E@nexus-tech.net> (raw)
In-Reply-To: 3A6C8248.88642C68@matrox.com


Sébastien Côté wrote:
> Ok, now this is exactly what I do.  The initrd doesn't get overwritten
> anymore.  The function mount_root is called, the root device is opened
> but I get a panic at:
>
>         sb = get_super(ROOT_DEV);
>         if (sb) { goto mount_it}
>         ...
>
>         read_unlock(&file_systems_lock);
>         panic("VFS: Unable to mount root fs on %s", kdevname(ROOT_DEV));

You'll also get this error if your kernel has not been built with
support for the filesystem (e.g. ext2) contained on your initrd.

Good luck, Kyle.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-22 19:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-18 15:53 initrd problems Sébastien Côté
2001-01-18 22:27 ` Sébastien Côté
2001-01-18 20:01   ` Matt Porter
2001-01-19 17:22     ` Sébastien Côté
2001-01-20 14:35       ` Matt Porter
2001-01-22 18:56         ` Sébastien Côté
2001-01-22 19:24           ` Kyle Harris [this message]
2001-01-22 20:45             ` Sébastien Côté
2001-01-19  1:13   ` Mark A. Greer
2001-01-19 14:53     ` Sébastien Côté
2001-01-23 21:03       ` Michael Pruznick
  -- strict thread matches above, loose matches on Subject: below --
2002-10-30 16:28 Anders Blomdell
2002-10-30 16:47 ` Wolfgang Denk
2003-04-24  5:32 Sriram Narasimhan
2003-04-24  7:35 ` Wolfgang Denk

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=3A6C88D1.39BC0E9E@nexus-tech.net \
    --to=kharris@nexus-tech$(echo .)net \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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