Can not mount root on mtd block

Can not mount root on mtd block

[mike]

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: 1
cfi_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

Re: Can not mount root on mtd block

[Aras Vaichas]

mike wrote:
> 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?
... SNIP ...
> *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)


What is your kernel cmdline? The error says that it doesn't understand your 
"root=" option.


regards,

Aras Vaichas

Re: Can not mount root on mtd block

[mike]

Aras Vaichas wrote:

> mike wrote:
>
>> Aras Vaichas wrote:
>>
>>> mike wrote:
>>>
>>>> Dear Aras
>>>>
>>>>>
>>>>>
>>>>> What is your kernel cmdline? The error says that it doesn't 
>>>>> understand your "root=" option.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> kernel cmdline:
>>>> root=/dev/mtdblock2 mem=16M console=ttySMX0,115200n8
>>>>
>>>> i also tried below cmdline. But the same result
>>>> root=/dev/mtd2 mem=16M console=ttySMX0,115200n8
>>>> root=1f:02 mem=16M console=ttySMX0,115200n8
>>>
>>>
>>>
>>>
>>> what is your filesystem type?
>>>
>>> for example, my command line is:
>>> root=/dev/mtdblock4 rootfstype=yaffs ... etc
>>>
>>> I'm sure that I had this same problem once and it was simply a 
>>> cmdline problem.
>>>
>>> Aras
>>>
>> i am using cramfs, i also try rootfstype=cramfs . but same result.
>> Also, i have trace the kernel to get_sb, it return ENXIO. Is it mean 
>> that i can not parse the super block or the driver problem.
>>
>> Thanks for helping
>> Mike,Lee
>
>
> Yes, I did exactly that same thing. My problem was that I was using:
>
> mtblock/4
>
> 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

Can not mount root on mtd block

[Pawel Studencki]

hello Mike, 

I read your e-mails about problems with mounting ramfs
as root filesystem
and I wonder if you found a solution.
I'm trying the same thing with kernel 2.6.11 on ppc
processor. I've already
checked following:
- boot options: root=/dev/mtdblock1 ro
- debugging to/from do_mount_root function...
and slowly I'm loosing ideas...In my case function
path_lookup (in do_mount)
returns with error  -ENOENT, because there were no
inode found for "root".
It looks similar to your problem...

So if you have any hints, I will enjoy to check them
and perhaps together we
can solve this annoying problem  :) 

best regards
Pawel


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/