From: "HappyPhot" <happyphot@gmail.com>
To: "David Jander" <david.jander@protonic.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: VFS: Cannot open root device "31:03" or unknown-block(31,3)
Date: Fri, 6 Jan 2006 22:09:53 +0800 [thread overview]
Message-ID: <002e01c612ca$f7614a80$0760120a@photon> (raw)
In-Reply-To: 200601050852.45616.david.jander@protonic.nl
> in your .config:
>
>> CONFIG_JFFS2_FS=m
>
> This is wrong. You have to choose "y", not "m" (for module).
> This way jffs2 is compiled as a module. That means, that jffs2 filesystem
> will
> not be available until the module is loaded with "insmod jffs2" of
> something
> similar. That in turn means that your system has to start up first in
> order
> to be able to do this, but since you can't start because your root
> filesystem
> is on jffs2, you have created yourself a "chicken and egg" problem.
> If you choose "y" then jffs2 support will be compiled into the kernel, and
> thus be available before booting.
Hi, David,
Yes, you are right. After changing it to 'y', the " VFS: Cannot open
root..."
message was gone. I'm so happy and thank you very much.
Now it is another problem again. (something like: Oops: kernel access of
bad
area. sig:11...). I am going to check what happened.
>
> In your bootlog:
>
>> Linux version 2.6.14.2 (happy@sddlinux1) (gcc version 3.3.3 (DENX ELDK
>> 3.1.1
>> 3.3.3-10)) #29 Sun Jan 1 22:34:28 CST 2006
>> Motorola SPS Sandpoint Test Platform
>
> I see you are using DENX ELDK 3.1.1 and a kernel which AFAIK is not
> supported
> by this version of ELDK. Are you sure this is supposed to work? It
> probably
> will, but I don't know what the "Sandpoint" is (it looks like a PowerPC
> processor of the MPC7xx series to me), so I couldn't tell.
Do you know where to get the infomation about which kernel version it
supports?
thank you,
/HappyPhot
next prev parent reply other threads:[~2006-01-06 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 14:48 VFS: Cannot open root device "31:03" or unknown-block(31,3) HappyPhot
2006-01-02 15:57 ` David Jander
2006-01-03 2:48 ` HappyPhot
[not found] ` <200601031410.55884.david.jander@protonic.nl>
[not found] ` <004701c611a8$557dbf00$0760120a@photon>
2006-01-05 7:52 ` David Jander
2006-01-06 14:09 ` HappyPhot [this message]
2006-01-06 14:19 ` David Jander
2006-01-06 15:08 ` Wolfgang Denk
2006-01-09 8:45 ` David Jander
2006-01-09 13:05 ` 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='002e01c612ca$f7614a80$0760120a@photon' \
--to=happyphot@gmail.com \
--cc=david.jander@protonic.nl \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).