From owner-freebsd-current@FreeBSD.ORG  Tue Jun 30 15:57:35 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3857C1065674;
	Tue, 30 Jun 2009 15:57:35 +0000 (UTC)
	(envelope-from gary.jennejohn@freenet.de)
Received: from mout2.freenet.de (mout2.freenet.de [IPv6:2001:748:100:40::2:4])
	by mx1.freebsd.org (Postfix) with ESMTP id B32088FC28;
	Tue, 30 Jun 2009 15:57:34 +0000 (UTC)
	(envelope-from gary.jennejohn@freenet.de)
Received: from [195.4.92.22] (helo=12.mx.freenet.de)
	by mout2.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port
	25) (Exim 4.69 #92)
	id 1MLfi8-0007vm-GH; Tue, 30 Jun 2009 17:57:32 +0200
Received: from tac42.t.pppool.de ([89.55.172.66]:57084
	helo=ernst.jennejohn.org)
	by 12.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port
	25) (Exim 4.69 #79)
	id 1MLfi8-0003N5-4V; Tue, 30 Jun 2009 17:57:32 +0200
Date: Tue, 30 Jun 2009 17:57:31 +0200
From: Gary Jennejohn <gary.jennejohn@freenet.de>
To: Chris Hedley <freebsd-current@chrishedley.com>
Message-ID: <20090630175731.4c589f80@ernst.jennejohn.org>
In-Reply-To: <alpine.BSF.2.00.0906301524240.12510@teapot.cbhnet>
References: <alpine.BSF.2.00.0906071604540.1724@teapot.cbhnet>
	<4A2C124A.1050707@freebsd.org>
	<alpine.BSF.2.00.0906261725570.1809@teapot.cbhnet>
	<alpine.BSF.2.00.0906261926080.1809@teapot.cbhnet>
	<alpine.BSF.2.00.0906300051400.33237@teapot.cbhnet>
	<3c1674c90906291830g1c79c80bq42ce99f44588e968@mail.gmail.com>
	<alpine.BSF.2.00.0906300326290.1621@teapot.cbhnet>
	<20090630113544.3e2bef31@ernst.jennejohn.org>
	<alpine.BSF.2.00.0906301524240.12510@teapot.cbhnet>
X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.2; amd64-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org
Subject: Re: New builds won't boot (fwd)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: gary.jennejohn@freenet.de
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2009 15:57:35 -0000

On Tue, 30 Jun 2009 15:25:59 +0100 (BST)
Chris Hedley <freebsd-current@chrishedley.com> wrote:

> On Tue, 30 Jun 2009, Gary Jennejohn wrote:
> > It does seem to number based on slot, whereby the driver for some reason
> > acts as though SATA has master/slave disks, which of course it doesn't.
> >
> > You can get back to the old behavior by putting "options ATA_STATIC_ID"
> > into your kernel config file.
> 
> Hmm... weirdly, I noticed that /after/ putting that line into my config; 
> maybe I should try again without it and see what happens...?  I think I'll 
> do that a bit later today and report back if there's any difference.

Ah, yes.  Now that I think about it again, you're right.  That's also
when I started seeing it.

I'm now running mav's ata-cam patches and took ATA_STATIC_ID out of
my config file.  I'd sort of forgotten when/why I'd done it.

Sorry for the confusion.

---
Gary Jennejohn