From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 0BD45138A1F for ; Sun, 27 Apr 2014 03:15:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 60EA7E09B4; Sun, 27 Apr 2014 03:15:49 +0000 (UTC) Received: from icp-osb-irony-out4.external.iinet.net.au (icp-osb-irony-out4.external.iinet.net.au [203.59.1.220]) by pigeon.gentoo.org (Postfix) with ESMTP id EA428E0962 for ; Sun, 27 Apr 2014 03:15:44 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjgFABZ1XFM6B0c6/2dsb2JhbABZgwZPgzyoAQGZdoEKFnSCJQEBBSNmCw0LAgIFIQICDwJGEwgBAYg8DqZFo0YXgSmEMYgxDEkWglmBSgSJb48dgTqFIyiLWYM+MIEu X-IronPort-AV: E=Sophos;i="4.97,936,1389715200"; d="scan'208";a="321111176" Received: from unknown (HELO moriah.localdomain) ([58.7.71.58]) by icp-osb-irony-out4.iinet.net.au with ESMTP; 27 Apr 2014 11:15:42 +0800 Received: from localhost (localhost [127.0.0.1]) by moriah.localdomain (Postfix) with ESMTP id 90BEA4C15 for ; Sun, 27 Apr 2014 11:15:40 +0800 (WST) X-Virus-Scanned: amavisd-new at lan.localdomain Received: from moriah.localdomain ([127.0.0.1]) by localhost (moriah.lan.localdomain [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qdDeNY4oMOdj for ; Sun, 27 Apr 2014 11:14:54 +0800 (WST) Received: from [192.168.44.3] (moriah [192.168.44.3]) by moriah.localdomain (Postfix) with ESMTP id A497C50F0 for ; Sun, 27 Apr 2014 11:14:41 +0800 (WST) Message-ID: <535C7603.709@iinet.net.au> Date: Sun, 27 Apr 2014 11:14:11 +0800 From: William Kenworthy User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: bluez 5 not connecting References: <53578420.1040604@iinet.net.au> <535864DD.10204@iinet.net.au> <201404261933.16917.michaelkintzios@gmail.com> In-Reply-To: <201404261933.16917.michaelkintzios@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 644e0de0-b82f-4474-8fab-f76f8a78fe86 X-Archives-Hash: 0c7f2c35da88cebf2a9c16f2f3c3ef00 On 04/27/14 02:33, Mick wrote: > On Thursday 24 Apr 2014 02:11:57 William Kenworthy wrote: > >> I was able to get it working manually - gentoo's init scripts are out of >> date with bluez 5, blutoothctl is broken (or probably just poorly >> documented which equates to the same thing if the command doesn't work) . >> >> In bluetoothctl: >> power on >> scan on >> agent on >> default-agent >> pair >> trust >> exit >> >> In a shell: >> rfcomm bind rfcomm0 >> >> do serial port stuff with /dev/rfcomm0 >> >> rfcomm unbind rfcomm0 >> >> bluetoothctl connect command does not work - connects and immediately >> disconnects with an error >> gentoo's rfcomm initscript has removed the -f flag which bluez 5 does >> not have, but it also looks like the bind all in the 5.17 ebuild is also >> not supported by late bluez5 so it immediately exits and no rfcomm >> device is created. >> >> Ive adapted my python script to the changes now - but the pairing does >> not survive restarting bluetooth so I'll need an expect script to set it >> up each bluetooth re-init as it looks like there are no scripting hooks >> in bluetoothctl. >> >> BillK > > Thanks BillK, your suggestions above helped somewhat, because I was able to > connect with my phone, but it didn't get me far enough. I was not able to > connect with rfcomm to my mobile. When I ran 'pon ' pppd > started, but I got errors like: > > Apr 26 18:15:12 dell_xps chat[29579]: -- write failed: Transport endpoint is > not connected > Apr 26 18:15:12 dell_xps chat[29579]: Failed > > > This was despite the fact that I had created manually the rfcomm0 device and > binded it to the bdaddr of my phone as you suggested. > > Googling for this error revealed that this is because the rfcomm code has > changed - but there is a patch which may fix things: > > http://comments.gmane.org/gmane.linux.bluez.kernel/42303 > > > I ran out of time and did not try 'rfcomm connect' instead of 'rfcomm bind' to > see if it makes a difference in my case. > > FYI, I'm on net-wireless/bluez-5.15 and kernel 3.12.13-gentoo. > I just upgraded to 3.12.13 and it stopped working with the same error you have. I did see some other messages saying that certain kernel versions are broken but I'll now need to look into that now. BillK