From owner-freebsd-current@FreeBSD.ORG Thu Dec 23 22:43:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6ADA16A4CE for ; Thu, 23 Dec 2004 22:43:15 +0000 (GMT) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 786A543D4C for ; Thu, 23 Dec 2004 22:43:15 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from [192.168.0.10] (jn@c-24-2-72-123.client.comcast.net [24.2.72.123]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id iBNMhEXI029653 for ; Thu, 23 Dec 2004 14:43:15 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-current@freebsd.org Date: Thu, 23 Dec 2004 15:42:11 -0700 User-Agent: KMail/1.7.2 References: <200412221315.47189.lists@jnielsen.net> <200412222048.32037.lists@jnielsen.net> <20041223060854.GB28133@odin.ac.hmc.edu> In-Reply-To: <20041223060854.GB28133@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412231542.11950.lists@jnielsen.net> X-Virus-Scanned: ClamAV 0.80/627/Sun Dec 12 11:53:11 2004 clamav-milter version 0.80j on ns1.jnielsen.net X-Virus-Status: Clean Subject: Re: nForce2 RAID MCP (SATA) support? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 22:43:15 -0000 On Wednesday 22 December 2004 11:08 pm, Brooks Davis wrote: > On Wed, Dec 22, 2004 at 08:48:31PM -0700, John Nielsen wrote: > > What would be needed to simply have the controller recognized > > and able to support UDMA 150 (or even 133)? > > At least in current, there's an nForce2 MCP device id that is supposed > to support UDMA6 so I suspect you may just need to wait a bit and it > will arrive. It's possiable you have a board with a non-standard > PCI-id. You might make sure "pciconf -lv" shows that your controler > shows a device ID of 0x008510de. If not, you may be a simple matter of > adding it to the necessicary two lines. Thanks, I'll try booting off a -current snapshot and see what shows up. JN