From: Tahoma Toelkes <tahoma@nshore.com>
To: Yoichi Yuasa <yuasa@hh.iij4u.or.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: difficulties with NFSROOT and DHCP
Date: Mon, 09 Feb 2004 17:14:56 -0600 [thread overview]
Message-ID: <40281470.1000701@nshore.com> (raw)
In-Reply-To: <20040210064821.7ef6a72f.yuasa@hh.iij4u.or.jp>
Yes! That was the trick. I've now booted and am able to ping the
board. Thank you, thank you, thank you.
If you're ever in Austin, Yoichi, you should let me treat you to a
pitcher of beer (or a bottle of wine/sake...whatever). :-)
Thanks again,
-- Tahoma
Yoichi Yuasa wrote:
>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 parent reply other threads:[~2004-02-09 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 20:41 difficulties with NFSROOT and DHCP Tahoma Toelkes
2004-02-09 21:48 ` Yoichi Yuasa
2004-02-09 23:14 ` Tahoma Toelkes [this message]
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=40281470.1000701@nshore.com \
--to=tahoma@nshore.com \
--cc=linux-mips@linux-mips.org \
--cc=yuasa@hh.iij4u.or.jp \
/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