Thanks for your answer.
No, it's seems that the kernel don't find this location.
I have tried the "root=/dev/ram0 initrd=0x12000" boot parameter but it
has not resolved the problem.
Could the MTD support be useful in this case?
Because the variable ROOT_DEV seems important and it can be by the
> created at this memory location. (0x12000). During boot, -rom1fs- appears
Does the kernel know that the romfs is at this location? There is a
initrd={mem-address} kernel parameter option available.
But I am not sure about it.
-syed
--
To unsubscribe from this list: send an email with
"unsubscr
Syed Khader a écrit :
So why my major number is wrong?
What could be the problem?
Did you enable CONFIG_BLK_DEV_INITRD and CONFIG_BLK_DEV_RAM in kernel
config? Its been ages since I last worked on uClinux.
IIRC you should see messages like :
RAMDISK: romfs filesystem found at block 0
RAMDI
Syed Khader a écrit :
VFS: Cannot open root device "ram0" or unknown-block(0,0)
Please append a correct "root=" boot option
AFAIK, /dev/ram0 has (1,0) as major/minor device numbers. Does your
/dev nodes get populated properly while generating your romfs?
-syed
--
To unsubscribe from this
> VFS: Cannot open root device "ram0" or unknown-block(0,0)
> Please append a correct "root=" boot option
AFAIK, /dev/ram0 has (1,0) as major/minor device numbers. Does your
/dev nodes get populated properly while generating your romfs?
-syed
--
To unsubscribe from this list: send an email with
Hi all,
I'm trying to boot kernel 2.6.19 in a new architecture and I have a
problem concerning romfs.
During compilation I've created a section .romfs which contains
romfs.img. I have checked with GDB and
I found correctly the magic number -rom1fs- at the expected location.
But I don't understa
