From owner-freebsd-questions@FreeBSD.ORG Sun Feb 3 11:58:26 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5750416A417 for ; Sun, 3 Feb 2008 11:58:26 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id DB4FC13C4E3 for ; Sun, 3 Feb 2008 11:58:25 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-25-183.bredband.comhem.se ([83.253.25.183]:58852 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1JLdUM-0001Ai-5v for freebsd-questions@freebsd.org; Sun, 03 Feb 2008 12:58:25 +0100 Received: (qmail 71720 invoked from network); 3 Feb 2008 12:58:20 +0100 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 3 Feb 2008 12:58:20 +0100 Received: (qmail 65938 invoked by uid 1001); 3 Feb 2008 12:58:20 +0100 Date: Sun, 3 Feb 2008 12:58:19 +0100 From: Erik Trulsson To: Ted Mittelstaedt Message-ID: <20080203115819.GA65788@owl.midgard.homeip.net> Mail-Followup-To: Ted Mittelstaedt , darryl@osborne-ind.com, freebsd-questions@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Originating-IP: 83.253.25.183 X-Scan-Result: No virus found in message 1JLdUM-0001Ai-5v. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1JLdUM-0001Ai-5v d3177c737b21da045e69cf547685b860 Cc: freebsd-questions@freebsd.org Subject: Re: SATA question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2008 11:58:26 -0000 On Sun, Feb 03, 2008 at 01:25:07AM -0800, Ted Mittelstaedt wrote: >=20 > Looks like it isn't detecting it as a generic controller. >=20 > But I think this is the problem. Note that the system is > applying ata2 and ata3 to atapci0, and ata0 and ata1 to > atapci1. This is backwards, I've not seen this before in > the ata driver. Normally, ata0 and ata1 are applied to the > first controller - atapci0 - and ata2 and ata3 are applied > to the second controller - atapci1 - and so on. I have seen that before on one of my computers: atapci0: port 0xd000-0xd007,0xcc00-0xcc03,0= xc800-0xc807,0xc400-0xc403,0xc000-0xc00f,0xb800-0xb8ff irq 20 at device 15.= 0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177= ,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ata0: on atapci1 ata1: on atapci1 It looks like ata0 and ata1 are assigned to whichever interface looks like the "standard" ATA interface, regardless of in what order various ATA controllers are detected. >=20 > S=F8ren Schmidt put the support in for this chipset to the > ata driver. I'd file a PR and put it down to a driver bug. >=20 > Ted >=20 >=20 > > -----Original Message----- > > From: owner-freebsd-questions@freebsd.org > > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Darryl Hoar > > Sent: Friday, February 01, 2008 7:06 AM > > To: 'Ted Mittelstaedt'; freebsd-questions@freebsd.org > > Subject: RE: SATA question > > > > > > > > > -----Original Message----- > > > From: owner-freebsd-questions@freebsd.org > > > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Darryl Hoar > > > Sent: Tuesday, January 29, 2008 6:59 AM > > > To: freebsd-questions@freebsd.org > > > Subject: SATA question > > > > > > > > > Well, > > > maybe I spoke to soon. While looking at dmesg in prep for doing > > > a custom kernel for my new server, I noticed an oddity. > > > > > > ad4 - DMA limited to UDMA33, device found non-ata66 cable. > > > ad4 - > > > > > > Is this telling me the system recognized my > > > 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as > > > a UDMA33 ? > > > > > > > >>No doubt, a pciconf followed by insertion of the ID into the > > >>ata detection routines would help - assuming your sata chipset > > >>is supported. > > > > >>You don't have the entire dmesg here but it looks like it's > > >>using the generic driver. > > > > >>Ted > > > > > > atapci0: port > > 0xecb0-0xecb7,0xeca0-0xeca > > 3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem > > 0xefdfe000-0xefdfffff irq 6 > > at d > > evice 14.0 on pci3 > > ata2: on atapci0 > > ata3: on atapci0 > > > > atapci1: port > > 0x1f0-0x1f7,0x3f6,0x170-0x > > 177,0x376,0x8c0-0x8cf at device 2.1 on pci0 > > ata0: on atapci1 > > ata1: on atapci1 > > > > acd0: CDRW at ata0-master UDMA33 > > ad4: DMA limited to UDMA33, device found non-ATA66 cable > > ad4: 152587MB at ata2-master UDMA33 > > ad6: DMA limited to UDMA33, device found non-ATA66 cable > > ad6: 152587MB at ata3-master UDMA33 > > > > This is the copied relevant portions of demsg's output. I have only used > > pciconf to > > list devices, so am basically unfamilar with it. > > > > So, how do I get the system to recognize the drives as SATA ? > > --=20 Erik Trulsson ertr1013@student.uu.se