From: Vipin Malik <vipin.malik@daniel.com>
To: joakim.tjernlund@lumentis.se
Cc: mtd@infradead.org
Subject: Re: JFFS2 as root FS
Date: Wed, 18 Apr 2001 12:11:39 -0500 [thread overview]
Message-ID: <3ADDCACB.15BF0590@daniel.com> (raw)
In-Reply-To: 001001c0c826$63b43200$0a01a8c0@Win1
Joakim Tjernlund wrote:
> Hi there
>
> Has anybody managed to get a root FS with JFFS2 to work?
Sure! But as you say that you followed the HOWTO, and since I wrote the
HOWTO,
I guess that something in my procedures tripped you up that worked ok for
me :)
>
> I followed the mtd howto and I have a root partition(with the necessary
> files) and
> all I get is: "Kernel panic: I have no root and I want to scream"
> message.
Hmm, what kernel version are you using? I've never seen that message (I've
seen Kernel panic: Unable to open root..blah blah..)
>
>
> first I tried to use "rdev zvmlinux /dev/mtdblock1", but
> the kernel ignored that an did a NFS mount as usual.
Wait, wait, wait. What do you mean by this? This is *a problem* right
here.
Why is it doing a NFS mount? Please describe your config and what you are
trying to do.
"usual" kernels don't NFS mount their root fs!
> I then
> specified on the kernel commad line: root=/dev/mtdblock1
> and the I got the kernel panic above.
Well, the kernel may not be able to understand the "mtdblock1" device by
name unless you patched
the init/main.c file to list a conversion table from mtdblockxx to a
*device number*.
>
>
> Any Ideas?
These are some.
Vipin
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-04-18 17:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 16:42 A pair of stupid questions, I hope Ian S. Nelson
2001-04-17 22:11 ` David Woodhouse
2001-04-18 0:04 ` Ian S. Nelson
2001-04-18 8:02 ` David Woodhouse
2001-04-18 16:41 ` JFFS2 as root FS Joakim Tjernlund
2001-04-18 16:50 ` David Woodhouse
2001-04-18 17:00 ` Joakim Tjernlund
2001-04-18 17:05 ` David Woodhouse
2001-04-18 18:58 ` Joakim Tjernlund
2001-04-18 17:11 ` Vipin Malik [this message]
2001-04-18 19:24 ` Joakim Tjernlund
2001-04-18 20:19 ` Vipin Malik
2001-04-18 22:00 ` Joakim Tjernlund
2001-04-19 8:28 ` Florian Schirmer / TayTron
2001-04-19 10:26 ` Joakim Tjernlund
2001-04-19 13:02 ` Florian Schirmer / TayTron
2001-04-19 12:45 ` Joakim Tjernlund
2001-04-19 13:02 ` David Woodhouse
2001-04-19 14:55 ` Nicolas Pitre
2001-04-19 16:44 ` Vipin Malik
2001-04-19 19:59 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2001-04-18 20:33 Williams, Kevin M.
2001-04-19 13:44 mkfs.jffs2 again Joakim Tjernlund
2001-04-19 13:52 ` David Woodhouse
2001-04-19 20:06 ` JFFS2 as root FS Joakim Tjernlund
2001-04-20 16:26 ` David Woodhouse
2001-04-21 8:07 ` Joakim Tjernlund
2001-04-21 11:22 ` David Woodhouse
2001-04-21 20:22 ` Joakim Tjernlund
2001-04-23 1:52 ` David Schleef
2001-04-23 6:15 ` Joakim Tjernlund
2001-04-23 9:28 ` Joakim Tjernlund
2001-04-23 9:31 ` David Woodhouse
2001-04-23 11:00 ` David Schleef
2001-04-23 11:04 ` David Woodhouse
2001-04-24 1:56 ` David Schleef
2001-04-21 12:08 ` David Woodhouse
2001-04-21 20:14 ` Joakim Tjernlund
2001-04-21 22:18 ` David Woodhouse
[not found] <3AE43929.3695C91D@daniel.com>
2001-04-24 12:22 ` Joakim Tjernlund
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=3ADDCACB.15BF0590@daniel.com \
--to=vipin.malik@daniel.com \
--cc=joakim.tjernlund@lumentis.se \
--cc=mtd@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