From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 726FE1381FA for ; Wed, 28 May 2014 18:58:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4726AE08EC; Wed, 28 May 2014 18:58:53 +0000 (UTC) Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 239F5E08AD for ; Wed, 28 May 2014 18:58:51 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id x13so11683333wgg.10 for ; Wed, 28 May 2014 11:58:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=2rPlcEamnLq4IPO1vngyp9QYdADtCZVkBr7S3UzB20c=; b=pStGZWaT0/2OU9FGXcHsYU3QYGmIr4C14T2psiejmgbNXW/lL1s1QUP649ux/yGpan sVshPPDwJCKigEi71BY5CVrUxrNsnLe5X9FDE458X2evH9UsT2nEwFSVl/LaJ8sNY73R fhxHQkb8ae4oARyIFHObNNF5aP0MKKt5jGdNHXL9yqeuC9aOHj3+srTXlyrncOqU4LsV 7T3MX59zr5z2hMHecS0hY/YIApbePsGwDEwqKKbP4LKXIhKVO7w+KJQFUU7kh6LoFzNT PCTkatXc3cpPZywuJBPdv3A8lPXuEopWwhPc2sv/7pj8x8tgQc3liqQMeiHOMudQIEV5 7tWQ== X-Received: by 10.194.89.40 with SMTP id bl8mr2209298wjb.90.1401303530688; Wed, 28 May 2014 11:58:50 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id b16sm45337342wjx.45.2014.05.28.11.58.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 28 May 2014 11:58:49 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: bluez 5 not connecting Date: Wed, 28 May 2014 19:42:10 +0100 User-Agent: KMail/1.13.7 (Linux/3.12.20-gentoo; KDE/4.12.5; x86_64; ; ) References: <53578420.1040604@iinet.net.au> <535C7603.709@iinet.net.au> <535CB163.8080008@iinet.net.au> In-Reply-To: <535CB163.8080008@iinet.net.au> 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 Content-Type: multipart/signed; boundary="nextPart23359476.ShPZY9i2Vh"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201405281942.20218.michaelkintzios@gmail.com> X-Archives-Salt: e552aa5a-7683-423a-87e9-e1e089e5a2f4 X-Archives-Hash: ec80832e73026c91565e0945bdba6c1a --nextPart23359476.ShPZY9i2Vh Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday 27 Apr 2014 08:27:31 William Kenworthy wrote: > On 04/27/14 11:14, William Kenworthy wrote: > > 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) . > >>>=20 > >>> In bluetoothctl: > >>> power on > >>> scan on > >>> agent on > >>> default-agent > >>> pair > >>> trust > >>> exit > >>>=20 > >>> In a shell: > >>> rfcomm bind rfcomm0 > >>>=20 > >>> do serial port stuff with /dev/rfcomm0 > >>>=20 > >>> rfcomm unbind rfcomm0 > >>>=20 > >>> 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. > >>>=20 > >>> 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. > >>>=20 > >>> BillK > >>=20 > >> Thanks BillK, your suggestions above helped somewhat, because I was ab= le > >> 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: > >>=20 > >> 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 > >>=20 > >>=20 > >> This was despite the fact that I had created manually the rfcomm0 devi= ce > >> and binded it to the bdaddr of my phone as you suggested. > >>=20 > >> Googling for this error revealed that this is because the rfcomm code > >> has > >>=20 > >> changed - but there is a patch which may fix things: > >> http://comments.gmane.org/gmane.linux.bluez.kernel/42303 > >>=20 > >> 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. > >>=20 > >> FYI, I'm on net-wireless/bluez-5.15 and kernel 3.12.13-gentoo. > >=20 > > I just upgraded to 3.12.13 and it stopped working with the same error > > you have. > >=20 > > I did see some other messages saying that certain kernel versions are > > broken but I'll now need to look into that now. > >=20 > > BillK >=20 > I used the patch from the reply above - worked! >=20 > It did take a couple of goes but after restarting the bluetooth > initscript before using bluetoothctl via expect (took 3 goes before I > got a clean run from "expect" - timing might need adjusting?) This is getting worse! O_O I am on net-wireless/bluez-5.18 and gentoo-sources-3.12.20 without the patc= h. Now I have no rfcomm service at all listed under rc-update and if I try to= =20 start /etc/init.d/bluetooth I get: # /etc/init.d/bluetooth restart * ERROR: bluetooth needs service(s) rfcomm Creating /dev/rfcomm0 with: # rfcomm bind rfcomm0 hci0 does not change the error. Starting KDE's BlueDevil shows no adaptor found= =2E =20 Indeed, hci0 is not configured. O_o So, running: # hciconfig hci0 up allows me to list it: $ hcitool dev=20 Devices: hci0 90:4C:E5:FA:F2:A8 but NOT under bluetoothctl! [bluetooth]# power on No default controller available [bluetooth]# show No default controller available [bluetooth]# list [bluetooth]# [bluetooth]# devices [bluetooth]#=20 NOTE: using hcitool I can scan my mobile phone, but without rfcomm I can't = use=20 it. Hmm ... am I alone in this quest? =2D-=20 Regards, Mick --nextPart23359476.ShPZY9i2Vh Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAABCAAGBQJThi4MAAoJELAdA+zwE4YeivwH/j7uQ5uSzC4/tgc+Jfic5SsE TbYy6L73yP9LcUMTREYNbINGqzN1vC0W80K9Hbe0RLI+RAo4Jnh5y89scFr14cB8 ukib04lfScEMfUck4O7d0mzvws+Xu1W20BqGR0WRRCjKRfOIvn7BvEdvjk+WhlOm kjnKDnnGObsiKq5Y7hTVzLPlNAtxF0Mcpj4LLNue4ZDFF3CuDIl23l5Aj8JhCf2l hKGOQT9sMZvvDxSU3BkTWOgk4vaUYvOfojVQovMeabV3tMZzGc55BmTelahhbks+ w2a8AACQa4sIg9LtyjWO56XBea0xnrsV6c3ERX0FgnQeTfgTms+yrkv8hY9rmfk= =spYH -----END PGP SIGNATURE----- --nextPart23359476.ShPZY9i2Vh--