Date: Wed, 22 Dec 2004 22:08:54 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: John Nielsen <lists@jnielsen.net> Cc: freebsd-current@freebsd.org Subject: Re: nForce2 RAID MCP (SATA) support? Message-ID: <20041223060854.GB28133@odin.ac.hmc.edu> In-Reply-To: <200412222048.32037.lists@jnielsen.net> References: <200412221315.47189.lists@jnielsen.net> <20041222202248.GB24094@odin.ac.hmc.edu> <200412222048.32037.lists@jnielsen.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Wed, Dec 22, 2004 at 08:48:31PM -0700, John Nielsen wrote: > On Wednesday 22 December 2004 01:22 pm, Brooks Davis wrote: > > On Wed, Dec 22, 2004 at 01:15:46PM -0700, John Nielsen wrote: > > > Hi folks- > > > > > > I'm trying to find out if there is support for integrated nForce2 RAID > > > MCP SATA controller already or planned in the forseeable future. > > > > > > I'm setting up a system with an MSI K7N2 Delta2 Series motherboard. > > > Booting from 5.3-R, the controller is detected as a generic ata > > > controller and runs the disks at UDMA33. I'm actually quite impressed > > > by the hardware even without a specialized driver, but I'd like to know > > > what to expect in terms of support. > > > > This RAID controler requires a software RAID implementation. We do > > support the necessicary RAID functionality, but apparently we don't > > support the meta data used by your BIOS. All your average onboard RAID > > system does is allow you to boot from a mirror or strip. Once you're > > booted, it's up to the OS to read the geometry data from the disks and > > proceed with software RAID support. Since there's no standard for the > > on-disk metadata, we only support those systems were we've managed to > > pry the data out of the manufacture or reverse engineer the format. > > That's understandable. I don't have an immediate need for RAID support > though. 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. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBymD2XY6L6fI4GtQRAjm9AJ4mRMRwGDrCGJWxLtRsDTGjN9oeWwCeMDe9 aCnL6cJGCALCY08iVrfiNfg= =+gBc -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041223060854.GB28133>