Problems with LNE100TX
Bryan Stillwell
arcane@verinet.com
Thu Sep 16 01:30:14 1999
It appears that the LNE100TX came with at least two different chips on
them. Most likely yours is the older one using the original PNIC chip
from lite-on, but mine uses the newer PNIC-II chip which would explain my
problems. Just to be sure, do you have the wake-on-lan option on your
card?
Thanks for helping,
Bryan
On Wed, 15 Sep 1999, Gerard Saraber wrote:
> Hi,
> I have an LNE100TX from linksys as well, and I have no problems
> whatsoever as long as i use
> a later version of the driver than the one included in the linux kernel,
> the one I currently use is
> v91g - also note that I use the "tulip" driver , tulip.c , not the de4x5
> driver.
> Let me know if you need anything else. btw. the driver I use with kernel
> 2.3.15 can be found on
> ftp://saraber.dhs.org/pub/tulip/
>
> Regards,
> --====================================================================--
> Gerard Saraber | http://saraber.dhs.org
> work: gsaraber@unlimitedsolutions.com | If you don't like Linux you
> home: gerard@saraber.dhs.org | didn't configure it
> right.
>
> > -----Original Message-----
> > From: Bryan Stillwell [SMTP:arcane@verinet.com]
> > Sent: Wednesday, September 15, 1999 11:11
> > To: linux-tulip@cesdis1.gsfc.nasa.gov
> > Subject: Problems with LNE100TX
> >
> > I've been messing around with trying to get my LinkSys LNE100TX to
> > work
> > under linux for some time now, but with not much success. I've tried
> > it
> > in two different computers with different distributions of linux
> > (Redhat
> > and Mandrake), multiple kernels, and different versions of the tulip.c
> > and
> > de4x5.c source code.
> >
> > When I compile the tulip driver as a module in kernel 2.2.12, I get a
> > message about the device or resource is busy... Which I believe means
> > that it couldn't find the card.
> >
> > So the next thing I did was try the 2.3.15 kernel, but same results.
> > I
> > figured that it would since the source didn't change between the two
> > versions as far as I can tell...
> >
> >
> > Then I tried updating the tulip.c file to v0.91j++ dated 9/8/99 off
> > the
> > ftp site: ftp://cesdis.gsfc.nasa.gov/pub/linux/drivers/kern-2.3/
> >
> > I do get a little farther after doing that, but now I get this when I
> > try
> > a 'insmod tulip.o':
> >
> > tulip.o: unresolved symbol pci_drv_unregister
> > tulip.o: unresolved symbol pci_drv_register
> >
> >
> > Doing a 'depmod -a' gives:
> > /lib/modules/2.3.15/net/tulip.o: unresolved symbol(s)
> >
> > Which also should be expected.
> >
> >
> > But now I don't know what else there is to do, but expose the problems
> > I've been having. I have two of these LNE100TX cards that I bought at
> > Best Buy for $30 each, so I'm hoping I can get them to work since
> > they're
> > such a good deal. (They were down to $20 each the last time I went
> > into
> > Best Buy)
> >
> > I did go ahead and install the tulip-diag program and it seems to find
> > the
> > card just fine. Here is the output from it:
> >
> > # ./tulip-diag
> > tulip-diag.c:v1.12 7/31/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> > Index #1: Found a Lite-On PNIC-II adapter at 0xf400.
> > Port selection is 10mpbs-serial, half-duplex.
> > Transmit stopped, Receive stopped, half-duplex.
> > The Rx process state is 'Stopped'.
> > The Tx process state is 'Stopped'.
> > The transmit threshold is 72.
> > The NWay status register is 000020ce.
> > Internal autonegotiation state is 'Ability detect'.
> > Use '-a' to show device registers,
> > '-e' to show EEPROM contents,
> > or '-m' to show MII management registers.
> >
> >
> > # ./tulip-diag -a
> > tulip-diag.c:v1.12 7/31/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> > Index #1: Found a Lite-On PNIC-II adapter at 0xf400.
> > Lite-On PNIC-II chip registers at 0xf400:
> > fe580000 ffffffff ffffffff 7cf5bff2 f452b9ed e4000000 e1000000
> > e7fe0000
> > fffe0000 00fecf08 fffe0466 fffe0000 000020ce ffff0000 ffffffff
> > fff00000
> > 03300000 03300000 03300000 f00ffff0 00004200 00001140 33ccf630
> > a000a000
> > 33ccf630 00000000 00000000 00000000 00000000 00000000 00000000
> > 00000000
> > Port selection is 10mpbs-serial, half-duplex.
> > Transmit stopped, Receive stopped, half-duplex.
> > The Rx process state is 'Stopped'.
> > The Tx process state is 'Stopped'.
> > The transmit threshold is 72.
> > The NWay status register is 000020ce.
> > Internal autonegotiation state is 'Ability detect'.
> >
> >
> > # ./tulip-diag -e
> > tulip-diag.c:v1.12 7/31/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> > Index #1: Found a Lite-On PNIC-II adapter at 0xf400.
> > Port selection is 10mpbs-serial, half-duplex.
> > Transmit stopped, Receive stopped, half-duplex.
> > The Rx process state is 'Stopped'.
> > The Tx process state is 'Stopped'.
> > The transmit threshold is 72.
> > The NWay status register is 000020ce.
> > EEPROM size is 6.
> > Ethernet MAC Station Address 00:a0:cc:33:30:f6.
> > Wake-On-Lan ID bytes a0:00:33:cc:f6:30.
> > PCI Subsystem IDs Vendor 11ad Device 01c0
> > Internal autonegotiation state is 'Ability detect'.
> >
> >
> > # ./tulip-diag -m
> > tulip-diag.c:v1.12 7/31/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> > Index #1: Found a Lite-On PNIC-II adapter at 0xf400.
> > Port selection is 10mpbs-serial, half-duplex.
> > Transmit stopped, Receive stopped, half-duplex.
> > The Rx process state is 'Stopped'.
> > The Tx process state is 'Stopped'.
> > The transmit threshold is 72.
> > The NWay status register is 000020ce.
> > No MII transceivers found!
> > Internal autonegotiation state is 'Ability detect'.
> >
> >
> > That's all the information I could think of that would help someone
> > help
> > me find my problem, but if you need any more feel free to ask.
> >
> > Thank you very much for any help you can provide,
> >
> > Bryan
> >
>