Intel EtherExpressPro 100 32bit Cardbus

[Donald Becker]

On Thu, 6 May 1999, Nick Birkett wrote:

> Subject: Intel EtherExpressPro 100 32bit Cardbus
> 
> I have been trying to use an Intel EtherExpress Pro 100 32 Bit Cardbus ethercard
> under Kernel 2.2.5 (RedHat 6.0).

This was discussed two or three weeks ago.

> tulip.c:v0.91 4/14/99 becker@cesdis.gsfc.nasa.gov
> eth0: Digital DS21143 Tulip rev 48 at 0x400, EEPROM not present, 00:4C:69:6E:75:79, IRQ 3.

The problem is the "EEPROM not present" message.
There is an EEPROM on the board, but it's not programmed with the station
address or a media table.

Note that your temporary station address is ASCII ;->.

I can provide a substitute media table (actually, Intel should do this), but
I need someone to experiment with their card first.

> However when trying to send any packets an icmp destination unreachable error
> is obtained.

This is an unrelated routing problem.  Add a default (aka gateway) route.

> Here is the output of tulip-diag :
> 
> [root@ibm0 test]# ./tulip-diag -ef
> tulip-diag.c:v1.10 4/12/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> Index #1: Found a Digital DS21143 Tulip adapter at 0x400.
>  Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
>  Transmit started, Receive started, half-duplex.
>   The Rx process state is 'Waiting for packets'.
>   The Tx process state is 'Idle'.
>   The transmit threshold is 128.
>  A simplifed EEPROM data table was found.
>  The EEPROM does not contain transceiver control information.  

Use "-ee" to see your full EEPROM contents.

> [root@ibm0 test]# ./tulip-diag -af
> tulip-diag.c:v1.10 4/12/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> Index #1: Found a Digital DS21143 Tulip adapter at 0x400.
> Digital DS21143 Tulip chip registers at 0x400:
>   ffa08000 ffffffff ffffffff 00a53810 00a53a10 f0660000 b3862002 fbfffbff
>   e0000000 ffffcbf8 ffffffff fffe0000 000000c5 ffff0001 fffbff7f 8ff10008
>  Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
>  Transmit started, Receive started, half-duplex.
>   The Rx process state is 'Waiting for packets'.
>   The Tx process state is 'Idle'.
>   The transmit threshold is 128.    

Hmmm, the status actually looks good -- you probably have 100baseTx link
beat.
Here is something to try if you don't:
   tulip-diag -p 0x400 -t 4 -G 0x08af0000
   tulip-diag -p 0x400 -t 4 -G 0x00a50000


Donald Becker					  becker@cesdis.gsfc.nasa.gov
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center,  Greenbelt, MD.  20771
301-286-0882	     http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html