You are not logged in.
I'm trying to pair a Bluetooth mouse. It's a miniPCIe combo card, Broadcom BCM94352, aka BCM4352, aka AzureWare2123. I've searched and searched. It seems I either haven't found the right thread, or my issue is different than others. I have no problem with bluetoothctl turning on Bluetooth and scanning. It sees all devices as it should. However, when I go to pair with a device, it returns:
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
<Devices MAC addresses show here>
[bluetooth]# pair <MAC address>
Attempting to pair with <MAC address>
Failed to pair: org.bluez.Error.AuthenticationTimeoutI get the same results with using the 'connect' command.
I tried checking any status or logs based on what others have experienced. Here is systemctl bluetooth status:
$ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2015-05-16 08:59:17 EDT; 33min ago
Docs: man:bluetoothd(8)
Main PID: 291 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─291 /usr/lib/bluetooth/bluetoothd
May 16 08:59:17 PC bluetoothd[291]: Error adding Link Loss service
May 16 08:59:17 PC bluetoothd[291]: Not enough free handles to register service
May 16 08:59:17 PC bluetoothd[291]: Not enough free handles to register service
May 16 08:59:17 PC bluetoothd[291]: Not enough free handles to register service
May 16 08:59:17 PC bluetoothd[291]: Current Time Service could not be registered
May 16 08:59:17 PC bluetoothd[291]: gatt-time-server: Input/output error (5)
May 16 08:59:17 PC bluetoothd[291]: Not enough free handles to register service
May 16 08:59:17 PC bluetoothd[291]: Not enough free handles to register service
May 16 08:59:17 PC bluetoothd[291]: Sap driver initialization failed.
May 16 08:59:17 PC bluetoothd[291]: sap-server: Operation not permitted (1)I don't know where to go from here...
Possibly helpful stuff:
$ dmesg | grep Bluetooth
[ 2.680011] Bluetooth: Core ver 2.20
[ 2.680040] Bluetooth: HCI device and connection manager initialized
[ 2.680046] Bluetooth: HCI socket layer initialized
[ 2.680051] Bluetooth: L2CAP socket layer initialized
[ 2.680060] Bluetooth: SCO socket layer initialized
[ 2.710066] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-13d3-3404.hcd not found
[ 4.353858] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.353862] Bluetooth: BNEP filters: protocol multicast
[ 4.353867] Bluetooth: BNEP socket layer initialized$ lspci | grep Broadcom
02:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03)$ uname -r
4.0.2-1-ARCHLast edited by FNtastic (2015-05-24 15:17:39)
Offline
It happened to me few times.
Try registering agent first, as in here https://wiki.archlinux.org/index.php/Bl … uetoothctl .
Offline
It happened to me few times.
Try registering agent first, as in here https://wiki.archlinux.org/index.php/Bl … uetoothctl .
Thanks for the suggestion. Here's what happens when I do that:
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# pair <MAC address>
Attempting to pair with <MAC address>
[CHG] Device <MAC address> Connected: yes
[CHG] Device <MAC address> Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
[bluetooth]# connect <MAC address>
Attempting to connect to <MAC address>
Failed to connect: org.bluez.Error.FailedI just deleted the original MAC address and tried to scan again. Now a scan returns nothing....
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller <MAC address> Discovering: yesGoing to try a restart and see if it helps.
EDIT: This is what I'm seeing after a reboot:
$ sudo systemctl status -l bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2015-05-17 07:44:17 EDT; 46s ago
Docs: man:bluetoothd(8)
Main PID: 290 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─290 /usr/lib/bluetooth/bluetoothd
May 17 07:44:17 PC bluetoothd[290]: Error adding Link Loss service
May 17 07:44:17 PC bluetoothd[290]: Not enough free handles to register service
May 17 07:44:17 PC bluetoothd[290]: Not enough free handles to register service
May 17 07:44:17 PC bluetoothd[290]: Not enough free handles to register service
May 17 07:44:17 PC bluetoothd[290]: Current Time Service could not be registered
May 17 07:44:17 PC bluetoothd[290]: gatt-time-server: Input/output error (5)
May 17 07:44:17 PC bluetoothd[290]: Not enough free handles to register service
May 17 07:44:17 PC bluetoothd[290]: Not enough free handles to register service
May 17 07:44:17 PC bluetoothd[290]: Sap driver initialization failed.
May 17 07:44:17 PC bluetoothd[290]: sap-server: Operation not permitted (1)And, I'm unable to connect or pair. I would appear to search, but never found any devices. I confirmed the devices are discoverable, etc. Searched and found them with other devices, etc. For some reason, this doesn't want to work for me.
Is there a GUI method to accomplishing this, or am I going to be stuck in CLI for this one? I tried using NetworkManager for WiFi and it worked great. I couldn't find a solution for bluez5 management in cinnamon.
Last edited by FNtastic (2015-05-17 12:56:04)
Offline
I was just messing around with bluetooth last night so I'm feeling your pain. I got some stuff working, but I'm surprised by how primitive this support seems. If you're using Cinnamon, you're probably stuck with the CLI for now.
I had an experience removing/deleting the MAC of a bluetooth device yesterday and that was not a good thing because, like you, I couldn't find it again. I was trying to pair my Galaxy S5 and, after getting it paired, I wanted to go through the process one more time to practice. I removed the device without understanding what that command did. Similar to what you're seeing, that made it so that the S5 wouldn't show up no matter what I did. I was eventually able to get it back (and I will never remove it again, LOL). I had to make my computer discoverable and the device discoverable and then I was only able to get the MAC address to show up again on my computer by initiating the connection from my S5. It was a pain in the butt, but I finally got it back. I know you're pairing a mouse, but maybe it might help to make your mouse and your computer discoverable and try the process again to see if that will get the MAC address back in the list. If worse comes to worst, maybe you might be able to enter the MAC address manually?
I saw something in one of the outputs that you posted that reminded me of something that I read yesterday. Here are the lines from your output that caught my attention:
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# pair <MAC address>
Attempting to pair with <MAC address>
[CHG] Device <MAC address> Connected: yes
[CHG] Device <MAC address> Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
[bluetooth]# connect <MAC address>
Attempting to connect to <MAC address>
Failed to connect: org.bluez.Error.FailedThe part where the pair failed because the authentication was canceled is something that I saw when I didn't answer yes quickly enough to the pair requests on my computer and my S5. I'm wondering if your mouse has a security code/pin that you need to enter or accept. If not, I remembered reading in the wiki that sometimes mice (or other devices) don't have a security code/pin and, in those cases, you need to manually trust the device by using the command "trust". It would look something like this (I'm just typing this from memory):
[bluetoothctl]# power on
[bluetoothctl]# agent on
[bluetoothctl]# default-agent
[bluetoothctl]# discoverable on
[bluetoothctl]# scan on
[bluetoothctl]# pair <MAC address>
(Not sure if you need to or are able to reverse the order of these two commands. You might try trusting before pairing and see if that helps...)
[bluetoothctl]# trust <MAC address>
[bluetoothctl]# connect <MAC address>Anyway, hope some of that helps you. Let us know how it goes.
Offline
There is a `connect` button on a backside of my keyboard. Unless it's pressed, `scan on` won't find the device.
Also I use radio mouse with usb dongle, never had an issue, unlike with bluetooth keyboard.
Last edited by c0ffeeartc (2015-05-18 16:49:50)
Offline
Thank you guys for your posts. I really appreciate any help I get with this issue.
I've tried again. And, no matter what I attempt, I can't find other devices with the PC, and I can't find the PC with another device.
To address some common issues/concerns:
-I don't have a hardware switch
-The bluetooth card is verified working in other OS's (and apparently worked on this one at some point, it was able to find devices)
Here are my most recent attempts:
$ bluetoothctl
[NEW] Controller <MAC address> PC [default]
[bluetooth]# power on
[CHG] Controller <MAC address> Class: 0x00010c
Changing power on succeeded
[CHG] Controller <MAC address> Powered: yes
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller <MAC address> Discovering: yes
[bluetooth]# scan off
Discovery stopped
[CHG] Controller <MAC address> Discovering: no
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller <MAC address> Discoverable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller <MAC address> Discovering: yes
[bluetooth]# scan off
Discovery stopped
[CHG] Controller <MAC address> Discovering: no
[bluetooth]# discoverable off
Changing discoverable off succeeded
[CHG] Controller <MAC address> Discoverable: no
[bluetooth]# discoverable on
Changing discoverable on succeeded
[CHG] Controller <MAC address> Discoverable: yes
[CHG] Controller <MAC address> Discoverable: noJust updated to 4.0.3 while typing this. Going to restart and try again. Will update with results.
Offline
Unfortunately, 4.0.3 did not yield better results. I'm getting the same as above. Won't find anything during scan.
Here is the bluetooth status from systemctl:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2015-05-18 18:28:10 EDT; 1min 55s ago
Docs: man:bluetoothd(8)
Main PID: 294 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─294 /usr/lib/bluetooth/bluetoothd
May 18 18:28:10 PC bluetoothd[294]: Error adding Link Loss service
May 18 18:28:10 PC bluetoothd[294]: Not enough free handles to register service
May 18 18:28:10 PC bluetoothd[294]: Not enough free handles to register service
May 18 18:28:10 PC bluetoothd[294]: Not enough free handles to register service
May 18 18:28:10 PC bluetoothd[294]: Current Time Service could not be registered
May 18 18:28:10 PC bluetoothd[294]: gatt-time-server: Input/output error (5)
May 18 18:28:10 PC bluetoothd[294]: Not enough free handles to register service
May 18 18:28:10 PC bluetoothd[294]: Not enough free handles to register service
May 18 18:28:10 PC bluetoothd[294]: Sap driver initialization failed.
May 18 18:28:10 PC bluetoothd[294]: sap-server: Operation not permitted (1)Offline
That stinks. Sorry to hear that that stuff didn't help. I'm trying to recall what, exactly, I had to do to get my device to display again. I was getting frustrated at the time so I was starting to just try different things and not being too methodical about it. I may have removed or unpaired my computer from my device as well. I've never tried working with bluetooth mice or keyboards so I'm not sure if this is possible with those types of devices, but is there any way to remove your computer from the keyboard or the mouse's "memory" so that you're starting fresh on both devices?
Offline
Wait a minute... I just re-read one of your posts and I just want to get something clarified. For your mouse, you mentioned that you have a USB dongle with the mouse. Does that dongle do the bluetooth connection? Do you have a separate bluetooth card in your computer? If so, you could be dealing with multiple bluetooth controllers. If that's the case, you'll probably need to make sure that you've selected the controller that you want to work with in bluetoothctl. You can find the available controllers with the following command:
[bluetoothctl]# list
<list of controllers here>
[bluetoothctl]# select <controller MAC address>
(then go through the rest of the process that we've discussed above)Also, the Arch wiki has some parts that might be helpful:
The troubleshooting section: https://wiki.archlinux.org/index.php/Bl … leshooting
Specifically, troubleshooting bluetooth USB dongles: https://wiki.archlinux.org/index.php/Bl … USB_Dongle
Also, the wiki page specifically covering bluetooth mice: https://wiki.archlinux.org/index.php/Bluetooth_mouse
If you've read through any of those pages and tried those things, tell us here what you've read and tried so that we (or others) can get a better idea of what you've done and maybe that will indicate what to try next.
Offline
Wait a minute... I just re-read one of your posts and I just want to get something clarified. For your mouse, you mentioned that you have a USB dongle with the mouse. Does that dongle do the bluetooth connection? Do you have a separate bluetooth card in your computer? If so, you could be dealing with multiple bluetooth controllers. If that's the case, you'll probably need to make sure that you've selected the controller that you want to work with in bluetoothctl. You can find the available controllers with the following command:
[bluetoothctl]# list <list of controllers here> [bluetoothctl]# select <controller MAC address> (then go through the rest of the process that we've discussed above)Also, the Arch wiki has some parts that might be helpful:
The troubleshooting section: https://wiki.archlinux.org/index.php/Bl … leshooting
Specifically, troubleshooting bluetooth USB dongles: https://wiki.archlinux.org/index.php/Bl … USB_Dongle
Also, the wiki page specifically covering bluetooth mice: https://wiki.archlinux.org/index.php/Bluetooth_mouseIf you've read through any of those pages and tried those things, tell us here what you've read and tried so that we (or others) can get a better idea of what you've done and maybe that will indicate what to try next.
No, I don't have a dongle. It's a built-in miniPCIe card with wifi/BT combo. And a bluetooth mouse. It was able to find devices before, but isn't anymore. I tried the 'list' then 'select' command as you've stated here. Same results unfortunately. Doesn't find anything. I'll dig through the troubleshooting section to see if anything.
EDIT: I couldn't find anything in troubleshooting that pertains to my issue unfortunately. Thank you for the suggestion.
Last edited by FNtastic (2015-05-18 23:37:40)
Offline
I am experiencing the same (or a similar) issue. I'm not using it very often, only for external audio but it was working fine last time I checked (maybe 3 weeks ago).
Some update must have broken it I guess...
Here's my output, sorry for not being of any help.
$ bluetoothctl
[NEW] Device 88:C6:26:07:19:E8 UE BOOM
[bluetooth]# connect 88:C6:26:07:19:E8
Attempting to connect to 88:C6:26:07:19:E8
Failed to connect: org.bluez.Error.Failed$ 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-05-20 22:04:24 CEST; 11min ago
Docs: man:bluetoothd(8)
Main PID: 432 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─432 /usr/lib/bluetooth/bluetoothd
May 20 22:04:24 popeye bluetoothd[432]: Not enough free handles to register service
May 20 22:04:24 popeye bluetoothd[432]: Not enough free handles to register service
May 20 22:04:24 popeye bluetoothd[432]: Not enough free handles to register service
May 20 22:04:24 popeye bluetoothd[432]: Current Time Service could not be registered
May 20 22:04:24 popeye bluetoothd[432]: gatt-time-server: Input/output error (5)
May 20 22:04:24 popeye bluetoothd[432]: Not enough free handles to register service
May 20 22:04:24 popeye bluetoothd[432]: Not enough free handles to register service
May 20 22:04:24 popeye bluetoothd[432]: Sap driver initialization failed.
May 20 22:04:24 popeye bluetoothd[432]: sap-server: Operation not permitted (1)
May 20 22:07:03 popeye bluetoothd[432]: a2dp-sink profile connect failed for 88:C6:26:07:19:E8: Protocol not availableLast edited by skiwi (2015-05-20 20:20:51)
Offline
I remember a few days ago when I was playing with the bluetooth, I was searching all through the forums here and I swear that I came across a thread mentioning a problem with bluez and the 4.0.x kernel. I can't remember if the issue was with the 4.0.1 or 4.0.3 kernel, but the person was basically saying that any devices that they had which were paired and connected before the v4 kernel were able to work, but anything they tried to add after that wouldn't work. The eventual conclusion of the thread was to either downgrade to one of the v3 kernels or go back to an LTS kernel or wait for an update. I've tried searching for the thread in the forum search and in Google but I can't find it. I wish that I could find it so that I could give you better details, but I just thought that I'd pass the info along, even if it is almost hearsay. Would you be able to (or open to) revert to a previous version of the kernel (not sure what the LTS kernel is on right now) to see if that helped?
Offline
I remember a few days ago when I was playing with the bluetooth, I was searching all through the forums here and I swear that I came across a thread mentioning a problem with bluez and the 4.0.x kernel. I can't remember if the issue was with the 4.0.1 or 4.0.3 kernel, but the person was basically saying that any devices that they had which were paired and connected before the v4 kernel were able to work, but anything they tried to add after that wouldn't work. The eventual conclusion of the thread was to either downgrade to one of the v3 kernels or go back to an LTS kernel or wait for an update. I've tried searching for the thread in the forum search and in Google but I can't find it. I wish that I could find it so that I could give you better details, but I just thought that I'd pass the info along, even if it is almost hearsay. Would you be able to (or open to) revert to a previous version of the kernel (not sure what the LTS kernel is on right now) to see if that helped?
Support was added for my chip in the 4+ kernel according to everything I've read... Including Broadcom wifi and bluetooth.
Offline
[ 2.710066] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-13d3-3404.hcd not found
Perhaps you need to pull in a proprietary firmware file? See: http://osdir.com/ml/kernel-team/2015-03/msg00069.html.
Offline
I found this to support my statement. I realize that it's Ubuntu related and not Arch.
https://lists.launchpad.net/touch-packa … 76560.html
Offline
Did you download and copy the hcd file to your /lib/firmware/brcm directory? Based on that message from your logs, it looks like its not being found.
Offline
It appears that patch is only relevant to 3.x kernels. http://permalink.gmane.org/gmane.linux. … rnel/55944
Also, read the thread in the other user's post. His references a 3.x kernel as well. None are related to 4.x kernel.
Last edited by FNtastic (2015-05-22 00:13:44)
Offline
I was able to get this far with 4.0.4:
[bluetooth]# select <MAC address>
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller <MAC address> Discovering: yes
[NEW] Device <MAC address> Microsoft Bluetooth Notebook Mouse 5000
[bluetooth]# connect <MAC address>
Attempting to connect to <MAC address>
Failed to connect: org.bluez.Error.FailedStill unable to pair or connect. But, able to scan again... Although discovery seems VERY SLOW.
Offline
But it appears that your system is still looking for this firmware file. I'm reading the bug reports a little differently. I think late in the 3.x kernel series, the ability to load the firmware file was added - not that the firmware itself was added (maybe for proprietary reasons?).
Look in your journal again for references to a missing BCM20702A0-13d3-3404.hcd file.
Offline
So, I installed b43-firmware using yaourt. This is now the dmesg:
[ 2.384390] bluetooth hci0: Direct firmware load for brcm/BCM20702A0-13d3-3404.hcd failed with error -2I noticed this in the documentation but didn't know what to make of it "To avoid a possible erroneous detection of the model, blacklist the non-used driver." What other driver do I need to blacklist?
Last edited by FNtastic (2015-05-22 02:04:28)
Offline
Just updated to 4.0.4-2. Still having same issues. Not discoverable, and not able to pair with other devices.
$ dmesg | grep bluetooth
[ 2.357233] bluetooth hci0: Direct firmware load for brcm/BCM20702A0-13d3-3404.hcd failed with error -2$ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2015-05-22 19:30:41 EDT; 8min ago
Docs: man:bluetoothd(8)
Main PID: 290 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─290 /usr/lib/bluetooth/bluetoothd
May 22 19:30:41 PC bluetoothd[290]: Error adding Link Loss service
May 22 19:30:41 PC bluetoothd[290]: Not enough free handles to register service
May 22 19:30:41 PC bluetoothd[290]: Not enough free handles to register service
May 22 19:30:41 PC bluetoothd[290]: Not enough free handles to register service
May 22 19:30:41 PC bluetoothd[290]: Current Time Service could not be registered
May 22 19:30:41 PC bluetoothd[290]: gatt-time-server: Input/output error (5)
May 22 19:30:41 PC bluetoothd[290]: Not enough free handles to register service
May 22 19:30:41 PC bluetoothd[290]: Not enough free handles to register service
May 22 19:30:41 PC bluetoothd[290]: Sap driver initialization failed.
May 22 19:30:41 PC bluetoothd[290]: sap-server: Operation not permitted (1)Offline
So, I installed b43-firmware using yaourt.
Why did you install this package? As far as I can tell, it doesn't include the BCM20702A0-13d3-3404.hcd file that you need. According to http://permalink.gmane.org/gmane.linux. … rnel/55944, you need to get the file from a windows driver package. One of the other links also had a shared dropbox file that you could get. I believe that all you need to do is copy that file to your /lib/firmware/bcrm directory.
You may need to undo the installation of b43-firmware now.
EDIT: I don't have any experience with broadcom drivers. I was simply pointing out that the error message in your journal was indicating a missing file.
Last edited by toz (2015-05-23 00:06:56)
Offline
FNtastic wrote:So, I installed b43-firmware using yaourt.
Why did you install this package? As far as I can tell, it doesn't include the BCM20702A0-13d3-3404.hcd file that you need. According to http://permalink.gmane.org/gmane.linux. … rnel/55944, you need to get the file from a windows driver package. One of the other links also had a shared dropbox file that you could get. I believe that all you need to do is copy that file to your /lib/firmware/bcrm directory.
You may need to undo the installation of b43-firmware now.
EDIT: I don't have any experience with broadcom drivers. I was simply pointing out that the error message in your journal was indicating a missing file.
I see what you are saying. However, I don't believe that's the case. The 4.0 kernel is supposed to include the appropriate drivers/firmware... I shouldn't have to patch or download anything according to everything I'm reading. Thank you for pointing that out. However, you can probably understand my hesitation to use something made for 3.x kernel on a 4.x kernel.
Offline
I loaded the file you suggested. I no longer get the error in dmesg. But, now I get this:
$ bluetoothctl
[bluetooth]# power on
No default controller availableOffline
I removed b43-firmware using yaourt. These are my results now:
$ sudo systemctl start bluetooth
$ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2015-05-22 20:46:10 EDT; 1s ago
Docs: man:bluetoothd(8)
Main PID: 744 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─744 /usr/lib/bluetooth/bluetoothd
May 22 20:46:10 PC systemd[1]: Starting Bluetooth service...
May 22 20:46:10 PC bluetoothd[744]: Bluetooth daemon 5.30
May 22 20:46:10 PC systemd[1]: Started Bluetooth service.
May 22 20:46:10 PC bluetoothd[744]: Starting SDP server
May 22 20:46:10 PC bluetoothd[744]: Bluetooth management interface 1.8 initialized
$ bluetoothctl
[bluetooth]# power on
No default controller available
[bluetooth]# EDIT: I'm also getting this in my dmesg now (don't remember seeing this before, and may have to do with my USB stick being inserted?):
[ 16.450641] usb 1-1.2: device descriptor read/64, error -110
[ 31.627537] usb 1-1.2: device descriptor read/64, error -110
[ 31.797530] usb 1-1.2: new full-speed USB device number 4 using ehci-pci
[ 46.871149] usb 1-1.2: device descriptor read/64, error -110
[ 62.048256] usb 1-1.2: device descriptor read/64, error -110
[ 62.218325] usb 1-1.2: new full-speed USB device number 5 using ehci-pci
[ 67.237322] usb 1-1.2: device descriptor read/8, error -110
[ 72.356395] usb 1-1.2: device descriptor read/8, error -110
[ 72.526377] usb 1-1.2: new full-speed USB device number 6 using ehci-pci
[ 77.545414] usb 1-1.2: device descriptor read/8, error -110
[ 82.664476] usb 1-1.2: device descriptor read/8, error -110
[ 82.767796] usb 1-1-port2: unable to enumerate USB deviceAnd this is the Bluetooth results:
[ 83.075682] usbcore: registered new interface driver uvcvideo
[ 83.075687] USB Video Class driver (1.1.1)
[ 218.181235] Bluetooth: Core ver 2.20
[ 218.181254] NET: Registered protocol family 31
[ 218.181256] Bluetooth: HCI device and connection manager initialized
[ 218.181261] Bluetooth: HCI socket layer initialized
[ 218.181265] Bluetooth: L2CAP socket layer initialized
[ 218.181272] Bluetooth: SCO socket layer initialized
[ 218.186869] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 218.186873] Bluetooth: BNEP filters: protocol multicast
[ 218.186877] Bluetooth: BNEP socket layer initialized
[ 467.920320] usbcore: registered new interface driver btusbLast edited by FNtastic (2015-05-23 00:58:51)
Offline