From owner-freebsd-current  Sun Apr 20 01:00:40 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA10652
          for current-outgoing; Sun, 20 Apr 1997 01:00:40 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA10640
          for <current@freefall.freebsd.org>; Sun, 20 Apr 1997 01:00:36 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA15759; Sun, 20 Apr 1997 17:58:22 +1000
Date: Sun, 20 Apr 1997 17:58:22 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199704200758.RAA15759@godzilla.zeta.org.au>
To: jwd@unx.sas.com, nate@mt.sri.com
Subject: Re: Install locks on HP Vectra XU
Cc: current@freefall.freebsd.org
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>    I've attempted to install from both the 2.2.1-RELEASE and
>> 3.0-CURRENT boot floppies. The boot process locks up with the
>> cursor in the lower left corner of the screen just before the
>> 1st screen would appear.
>
>Set the npx0 flags to 0x1, which is the default now on the 2.2 branch.

This problem is known to be a syscons or h/w bug on at least one
IBM portable.  You can also hang the system by writing to the frame
buffer using `fistpq' in user mode.  Fortunately, normal permissions on
/dev/ttyv0 prevent the world from writing to the frame buffer (`mesg y'
gives write permission, but both read and write permission are required
for mmap).

Bruce