From owner-freebsd-alpha Mon Mar 15 7:44:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from octopus.originative (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (Postfix) with ESMTP id 4A0201546D for ; Mon, 15 Mar 1999 07:44:14 -0800 (PST) (envelope-from paul@originative.co.uk) Received: by octopus with Internet Mail Service (5.5.2232.9) id ; Mon, 15 Mar 1999 15:42:18 -0000 Message-ID: From: paul@originative.co.uk To: tcrimi+@andrew.cmu.edu, alpha@freebsd.org, paul@originative.co.uk Subject: RE: New bootblocks Date: Mon, 15 Mar 1999 15:42:15 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: Thomas Valentino Crimi [mailto:tcrimi+@andrew.cmu.edu] > Sent: 15 March 1999 15:27 > To: alpha@freebsd.org; paul@originative.co.uk > Subject: Re: New bootblocks > > > Excerpts from FreeBSD-Alpha: 15-Mar-99 New bootblocks by > paul@originative.co.uk > > halt code = 2 > > kernel stack not valid halt > > PC = 184ec > > > > > I had this same problem, too, making it worse was that I had played > around with my boot.conf and guess what, unload was halting (in the > older bootblocks, wasn't this recently fixed?) > > One good replacement to fixit disks I found was that the emergecy > shell, while lacking ls (use echo *) did have ifconfig, ppp and > mount_nfs if you happen to have a machine nearby to stick an > alpha dist > on for binaries. The way I got my machine to boot doens't seem like > more than luck (replaced bootblocks and booted of an old > kernel). Just > wanted to share the fixit trick for all who may come to need it. > Only problem there is that on the Multia there's no vga support so there's no emergency shell either :-( Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message