From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 25 13:07:07 2008 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 744D316A41B; Fri, 25 Jan 2008 13:07:07 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id 34A1313C442; Fri, 25 Jan 2008 13:07:06 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id F35A543C7E8; Fri, 25 Jan 2008 14:35:32 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U+bqaw3BMn7I; Fri, 25 Jan 2008 14:35:32 +0200 (EET) Received: from [10.2.1.87] (gateway.cybervisiontech.com.ua [88.81.251.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 5955A43C6D6; Fri, 25 Jan 2008 14:35:32 +0200 (EET) Message-ID: <4799D78F.6000405@icyb.net.ua> Date: Fri, 25 Jan 2008 14:35:27 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20080123) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: mikeh@FreeBSD.org, yokota@freebsd.org Subject: mouse problems X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 13:07:07 -0000 I've recently got a cheap PS/2 mouse A4 Tech OP-3D: http://www.a4tech.com/EN/product2.asp?CID=114&SCID=115&MNO=OP-3D It looks like your regular mouse with a combined middle-button/scroll-wheel. The only unusual feature is an additional button for "double-click" - I am not sure if it's simulated within the mouse itself or if it is reported to controller/driver. There is a problem with this mouse though: if I don't do anything special then this mouse acts very erratically and misbehaves all it can - movements are ignored or reported as button clicks, button clicks get reported as movements or clicks of different buttons, etc. One cure that I initially found was to kill moused, disconnect and reconnect the mouse and restart moused, after that moused worked well. Then, I found out that I could achieve the same if I specify 0x200 flag (no id probing). Judging from verbose dmesg the mouse is detected as a generic ps/2 mouse with or without this flag, there is no difference whatsoever. So it seems that probing for various mouse models somehow hoses this mouse. Question #1: maybe some kind of additional mouse reset should be performed after all probes failed and we settle on generic? Well, while flag 0x200 makes the mouse behave reasonably, it seems that the presence of the wheel is not detected (or mouse is configured to ignore it?), so I can not use it. Question #2: what are the further steps to debug this issue so that this mouse is properly recognized? I really would like to get the wheel working. I can provide any additional information needed. Thank you. -- Andriy Gapon