From owner-freebsd-hackers  Fri Jun 26 11:44:53 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA05428
          for freebsd-hackers-outgoing; Fri, 26 Jun 1998 11:44:53 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05363;
          Fri, 26 Jun 1998 11:44:23 -0700 (PDT)
          (envelope-from bmcgover@bmcgover-pc.cisco.com)
Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1])
	by bmcgover-pc.cisco.com (8.8.8/8.8.8) with ESMTP id OAA00218;
	Fri, 26 Jun 1998 14:45:24 -0400 (EDT)
	(envelope-from bmcgover@bmcgover-pc.cisco.com)
Message-Id: <199806261845.OAA00218@bmcgover-pc.cisco.com>
To: questions@FreeBSD.ORG, hackers@FreeBSD.ORG
Reply-To: mcgovern@spoon.beta.com
Subject: PSM problem...
Date: Fri, 26 Jun 1998 14:45:23 -0400
From: Brian McGovern <bmcgover@bmcgover-pc.cisco.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Just got a new AL440LX motherboard that has a PS/2 mouse port that is acting
quirky. It works fine under Win95, but not under FreeBSD. I'm not sure whether
its a bad port, or whether its just a bad probe that we're doing. 

Anyhow, here is some -v output for people to take a peek at. If someone could
point me towards a patch for the psm driver, or make the statement 'bad 
motherboard', I'd appreciate it. I have others of the same type that seem to
work ok.
	-Brian


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message