From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jun 20 21:22:33 2005 Return-Path: X-Original-To: bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67E2C16A41C for ; Mon, 20 Jun 2005 21:22:33 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CF2443D48 for ; Mon, 20 Jun 2005 21:22:33 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id ABEE919F3B; Mon, 20 Jun 2005 14:24:09 -0700 (PDT) From: "Darren Pilgrim" To: "'Maksim Yevmenkin'" , Date: Mon, 20 Jun 2005 14:22:33 -0700 Message-ID: <001d01c575de$2c821800$0b2a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <42B72DC4.2090104@savvis.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Importance: Normal Cc: 'bluetooth' Subject: RE: Problem with Logitech Mx900 again X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2005 21:22:33 -0000 > From: Maksim Yevmenkin > > It does not work in bot WinXP and FreeBSD (works for both=20 > > before), but it still works with native cradle. >=20 > what do you mean with native cradle? is it some sort of wired=20 > interface? bluetooth usb receiver? or bluetooth usb receiver > which os detects as usb mouse (i.e. bluetooth usb receiver with > hid proxy feature activated)? He would be talking about the bluetooth receiver charging base that comes with the MX900. It proxies Logitech bluetooth mice and keyboards as usb devices. > from what i can see, it looks like the mouse does not like new host.=20 > most hid devices will "lock" on the first device that contacted it. > that is why you need to "reset" the mouse to make sure it "forgets" > about previous host. I use my MX900 and Targus mice in both FreeBSD and Windows XP. Rebooting back an forth doesn't break the connection to either. I would guess that the MX900 is sensitive only to the hardware address, since both OSes use my notebook's internal bluetooth receiver. I have found, however, that something does get broken if use bthidd with Windows XP hibernated. When I bring Windows XP back out of hibernation, I have to have the machine search for devices to clear the stale connection, then push the connect button on the mouse, search again and manually reconnect the mouse. > another thing you could try to do is to force paring between=20 > the mouse and pc. you need to know default pin-code for the mouse. > check the manual to see if its there, if not - try "0000" - four > zeros. The MX900 doesn't support pin-based pairing AFAIK. It "auto-pairs" by remembering the last host to which it was connected and restores the connection whenever the host shows up.