From: Marc Leeman <marc.leeman@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] question on drive
Date: Wed, 24 Nov 2004 10:14:33 +0100 [thread overview]
Message-ID: <1f729c4804112401141cd5deb7@mail.gmail.com> (raw)
In-Reply-To: <200411241525.AA37617880@RCS-9000.COM>
I don't think this has to do with u-boot :) I think you should send
this to the correct mailing list.
> 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.
> 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.
--
ash nazg durbatul?k, ash nazg gimbatul,
ash nazg thrakatul?k agh burzum-ishi krimpatul
next prev parent reply other threads:[~2004-11-24 9:14 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 [this message]
2004-11-24 10:30 ` Wolfgang Denk
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=1f729c4804112401141cd5deb7@mail.gmail.com \
--to=marc.leeman@gmail.com \
--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