From owner-freebsd-bugs  Sun Feb  9 19:35:48 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA04471
          for bugs-outgoing; Sun, 9 Feb 1997 19:35:48 -0800 (PST)
Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA04466
          for <bugs@freebsd.org>; Sun, 9 Feb 1997 19:35:41 -0800 (PST)
Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id VAA06325 for <bugs@freebsd.org>; Sun, 9 Feb 1997 21:35:03 -0600
Message-Id: <3.0.1.32.19970209213501.006b97fc@bugs.us.dell.com>
X-Sender: tony@bugs.us.dell.com
X-Mailer: Windows Eudora Light Version 3.0.1 beta 12 (32)
Date: Sun, 09 Feb 1997 21:35:01 -0600
To: bugs@freebsd.org
From: Tony Overfield <tony@dell.com>
Subject: re: Stuck! 2.2 Gamma won't go.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I previously said:
>I'm attempting to do a test install of 2.2-gamma on a system
>with a PS/2 style Microsoft mouse.

The install is ruined.  I'll have to turn off the system.  In my
frustration, I furiously pounded enough random keys to get back 
to the blue text screen (console) which says, 

"Press [Enter] to switch to graphics mode.  

This make take a while..."

But it's now stuck here.

>It seems to have the classical
>"crazy mouse" problem, where the mouse data packets are out of 
>phase (mouse moves only along top and left edges of screen).

It has been suggested to me that the keyboard handler is 
confused by incoming mouse data.  This just can't be true. 
(Yes, I know the 8042 does both, but since it does them both 
"correctly", this can only be a driver bug.)

What's the magic secret key to un-confuse the keyboard driver?

Tony