[KLUG Members] Linksys NICs

Bryan J. Smith members@kalamazoolinux.org
Thu, 28 Jun 2001 21:29:31 -0400


Bruce Smith wrote:
> The thing I don't like is when I purchase the exact same model
> card as the one I already own,

But they changed the "revision."  Blame Digital for selling off its
network semiconductor division back in 1997.

> the new one doesn't work under Linux because they completely
> changed the chipset on the card.

It's just the Centaur 985 chip.

> Maybe there was a new driver that I could have downloaded, but
> I was loading Redhat for someone else and didn't have a half
> a day to waste trying to get the card working.

It takes me ~5 minutes.

> This was a release or two ago of Redhat, so maybe they are all
> supported under stock Redhat now, but I wouldn't buy another
> Linksys card because I have no idea what chipset I'm getting.

Linus and Becker had a "falling out" on how to do NIC drivers under
kernel 2.2.  Becker's setup is fine once you learn how to do it. 
It's actually quite sweet, and Becker puts the compile command at
the end of the .c source file.

> If you look at their support page on their site, they have
> four different windows drivers for the same model card.
> You have to look at the physical card and read the numbers
> off the chips to determine what windows driver to download.
> Four different chipsets?  I don't know.
> I also have two LNE100TX purchased at the same time that
> amazingly have the same chipset and same rev.  They both
> work fine under Linux (tulip driver), but only one works
> under Windows 98.  I've also seen other flaky things
> things with them under windows at work.

Yep, I concur.  I just had to replace one in my system for Windows. 
Of course, I've got other issues:
http://lists.leap-cf.org/pipermail/leapbs/2001-June/000223.html

-- TheBS

-- 
Bryan J. Smith   mailto:b.j.smith@ieee.org   chat:thebs413
SmithConcepts, Inc.           http://www.SmithConcepts.com
==========================================================
Linux 'Worms' exploit known security holes that were fixed
3-12 months earlier.  NT/2000 'Worms' exploit unknown se-
curity holes that won't be fixed for another 3-12 months.