From: sam <sam.hsu@southpro.com.tw>
To: linux-mtd@lists.infradead.org
Subject: jffs2 root filesystem
Date: Tue, 09 Nov 2004 16:30:29 +0000 [thread overview]
Message-ID: <4190F0A5.80609@southpro.com.tw> (raw)
hi
I try to port linux-2.4.19-rmk1 to a pxa255 board
i am success to use MTD partition and can mount it
But when i try to use MTD as root filesystem (root=/dev/mtdblock/3
console=ttyS0,38400)
kernel boot message show:
.......
physmap flash device: 2000000 at 0
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
mtd: Giving out device 0 to Physically mapped flash
MTD partition setup...
partition num: 4
Using physmap partition definition
Creating 4 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "U-boot"
mtd: Giving out device 1 to U-boot
0x00040000-0x00340000 : "zImage"
mtd: Giving out device 2 to zImage
0x00340000-0x00a00000 : "ramdisk"
mtd: Giving out device 3 to ramdisk
0x00a00000-0x02000000 : "User system"
mtd: Giving out device 4 to User system
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.97 (double precision)
mtdblock_open
ok
mtdblock: read on "Physically mapped flash" at 0x400, size 0x400
mtdblock_release
ok
mtdblock_open
ok
mtdblock: read on "Physically mapped flash" at 0x0, size 0x200
FAT: bogus logical sector size 5349
mtdblock_release
ok
mtdblock_open
ok
mtdblock: read on "Physically mapped flash" at 0x0, size 0x200
FAT: bogus logical sector size 5349
mtdblock_release
ok
mtdblock_open
ok
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000:
0x0016 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000014:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000018:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000001c:
0xf014 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000020:
0x0160 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024:
0x01c0 instead
Further such events for this erase block will not be printed
JFFS2: Erase block at 0x00000000 is not formatted. It will be erased
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing init memory: 64K
Warning: unable to open an initial console.
Kernel panic: No init found. Try passing init= option to kernel.
..................
why can't i use mtd as my root disk
Sam
next reply other threads:[~2004-11-09 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 16:30 sam [this message]
2004-11-09 18:00 ` jffs2 root filesystem Michael
2004-11-09 18:05 ` Jeff Angielski
-- strict thread matches above, loose matches on Subject: below --
2005-08-11 13:32 Alex Karev
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=4190F0A5.80609@southpro.com.tw \
--to=sam.hsu@southpro.com.tw \
--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