imx31-3 stack board with new linux PDK 1.4 Bsp :The NFS File system is not booting

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

imx31-3 stack board with new linux PDK 1.4 Bsp :The NFS File system is not booting

3,626 Views
Ramesh_Danlaw
Contributor I
Hi ,
  I am facing a problem in mounting the nfs file system  with the new linux PDK1.4 on the imx31-3 stack board. I did have this problem with the old linux bsp and the redboot.
 
With the new PDK Linux version1.4 , i am facing problem in mounting the NFS .
 
I am giving the following command during the kernel boot up. 
 
 
exec -c "noinitrd console=ttymxc0 root=/dev/nfsroot rootfstype=nfsroot  nfsroot=192.168.1.84:/tftpboot/Disk-Tftp/rootfs ip=192.168.1.83:192.168.1.84"
 
(The NFS Server ip address is 192.168.1.84  and the imx31-3 stack board ip address is 192.168.1.83.)
 
The following error messages are coming on the hyperterminal
 
 
 
eth0: link down
IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
      device=eth0, addr=192.168.1.83, mask=255.255.255.0, gw=255.255.255.255,
     host=192.168.1.83, domain=, nis-domain=(none),
     bootserver=192.168.1.84, rootserver=192.168.1.84, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.84
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
rpcbind: server 192.168.1.84 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.84
rpcbind: server 192.168.1.84 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 192.168.1.84 not responding, timed out
Root-NFS: Server returned error -5 while mounting /tftpboot/Disk-Tftp/rootfs
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfsroot" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00       1024 mtdblock0 (driver?)
1f01       5120 mtdblock1 (driver?)
1f02      98304 mtdblock2 (driver?)
1f03       8192 mtdblock3 (driver?)
1f04     149504 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
 
 
When i check the  /var/log/messages    i did not find any request coming from the imx31-stack board for nfs mounting.
 
Could any one help what is the problem?
 
 
 
Regds,
S.Ramesh CHandra.
 
 
 
 
0 Kudos
Reply
6 Replies

1,020 Views
fabio_estevam
NXP Employee
NXP Employee
Also, besides the NFS testing your command line looks incorrect. Try something like:

exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/nfs nfsroot=192.168.1.1:/tftpboot/ltib init=/linuxrc ip=dhcp"

0 Kudos
Reply

1,020 Views
Ramesh_Danlaw
Contributor I
Hi,
 
   Thanks for your response.
 
1.Rsponse to :
              mount 192.168.1.84:/tftpboot/Disk-Tftp/rootfs  /mnt
             cd /mnt
             ls
      I am able to mount the file system with the above command on the host whose ip is 192.168.1.84.
     I see the request is logged in the    "/var/log/messages" file.
    With "ls" command , i am able to see the root file system in '"mnt"
 
2.Rsponse to :
 
 
          
Also, besides the NFS testing your command line looks incorrect. Try something like:

exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/nfs nfsroot=192.168.1.1:/tftpboot/ltib init=/linuxrc ip=dhcp"

 i tried the above but failed to mount the file system.
   
 i am getting the  following on the hyperterminal
 
 
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfsroot" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00       1024 mtdblock0 (driver?)
1f01       5120 mtdblock1 (driver?)
1f02      98304 mtdblock2 (driver?)
1f03       8192 mtdblock3 (driver?)
1f04     149504 mtdblock4 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
 
When i checked in the "/var/log/messages" file i am not able to see any request for the NFS Mount. The board is not sending the NFS mount request to the NFS Host server.
 
3.Question:
 
       I was able to use the same with the PDK1.2 LINUX and my own compiled linux root file system(or any root file system) and successfully mounted the root file system.
 
   With the new redboot and new PDK1.4 Linux BSP i am not able to load the NFS Root file system.
  Now even i am not able to use my old redboot now .
 
  is the problem is with the Redboot (as i am not able to run the old redboot even after i tried with erasing all the flash and download the  old redboot)? Why i am only able to use the new redboot not the old redboot?
        0R
 is it the problem with the linux compilation?
 
What type of the root filesystems the new linux PDK 1.4 Supports?
Do i need to use only a specific file system for this PDK1.4?
 
 
 
Thank you,
S.Ramesh Chandra.
 
 
 
 
 
 
0 Kudos
Reply

1,020 Views
fabio_estevam
NXP Employee
NXP Employee
Did you select NFS in Target Image Generation?
 
Please do a ./ltib -c , then on Target Image Generation you need to select  (*) NFS only
 
Then under Target System Configuration, mark [*] start networking, then click on Network setup ---> and fill  your network parameters or mark " [*] get network parameters using dhcp " option if you want to use dhcp.
 
Regards,
 
Fabio Estevam
 
 
0 Kudos
Reply

1,020 Views
Ramesh_Danlaw
Contributor I
Hi Fabio Estevam,
 
   Thanks for your response.
 
 I compiled for the NFS Only.
 I tested the kernel compiled with the network setup and with DHCP.
 
I have one quesiton.
  I compiled a kernel with some net work setup.
  by using the ./ltib -c  and changed the network setup to DHCP , is the  'zImage' is going to change or not. Or only the system configuration files changes?
 
In any case i am not able to mount the NFS. Is there any problem with the bootloader?
 
Thank you,
S.Ramesh Chandra.
0 Kudos
Reply

1,020 Views
fabio_estevam
NXP Employee
NXP Employee
When you select the NFS option it will not change the kernel. Only the deployment option is changed.
 
Also, make sure you are using the bootloader that comes with SDK1.4. I suggest you to do a full erase of the NAND using the ATK tool from Freescale website and then re-flash it with the Redboot 200834 that comes with SDK1.4.
 
Regards,
 
Fabio Estevam
0 Kudos
Reply

1,020 Views
fabio_estevam
NXP Employee
NXP Employee
Check if your NFS server is working. Are you able to mount your rootfs in the Linux host? For example:
 
mount 192.168.1.84:/tftpboot/Disk-Tftp/rootfs  /mnt
cd /mnt
ls
 
Does it work?
 
Regards,
 
Fabio Estevam
 
 
0 Kudos
Reply