Arch Linux

musasabi

Member

From: Chicago, IL

Registered: 2011-06-23

Posts: 63

bluetooth - hci0: Connection timed out (110)

Some while ago (after a system update) I stopped being able to connect my bluetooth headphones to my Gigabyte GA-Z97N-Wifi motherboard's bluetooth module. For reference:

$ uname -a
Linux blendtec 4.1.6-1-ARCH #1 SMP PREEMPT Mon Aug 17 08:52:28 CEST 2015 x86_64 GNU/Linux
...
$ pacaur -Q | egrep -w "pulseaudio-alsa|pulseaudio-bluetooth|bluez|bluez-libs|bluez-utils|bluez-firmware"
bluez 5.33-1
bluez-firmware 1.2-8
bluez-hid2hci 5.33-1
bluez-libs 5.33-1
bluez-plugins 5.33-1
bluez-utils 5.33-1
pulseaudio-alsa 2-3
pulseaudio-bluetooth 6.0-2
...
$ lsmod | grep bt
btusb                  45056  0
btbcm                  16384  1 btusb
btintel                16384  1 btusb
bluetooth             458752  9 bnep,btbcm,btusb,btintel
usbcore               200704  7 btusb,ehci_hcd,ehci_pci,usbhid,usbip_host,xhci_hcd,xhci_pci

And, following the guide I get the following results

$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2015-08-26 08:46:17 CDT; 37s ago
     Docs: man:bluetoothd(8)
 Main PID: 356 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─356 /usr/lib/bluetooth/bluetoothd

Aug 26 08:46:17 blendtec systemd[1]: Starting Bluetooth service...
Aug 26 08:46:17 blendtec bluetoothd[356]: Bluetooth daemon 5.33
Aug 26 08:46:17 blendtec systemd[1]: Started Bluetooth service.
Aug 26 08:46:17 blendtec bluetoothd[356]: Starting SDP server
Aug 26 08:46:17 blendtec bluetoothd[356]: Bluetooth management interface 1.9 initialized
...
$ sudo bluetoothctl
[sudo] password for patrick: 
[bluetooth]# list
[bluetooth]# power on
No default controller available
[bluetooth]# exit

Beginning to wonder if I uninstalled the wireless module in my sleep or something, I checked:

$ sudo hciconfig -a
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:3 acl:0 sco:0 commands:1 errors:0
	Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
	Packet type: DM1 DH1 HV1 
	Link policy: 
	Link mode: SLAVE ACCEPT

So I tried to bring it up:

$ sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

And that's it. That's as far as I've gotten. Bluetooth support for this board has been iffy for the ~year I've been using it, but I've generally always been able to coax it into functionality. After this most recent breakage, however, I've been stuck facing this timeout for some weeks now, with no perceptible change.

EDIT: I've also tried the cold boot solution mentioned in a few other threads a number of times. Also, in case anyone asks, rfkill isn't the problem here:

$ rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

Last edited by musasabi (2015-08-26 14:10:43)