From owner-freebsd-hardware  Fri Jun  6 13:35:31 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA10247
          for hardware-outgoing; Fri, 6 Jun 1997 13:35:31 -0700 (PDT)
Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA10240
          for <hardware@freebsd.org>; Fri, 6 Jun 1997 13:35:27 -0700 (PDT)
Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by sparkie.gnofn.org (8.7.Beta.10/8.7.Beta.10) with SMTP id PAA20089 for <hardware@freebsd.org>; Fri, 6 Jun 1997 15:35:10 -0500 (CDT)
Date: Fri, 6 Jun 1997 15:35:10 -0500 (CDT)
From: Craig Johnston <craig@gnofn.org>
To: hardware@freebsd.org
Subject: psm0 problems
Message-ID: <Pine.GSO.3.95.970606152829.19262A-100000@sparkie.gnofn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I'm using a Mousesystems optical mouse plugged into the ps/2 port of
my ABIT IT5H mobo.  Kernel is FreeBSD 2.2-stable cvsup'd yesterday, June
5.  

Problem is, when psm0 is enabled, I just hang at the check for it.
I enabled the debugging info, I get this during boot:

psm0: current command byte:0047
kbdio: new command byte:0054 (set controller...)
kbdio: TEST_AUX_PORT status:0000

and then we hang.  

I had the same problem previously, but sometimes if I played with
the mouse as the system came up I was able to get it detected and working
fine.  Apparently not so anymore.

Any clues?

regards,
Craig.