I did mount NFS but I can't next

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

I did mount NFS but I can't next

Jump to solution
941 Views
yongkimin
Contributor III

Hi everybody.

I did mount NFS but I did't next to do.

eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)

IP-Config: Complete:

     device=eth0, addr=192.168.1.103, mask=255.255.255.0, gw=255.255.255.255,

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

     bootserver=192.168.1.101, rootserver=192.168.1.101, rootpath=

Looking up port of RPC 100003/3 on 192.168.1.101

PHY: 0:00 - Link is Up - 100/Full

Looking up port of RPC 100005/3 on 192.168.1.101

VFS: Mounted root (nfs filesystem) on device 0:14.

Freeing init memory: 160K

init started: BusyBox v1.15.0 ()

starting pid 1093, tty '': '/etc/rc.d/rcS'

Mounting /proc and /sys

Setting the hostname to freescale

Mounting filesystems

mount: mounting shm on /dev/shm failed: No such file or directory

mount: mounting usbfs on /proc/bus/usb failed: No such file or directory

Starting inetd:

starting pid 1122, tty '': '/sbin/getty -L ttyAM0 115200 vt100'

process '/sbin/getty -L ttyAM0 115200 vt100' (pid 1122) exited. Scheduling for restart.

starting pid 1123, tty '': '/sbin/getty -L ttyAM0 115200 vt100'

process '/sbin/getty -L ttyAM0 115200 vt100' (pid 1123) exited. Scheduling for restart.

As you see above I don't understand repeat log tty..

I'm using iMX285 and ubuntu 9.04 and ltib version L2.6.35_10.12.01 version.

The board designed by me can connected to Ubuntu by ping test. I'm using cross cable so I don't use dhcp option when NFS settings.

My board use NAND boot.

I did success after tftpboot and also success nfs boot.

My u-boot version is 2009.08. I did download a u-boot to my NAND boot board.

After u-boot boot I do tftpboot command then the board download the image from tftp server in my Ubuntu PC.

After tftpboot I did boot command then the terminal show the boot log. But below log repeat..

starting pid 1122, tty '': '/sbin/getty -L ttyAM0 115200 vt100'

process '/sbin/getty -L ttyAM0 115200 vt100' (pid 1122) exited. Scheduling for restart.

starting pid 1123, tty '': '/sbin/getty -L ttyAM0 115200 vt100'

process '/sbin/getty -L ttyAM0 115200 vt100' (pid 1123) exited. Scheduling for restart.

The u-boot settings is no problem. This settings is same as EVK board. EVK test is good.

Who can tell me the reason?

Thank you.

Labels (2)
0 Kudos
1 Solution
513 Views
yongkimin
Contributor III

Thanks for Yongcail Huang answer!

I did review my Ubuntu directory and files. I didn't find /etc/rc.d/rc_mxc.S.

I find different files.

drwxr-xr-x  2 root root     4096 2013-11-05 17:33 rc0.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc1.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc2.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc3.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc4.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc5.d

drwxr-xr-x  2 root root     4096 2013-11-05 17:33 rc6.d

-rwxr-xr-x  1 root root      306 2009-04-20 22:59 rc.local

drwxr-xr-x  2 root root     4096 2013-11-05 13:25 rcS.d

I solved this rebuild image.

./ltib --selectyp

Choose the packages profile

Selection (Minimum bootable root filesystem) --> (instead mfg firmware profile)

and disable Build mfg firmware

and rebuild ./ltib -f

The reason is above.

Thanks.

View solution in original post

0 Kudos
2 Replies
513 Views
AnsonHuang
NXP Employee
NXP Employee

Hi, Yongki

     Can you check your NFS's setting of tty device? Such as on my i.MX6 platform, if I use ttymxc0, then I need to have below config in my NFS, your case is same as mine if I comment out the ttymxc0 line. So the issue must be the console you set in uboot is not matching the one in NFS.

./etc/rc.d/rc_mxc.S

  1 #!/bin/bash

  2 #

  3 if grep -sq ttymxc0 /proc/cmdline; then

  4         /sbin/getty -L ttymxc0 115200 vt100

  5 elif grep -sq ttymxc1 /proc/cmdline; then

  6         /sbin/getty -L ttymxc1 115200 vt100

  7 elif grep -sq ttymxc2 /proc/cmdline; then

  8         /sbin/getty -L ttymxc2 115200 vt100

  9 elif grep -sq ttymxc3 /proc/cmdline; then

10         /sbin/getty -L ttymxc3 115200 vt100

11 else

12         sleep 100000

13 fi

0 Kudos
514 Views
yongkimin
Contributor III

Thanks for Yongcail Huang answer!

I did review my Ubuntu directory and files. I didn't find /etc/rc.d/rc_mxc.S.

I find different files.

drwxr-xr-x  2 root root     4096 2013-11-05 17:33 rc0.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc1.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc2.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc3.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc4.d

drwxr-xr-x  2 root root     4096 2013-11-06 18:35 rc5.d

drwxr-xr-x  2 root root     4096 2013-11-05 17:33 rc6.d

-rwxr-xr-x  1 root root      306 2009-04-20 22:59 rc.local

drwxr-xr-x  2 root root     4096 2013-11-05 13:25 rcS.d

I solved this rebuild image.

./ltib --selectyp

Choose the packages profile

Selection (Minimum bootable root filesystem) --> (instead mfg firmware profile)

and disable Build mfg firmware

and rebuild ./ltib -f

The reason is above.

Thanks.

0 Kudos