Cannot start bluetooth.service [SOLVED]

graysky · 2013-12-08 15:08:19

Both bluez and bluez-utils are installed, but I remain unable to run the bluetooth.service either before or after plugging in a blue tooth USB dongle that I know worked 6-8 months ago (likely under bluez4 which is now deprecated).

Hardware info physically printed on the dongle: "ASUS USB-BT211" (omitted serial number).

The kernel sees the dongle:

[ 2320.160988] usb 1-2: new full-speed USB device number 2 using xhci_hcd

And

# lsusb -v
...
Bus 001 Device 002: ID 0cf3:3000 Atheros Communications, Inc. AR3011 Bluetooth (no firmware)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0cf3 Atheros Communications, Inc.
  idProduct          0x3000 AR3011 Bluetooth (no firmware)
  bcdDevice            2.00
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      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               0
Device Status:     0x0001
  Self Powered

But the bluetooth deamon does not start:

% start bluetooth
bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
   Active: failed (Result: exit-code) since Sun 2013-12-08 10:17:32 EST; 2ms ago
     Docs: man:bluetoothd(8)
  Process: 5149 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/FAILURE)
 Main PID: 5149 (code=exited, status=1/FAILURE)
   Status: "Starting up"

Dec 08 10:17:32 ease bluetoothd[5149]: Bluetooth daemon 5.11
Dec 08 10:17:32 ease systemd[1]: Started Bluetooth service.
Dec 08 10:17:32 ease systemd[1]: bluetooth.service: main process exited, code=exited, status=1/FAILURE
Dec 08 10:17:32 ease systemd[1]: Unit bluetooth.service entered failed state.

All I get in my journalctl are some errors with pulseaudio (but this is a USB keyboard so I don't care to fix these nor have I in the past).

-- Logs begin at Sun 2013-12-08 09:44:30 EST, end at Sun 2013-12-08 10:18:25 EST. --
Dec 08 10:17:32 ease pulseaudio[936]: [pulseaudio] bluez4-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Dec 08 10:17:32 ease pulseaudio[936]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

Can't seem to find this exact problem on our bbs or in the wild. Most other posts indicate this daemon is running. Productive thoughts are appreciated.

Last edited by graysky (2013-12-08 22:39:49)

graysky · 2013-12-08 15:25:41

More info: if I run the deamon manually with the nodetatch flag, I get a little more info seeming to indicate a problem communicating with the USB dongle or that the dongle is not supported under version 5?

# /usr/lib/bluetooth/bluetoothd -n                                                                                                                                                                                                    :(
bluetoothd[5824]: Bluetooth daemon 5.11
bluetoothd[5824]: Failed to access management interface
bluetoothd[5824]: Adapter handling initialization failed

# hciconfig --all
Can't open HCI socket.: Address family not supported by protocol

bluetoothctl -a 
[bluetooth]# list
[bluetooth]#

Last edited by graysky (2013-12-08 15:28:50)

karol · 2013-12-08 15:26:42

Have you tried bluez4 https://aur.archlinux.org/packages/bluez4/ ?

Last edited by karol (2013-12-08 15:27:03)

graysky · 2013-12-08 15:31:41

@k - Just removed bluez and built/installed bluez4... similar error:

% start bluetooth                                                                                                                      :(
bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
   Active: failed (Result: exit-code) since Sun 2013-12-08 10:29:53 EST; 4ms ago
  Process: 12710 ExecStart=/usr/lib/bluetooth/bluetoothd -n (code=exited, status=1/FAILURE)
 Main PID: 12710 (code=exited, status=1/FAILURE)
   Status: "Starting up"

Dec 08 10:29:53 ease bluetoothd[12710]: bluetoothd[12710]: Can't init bnep module
Dec 08 10:29:53 ease bluetoothd[12710]: bluetoothd[12710]: Failed to init network plugin
Dec 08 10:29:53 ease bluetoothd[12710]: bluetoothd[12710]: Unable to start SCO server socket
Dec 08 10:29:53 ease bluetoothd[12710]: bluetoothd[12710]: Failed to init audio plugin
Dec 08 10:29:53 ease bluetoothd[12710]: bluetoothd[12710]: Failed to init gatt_example plugin
Dec 08 10:29:53 ease bluetoothd[12710]: bluetoothd[12710]: Can't open HCI socket: Address family not supported by protocol (97)
Dec 08 10:29:53 ease bluetoothd[12710]: bluetoothd[12710]: adapter_ops_setup failed
Dec 08 10:29:53 ease systemd[1]: Started Bluetooth service.
Dec 08 10:29:53 ease systemd[1]: bluetooth.service: main process exited, code=exited, status=1/FAILURE
Dec 08 10:29:53 ease systemd[1]: Unit bluetooth.service entered failed state.

And manually:

# /usr/lib/bluetooth/bluetoothd -n
bluetoothd[12943]: Bluetooth daemon 4.101
bluetoothd[12943]: Starting SDP server
bluetoothd[12943]: opening L2CAP socket: Address family not supported by protocol
bluetoothd[12943]: Server initialization failed
bluetoothd[12943]: DIS cannot start: GATT is disabled
bluetoothd[12943]: Failed to init deviceinfo plugin
bluetoothd[12943]: Failed to init proximity plugin
bluetoothd[12943]: Failed to init time plugin
bluetoothd[12943]: Failed to init alert plugin
bluetoothd[12943]: Failed to init thermometer plugin
bluetoothd[12943]: Failed to open control socket: Address family not supported by protocol (97)
bluetoothd[12943]: Can't init bnep module
bluetoothd[12943]: Failed to init network plugin
bluetoothd[12943]: Unable to start SCO server socket
bluetoothd[12943]: Failed to init audio plugin
bluetoothd[12943]: Failed to init gatt_example plugin
bluetoothd[12943]: Can't open HCI socket: Address family not supported by protocol (97)
bluetoothd[12943]: adapter_ops_setup failed

...thing is that I had this working just fine 6-8 months ago

Last edited by graysky (2013-12-08 15:32:00)

graysky · 2013-12-08 19:58:53

I am left scratching my head... inserting this into another machine works as expected. I have tried multiple USB slots on my workstation, but none of them are working

Successful operation on another machine:

% dmesg
...
[ 8811.963293] usb 1-11: new full-speed USB device number 4 using xhci_hcd
[ 8811.986205] Bluetooth: Core ver 2.16
[ 8811.986376] NET: Registered protocol family 31
[ 8811.986378] Bluetooth: HCI device and connection manager initialized
[ 8811.986385] Bluetooth: HCI socket layer initialized
[ 8811.986388] Bluetooth: L2CAP socket layer initialized
[ 8811.986393] Bluetooth: SCO socket layer initialized
[ 8812.198259] usb 1-11: USB disconnect, device number 4
[ 8812.199676] usbcore: registered new interface driver ath3k
[ 8813.536163] usb 1-11: new full-speed USB device number 5 using xhci_hcd
[ 8813.563039] usbcore: registered new interface driver btusb

I am able to start the bluetooth daemon and related tools... guess my question now is wtf?

EDIT: AH! I suspect that I am missing modules on my workstation!

From other box:

% lsmod | grep blue
bluetooth             309116  22 bnep,ath3k,btusb
rfkill                 15651  3 bluetooth,asus_wmi
crc16                   1367  2 ext4,bluetooth

I lack these on my workstation due to building the kernel up custom without them. I will rebuild/reboot and update the thread is I am correct.

Last edited by graysky (2013-12-08 20:00:52)

graysky · 2013-12-08 22:40:17

Yep... that was the problem! This was pilot error.

Arch Linux

#1 2013-12-08 15:08:19

Cannot start bluetooth.service [SOLVED]

#2 2013-12-08 15:25:41

Re: Cannot start bluetooth.service [SOLVED]

#3 2013-12-08 15:26:42

Re: Cannot start bluetooth.service [SOLVED]

#4 2013-12-08 15:31:41

Re: Cannot start bluetooth.service [SOLVED]

#5 2013-12-08 19:58:53

Re: Cannot start bluetooth.service [SOLVED]

#6 2013-12-08 22:40:17

Re: Cannot start bluetooth.service [SOLVED]

Board footer