[tulip] LNE100TX rev. 5.0

Jacob Schroeder j-schroeder@myrealbox.com
Wed Dec 12 23:40:00 2001


Pardon my questions if I seem like a newbie, I'm still trying to learn. I had the network setup the same way and never had a problem with an older linksys ISA that was ne2000 compatible, so why would I have so many collisions with the new card? This computer is also the only one on the network to have this many collisions in such a short amount of time. 

On a network going through a properly sized hub shouldn't network errors be few? And Full Duplex would cause more collisions? I've got 5 sometimes 6 computers on an 8 port hub, with the only traffice being sharing a dialup and a fileserver. I can get roughly 6,000 errors just doing a 4 minute ssh connection with another computer on the lan, and those two computers being the only traffic going through the hub

Thanks,
Jacob

On Wed, 12 Dec 2001 15:14:14 -0800 (PST)
"..." <goemon@anime.net> wrote:

> collisions are a normal behaviour through a hub. if you were running full 
> duplex you would have 0 collisions. so its working properly.
> 
> On Wed, 12 Dec 2001, Jacob Schroeder wrote:
> 
> > I've got a Linksys LNE100TX that is marked ver. 5.0 on the board and 4.1 on the chipset. It's seems to be working fine as far as the driver finding it and being able to access the network and all, but my problem is that I've had an unusually large number of packet collisions since I hooked this NIC upto the network. I've got 5 sometimes 6 computers on the network counting the firewall, all going through the 8 port hub. My machine with the LNE100TX is the fileserver for the LAN. In just a couple hours ifconfig tells me I've had 65,832 packet collisions on this NIC. I think the problem is just that the NIC is trying to use full duplex instead of half, so I tried using "insmod tulip debug=1 options=9" and "insmod tulip debug=1 options=12" as seen on the www.scyld.com site but I'm still having the problem. 
> > 
> > Is there something I'm missing or does this NIC not support those options?
> > 
> > TIA,
> > Jacob
> > 
> > BTW - system specs are Debian 2.2r4 on a 1Ghz Athlon w/256MB Ram. The tulip driver is version 0.91 loading as a module at boot time.
> > 
> > -----
> > Windows:
> > 
> > 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit
> > operating system originally coded for a 4 bit microprocessor, written
> > by a 2 bit company, that can't stand 1 bit of competition.
> > 
> > Linux:
> > 
> > The ultimate windows patch.
> > 
> > http://www.linux.org/
> > _______________________________________________
> > tulip mailing list, tulip@scyld.com
> > To change to digest mode or unsubscribe visit
> > http://www.scyld.com/mailman/listinfo/tulip
> > 
> 
> -- 
> [-] Omae no subete no kichi wa ore no mono da. [-]
> 
> 


-----
Windows:

32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit
operating system originally coded for a 4 bit microprocessor, written
by a 2 bit company, that can't stand 1 bit of competition.

Linux:

The ultimate windows patch.

http://www.linux.org/