linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "HappyPhot" <happyphot@gmail.com>
To: "David Jander" <david.jander@protonic.nl>,
	<linuxppc-embedded@ozlabs.org>
Subject: Re: VFS: Cannot open root device "31:03" or unknown-block(31,3)
Date: Tue, 3 Jan 2006 10:48:02 +0800	[thread overview]
Message-ID: <00af01c61010$245773b0$0760120a@photon> (raw)
In-Reply-To: 200601021657.35359.david.jander@protonic.nl

> On Monday 02 January 2006 15:48, HappyPhot wrote:
>> Hi,
>>   I've suffered for many days and "google" almost every where.
>> I would like to boot from the flash with jffs2 (i.e. using jffs2 as my
>> root /) . But it alyaws shows:
>> VFS: Cannot open root device..... (whole message is as below)
>>
>>   Anybody knows what may cause this ? Please help and
>> thank you.
>>[...]
>
> You omitted the interesting part of the log output, the bootarguments at 
> the
> very beginning. What is the value of root= ?
> Maybe you made the typical mistake of specifying /dev/mtd3 instead
> of /dev/mtdblock3, or you didn't compile in support for mtd access as a 
> block
> device?
>

Hi, David and all,
  I've tried root=/dev/mtdblock3, root=/dev/mtd3, root=31:03 etc.  And 
"Caching
block device access to MTD devices" was also selected when 'make 
menuconfig'.
The results were the same.
  I use "phys_mapped_flash" and "mtdparts=phys_mapped_flash:2M(k4),2M(k6),
4M(rd),4M(jffs2),-(User_Data)". What is the "root=" I should use ?

  Also, I am wondering how the kernel knows "/dev/mtdblock3" is in my flash 
?
I think I never do any setting about this....

thank you ,
/HappyPhot

  reply	other threads:[~2006-01-03  2:48 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 [this message]
     [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
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='00af01c61010$245773b0$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).