Date: Sat, 16 Sep 2000 20:55:31 +0200 From: Bernd Walter <ticso@cicely5.cicely.de> To: John Baldwin <jhb@pike.osd.bsdi.com> Cc: Wilko Bulte <wkb@freebie.demon.nl>, Matthew Jacob <mjacob@feral.com>, alpha@freebsd.org, dcs@freebsd.orgg Subject: Re: Loader badly broken on the alpha Message-ID: <20000916205531.B66584@cicely5.cicely.de> In-Reply-To: <200009161831.LAA21933@pike.osd.bsdi.com>; from jhb@pike.osd.bsdi.com on Sat, Sep 16, 2000 at 11:31:27AM -0700 References: <20000916200658.B66455@cicely5.cicely.de> <200009161831.LAA21933@pike.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 16, 2000 at 11:31:27AM -0700, John Baldwin wrote: > 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. Mmmh - Bad. Then the first place is the kernel root mount where we can change drives so the kernel need to be on the disk too. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de 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?20000916205531.B66584>