ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] ltib network error


From: Stuart Hughes
Subject: Re: [Ltib] ltib network error
Date: Wed, 06 Sep 2006 11:44:24 +0100

Hi Sivakumar,

What's happening is that you're booting the kernel with one IP address
and mounting the root filesystem using that, and later in the system
startup where the network is initialised it is getting changed.  When
this happens you lose the connection to the rootfs and get all those
'101' messages.

To fix this you need to run: './ltib --configure' in the configuration
screen either change the target's IP address to match the one for the
target board you used when booting, or don't start the network.
To find these options, go to:

--- Target System Configuration
    Options  ---> 

In there you'll see:
[*] start networking

Disable this and networking won't get started.

Or (and probably better), go into:

      Network setup  --->

And change the entry for IP address:
            [*] Enable interface 0
            (eth0) interface
            [ ]   get network parameters using dhcp
            (192.168.0.254) IP address

Regards, Stuart

On Wed, 2006-09-06 at 14:48 +0530, Sivakumar wrote:
> On Thursday 24 August 2006 8:37 pm, Paul Barrette wrote:
> sir, 
>    when i try to port the zImage to SDRAM,during 
> kernel installation iam getting the 
> following error.please suggest me to 
> overcome this 
>  
> Looking up port of RPC 100003/2 on 
> 192.168.1.205 
> Looking up port of RPC 100005/1 on 
> 192.168.1.205 
> VFS: Mounted root (nfs filesystem). 
> Mounted devfs on /dev 
> Freeing init memory: 116K 
> Setting the hostname to freescale 
> Mounting filesystems 
> Creating device symlinks: 
> Creating device nodes: 
> Starting syslogd and klogd 
> Setting up networking on loopback 
> device: 
> Setting up networking on eth0: 
> Adding static route for default 
> gateway to 172.27.RPC: sendmsg 
> returned error 101 
> 255.254: 
> nfs: RPC call returned error 101 
> /etc/rc.d/init.d/network: line 48: 
> route: command RPC: sendmsg returned 
> error 101 
> not found 
> nfs: RPC call returned error 101 
> RPC: sendmsg returned error 101 
> nfs: RPC call returned error 101 
> /etc/rc.d/init.d/network: line 49: 
> sed: command noRPC: sendmsg returned 
> error 101 
> t found 
> nfs: RPC call returned error 101 
> RPC: sendmsg returned error 101 
> nfs: RPC call returned error 101 
> /etc/rc.d/init.d/network: line 50: mv: 
> command not found 
> Setting RPC: sendmsg returned error 
> 101 
> nameserver to 172.27.0.1 in /etcnfs: 
> RPC call returned error 101 
> /resolv.conf: 
> /etc/rc.d/init.d/network: line 
> 53: /etc/resolv.conRPC: sendmsg 
> returned error 101 
> f: Network is unreachable 
> nfs: RPC call returned error 101 
> RPC: sendmsg returned error 101 
> nfs: RPC call returned error 101 
> Bummer, could not run '/sbin/getty': 
> Network is unreachable 
> RPC: sendmsg returned error 101 
> nfs: RPC call returned error 101 
> Bummer, could not run '/sbin/getty': 
> Network is unreachable 
> RPC: sendmsg returned error 101 
> nfs: RPC call returned error 101 
>  
>  
> regards 
> Sivakumar.R.J
> 
> 
> _______________________________________________
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]