[tulip] problems with accton en2242

PAZINCZAR Peter pai@erise.hu
Tue Jan 22 10:45:02 2002


Hi!

I have a problem with the card called Accton EN2242 MiniPCI (recognized as
ADMtek comet (rev 17) by tulip).
I'm using the kernel v. 2.4.17 (debian/linux). The notebook is a Gericom
stuff. First of all, on boot time the card got an IRQ 0. I`ve solved this
problem setting the IRQ by setpci -s 00:05.0 interrupt_line=0a (03 also
tried), `cos there were no possibility to set it in the PCI BIOS. After
reboot it worked with the new IRQ. The kernels module passed, eth0 seemed
to work fine. After this came some problems.

The output of tulip-diag is:
p-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html Assuming a Digital Tulip series
adapter at 0x1c00.
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
 Transmit stopped, Receive stopped, half-duplex.
 The Rx process state is 'Waiting for packets'.
 The Tx process state is 'Stopped'.
 The transmit threshold is 128.
Interrupt sources are pending!  CSR5 is fc07c017.
 Tx done indication.
 Tx complete indication.
 Tx out of buffers indication.
 Link passed indication.
 Early Rx indication. EEPROM 256 words, 8 address bits.
 A simplifed EEPROM data table was found.
 The EEPROM does not contain transceiver control information.
 EEPROM contents (256 words):
0x00:  0985 0002 0000 0000 9000 1d96 9ff5 0000
0x08:  0000 0400 0001 0000 0000 0000 0000 0100
0x10:  1216 1113 2242 1113 ffff 0000 0000 a04c
0x18:  0000 0000 0000 0000 0000 0000 0000 0000
0x20:  0000 0000 0000 0000 0000 0000 0000 0000
0x28:  0000 0000 0000 0000 0000 0000 0000 0000
0x30:  0000 0000 0000 0000 0000 0000 0000 0000
0x38:  0000 0000 0000 0000 0000 0000 0000 cf0a
.
.
.
the rest are all zeros.

 ID block CRC 0x21 (vs. 00).
  Full contents CRC 0xcf0a (read as 0xcf0a).

If i send a packet over eth0 (ifconfig output seems to be normal), i get
the following:
Jan 21 21:54:19 xxx kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jan 21 21:54:19 xxx kernel: eth0: Transmit timed out, status fc67c017,
CSR12 00000000, resetting...

Sure, because the eeprom contains no controll information. As i read on
the tulip website, there are some other ways to define them in the module
source. But, i don`t know how to get the values to set, and how to set
them? ( :) ). Or is there any other way by writing the eeprom whith some
controll information (as i did with IRQ before)?
Could sy help me in this?

Thx,

{pai}