[gentoo-user] bluez 5 not connecting

[William Kenworthy]

The bluez-5 stack is causing me some problems. It will pair but then
says its not paired so wont connect. Googling shows lots of problems
with many saying it suddenly starts working and they don't know what
happened!

The BT dongle worked fine under bluez-3 and 4. The other end is an
arduino which needs to be connected via an rfcomm channel (for serial
comms) and the hardware on both ends has been working for literally years.

After upgrading to bluez-5 it stopped working.

I used bluetoothctl to pair it and info shows it paired and trusted, but
I cant connect to it:

[bluetooth]# info 00:11:03:17:01:12
Device 00:11:03:17:01:12
Name: anubis
Alias: anubis
Class: 0x001f00
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: yes
UUID: Serial Port
(00001101-0000-1000-8000-00805f9b34fb)
[bluetooth]# connect 00:11:03:17:01:12
Attempting to connect to 00:11:03:17:01:12
[CHG] Device 00:11:03:17:01:12 Connected: yes
Failed to connect: org.bluez.Error.NotAvailable
[CHG] Device 00:11:03:17:01:12 Connected: no
[bluetooth]#


What am I missing/misunderstanding?

BillK

[cov...@ccs.covici.com]

Make sure you have at least 5.14, below that mine did not work at all.
Try the connect from blutoothctl and seewhat it says. Also, you have to
put the device up before you do anything, such as hciconfig hci0 up
whereas before you did not have to do this.

--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici
cov...@ccs.covici.com

[William Kenworthy]

Hi John, the above is bluez 5.15, and the messages above including from
the connect command are using bluetoothctl ...

Had a play with hcitool and and I cant get a connect with that either.
Tried updating bluez to 5.17 and still nothing.

BillK

[cov...@ccs.covici.com]

Can you do hcitool scan? If not, do
hciconfig hci0 up or whatever your device name if you have more than
one.

[James]

William Kenworthy <billk <at> iinet.net.au> writes:


> The bluez-5 stack is causing me some problems.

> What am I missing/misunderstanding?

These wireless protocols, have many versions (variants) and
nuances via the prticular hardware that is used. Some light
reading might better postion you?


https://www.usenix.org/legacy/event/woot07/tech/full_papers/
spill/spill_html/index.html

http://www.ti.com/tool/packet-sniffer

net-wireless/bluez-hcidump (never tried this one)


I would think that there should be some open-source Bluetooth packet
sniffers that may help diagnose the problem.

I was able to find :

MAC Address Prefix Manufacturer
001103 kawamura electric inc.


using the MAC address. Perhaps an email to their tech support
descriping your problems might help?

I suggest you dissect the packets and hardware and look for the issue
to your problem. Can you move the BT device to a winblozs box and
see if it works? Amplifiers die all the time, particularly if they
are overheated or fed noisy power......

could be hardware or software related..... dissect the pieces,

HTH,
good_hunting!
James

[William Kenworthy]

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 <dev_id>
trust <dev_id>
exit

In a shell:
rfcomm bind rfcomm0 <dev_id>

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

[Mick]

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 <connection_name>' 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.
--
Regards,
Mick

[William Kenworthy]

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

[William Kenworthy]

I used the patch from the reply above - worked!

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?)

BillK

[Mick]

This is getting worse! O_O

I am on net-wireless/bluez-5.18 and gentoo-sources-3.12.20 without the patch.

Now I have no rfcomm service at all listed under rc-update and if I try to
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.
Indeed, hci0 is not configured. O_o

So, running:

# hciconfig hci0 up

allows me to list it:

$ hcitool dev
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]#

NOTE: using hcitool I can scan my mobile phone, but without rfcomm I can't use
it.


Hmm ... am I alone in this quest?

--
Regards,
Mick

[Samuli Suominen]

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

[Mick]

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?

--
Regards,
Mick

[William Kenworthy]

No its the fact that bluez 5 has been redesigned to fit in more with the
systemd world.

it works if:

remove rfcomm using rc-update
/etc/init.d/bluetoothctl restart (get rid of any existing config)

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

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.

BillK

[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

[Mick]

Hmm... also noticed that BT_HCIBCM203X is not loaded either. This is what
dmesg shows:
=========================================================================
...
[ 2.778306] usb 2-1.6: new full-speed USB device number 3 using ehci-pci
[ 2.795308] hub 2-1:1.0: port 6 not reset yet, waiting 10ms
[ 2.844701] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.2, id:
0x1c0b1, caps: 0xd04733/0xa40000/0xa0000, board id: 3655, fw id: 579772
[ 2.870246] usb 2-1.6: ep0 maxpacket = 8
[ 2.873102] usb 2-1.6: default language 0x0409
[ 2.873610] usb 2-1.6: udev 3, busnum 2, minor = 130
[ 2.873617] usb 2-1.6: New USB device found, idVendor=0a5c, idProduct=4500
[ 2.879698] usb 2-1.6: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 2.884038] usb 2-1.6: Product: BCM2046B1
[ 2.888341] usb 2-1.6: Manufacturer: Broadcom
[ 2.891237] usb 2-1.6: usb_probe_device
[ 2.891244] usb 2-1.6: configuration #1 chosen from 1 choice
[ 2.891354] usb 2-1.6: adding 2-1.6:1.0 (config #1, interface 0)
[ 2.891398] hub 2-1.6:1.0: usb_probe_interface
[ 2.891403] hub 2-1.6:1.0: usb_probe_interface - got id
[ 2.891409] hub 2-1.6:1.0: USB hub found
[ 2.894104] hub 2-1.6:1.0: 3 ports detected
[ 2.896322] hub 2-1.6:1.0: compound device; port removable status: FFF
[ 2.896325] hub 2-1.6:1.0: ganged power switching
[ 2.896327] hub 2-1.6:1.0: global over-current protection
[ 2.896329] hub 2-1.6:1.0: power on to power good time: 100ms
[ 2.896606] hub 2-1.6:1.0: local power source is good
[ 2.896611] hub 2-1.6:1.0: no over-current condition exists
[ 2.896687] hub 2-1.6:1.0: enabling power on all ports
[snip ...]


[ 9.117034] Bluetooth: Core ver 2.16
[ 9.117051] NET: Registered protocol family 31
[ 9.117053] Bluetooth: HCI device and connection manager initialized
[ 9.117058] Bluetooth: HCI socket layer initialized
[ 9.117061] Bluetooth: L2CAP socket layer initialized
[ 9.117067] Bluetooth: SCO socket layer initialized
[ 9.189459] cfg80211: World regulatory domain updated:
[ 9.189460] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 9.189462] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 9.189463] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 9.189465] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi,
2000 mBm)
[ 9.189466] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 9.189467] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[ 9.229696] btusb 2-1.6.3:1.0: usb_probe_interface
[ 9.229699] btusb 2-1.6.3:1.0: usb_probe_interface - got id
[ 9.230158] btusb 2-1.6.3:1.2: usb_probe_interface
[ 9.230164] btusb 2-1.6.3:1.2: usb_probe_interface - got id
[ 9.230178] btusb 2-1.6.3:1.3: usb_probe_interface
[ 9.230182] btusb 2-1.6.3:1.3: usb_probe_interface - got id
[ 9.230211] usbcore: registered new interface driver btusb
[ 9.230410] usb 2-1.6.3: link qh1-3008/ffff8801325a7c00 start 0 [1/2 us]
[ 9.346066] input: HDA Intel MID Headphone Surround as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input14
=========================================================================

So it picks up and loads btusb, but not bcm203x, or rfcomm. Is my kernel
config wrong?


This is the device in question:
==============================
Bus 002 Device 006: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth
Mini-card
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x413c Dell Computer Corp.
idProduct 0x8156 Wireless 370 Bluetooth Mini-card
bcdDevice 4.56
iManufacturer 1 Dell Computer Corp
iProduct 2 Dell Wireless 370 Bluetooth Mini-card
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 216
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 0
iInterface 0
Device Firmware Upgrade Interface Descriptor:
bLength 7
bDescriptorType 33
bmAttributes 7
Will Not Detach
Manifestation Tolerant
Upload Supported
Download Supported
wDetachTimeout 5000 milliseconds
wTransferSize 64 bytes
Device Status: 0x0001
Self Powered
==============================

--
Regards,
Mick

[William Kenworthy]

On 29/05/14 18:18, Mick wrote:
> On Thursday 29 May 2014 07:27:24 Mick wrote:
>> 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 am not using systemd either - there is no bluetoothctl service (its an
application and written with no remote control capabilities - why?: no
idea - in my reading I came across a message saying that its designed
for use with systemd but I thought it would still need the remote option
unless bluetoothctl like functions are natively included in systemd)

You will probably have to load the modules manually
(/etc/conf.d/modules) - mine do load automatically though

moriah ~ # lsmod|grep bt
btusb 14099 0
bluetooth 191573 24 bnep,btusb,rfcomm
usbcore 132770 10
btusb,usblp,uhci_hcd,usb_storage,usbserial,ehci_hcd,ehci_pci,usbhid,ftdi_sio,cdc_acm
moriah ~ #

Sounds like you have more than one problem and you need to get the
modules loaded and working first, then you can run bluetoothctl manually.

BillK

[Mick]

On Thursday 29 May 2014 23:32:55 William Kenworthy wrote:

> I am not using systemd either - there is no bluetoothctl service (its an
> application and written with no remote control capabilities - why?: no
> idea - in my reading I came across a message saying that its designed
> for use with systemd but I thought it would still need the remote option
> unless bluetoothctl like functions are natively included in systemd)
>
> You will probably have to load the modules manually
> (/etc/conf.d/modules) - mine do load automatically though

Right, so did mine until recently. I'm guessing that it's something to do
with udev, or with changes in the kernel that affect my Broadcom bluetooth
chip.

> moriah ~ # lsmod|grep bt
> btusb 14099 0
> bluetooth 191573 24 bnep,btusb,rfcomm
> usbcore 132770 10
> btusb,usblp,uhci_hcd,usb_storage,usbserial,ehci_hcd,ehci_pci,usbhid,ftdi_si
> o,cdc_acm moriah ~ #
>
> Sounds like you have more than one problem and you need to get the
> modules loaded and working first, then you can run bluetoothctl manually.

I already tried that. The modules load, hciconfig works to bring up hci0, but
bluetoothctl complains that there is no available bluetooth controller. :-/
--
Regards,
Mick

[Mick]

I tried bluetooth with another laptop - also broadcom bluetooth but a
different chip. Well, what do you know. I had to manually modprobe bnep and
rfcomm, but /etc/init.d/bluetooth started without complaining that it needs
the rfcomm service and bluetoothctl worked fine showing the bt controller SSID
and other devices in the vicinity.

So the problem seems to be with the particular broadcom BCM2046 Bluetooth
device that I have on my laptop. :-(

I've posted in the forums in case someone there has any ideas.

--
Regards,
Mick