From owner-freebsd-current@FreeBSD.ORG Sun Jun 19 22:47:00 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1330316A41C; Sun, 19 Jun 2005 22:47:00 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F14A943D48; Sun, 19 Jun 2005 22:46:59 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id BA1D972DD4; Sun, 19 Jun 2005 15:46:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id B545E72DCB; Sun, 19 Jun 2005 15:46:59 -0700 (PDT) Date: Sun, 19 Jun 2005 15:46:59 -0700 (PDT) From: Doug White To: Ade Lovett In-Reply-To: <42AFE83B.9050305@FreeBSD.org> Message-ID: <20050619154633.Y83634@carver.gumbysoft.com> References: <42AFE83B.9050305@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: current@FreeBSD.org Subject: Re: USB mouse woes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jun 2005 22:47:00 -0000 On Wed, 15 Jun 2005, Ade Lovett wrote: > Microsoft wireless USB mouse is completely non-responsive after boot. > Moving the mouse will produce a mouse cursor on syscons, but no movement > is observed. Same mouse operates successfully on Ubuntu Linux 5.04 and > Windows XP, and also under FreeBSD with a USB-PS/2 adapter (via psm) > > System info: > > MSI KT800 Neo, VIA chipset > > FreeBSD 6.0-CURRENT #0: Wed Jun 15 01:00:33 PDT 2005 > root@nail.lovett.com:/usr/obj/work/src.6/sys/NAIL > [...] > CPU: AMD Athlon(tm) 64 Processor 2800+ (1800.07-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xfc0 Stepping = 0 > [...] > uhci0: port 0xc400-0xc41f irq 21 at device > 16.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > [...] > [repeat for usb1, usb2, usb3] > [...] > usb4: EHCI version 1.0 > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > usb4: on ehci0 > usb4: USB revision 2.0 > uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub4: 8 ports with 8 removable, self powered > [...] > ums0: Microsoft Microsoft Wireless Optical Mouse\M-. 1.0A, rev > 2.00/0.17, addr 2, iclass 3/1 > ums0: 3 buttons and Z dir. > [...] > > "NAIL" kernel config is merely GENERIC with un-needed drivers. Makes no > difference for any combinations of (uhci,ehci,usb,ums) compiled in to > the kernel, or as modules with appropriate loader.conf magic. > > usbd is running (via /etc/rc.conf), and the appropriate moused on > /dev/ums0 is also running. > > crw-r--r-- 1 root operator 7, 82 Jun 15 01:15 /dev/ums0 > > Any suggestions on further places to look to get the mouse working > appreciated. Running under a base install of ports/x11/xorg reveals > similar breakage, both either via the SysMouse protocol, or direct > talking to /dev/ums0 as a USB mouse without usbd (and moused) running. > > A quick look through the archives reveals a few other reports of similar > issues, but no resolution. > > Ideas? Compile with USB_DEBUG and ratchet up the ums debug level and see what movement deltas are coming off the device. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org