From owner-freebsd-alpha Thu Nov 1 11: 1:22 2001 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 968A537B405 for ; Thu, 1 Nov 2001 11:01:12 -0800 (PST) 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 OAA14693; Thu, 1 Nov 2001 14:01:08 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id fA1J0gj59952; Thu, 1 Nov 2001 14:00:42 -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 Message-ID: <15329.39897.847099.976000@grasshopper.cs.duke.edu> Date: Thu, 1 Nov 2001 14:00:41 -0500 (EST) To: "DAVE CUSHING" Cc: Subject: Re: AlphaServer 400 In-Reply-To: <01Nov1.133922est.119057@charon.cambrianc.on.ca> References: <01Nov1.133922est.119057@charon.cambrianc.on.ca> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org DAVE CUSHING writes: > I forgot to try to boot from the second controller, so I decided to try it and see if it would see the drives properly, here are the results: > > >>>boot dkb0 > (boot dkb0.0.0.1000.0 -file kernel) > block 0 of dkb0.0.0.1000.0 is a valid boot block > reading 921 blocks from dkb0.0.0.1000.0 > bootstrap code read in > base = 1f2000, image_start = 0, image_bytes = 73200 > initializing HWRPB at 2000 > initializing page table at 1e4000 > initializing machine state > setting affinity to the primary CPU > jumping to bootstrap code > > > OpenVMS (TM) Alpha Operating System, Version V7.2-1 > > Guess, this was the test VMS machine :) Either way, I know the drives work ok with the hardware configuration, how come no FreeBSD?? > > Thanks in advance for your help (and patience with a newbie). Some older DEC disks don't spin up automatically. I can't remember if we send start-unit command to spin them up or not. If we don't, that might explain things. So now that the SRM has spun this disk up, does FreeBSD see it the next time you boot? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message