From owner-freebsd-amd64@FreeBSD.ORG Fri Oct 31 13:00:51 2003 Return-Path: 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 49AFE16A4D0 for ; Fri, 31 Oct 2003 13:00:51 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0583D43FAF for ; Fri, 31 Oct 2003 13:00:50 -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 id h9VL0R6G026312 (8.12.10/3.58); Fri, 31 Oct 2003 22:00:40 +0100 (MET) From: Adriaan de Groot To: amd64@freebsd.org Date: Fri, 31 Oct 2003 22:00:06 +0100 User-Agent: KMail/1.5.2 References: <200310272055.54288.adridg@cs.kun.nl> <20031028201317.GD50559@dragon.nuxi.com> In-Reply-To: <20031028201317.GD50559@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310312200.06633.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2003 21:00:51 -0000 On Tuesday 28 October 2003 21:13, David O'Brien wrote: > On Mon, Oct 27, 2003 at 08:55:54PM +0100, Adriaan de Groot wrote: > > gather there's no really working cvsup, and David's snapshot build from > > way back is (a) from wayback (b) unstable under load. > > I'll start a new snapshot build now. Can you wait 2 days? I am, like, patience incarnate. > That will work fine (32-bit FreeBSD). My FreeBSD/i386 5-CURRENT > reference system is now an Athlon64, and is my fastest "i386" box now. So I got a new board, discovered that the Zalman cooler didn't fit right and improvised with motherboard standoffs, and now it's time for me to start asking n00b questions again. My cvsup of -CURRENT is fetching src/sys/i4b now, it'll be a while before I'm ready to compile a kernel ... In the meantime I'm still using David's previous snapshot build, with a 3Com 3C905 for networking and an old 2G PATA HDD to start from. 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? Well, it'll all come out in the wash, once the kernel builds. Only 16M of cvsup to go ..