From owner-freebsd-amd64@FreeBSD.ORG  Fri Oct 31 13:30:56 2003
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 378BE16A4CF
	for <amd64@freebsd.org>; Fri, 31 Oct 2003 13:30:56 -0800 (PST)
Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F1FEF43F85
	for <amd64@freebsd.org>; Fri, 31 Oct 2003 13:30:54 -0800 (PST)
	(envelope-from adridg@cs.kun.nl)
Received: from localhost.ebn.kun.nl by pandora.cs.kun.nl
	via odin.cs.kun.nl [131.174.33.33] with ESMTP for <amd64@freebsd.org>
	id h9VLUW6G029901 (8.12.10/3.58);
	Fri, 31 Oct 2003 22:30:45 +0100 (MET)
From: Adriaan de Groot <adridg@cs.kun.nl>
To: amd64@freebsd.org
Date: Fri, 31 Oct 2003 22:30:09 +0100
User-Agent: KMail/1.5.2
References: <200310272055.54288.adridg@cs.kun.nl>
	<20031028201317.GD50559@dragon.nuxi.com> <200310312200.06633.adridg@cs.kun.nl>
In-Reply-To: <200310312200.06633.adridg@cs.kun.nl>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310312230.09619.adridg@cs.kun.nl>
Subject: Re: bootstrapping
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Oct 2003 21:30:56 -0000

On Friday 31 October 2003 22:00, Adriaan de Groot wrote:
> I'm wondering about the promise fasttrack 378 RAID controller. I picked up
> one (1) SATA drive, and stuck it to the promise connectors. While the
> controller sees the drive on bootup, once the kernel boots (and reports
> ata[234] on atapci1) there's no devices there to speak of. Is this a normal
> phenomenon? A driver issue? Have I been a moron to think that a RAID
> controller can also act like a plain ata bus?

This was just me being foolish. The new slimmer cable doesn't obviate the need 
for a 4-pin molex power connector. Doing newfs on the drive, though, gets me 
a GPF panic, Stopped at getdirtybuf+0x2d: decl %eax. Guess it's NFS mount 
then for the sources.