From owner-freebsd-alpha Fri Feb 25 13:22:13 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C090137B884; Fri, 25 Feb 2000 13:22:09 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA14734; Fri, 25 Feb 2000 16:22:06 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA52160; Fri, 25 Feb 2000 16:21:35 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 25 Feb 2000 16:21:35 -0500 (EST) To: Mike Smith Cc: Dirk Kleinhesselink , mjacob@feral.com, freebsd-alpha@FreeBSD.ORG Subject: Re: problems with Qlogic SCSI combo card In-Reply-To: <200002252027.MAA00541@mass.cdrom.com> References: <14518.56559.18725.1757@grasshopper.cs.duke.edu> <200002252027.MAA00541@mass.cdrom.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14518.60317.343300.244411@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: > > > > Dirk Kleinhesselink writes: > > > > > > I booted off the FreeBSD 4.0 CD-ROM -- it is true that my system disk has > > > NetBSD/alpha 1.4.1 on it and that my 2nd IDE disk has Linux on it, but I > > > had booted off the SCSI CD-ROM I put on the 2nd channel of the card. > > > > > > > OK. Then it looks like the install kernel is broken & will latch onto > > any random BSD partition it finds. I'm not familiar with the install > > process, so I'll bow out now.. > > This certainly isn't the normal case; I used the 4.0 RC2 CDROM to > reinstall our DS20 the other day. Hmm.. I'm grasping at straws here..: Does the alpha install from a single kernel with the root device complied in, or does it load the contents of md0 from the boot loader, or does it mount the cdrom for its root..? I'm wondering if my instructions for him to break into the boot loader to set isp_mem_map=0xff might have prevented the script from loading the contents of md0, thus causing the vfs_conf code to go looking around for a filesystem & finding his netbsd fs? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message