From owner-freebsd-stable@FreeBSD.ORG Fri Mar 11 01:10:04 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEA7216A4CE for ; Fri, 11 Mar 2005 01:10:04 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AB9643D54 for ; Fri, 11 Mar 2005 01:10:04 +0000 (GMT) (envelope-from security@jim-liesl.org) Received: from daemon.jim-liesl.org ([69.170.98.158]) by mta9.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with ESMTP id <20050311011003.CIDJ12278.mta9.adelphia.net@daemon.jim-liesl.org> for ; Thu, 10 Mar 2005 20:10:03 -0500 Received: from [127.0.0.1] (unknown [192.168.1.10]) by daemon.jim-liesl.org (Postfix) with ESMTP id 68DF360D3 for ; Thu, 10 Mar 2005 18:09:49 -0700 (MST) Message-ID: <4230EFD1.2040908@jim-liesl.org> Date: Thu, 10 Mar 2005 18:09:37 -0700 From: secmgr User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: New Nforce2 variant doesn't recognize SATA as SATA X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2005 01:10:05 -0000 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" }, pciconf -lv says... atapci0@pci0:9:0: class=0x01018a card=0x1c08147b chip=0x008510de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'MCP2S Parallel ATA Controller' class = mass storage subclass = ATA atapci1@pci0:11:0: class=0x010185 card=0x1c08147b chip=0x008e10de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'MCP2S Serial ATA Compatible Controller' class = mass storage subclass = ATA dmesg says... atapci0: port 0xf000-0xf00f,0x376,0x170- 0x177,0x3f6,0x1f0-0x1f7 at device 9.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atapci1: port 0xcc00-0xcc0f,0xb70-0xb73,0x970-0x977,0xb f0-0xbf3,0x9f0-0x9f7 irq 11 at device 11.0 on pci0 Just for completeness, they use the VIA vge driven chip. pciconf says... vge0@pci2:11:0: class=0x020000 card=0x1c08147b chip=0x31191106 rev=0x11 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT3119 Rhine-GE Gigabit Ethernet Controller' class = network subclass = ethernet desg says... vge0: port 0xb000-0xb0ff mem 0xe8000000-0xe800 00ff irq 10 at device 11.0 on pci2 miibus0: on vge0 ciphy0: on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto