From owner-freebsd-current Sun Oct 18 19:56:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06344 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:56:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles338.castles.com [208.214.167.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06339 for ; Sun, 18 Oct 1998 19:56:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA15782; Sun, 18 Oct 1998 20:00:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810190300.UAA15782@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dan@math.berkeley.edu (Dan Strick) cc: freebsd-current@FreeBSD.ORG Subject: Re: more 3.0-RELEASE boot.flp problems In-reply-to: Your message of "Sun, 18 Oct 1998 17:46:54 PDT." <199810190046.RAA12702@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Oct 1998 20:00:56 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After installing 3.0-RELEASE, I attempted to boot the new system > The booteasy program listed all the dos partition table entries and > asked which one to boot, giving the FreeBSD partition as the default. > I thought this was a bit odd. In my experience, the first time you > boot after a booteasy installation it indicates "F?" is the default. The default bootmanager is actually 'boot0' (pronounced 'BootZero'). You can install Booteasy to (hopefully) fix your problems by fetching it from the directory ftp.cdrom.com/pub/FreeBSD/tools. > So I hit return and the booteasy program beeped at my. The I hit > the specifically desired F-key and the booteasy program beeped at > me again. No matter what I typed, the boot program just beeped > at me. It did not even retype the boot prompt as I recall it > did after an inappropriate input. Boot0 behaves differently. There appears to be a problem with some BIOS translations for disks bigger than the old 504MB limit. > Then I did a hard reset. No change. I power cycled the machine. > No change. I rebooted the bootstrap floppy and it came up running > the standard installation script but was very confused about which > keyboard key meant what. (For example, the left arrow key selected > the "exit" option and the other arrow keys did nothing at all.) We've seen this problem during testing as well, but we haven't been able to characterise it, so we have no idea what's causing it. It doesn't ever seem to happen with the system once installed, only with the installation kernel. > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. Quite erroneous. There are a number of components that aren't working 100%, however on the whole it works pretty well. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message