Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 10 Sep 2007 03:52 AM by  titinger@digigram.com
NFS boot problem
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
titinger@digigram.com
New Member
New Member
Posts:


--
07 Sep 2007 07:34 AM
    Hi,

    i've loaded a linux kernel on my litekit, based on the freescale ltib iso, and the patches found on this forum (thanks to many of you for the great work!).

    the second stage loader passes the following kernel options :

    noinitrd console=ttymxc0 root=/dev/nfs nfsroot=192.168.1.102:/mnt/rootfs rw init=/linuxrc ip=192.168.1.103:192.168.1.102:192.168.1.102:255.255.255.0 noalign


    192.168.1.102 being the server, 192.168.1.103 the litekit, and /mnt/rootfs the folder where the all the OS files where copied from rootfs and rootfs/boot.

    in LoLo, I do

    ifconfig sm0 192.168.1.103 255.255.255.0 192.168.1.102
    load elf 0x800d0000 34792 /tftp/192.168.1.102:loader
    load raw 0x81000000 1620768 /tftp/192.168.1.102:zImage
    exec 0x800d000

    linux starts ok, mounts the NFS root and hangs with the following message :


    eth0: SMSC911x/921x identified at 0xc7a00000, IRQ: 90

    eth0: SMSC911x MAC Address: 00:08:ee:01:67:fa

    eth0: link down

    IP-Config: Complete:

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

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

    bootserver=192.168.1.102, rootserver=192.168.1.102, rootpath=

    Looking up port of RPC 100003/2 on 192.168.1.102

    eth0: link up, 100Mbps, full-duplex, lpa 0x8DE1

    Looking up port of RPC 100005/1 on 192.168.1.102

    VFS: Mounted root (nfs filesystem).

    Freeing init memory: 116K

    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

    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.1.102 not responding, still trying

    nfs: server 192.168.1.102 not responding, still trying

    ***
    I'm not sure on what side to look, i've spent quite some time on checking the server side, tried with dhcp instead of static ip, but at best it fails at the same point.

    here are my conf files on server side :

    /etc/exports
    /mnt/rootfs 192.168.1.103/255.255.255.0(rw,no_root_squash)

    /ect/inetd.conf
    tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /mnt/rootfs/

    any suggestions ?

    thank you
    Marc.
    ashwinb@logicpd.com
    New Member
    New Member
    Posts:


    --
    07 Sep 2007 08:50 AM
    Posted By mtrdgm on 7 Sep 2007 7:34 AM
    Setting up networking on eth0:

    Adding static route for default gateway to 172.27.255.254:

    nfs: server 192.168.1.102 not responding, still trying

    nfs: server 192.168.1.102 not responding, still trying



    Marc, it is these lines that indicate what your problem might be. Take a look at the networking scripts on the server in /mnt/rootfs. If the scripts follow the Redhat style configuration, then you'd want to look at /etc/sysconfig/network-scripts/ifcfg-eth0. If they follow the Debian style scripts, look for /etc/network/interfaces. Either way, you'd want to see how eth0 is being configured here.

    You've chosen a static IP address for Linux and the eth0 configuration should preserve that same scheme. It looks like the configuration scripts are changing the IP to fall within the 172.27.x.x domain and that will, obviously, disable your access to the 192.168.1.x domain, thus the NFS error..

    Regards
    titinger@digigram.com
    New Member
    New Member
    Posts:


    --
    10 Sep 2007 03:52 AM
    Thank you Cypher !

    I'm happy now, indeed the rootfs/etc/rc.d/rc.conf file needed to be set up with the right ip addresses.

    Regards,

    Marc.
    You are not authorized to post a reply.