Re: [Etherboot-users] epic100 problem

[Ken Y. <ke...@nl...>]

>	Loading ROM image...
>	ROM segment 0x8000 length 0x4000 reloc 0x9800
>	Boot from (N)etwork or from (L)ocal
>(we choose N)
>	Etherboot/32 version 4.6.4 (GPL) for [EPIC100]
>	Found SMC EtherPpowerII at 0xF800, ROM addres 0x000000000
>	Probing....[EPIC100] I/O F800 00:E0:29:1D:3D:97
>	Searching for server (BOOTP)...
>(all fine 'till now)
>	OOPS, Something wrong with transmitter. status=2003
>
>I've tried this in two seperate PCs with the same hardware characteristics
>(including the same network card). On the second one it gave an address of
>FF:FF:FF:FF:FF:FF in the ``Probing...'' line and a status=8000 in the last
>line
>
>Is there any hardware problem, an incompatibility, am I doing something
>wrong?

One thing I can suggest is it's some kind of timing problem, perhaps the
driver isn't waiting long enough for some operations.  Another thing to
check is the PCI config in the BIOS, it's possible that the PCI bus
latency is set too low on your motherboard. There is code in eepro100.c
to adjust this to 32 clocks so it seems to matter for some NICs. I don't
have this NIC so could you also please contact the author of the driver.
Other than that, you'd could try to debug this yourself, armed with a
datasheet for the Ethernet controller chip. Maybe also look at the Linux
driver to see if there are any places where timing is important.