From owner-freebsd-hackers  Tue Mar  4 11:11:40 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id LAA08520
          for hackers-outgoing; Tue, 4 Mar 1997 11:11:40 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA08515
          for <freebsd-hackers@freebsd.org>; Tue, 4 Mar 1997 11:11:37 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA00389; Tue, 4 Mar 1997 12:07:57 -0700 (MST)
Date: Tue, 4 Mar 1997 12:07:57 -0700 (MST)
Message-Id: <199703041907.MAA00389@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Terry Lambert <terry@lambert.org>
Cc: slaterm@excel.tnet.com.au (Michael Slater), freebsd-hackers@freebsd.org
Subject: Re: PS2 Mouse on FreeBSD 2.1.5
In-Reply-To: <199703041725.KAA09986@phaeton.artisoft.com>
References: <Pine.LNX.3.91.970304173509.358A-100000@excel.tnet.com.au>
	<199703041725.KAA09986@phaeton.artisoft.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >       I am having trouble getting FreeBSD 2.1.5 to recognise my PS/2 mouse.
> > I'm using a normal Austek Pentium mb, with a built in PS/2 connector. I 
> > noticed that in the kernel, it defaults to IRQ 12, port 0x60 but when 
> > ever i boot up the machine, it gives me the message "psm0 not found on 0x60"
> > It seems to work fine in Windoze 95 however. So perhaps im using the 
> > wrong port ? Any suggestions would be appriciated!
> 
> You are confusing a PS/2 mouse (psm0 on port 0x60 of the keyboard
> controller) with a bus mouse (IRQ 12).

The PS/2 mouse uses IR 12 by default.  You are confused. :)

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

To answer the original poster's question, the PS/2 driver in 2.1.* was
completely re-written in 2.2, and works much better.  Unfortunately,
it's no trivial matter to port it back to 2.1, so if it doesn't work for
in 2.1.* there here is a suggestion.  Hard-code the probe to *always*
return true, and see if it works.  I did this on my ThinkPad's and it
worked fine.



Nate