From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 12 17:16:21 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D1D116A416 for ; Tue, 12 Dec 2006 17:16:21 +0000 (UTC) (envelope-from brucegb@realtime.net) Received: from ruth.realtime.net (mercury.realtime.net [205.238.132.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D83E44117 for ; Tue, 12 Dec 2006 17:08:34 +0000 (GMT) (envelope-from brucegb@realtime.net) Received: from tigerfish2.my.domain (cpe-24-27-51-69.austin.res.rr.com [24.27.51.69]) by realtime.net (Realtime Communications Advanced E-Mail Services V9.2) with ESMTP id 33271316-1817707 for ; Tue, 12 Dec 2006 11:09:57 -0600 Received: from tigerfish2.my.domain (localhost [127.0.0.1]) by tigerfish2.my.domain (8.13.8/8.13.8) with ESMTP id kBCH9v1Q085446 for ; Tue, 12 Dec 2006 11:09:57 -0600 (CST) (envelope-from brucegb@tigerfish2.my.domain) Received: (from brucegb@localhost) by tigerfish2.my.domain (8.13.8/8.13.8/Submit) id kBCH9vQm085445 for freebsd-hardware@freebsd.org; Tue, 12 Dec 2006 11:09:57 -0600 (CST) (envelope-from brucegb) Date: Tue, 12 Dec 2006 11:09:57 -0600 From: Bruce Burden To: freebsd-hardware@freebsd.org Message-ID: <20061212170913.GK44309@tigerfish2.my.domain> References: <20061212004136.4ef66c6f@vixen42> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061212004136.4ef66c6f@vixen42> User-Agent: Mutt/1.4.2.2i Subject: Re: nVidia chipsets? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2006 17:16:21 -0000 On Tue, Dec 12, 2006 at 12:41:36AM -0600, Vulpes Velox wrote: > > The only problem I ever ran into was with was the > ethernet chipset. It was originally a bit funky in regards to > deciding to go unresonsive for awhile. > Hmmm, I am having that problem with my Tyan Thunder K8WE with the nForce4 Profession chipset using the nfe driver from 9/1. I have NOT used the new PHY driver from late October/ early November. Perhaps that is the issue? [brucegb@tigerfish2 ~]$ Dec 6 18:13:44 tigerfish2 routed[444]: interface nfe0 to 192.168.1.2 broken: in=0 ierr=3 out=3 oerr=0 Dec 6 18:13:49 tigerfish2 routed[444]: interface nfe0 to 192.168.1.2 restored Hmm, now I see there is a 12/11 driver... Anyway, I have an Intel GB NIC arriving soon, so I'll get this dealt with one way or another. :-) Bruce -- ------------------------------------------------------------------------ "I like bad!" Bruce Burden Austin, TX. - Thuganlitha The Power and the Prophet Robert Don Hughes