From owner-freebsd-alpha Fri Feb 25 11:45:36 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 6D1E437BAD5 for ; Fri, 25 Feb 2000 11:45:32 -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 OAA12092; Fri, 25 Feb 2000 14:45:29 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA51624; Fri, 25 Feb 2000 14:44:58 -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 14:44:58 -0500 (EST) To: mjacob@feral.com Cc: Dirk Kleinhesselink , freebsd-alpha@FreeBSD.ORG Subject: Re: problems with Qlogic SCSI combo card In-Reply-To: References: <14518.55529.208690.253836@grasshopper.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14518.55904.927335.311841@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > > On Fri, 25 Feb 2000, Andrew Gallatin wrote: > > > > > Matthew Jacob writes: > > > > > > I was loaned the mystery card from Dirk- it's got 2 Qlogic 1020 chips and a > > > 21040-AA (!!) chip and a 21050 bridge. I think he got past the memory mapped > > > vs. I/O, but couldn't boot. We'll see- I probably won't get to this today. > > > > Odd -- where did his boot stop? I'm running 5 or 6 AS600s with these > > cards & booting off them fine. They are production machines & are > > running -current from Jan, so something may have changed.. > > He said "could not find init"...It may be just plain pilot error. > The hardware is fine. His problem is pilot error -- he has probably booted from a Tru64 disk (or NetBSD, or OpenBSD, or Linux using BSD disklabels, etc). This can happen with the new bootstrap glue from Mike Smith which obtains the location of / from /etc/fstab. He needs to fix this by breaking into the boot loader & setting vfs.root.mountfrom to the appropriate disk. Somethine like ok set vfs.root.mountfrom=da1 is probably what he needs. I'm not terribly confident the syntax is correct. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message