linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Jin <shawnxjin@gmail.com>
To: ppcembed <linuxppc-embedded@ozlabs.org>
Subject: Re: Incomplete network configuration information when booting from NFS root on Ebony
Date: Wed, 16 Feb 2005 08:59:02 -0800	[thread overview]
Message-ID: <c3d0340b05021608591692a460@mail.gmail.com> (raw)
In-Reply-To: <20050216025921.GA25838@gate.ebshome.net>

> > 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.

What's your boot loader? I should ask if anybody has successful story
on using uboot to boot 2.6.10 to test Ebony board.

> Did you try looking at net/ipv4/ipconfig.c? This is file responsible
> for this message.

Yes. I did find the comment you pointed and thought it might be a
problem. But another issue I don't understand is why it cannot fetch
MAC addresses from VPD? Without my hack the MAC addresses fetched from
VPD are all FF:FF:FF:FF:FF:FF. The Rom Monitor can detect the
addresses, which I guess are from VPD.

> /*
> * 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.

Do you know how to set a default active device?

Thanks,
-Shawn.

  reply	other threads:[~2005-02-16 16: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
2005-02-16 16:59   ` Shawn Jin [this message]
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=c3d0340b05021608591692a460@mail.gmail.com \
    --to=shawnxjin@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /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).