Can not mount root on mtd block
Dear all
I am using kernel 2.6.10 with patched cvs mtd and my flash mapping
driver. I also add debug msg on mount_block_root. The return value is ENXIO. I am really get mess , because the cfi proded the flash successfully, but final result is "no such a device". Does anyone have ideas on this?
NOR flash driver (size->0x800000 mem->0x10000000)
NOR Flash 1: Found 1 x8 devices at 0x0 in 8-bit bank Amd/Fujitsu Extended Query Table at 0x0040
NOR Flash 1: CFI does not contain boot bank location. Assuming top. number of CFI chips: 1cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness. Creating 5 MTD partitions on "NOR Flash 1":
0x00000000-0x00100000 : "bootloader"
0x00100000-0x00300000 : "kernel"
0x00300000-0x00500000 : "System RFS"
0x00500000-0x00700000 : "User Application" 0x00700000-0x00800000 : "User Data"
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048) Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
*VFS: Tried fs_name = <cramfs> err = -6*
VFS: Cannot open root device "mtdblock2" or unknown-block(0,0) Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Thanks for helping
best regard
Mike,Lee
Quoted 3 lines · mike
Dear all
I am using kernel 2.6.10 with patched cvs mtd and my flash mapping
driver. I also add debug msg onmount_block_root. The return value is ENXIO. I am really get mess , because the cfi proded the flash successfully, but final result is "no such a device". Does anyone have ideas on this?
... SNIP ...
Quoted 4 lines
*VFS: Tried
fs_name= <cramfs> err = -6*
VFS: Cannot open root device "mtdblock2" or unknown-block(0,0) Please append a correct "root=" boot optionKernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
What is your kernel cmdline? The error says that it doesn't understand your "root=" option.
regards,
Aras Vaichas
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 46 lines · Aras Vaichas
Quoted 31 lines · mike
Quoted 29 lines · Aras Vaichas
Quoted 10 lines · mike
Dear Aras
Quoted 3 lines
What is your kernel cmdline? The error says that it doesn't understand your "root=" option.
Quoted 6 lines
kernel cmdline:
root=/dev/mtdblock2 mem=16M console=ttySMX0,115200n8i also tried below cmdline. But the same result
root=/dev/mtd2 mem=16M console=ttySMX0,115200n8
root=1f:02 mem=16M console=ttySMX0,115200n8what is your filesystem type?
for example, my command line is:
root=/dev/mtdblock4 rootfstype=yaffs ... etcI'm sure that I had this same problem once and it was simply a cmdline problem.
Quoted 7 lines
Quoted 2 lines
Aras
i am using cramfs, i also try rootfstype=cramfs . but same result.
Also, i have trace the kernel toget_sb, it return ENXIO. Is it mean that i can not parse the super block or the driver problem.Thanks for helping
Mike,LeeYes, I did exactly that same thing. My problem was that I was using:
mtblock/4
Quoted 7 lines
instead of:
mtdblock4
It was something very simple. Good luck anyway!
Aras
I also try it but same result, in my rootfs i only add note like mtdblock0,mtdblock1.... I do not mknod mtd node to a directory Also, the cram root fs work with 2.4.18. Do i miss something in the root directory?
best regard
Mike,Lee