From owner-freebsd-alpha Sat Mar 3 14:40:17 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 9501B37B719 for ; Sat, 3 Mar 2001 14:40:10 -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 RAA14987; Sat, 3 Mar 2001 17:40:09 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f23MddQ12345; Sat, 3 Mar 2001 17:39:39 -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: <15009.29355.378253.970478@grasshopper.cs.duke.edu> Date: Sat, 3 Mar 2001 17:39:39 -0500 (EST) To: Oliver Lehmann Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: FreeBSD 4.2 on AlphaPC 164LX In-Reply-To: <13872.983652826@www13.gmx.net> References: <13872.983652826@www13.gmx.net> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oliver Lehmann writes: > >>>boot dva0 > (boot dva0.0.0.0.0 -flags 0) > block 0 af dva0.0.0.0.0 is a valif boot block reading 15 blocks from > dva0.0.0.0.0 bootstrap code read in base = 560000, image_start=0, > image_bytes = 1e00 initializing HWRPB at 2000 initializing page table at > ff56000 initializing machin state setting affinity to the primary VPU > jumping to bootstrap code > > And the System stops... This is the classic symptom of having your console pointed at the wrong device. FreeBSD is actually booting, but you can't see it, since you're not looking at the currently defined system console. The SRM console gives you enough feedback through a non-console input device to lull you into thinking you have the console setting correct. If you're using a serial console, make sure you're connected to COM1 and you've told the srm console you're using a serial console via this command at the SRM prompt: >>> set console serial If you're using a graphics console with keyboard and mouse, make sure you tell the SRM console to use it rather than the serial console via this command from the SRM prompt: >>> set console graphics After issuing one of those commands, make sure you power-cycle the box or do a hard reset. When the machine re-inits, you should notice the POST process is much more verbose. This is a FAQ. Too bad we don't have an FAQ to refer people to.. 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