From owner-freebsd-hackers  Mon Sep 16 00:12:54 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id AAA17381
          for hackers-outgoing; Mon, 16 Sep 1996 00:12:54 -0700 (PDT)
Received: from relay.philips.nl (ns.philips.nl [130.144.65.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA17362
          for <freebsd-hackers@freebsd.org>; Mon, 16 Sep 1996 00:12:48 -0700 (PDT)
Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id JAA26225; Mon, 16 Sep 1996 09:11:30 +0200
Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP
	id sma026130; Mon Sep 16 09:11:01 1996
Received: from spooky.lss.cp.philips.com (spooky.lss.cp.philips.com [130.144.199.105]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id JAA26983; Mon, 16 Sep 1996 09:13:56 +0200
Received: (from guido@localhost) 
	by spooky.lss.cp.philips.com (8.6.10/8.6.10-0.991c-08Nov95) id JAA26316; Mon, 16 Sep 1996 09:10:58 +0200
From: Guido van Rooij <Guido.vanRooij@nl.cis.philips.com>
Message-Id: <199609160710.JAA26316@spooky.lss.cp.philips.com>
Subject: Re: vx device broken in 21.1.5?
To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=)
Date: Mon, 16 Sep 1996 09:10:58 +0200 (MET DST)
Cc: pb@hsc.fr, Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@freebsd.org
Reply-To: Guido.vanRooij@nl.cis.philips.com
In-Reply-To: <199609131927.XAA00410@nagual.ru> from "[______ ______]" at "Sep 13, 96 11:27:46 pm"
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

[______ ______] wrote:
> > According to Guido van Rooij:
> > > I just ported the current Open/NetBSD if_vx driver to FreeBSD 2.1.5 and
> > > I am seeeing the exact same problems.
> > > 
> > > I've ben assured that these drivers do work.
> > 
> > I can say that I've experienced similar problems with
> > the 2.1.5 vx driver in an installation just a few days ago.
> > 
> > Some of the 3C595 series might be buggy: the vx driver (sometimes
> > but not always) prints a "early defective adapter" at boot time.
> > In addition to that, the reseller of the card told us that it was to
> > be discontinued and replaced with the 3C905... That's all the information
> > I have.
> > 
> > We replaced it with a 3C509 and lived happily ever after.
> 
> I have 3C509 and
> 1) Have "early defective..." diagnostic too
> 2) Hangs on output, ifconfig down/up heals it.
> 

I have a fix now. But it seems at least somethig is broken on my card. 
Tell me where to put my version of the driver. (which might be buggy though).

-Guido