[eepro100] sgi 320 visws and eepro100

[Jim Edwards]

Hi,

I've been fighting this battle on my own for a couple of weeks now and
it's time to ask for help.  I have an sgi320 visual workstation platform
- it is an unusual machine in that it runs a pentium chip but most of
the other components are more typical of sgi architectures.  I am
running linux kernel 2.2.10 with patchs provided by sgi and a few bug
fixes that came in kernel patchs up to 2.2.17.  This machine is not
supported in newer kernels because sgi pulled their support and no-one
in the kernel development community has one to work with.   It's also a
2 proc SMP.

With the original eepro100 driver (from kernel 2.2.17) under heavy usage
(such as serving X or running multiple ftps) I get the following
message:


> kernel: eth0: card reports no resources.
>
With the latest driver from  http://www.scyld.com/network/eepro100.html
loaded as a module I get

> May 16 11:12:37 ndpndes kernel: eepro100.c:v1.13 1/9/2001 Donald Becker
> May 16 11:12:37 ndpndes kernel:   http://www.scyld.com/network/eepro100.html
> May 16 11:12:37 ndpndes kernel: eth0: Invalid EEPROM checksum 0x423c, check settings before activating this device!
> May 16 11:12:37 ndpndes kernel: eth0: OEM i82557/i82558 10/100 Ethernet at 0xe9834000, FD:C7:3F:C8:7B:05, IRQ 19.
> May 16 11:12:37 ndpndes kernel:   Receiver lock-up bug exists -- enabling work-around.
> May 16 11:12:37 ndpndes kernel:   Board assembly 96f6fe-099, Physical connectors present: RJ45 MII
> May 16 11:12:37 ndpndes kernel:   Primary interface chip i82553-A/B PHY #16.
> May 16 11:12:37 ndpndes kernel:     Secondary interface chip i82553-A/B.
> May 16 11:12:37 ndpndes kernel: Self test failed, status ffffffff:
> May 16 11:12:37 ndpndes kernel:  Failure to initialize the i82557.
> May 16 11:12:37 ndpndes kernel:  Verify that the card is a bus-master capable slot.
> May 16 11:12:37 ndpndes kernel:   Receiver lock-up workaround activated.
>
>
But the eepro100-diag program run with -ee suggests that the eeprom
checksum is okay:


> ./eepro100-diag -ee
> eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
>  http://www.scyld.com/diag/index.html
> Index #1: Found a Intel i82557 (or i82558) EtherExpressPro100B adapter at 0xa100.
> EEPROM contents, size 64x16:
>     00: 0008 1369 693c 0000 0000 0101 4401 0000
>   0x08: 1234 5678 0000 0004 8086 0000 0000 0000
>       ...
>   0x38: 0000 0000 0000 0000 0000 0000 0000 0fd5
>  The EEPROM checksum is correct.
> Intel EtherExpress Pro 10/100 EEPROM contents:
>   Station address 08:00:69:13:3C:69.
>   Receiver lock-up bug exists. (The driver work-around *is* implemented.)
>   Board assembly 123456-120, Physical connectors present: RJ45
>   Primary interface chip DP83840 PHY #1.
>   Transceiver-specific setup is required for the DP83840 transceiver.
>
Finally one more piece of info:

> ./eepro100-diag -aa
> eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
>  http://www.scyld.com/diag/index.html
> Index #1: Found a Intel i82557 (or i82558) EtherExpressPro100B adapter at 0xa100.
> i82557 chip registers at 0xa100:
>   00000000 00000000 00000000 00080002 1821782d 00000000
>   No interrupt sources are pending.
>    The transmit unit state is 'Idle'.
>    The receive unit state is 'Idle'.
>   This status is unusual for an activated interface.
>

Can anyone help me figure this out?

thanks,
Jim