From owner-freebsd-questions@FreeBSD.ORG Sat Jul 28 17:10:08 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 376A416A4A0 for ; Sat, 28 Jul 2007 17:10:08 +0000 (UTC) (envelope-from chris@chrismaness.com) Received: from ns1.kq6up.org (adsl-76-238-148-145.dsl.irvnca.sbcglobal.net [76.238.148.145]) by mx1.freebsd.org (Postfix) with ESMTP id 98F8013C465 for ; Sat, 28 Jul 2007 17:10:02 +0000 (UTC) (envelope-from chris@chrismaness.com) Received: from ns1.kq6up.org (localhost.kq6up.org [127.0.0.1]) by ns1.kq6up.org (8.13.8/8.13.6) with ESMTP id l6SGtbFB031237; Sat, 28 Jul 2007 09:55:38 -0700 (PDT) (envelope-from chris@chrismaness.com) Received: from localhost (chris@localhost) by ns1.kq6up.org (8.13.8/8.13.6/Submit) with ESMTP id l6SGtbto031234; Sat, 28 Jul 2007 09:55:37 -0700 (PDT) (envelope-from chris@chrismaness.com) X-Authentication-Warning: ns1.kq6up.org: chris owned process doing -bs Date: Sat, 28 Jul 2007 09:55:36 -0700 (PDT) From: Chris Maness X-X-Sender: chris@ns1.kq6up.org To: Garrett Cooper In-Reply-To: <46AABA18.7080205@u.washington.edu> Message-ID: <20070728095154.I11066@ns1.kq6up.org> References: <20070727190640.J15421@ns1.kq6up.org> <46AAA9FD.20706@crackmonkey.us> <46AAAC79.309@chrismaness.com> <46AABA18.7080205@u.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD List , Adam J Richardson Subject: Re: USB Mouse not Working X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jul 2007 17:10:08 -0000 > Chris Maness wrote: >> Adam J Richardson wrote: >>> Chris Maness wrote: >>>> I am having issues getting my USB mouse running. I don't get any error >>>> messages of the sort, and when I do #cat /dev/ums0 I don't get any funny >>>> garbage like I normally do out of a IO device. (That is after I kill >>>> moused). >>>> >>>> Any suggestions? >>> >>> I had this. I had to start some daemon before starting X... what was it >>> now... devd? usbd? psmd? moused? Something like that, anyway. And I had to >>> specify the "mouse port" IIRC. You know, something like "moused -p >>> /dev/ums0". >>> >>> Adam J Richardson >> I tried that, but I get nothing. Should I expect to see garbage from #cat >> /dev/sysmouse and then move the mouse around? Can you do that in console >> mode, and see if that gives you anything? >> >> Chris Maness > > moused(1) with usbd(1). Don't forget to compile uhid, ums, and all other > dependent drivers into the kernel, either statically or as modules (man ums, > uhid will get you on your way here). > > Try moused with auto detection, using /dev/ums0. If you don't see anything > about a USB mouse being attached in dmesg, you don't have the right drivers > compiled for your kernel. If you do, moused / usbd hasn't been setup yet. > > cat /dev/sysmouse will yield you the info you seek in the end, but you > should try /dev/ums0 first, because that will work regardless of whether or > not moused is started. > > Good luck :), > -Garrett > The mouse seems to get detected perfectly and this is the GENERIC kernel build that has the modules. The mouse gets detected and listed at boot time. However, I don't think I am getting data out of the mouse port. I beleive in the past I have checked with #cat /dev/ums0 and if things are working corectly, cat display binary garbage on the screen when you wiggle the mouse. Try this after killing moused (moused makes ums0 unavailable). Chris Maness