From owner-freebsd-hardware Mon Sep 15 11:57:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16760 for hardware-outgoing; Mon, 15 Sep 1997 11:57:51 -0700 (PDT) Received: from onyx.atipa.com (user27586@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA16750 for ; Mon, 15 Sep 1997 11:57:47 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 15 Sep 1997 19:01:31 -0000 Date: Mon, 15 Sep 1997 13:01:31 -0600 (MDT) From: Atipa X-Sender: freebsd@dot.ishiboo.com To: Jason Lixfeld cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: DLINK 21140 Card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The D-Link cards I am familiar with have a nice chipset, but a piss-poor connector. Instead of using all 8 pins for the RJ-45 connector, they try to save about $.0005 per card by only using the 4 TX/RX pins. This results in lots of intermittant connections. An intermittant connection on a switching medium (10/100) can cause lock-ups like you are reporting. We discontinued carrying that card for this exact reason. My recommendation would be to make sure you have good strain-relief on the cable, and lateral support if possible. Or replace the card... If it is not a physical connection problem, you may have buffer overflows. Do you get any erros in /var/log/messages? Does dmesg report "deo timeout"? Kevin On Sun, 14 Sep 1997, Jason Lixfeld wrote: > I have FreeBSD 2.2.2, DLink DEC Tulip 21140AE REV-2C Chipset with the > if_de.c from Matt Thomas' site, 3am-software.com. I have tried with the > 21140AC REV-1B Chipset, and am getting the same problems: It's fine on a > bootup, but after a few hours, the ethernet just stops responding. Their > is still a link light on my hub, put it is not pingable, and tests from > the console are useless. ifconfig de0 shows the interface as being up, > however I'm seeing a flag "OACTIVE" and I'm not sure that is supposed to > be there. Has anyone had trouble with these cards/driver before, and does > anyone have a solution? > > TiA.. > > >