From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] question on drive
Date: Wed, 24 Nov 2004 11:30:14 +0100 [thread overview]
Message-ID: <20041124103019.B0D95C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 24 Nov 2004 10:14:33 +0100." <1f729c4804112401141cd5deb7@mail.gmail.com>
In message <1f729c4804112401141cd5deb7@mail.gmail.com> you wrote:
> I don't think this has to do with u-boot :) I think you should send
> this to the correct mailing list.
thanks for pointing out.
> > IP-Config: Retrying forever (NFS root)...
> > eth1: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX.
> > eth1: Waiting for the link to be up...
> > eth1: status: link up, 100 Mbps Full Duplex, auto-negotiation complete.
> > e100: eth0 NIC Link is Up 100 Mbps Full duplex
>
> Maybe your board configuration of the kernel is not quite correct
> and/or some interrupt lines are wongly addressed.
No, you are wrong here. It seems the kernel is working perfectly fine.
> > Sending DHCP requests ...... timed out!
> > Please tell me how can I handle it! Thanks in advance!
>
> $ find . -name '*.c' | xargs grep Sending\ DHCP
> And start debugging/instrumenting from there.
Always try simple things first! Is there a DHCP server running to
answer the DHCP requests from the target? Did you run a network
sniffer and actually see the DHCP reply packets on the wire?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
No one wants war.
-- Kirk, "Errand of Mercy", stardate 3201.7
next prev parent reply other threads:[~2004-11-24 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 7:25 [U-Boot-Users] question on drive zhonglei
2004-11-24 9:14 ` Marc Leeman
2004-11-24 10:30 ` Wolfgang Denk [this message]
2004-11-24 10:47 ` Marc Leeman
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=20041124103019.B0D95C1430@atlas.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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