Go to previous topic
Go to next topic
Last Post 13 Sep 2011 02:10 PM by  DarenYeo
AM3517 NFS boot Failing
 0 Replies
Author Messages
DarenYeo
New Member
New Member
Posts:4


--
13 Sep 2011 02:10 PM
    I have a AM3517 EVM and am following the Linux User Guide Software Documentation by Logic PD. I got stuck attempting to boot from NFS (see section 4.4)

    I am new to Linux, so my problem could be on my Ubuntu 11.04 PC side of network too.

    Here is the last part of the boot output:

    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, id=7c0f1)
    Sending DHCP requests .
    PHY: ffffffff:00 - Link is Up - 100/Full
    ., OK
    IP-Config: Got DHCP answer from 192.168.0.1, my address is 192.168.0.163
    IP-Config: Complete:
    device=eth0, addr=192.168.0.163, mask=255.255.255.0, gw=192.168.0.1,
    host=192.168.0.163, domain=internal, nis-domain=(none),
    bootserver=192.168.0.1, rootserver=192.168.0.150, rootpath=
    Looking up port of RPC 100003/2 on 192.168.0.150
    Looking up port of RPC 100005/1 on 192.168.0.150
    VFS: Mounted root (nfs filesystem) on device 0:11.
    Freeing init memory: 164K
    INIT: version 2.86 booting
    Please wait: booting...
    Starting udev
    kjournald starting. Commit interval 5 seconds
    EXT3-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is recommended
    kjournald starting. Commit interval 5 seconds
    EXT3-fs (mmcblk0p2): using internal journal
    EXT3-fs (mmcblk0p2): recovery complete
    EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
    EXT3-fs (mmcblk0p3): using internal journal
    EXT3-fs (mmcblk0p3): recovery complete
    EXT3-fs (mmcblk0p3): mounted filesystem with writeback data mode
    Remounting root file system...
    Caching udev devnodes
    Populating dev cachemv: cannot rename '/tmp/devices': No such file or directory
    root: mount: mounting rootfs on / failed: No such file or directory
    root: mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
    NOT configuring network interfaces: / is an NFS mount
    Wed Sep 7 09:42:00 UTC 2011
    INIT: Entering runlevel: 5
    Starting telnet daemon.
    Starting syslogd/klogd: done

    And this is where it hangs - I believe it has something to do with where and how the rootfs is setup on the PC, but I am not sure how to correct the problem.

    The AM3517 EVM printenv is:

    bootdelay=10
    baudrate=115200
    loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
    bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
    loaduimage=fatload mmc 0 ${loadaddr} uImage
    mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
    nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr}
    dieid#=0e24000100000000015da3960e012006
    ethact=DaVinci EMAC
    ethaddr=00:08:00:28:00:0f:25:9b
    bootfile=uImage
    loadaddr=0x83000000
    console=ttyS2,115200n8
    rootpath=/opt/nfs-exports/am3517
    nfsoptions=,wsize=1500,rsize=1500
    loadnet=tftpboot ${loadaddr} ${serverip}:${bootfile};
    loadfl=nand device 0; nand read ${loadaddr} 0x280000 0x500000;
    loadmmc=mmc init; fatload mmc 0 ${loadaddr} ${bootfile};
    nandargs=setenv bootargs console=${console} root=/dev/mtdblock4 rw rootfstype=jffs2 ${otherbootargs};
    mmcargs=setenv bootargs console=${console} root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait ${otherbootargs};
    nfsargs=setenv bootargs console=${console} root=/dev/nfs rw nfsroot=${serverip}:${rootpath}${nfsoptions} ip=dhcp ${otherbootargs};
    stdin=serial
    stdout=serial
    stderr=serial
    otherbootargs=bootwait=4
    bootargs=console=ttyS2,115200n8 root=/dev/nfs rw nfsroot=192.168.0.150:/opt/nfs-exports/am3517,wsize=1500,rsize=1500 ip=dhcp bootwait=4
    filesize=2338E4
    fileaddr=83000000
    netmask=255.255.255.0
    ipaddr=192.168.0.200
    serverip=192.168.0.150

    Can anyone see what I have wrong? Is there any other information which would be helpful to check?
    Thank You
    -Daren


    ---