Problems getting NFS to work

[augustus]

hello, I'm a newbie to all the linux stuff so please forgive any obvious stupidity.  I'm trying to get my plug to boot from NFS (simply because I messed around to much and now it will not come up on its own anymore).  I believe I have my server setup correctly, it's showing a share:

/tftpboot *

and the file "uImage.sheeva.040309" is in that directory, the ip of the server is 192.168.1.100

On the plug I followed the instructions from Appendix C of hte SheevaPlug dev kit document, and have the following for printenv:

Code:

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
CASset=min
MALLOC_len=1
ethprime=egiga0
ethmtu=1500
usb0Mode=host
nandEcc=1bit
cesvcid=ULULULULULULPPULULULULULDA
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethaddr=00:50:43:01:C3:B6
run_diag=no
ethact=egiga0
boocmd=nand read 0x800000 0x100000 0x200000: bootm 0x800000
ipaddr=192.168.1.105
serverip=192.168.1.100
image_name=uImage.sheeva.040309
console=console=ttyS0,115200 mtdparts==cfi_flash:0x200000@0x100000(uImage)ro,0x1f800000@0x300000(rootfs)rw
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
bootcmd=tftpboot 0x200000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
bootargs=console=ttyS0,115200 mtdparts==cfi_flash:0x200000@0x100000(uImage)ro,0x1f800000@0x300000(rootfs)rw root=/dev/nfs rw nfsroot=192.168.1.100:/mnt/ARM_FS/ ip=192.168.1.105:192.168.1.100:::DB88FXX81:eth0:none

So, I'm wondering about the ipaddr and the serverip, I didn't completely understand the Appendix C instructions in this area:

set ipaddr 10.81.xxx.yyy
set serverip 10.81.xxx.zzz

so I just put
set ipaddr 192.168.1.105  (the IP of the plug)
set serverip 192.168.1.100 (the IP of the server)

Any ideas what i'm messing up here?  I'm sort of overloaded and having trouble figuring all this out.  Any direction is greatly appreciated as I'm excited to get my plug back up and running!

Thanks!

also, does anyone else find the U-boot command prompt to act a little funny sometimes?  Sometimes I'll have to enter the same command twice in a row before it recognizes it.

[kilowatt]

Two things:

Check you rootpath definition.  it should match the path to the root FileSystem files on your nfs server.  Mine are in /tftpboot/Ubuntu-SheevaPlug.  But yours need to match where you put your files and the /etc/exports file on your nfs server must allow this path to be accessed.

your console def has mtparts=cfi_flash... I have only seen nand_mtd used.

[moshiach]

What jumps out at me is your rootpath.  Unless you are exporting /mnt/ARM you need to change that.  I beleive you said you are exporting /tftpboot Hopefully underneath that directory you have a directory that conatains the root filesystem (like /tftpboot/sheevaroot)  That should be your rootpath.  You have the right of it with the ip and serverip.

One thing I would change on the system you are hosting the nfs at, not sure if it makes too much difference in this case, but instead of your export file looking like this

Code:

/tftpboot *

you should probably add some options to it

Code:

/tftpboot/ *(rw,sync,no_root_squash,subtree_check)

But dfix your rootpath and you'll be on the right track.

[tmk]

Not sure if its been mentioned, but i think the u-boot image is obtained via tftp, not NFS, then the root filesystem is mounted once NFS is up.

Can anyone confirm or deny this? If so, you'll need to set up a tftp server as well.

-tmk

[plugit]

That's right. It grabs the uImage via tftp, and after the kernel boots, it goes to get the rootfs via NFS.

FWIW, I had absolutely no success getting NFS to work with Ubuntu as the host, but it worked perfectly after I switched to SUSE. Thank goodness for VMWare.

[augustus]

For starters I greatly appreciate your help everyone!

for a reference, here's what I followed:

Boot SheevaPlug from NFS
This section provides the information on the settings needed on the Linux host and the SheevaPlug U-Boot to boot SheevaPlug from NFS.
Linux Host Settings
On the Linux host follow the steps below:
1. Copy the ‘uImage.Sheeva_USB’ to the ‘tftpboot’ folder.
[root@localhost SheevaPlug]# cp –a uImage.Sheeva_USB /tftpboot
2. Edit the NFS exports script residing in the /etc folder.
[root@localhost SheevaPlug]# pwd
/home/SheevaPlug
[root@localhost SheevaPlug]# vi /etc/exports
3. Add the following lines to the ‘exports’ script and save.
/home/ *(rw,sync,no_root_squash)
/tftpboot/ *(rw,sync,no_root_squash)
4. Restart the ‘NFS’ server.
[root@localhost SheevaPlug]# /etc/init.d/nfs restart
Shutting down NFS mountd: [ OK ]
Shutting down NFS daemon: [ OK ]
Shutting down NFS quotas: [ OK ]
Shutting down NFS services: [ OK ]
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]
[root@localhost SheevaPlug]#
SheevaPlug U-Boot Settings
On the SheevaPlug reference board follow the steps below to boot from NFS.
Marvell>> set ipaddr 10.81.xxx.yyy
Marvell>> set serverip 10.81.xxx.zzz
Marvell>> set rootpath /home/Ubuntu-SheevaPlug
Marvell>> set image_name uImage.Sheeva_USB
Marvell>> set console 'console=ttyS0,115200 mtdparts=cfi_flash:0x200000@0x100000(uImage)ro,0x1f800000@0x300000(rootfs)rw'
Marvell>> set bootargs_root 'root=/dev/nfs rw'
Marvell>> set bootargs_end ‘:::DB88FXX81:eth0:none’
Marvell>> set bootcmd 'tftpboot 0x2000000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000'
Marvell>> saveenv

that's where the "cfi_flash" came from, at least I think.  I'll try making that nand_mtd and modifying the rootpath.

here's my new bootup:

Code:

U-Boot 1.1.4 (Mar 19 2009 - 16:06:59) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CEE80

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Using egiga0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.105
Filename 'uImage.sheeva.040309'.
Load address: 0x200000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
## Booting image at 02000000 ...
Bad Magic Number
Marvell>>

here's my new printenv:

Code:

baudrate=115200
loads_echo=0
netmask=255.255.0.0
CASset=min
MALLOC_len=1
ethprime=egiga0
ethmtu=1500
usb0Mode=host
nandEcc=1bit
cesvcid=ULULULULULULPPULULULULULDA
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethaddr=00:50:43:01:C3:B6
run_diag=no
ethact=egiga0
boocmd=nand read 0x800000 0x100000 0x200000: bootm 0x800000
ipaddr=192.168.1.105
serverip=192.168.1.100
image_name=uImage.sheeva.040309
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
bootcmd=tftpboot 0x200000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000
rootpath=/home/SheevaPlug
console=console=ttyS0,115200 mtdparts=nand_mtd:0x200000@0x100000(uImage)ro,0x1f800000@0x30000(rootfs)rw
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x200000@0x100000(uImage)ro,0x1f800000@0x30000(rootfs)rw root=/dev/nfs rw nfsroot=192.168.1.100:/home/SheevaPlug ip=192.168.1.105:192.168.1.100:::DB88FXX81:eth0:none

also, on the host ubuntu server, here's my /etc/exports file:

Code:

# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes  gss/krb5i(rw,sync)
/home/ *(rw,sync,no_root_squash)
/tftpboot/ *(rw,sync,no_root_squash)
#

on the host I have a directory /tftpboot/ with uImage.sheeva.040309 in it.

Another problem I'm having is when I follow the "procedure to configure and build the linux kernel with 4.2.7 LSP" I get stuck toward the end with:

Code:

grant@SUN:/home/SheevaPlug/linux-feroceon_4_2_7_KW$ make ARCH=arm mrproper
make: arm-none-linux-gnueabi-gcc: Command not found
make[2]: arm-none-linux-gnueabi-gcc: Command not found

I don't know what that means, and i'm not totally certain I have to go through all that to get booting from NFS.

needless to say i'm a little turned around here.

Thanks again for any help you can offer!

[kilowatt]

You need both a TFTP server and a NFS server running on you host system.

Your bootcmd is tftpboot which is correct but it is not getting any response from your tftp server.  Do you have a tftp server setup?  you need to put the uImage.sheeva.040309 image at the root directory served by the tftp server. 

Once you have loaded the kernel via tftp it will try to load the root file system via nfs and we will see if you have that server setup properly.

Mark

[augustus]

kilowatt, that makes alot of sense, I am learning now that the documentation for the plug isn't exactly comprehensive, or certainly not written for those with little experience.  I will try and get the tftp working tonight.

Any ideas on the make mrproper stuff?  I'm assuming I need to get to the end of that Procedure or I still will not work after I get the tftp working?

here's the procedure I'm speaking of:

Code:

Procedure to Configure and Build the Linux kernel with 4.2.7 LSP
This document provides the procedure to configure the Linux kernel 2.6.22.18 with the linux-feroceon_4_2_7_KW.zip for the SheevaPlug platform based on Kirkwood 6281(A0).
1. On a Linux machine, go to the ‘home’ directory and create a directory ‘SheevaPlug’.
/home# mkdir SheevaPlug
2. Copy the source of the Linux kernel in /home/SheevaPlug folder: linux-2.6.22.18.tar.bz2
3. On the same Linux machine, copy Marvell’s LSP in the /home/SheevaPlug folder: linux-feroceon_4_2_7_KW.zip
4. Copy the two patches : 0001_gw_BE_fix.patch and 0002_SheevaPlug_support_mod.patch.
5. Expand the source in the /home/SheevaPlug folder
~/SheevaPlug# tar –xvf linux-2.6.22.18.tar.bz2
6. Move the folder linux-2.6.22.18 to a new folder linux-feroceon_4_2_7_KW
~/SheevaPlug# mv linux-2.6.22.18 linux-feroceon_4_2_7_KW
7. Unzip the LSP patch
~/SheevaPlug# unzip linux-feroceon_4_2_7_KW.zip
8. During the unzip process, the following message will appear. Select the option ‘All’.
Replace linux-feroceon_4_2_7_kw/init/do_mounts_rd.c? [Y]es, [N]o, [A]ll, [R]ename: All
9. Go to the working directory where all the configuration files are unzipped.
~/SheevaPlug# cd linux-feroceon_4_2_7_KW
10. Copy the big endian patch from the base directory to the working directory.
~/SheevaPlug# cp –a 0001_gw_BE_fix.patch ./ linux-feroceon_4_2_7_KW
11. Copy the SheevaPlug support patch from the base directory to the working directory.
~/SheevaPlug# cp –a 0002_SheevaPlug_support_mod.patch ./ linux-feroceon_4_2_7_KW
12. Apply the big endian patch ‘0001_gw_BE_fix.patch’ and check for any errors. If none, proceed to the next step.
~/SheevaPlug /linux-feroceon_4_2_7_KW# patch –p1 < 0001_gw_BE_fix.patch
13. Apply the SheevaPlug support patch ‘0002_SheevaPlug_support_mod.patch’ and check for any errors. If none proceed to the next step.
~/SheevaPlug /linux-feroceon_4_2_7_KW# patch –p1 < 0002_SheevaPlug_support_mod.patch
14. Do a make mrproper for a total clean build.
~/SheevaPlug /linux-feroceon_4_2_7_KW # make mrproper
15. Goto the configs folder and check for the mv88f6281_defconfig file.
~/SheevaPlug /linux-feroceon_4_2_7_KW # make mv88f6281_defconfig
16. Create a uImage
~/SheevaPlug /linux-feroceon_4_2_7_KW # make uImage
17. Rename it as uImage.Sheeva_USB
~/SheevaPlug /linux-feroceon_4_2_7_KW # cp –a arch/arm/boot/uImage /SheevaPlug /linux-feroceon_4_2_7_KW /uImage.Sheeva_USB

for mine I didn't have patches 0001 and 0002, instead I had just the 0011 patch, which is all i incorporated.  So, I got everything up to step 14 above which is where I get:

Code:

grant@SUN:/home/SheevaPlug/linux-feroceon_4_2_7_KW$ make ARCH=arm mrproper
make: arm-none-linux-gnueabi-gcc: Command not found
make[2]: arm-none-linux-gnueabi-gcc: Command not found

So, do I even need to do this for booting from NFS, I was thinking I do.

[hammerinhank]

It looks to me like you need to set your path for the cross compiler.  Check out Appendix A in the SheevaPlug Development Kit README-Rev1.1.pdf file. 

On mine I use:   export PATH=/root/Sheeva/gcc/bin:$PATH

[freebsdfan@hotmail.com]

I am also trying to get an NFS boot working.  Since I'm also going to try to use a new Kernel I wanted to test the NFS
setup first.  So I did a normal boot and then tried to mount my nfs share:

Code:

root@debian:~# mount -t nfs 192.168.123.82:/plug_root /mnt/nfs
mount: wrong fs type, bad option, bad superblock on 192.168.123.82:/plug_root,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

and infact there's no /sbin/mount.nfs.  Anyone know where I can find one?

Skip

[hammerinhank]

This looks like your trying to mount a nfs share onto the Sheevaplug.  You first need to install nfs-common.  The nfs client is installed but common is not.


apt-get install nfs-common   should work after of course you   mkdir -p /var/cache/apt/archives/partial

[jdonth]

I am getting the following error when trying to connect via NFS:
mount: server 192.168.1.91 not responding, timed out
Root-NFS: Server returned error -5 while mounting /home/sheeva

Any thoughts or suggestions?
~Joe Donth


I am connecting to a Ubuntu Linux host.

/etc/exports:
/home/ *(rw,sync,no_root_squash)
/tftpboot/ *(rw,sync,no_root_squash)



U_Boot environment

Code:

Marvell>> print
baudrate=115200
loads_echo=0
netmask=255.255.255.0
CASset=min
MALLOC_len=1
ethprime=egiga0
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end)
$(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethaddr=00:50:43:01:C1:FB
run_diag=no
ipaddr=192.168.1.103
serverip=192.168.1.91
image_name=uImage.sheeva.040309
console=console=ttyS0,115200 mtdparts=nand_flash:0x100000@0x000000(u-boot),0x400000@0x10000 0(uImage),0x1f800000@0x500000(rootfs)rw
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
bootcmd=tftpboot 0x2000000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(
serverip)$(bootargs_end); bootm 0x2000000
bootargs=console=ttyS0,115200 mtdparts=nand_flash:0x100000@0x000000(u-boot),0x400000@0x10000 0(uImage),0x1f800000@0x500000(rootfs)rw
 root=/dev/nfs rw nfsroot=192.168.1.91:/home ip=192.168.1.103:192.168.1.91:::DB88FXX81:eth0:none
ethact=egiga0
rootpath=/home/sheeva
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes

Environment size: 1534/131068 bytes

boot process:

Code:

        __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Mar 16 2009 - 18:03:32) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CEE80

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Using egiga0 device
TFTP from server 192.168.1.91; our IP address is 192.168.1.103
Filename 'uImage.sheeva.040309'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###############
done
Bytes transferred = 2070316 (1f972c hex)
## Booting image at 02000000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-04-04   1:49:44 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2070252 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux...
................. done, booting the kernel.
Linux version 2.6.22.18 (root@localhost.localdomain) (gcc version 4.2.0 20070413 (prerelease)) #1 Fri Apr 3 18:49:38 PDT 2009

<<<<...SNIP...>>>>>

md: autorun ...
md: ... autorun DONE.
Looking up port of RPC 100003/2 on 192.168.1.91
eth0: link up, full duplex, speed 100 Mbps
Looking up port of RPC 100005/1 on 192.168.1.91
mount: server 192.168.1.91 not responding, timed out
Root-NFS: Server returned error -5 while mounting /home/sheeva
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00       1024 mtdblock0 (driver?)
1f01       2048 mtdblock1 (driver?)
1f02     521216 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

[freebsdfan@hotmail.com]

This looks like your trying to mount a nfs share onto the Sheevaplug.  You first need to install nfs-common.  The nfs client is installed but common is not.


apt-get install nfs-common   should work after of course you   mkdir -p /var/cache/apt/archives/partial

Thank you!  That in fact worked and I was able to verify my NFS share and I've now been able NFS boot a newly
compiled kernel with the supplyed rootfs w/o touching flash (well, almost ... I had to set some Uboot env vars).

Skip

[hammerinhank]

I am getting the following error when trying to connect via NFS:
mount: server 192.168.1.91 not responding, timed out
Root-NFS: Server returned error -5 while mounting /home/sheeva

Any thoughts or suggestions?
~Joe Donth


I am connecting to a Ubuntu Linux host.

/etc/exports:
/home/ *(rw,sync,no_root_squash)
/tftpboot/ *(rw,sync,no_root_squash)



U_Boot environment

Code:

Marvell>> print
baudrate=115200
loads_echo=0
netmask=255.255.255.0
CASset=min
MALLOC_len=1
ethprime=egiga0
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end)
$(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethaddr=00:50:43:01:C1:FB
run_diag=no
ipaddr=192.168.1.103
serverip=192.168.1.91
image_name=uImage.sheeva.040309
console=console=ttyS0,115200 mtdparts=nand_flash:0x100000@0x000000(u-boot),0x400000@0x10000 0(uImage),0x1f800000@0x500000(rootfs)rw
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
bootcmd=tftpboot 0x2000000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(
serverip)$(bootargs_end); bootm 0x2000000
bootargs=console=ttyS0,115200 mtdparts=nand_flash:0x100000@0x000000(u-boot),0x400000@0x10000 0(uImage),0x1f800000@0x500000(rootfs)rw
 root=/dev/nfs rw nfsroot=192.168.1.91:/home ip=192.168.1.103:192.168.1.91:::DB88FXX81:eth0:none
ethact=egiga0
rootpath=/home/sheeva
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes

Environment size: 1534/131068 bytes

boot process:

Code:

        __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Mar 16 2009 - 18:03:32) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CEE80

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Using egiga0 device
TFTP from server 192.168.1.91; our IP address is 192.168.1.103
Filename 'uImage.sheeva.040309'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###############
done
Bytes transferred = 2070316 (1f972c hex)
## Booting image at 02000000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-04-04   1:49:44 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2070252 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux...
................. done, booting the kernel.
Linux version 2.6.22.18 (root@localhost.localdomain) (gcc version 4.2.0 20070413 (prerelease)) #1 Fri Apr 3 18:49:38 PDT 2009

<<<<...SNIP...>>>>>

md: autorun ...
md: ... autorun DONE.
Looking up port of RPC 100003/2 on 192.168.1.91
eth0: link up, full duplex, speed 100 Mbps
Looking up port of RPC 100005/1 on 192.168.1.91
mount: server 192.168.1.91 not responding, timed out
Root-NFS: Server returned error -5 while mounting /home/sheeva
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00       1024 mtdblock0 (driver?)
1f01       2048 mtdblock1 (driver?)
1f02     521216 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

You need to change the interface from hdcp to static.  In your nfs filesystem on the nfs server go to the etc/network/interfaces file and change:

iface eth0 inet dhcp

to:

iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1

replacing the address with the one you set in uboot.