linux-mips
[Top] [All Lists]

Re: difficulties with NFSROOT and DHCP

To: Tahoma Toelkes <tahoma@nshore.com>
Subject: Re: difficulties with NFSROOT and DHCP
From: Yoichi Yuasa <yuasa@hh.iij4u.or.jp>
Date: Tue, 10 Feb 2004 06:48:21 +0900
Cc: yuasa@hh.iij4u.or.jp, linux-mips@linux-mips.org
In-reply-to: <4027F08D.5030601@nshore.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <4027F08D.5030601@nshore.com>
Sender: linux-mips-bounce@linux-mips.org
Hi,

On Mon, 09 Feb 2004 14:41:49 -0600
Tahoma Toelkes <tahoma@nshore.com> wrote:

> The context is that I am in the process of bringing up a 2.4.24 kernel 
> (pulled from linux-mips CVS using the linux_2_4_24 tag) on a DBAu1500 
> board (Zinfandel).
> 
> I'm having trouble mounting my root filesystem over NFS.  After the 
> ethernet ports have been enumerated, the kernel attempts to contact the 
> DHCP server to obtain its IP configuration information.  At this point 
> the boot sequence hangs, perpetually retrying the DHCP server.  Here are 
> the last several lines from the log of the boot messages, prefixed with 
> a vertical bar to set them apart:
> 
> | Sending DHCP requests .<6>eth0: link up
> | eth0: going to full duplex
> | ..... timed out!
> | IP-Config: Retrying forever (NFS root)...
> | Sending DHCP requests ...... timed out!
> | IP-Config: Retrying forever (NFS root)...
> | Sending DHCP requests ..
> 
> I've verified that the exported root filesystem can be mounted by 
> another Linux workstation.  I've also verified on the DHCP server that 
> it is seeing the board initiate a DHCP discovery and that the DHCP 
> server is replying with offer for the correct address.  Here is an 
> excerpt from '/var/log/messages' on the DHCP server:
> 
> | Feb  9 13:25:33 kapala dhcpd: DHCPDISCOVER from 00:50:c2:0c:38:8a via eth0
> | Feb  9 13:25:33 kapala dhcpd: DHCPOFFER on 172.16.108.42 to 
> 00:50:c2:0c:38:8a via eth0

Please try the following option.

YAMON> go . root=/dev/nfs nfsroot=172.16.108.11:/export/root ip=dhcp


> For completeness sake, I've attached the full log of the boot sequence 
> until it hangs as well as my current kernel configuration.  If any of 
> you have seen this particular problem and know how to get around it, 
> please respond.  Further, if you simply have suggestions for avenues I 
> could explore, I would appreciate any advice you might have to offer.

Yoichi

<Prev in Thread] Current Thread [Next in Thread>