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 205D613873B for ; Sun, 2 Mar 2014 11:06:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ADC0CE0AB8; Sun, 2 Mar 2014 11:06:16 +0000 (UTC) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 45725E0A6E for ; Sun, 2 Mar 2014 11:06:14 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id l18so1998203wgh.33 for ; Sun, 02 Mar 2014 03:06:13 -0800 (PST) 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=6d4tdSsfs8/BS2xR4Oav6/LX5fDvv08w5uvJXMPYuqg=; b=TgBIjQTu+kVjtq2LElMGr/3RfrBRbsKVAJsP0k/wZbkgMZp87O9EEOLzkGDHfwVcY8 1SeW3cvq1DG/gvsv6FvYzeN1xGGEEF5PWIfdQUjvZQxVyy/DRMm6LfvkzH4lrIbrEVEc XEN0DRlA4bCPqZICPZLp7bSVAtS+vhmYLSeQvL9PFDnzsiyn8mkZ4P3w9D3IKnSrgBLx vC9AjjFwcciRbBAOlhE/JThLs/JYNrm6INIOt8DRs5yLQgHYbgZTpSPA6XoAHhEqgJRY g8shVrSrUwk5GYoA8xt7jRxe30ypXqjyjG7VKbslDjy5mJWYt7lFqpU5LlbGgfHkxoMq tR5A== X-Received: by 10.194.2.168 with SMTP id 8mr10474805wjv.8.1393758373644; Sun, 02 Mar 2014 03:06:13 -0800 (PST) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id jd2sm22845927wic.9.2014.03.02.03.06.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Mar 2014 03:06:12 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] more bluetooth troubles with 5.14 Date: Sun, 2 Mar 2014 11:05:28 +0000 User-Agent: KMail/1.13.7 (Linux/3.10.17-gentoo; KDE/4.11.5; x86_64; ; ) References: <18934.1393744878@ccs.covici.com> In-Reply-To: <18934.1393744878@ccs.covici.com> 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="nextPart1915992.W0dFMGbLZW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201403021105.55927.michaelkintzios@gmail.com> X-Archives-Salt: 7edb0896-429d-4b8c-8aff-5738a5b11fec X-Archives-Hash: 5b0e9ca2381ceb5a173fb8f9695fe509 --nextPart1915992.W0dFMGbLZW Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Sunday 02 Mar 2014 07:21:18 covici@ccs.covici.com wrote: > Hi. I am getting more troubles with bluetooth 5.14 -- 4 worked fine, 5 > seems to have a lot of quirks. I occasionally tether my phone to my laptop using bluetooth and have found= =20 that establishing a connection can be quite temperamental. Rebooting the=20 phone or disabling/enabling its bluetooth service usually helps get a respo= nse=20 from it. > I get the following lines from a program I am running called brltty: > >Mar 1 15:25:35 ccs bluetoothd[2684]: No agent available for request > >type 0 This is typically obtained when the device is not set to be discoverable. = =20 Check that they both are. If you have restarted/reset either you may need = to=20 set them back to discoverable. > >Mar 1 15:25:35 ccs bluetoothd[2684]: device_request_pin: Operation not > >permitted > >Mar 1 15:25:35 ccs brltty[16004]: RFCOMM connect error 111: Connection > >refused. Have you set up the correct device MAC address in /etc/bluetooth/rfcomm.con= f=20 and restarted it? If yes then this may be a matter of misstyping the pin? > HOw can I fix this? There is a new program under bluetooth 5 called > bluetoothctl, and I paired, trusted and connected, and still no joy. I don't have bluetoothctl here to know what it does, but I use l2ping,=20 hciconfig and sdptool first to make sure that I can see and read the device= I=20 am trying to pair with. If you have indeed managed to pair the two devices= =20 you would not be getting the above connection errors, unless the radio sign= al=20 broke down after pairing, due to e.g. weak signal or electromagnetic=20 interference from some external source. =2D-=20 Regards, Mick --nextPart1915992.W0dFMGbLZW 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) iQEcBAABAgAGBQJTExCTAAoJELAdA+zwE4YerYUH/jcWV9Qa5fw6RjL99JiAg6af 8qC9Sw2A24YHshDEE5OIQhihKFsEwUnnUfns9waC7Be6iP13BXspiIGr0a43+ruu 28pzKKbYqq0q0/5rl5rAPVdZWi1DdQLW2Zjf8thNaVddRCPUBh0w31WR7aLqvpAj hgKcSV1rmTMK1R7WAvr3u2sD71wv5qcO3GRTsAxAQkBQlK8gm+9vIACAp5r54BiL 0GzdM+qWGIwPQjTc6diGyn/pwhL2FuyJaE0WVMM3zanUtGOhxE490KsPCSrJi9Ba qJZFIF2NgMVvZTmzUkApUNinvre6djMK1JwgEQpjdGtMdQ70mMWbS0KoKIIgwm0= =PSJz -----END PGP SIGNATURE----- --nextPart1915992.W0dFMGbLZW--