This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

problem with mounting root fs via NFS

Hello,

I am trying to boot my DM365 EVM board over the network for the first time, and the following error appears:

-----------------------

RAMDISK: Couldn't find valid RAM disk image starting at 0.
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "/mtdblock4" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00           15360 mtdblock0 (driver?)
1f01            1024 mtdblock1 (driver?)
1f02            4096 mtdblock2 (driver?)
1f03          524288 mtdblock3 (driver?)
1f04         1552384 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

-----------------------

For reference, I've pasted my environment variables here:

-----------------------

ethaddr=00:0e:99:02:c9:19
bootdelay=4
baudrate=115200
bootfile=uImage-dm365-evm.bin
serverip=192.168.1.142
bootcmd=dhcp;tftpboot;bootm
bootargs=mem=116M console=ttyS0,115200n8 root=/mtdblock4 rw initrd=0x82000000,4M ip=off
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.3.4 (May 22 2009 - 11:25:39)

Environment size: 306/262140 bytes

-----------------------

Prior to booting, I ran the ./setup.sh script in ./dvsdk/ and chose the defaults for all of the settings.  Is there another step I need to take?

Any help is appreciated, thank you.

  • You post seems to have fallen through the cracks. Usually TI guys respond by now. Maybe bumping this thread will bring eyes on it. I have no experience with the DM365 and ti's DVSDK. The setup.sh script is an indirection that complicates things a bit. For NFS, the bootargs will have root=/dev/nfs and nfsroot=your_nfshost_address:your_path_to_root_on_server,nolock. Also your target's network address must be specified. It you have dhcp then the bootargs should be ip=dhcp. For static address, it's a little more complicated. Bootargs then need to be ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:eth0:off  - details in kernel source at Documentation/filesystems/nfs/nfsroot.txt. Configuring a NFS server is another large task. All depends on what flavour of Linux server your have. A good place for info is the TI Wiki. Some DM365/NFS Wiki links:

    http://processors.wiki.ti.com/index.php/Linux_Host_Configuration_-_Ubuntu#Installing_a_NFS_Server
    http://processors.wiki.ti.com/index.php/GSG:_DM365_DVEVM_Software_Setup_for_MontaVista_Kernel#Creating_a_Shared_File_System_Between_Host_and_Target
    http://processors.wiki.ti.com/index.php/GSG:_DM365_DVEVM_Additional_Procedures#Booting_from_Flash_Using_NFS_File_System
    http://processors.wiki.ti.com/index.php/GSG:_DM365_DVEVM_Additional_Procedures#Booting_via_TFTP_Using_NFS_File_System
    http://processors.wiki.ti.com/index.php/UG:_DaVinci_PSP_Installation_on_DM365_EVM#Booting_with_NFS_as_a_root_filesystem

  • Amy Lu said:
    bootargs=mem=116M console=ttyS0,115200n8 root=/mtdblock4 rw initrd=0x82000000,4M ip=off

    This bootargs won't work for NFS. Please look into the PSP user guide for the bootarg to be used for NFS boot.

    Regards,

    Vaibhav