From owner-freebsd-bluetooth@FreeBSD.ORG Mon Mar 14 21:17:46 2011 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87CAC1065670 for ; Mon, 14 Mar 2011 21:17:46 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 13D338FC0C for ; Mon, 14 Mar 2011 21:17:45 +0000 (UTC) Received: by fxm11 with SMTP id 11so3908797fxm.13 for ; Mon, 14 Mar 2011 14:17:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PL7f8as9kcba6hnQ4mBDbf6HYUNglcGpLHhRA0DfGsQ=; b=DjvuylDhnDrtMuOKGt0yHe5EE936i7WNFW9VDUujrv3KTDC0/vwRgpp6xJFcDJYKZs K/CXDGYn7m7fkZQuJSvm8FuXOXyPR3LDBuu8TbWl0Vm8ITcdrJnoLH6qonjHg00OEkaq g1EozWJFsI7kmUIV8GxBf6tYwqtOzj+9pQ/hE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=U0dvXQJ59Ntt5cpwH30Ulkml5m+d2m1rNaxgpHC8jBAVy1V9Hd7etEiwJ9Vd9+mCr+ iFdBvM67MqJPhxdd8Nr24cdMGzaxLL7NSVYnCF8iE4WW/B9lNor1UwhY0DLdtL/NDeSj pRiUFxIZkURxmyrqnW8ewZLQ3BcpJUo4CCvO4= Received: by 10.223.2.205 with SMTP id 13mr2489344fak.138.1300135424014; Mon, 14 Mar 2011 13:43:44 -0700 (PDT) Received: from Melon.malikania.fr (65.21.102-84.rev.gaoland.net [84.102.21.65]) by mx.google.com with ESMTPS id n1sm71854fam.16.2011.03.14.13.43.40 (version=SSLv3 cipher=OTHER); Mon, 14 Mar 2011 13:43:41 -0700 (PDT) Message-ID: <4D7E7DBE.7080601@gmail.com> Date: Mon, 14 Mar 2011 21:42:38 +0100 From: David Demelier User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110306 Thunderbird/3.1.9 MIME-Version: 1.0 To: Maksim Yevmenkin References: <4D36ED39.7070807@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth mouse does not connect after reboot 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, 14 Mar 2011 21:17:46 -0000 On 23/01/2011 03:32, Maksim Yevmenkin wrote: > On Sat, Jan 22, 2011 at 11:07 AM, David DEMELIER > wrote: >> 2011/1/19 David Demelier: >>> Hello, >>> >>> I've successfully setup a Logitech v470 mouse using bthidd / hcsecd. The >>> problem is each time /var/db/bthidd.hids is created the mouse does not >>> connect anymore and if I remove this file and restart bthidd it works, thing >>> which is quite boring. >>> >>> In hcsecd.conf I have : >>> >>> device { >>> bdaddr 00:1f:20:0f:62:31; >>> name "Logitech V470"; >>> key nokey; >>> pin "0000"; >>> } >>> >>> and in bthidd.conf : >>> >>> device { >>> bdaddr 00:1f:20:0f:62:31; >>> control_psm 0x11; >>> interrupt_psm 0x13; >>> reconnect_initiate true; >>> battery_power true; >>> normally_connectable false; >>> hid_descriptor { >>> 0x05 0x01 0x09 0x02 0xa1 0x01 0x85 0x02 >>> 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 >>> 0x29 0x08 0x15 0x00 0x25 0x01 0x75 0x01 >>> 0x95 0x08 0x81 0x02 0x05 0x01 0x09 0x30 >>> 0x09 0x31 0x16 0x01 0xf8 0x26 0xff 0x07 >>> 0x75 0x0c 0x95 0x02 0x81 0x06 0x09 0x38 >>> 0x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x01 >>> 0x81 0x06 0x05 0x0c 0x0a 0x38 0x02 0x75 >>> 0x08 0x95 0x01 0x81 0x06 0xc0 0xc0 0x06 >>> 0x00 0xff 0x09 0x01 0xa1 0x01 0x85 0x10 >>> 0x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff >>> 0x00 0x09 0x01 0x81 0x00 0x09 0x01 0x91 >>> 0x00 0xc0 >>> }; >>> } >>> >>> If you have any clue how to fix this. Thanks. >>> >>> -- >>> David Demelier >>> >> >> I'm sad, it seems I cannot setup my bluetooth mouse for two computer. >> Maybe the mouse save the "known" bluetooth dongle so it doesn't attach >> to an other computer "unknown" > > yes, that is how it usually works. "connect" button puts mouse into > "paring" mode where it "pairs" with a particular host. after "pairing" > is complete, mouse will connect to the same host and will not accept > connections from other hosts. the same (well almost the same) > situation is with bluetooth headsets. "almost" here means that the > some headsets can "remember" multiple (usually about 5) hosts. the > logic is to connect to the last known/active one, and if it fails, try > others in order. i'm guessing your mouse can only "remember" one host. > i'm afraid there is nothing can be done here. except "re-pairing" > (i.e. pressing connect button) mouse to each host every time you > switch computers. > > thanks, > max Hello Maksim, Sorry to talk about this again, but If it's possible I found a solution: Can we set a fake mac address for the bluetooth nic? For example, if I use the same mac address on my laptop and my desktop it will try to pair it so I just need to connect my mouse to it :) But I don't know how to change the mac address... Cheers, -- David Demelier