From: "colin" <colin@realtek.com.tw>
To: unlisted-recipients:; (no To-header on input)
Cc: <linux-mips@linux-mips.org>
Subject: Re: [*VIP*] Re: Strange! Cannot use JFFS2 as root
Date: Thu, 21 Oct 2004 11:00:11 +0800 [thread overview]
Message-ID: <007101c4b71a$171bd830$8b1a13ac@realtek.com.tw> (raw)
In-Reply-To: 20041020163048.GC17445@gate.ebshome.net
Hi Eugene,
The Kernel I use is 2.6.4, and I donot see the entry you mentioned.
Regards,
Colin
----- Original Message -----
From: "Eugene Surovegin" <ebs@ebshome.net>
To: "colin" <colin@realtek.com.tw>
Cc: <linux-mips@linux-mips.org>
Sent: Thursday, October 21, 2004 12:30 AM
Subject: [*VIP*] Re: Strange! Cannot use JFFS2 as root
> On Wed, Oct 20, 2004 at 10:02:26PM +0800, colin wrote:
> >
> > Hi all,
> > I had booted up Linux with nfs root, and write a JFFS2 image to
/dev/mtd1.
> > Here is my cmdline for Kernel:
> > go 0x80305018 root=/dev/nfs rw nfsroot=172.19.26.145:/nfs/rootfs
> > ip=172.19.27.193::172.19.27.254:255.255.254.0:::
> > mtdparts=maltaflash:1536k(ldr),2048k(root)
> >
> > After writing the JFFS2 image to /dev/mtd1, I can mount /dev/mtdblcok1
to
> > some directory.
> > mount -t jffs2 /dev/mtdblock1 /mnt
> >
> > Next, I hope to boot up Linux with JFFS2 root, and try to give this
cmdline
> > to Kernel:
> > go 0x80305018 rootfstype=jffs2
> > mtdparts=maltaflash:1536k(ldr),2048k(root) root=/dev/mtdblock1
> >
> > and the Kernel would complain me about no root:
> > VFS: Unable to mount root fs via NFS, trying floppy.
> > Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0)
> >
> > I traced the code and found that when passing "/dev/mtdblock1" to
> > name_to_dev_t() in do_mounts.c, it would return 0 at every try_name(),
> > which will fail at open() with the path "/sys/block/%s/dev".
> >
> > What's the problem? Could anyone tell me?
>
> What is the kernel version you are using?
>
> Check that root_dev_names array in init/do_mounts.c has an entry,
> which looks like
>
> { "mtdblock", 0x1f00 }
>
> --
> Eugene
WARNING: multiple messages have this Message-ID (diff)
From: "colin" <colin@realtek.com.tw>
Cc: linux-mips@linux-mips.org
Subject: Re: [*VIP*] Re: Strange! Cannot use JFFS2 as root
Date: Thu, 21 Oct 2004 11:00:11 +0800 [thread overview]
Message-ID: <007101c4b71a$171bd830$8b1a13ac@realtek.com.tw> (raw)
Message-ID: <20041021030011.j8BdbUd9rWjJzon0E6cQmZ0AiIhCYJH0bSYZMy0uXpA@z> (raw)
In-Reply-To: 20041020163048.GC17445@gate.ebshome.net
Hi Eugene,
The Kernel I use is 2.6.4, and I donot see the entry you mentioned.
Regards,
Colin
----- Original Message -----
From: "Eugene Surovegin" <ebs@ebshome.net>
To: "colin" <colin@realtek.com.tw>
Cc: <linux-mips@linux-mips.org>
Sent: Thursday, October 21, 2004 12:30 AM
Subject: [*VIP*] Re: Strange! Cannot use JFFS2 as root
> On Wed, Oct 20, 2004 at 10:02:26PM +0800, colin wrote:
> >
> > Hi all,
> > I had booted up Linux with nfs root, and write a JFFS2 image to
/dev/mtd1.
> > Here is my cmdline for Kernel:
> > go 0x80305018 root=/dev/nfs rw nfsroot=172.19.26.145:/nfs/rootfs
> > ip=172.19.27.193::172.19.27.254:255.255.254.0:::
> > mtdparts=maltaflash:1536k(ldr),2048k(root)
> >
> > After writing the JFFS2 image to /dev/mtd1, I can mount /dev/mtdblcok1
to
> > some directory.
> > mount -t jffs2 /dev/mtdblock1 /mnt
> >
> > Next, I hope to boot up Linux with JFFS2 root, and try to give this
cmdline
> > to Kernel:
> > go 0x80305018 rootfstype=jffs2
> > mtdparts=maltaflash:1536k(ldr),2048k(root) root=/dev/mtdblock1
> >
> > and the Kernel would complain me about no root:
> > VFS: Unable to mount root fs via NFS, trying floppy.
> > Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0)
> >
> > I traced the code and found that when passing "/dev/mtdblock1" to
> > name_to_dev_t() in do_mounts.c, it would return 0 at every try_name(),
> > which will fail at open() with the path "/sys/block/%s/dev".
> >
> > What's the problem? Could anyone tell me?
>
> What is the kernel version you are using?
>
> Check that root_dev_names array in init/do_mounts.c has an entry,
> which looks like
>
> { "mtdblock", 0x1f00 }
>
> --
> Eugene
next prev parent reply other threads:[~2004-10-21 3:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 14:02 Strange! Cannot use JFFS2 as root colin
2004-10-20 14:02 ` colin
2004-10-20 14:19 ` Charles Eidsness
2004-10-21 1:49 ` colin
2004-10-21 1:49 ` colin
2004-10-20 16:30 ` Eugene Surovegin
2004-10-21 3:00 ` colin [this message]
2004-10-21 3:00 ` [*VIP*] " colin
[not found] ` <005601c4b719$ea253970$8b1a13ac@realtek.com.tw>
2004-10-21 4:07 ` Eugene Surovegin
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='007101c4b71a$171bd830$8b1a13ac@realtek.com.tw' \
--to=colin@realtek.com.tw \
--cc=linux-mips@linux-mips.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