From owner-freebsd-questions@FreeBSD.ORG Tue Oct 10 01:55:20 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6C1416A407 for ; Tue, 10 Oct 2006 01:55:20 +0000 (UTC) (envelope-from juhasaarinen@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2733043D4C for ; Tue, 10 Oct 2006 01:55:19 +0000 (GMT) (envelope-from juhasaarinen@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1681855wxd for ; Mon, 09 Oct 2006 18:55:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZXvge1lRnIkjQ+vUYavQ7zmZPCZjOGB5tIdWZ4SSVMkX38OkVsR6cPZpi4mIjbX/bHCyYgE1XekbaV6VR7U9V8g3eGp+BBkE21LQgkcm5oZcEaD02KPyXG2PDUpcbl0ZnNgiRmC1Pk6AMNVYhxwvJXFhfOpcF3iy5BeWGxqeh5M= Received: by 10.90.68.15 with SMTP id q15mr3322219aga; Mon, 09 Oct 2006 18:55:19 -0700 (PDT) Received: by 10.90.63.8 with HTTP; Mon, 9 Oct 2006 18:55:19 -0700 (PDT) Message-ID: Date: Tue, 10 Oct 2006 14:55:19 +1300 From: "Juha Saarinen" To: "Antony Mawer" In-Reply-To: <452AF31C.4080302@mawer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <452AEA98.2030409@mawer.org> <452AF31C.4080302@mawer.org> Cc: FreeBSD questions Subject: Re: AHCI support in 6.1-RELEASE? 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: Tue, 10 Oct 2006 01:55:20 -0000 On 10/10/06, Antony Mawer wrote: > Usually I find that ad0/ad1 = primary IDE (master/slave), ad2/3 = > secondary IDE (master/slave), and then the SATA connectors pick up from > ad4 onwards... > > The SATA ports seem to be numbered in increments of 2, presumably > because every SATA port is a "master", so the usual "slave" position is > unused... ie: > > SATA 0 -> ad4 > SATA 1 -> ad6 > SATA 2 -> ad8 > SATA 3 -> ad10 This is how it looks in dmesg now: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xd000-0xd007,0xd400-0xd403,0xd800-0xd807,0xdc00-0 xdc03,0xe000-0xe00f mem 0xe2307000-0xe23073ff irq 19 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 > Presumably turning off ATA_STATIC_ID would just number them in the > sequential order (ad0, ad1, ad2, ...) based on the devices that are > actually connected... but this can mess things up when you connect > additional drives at a later date somewhere in the middle of the chain! > > I have a patch I wrote for sysinstall somewhere that allows you to do > disk=auto in an install.cfg, and it picks the first device it comes > across (eg. if ad4 is the first IDE disk, it picks it over ad10)... > we've found this very handy for installation/deployment scenarios that > are automated via install.cfg but may have different disk configurations... > > If there's enough interest I might look at submitting it for inclusion... Could be useful... -- Juha