From owner-freebsd-bugs Thu Mar 2 02:04:13 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id CAA07197 for bugs-outgoing; Thu, 2 Mar 1995 02:04:13 -0800 Received: from mail.Germany.EU.net (mail.Germany.EU.net [192.76.144.65]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id CAA07182 for ; Thu, 2 Mar 1995 02:04:08 -0800 Received: by mail.Germany.EU.net with SMTP (8.6.5:29/EUnetD-2.5.1.d) via EUnet id LAA24065; Thu, 2 Mar 1995 11:05:20 +0100 Received: by ruhrgebiet.individual.net (/\==/\ Smail3.1.28.1 #28.1) id ; Thu, 2 Mar 95 10:00 GMT Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Thu, 2 Mar 95 10:57 MET Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: 021095-SNAP To: jeffh@cybernetics.net (Jeff Hoffman) Date: Thu, 2 Mar 1995 10:57:49 -0500 (MET) Cc: bugs@FreeBSD.org In-Reply-To: from "Jeff Hoffman" at Mar 1, 95 02:44:36 pm X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1167 Sender: bugs-owner@FreeBSD.org Precedence: bulk > > On Wed, 1 Mar 1995, Michael Quigley wrote: > > > I've not been able to boot the latest snapshot version on at least 3 > > machines at my disposal. They are all of varying configurations and > > processors. Basically what happens, is that they lock up when trying to > > boot off the floppy. I've made my boot disk the same way I did with > > 2.0-RELEASE: > > > > dd if= of=/dev/fd0 bs=18k > > > > With no luck. Any ideas? > > I had this same thing happen to me. What always get me by it (this may > be totally different from what's happening with you) is to repeatedly tap > the num lock key while it's booting. > > ie. hit turn on the computer, right before it hits the floppy start > tapping num lock until you see the FreeBSD boot prompt. > > Don't ask me why this works, I have no clue, but it DOES work. My > computer would not boot (it would lock) any I did this and it fixed it. > Then I tried it again to make sure it wasn't a fluke. > I have made a similiar experience. I have to reset my machine a few times before FreeBSD will be booted. Never had this problem with 2.0-RELEASE. Why was the boot code changed? Robert