From owner-freebsd-hackers Tue Dec 29 20:31:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28236 for freebsd-hackers-outgoing; Tue, 29 Dec 1998 20:31:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28228 for ; Tue, 29 Dec 1998 20:31:22 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id XAA10206; Tue, 29 Dec 1998 23:30:46 -0500 (EST) Date: Tue, 29 Dec 1998 23:30:46 -0500 (EST) From: Daniel Eischen Message-Id: <199812300430.XAA10206@pcnet1.pcnet.com> To: mrcpu@internetcds.com, wilko@yedi.iaf.nl Subject: Re: comments on de driver error message? Cc: FreeBSD-hackers@FreeBSD.ORG, eischen@vigrid.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I tested all mine with a Fluke Lanmeter 6802 to 100mbit, and they all > checked fine. Only the de0 card reports any errors, nothing else > (including the hubs and the lan tester) think anything is wrong at all... Does the Lanmeter also validate the CRCs in the packets? If the de error messages always indicate teh same Ethernet address(es) and there are other systems in the network that don't evoke these same messages, then it is hard to point the finger at the de card. In my case, the error message always indicated the same Ethernet address. It turned out the RJ58 connector was crimped too hard, so that the metal contacts were recessed too much and didn't make a good connection when it was plugged in. The fault was mine because I made the [bad] cables in the first place :( Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message