> Perhaps someone can shed some light on this. I'm using a version of
> u-boot from Dec from CVS which calls itself 1.0.1 and Linux 2.4.21
> (with patches to allow it to compile) on an AT91RM9200DK board.
>
> Most people won't notice this, because they'll be booting from tftp.
> However, in this instance, I have a ramdisk and kernel in flash. If
> u-boot doesn't prod the ethernet (e.g. by tftping a random file), then
> it turns out that the ethernet doesn't work from within Linux. I'm
> afraid I'm not able to shed any further light on why it doesn't, but
> perhaps someone else can.
>
Did you set the "ethaddr" in u-boot properly? If you managed to ftp, I guess it
should work.
I notice that if I use the U-boot/Linux 2.4.19 on the September CD, then
It does not care if tftp is used or not.
I will get "00:00:00:00:00:00" when there is no cable or faulty cable is
attached.
I know of one other which has the same problem, but I have not been able to
reproduce.
>
Best Regards
Ulf Samuelsson ulf@xxxxxxxxx
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavallerivägen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
-------------------------------------------------------------------
Subscription options: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
FAQ/Etiquette: http://www.arm.linux.org.uk/armlinux/mailinglists.php
|
