From owner-freebsd-hackers Mon Sep 15 12:30:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18769 for hackers-outgoing; Mon, 15 Sep 1997 12:30:22 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA18752; Mon, 15 Sep 1997 12:30:02 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.7/8.7.1) id PAA14616; Mon, 15 Sep 1997 15:40:02 -0400 Date: Mon, 15 Sep 1997 15:40:01 -0400 (EDT) From: Ben Black To: Atipa cc: Jason Lixfeld , 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk this is called T4 (vs TX) and it is a simplex version of fast ethernet. On Mon, 15 Sep 1997, Atipa wrote: > > 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.. > > > > > > >