Re: nForce2 RAID MCP (SATA) support?

MCP 2 doesn't have ANY SATA support. MCP have 6ch codec, 2xATA133, 
6xUSB2, 100Mbps ethernet, 6xPCI. MCP-T also have IEEE1394, SoundStorm 
support (I'm afraid it still unsupported, just 6ch codec too) and the 
interface for second 100Mbps ethernet (3COM). No SATA at all... Usually 
motherboard manufacturers add SATA controller (Silicon, etc) that allows 
to implement SATA support. Some puts GigE chip. But usually you need to 
pay a fee - one or more available PCI slots.

    Sincerely, Maxim M. Kazachek
        mailto:stranger_at_sberbank.sibnet.ru
        mailto:stranger_at_fpm.ami.nstu.ru


On Wed, 22 Dec 2004, Brooks Davis wrote:

> 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
>