Date: Mon, 16 Sep 1996 09:10:58 +0200 (MET DST) From: Guido van Rooij <Guido.vanRooij@nl.cis.philips.com> To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Cc: pb@hsc.fr, Guido.vanRooij@nl.cis.philips.com, freebsd-hackers@freebsd.org Subject: Re: vx device broken in 21.1.5? Message-ID: <199609160710.JAA26316@spooky.lss.cp.philips.com> In-Reply-To: <199609131927.XAA00410@nagual.ru> from "[______ ______]" at "Sep 13, 96 11:27:46 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
[______ ______] 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609160710.JAA26316>