Date: Tue, 11 Jul 2000 10:17:38 +0100 From: "Lawrence Farr" <lawrence@epcdirect.co.uk> To: <freebsd-hardware@freebsd.org> Subject: Tigon-II boards (Was sysconnect and intel gig boards) Message-ID: <NDBBJNMBOLGAIICJIEIGGEPKCJAA.lawrence@epcdirect.co.uk> In-Reply-To: <200007102356.e6ANuGk18566@portnoy.lbl.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
I am seeing the same problem with the card going up and down at boot time, which stops netatalk from running. Unfortunately, every time you start netatalk it brings the card down then up again. Are there any patches for this as yet? Lawrence Farr EPC Direct Limited mailto:lawrence@epcdirect.co.uk T:01179666123 F:01179666111 M:07970780901 > -----Original Message----- > From: owner-freebsd-hardware@FreeBSD.ORG > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Jin Guojun (DSD > staff) > Sent: 11 July 2000 00:56 > To: jhartley@netrail.net; mjacob@feral.com > Cc: freebsd-hardware@FreeBSD.ORG > Subject: Re: SysKonnect and Intel gig boards > > > Matthew Jacob <mjacob@feral.com> Wrote: > > > Don't use the wx driven EEPRO-1000 from 4.0 (wait for the 4.1 > release which > > will have some bug fixes). > > > > I can't speak about SysKonnect. The Tigon-II based NetGear > cards have been > > peachy. > > Just more info.: > > SysKonnect and Intel EEPRO-1000 have the similar pricey, but they > work well. > The Tigon-II based NetGear card is cheaper, but has a couple of drawback: > (1) the driver under FreeBSD up/down a couple of times at boottime, > this causes NFS mount failure during boot. It is not a big > deal. I fixed it in rc.local with a line: > > df | grep $mymount_point || mount -a > > (2) chewing significant CPU: (tested on completely idle machines) > 500 MHz P-III + single NetGear A620 I/O > takes 47% CPU time > > 750 MHz AMD K7 + single NetGear A620 I/O > takes less 10% CPU > > 500 MHz P-III + single SysKonnect I/O > takes less 5% CPU > > If you have a high end machine, it is probably not a big issue. The driver > chews CPU on both FreeBSD and Linux; so it is driver issue, but > O.S. Hopefully, > the newer driver will fix the problem. > > -Jin > > > On Mon, 10 Jul 2000, Jeff Hartley wrote: > > > > > Anyone have any experience (good/bad/indifferent) with the Intel GigSX > > > boards, or the SysKonnect dual-port GigSX boards, under > 4.0-RELEASE? I'm in > > > need of quad-gig boxes, and I'm reluctant to stick with 3COM, > based on an > > > unsatisfactory failure rate in the past. Horror stories or blessings, > > > anyone? I did notice that SysKonnect seems to be friendlier with the > > > developer community than Intel (go figure). > > > > > > Thanks, > > > -Jeff Hartley > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBJNMBOLGAIICJIEIGGEPKCJAA.lawrence>