2008-04-26 05:39:33 Unable to mount rootfs of jffs2 on BF527-EZKIT
Aaron Zhong (CHINA)
Message: 55019
Hi, could anyone help me to find out why the kernel can't mount the rootfs of jffs2?
I have followed the guide http://docs.blackfin.uclinux.org/doku.php?id=enabling_jffs2&s=serial%20flash
but it seemed not work.
The ls command on u-boot works and I also checked the magic number of rootfs:
bfin> md.b 0x20100000 0x02
20100000: 85 19 ..
The uclinux and toolchain version is 2008R1-RC8 and 08r1-8 respectlvely.
Any suggestions? Thanks in advance.
Starting Kernel at = 13c000
Linux version 2.6.22.18-ADI-2008R1-svn (root@W55) (gcc version 4.1.2 (ADI svn)) #53 Sat Apr 26 17:26:19 CST 2008
early printk enabled on early_BFuart0
Hardware Trace Active and Enabled
Blackfin support (C) 2004-2007 Analog Devices, Inc.
Compiled for ADSP-BF527 Rev 0.0
Warning: Unsupported Chip Revision ADSP-BF527 Rev 0.0 detected
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 525 MHz core clock and 131 MHz System Clock
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
text = 0x00001000-0x00102aa0
rodata = 0x00103000-0x0012a064
data = 0x0012b000-0x0013c000
stack = 0x0012c000-0x0012e000
init = 0x0013c000-0x00151000
bss = 0x00151000-0x0015fe88
available = 0x0015fe88-0x03eff000
DMA Zone = 0x03f00000-0x04000000
Instruction Cache Enabled
Data Cache Enabled (write-through)
Built 1 zonelists. Total pages: 16002
Kernel command line: root=/dev/mtdblock2 rw rootfstype=jffs2 earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600 mtdparts=physmap-flash.0:192k(uboot)ro,832k(kernel),-(rootfs)
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
console handover: boot [early_BFuart0] -> real [ttyBF0]
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory available: 59836k/65536k RAM, (84k init code, 1030k kernel code, 289k data, 1024k dma, 3272k reserved)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Data A SRAM: 16 KB (15 KB free)
Blackfin Data B SRAM: 16 KB (16 KB free)
Blackfin Instruction SRAM: 48 KB (43 KB free)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
stamp_init(): registering device resources
Generic PHY: Registered new driver
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
JFFS2 version 2.2. (NAND) (SUMMARY) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc02000 (irq = 31) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
bfin_mac_mdio: probed
bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:03, irq=-1, mdc_clk=2500000Hz(mdc_div=25)@sclk=131MHz)
bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver
physmap platform flash device: 00400000 at 20000000
3 cmdlinepart partitions found on MTD device physmap-flash.0
Creating 3 MTD partitions on "physmap-flash.0":
0x00000000-0x00030000 : "uboot"
0x00030000-0x00100000 : "kernel"
0x00100000-0x00400000 : "rootfs"
Generic platform RAM MTD, (c) 2004 Simtec Electronics
bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@7
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
i2c /dev entries driver
i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller Driver, Version 1.8, regs_base@ffc01400
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
rtc-bfin rtc-bfin: setting the system clock to 1982-10-09 04:45:20 (402986720)
jffs2: Flash size not aligned to erasesize, reducing to 0KiB
jffs2: Too few erase blocks (0)
List of all partitions:
1f00 192 mtdblock0 (driver?)
1f01 832 mtdblock1 (driver?)
1f02 3072 mtdblock2 (driver?)
No filesystem could mount root, tried: jffs2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
QuoteReplyEditDelete
2008-04-26 17:22:03 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Robin Getz (UNITED STATES)
Message: 55027 Aaron:
Your bootmessage has the error:
>jffs2: Flash size not aligned to erasesize, reducing to 0KiB
> jffs2: Too few erase blocks (0)
> List of all partitions:
> 1f00 192 mtdblock0 (driver?)
> 1f01 832 mtdblock1 (driver?)
> 1f02 3072 mtdblock2 (driver?)
You don't have the proper flash chip driver installed in your kernel (I think).
-Robin
QuoteReplyEditDelete
2008-04-28 05:22:27 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Aaron Zhong (CHINA)
Message: 55110
Hi Robin, could you give me a way to check whether the flash driver works? From the boot message,
I think the flash has been detected. My flash is 4M parallel flash of M29W320EB. My MTD configuration is
CONFIG_MTD=y
CONFIG_MTD_CONCAT=y
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CMDLINE_PARTS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_CFI=y
CONFIG_MTD_JEDECPROBE=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_CFI_ADV_OPTIONS=y
CONFIG_MTD_CFI_NOSWAP=y
CONFIG_MTD_CFI_GEOMETRY=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_CFI_I4=y
CONFIG_MTD_CFI_INTELEXT=y
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_STAA=y
CONFIG_MTD_CFI_UTIL=y
CONFIG_MTD_RAM=y
CONFIG_MTD_ROM=y
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PHYSMAP_START=0x20000000
CONFIG_MTD_PHYSMAP_LEN=0x400000
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
CONFIG_MTD_PLATRAM=y
QuoteReplyEditDelete
2008-04-28 08:08:46 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Robin Getz (UNITED STATES)
Message: 55122 Aaron:
If the flash driver was working it wouldn't say " (driver?)" in the bootmsg.
I'll check things out on a platform today.
-robin
QuoteReplyEditDelete
2008-04-28 22:36:44 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Aaron Zhong (CHINA)
Message: 55185
Thanks very much. Actually, I add some prink in jedec_probe_chip and found it is not called.
I think the M29W320EB flash chip should also be probed by jedec interface, is it right?
I found some similar M29Wxxx chips in jedec_probe.c.
QuoteReplyEditDelete
2008-04-29 15:10:25 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Robin Getz (UNITED STATES)
Message: 55241 Aaron:
I think Michael fixed this on 2008R1 branch and trunk.
Can you check things out, and try it?
Thanks
-Robin
QuoteReplyEditDelete
2008-04-29 21:36:57 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Aaron Zhong (CHINA)
Message: 55259 My uClinux distribution version is already 2008R1-RC8. Do you mean check the newest version out from SVN?
QuoteReplyEditDelete
2008-04-30 00:36:56 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Robin Getz (UNITED STATES)
Message: 55266 Aaron:
Yes. - check out _branch_ version from svn.
The plan is to fix a few more bugs/issues on BF548/BF527 and make a new version of the 2008R1 release, but it may not be for a few weeks/few months before all planned things get resolved.
-Robin
QuoteReplyEditDelete
2008-05-09 04:21:22 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Aaron Zhong (CHINA)
Message: 55665
Hi Robin:
I have tried the newest version in svn, but it did not work either. Could you give me some help?
The kernel configuration is:
CONFIG_MTD=y
CONFIG_MTD_CONCAT=y
CONFIG_MTD_PARTITIONS=y
CONFIG_MTD_CMDLINE_PARTS=y
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_CFI=y
CONFIG_MTD_GEN_PROBE=y
CONFIG_MTD_CFI_ADV_OPTIONS=y
CONFIG_MTD_CFI_NOSWAP=y
CONFIG_MTD_CFI_GEOMETRY=y
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_MAP_BANK_WIDTH_8=y
CONFIG_MTD_MAP_BANK_WIDTH_16=y
CONFIG_MTD_MAP_BANK_WIDTH_32=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
CONFIG_MTD_CFI_I4=y
CONFIG_MTD_CFI_I8=y
CONFIG_MTD_CFI_AMDSTD=y
CONFIG_MTD_CFI_STAA=y
CONFIG_MTD_CFI_UTIL=y
CONFIG_MTD_RAM=y
CONFIG_MTD_ROM=y
CONFIG_MTD_COMPLEX_MAPPINGS=y
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_PHYSMAP_START=0x0
CONFIG_MTD_PHYSMAP_LEN=0x0
CONFIG_MTD_PHYSMAP_BANKWIDTH=2
CONFIG_MTD_PLATRAM=y
CONFIG_MTD_BLOCK2MTD=y
kernel message:
Linux version 2.6.24.5-ADI-2008R2-pre-svn4709 (root@fedora6) (gcc version 4.1.2 (ADI svn)) #6 Fri May 9 16:14:51 CST 2008
console [early_BFuart0] enabled
early printk enabled on early_BFuart0
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
fixedcode = 0x00000400-0x00000490
text = 0x00001000-0x00116720
rodata = 0x00116860-0x0013fed8
bss = 0x0013fee0-0x0014d75c
data = 0x0014d75c-0x00160000
stack = 0x0015e000-0x00160000
init = 0x00160000-0x00179000
available = 0x00179000-0x03eff000
DMA Zone = 0x03f00000-0x04000000
Hardware Trace Active and Enabled
Blackfin support (C) 2004-2008 Analog Devices, Inc.
Compiled for ADSP-BF527 Rev 0.0
Warning: Unsupported Chip Revision ADSP-BF527 Rev 0.0 detected
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 525 MHz core clock and 131 MHz System Clock
MPU: setting up cplb tables with memory protection
Instruction Cache Enabled
Data Cache Enabled (write-through)
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 16002
Kernel command line: bootargs=root=/dev/mtdblock2 rw rootfstype=jffs2 earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
console handover: boot [early_BFuart0] -> real [ttyBF0]
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory available: 59832k/65536k RAM, (100k init code, 1109k kernel code, 295k data, 1024k dma, 3172k reserved)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Data A SRAM: 16 KB (15 KB free)
Blackfin Data B SRAM: 16 KB (16 KB free)
Blackfin Instruction SRAM: 48 KB (43 KB free)
Security Framework initialized
Capability LSM initialized
Mount-cache hash table entries: 512
net_namespace: 64 bytes
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
stamp_init(): registering device resources
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
JFFS2 version 2.2. (NAND) (SUMMARY) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc02000 (irq = 31) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
bfin_mac_mdio: probed
bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=25)@sclk=131MHz)
bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1
physmap platform flash device: 00400000 at 20000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
Using physmap partition information
Creating 3 MTD partitions on "physmap-flash.0":
0x00000000-0x00030000 : "Bootloader"
0x00030000-0x00100000 : "Kernel"
0x00100000-0x00400000 : "RootFS"
Generic platform RAM MTD, (c) 2004 Simtec Electronics
block2mtd: version $Revision: 4684 $
bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@7
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
i2c /dev entries driver
i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc01400
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
rtc-bfin rtc-bfin: setting system clock to 1982-10-22 03:30:21 UTC (404105421)
List of all partitions:
1f00 192 mtdblock0 (driver?)
1f01 832 mtdblock1 (driver?)
1f02 3072 mtdblock2 (driver?)
No filesystem could mount root, tried: jffs2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
QuoteReplyEditDelete
2008-05-09 04:42:57 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Mike Frysinger (UNITED STATES)
Message: 55667
your bootargs is not set correctly in u-boot ... you've accidently prepended a literal bootargs=
QuoteReplyEditDelete
2008-05-09 05:54:55 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Aaron Zhong (CHINA)
Message: 55670
Mike:
Do you mean the bootargs is not correct? When I reset the bootargs, the kernel print different messages.
It seemed the kernel try to mount rootfs but /dev/mtdblock2 is not a jffs2 device.
bfin> print bootargs
bootargs=root=/dev/mtdblock2 rw rootfstype=jffs2 earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600
bfin> flinfo
Bank # 1: CFI conformant FLASH (16 x 16) Size: 4 MB in 71 Sectors
Erase timeout 8192 ms, write timeout 1 ms, buffer write timeout 1 ms, buffer size 1
Sector Start Addresses:
20000000 (RO) 20002000 (RO) 20004000 (RO) 20006000 (RO) 20008000 (RO)
2000A000 (RO) 2000C000 (RO) 2000E000 (RO) 20010000 (RO) 20020000
20030000 20040000 20050000 20060000 20070000
20080000 20090000 200A0000 200B0000 200C0000
200D0000 200E0000 200F0000 20100000 20110000
20120000 20130000 20140000 20150000 20160000
20170000 20180000 20190000 201A0000 201B0000
201C0000 201D0000 201E0000 201F0000 20200000
20210000 20220000 20230000 20240000 20250000
20260000 20270000 20280000 20290000 202A0000
202B0000 202C0000 202D0000 202E0000 202F0000
20300000 20310000 20320000 20330000 20340000
20350000 20360000 20370000 20380000 20390000
203A0000 203B0000 203C0000 203D0000 203E0000
203F0000
bfin> fsinfo
### filesystem type is JFFS2
Scanning JFFS2 FS: | / - \ . | . / - \ | / - \ | / - done.
Compression: NONE
frag count: 99
compressed sum: 9410
uncompressed sum: 9410
Compression: ZERO
frag count: 0
compressed sum: 0
uncompressed sum: 0
Compression: RTIME
frag count: 1
compressed sum: 26
uncompressed sum: 40
Compression: RUBINMIPS
frag count: 0
compressed sum: 0
uncompressed sum: 0
Compression: COPY
frag count: 0
compressed sum: 0
uncompressed sum: 0
Compression: DYNRUBIN
frag count: 0
compressed sum: 0
uncompressed sum: 0
Compression: ZLIB
frag count: 248
compressed sum: 629264
uncompressed sum: 920314
bfin> ls
drwxrwxrwt 0 Wed Apr 23 01:56:05 2008 tmp
drwxr-xr-x 0 Wed Apr 23 01:56:05 2008 root
drwxr-xr-x 0 Wed Apr 23 01:56:05 2008 usr
drwxr-xr-x 0 Sat Apr 26 08:10:04 2008 etc
drwxr-xr-x 0 Wed Apr 23 01:56:05 2008 var
drwxr-xr-x 0 Wed Apr 23 01:56:05 2008 home
drwxr-xr-x 0 Wed Apr 23 01:56:05 2008 mnt
drwxr-xr-x 0 Wed Apr 23 01:56:05 2008 sys
drwxr-xr-x 0 Sat Apr 26 08:10:05 2008 bin
drwxr-xr-x 0 Wed Apr 23 01:56:05 2008 proc
drwxr-xr-x 0 Wed Apr 23 01:56:05 2008 lib
drwxr-xr-x 0 Sat Apr 26 08:10:06 2008 dev
lrwxrwxrwx 3 Sat Apr 26 08:09:51 2008 sbin -> bin
bfin>
bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1
physmap platform flash device: 00400000 at 20000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
Using physmap partition information
Creating 3 MTD partitions on "physmap-flash.0":
0x00000000-0x00030000 : "Bootloader"
0x00030000-0x00100000 : "Kernel"
0x00100000-0x00400000 : "RootFS"
Generic platform RAM MTD, (c) 2004 Simtec Electronics
block2mtd: version $Revision: 4684 $
bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@7
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
i2c /dev entries driver
i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc01400
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
rtc-bfin rtc-bfin: setting system clock to 1982-10-22 04:50:59 UTC (404110259)
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004: 0x0010 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000024: 0xffff instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000002c: 0x292b instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000030: 0xd3ae instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000034: 0xff70 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000038: 0xe002 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000040: 0x98f7 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000044: 0xffff instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000058: 0x480e instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000005c: 0x480e instead
Further such events for this erase block will not be printed
Empty flash at 0x000013f4 ends at 0x000013f8
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010000: 0xe9b3 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001000c: 0xe002 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010014: 0x8b2d instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001002c: 0x4812 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010030: 0x4812 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010034: 0x4812 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010044: 0x0438 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010048: 0xcff8 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001004c: 0xe69e instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00010050: 0x5654 instead
Further such events for this erase block will not be printed
Empty flash at 0x0001d398 ends at 0x0001d39c
Old JFFS2 bitmask found at 0x0001d3a8
You cannot use older JFFS2 filesystems with newer kernels
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020004: 0x042f instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002000c: 0xe002 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020014: 0xe8cd instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020028: 0x0005 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002002c: 0x4812 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020030: 0x4812 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020034: 0x4812 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020048: 0x516a instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0002004c: 0xc642 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00020050: 0x5354 instead
Further such events for this erase block will not be printed
Old JFFS2 bitmask found at 0x0002a8e0
You cannot use older JFFS2 filesystems with newer kernels
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00030004: 0x0176 instead
...
Empty flash at 0x000ffebc ends at 0x000fff24
Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
empty_blocks 32, bad_blocks 0, c->nr_blocks 48
VFS: Cannot open root device "mtdblock2" or unknown-block(31,2)
Please append a correct "root=" boot option; here are the available partitions:
1f00 192 mtdblock0 (driver?)
1f01 832 mtdblock1 (driver?)
1f02 3072 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
QuoteReplyEditDelete
2008-05-09 06:30:30 Re: Unable to mount rootfs of jffs2 on BF527-EZKIT
Mike Frysinger (UNITED STATES)
Message: 55674
make sure you wrote the jffs2 rootfs at the right offset that corresponds to the mtd partitioning scheme you're using