From owner-freebsd-current Sun Oct 18 19:53:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06078 for freebsd-current-outgoing; Sun, 18 Oct 1998 19:53:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06073 for ; Sun, 18 Oct 1998 19:53:41 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id VAA08723; Sun, 18 Oct 1998 21:53:11 -0500 (CDT) From: Kevin Day Message-Id: <199810190253.VAA08723@home.dragondata.com> Subject: Re: more 3.0-RELEASE boot.flp problems In-Reply-To: <19981018184704.A21657@Alameda.net> from Ulf Zimmermann at "Oct 18, 98 06:47:04 pm" To: ulf@Alameda.net Date: Sun, 18 Oct 1998 21:53:10 -0500 (CDT) Cc: dan@math.berkeley.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just installed 3.0-R and have exactly the same problems. argl. > > On Sun, Oct 18, 1998 at 05:46:54PM -0700, Dan Strick wrote: > > 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. > > 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. > > > > 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.) > > I checked all the keyboard "lock" keys and they were ok. > > > > So I reset the system and rebooted and this time the boot floppy > > came up ok. I went into the disk selection/partition menu > > and reinstalled the booteasy boot block (with the undocumented > > "w" option). Booteasy continued to misbehave as described > > above. The I booted a slightly older boot floppy (3.0-19981009-BETA > > I believe) and reinstalled the booteasy boot block. This fixed > > the problem. Then I reinstalled booteasy from the 3.0-RELEASE > > floppy and the problem came back. Then I reinstalled booteasy > > from the BETA release floppy and this fixed the problem. > > I decided to leave well enough alone. > > > > Then I checksummed my 3.0-RELEASE boot floppy and compared it > > to the boot.flp image on disk and the boot.flp entry in the > > 3.0-RELEASE/floppies/CHECKSUM.MD5 file. They all agreed. > > My floppy was copied correctly. > > > > Conclusion: 3.0-RELEASE/floppies/boot.flp is broken. > > > > Dan Strick > > dan@math.berkeley.edu > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > To add to this, I've got a Tyan Tomcat IV board.... booted it for the first time after doing a clean install of 3.0.... I got the: F1 FreeBSD Default: F2 Thing.. I hit F1, and it beeped 3-4 times, then went ahead and booted anyway. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message