From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jan 23 02:32:40 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 EE8CB106566C for ; Sun, 23 Jan 2011 02:32:39 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id B38808FC14 for ; Sun, 23 Jan 2011 02:32:39 +0000 (UTC) Received: by iyb26 with SMTP id 26so3001620iyb.13 for ; Sat, 22 Jan 2011 18:32:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=IiRIewPb0Ywt9vq9auBVpx/tuUG3K0VxMa48JqO402k=; b=XcZ3wlPsTBmvnOLAHocCZdLhQMGVZG9hjx82IWRDQA8S2p0L9i1hFKmwKwVmx/TyRC xlvum6Jw0bZ59r8xIHF0Egs6qNDvBy61h1dRvGldSZ69trp2fLxYzXKh1fKd0sL25jyF WLqMyzViMCWs9Pu0EBa+RcIyfuGXPgSc7H+6U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=O7VrwqbCn00gtcn0DSx8cIE/W45AF1Z9kzw0IiL3gNwtSI0p4U99aS+EvUOaoBe9yP 7y5rxjEbTkic3/E0Z98ACFnWoyW11h4ga92k4VqUwPWIUt2wspar2BRpdDR+iITkJkg0 feBuRpxVsxmYW0Dns+3mM08Gsk8Uhmf0Pm7vI= MIME-Version: 1.0 Received: by 10.231.31.6 with SMTP id w6mr2855155ibc.160.1295749959023; Sat, 22 Jan 2011 18:32:39 -0800 (PST) Received: by 10.231.208.19 with HTTP; Sat, 22 Jan 2011 18:32:38 -0800 (PST) In-Reply-To: References: <4D36ED39.7070807@gmail.com> Date: Sat, 22 Jan 2011 18:32:38 -0800 Message-ID: From: Maksim Yevmenkin To: David DEMELIER Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Sun, 23 Jan 2011 02:32:40 -0000 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, t= hing >> which is quite boring. >> >> In hcsecd.conf I have : >> >> device { >> =A0 =A0 =A0 =A0bdaddr =A000:1f:20:0f:62:31; >> =A0 =A0 =A0 =A0name =A0 =A0"Logitech V470"; >> =A0 =A0 =A0 =A0key =A0 =A0 nokey; >> =A0 =A0 =A0 =A0pin =A0 =A0 "0000"; >> } >> >> and in bthidd.conf : >> >> device { >> =A0 =A0 =A0 =A0bdaddr =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A000:1f:20:0f:62:= 31; >> =A0 =A0 =A0 =A0control_psm =A0 =A0 =A0 =A0 =A0 =A0 0x11; >> =A0 =A0 =A0 =A0interrupt_psm =A0 =A0 =A0 =A0 =A0 0x13; >> =A0 =A0 =A0 =A0reconnect_initiate =A0 =A0 =A0true; >> =A0 =A0 =A0 =A0battery_power =A0 =A0 =A0 =A0 =A0 true; >> =A0 =A0 =A0 =A0normally_connectable =A0 =A0false; >> =A0 =A0 =A0 =A0hid_descriptor =A0 =A0 =A0 =A0 =A0{ >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x05 0x01 0x09 0x02 0xa1 0x01 0x85 0x02 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x29 0x08 0x15 0x00 0x25 0x01 0x75 0x01 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x95 0x08 0x81 0x02 0x05 0x01 0x09 0x30 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x09 0x31 0x16 0x01 0xf8 0x26 0xff 0x07 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x75 0x0c 0x95 0x02 0x81 0x06 0x09 0x38 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x15 0x81 0x25 0x7f 0x75 0x08 0x95 0x01 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x81 0x06 0x05 0x0c 0x0a 0x38 0x02 0x75 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x08 0x95 0x01 0x81 0x06 0xc0 0xc0 0x06 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x00 0xff 0x09 0x01 0xa1 0x01 0x85 0x10 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x75 0x08 0x95 0x06 0x15 0x00 0x26 0xff >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x00 0x09 0x01 0x81 0x00 0x09 0x01 0x91 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00x00 0xc0 >> =A0 =A0 =A0 =A0}; >> } >> >> 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 From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jan 23 11:25:16 2011 Return-Path: Delivered-To: freebsd-bluetooth@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9D4D1065672; Sun, 23 Jan 2011 11:25:16 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 802138FC12; Sun, 23 Jan 2011 11:25:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p0NBPGED023629; Sun, 23 Jan 2011 11:25:16 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0NBPFJG023625; Sun, 23 Jan 2011 11:25:15 GMT (envelope-from arundel) Date: Sun, 23 Jan 2011 11:25:15 GMT Message-Id: <201101231125.p0NBPFJG023625@freefall.freebsd.org> To: alexbestms@wwu.de, arundel@FreeBSD.org, freebsd-bluetooth@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: kern/140590: [bluetooth] ng_ubt(4) ng_l2cap_process_cmd_rej warnings 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: Sun, 23 Jan 2011 11:25:16 -0000 Synopsis: [bluetooth] ng_ubt(4) ng_l2cap_process_cmd_rej warnings State-Changed-From-To: patched->closed State-Changed-By: arundel State-Changed-When: Sun Jan 23 11:20:03 UTC 2011 State-Changed-Why: The "ng_l2cap_process_cmd_rej"-issue was fixed in all supported branches. As Iain Hibbert revealed in his analaysis of the hcidump, the "ng_btsocket_rfcomm_receive_dm"-issue was cause by a device not sticking to bluetooth protocol standards. So this is not FreeBSD's fault and we defenately want to inform the user about any irregularities during the transfer. http://www.freebsd.org/cgi/query-pr.cgi?pr=140590 From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jan 23 11:30:15 2011 Return-Path: Delivered-To: freebsd-bluetooth@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B666106566B for ; Sun, 23 Jan 2011 11:30:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1A5798FC1F for ; Sun, 23 Jan 2011 11:30:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p0NBUE7q023954 for ; Sun, 23 Jan 2011 11:30:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0NBUEtt023950; Sun, 23 Jan 2011 11:30:14 GMT (envelope-from gnats) Date: Sun, 23 Jan 2011 11:30:14 GMT Message-Id: <201101231130.p0NBUEtt023950@freefall.freebsd.org> To: freebsd-bluetooth@FreeBSD.org From: Alexander Best Cc: Subject: Re: kern/140590: [bluetooth] ng_ubt(4) ng_l2cap_process_cmd_rej warnings X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexander Best List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2011 11:30:15 -0000 The following reply was made to PR kern/140590; it has been noted by GNATS. From: Alexander Best To: bug-followup@freebsd.org Cc: Iain Hibbert Subject: Re: kern/140590: [bluetooth] ng_ubt(4) ng_l2cap_process_cmd_rej warnings Date: Sun, 23 Jan 2011 11:19:54 +0000 the device is a mobile phone (samsung i550). from your analysis it appears that the device is not following standard protocol procedures. i think the _WARN should stay. turning it into a _INFO would introduce inconsistency with the other dlci related warnings. so i guess this PR can be closed. thanks for your in depth description of the problem. cheers. alex -- a13x