From owner-freebsd-bugs  Tue Feb  6 06:16:39 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA04427
          for bugs-outgoing; Tue, 6 Feb 1996 06:16:39 -0800 (PST)
Received: from UConnVM.UConn.Edu (uconnvm.uconn.edu [137.99.26.3])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA04412
          for <bugs@FreeBSD.org>; Tue, 6 Feb 1996 06:16:36 -0800 (PST)
Received: from ruddles.stat.uconn.edu by UConnVM.UConn.Edu (IBM VM SMTP V2R2)
   with TCP; Tue, 06 Feb 96 09:16:29 EST
Received: from marstons.stat.uconn.edu by ruddles.stat.uconn.edu (4.1/SMI-4.1)
	id AA09674; Tue, 6 Feb 96 09:12:05 EST
Date: Tue, 6 Feb 96 09:12:04 EST
From: jeff@stat.uconn.edu (Jeffrey M. Metcalf)
Message-Id: <9602061412.AA09674@ruddles.stat.uconn.edu>
To: bugs@FreeBSD.org
Subject: PS/2 Mouse
Sender: owner-bugs@FreeBSD.org
Precedence: bulk


Hi,

I recently recompiled a custom kernel by adding the line:

device   psm0   at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr


I removed all conflicts with my PS/2 mouse and the kernel boots fine and
detects my mouse.  I added the dev psm0.  But after I rebooted the 
second time (after editing out the conflicts), my keyboard froze up
just like I was warned it could.  Unfortunately pressinf the numlock
key multiple times during the bootup process didn't help (unless I am
not doing it correctly).  Any other fixes short of buying a microsoft
mouse?  The fix would have to be as simple as possible since I have
no experience building drivers or anything of that sort.

Thanks,

J. Metcalf