From owner-freebsd-hardware  Thu Apr  4 11:34:37 2002
Delivered-To: freebsd-hardware@freebsd.org
Received: from postal1.es.net (postal1.es.net [198.128.3.205])
	by hub.freebsd.org (Postfix) with ESMTP id BFB6B37B41A
	for <hardware@freebsd.org>; Thu,  4 Apr 2002 11:34:33 -0800 (PST)
Received: from ptavv.es.net ([198.128.4.29])
        by postal1.es.net (Postal Node 1) with ESMTP id GQF37091
        for <hardware@freebsd.org>; Thu, 04 Apr 2002 11:34:32 -0800
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Postfix) with ESMTP id EBACA5D05
	for <hardware@freebsd.org>; Thu,  4 Apr 2002 11:34:31 -0800 (PST)
To: hardware@freebsd.org
Subject: Mouse problems
Date: Thu, 04 Apr 2002 11:34:31 -0800
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20020404193431.EBACA5D05@ptavv.es.net>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-hardware.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-hardware>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-hardware>
X-Loop: FreeBSD.org

I recently purchased a cheap PC Concepts optical mouse for my FreeBSD
desktop system. It seems to work fine with Windows. I just plugged it
in and it worked. But no such luck for FreeBSD.

On FreeBSD, motion up or to the right is fine with the cursor tracking
mouse movement in any combination of these directions. Any movement
down causes the cursor to jump to the bottom of the screen and any
movement to the left causes the cursor to jump to the left edge of the
screen.

I have also tried the mouse on my ThinkPad with identical results.

These symptoms apply to most device selections, but "Auto" is even
worse, with erratic motion and garbage characters appearing in the
syscons.

I asked about this on questions and only received responses from other
who had seen the same problems.

Is this a known problem and is there any fix/work-around? I feel a
kernel debug session coming and I'd love to avoid it.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634

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