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 C549C1381FA for ; Thu, 29 May 2014 06:28:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8BC9BE0884; Thu, 29 May 2014 06:28:02 +0000 (UTC) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 502B0E0819 for ; Thu, 29 May 2014 06:28:00 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id r20so21152wiv.3 for ; Wed, 28 May 2014 23:27:59 -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=a6RPPXBo8lbdaf50EI8+kwYjkodYhZ3nF0Mnf+zE230=; b=nMDhmh2BTIh022aemK8joJV54u9Gr9uiXHic9lTVlpg7iG3uZZIA1685Es2xYa+3on PM4GOfliystr1ELLCQjbbcmVoQuW9PPwdE1LJ54YTUWCFmJXZyASIkcDee6jQ/MjzJBC W6tNnEQSWQ2ZXxy/N1+jJ1pKaTcyhc7idDnhiCP8g6RoKiQdivVrsuHlGYNF12CVlw8t 2ywfzGsEFWhHw9r7kkzu5HXGdemSRmRRYkif/TUl8u4e0/pJGxOBo5zVK8e2bzan5zeT 9QSDdMM2FZbG1jjr+vAYB3VBu9IjH+4PTiLCtLo2F90xWGy1jcyrFwMq5sHF3muqeQLD VfIA== X-Received: by 10.180.210.238 with SMTP id mx14mr55360294wic.61.1401344879789; Wed, 28 May 2014 23:27:59 -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 mw4sm22967768wib.12.2014.05.28.23.27.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 28 May 2014 23:27:58 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: bluez 5 not connecting Date: Thu, 29 May 2014 07:27:24 +0100 User-Agent: KMail/1.13.7 (Linux/3.12.20-gentoo; KDE/4.12.5; x86_64; ; ) References: <53578420.1040604@iinet.net.au> <201405282329.03803.michaelkintzios@gmail.com> <53866BAC.6070002@iinet.net.au> In-Reply-To: <53866BAC.6070002@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="nextPart1409093.hgN5708HmV"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201405290727.35118.michaelkintzios@gmail.com> X-Archives-Salt: 124e4ecf-29fd-4319-92e4-a88eb2c4c2ac X-Archives-Hash: 491093b32e67178f1dadc6cc6d708603 --nextPart1409093.hgN5708HmV Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Thursday 29 May 2014 00:05:16 William Kenworthy wrote: > On 29/05/14 06:28, Mick wrote: > > On Wednesday 28 May 2014 20:02:29 Samuli Suominen wrote: > >> On 28/05/14 21:42, Mick wrote: > >>> Hmm ... am I alone in this quest? > >>=20 > >> See here, http://bugs.gentoo.org/show_bug.cgi?id=3D505362 > >=20 > > Thanks! I missed this bug when I glanced earlier. However, it does not > > mention rfcomm is now missing, or the fact that the gentoo rc script > > fails to initialise bluethooth and complains about rfcomm service not > > having started/exist, or that bluetoothctl now does not work at all. Is > > all this down to a missing udev rule? >=20 > No its the fact that bluez 5 has been redesigned to fit in more with the > systemd world. I see. No systemd here, other than systemd's udev. > it works if: >=20 > remove rfcomm using rc-update I didn't have to remove it because it wasn't there ... no rfcomm service=20 anymore, or any /etc/conf.d/rfcomm file. There is a /etc/conf.d/bluetooth= =20 showing: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # Bluetooth configuraton file # Bind rfcomm devices (allowed values are "true" and "false") RFCOMM_ENABLE=3Dtrue # Config file for rfcomm RFCOMM_CONFIG=3D"/etc/bluetooth/rfcomm.conf" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > /etc/init.d/bluetoothctl restart (get rid of any existing config) Ahh! I have no /etc/init.d/bluetoothctl service, only /etc/init.d/bluetooth Am I missing some package for it? Interestingly the module bt_rfcomm was n= ot=20 initialised by udev and I had to modprobe it manually ... # lsmod | grep bt btusb 14115 0=20 bluetooth 173578 5 btusb,rfcomm > bluetoothctl > power on > scan on > agent on > default-agent > trust [MAC ADDRESS OF CLIENT] > pair [MAC ADDRESS OF CLIENT] > enter PIN when requested > wait for "Connected: no" > exit Unfortunately, none of the above works anymore for me: [bluetooth]# power on No default controller available [bluetooth]# scan on No default controller available [bluetooth]# agent on Agent registration enabled [bluetooth]# default-agent=20 No agent is registered [bluetooth]# > After this you should have an rfcomm channel available to the client. I > have the above in an expect script as bluetoothctl has no inate remote > controllability capabilities. No separate pairing app or rfcomm init > script needed. I do not get a /dev/rfcommX, unless I manually set it up like so: # rfcomm bind rfcomm0 hci0 # ls -la /dev/rfcomm* crw-rw---- 1 root uucp 216, 0 May 29 07:06 /dev/rfcomm0 and hci0 will not come up unless I start it with hciconfig. Despite all th= is=20 manual intervention bluetooth does not have access or use the rfcomm device= ,=20 although 'hcitool scan' and 'sdptool browse' return results from my mobile= =20 phone. Please note I have not used the previous patch you have posted on the list. These are the BT modules in my 3.12.20-gentoo kernel: $ grep -i BT /usr/src/linux/.config CONFIG_BT=3Dm CONFIG_BT_RFCOMM=3Dm CONFIG_BT_RFCOMM_TTY=3Dy CONFIG_BT_BNEP=3Dm CONFIG_BT_BNEP_MC_FILTER=3Dy CONFIG_BT_BNEP_PROTO_FILTER=3Dy CONFIG_BT_HIDP=3Dm CONFIG_BT_HCIBTUSB=3Dm CONFIG_BT_HCIBTSDIO=3Dm # CONFIG_BT_HCIUART is not set CONFIG_BT_HCIBCM203X=3Dm # CONFIG_BT_HCIBPA10X is not set # CONFIG_BT_HCIBFUSB is not set # CONFIG_BT_HCIDTL1 is not set # CONFIG_BT_HCIBT3C is not set # CONFIG_BT_HCIBLUECARD is not set # CONFIG_BT_HCIBTUART is not set # CONFIG_BT_HCIVHCI is not set # CONFIG_BT_MRVL is not set # CONFIG_BT_ATH3K is not set CONFIG_MAC_EMUMOUSEBTN=3Dy # CONFIG_INPUT_ATLAS_BTNS is not set # CONFIG_VIDEO_USBTV is not set # CONFIG_SND_BT87X is not set # CONFIG_USB_BTMTK is not set # CONFIG_TOSHIBA_BT_RFKILL is not set # CONFIG_BTRFS_FS is not set # CONFIG_RBTREE_TEST is not set CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=3Dy and I don't recall changing any of them since the good ol' bluez-4 days. =2D-=20 Regards, Mick --nextPart1409093.hgN5708HmV 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) iQEcBAABCAAGBQJThtNXAAoJELAdA+zwE4YesXYH/juKZxFhy8Kpp7ik05waMcRO GjdffMzourWcZJmiRVaNTeN3mIUfhWJ5xsTbN+ObHj4eY/1ccyAvI9eXG+VzpJ1g XrYwGT4d8AAGIRF6kNe7lEPD7dEzaSDkn06gZGqDVbYXssw4ErSdZFGDHW5CJ/VM iXSuJWBE8oMXXD47eFQs6wjwFCG6E1n3fimPcFPtnVfhqWTznqB0qOX39huHAafw nE7aZVHFftTtGzoa53EWgZQHmgdLLKjFw3Ejflm4TU1wXVd5WzW6t4IIriFdQ/uy xLQ36c4tFW/WgxqxfzEnicYddWCIp53hVEivvenkMO3tVB5h66Key5Z+4C+oyog= =T1Vn -----END PGP SIGNATURE----- --nextPart1409093.hgN5708HmV--