[tulip] admtek an983b multiport not supported?

Fri Aug 27 13:10:10 PDT 2004

Hello all,
I've been trying to get this card working with the tulip driver on a rh9
(kernel 2.4.20-6) machine.  We have one of these that works in another
identical machine, but (without being able to look at the board itself)
appears to use a different chip.

(slight digression)
The working model looks to have separate eeproms for each port and uses a
different chip; has this:
desc: "DEC|DECchip 21140 [FasterNet]"
vendorId: 1011
deviceId: 0009
subVendorId: 0000
subDeviceId: 0000
The tulip driver shipped with rh9 recognized these as separate interfaces
(separate interrupts for each) and 'just worked'.

The one I have in hand uses an ADMTek AN983B.  I've compiled and loaded the
newest tulip driver (tulip.c:v0.98 1/8/2004) and have run tulip-diag on this
as well.  This is running on a Dell poweredge 400sc with the latest BIOS
(A06).  There is a large heatsink on the card, which might mean the board
has an on-board processor?  (If so, it is unsupported...).  I guess it is
possible these two boards are that much different. ??  This is a cheap no
namer.

I notice from http://www.scyld.com/tulip_devel.html
Current Driver Issues:
"Detecting when the interrupt lines are actually mapped to the reported
IRQs, instead of all being on one IRQ. Almost all x86 motherboard BIOSes
report incorrect IRQ lines for all but the first port on multiport boards.
The best I can come up with storing an alternate possible IRQ value in
struct tulip_private. If the timer code detects that the chip has posted an
interrupt that we haven't gotten, release the primary IRQ and request the
new one. Ugly, especially if we fail requesting the new one. "

This seems like what is happening here. ??

If not,
The stock rh9 driver recognized the card as
desc: "Linksys|Network Everywhere Fast Ethernet 10/100 model NC100"
vendorId: 1317
deviceId: 0985
subVendorId: 1113
subDeviceId: 1216

Manually loading the newest tulip.o with debug=31 produces
Aug 27 11:40:59 kernel: tulip.c:v0.98 1/8/2004  Written by Donald Becker <be
cker at scyld.com>
Aug 27 11:40:59 kernel:   http://www.scyld.com/network/tulip.html
Aug 27 11:40:59 kernel: eth1: ADMtek Centaur-P rev 17 at 0xe896bc00,
00:02:2A:CB:46:62, IRQ 10.
Aug 27 11:40:59 kernel: eth1:  MII transceiver #1 config 1100 status 786d
advertising 05e1.
Aug 27 11:40:59 kernel: eth1:  MII transceiver #2 config 1100 status 786d
advertising 05e1.
Aug 27 11:40:59 kernel: eth1:  MII transceiver #3 config 1100 status 786d
advertising 05e1.
Aug 27 11:40:59 kernel: eth1:  MII transceiver #4 config 1100 status 786d
advertising 05e1.

and /proc/pci shows:
(The Intel is the onboard controller)
<snip>
  Bus  2, device   2, function  0:
    Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100
model NC100 (rev 17).
      IRQ 10.
      Master Capable.  Latency=64.  Min Gnt=64.Max Lat=128.
      I/O at 0xde00 [0xdeff].
      Non-prefetchable 32 bit memory at 0xfe9dec00 [0xfe9defff].
  Bus  2, device  12, function  0:
    Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller
(rev 2).
      IRQ 9.
      Master Capable.  Latency=64.  Min Gnt=255.
      Non-prefetchable 32 bit memory at 0xfe9e0000 [0xfe9fffff].
      I/O at 0xdcc0 [0xdcff].
<snip>

Here is output from tulip-diag -aem
tulip-diag.c:v2.18 11/12/2003 Donald Becker (becker at scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xde00.
ADMtek AL985 Centaur-P chip registers at 0xde00:
 0x00: fff98000 ffffffff ffffffff 20af5000 20af5200 fc06c812 ff970111
fffe5410
 0x40: fffe0000 fff597f8 00000000 fffe0000 00000000 00000200 00000000
00000008
 Extended registers:
 0x80: 0006c812 03fe5410 a0cc0005 0000ff00 00000000 20af5200 20af5010
ffe0f000
 0xa0: f0000000 cb2a0200 ffff6246 00000000 00000000 00000000 00000000
00000000
 0xc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
 0xe0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
f0000027
 Comet duplex is reported in the MII status registers.
 Transmit stopped, Receive stopped.
  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 fc06c812.
   Tx complete indication.
   Link passed indication.
   Timer expired indication.
   Early Rx indication.
  Comet MAC address registers cb2a0200 ffff6246
  Comet multicast filter 0000000000000000.
EEPROM 64 words, 6 address bits.
  Ethernet MAC Station Address 00:02:2a:cb:46:62.
  Default connection type 'Autosense'.
  PCI IDs Vendor 1317 Device 0985  Subsystem 1113 1216
  PCI min_grant 64 max_latency 128.
  CSR18 power-up setting 0xa0cc****.
 MII PHY found at address 1, status 0x786d.
 MII PHY found at address 2, status 0x786d.
 MII PHY found at address 3, status 0x786d.
 MII PHY found at address 4, status 0x786d.
 MII PHY #1 transceiver registers:
   1100 786d 001d 2411 05e1 45e1 0007 2001
   0000 0000 0000 0000 0000 0000 0000 0000
   1001 0000 14a1 2219 0000 010f 7490 0000
   868f 7317 2f60 1428 9912 0514 0230 0000.
 MII PHY #2 transceiver registers:
   1100 786d 001d 2411 05e1 45e1 0007 2001
   0000 0000 0000 0000 0000 0000 0000 0000
   1001 0000 00a2 2219 0000 000f 7490 0000
   868f 7218 3060 1428 8912 0404 0230 0000.
 MII PHY #3 transceiver registers:
   1100 786d 001d 2411 05e1 45e1 0007 2001
   0000 0000 0000 0000 0000 0000 0000 0000
   1001 0000 00a0 2218 0000 010f 7490 0000
   868f 7317 2f60 1428 9912 0404 0230 0000.
 MII PHY #4 transceiver registers:
   1100 786d 001d 2411 05e1 45e1 0007 2001
   0000 0000 0000 0000 0000 0000 0000 0000
   1001 0000 009f 2219 0000 017f 7490 0000
   868f 7317 2f61 1427 9913 0405 0230 0000.

I've included gobs of output as I'm not certain as to what is most relevant.
I will provide whatever else might be needed.

Will this card work?  What other troubleshooting steps can I take?  Is this
an issue with the specific kernel, or BIOS or ???  I've had experience with
C, but not much at the driver level and I'm not familiar with the sequence
of events that take place, but am very willing to learn and tinker with the
source (with a little guidance as to starting).  With all that said, I
suspect that the driver will handle this card and I'm just overlooking some
configuration or the like and there isn't any (or little) source level
modification needed.  Any help you all can provide is appreciated.

Thanks,
Thomas