From: "Brian T" <btuch@usa.net>
To: <linux-mtd@lists.infradead.org>
Subject: Re: 2.6.x nettel.c compile problems
Date: Fri, 2 Jul 2004 11:58:27 -0500 [thread overview]
Message-ID: <040801c46055$cbfae280$fd0ba8c0@briantpc> (raw)
In-Reply-To: 03c201c46041$57b3fa10$fd0ba8c0@briantpc
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Kernel panic: VFS: Unable to mount root fs on mtdblock1
>
> I also tried enabling INITRD without the headers I added at the top, but
> with the same result.
>
I added some debugging output to do_mounts.c and got this on boot:
Loading................................................................
Linux version 2.6.2 (root@FedoraCore1) (gcc version 3.3.2 20031022 (Red Hat
Linux 3.3.2-1)) #35 Fri Jul 2 11:20:05 CDT 2004
.......
Linux Kernel Card Services
options: [pci] [cardbus]
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
......
VFS: name=/dev/root, p=ext2, root_mount_data=<NULL>, err=-22,
VFS: name=/dev/root, p=minix, root_mount_data=<NULL>, err=-22,
Kernel panic: VFS: Unable to mount root fs on mtdblock1
Now, I have JFFS2 support compiled into the kernel. Any ideas on why it is
only trying to mount the root fs as ext2 or minix? I use ext2 for a ram
disk, and minix is used for 128k BRAM.
Any help is appreciated.
-Brian
next prev parent reply other threads:[~2004-07-02 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 14:32 2.6.x nettel.c compile problems Brian T
2004-07-02 16:58 ` Brian T [this message]
2004-07-02 17:28 ` Josh Boyer
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='040801c46055$cbfae280$fd0ba8c0@briantpc' \
--to=btuch@usa.net \
--cc=linux-mtd@lists.infradead.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