[tulip] Conexant LANfinity

Eberhard Moenkeberg emoenke@gwdg.de
Fri, 29 Dec 2000 15:56:56 +0100 (MET)


I have a notebook Compaq Presario 1700 which has a builtin
miniPCI modem/LAN interface.

The LAN chip has PCI ID 14F1:1803. lspci is telling:
00:09.0 Ethernet controller: CONEXANT: Unknown device 1803 (rev 08)

I grepped for these strings through my mirror of ftp.scyld.com,
and sic! Donald covers that chip in network/test/tulip.c
(but not in tulip-diag yet).

So I put this 0.92p tulip driver into my 2.2.18 kernel source
(let it replace drivers/net/tulip.c), put
into drivers/net too and patched the Makefile there:

--- linux/drivers/net/Makefile.~1~  Thu Dec 28 11:06:43 2000
+++ linux/drivers/net/Makefile  Fri Dec 29 12:27:42 2000
@@ -782,9 +782,11 @@
 ifeq ($(CONFIG_DEC_ELCP),y)
+L_OBJS += pci-scan.o
 L_OBJS += tulip.o
   ifeq ($(CONFIG_DEC_ELCP),m)
+  M_OBJS += pci-scan.o
   M_OBJS += tulip.o

and compiled a kernel 2.2.18 with built-in tulip 0.92p support.

The next boot messages told:

  The PCI BIOS has not enabled the device at 0/72!
   Updating PCI command 0003->0007.
eth0: Conexant LANfinity rev 8 at 0x1400, EEPROM not present,
   00:4C:69:6E:75:79, IRQ 9.
eth0:  MII transceiver #1 config 1000 status 782d advertising 01e1.
eth0:  MII transceiver #0 config 1000 status 782d advertising 01e1.
tulip.c:v0.92p 11/28/2000  Written by Donald Becker <becker@scyld.com>

eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.

and things looked very good, but the chip does not work yet:

eth0      Link encap:Ethernet  HWaddr 00:4C:69:6E:75:79  
          inet addr:  Bcast:  Mask:
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:806 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:9 Base address:0x1400 

tulip-diag says "Unable to find a recognized card in proc/pci", and
with a little help I get:

ag4-05:0 15:49:14 /usr/src/tulip/diag # ./tulip-diag -p 0x1400
tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
Assuming a Digital Tulip series adapter at 0x1400.
 Port selection is 10mpbs-serial, full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Processing setup information'.
  The transmit threshold is 72.
 Use '-a' or '-aa' to show device registers,
     '-e' to show EEPROM contents, -ee for parsed contents,
  or '-m' or '-mm' to show MII management registers.
ag4-05:0 15:49:33 /usr/src/tulip/diag # 

"10mpbs-serial" is wrong (not only the bp switching ;-).
The connection is full-duplex 100baseTX.
Neither RX nor TY is working...

Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)