Skip to contentSkip to conversation

question on drive

U-Boot-Users zhonglei 3 participants 4 messages Nov 24, 2004

lore
Share & tools
lore

zhonglei

author
#0 lore raw

hi
Sorry for bothering you! But would you please give me a hand.When I insert a Intel Pro/100s server Adapter into the PCI slot on Lite5200(motorola MPC5200 development kit) and start the kernel,the kernel run into a dead lock. The reports are as follows:
.
.
.
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
Sending DHCP requests ...... timed out!
Please tell me how can I handle it! Thanks in advance!
Best Regards
zhonglei

#1 lore raw

I don't think this has to do with u-boot :) I think you should send this to the correct mailing list.

Quoted 5 lines

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.

Quoted 2 lines

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.
Signature · 2 lines
ash nazg durbatul?k, ash nazg gimbatul,
ash nazg thrakatul?k agh burzum-ishi krimpatul
#2 lore raw
Quoted 2 lines · In message <[email protected]> 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.

Quoted 8 lines
Quoted 5 lines

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.

Quoted 5 lines
Quoted 2 lines

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

Signature · 4 lines
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
#3 lore raw
Quoted 3 lines

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?

Hm, I assumed this was already checked since it the easiest to do :) I know, 'assuming' is bad...

This would be (on the server)

# tail -f /var/log/syslog
to check the DCHP packages arriving at the server and the replies being sent.
Signature · 2 lines
ash nazg durbatul?k, ash nazg gimbatul,
ash nazg thrakatul?k agh burzum-ishi krimpatul