Date: Thu, 17 Feb 2000 16:39:34 -0500 From: Coleman Kane <cokane@one.net> To: Mikhail Teterin <mi@kot.ne.mediaone.net> Cc: Omachonu Ogali <oogali@intranova.net>, stable@freebsd.org Subject: Re: xl0 packet dropping, still Message-ID: <20000217163934.A11257@evil.2y.net> In-Reply-To: <200002171632.LAA07138@rtfm.newton>; from mi@kot.ne.mediaone.net on Thu, Feb 17, 2000 at 11:35:03AM -0500 References: <Pine.BSF.4.10.10002171031520.91789-100000@hydrant.intranova.net> <200002171632.LAA07138@rtfm.newton>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Well, I do have an AMD based machine, but I don't see how the problem could possibly manifest itself to AMD based machines. There is no hw on the card that takes advantage of any Intel-only stuff. In fact, the 3Com cards are used in non-x86 boxes sometimes. FWIW, I know enough about CompUSA not to believe what those guys say. I have seen to many dumb responses to queries. Once, one of them told a customer that he could probably use EDO ram in his 486, but that it wouldn't take advantage of the EDO-ness. In fact, this is a very dangerous thing to do, and in some cases can fry your poor 486 mobo's cache. Needless to say, I 1-up'd him. --cokane Mikhail Teterin had the audacity to say: > > Omachonu Ogali once stated: > > =I had problems with the xl0 devices dropping packets and timing out, so > =I reverted to using an Intel EtherExpress Pro/100 (fxp0). > > FWIW, a CompUSA clerk told me, those don't work well in, say, AMD > based machines... > > -mi > [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE4rGqWERViMObJ880RASpDAJ4+DoSPxt0GZSRM3TbvnXBxSYN6JwCg19CK YcXOBXCqGNG67CxnFpfPquI= =5JuO -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000217163934.A11257>