From owner-freebsd-alpha Sat Sep 16 11:31:45 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id F298D37B422 for ; Sat, 16 Sep 2000 11:31:43 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id LAA21933; Sat, 16 Sep 2000 11:31:27 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009161831.LAA21933@pike.osd.bsdi.com> Subject: Re: Loader badly broken on the alpha In-Reply-To: <20000916200658.B66455@cicely5.cicely.de> from Bernd Walter at "Sep 16, 2000 08:06:58 pm" To: Bernd Walter Date: Sat, 16 Sep 2000 11:31:27 -0700 (PDT) Cc: Wilko Bulte , Matthew Jacob , alpha@freebsd.org, dcs@freebsd.orgg X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bernd Walter wrote: > On Sat, Sep 16, 2000 at 11:27:59AM +0200, Wilko Bulte wrote: > > Great :-( I nuked my -current box yesterday with the same loader problems. > > I promised billf to test the tx driver but now I'm screwed it seems. > > > > Any good suggestions to fix this loader thing short of reinstalling 4.1 > > first? > > I had the real luck to have an ancient loader from April on the disk. > It did not understood some configfiles and stopped with an prompt. > Then I had to do the set commands for the device hints. > > You should try offering a loader from a disk and then switching disks > on the loader prompt. You can't do that with SRM. :( SRM only tells you about your boot device, unlike the x86 BIOS which lets you talk to all the devices it knows about. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message