New Nforce2 variant doesn't recognize SATA as SATA

secmgr security at
Fri Mar 11 09:26:38 PST 2005

secmgr wrote:

> I just picked up a new ABIT NF7-S2G motherboard (NF2 MCP chip set with 
> gigE and SATA/RAID).  I'm running 5.3 release on it.  The standard 
> parallel ATA chipset returns a "known" id .  The SATA i/f  seems to be 
> too new, and freebsd treats it like an unknown udma33 controller.  
> There's no Marvel bridge on the mobo.  Is this a true SATA interface?  
> Should I be able to get away with putting entries in the following? 
> (i'm not concerned about the raid thing).  They curently work as 
> udma33 disks.
> thanks
> jim
> ata-pci.h:#define ATA_NFORCE2_MCP2      0x008e10de
> ata-chipset.c:     { ATA_NFORCE2_MCP2, 0, AMDNVIDIA, NVIDIA, 
> ATA_UDMA6, "nVidia nForce2 MCP2" },

well, to follow up my own mail, the trick above didn't help.  the ata 
code still thinks it's a brain dead ata device and limits it to UDMA33.  
Help!  When I looked through the H/W compat list, it said that Nforce 2 
was supported, which is why I felt confident buying the board.  I'd 
really like to get this working at SATA 150, even if the current drives 
might be bridged.

Failing that, is there a definitive list of SATA PCI boards which 
FreeBSD does full support?


atapci0: <nVidia nForce2 MCP UDMA133 controller> port 
0x177,0x3f6,0x1f0-0x1f7 at device 9.0 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
atapci1: <nVidia nForce2 MCP2 UDMA133 controller> port 
,0x970-0x977,0xbf0-0xbf3,0x9f0-0x9f7 irq 11 at device 11.0 on pci0
ata2: channel #0 on atapci1
ata3: channel #1 on atapci1
.ata2-master: DMA limited to UDMA33, non-ATA66 cable or device
ad4: 152627MB <SAMSUNG SP1614C/SW100-30> [310101/16/63] at ata2-master 
ata3-master: DMA limited to UDMA33, non-ATA66 cable or device
ad6: 152627MB <SAMSUNG SP1614C/SW100-30> [310101/16/63] at ata3-master 

More information about the freebsd-stable mailing list