Incomplete network configuration information when booting from NFS root on Ebony

Incomplete network configuration information when booting from NFS root on Ebony

[Shawn Jin]

Hi,

Is anybody using linux-2.6.10 from kernel.org for testing IBM Ebony board?

I found that 2.6.10 is not aware of U-Boot. That is, it neither
understands U-Boot's bd_info nor parses U-Boot's bootargs. So even if
the ethernet MAC address is set for EMAC0 on uboot, the kernel doesn't
get the value from it. Instead it reads MAC address from Ebony VPD,
which results in FF:FF:FF:FF:FF:FF. Isn't it strange that mac address
isn't set in its VPD?

After some hacks in arch/ppc/platforms/4xx/ebony.c, the kernel now can
get MAC address and boot arguments from uboot. 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.

## Transferring control to Linux (at address 00000000) ...
Linux version 2.6.10 (xjin@swl001.scs.agilent.com) (gcc version 3.3.3
(DENX ELDK 3.1 3.3.3-8)) #11 T
ue Feb 15 16:41:47 PST 2005
IBM Ebony port (MontaVista Software, Inc. (source@mvista.com))
Built 1 zonelists
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

<snipped>

mal0: Initialized, 4 tx channels, 2 rx channels
emac: IBM EMAC Ethernet driver, version 2.0
Maintained by Benjamin Herrenschmidt <benh@kernel.crashing.org>
zmii0: input 0 in SMII mode
eth0: IBM emac, MAC 00:04:ac:e3:1b:bb
eth0: Found Generic MII PHY (0x08)
zmii0: input 1 in RMII mode
eth1: IBM emac, MAC FF:FF:FF:FF:FF:FF
eth1: Found Generic MII PHY (0x09)

<--- only eth0's mac address is set on uboot -->

mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET: Registered protocol family 1
NET: Registered protocol family 17
eth0: Link is Up
eth0: Speed: 100, Full duplex.
IP-Config: Incomplete network configuration information.

????

Looking up port of RPC 100003/2 on 130.27.84.47
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 130.27.84.47
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get mountd port number from server, using default
RPC: sendmsg returned error 101
mount: RPC call returned error 101
Root-NFS: Server returned error -101 while mounting /opt/eldk3.1/ppc_4xx
VFS: Unable to mount root fs via NFS, trying floppy.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
 <0>Rebooting in 180 seconds..<6>eth0: Link is Up
eth0: Speed: 100, Full duplex.

-Shawn.

Re: Incomplete network configuration information when booting from NFS root on Ebony

[Eugene Surovegin]

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

Re: Incomplete network configuration information when booting from NFS root on Ebony

[Eugene Surovegin]

On Tue, Feb 15, 2005 at 06:03:12PM -0800, Shawn Jin wrote:


> zmii0: input 0 in SMII mode

...

> zmii0: input 1 in RMII mode

BTW, this is wrong. All inputs must be in the same mode. This is not a 
cause for you current problem, but will be the next one :).

--
Eugene

Re: Incomplete network configuration information when booting from NFS root on Ebony

[Shawn Jin]

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

Re: Incomplete network configuration information when booting from NFS root on Ebony

[Eugene Surovegin]

On Wed, Feb 16, 2005 at 08:59:02AM -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.
> 
> What's your boot loader? 

Default IBM one (OpenBIOS).

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

I'd suggest using standard IBM bootloader which is what Ebony comes 
with and make it work first, and only after this you should try to put 
non-standard one like u-boot. This is just common sense. If you need 
help with u-boot, there is a mail list for it. Ask quiestions there.

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

Doh, please, spend some time and read this ipconfig.c yourself. It has 
a big comment describing format of "ip=...":

<client-ip>:<server-ip>:<gw-ip>:<netmask>:<host name>:<device>:<PROTO>

--
Eugene.