From owner-freebsd-usb@FreeBSD.ORG Fri Jan 19 17:36:04 2007 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AF54716A401 for ; Fri, 19 Jan 2007 17:36:04 +0000 (UTC) (envelope-from nemox@deathwish.net) Received: from mail.math.fsu.edu (mail.math.fsu.edu [128.186.104.32]) by mx1.freebsd.org (Postfix) with ESMTP id 560B613C4C4 for ; Fri, 19 Jan 2007 17:36:04 +0000 (UTC) (envelope-from nemox@deathwish.net) Received: from [128.186.104.245] (mac245 [128.186.104.245]) by mail.math.fsu.edu (8.13.8/8.13.8) with ESMTP id l0JHa2Ff018571 for ; Fri, 19 Jan 2007 12:36:03 -0500 (EST) Message-ID: <45B1017D.7050602@deathwish.net> Date: Fri, 19 Jan 2007 12:35:57 -0500 From: Andrew Tamm User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: freebsd-usb@freebsd.org References: <45B06B45.1080300@deathwish.net> <200701191106.51206.hselasky@c2i.net> <45B0E96D.3020002@deathwish.net> <200701191706.31322.hselasky@c2i.net> In-Reply-To: <200701191706.31322.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: no data from USB wireless mouse X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2007 17:36:04 -0000 Hans Petter Selasky wrote: > On Friday 19 January 2007 16:53, Andrew Tamm wrote: >> Hans Petter Selasky wrote: >>>> I am having no success at all in getting a Microsoft Optical Wireless >>>> Desktop Pro mouse to work in FreeBSD 6.2-RC2. >>>> >>>> The kernel sees it as: >>>> ums0: Microsoft Microsoft Wireless Optical Desktop >>>> ums0: 5 buttons and Z dir and a TILT dir. >>>> >>>> cat /dev/usm0 gives no data, no matter what buttons are pushed on the >>>> mouse. >>>> >>>> After looking online, I saw a few things to try, the first of which to >>>> recompile the kernel with USB_dEBUG option enabled. After doing this, >>>> and cranking hw.usb.usm.debug up to 10, I still can get nothing out of >>>> the usm0, however, typing cat /dev/usm0 and then hitting ^C gives this >>>> following message: (note the system has been rebooted with a second >>>> wired mouse attached at usm0, so the offending device has moved to usm1 >>>> ) >>>> >>>> ums_intr: sc=0xc50bf000 status=6 >>>> ums_intr: data = 00 00 00 00 00 00 >>> Could you try my new USB stack: >>> >>> # You need /usr/ports/devel/subversion installed >>> >>> svn --username anonsvn --password anonsvn \ >>> checkout svn://svn.turbocat.net/i4b >>> # >>> # The following commands will >>> # install the driver on FreeBSD: >>> # >>> cd i4b/trunk/i4b/FreeBSD.usb >>> make S=../src package >>> make install >>> >>> When the kernel is built, enable the ums debug sysctl. Set it to 15. Then >>> repeat your tests, if the mouse doesn't work. >>> >>> --HPS >> Done, now i'm not getting the status=6 when I cat the usm1, and the mouse >> still does not work. ''ums_open'' appears when you cat the usm1, but >> nothing else on mouse move or click. The other wired mouse ( also an >> Intellimouse ) giving a copius amount of data though. Could the MS >> wireless require some init code to be sent? I've seen that they will work >> using a PS/2 adaptor, but that seems messy and improper. >> > > Markus Brueffer is working on some HID parsing improvements. Maybe that will > fix it. > > But could you have run "sysctl hw.usb.ums.debug=15". Then plug your mouse, > open /dev/umsX, and then move the mouse around a little bit. Do you get any > messages? > > --HPS > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" I did that, although I already had the mouse plugged in before I tried to cat the device. I'll get the plug in messages this evening. Is there a way to have something sort-of waiting for the device to appear in /dev. Something like a cat, but that will automatically open the device as soon as it appears? Andrew