Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!sgiblab!gatekeeper.us.oracle.com!decwrl!pa.dec.com!usenet.pa.dec.com!jkh From: jkh@nx.ilo.dec.com (Jordan Hubbard) Newsgroups: comp.os.386bsd.bugs Subject: Re: 3com509 driver for FreeBSD?? Date: 29 Jun 1994 05:57:00 GMT Organization: Digital Equipment Corporation, Galway Ireland Lines: 16 Message-ID: <JKH.94Jun29065700@nx.ilo.dec.com> References: <19940626.122208.045870.NETNEWS@VM.BIU.AC.IL> <2uq6ji$rmj@fw.novatel.ca> NNTP-Posting-Host: nx.ilo.dec.com In-reply-to: hpeyerl@sidney.novatel.ca's message of 28 Jun 1994 22:01:21 GMT In article <2uq6ji$rmj@fw.novatel.ca> hpeyerl@sidney.novatel.ca (Herb Peyerl) writes: This might sound stupid but our company uses only 3c509 cards as well (which is why I originally wrote the driver) and I'm using them in many PC's running NetBSD and am having "no" problems. In fact, the PC's are backed up nightly through the cards via NFS. One of the machines is running an EISA (3c579) version of the card and one of the PC's even runs two cards: Similarly good results are being had with FreeBSD (1.1R and 1.1.5A) machines and 3c509 ethernet cards all over the place, so I can also only gather that it's something in your configuration or the hardware itself. The 3c509 drivers in FreeBSD and NetBSD are so similar as to be indistinguishable. Jordan