NFS with the IMX27 board

[aurelihein]

I successfully cross compiled with LTIB the linphone application from the fs.bluewind.it website.
I downloaded the kernel on the board, the problem is that the rootfs.jffs2 is to big to fit on the NOR flash...

So i tried to boot from nfs...
My daemon nfs is working correctly because i can mount it from a distant computer...
But I am not able to do it from the iMX27 board

Here is what i did :
fis load kernel
exec -c "root=/dev/nfs nfsroot=192.168.49.30:/tftpboot console=ttymxc0  ip=192.168.49.179:192.168.49.30:192.168.49.254:255.255.255.0:imx27:ff"

here is what i get :

eth0: using half-duplex 10Base-T (RJ-45)

IP-Config: Complete:

      device=eth0, addr=192.168.49.179, mask=255.255.255.0, gw=192.168.49.254,

     host=imx27, domain=, nis-domain=(none),

     bootserver=192.168.49.30, rootserver=192.168.49.30, rootpath=

Looking up port of RPC 100003/2 on 192.168.49.30

Looking up port of RPC 100005/1 on 192.168.49.30

VFS: Mounted root (nfs filesystem).

Freeing init memory: 192K

Setting the hostname to freescale
Mounting /proc and /sys
Starting the hotplug events dispatcher udevd
Synthesizing initial hotplug events
Mounting filesystems
Starting syslogd and klogd
Running depmod
Setting up networking on loopback device:
Setting up networking on eth0:

Adding static route for default gateway to 172.27.255.254:
nfs: server 192.168.49.30 not responding, still trying

nfs: server 192.168.49.30 not responding, still trying


Thanks for your help,

aurelien

[Yuri]

Default network (NFS, non-DHCP) configuration uses internal Freescale IP resources, that, of course, are not accessible for most (non Freescale) users.

Please try static IP configuration during system configuring as follows :

./ltib -c

Select :

Target System Configuration
Options ->
Start Networking
Network setup ->
Enable interface 0
[] IP address
…

Then enter (target) IP, appropriate for your network,
say 192.168.1.150, netmask =255.255.255.0, set gateway
address, if your target MX27 board is placed in local
net (for example – 192.168.1.64) and finally – nameserver IP address (say, 192.168.1.83), where your NFS is hosted.

After Linux kernel and file system are built, in target redboot the following may be entered as an example :

load -r -b 0x100000 /iMX27/zImage

exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/nfs nfsroot=192.168.1.83:/ltib/ltib-imx27ads-20070522/rootfs init=/linuxrc ip=192.168.1.150:192.168.1.83"

Message Edited by Yuri on 2008-08-25 12:14 PM

[aurelihein]

So everything was ok, actually the problem was my network configuration in the LTIB, My board changed its IP since I booted from NFS, so it couldn't find anymore the NFS server
thanks,

[eriko]

You could try nfs over tcp instead of the default udp, in my case it works more reliable:

nfsroot=192.168.49.30:/tftpboot,rsize=8192,wsize=8192,hard,intr,tcp,nolock