From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 4 06:31:59 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A157116A4CE; Sat, 4 Sep 2004 06:31:59 +0000 (GMT) Received: from mail.cableone.net (scanmail3.cableone.net [24.116.0.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CC7D43D4C; Sat, 4 Sep 2004 06:31:59 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.71.12]) by smail3.cableone.net (SurgeMail 1.9b) with ESMTP id 34575476 for multiple; Fri, 03 Sep 2004 23:15:21 -0700 Date: Sat, 4 Sep 2004 01:31:24 -0500 From: Vulpes Velox To: "Jeremy Messenger" Message-ID: <20040904013124.2f2af482@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: References: <20040825225405.SUTS4710.lakermmtao06.cox.net@smtp.east.cox.net> <20040825232842.14a8cf08@vixen42.24-119-122-191.cpe.cableone.net> <20040903223930.72e603bd@vixen42.24-119-122-191.cpe.cableone.net> X-Mailer: Sylpheed-Claws 0.9.12a (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Server: High Performance Mail Server - http://surgemail.com cc: gnome@freebsd.org cc: hardware@freebsd.org Subject: Re: motherboard has died, any recommend? nForce2? or else? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2004 06:31:59 -0000 On Sat, 04 Sep 2004 01:02:33 -0500 "Jeremy Messenger" wrote: > I think, I have finished with the walk throught in pciconf.. > Current, I have six 'noneN': Five are Memory controller and one is > ethernet. The USB 2.0 is already included, so I just add 'device > ehci' in kernel. I don't know if your has same USB as mine (8 USB > ports). Not sure about yours, but here it works nicely under the vr driver. > As for the ethernet, nvnet is out of date that doesn't has our ID. I > went to Nvidia's website and it has newer nforce driver that has > our ethernet support. I have contracted with the nvnet port author > and he is planning to update, then let me to test it. The nvnet in > ports tree is using nforce driver that is from 2003, btw. Try the vr driver? Those are used on some of those boards.