autonegotiate problems on a SMC Etherpower II 9432BTX Combo

[root]

Hi Epic developers!

Our institute uses the SMC 9432 BTX network adapter with 10base2 and
10/100baseT
connectors in the following hardware environment:

ASUS P2B-S Motherboard
Pentium II Processor 350,400,450 MHz 
64MB SDRAM (PC-100) for 100MHz boards 
Matrox Productiva G100 AGP graphics adapter with 8MB 
Soundblaster PCI 128 sound adapter 
IBM DDRS 4.5GB U2W-SCSI harddisk 
Toshiba XM6401B 32x CDROM, SCSI 

WinNT4.0 runs fine with 10base2,10BaseT and 100BaseTx, the network
components
(ATI MR 128FT Micro repeater (10baseT-HD) or  ATI MS425FSC micro switch(
10/100baseT-FD))
and the cabeling should be fine.

SuSE-Linux 6.1 (Kernel 2.2.5) epic100 driver 1.06 has problems using the
twisted pair
port. After the upgrade to epic100 v.1.07, setting options=1 (BNC)
works  to get a 
connection over the 10base2 port, but options=3,4,5
(100baseTX,10baseT-FD,100baseTx-FD)
work sometimes but fail most of the time.

Has anyone gotten the  above card up and running reliably in 10 or
100baseT mode (half duplex and full duplex) ?

To me it looks like a problem in the half/full-duplex negotiation.

Thanks in advance for any hint

Armin

Additional information:

1. kernel output of a failed tp session:

Apr 22 16:08:04 multix4 kernel: eth0: SMSC EPIC/100 83c170 at 0xb400,
IRQ 10, 00:e0:29:1b:71:65.
Apr 22 16:08:04 multix4 kernel: eth0: EEPROM contents
Apr 22 16:08:04 multix4 kernel:  e000 1b29 6571 0600 001d 1c08 10b8 a015
0000 0000 0000 0000 0000 0000 0000 0000
Apr 22 16:08:04 multix4 kernel:  0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
Apr 22 16:08:04 multix4 kernel:  0010 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 4d53 3943 3334 4232
Apr 22 16:08:04 multix4 kernel:  5854 2020 0000 0000 00c0 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
Apr 22 16:08:04 multix4 kernel: eth0: MII transceiver #3 control 3000
status 7809.
Apr 22 16:08:04 multix4 kernel: eth0:  Autonegotiation advertising 01e1
link partner 0001.
Apr 22 16:08:04 multix4 kernel: eth0: Setting half-duplex based on MII
xcvr 3 register read of 0001.
Apr 22 16:08:04 multix4 kernel: eth0: epic_open() ioaddr b400 IRQ 10
status 0512 half-duplex.


2. Output of epic-diag (the 16 collisions result from a failed ping
attempt)

Found SMC83C170 EPIC/100 card #1 at 0xb400.
The EPIC/100 chip appears to be active, so some registers will not be
read.
To see all register values use the '-f' flag.
EPIC chip registers at 0xb400
 0x000: 00000008 00248040 000013bf 00000512 0000001d 00000065 00000000
00000000
 0x020: 00000000 00000000 00000000 00000000 00000650 00000001 00000016
00003c60
 0x040: 0000e000 00001b29 00006571 00000600 0000ffff 0000ffff 0000ffff
0000ffff
 0x060: 0000000c ******** ******** ******** 00003c79 00003000 ********
********
 0x080: ******** 0007f820 ******** ******** ******** ******** ********
********
 0x0A0: ******** ffff087f ******** ******** ffff0bff ******** ********
********
 0x0C0: ******** 0007fa80 ******** ******** ******** ******** ********
0007f900
 0x0E0: ******** ******** ******** ******** ******** ******** ********
********
  Interrupt sources are pending.
   Tx chain done indication.
   Rx status valid indication.
  Transmitter: slot time 512 bits, half-duplex mode.
   Last transmit FAILED!!, 16 collisions.

3. Output of mii-diag

Basic registers of MII PHY #3:  0100 780d 0181 4401 01e1 0001 0000 ffff.
 Basic mode control register 0x0100: Auto-negotiation disabled, with
 speed fixed at 10 mbps, full-duplex.
 You have link beat, and everything is working OK.
 Your link partner is strange, status 0001.
 | To unsubscribe, send mail to Majordomo@cesdis.gsfc.nasa.gov, and within the
 |  body of the mail, include only the text:
 |   unsubscribe this-list-name youraddress@wherever.org
 | You will be unsubscribed as speedily as possible.