From: Eugene Surovegin <ebs@ebshome.net>
To: Shawn Jin <shawnxjin@gmail.com>
Cc: ppcembed <linuxppc-embedded@ozlabs.org>
Subject: Re: Incomplete network configuration information when booting from NFS root on Ebony
Date: Tue, 15 Feb 2005 18:59:21 -0800 [thread overview]
Message-ID: <20050216025921.GA25838@gate.ebshome.net> (raw)
In-Reply-To: <c3d0340b05021518037b1758cc@mail.gmail.com>
On Tue, Feb 15, 2005 at 06:03:12PM -0800, Shawn Jin wrote:
> Is anybody using linux-2.6.10 from kernel.org for testing IBM Ebony board?
Yes, with stock boot loader and great success (bootp + NFS root). I
just use "ip=on root=/dev/nfs" and let my bootp server tell the kernel
about all other parameters.
[snip]
> However a new problem
> occurs. When the kernel tries to mount a NFS root filesystem, it
> complains incomplete network configuration information. See the
> following message dump. Any hints to solve the problem? Thanks a lot.
[snip]
> Kernel command line: root=/dev/nfs rw
> nfsroot=192.68.0.47:/opt/eldk3.1/ppc_4xx
> ip=192.168.0.245:192.168.0.47:::::off
[snip]
> IP-Config: Incomplete network configuration information.
Did you try looking at net/ipv4/ipconfig.c? This is file responsible
for this message.
I think there is relevant comment in ip_auto_config() function:
/*
* If the config information is insufficient (e.g., our IP address or
* IP address of the boot server is missing or we have multiple network
* interfaces and no default was set), use BOOTP or RARP to get the
* missing values.
*/
Probably your case - multiple ethernet devices (440GX has 4) and
you haven't specified which device should be assigned IP.
--
Eugene
next prev parent reply other threads:[~2005-02-16 2:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 2:03 Incomplete network configuration information when booting from NFS root on Ebony Shawn Jin
2005-02-16 2:59 ` Eugene Surovegin [this message]
2005-02-16 16:59 ` Shawn Jin
2005-02-16 17:35 ` Eugene Surovegin
2005-02-16 10:27 ` Eugene Surovegin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050216025921.GA25838@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=shawnxjin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).