From owner-freebsd-questions Wed Mar 29 10:25:50 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23981 for questions-outgoing; Wed, 29 Mar 1995 10:25:50 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA23975 for ; Wed, 29 Mar 1995 10:25:47 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id NAA00268; Wed, 29 Mar 1995 13:24:09 -0500 From: Peter Dufault Message-Id: <199503291824.NAA00268@hda.com> Subject: Re: New FreeBSD boot floppies won't boot To: jmrueda@diatel.upm.es (Javier Martin Rueda) Date: Wed, 29 Mar 1995 13:24:09 -0500 (EST) Cc: questions@FreeBSD.org In-Reply-To: <643*/S=jmrueda/OU=diatel/O=upm/PRMD=iris/ADMD=mensatex/C=es/@MHS> from "Javier Martin Rueda" at Mar 29, 95 07:31:44 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1608 Sender: questions-owner@FreeBSD.org Precedence: bulk Javier Martin Rueda writes: > > > I have a PC which will boot all the boot floppies I have thrown at it > > (dos os2 linux netbsd and even freebsd) except FreeBSD boot disks from > > 950210 onwards. > > So, you are in the same case as I: I installed 2.0 RELEASE and it worked > fine. However, from SNAPSHOT 950210 onwards, the following happens: > > I enter the boot/install disk, the system begins booting, reading the disk > and so on. Everything seems to be going OK, except for a "minor" detail: > I cannot see anything in the screen. Only the cursor goes from blinking to > steady a few seconds after boot. > > I don't know the reason yet, but I managed to solve that: just install the > boot blocks from 2.0 RELEASE on the install disk and you will see things > again. I've done that this morning, as I wanted to test 950322-SNAP, and > it worked! > > To do that, you must have a 2.0 system running already, of course :-). > > NOTE: the cursor still goes from blinking to steady, just when the kernel > has been loaded and the memory test begins, and the screen seems to be in > a graphic mode instead of a text mode (because text display is slower than > usual). But at least, you see the display :-) > > Anyone has a better solution than this one? My guess is your problem is the keyboard probe in the new boot blocks to support serial consoles. Be sure you have the latest since there were some problems with some revs. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267