You are not logged in.

#1 2019-03-17 22:41:53

nstgc
Member
Registered: 2014-03-17
Posts: 393

[solved] USB Bluetooth dongle not working.

Solution: There wasn't enough power to the port so I changed ports.

I'm trying to get a bluetooth dongle to work. I didn't have any difficulties getting the bluetooth on my laptop to work (also running Arch), but this dongle is giving me grief.

I followed the installation guide in https://wiki.archlinux.org/index.php/Bluetooth

Result of `journalctl -b |grep bluetooth`:

Mar 17 18:19:20 Lain-Arch polkitd[949]: Operator of unix-session:1 successfully authenticated as unix-user:briggs5 to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.1913 [systemctl start bluetooth.service] (owned by unix-user:briggs5)
Mar 17 18:19:20 Lain-Arch bluetoothd[22149]: Bluetooth daemon 5.50
Mar 17 18:19:20 Lain-Arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 17 18:19:20 Lain-Arch bluetoothd[22149]: Starting SDP server
Mar 17 18:19:20 Lain-Arch kernel: audit: type=1130 audit(1552861160.472:75): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 17 18:19:20 Lain-Arch dbus-daemon[756]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1918' (uid=0 pid=22149 comm="/usr/lib/bluetooth/bluetoothd ")
Mar 17 18:19:20 Lain-Arch bluetoothd[22149]: Bluetooth management interface 1.14 initialized

Which isn't right according to the USB dongle troubleshooting section. I then unplugged the dongle and plugged it back in (since I loaded the kernel module and started the service after plugging it in). The output from `journelctl -b |grep bluetooth` did not change.

I then try `hciconfig -a hci0` as stated in that section, but I don't have it installed. According to the wiki `hciconfig` was replaced by `bluetoothctl`.

Its at this point that I'm in the dark, since wiki appears to be outdated.

In `bluetoothctl` I tried `list` but that returned nothing. I tried `devices` but that also returned "No default controller available".

I have no clue what's going on here, but the dongle advertised that it was Linux compatible out of the box.

When I plug it in with `journelctl -f` running I get

Mar 17 18:49:56 Lain-Arch kernel: usb 1-1.3.1: new full-speed USB device number 28 using xhci_hcd
Mar 17 18:50:12 Lain-Arch kernel: usb 1-1.3.1: device descriptor read/64, error -110
Mar 17 18:50:27 Lain-Arch kernel: usb 1-1.3.1: device descriptor read/64, error -110
Mar 17 18:50:27 Lain-Arch kernel: usb 1-1.3.1: new full-speed USB device number 29 using xhci_hcd
Mar 17 18:50:43 Lain-Arch kernel: usb 1-1.3.1: device descriptor read/64, error -110
Mar 17 18:50:43 Lain-Arch kernel: usb 1-1.3.1: device descriptor read/64, error -32
Mar 17 18:50:43 Lain-Arch kernel: usb 1-1.3-port1: attempt power cycle
Mar 17 18:50:44 Lain-Arch kernel: usb 1-1.3.1: new full-speed USB device number 30 using xhci_hcd
Mar 17 18:50:44 Lain-Arch kernel: usb 1-1.3.1: Device not responding to setup address.
Mar 17 18:50:44 Lain-Arch kernel: usb 1-1.3.1: Device not responding to setup address.
Mar 17 18:50:44 Lain-Arch kernel: usb 1-1.3.1: device not accepting address 30, error -71
Mar 17 18:50:44 Lain-Arch kernel: usb 1-1.3.1: new full-speed USB device number 31 using xhci_hcd
Mar 17 18:50:44 Lain-Arch kernel: usb 1-1.3.1: Device not responding to setup address.
Mar 17 18:50:44 Lain-Arch kernel: usb 1-1.3.1: Device not responding to setup address.
Mar 17 18:50:45 Lain-Arch kernel: usb 1-1.3.1: device not accepting address 31, error -71
Mar 17 18:50:45 Lain-Arch kernel: usb 1-1.3-port1: unable to enumerate USB device
Mar 17 18:50:45 Lain-Arch kernel: usb 1-1.3.2: new full-speed USB device number 32 using xhci_hcd
Mar 17 18:50:45 Lain-Arch kernel: usb 1-1.3.2: device descriptor read/64, error -32
Mar 17 18:50:45 Lain-Arch kernel: usb 1-1.3.2: device descriptor read/64, error -32
Mar 17 18:50:45 Lain-Arch kernel: usb 1-1.3.2: new full-speed USB device number 33 using xhci_hcd
Mar 17 18:50:45 Lain-Arch kernel: usb 1-1.3.2: device descriptor read/64, error -32
Mar 17 18:50:46 Lain-Arch kernel: usb 1-1.3.2: device descriptor read/64, error -32
Mar 17 18:50:46 Lain-Arch kernel: usb 1-1.3-port2: attempt power cycle
Mar 17 18:50:46 Lain-Arch kernel: usb 1-1.3.2: new full-speed USB device number 34 using xhci_hcd
Mar 17 18:50:46 Lain-Arch kernel: usb 1-1.3.2: Device not responding to setup address.
Mar 17 18:50:47 Lain-Arch kernel: usb 1-1.3.2: Device not responding to setup address.
Mar 17 18:50:47 Lain-Arch kernel: usb 1-1.3.2: device not accepting address 34, error -71
Mar 17 18:50:47 Lain-Arch kernel: usb 1-1.3.2: new full-speed USB device number 35 using xhci_hcd
Mar 17 18:50:47 Lain-Arch kernel: usb 1-1.3.2: Device not responding to setup address.
Mar 17 18:50:47 Lain-Arch kernel: usb 1-1.3.2: Device not responding to setup address.
Mar 17 18:50:47 Lain-Arch kernel: usb 1-1.3.2: device not accepting address 35, error -71
Mar 17 18:50:47 Lain-Arch kernel: usb 1-1.3-port2: unable to enumerate USB device

The manufacture's info: https://support.kinivo.com/customer/por … n&t=536917

Last edited by nstgc (2019-03-18 00:16:52)

Offline

#2 2019-03-17 23:15:22

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,325

Re: [solved] USB Bluetooth dongle not working.

Mar 17 18:50:12 Lain-Arch kernel: usb 1-1.3.1: device descriptor read/64, error -110

The thing is drawing more power than the port can provide.
The host does not happen to be a raspberry pi, does it?

Offline

#3 2019-03-18 00:16:20

nstgc
Member
Registered: 2014-03-17
Posts: 393

Re: [solved] USB Bluetooth dongle not working.

seth wrote:
Mar 17 18:50:12 Lain-Arch kernel: usb 1-1.3.1: device descriptor read/64, error -110

The thing is drawing more power than the port can provide.
The host does not happen to be a raspberry pi, does it?

No, it was pugged into a hub, but it was the only thing in use so I would have expected full power.

Changing ports fixed the issue of it now being detected, but I'm still having problems getting my DS4 to work with it. Oh well. One step at a time.

Thanks!

Offline

Board footer

Powered by FluxBB