NFS doent work with EVM SDK 1.0.2 and DVSDK

I can assure you it is possible to get it to work (mine does and many others as well) so I am sure there is some configuration issue here.

Have you tried configuring your U-Boot for mounting the root filesystem of the board over NFS? If so and that part is failing could you post your printenv output from U-Boot?

Based on the initial error you have there, my first thought would be some firewall issue, most NFS failures are either the firewall still being active on the host (check iptables) or the host having some NFS configuration issue (check exports file contents).

It looks like you are booting to a root file system and trying to nfs mount from the EVM.  To do an nfs mount on the EVM you need a few more packages built for ARM (mountd and some others I cannot remember).  The best way to nfs mount is to modify your u-boot bootargs so that you include "root=/dev/nfs rw nfsroot=192.168.1.1:/nfsdir,nolock,rsize=1024,wsize=1024"

Steve K.

Here are my printenv :

OMAP3EVM # printenv
baudrate=115200
ipaddr=192.168.1.10
preboot=
gatewayip=192.168.1.1
netmask=255.255.255.0
bootfile="uImage"
ethaddr=00:50:c2:7e:8b:5f
serverip=192.168.1.1
filesize=24BB44
get_kernel=run nand_kernel
get_initrd=run nand_initrd
nand_kernel=nand read.i 0x80000000 280000 200000
nand_initrd=nand read.i 0x81600000 780000 1000000
tftp_kernel=tftpboot 0x80000000 uImage
tftp_initrd=tftpboot 0x81600000 ramdisk.gz
bootargs_rd=mem=128M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,40M
 ramdisk_size=40960
bootargs_fs=mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw root
fstype=jffs2
bootargs_nfs=mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=/
mnt/nfs,nolock
addip=setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmas
k):$(hostname):eth0:on
boot_rd=run get_kernel; run get_initrd; setenv bootargs $(bootargs_rd); run addi
p; bootm 0x80000000
boot_fs=run get_kernel; setenv bootargs $(bootargs_fs); run addip; bootm 0x80000
000
boot_nfs=run get_kernel; setenv bootargs $(bootargs_nfs); run addip; bootm 0x800
00000
bootcmd=run boot_rd
bootdelay=20
stdin=serial
stdout=serial
stderr=serial
mmcboot=mmcinit;fatload mmc 0 0x80000000 uImage;fatload mmc 0 0x81600000 ramdisk
.gz;bootm 0x80000000
rootpath=/root/workdir/filesys
nfshost=192.168.1.1
bootargs=console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nftroot=192.168.1.1:/r
oot/workdir/filesys,nolock mem=88M video=omap24xxfb:rotation=90

Environment size: 1436/131068 bytes

pinging the server is good:

OMAP3EVM # ping 192.168.1.1
Reseting CHIP... Done
LAN9x18 (0x01150002) detected.
Setting mac address: 00:50:c2:7e:8b:5f
start Auto negotiation... (take ~2sec)
Auto negotiation complete, 100BaseTX, full duplex
host 192.168.1.1 is alive

then I load the kernel on flash to mem:

OMAP3EVM # run get_kernel

NAND read: device 0 offset 0x280000, size 0x200000

Reading data from 0x47f800 -- 100% complete.
 2097152 bytes read: OK

run boot:

OMAP3EVM # bootm 0x80000000

here are booting message:

## Booting image at 80000000 ...
   Image Name:   Linux-2.6.22.18-omap3
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1964420 Bytes =  1.9 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
...................................................................... done, boo
ting the kernel.
Linux version 2.6.22.18-omap3 (root@wei-desktop) (gcc version 4.2.1 (Sourcery G+
+ 4.2-107)) #1 Fri Apr 10 18:06:01 EDT 2009
CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f
Machine: OMAP3EVM Board
Memory policy: ECC disabled, Data cache writeback
BUG: map for 0x50000000 at 0xe0000000 can not be mapped using pages, ignoring.
OMAP3430ES1
SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
CPU0: D VIPT write-through cache
CPU0: cache: 768 bytes, associativity 1, 8 byte lines, 64 sets
Built 1 zonelists.  Total pages: 22352
Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nftroot=19
2.168.1.1:/root/workdir/filesys,nolock mem=88M video=omap24xxfb:rotation=90
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 88MB = 88MB total
Memory: 84992KB available (3636K code, 447K data, 140K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
twl4030: I2C Client[3] is not initialized[513]
twl4030: I2C Client[3] is not initialized[462]
SmartReflex driver initialized
OMAP DMA hardware revision 4.0
OMAP Display hardware version 2.0
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
i2c_omap i2c_omap.2: bus 2 rev3.12 at 100 kHz
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
TWL4030: TRY attach Slave TWL4030-ID0 on Adapter OMAP I2C adapter [1]
TWL4030: TRY attach Slave TWL4030-ID1 on Adapter OMAP I2C adapter [1]
TWL4030: TRY attach Slave TWL4030-ID2 on Adapter OMAP I2C adapter [1]
TWL4030: TRY attach Slave TWL4030-ID3 on Adapter OMAP I2C adapter [1]
TWL4030 Power Companion Active
<6>TWL4030: Driver registration complete.
TWL4030 GPIO Demux: IRQ Range 376 to 386, Initialization Success
Initialized TWL4030 USB module<5>SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 2.2a/db-0.5.2/dbg, musb-dma, host, debug=1
musb_platform_resume 171:
3430-resume()<7>HS USB OTG: revision 0x33, sysconfig 0x2015, sysstatus 0x1, intr
fsel 0x1, simenable  0x0
musb_hdrc: USB Host mode controller at c6000000 using DMA, IRQ 92
musb_hdrc musb_hdrc.0: MUSB HDRC host driver
musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.22.18-omap3 musb-hcd
usb usb1: SerialNumber: musb_hdrc.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb_init_controller 2149: HOST mode, status 0, devctl 19 A
NET: Registered protocol family 2
Time: 32k_counter clocksource has been installed.
Switched to high resolution mode on CPU 0
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
Power Management for TI OMAP.
cpuidle: using driver omap3_idle
create_proc_entry succeeded
create_proc_entry succeeded
NetWinder Floating Point Emulator V0.97 (double precision)
OMAP35x Linux PSP version 1.0.1 (OMAP3EVM)
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
musb_stage0_irq 699: CONNECT (a_host) devctl 5d
omap24xxfb: Options "rotation=90"
omap24xxfb: Rotation rotation=90
Console: switching to colour frame buffer device 80x30
omap24xxfb: fb0 frame buffer device (rotation support)
omap24xxfb: display mode 640x480x16@90  hsync 38kHz vsync 59Hz<6>omap_rng omap_r
ng: OMAP Random Number Generator ver. 70
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
usb 1-1: new high speed USB device using musb_hdrc and address 2
loop: module loaded
smc911x: Driver version 2007-07-13.
Linux video capture interface: v2.00
i2c /dev entries driver
OMAP HDQ Hardware Revision 0.5. Driver in interrupt mode.
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bi
t)
Creating 5 MTD partitions on "omap2-nand.0":
0x00000000-0x00080000 : "X-Loader-NAND"
0x00080000-0x00240000 : "U-Boot-NAND"
0x00240000-0x00280000 : "Boot Env-NAND"
0x00280000-0x00780000 : "Kernel-NAND"
0x00780000-0x10000000 : "File System - NAND"
OMAP2 OneNAND driver initializing
usbmon: debugfs is not available
usb 1-1: Product: USB2.0 Hub
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new low speed USB device using musb_hdrc and address 3
usb 1-1.1: Product: Logitech USB Keyboard
usb 1-1.1: Manufacturer: Logitech
usb 1-1.1: configuration #1 chosen from 1 choice
usb 1-1.2: new low speed USB device using musb_hdrc and address 4
usb 1-1.2: Product: Microsoft 5-Button Mouse with IntelliEye(TM)
usb 1-1.2: Manufacturer: Microsoft
usb 1-1.2: configuration #1 chosen from 1 choice
usb 1-1.3: new high speed USB device using musb_hdrc and address 5
usb 1-1.3: Product: U3 Cruzer Micro
usb 1-1.3: Manufacturer: SanDisk Corporation
usb 1-1.3: SerialNumber: 0000060426086446
usb 1-1.3: configuration #1 chosen from 1 choice
usbcore: registered new interface driver cdc_acm
drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB mod
ems and ISDN adapters
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbtest
input: omap_twl4030keypad as /class/input/input0
ads7846 spi1.0: touchscreen, irq 335
input: ADS784x Touchscreen as /class/input/input1
input: Logitech Logitech USB Keyboard as /class/input/input2
input: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-musb_hdrc.
0-1.1
input: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) as /class/input/in
put3
input: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(T
M)] on usb-musb_hdrc.0-1.2
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 200
7 UTC).
OMAP3430 TWL4030 Audio Support: Chip Rev[0x2f] Initialized
audio support initialized
usbcore: registered new interface driver snd-usb-audio
ALSA device list:
  #0: TWL4030
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
Buffer Size = 3686400
omap24xxvout: registered device video1 [v4l2]
Buffer Size = 3686400
omap24xxvout: registered device video2 [v4l2]
cpuidle: using governor menu
Root-NFS: No NFS server available, giving up.
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        512 mtdblock0 (driver?)
1f01       1792 mtdblock1 (driver?)
1f02        256 mtdblock2 (driver?)
1f03       5120 mtdblock3 (driver?)
1f04     254464 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

it looks like EVM cannot connect to NFS server,

but I tested NFS server from Windwos and it is working all right.

I really dont know what could go wrong now.

Thanks for your help!

wpl said:

Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nftroot=19
2.168.1.1:/root/workdir/filesys,nolock mem=88M video=omap24xxfb:rotation=90

Things I'd try:

a) add rsize=1024,wsize=1024

b) try mounting the server on another machine (mkdir test && mount -t nfs  192.168.1.1:/root/workdir/filesys test -o "nolock" && ls test)

c) if you dont have another machine, try booting using ramdisk (different procedure), then mount from the ramdisk the remote nfs filesystem

Looks like you have a spelling error,

bootargs=console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nftroot=192.168.1.1:/r
oot/workdir/filesys,nolock mem=88M video=omap24xxfb:rotation=90

That should be nfsroot= not nftroot=

Try this bootargs

bootargs console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=192.168.1.1:/r
oot/workdir/filesys,nolock,rsize=1024,wsize=1024 mem=88M video=omap24xxfb:rotation=90

Steve K.

Hi Steve,

I corrected the bootargs but still no luck.

here is my printenv:

baudrate=115200
ipaddr=192.168.1.10
preboot=
gatewayip=192.168.1.1
netmask=255.255.255.0
bootfile="uImage"
ethaddr=00:50:c2:7e:8b:5f
serverip=192.168.1.1
filesize=24BB44
get_kernel=run nand_kernel
get_initrd=run nand_initrd
nand_kernel=nand read.i 0x80000000 280000 200000
nand_initrd=nand read.i 0x81600000 780000 1000000
tftp_kernel=tftpboot 0x80000000 uImage
tftp_initrd=tftpboot 0x81600000 ramdisk.gz
bootargs_rd=mem=128M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,40M
 ramdisk_size=40960
bootargs_fs=mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw root
fstype=jffs2
bootargs_nfs=mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=/
mnt/nfs,nolock
addip=setenv bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmas
k):$(hostname):eth0:on
boot_rd=run get_kernel; run get_initrd; setenv bootargs $(bootargs_rd); run addi
p; bootm 0x80000000
boot_fs=run get_kernel; setenv bootargs $(bootargs_fs); run addip; bootm 0x80000
000
boot_nfs=run get_kernel; setenv bootargs $(bootargs_nfs); run addip; bootm 0x800
00000
bootcmd=run boot_rd
bootdelay=20
rootpath=/root/workdir/filesys
nfshost=192.168.1.1
bootargs=console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=192.168.1.1:/r
oot/workdir/filesys,nolock,rsize=1024,wsize=1024 mem=88M video=omap24xxfb:rotati
on=90
stdin=serial
stdout=serial
stderr=serial
mmcboot=mmcinit;fatload mmc 0 0x80000000 uImage;fatload mmc 0 0x81600000 ramdisk
.gz;bootm 0x80000000

Environment size: 1458/131068 bytes

when I boot with NFS I got:

Looking up port of RPC 100003/2 on 192.168.1.1
mmc0: host does not support reading read-only switch. assuming write-enable.
mmcblk0: mmc0:abcf SD04G 3979776KiB
 mmcblk0: p1 p2
rpcbind: server 192.168.1.1 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.1.1
rpcbind: server 192.168.1.1 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 192.168.1.1 not responding, timed out
Root-NFS: Server returned error -5 while mounting /root/workdir/filesys
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        512 mtdblock0 (driver?)
1f01       1792 mtdblock1 (driver?)
1f02        256 mtdblock2 (driver?)
1f03       5120 mtdblock3 (driver?)
1f04     254464 mtdblock4 (driver?)
b300    3979776 mmcblk0 driver: mmcblk
  b301     401593 mmcblk0p1
  b302    3574462 mmcblk0p2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

My Linux host ip address is 192.168.1.1

I can ping this ip from evm before booting.

when I run rpcinfo on my linux host I got:

rpcinfo -p

program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp  42589  status
    100024    1   tcp  55440  status
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100021    1   udp  60028  nlockmgr
    100021    3   udp  60028  nlockmgr
    100021    4   udp  60028  nlockmgr
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100021    1   tcp  51070  nlockmgr
    100021    3   tcp  51070  nlockmgr
    100021    4   tcp  51070  nlockmgr
    100005    1   udp  55239  mountd
    100005    1   tcp  36509  mountd
    100005    2   udp  55239  mountd
    100005    2   tcp  36509  mountd
    100005    3   udp  55239  mountd
    100005    3   tcp  36509  mountd

So I can see my NFS is runnig all right.

my /etc/exports is like:

/root/workdir/filesys 192.168.1.10(rw,sync,no_subtree_check)

My /etc/host.allow and host.dent is empty.

It loooks like everything is fine, but EVM just can not connect.

from the err message:

Root-NFS: Unable to get mountd port number from server, using default
mount: server 192.168.1.1 not responding, timed out
Root-NFS: Server returned error -5 while mounting /root/workdir/filesys

it looks like EVM can not connect to portmapper service , then it can not find the correct mountd port  or NFS port.

Nishanth,

I also tired to mount nfs after I booted into Linux and I got this.

[root@OMAP3EVM /]# mount -t nfs 192.168.1.1:/root/workdir/filesys /mnt/nfs
rpcbind: server localhost not responding, timed out
RPC: failed to contact local rpcbind server (errno 5).
rpcbind: server localhost not responding, timed out
RPC: failed to contact local rpcbind server (errno 5).
lockd_up: makesock failed, error=-5
rpcbind: server localhost not responding, timed out
RPC: failed to contact local rpcbind server (errno 5).
mount: mounting 192.168.1.1:/root/workdir/filesys on /mnt/nfs failed: Input/outp
ut error

Thank you all for your help!

The two key command to keep in mind are 'bootcmd' which tells u-boot where to find Linux kernel and 'bootargs' which passes arguments to Linux kernel and instructs where to find file-system; bootcmd runs first.

That said, the main problem I see is that your bootcmd calls on a series of 'run' commands that end up changing your bootargs; the bootargs being used to boot is only temporary (not saved via saveenv).  Bottom line, you are not really using the bootargs displayed by your log above as this is being temporarily overwritten right before boot process begins..  You may want to reconsider revising your bootcmd.

Juan, thanks for pointing ou that.

but I use bootm 0x80000000 instaed of boot, so I guess bootargs is sent to kernel when booting up

actually I did boot up in this order:

1. setenv bootargs to the nfs bootargs

2. run get_kernel

 this will load uimage from flash to 0x80000000

3. bootm 0x80000000

I assume this will boot p the kernel with the bootargs I just specified.

do you think these steps are all right/

Thanks!

Great.. happy hacking..