From owner-freebsd-hackers Thu Dec 23 10:33:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id DB1CD14D6A for ; Thu, 23 Dec 1999 10:33:37 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA03865; Thu, 23 Dec 1999 13:33:32 -0500 (EST) Date: Thu, 23 Dec 1999 13:33:32 -0500 (EST) From: Daniel Eischen Message-Id: <199912231833.NAA03865@pcnet1.pcnet.com> To: dgilbert@velocet.ca, freebsd-hackers@FreeBSD.ORG Subject: Re: deX OErrs on crossed link. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Gilbert wrote: > I've been trying a number of different ethernet configurations > out... and at first I was willing to accept that the cable may have > been at fault. However, Now that I have had the chance for further > experimentation, it appears that it may not. > > I am using the 4-port DLink adapter (uses tulip chips) on the server > and currently intel fxp0 chips on the clients. With this setup, I get > a huge number of OErrs on the deX interface (nothing shows on the fxp0 > on the other end). If I use an fxp in the server, no errors... and I > have tried a variety of handmade and professionally-made cables to > join them. > > I have even tried shutting down full-duplex... doesn't help. Someone else, just yesterday, posted the a similar problem on the -stable list. He was using a 4-port ZNYX card (de driver also). With the de driver in -stable, he got a huge number of output errors, but no errors on input. Using the ZNYX supplied driver for FreeBSD instead of de, the problem didn't exist. FWIW, I'm using a 4-port ZNYX card with the stock de driver on 3.3-stable without any problems - 10BaseT and 100BaseT, both at half-duplex. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message