You are not logged in.
Hello gents,
I've got a problem with my bluetooth.
13:05 faceless ~ $ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since sab 2015-05-16 12:20:26 CEST; 45min ago
Docs: man:bluetoothd(8)
Main PID: 3293 (bluetoothd)
Status: "Running"
CGroup: /system.slice/bluetooth.service
└─3293 /usr/lib/bluetooth/bluetoothd
mag 16 12:20:26 Archibald systemd[1]: Starting Bluetooth service...
mag 16 12:20:26 Archibald bluetoothd[3293]: Bluetooth daemon 5.30
mag 16 12:20:26 Archibald systemd[1]: Started Bluetooth service.
mag 16 12:20:26 Archibald bluetoothd[3293]: Starting SDP server
mag 16 12:20:26 Archibald bluetoothd[3293]: Bluetooth management interface 1.8 initializedbluetooth.service is normally running
12:50 faceless ~ $ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
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 001 Device 004: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 001 Device 003: ID 413c:8161 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 hubDell wireless 365 is not shown, missing driver?
13:09 faceless ~ $ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: noNo hard or soft block on bluetooth device.
12:50 faceless ~ $ lsusb -t
/: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Application Specific Interface, Driver=, 12M
|__ Port 1: Dev 2, If 1, Class=Chip/SmartCard, Driver=, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M
|__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M12:54 faceless ~ $ hcitool dev
Devices:12:51 faceless ~ $ lsmod |grep blue
3:bluetooth 442368 5 bnep
38:rfkill 24576 6 cfg80211,bluetooth,dell_laptop
71:crc16 16384 2 ext4,bluetoothThe bluetooth device is seen as a usb hub, for some HIDs. After some research i found out this is because in some cases the bluetooth device is set as a HID to allow keyboard and mouse to connect even if the system doesn't support bluetooth. To be used as a standard bluetooth device by the bluetooth stack ( eg. bluez ) it should be switched to HCI mode.
i tried this command but there's no device ( i tried just in case blindly throwing in hci1, hci2 etc hoping something would change but nope ).
12:54 faceless ~ $ sudo hciconfig hci0 up
[sudo] password di faceless:
Can't get device info: No such deviceI also tried using hid2hci utility provided by bluez-utils package but it ask for "sys device path" and i have no idea how to fetch it.
The strange thing is that the bluetooth LED is on.
All attempts to find bcm2046b1 or dell wireless 365 bluetooth drivers online have been unsuccessful, only found windows versions.
Also, i know there is a way to solve this problem: if you have a dual boot you can boot in windows, install or update the bluetooth drivers from there and when you come back the device is recognized ( work with a virtual machine too ). The problem is, i don't dual boot and i refuse setting up a virtual machine every reboot just to have the system recognize the bluetooth.
I'll keep digging on the matter, maybe something will come up.
Any suggestion is welcome, if other dumps are needed ask and you'll be given.
Cheers! ![]()
EDIT:
I just rebooted the machine and now it seems to be working properly, it is recognized and everything works.
lsmod shows that btusb and rfcomm are now loaded.
lsusb shows the Dell Wireless 365 is now recognized.
I sincerely don't know what happened nor what i changed. Stupidly i tried too many things before rebooting so i can't really pinpoint the cause.
The thing that i remember changing explicitly was adding a line to /etc/dbus-1/system.d/bluetooth.conf:
<!-- This configuration file specifies the required security policies
for Bluetooth core daemon to work. -->
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<!-- ../system.conf have denied everything, so we just punch some holes -->
<policy user="root">
<allow own="org.bluez"/>
<allow send_destination="org.bluez"/>
<allow send_interface="org.bluez.Agent"/>
<allow send_interface="org.bluez.PasskeyAgent"/> <------- Added this line here.
.....
# other stuff
.......
</policy>
<policy at_console="true">
<allow send_destination="org.bluez"/>
</policy>
<policy context="default">
<deny send_destination="org.bluez"/>
</policy>
</busconfig>EDIT 2:
I add the links to the threads where i found the solution, since there were some more possible fixes if others have my same problem.
http://www.linuxquestions.org/questions … 00-787691/
http://www.linuxquestions.org/questions … es-759397/
https://idebian.wordpress.com/2008/07/0 … -in-linux/
![]()
Last edited by TheCreeL (2015-05-16 14:15:41)
Offline