boot linux kernel error

I like linux ,also like the embed system design technology.
so i brought a development board(FriendlyARM mini2440),i have compiled the linux Kernel many times.
also it all doesn't work.
when i compiled the linux Kernel(linux-2.6.29) to a zImage and downloaded to board.
at the same time the rootfs.img download to board.
when boot the kernel it show that "Root-NFS: No NFS server available, giving up." ,"VFS: Unable to mount root fs via NFS, trying floppy."
"VFS: Cannot open root device "mtdblock3" or unknown-block(2,0)"
how can i do to this problem?
At last thanks for you spent the time to read my questions.

This sort of problem can be very hard to find, there can be many things that give this sort of error. One place to start looking is the compiling process, did you compile the kernel with initrd.gz and ram support, this will need to be compiled into the kernel, not as a module.

Hello, I hope this blog could help your problem
http://mini2440vietnam.blogspot.com/
Good luck, friend

hei,I think this question is related to bootloader,the bootloader provide to the kernel boot parameters is error.

Originally Posted by wenlan I like linux ,also like the embed system design technology. so i brought a development board(FriendlyARM mini2440),i have compiled the linux Kernel many times. also it all doesn't work. when i compiled the linux Kernel(linux-2.6.29) to a zImage and downloaded to board. at the same time the rootfs.img download to board. when boot the kernel it show that "Root-NFS: No NFS server available, giving up." ,"VFS: Unable to mount root fs via NFS, trying floppy." "VFS: Cannot open root device "mtdblock3" or unknown-block(2,0)" how can i do to this problem? At last thanks for you spent the time to read my questions.

First of all you need to understand the Whole scenario. Here the problem is your kernel unable to find the filesystem need to be mounted after kernel boots up. So here you need to check your bootloader boot parameters to provide proper location to your filesystem.
Another suggestion it seems like your boot parameter is searching for mtdblock device for filesystem but you are using NFS (network file system). Which is the main culprit here. Search in google how to give boot parameters for NFS .

You can set kernel commandline parameters either from the bootloader (maybe), or by building them into the kernel. In your kernel config, search for CONFIG_CMDLINE. Add a parameter like init=/bin/init (point to the init binary in your rootfs).
--- rod.