Unable to mount root fs via NFS (imx287 - u-boot)

[vvg70]

I can't mount root fs via NFS on i.mx287. NFS server works correctly. I tested it from other linux PC.

Here is last messages

..........................................

TCP cubic registered

NET: Registered protocol family 17

can: controller area network core (rev 20090105 abi 8)

NET: Registered protocol family 29

can: raw protocol (rev 20090105)

can: broadcast manager protocol (rev 20090105 t)

regulator_init_complete: incomplete constraints, leaving vbus5v on

mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:00:21 UTC (21)

eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=0:00, ir

q=-1)

eth1: Freescale FEC PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=0:01, ir

q=-1)

IP-Config: Incomplete network configuration information.

Looking up port of RPC 100003/3 on 10.254.53.251

rpcbind: server 10.254.53.251 not responding, timed out

Root-NFS: Unable to get nfsd port number from server, using default

Looking up port of RPC 100005/3 on 10.254.53.251

rpcbind: server 10.254.53.251 not responding, timed out

Root-NFS: Unable to get mountd port number from server, using default

Root-NFS: Server returned error -110 while mounting /tftpboot/rootfs

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            8192 mtdblock0 (driver?)

b300         1902592 mmcblk0 driver: mmcblk

  b301         1893248 mmcblk0p1

  b302            1025 mmcblk0p2

  b303            1024 mmcblk0p3

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

and here is my environment

MX28 U-Boot > printenv

bootargs=console=ttyAM0,115200n8

bootdelay=3

baudrate=115200

netmask=255.255.255.0

bootfile="uImage"

loadaddr=0x42000000

bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk0p3 rw rootwait ip=dhcp

fec_mac=${ethaddr}

bootcmd_mmc=run bootargs_mmc; mmc read 0 ${loadaddr} 100 3000; bootm

ethact=FEC0

serverip=10.254.53.251

ethaddr=00:08:02:6B:A3:1A

nfsroot=/tftpboot/rootfs

bootcmd_net=run bootargs_nfs; bootm

bootcmd=run bootargs_nfs; bootm

bootargs_nfs=setenv bootargs ${bootargs} ip=dhcp root=/dev/nfs nfsroot=${serveri

p}:${nfsroot},v3,tcp; nfs ${loadaddr} ${serverip}:${nfsroot}/boot/uImage

ipaddr=10.254.53.249

stdin=serial

stdout=serial

stderr=serial

ver=U-Boot 2009.08 (Jul 10 2012 - 21:34:36)

Environment size: 704/130044 bytes

I have looked like problems of other people, tested their errors but I havn't got successful result.

Please help me!

[vvg70]

Hi All!

I resolved my problem. Marek was absolutly right. I simply havn't big experience.

Reason was in network settings. Firstly I set DHCP everywhere (in Target System Configuration and U-boot environment) but for some reason such variant didn't work. One of reasons is different ip leasing DHCP on different stage. Their combination don't work too. After I set IP everywhere explicitly NFS has been working.

Maybe somebode will encounter with such problem and see

       P-Config: Incomplete network configuration information.

Looking up port of RPC 100003/3 on 10.254.53.251

rpcbind: server 10.254.53.251 not responding, timed out

Root-NFS: Unable to get nfsd port number from server, using default

Looking up port of RPC 100005/3 on 10.254.53.251

rpcbind: server 10.254.53.251 not responding, timed out

Root-NFS: Unable to get mountd port number from server, using default

Root-NFS: Server returned error -110 while mounting /tftpboot/rootfs

VFS: Unable to mount root fs via NFS, trying floppy.

VFS: Cannot open root device "nfs" or unknown-block(2,0)

then let know the problem is in network settings.

Now my u-boot environment is such

MX28 U-Boot > printenv

bootargs=console=ttyAM0,115200n8

bootdelay=3

baudrate=115200

netmask=255.255.255.0

bootfile="uImage"

loadaddr=0x42000000

bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk0p3 rw rootwait ip=dhcp

fec_mac=${ethaddr}

bootcmd_mmc=run bootargs_mmc; mmc read 0 ${loadaddr} 100 3000; bootm

ethact=FEC0

ipaddr=10.254.53.249

ethaddr=00:04:00:00:00:00

serverip=10.254.53.245

bootcmd_net=run bootargs_nfs; bootm

bootcmd=run bootcmd_net

bootargs_nfs=setenv bootargs ${bootargs} ip=10.254.53.249:10.254.53.245:10.254.5

3.254:255.255.255.0:freescale:eth0 root=/dev/nfs nfsroot=${serverip}:${nfsroot}

v3

nfsroot=/tftpboot/rootfs

stdin=serial

stdout=serial

stderr=serial

ver=U-Boot 2009.08 (Jul 10 2012 - 21:34:36)

Environment size: 712/130044 bytes

Best regards,

Vladimir      

[vvg70]

Hi Fabio!

Thanks for your quick response. My settings are right and I changed my bootargs_nfs line. But perhaps reason is other. I found next messages in boot log:

.......

i.MX GPMI NFC

NFC: Version 1, 8-chip GPMI and BCH

gpmi-nfc: probe of gpmi-nfc.0 failed with error 1

.......

I will examine why this message appear.

Regards,

Vladimir.

[MarekVasut]

NAND could not be probed. That's what it means ;-)

Are you porting to a new board or is this an existing design ? What board is it ? What kernel do you use, can you try with upstream 3.7 (I know there were fixes for GPMI NAND there) ?

It is unrelated to NFS ;-)

[fabio_estevam]

I would recommend removing the 'nfs ${loadaddr} ${serverip}:${nfsroot}/boot/uImage' from your
bootargs_nfs line.

Also, make sure that in ltib you select dhcp option:

Target System Configuration

---Options --->

        Network setup  --->

         [*]   get network parameters using dhcp

Regards,

Fabio Estevam