You are not logged in.
Hello all,
I have a notebook (Dell Studio 1555) with an internal bluetooth adapter (dell 370, if I remember correctly), that I'm unable to set up in Gnome 3.10.
It has worked before under KDE 4.10, but I think it stopped working under KDE 4.11, prior to switching to Gnome, though I'm not sure.
Here are some outputs I'm getting:
[adamdagan@admdgn ~]$ lsusb
Bus 008 Device 004: ID 0781:74e5 SanDisk Corp.
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58)
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 003: ID 0c45:63ea Microdia
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick
Bus 001 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub[adamdagan@admdgn ~]$ dmesg | grep Blue
[ 17.706430] Bluetooth: Core ver 2.16
[ 17.706452] Bluetooth: HCI device and connection manager initialized
[ 17.706463] Bluetooth: HCI socket layer initialized
[ 17.706466] Bluetooth: L2CAP socket layer initialized
[ 17.706472] Bluetooth: SCO socket layer initialized
[ 17.889299] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 17.889313] Bluetooth: BNEP socket layer initialized[adamdagan@admdgn ~]$ sudo systemctl status bluetooth -l
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Sun 2013-11-03 23:10:49 IST; 10h ago
Docs: man:bluetoothd(8)
Main PID: 487 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─487 /usr/lib/bluetooth/bluetoothd
Nov 03 23:10:49 admdgn bluetoothd[487]: Bluetooth daemon 5.10
Nov 03 23:10:49 admdgn systemd[1]: Started Bluetooth service.
Nov 03 23:10:49 admdgn bluetoothd[487]: Starting SDP server
Nov 03 23:10:50 admdgn bluetoothd[487]: Bluetooth management interface 1.3 initialized[adamdagan@admdgn /]$ hcitool dev
Devices:The Gnome applet reads "no bluetooth adapter found"
Thanks, Adam.
Last edited by adam777 (2013-11-21 08:32:51)
Offline
Probably connected to this: https://wiki.archlinux.org/index.php/Bl … _not_found
Offline
Hi adam,
I'm running 64bit Arch on a Studio 1557 with an integrated usb bluetooth adapter (BCM2046).
In 2011 I had the very same problem you describe and got it fixed. Let me explain:
The bluetooth adapter has 2 modes of operation: HID mode and HCI mode.
In HID mode, it presents itself as a keyboard/mouse input device (in your case 413c:815[8/7]).
This allows you to use e.g. a bluetooth mouse that has been paired earlier - even if your OS doesn't support bluetooth.
In HCI mode, the device presents itself as a regular bluetooth adapter which can be used by your bluetooth stack (e.g. bluez) - that's what we want.
The problem back in 2011 was, that my adapter would default to HID mode and to switch it to HCI mode I had to use the 'hid2hci' tool (now part of bluez-utils).
For some time now bluez ships a udev rule which takes care of switching modes so everything worked flawlessly.
A couple of weeks ago, however, the problem resurfaced and I haven't found a fix yet.
I noticed that the udev rule isn't triggered anymore and running hid2hci (/lib/udev/hid2hci) manually doesn't work either (gives an error saying 'unable to handle [devpath]').
The only way to use the bluetooth adapter in arch for me is to boot Windows inside a Virtual machine, attach the USB touchpad device (the HID proxy) and let Windows switch it to HCI mode.
This, however, only lasts until I reboot/resume from standby.
I believe this regression was caused by a package upgrade, since an older arch installation I had lying around still recogniced the adapter while an up-to-date installation wouldn't.
Unfortunately, said lecacy installation is now gone and downgrading arch to a point before the regression doesn't seem feasible.
Any suggestions are more than welcome!
So long,
rev
Last edited by revinary (2013-11-05 11:45:56)
Offline
Thanks for the pointers, ijanos and revinary.
I tried hid2hci but could not get it to work either.
I'll post again if something changes.
Offline
I just run a system upgrade after a few days away from my Laptop.
After a reboot my adapter is now working. I suppose the reason is bluez 5.11.
Thanks all, marking as solved.
Offline
I had the same problem, and it turns out you need to install bluez-hid2hci for this to work.
I guess this means bluez-hid2hci should be a dependency of bluez, because if it's not installed, bluetooth won't work out of the box for people with this sort of hardware.
Offline