Re: [gentoo-user] Re: bluez 5 not connecting

[Mick]

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?
> >>
> >> See here, http://bugs.gentoo.org/show_bug.cgi?id=505362
> >
> > 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?
>
> 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:
>
> remove rfcomm using rc-update

I didn't have to remove it because it wasn't there ... no rfcomm service 
anymore, or any /etc/conf.d/rfcomm file.  There is a /etc/conf.d/bluetooth 
showing:
============================================================
# Bluetooth configuraton file

# Bind rfcomm devices (allowed values are "true" and "false")
RFCOMM_ENABLE=true

# Config file for rfcomm
RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf"
============================================================


> /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 not 
initialised by udev and I had to modprobe it manually ...

# lsmod | grep bt
btusb                  14115  0 
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 
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 this 
manual intervention bluetooth does not have access or use the rfcomm device, 
although 'hcitool scan' and 'sdptool browse' return results from my mobile 
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=m
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m
CONFIG_BT_HCIBTUSB=m
CONFIG_BT_HCIBTSDIO=m
# CONFIG_BT_HCIUART is not set
CONFIG_BT_HCIBCM203X=m
# 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=y
# 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=y

and I don't recall changing any of them since the good ol' bluez-4 days.
-- 
Regards,
Mick