From owner-freebsd-questions@FreeBSD.ORG Sat Apr 17 11:26:55 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2598216A4CE for ; Sat, 17 Apr 2004 11:26:55 -0700 (PDT) Received: from neverwhere.in-flux.org (neverwhere.in-flux.org [65.103.12.250]) by mx1.FreeBSD.org (Postfix) with SMTP id 7090043D4C for ; Sat, 17 Apr 2004 11:26:54 -0700 (PDT) (envelope-from talon@neverwhere.in-flux.org) Received: (qmail 89665 invoked by uid 1100); 17 Apr 2004 18:26:53 -0000 Resent-From: talon@in-flux.org Resent-Date: Sat, 17 Apr 2004 13:26:53 -0500 Resent-Message-ID: <20040417182653.GK76250@neverwhere.in-flux.org> Resent-To: freebsd-questions@freebsd.org Date: Sat, 17 Apr 2004 13:23:21 -0500 From: "10,000 Screaming Monkeys" To: Mark Ovens Message-ID: <20040417182321.GJ76250@neverwhere.in-flux.org> References: <20040417014400.GI76250@neverwhere.in-flux.org> <4081634F.10609@ukug.uk.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4081634F.10609@ukug.uk.freebsd.org> User-Agent: Mutt/1.5.6i Subject: Re: Microsoft wireless mouse problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Apr 2004 18:26:55 -0000 On 04/17, Mark Ovens rearranged the electrons to read: > Ah, now that _does_ WFM, and that fact makes me suspect that the > problem lies with the USB driver rather than the mouse driver. > > What are your mouse settings in rc.conf and XFree86config? At the moment, all I have in /etc/rc.conf is: usbd_enable="YES" moused_type="auto" That seems to detect the mouse properly and starts moused with the correct port. /etc/X11/XF86Config is: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" EndSection I've also tried killing moused and pointing the Device to /dev/ums[01], but that didn't seem to make a difference. > I really think it would be worth getting this problem solved as MS > cordless mice are very popular. They're not only popular, they're almost the only thing you can buy anymore. I wanted a corded keyboard and mouse for work, but the only models manufacturers put out with cords anymore (for keyboards, anyhow), if they sell one at all (Are you listening, Logitech? You bastards...) feel like crap to type on. But this isn't the place for that rant. Also, to address Lucas Holt's comment, the keyboard & mouse combo I'm trying to get working at work is the infrared model. I have the Bluetooth model keyboard/mouse at home, but it's not connected to a BSD box. I'm still puzzled why the wireless keyboard would work fine, but the wireless mouse, which uses the same receiver, doesn't. -Jamie