Date: Fri, 31 Oct 2003 22:00:06 +0100 From: Adriaan de Groot <adridg@cs.kun.nl> To: amd64@freebsd.org Subject: Re: bootstrapping Message-ID: <200310312200.06633.adridg@cs.kun.nl> In-Reply-To: <20031028201317.GD50559@dragon.nuxi.com> References: <200310272055.54288.adridg@cs.kun.nl> <20031028201317.GD50559@dragon.nuxi.com>
index | next in thread | previous in thread | raw e-mail
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 ..home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200310312200.06633.adridg>