Date: Fri, 21 Aug 1998 14:53:44 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Doug Rabson <dfr@nlsystems.com>, "Brent J. Nordquist" <bjn@visi.com>, John Birrell <jb@cimlogic.com.au>, freebsd-alpha@FreeBSD.ORG Subject: Re: FreeBSD/Alpha make buildworld stops at groff Message-ID: <13789.49021.995565.325186@grasshopper.cs.duke.edu> In-Reply-To: <1223.903721282@time.cdrom.com> References: <Pine.BSF.4.01.9808211016540.2954-100000@herring.nlsystems.com> <1223.903721282@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jordan K. Hubbard writes: <crashing on boot> How far do you get, exactly? Do you have an Intel or Cypress SIO? (show config from the SRM console prompt will tell you). One handy tip is to be absolutely certain to configure the root disk to match what you're actually using. It tends to blow up rather spectacularly when it cannot mount root / run init. > I've finally got a suitable cable for a serial console - does all of > that work the same way on the ALPHA? And how do you get the thing to Somewhat. It currently follows what the SRM console is using. If you're using a graphics console, it attempts to use the kbd/monitor, if you have previously 'set console serial' in the SRM, then it uses the serial console. > drop into gdb-remote mode when it falls over this quickly? There's no > chance to get into the debugger pre-emptively to type "gdb" for the > next trap. Make sure to have 'options DDB' defined, then boot with the -d flag. That should drop you into ddb almost immediately after the kernel begins execution. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13789.49021.995565.325186>