Jeff Garzik wrote:
As I said, the driver only "chokes" on a heterogeneous network with
Win98 hosts on the segment. After discovering this unfortunate
correlation we moved our Win98 boxes to a seperate segment and the
problems went away.
I can still heartily recommend the FA310TX boards for Linux
environments, however. We run approximately 15 Linux machines with
various hardware/software configurations, all using this card, and have
never had any problems except problems between Microsoft and Linux
hosts, which were easily solved as I stated above. Of course our small
office environment allowed us to make this change easily. If you are
part of a large-scale network that isn't so flexible I suppose the
Netgear cards might not be such a good choice. They cost us about $15 a
piece here and have proved themselves to us.
Scott
>
> Scott Long wrote:
> > Jeff Garzik wrote:
> > > Donald has recorded a sampling of some of the boards which work with his
> > > drivers on the each driver web page, at http://www.scyld.com/network/
> > > Since I particularly favor eepro100[1] and tulip chipsets, especially
> > > tulips, hunt around for boards which use that driver. People seem to
> > > report that the 21140-based Tulip boards are particularly stable, and
> > > the PNIC boards (such as NetGear) are particularly unstable.[2]
>
> > I have to say I disagree on this. We've been using the NetGear boards
> > almost exclusively for over a year at my site, and they have NEVER given
> > us problems. I have occasionally had problems with the NetGear cards
> > when they are on a network with Win98 hosts. The driver would choke, but
> > unloading and reloading the Tulip module would always solve the problem.
>
> If a driver "chokes" at all, I consider that particularly unstable :)
> Regardless of how easy it is to recover...
>
> Jeff
>
> --
> Jeff Garzik |
> Building 1024 | Free beer tomorrow.
> MandrakeSoft, Inc. |
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
