[tulip] LNE100TX... not solved

[Tony Likhite]

The driver in LinkSys' 4.2 kit (the latest available) is the standard
4/17/00 0.92 version of tulip.c.  It doesn't solve the problem for me,
and I still get the card reporting:

tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xa800.
 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.
 The Comet MAC registers are 0d782000 ffff5fd0 filter 8000000000000000.

(back to the 0.92p driver)

Even when I try to force the card into a mode other then 100baseTx
(half-duplex) with e.g. 'options=10' for MII 10baseT-FD, tulip-diag
reports 100baseTx half duplex.  The syslog messages (debug=4) say:

...kernel: tulip.c:v0.92p 11/28/2000  Written by Donald Becker <becker@scyld.com>
...kernel:   http://www.scyld.com/network/tulip.html
...kernel: eth0: ADMtek Centaur-P rev 17 at 0xc8a06000, 00:20:78:0D:D0:5F, IRQ 10.
...kernel: eth0:  MII transceiver #1 config 1100 status 7869 advertising 0101.
...kernel: eth0:  Advertising 0040 on PHY 1, previously advertising 0101.
...kernel: eth0: tulip_open() irq 10.
...kernel: eth0: No media description table, assuming MII 10baseT-FDX transceiver, CSR1200.
...kernel: eth0: Done tulip_open(), CSR0 fff98000, CSR5 fc124010 CSR6 ff9f2117.
...kernel: eth0: interrupt  csr5=0xfc674014 new csr5=0xfc664010.
...kernel: eth0: Added filter for 01:00:5e:00:00:01 bit 31.
...kernel: eth0: Added filter for 01:00:5e:00:00:01 bit 31.
...kernel: eth0: Comet link status 786d partner capability 41e1.

Please excuse the formatting.  I can ifconfig the interface and it
works (briefly and badly) at 100Mbps (?).

Other than not buying LinkSys again, is there anything else I should try?

Erik Steffl wrote:
>   does it work OK in 100Mbs full duplex mode?
> 
> 	erik
> 
> > "Mr V (Note my email change!!!)" wrote:
> > 
> > Hopefully, this helps everyone with this card.  I actually got some
> > assistance from Linksys on this one:
> > 
> > The drivers I found on the Linksys site work. It's just a matter of
> > getting it all together.
> > 
> > 1. Copy their netdrivers.tgz file to, say, /netdrivers and then
> > decompress the file
> > 
> > using 'tar xzvf netdrivers.tgz'
> > 
> > 2. Run a compile on them by typing 'make' in the /netdrivers directory
> > 
> > 3. Now, after all of the error messages (and there were TONS on my
> > machine), run 'depmod -a'
> > 
> > 4. Okay, run 'insmod pci-scan.o' followed by 'insmod tulip.' Assuming
> > you get no error output, you're good to go. ****BE SURE TO INSMOD
> > PCI-SCAN.O BEFORE TULIP.O
> > 
> > 5. If the modules loaded (and you got no errors) you should be able to
> > run 'ifconfig' and see an entry for 'eth0; in addition to 'lo'. Run
> > the ifconfig even if you did get errors just to be safe.
> > 
> > 6. If your 'ifconfig' shows an 'eth0' is loaded, copy your new
> > pci-scan.o and tulip.o modules to EVERY directory on your system that
> > has them in it now. (Run a 'locate tulip.o' and it will tell you where
> > the files are located.) It will probably be
> > '/lib/modules/2.2.xx-xx/net' AND '/lib/modules/2.2.xx-xxBOOT/net'
> > 
> > 7. Do a 'shutdown -r now' and see if it recognizes the card - it
> > should.
> > 
> > 8. Good luck <G>
> 
> 
> 
> _______________________________________________
> tulip mailing list
> tulip@scyld.com
> http://www.scyld.com/mailman/listinfo/tulip

-- 
Tony Likhite
Vicinity Corp.
(603)442-1746
This Is What I Think I Know®