From owner-freebsd-questions@FreeBSD.ORG Sun Jul 29 14:14:09 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 2A2EC16A41A for ; Sun, 29 Jul 2007 14:14:09 +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 037CC13C4A6 for ; Sun, 29 Jul 2007 14:14:08 +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 l6TEE5Hv094367; Sun, 29 Jul 2007 07:14:06 -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 l6TEE5Na094364; Sun, 29 Jul 2007 07:14:05 -0700 (PDT) (envelope-from chris@chrismaness.com) X-Authentication-Warning: ns1.kq6up.org: chris owned process doing -bs Date: Sun, 29 Jul 2007 07:14:05 -0700 (PDT) From: Chris Maness X-X-Sender: chris@ns1.kq6up.org To: Adam J Richardson In-Reply-To: <46AC95D3.5060008@crackmonkey.us> Message-ID: <20070729070957.L94300@ns1.kq6up.org> References: <20070727190640.J15421@ns1.kq6up.org> <46AAA9FD.20706@crackmonkey.us> <46AAAC79.309@chrismaness.com> <46AABA18.7080205@u.washington.edu> <20070728095154.I11066@ns1.kq6up.org> <46AC95D3.5060008@crackmonkey.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Garrett Cooper , FreeBSD List 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: Sun, 29 Jul 2007 14:14:09 -0000 > >> >> 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 >> _______________________________________________ > > Perhaps the mouse is dead or dying? Mine keeps its USB cable on a little > spindle, and to unreel the cable you have to tug on the cable. Not the best > design since the cable is very thin and has taken damage over time. > > Adam J Richardson > The mouse is working well on another system. Did you try my little experiment? Chris Maness