Ken Brownfield wrote:
>Ah, I bet you didn't live through the truly atrocious 3Com drivers of
>the past. ;) The new 3Com stuff seems passable for desktops, but having
>been bitten dozens of times, I'm about 4^4^4^4 times shy.
>
I didn't really start using 3coms until
a couple of years ago...
>That's all logged (dmesg, etc), if not distinctly queryable. Don't the
>iANS tools allow this functionality, and more?
>
yes, you can grope through the logs (as part of
the process of puzzling it out) and there are
ways to get the information - but it's so much
nicer to just get the speed and duplex from
an mii-command, on the spot.
>
>
>Oh, and six years of production on hundreds of EtherExpress NICs with
>zero (0) issues. Obviously, not everyone sees every bug, but the
>preponderance of evidence I've seen in production environments puts the
>EE way ahead of 3Com.
>
Well, like I say it's a mixed bag. We have mail/dns
servers (580 dns domains, 100,000 messages/day)
that have been runing for over 600 days, and not
a hint of trouble from the eepro100 drivers.
OTOH we have some new dell boxes with intel
pro 100 nics where we can quickly get the "eth0
reports no resources" message and poor or no
connectivity with a couple hours of apachebench
on a 100 MB lan.
could be a chipset issue...
>3Com for Windows desktops works just fine.
>
windoze desktops? give them ne2000s, who cares.
>
>I'd like to try existing Tulip hardware though for another option.
>Though 8139too seems to work well.
>
I've heard the horror stories about realtek
cards, but they seem to work well for me -
Joe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 07 2002 - 21:00:59 EST