From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 14:15:33 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C98716A41C for ; Fri, 10 Jun 2005 14:15:33 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from olive.qinip.net (olive.qinip.net [62.100.30.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4014E43D49 for ; Fri, 10 Jun 2005 14:15:33 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (h8441134153.dsl.speedlinq.nl [84.41.134.153]) by olive.qinip.net (Postfix) with SMTP id 6CD6A18426 for ; Fri, 10 Jun 2005 16:15:29 +0200 (MEST) Received: (qmail 17710 invoked from network); 10 Jun 2005 14:15:30 -0000 Received: from unknown (HELO localhost) (10.0.1.4) by ronald.echteman.nl with SMTP; 10 Jun 2005 14:15:30 -0000 In-Reply-To: <42A997E2.1060903@satro.sk> References: <42A997E2.1060903@satro.sk> To: "freebsd-stable@freebsd.org" Message-ID: From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Fri, 10 Jun 2005 16:15:28 +0200 User-Agent: Opera M2/8.0 (FreeBSD, build 1095) Subject: Re: Microsoft USB Wireless Mouse not working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 14:15:33 -0000 On Fri, 10 Jun 2005 15:38:42 +0200, Michal Vanco wrote: > Hi, > > I'm running 5.4-STABLE and I'm not able to get my MS USB Wireless mouse > working. > After plugging the mouse I see this in my dmesg: > uhid0: Microsoft Microsoft USB Wireless Mouse, rev 2.00/0.17, addr 2, > iclass 3/1 > > But there is no ums device. I have "device ums" in kernel. > > Is there any patch available to get this working? Do you also have 'uhid' in your kernel or loaded as a module? Maybe it attaches before ums. If yes, try removing it from your kernel and boot again. This is just a thought, so maybe it doesn't work. Ronald. -- Ronald Klop Amsterdam, The Netherlands