LinuxQuestions.org - cannot get bluetooth working

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - cannot get bluetooth working (https://www.linuxquestions.org/questions/slackware-14/cannot-get-bluetooth-working-4175607979/)

cannot get bluetooth working

lsusb

Quote:

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 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 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
Bus 005 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 002: ID 0b05:179d ASUSTek Computer, Inc. USB-N53 802.11abgn Network Adapter [Ralink RT3572]
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have the appropriate groups for my user. I have firmware for the Broadcom bluetooth device.

hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 5C:F3:70:60:02:66 ACL MTU: 1021:8 SCO MTU: 64:1
DOWN
RX bytes:6760 acl:0 sco:0 events:820 errors:0
TX bytes:72686 acl:0 sco:0 commands:818 errors:0

hciconfig hci0 up
Can't init device hci0: Invalid request code (56)

appreciate some help

Maybe You should try

Code:

rfkill

here are the results of that.

Quote:

bash-4.3# rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
bash-4.3#

I hate to be a wet blanket, but I could never get bluetooth to work in Linux.

When I get home, I'll look my setup. I've been using a heart rate monitor and several headsets over Bluetooth on a Slackware64 14.2 system without a lot of problems.

Are you trying this within a desktop environment? If so, which one?

So, as root, run

Code:

/etc/rc.d/rc.bluetooth stop

/etc/rc.d/rc.bluetooth start

and provide the output.

You should look inside /var/log/messages to see what bluetooth logged while it was coming up.

Once you're sure that bluetoothd is running, then try as your normal user these commands (if one of them fails to work, there's no need to continue running the remainder). The last command will make your adapter look for devices with which to pair.

Code:

dbus-send --system --print-reply --dest="org.freedesktop.DBus" /org/freedesktop/DBus org.freedesktop.DBus.ListActivatableNames

dbus-send --system --print-reply --type=method_call --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames

dbus-send --system --print-reply --dest=org.bluez /org/bluez org.freedesktop.DBus.Introspectable.Introspect

dbus-send --system --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter1.StartDiscovery

At this point, we'd have to know what you want to do.

kde on 14.2 slackware.
I had this running on debian wheezy and slackware 14.1.

bash-4.3# sh rc.bluetooth stop
bash-4.3# sh rc.bluetooth start
Starting Bluetooth services: bluetoothd hciconfig sdptool hciattach
bash-4.3#

[14088.321461] Bluetooth: hci0: BCM: chip id 63
[14088.338627] Bluetooth: hci0: Broadcom Bluetooth Device
[14088.340566] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1764
[14089.497752] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1764
[14089.514746] Bluetooth: hci0: Broadcom Bluetooth Device
[14103.598071] Bluetooth: hci0: BCM: chip id 63
[14103.615235] Bluetooth: hci0: Broadcom Bluetooth Device
[14103.617295] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1764
[14104.771347] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1764
[14104.788218] Bluetooth: hci0: Broadcom Bluetooth Device

I would like to use bluetooth headset,ftp,remote control and some other stuff

I'd have expected more in the logs. (/var/log/messages)

Code:

Jun 15 20:11:44 cranium kernel: [ 1402.134207] usb 2-3.1: new full-speed USB device number 6 using ehci-pci

Jun 15 20:11:44 cranium kernel: [ 1402.283852] usb 2-3.1: New USB device found, idVendor=0a12, idProduct=0001

Jun 15 20:11:44 cranium kernel: [ 1402.283864] usb 2-3.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0

Jun 15 20:11:44 cranium kernel: [ 1402.283871] usb 2-3.1: Product: CSR8510 A10

Jun 15 20:11:44 cranium kernel: [ 1402.352363] Bluetooth: Core ver 2.21

Jun 15 20:11:44 cranium kernel: [ 1402.352403] NET: Registered protocol family 31

Jun 15 20:11:44 cranium kernel: [ 1402.352408] Bluetooth: HCI device and connection manager initialized

Jun 15 20:11:44 cranium kernel: [ 1402.352418] Bluetooth: HCI socket layer initialized

Jun 15 20:11:44 cranium kernel: [ 1402.352425] Bluetooth: L2CAP socket layer initialized

Jun 15 20:11:44 cranium kernel: [ 1402.352439] Bluetooth: SCO socket layer initialized

Jun 15 20:11:44 cranium kernel: [ 1402.368144] usbcore: registered new interface driver btusb

Jun 15 20:14:19 cranium bluetoothd[3586]: Bluetooth daemon 5.40

Jun 15 20:14:19 cranium bluetoothd[3586]: Starting SDP server

Jun 15 20:14:19 cranium kernel: [ 1556.715043] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Jun 15 20:14:19 cranium kernel: [ 1556.715052] Bluetooth: BNEP filters: protocol multicast

Jun 15 20:14:19 cranium kernel: [ 1556.715063] Bluetooth: BNEP socket layer initialized

Jun 15 20:14:19 cranium bluetoothd[3586]: Bluetooth management interface 1.10 initialized

Jun 15 20:14:19 cranium kernel: [ 1556.771613] Bluetooth: RFCOMM TTY layer initialized

Jun 15 20:14:19 cranium kernel: [ 1556.771629] Bluetooth: RFCOMM socket layer initialized

Jun 15 20:14:19 cranium kernel: [ 1556.771645] Bluetooth: RFCOMM ver 1.11

What's in your /etc/bluetooth directory?

Quote:

I hate to be a wet blanket, but I could never get bluetooth to work in Linux.

Bluetooth works fine for me on Magiea. I have no interest in using it on my Slackware box, so I can't say . . . .

But my Slackware box shows up on my HTC One phone when I start KDE Connect, so I reckon it's working.

By any chance is BT working when logged as root?
ciao

Quote:

Originally Posted by urka58 (Post 5723549)

By any chance is BT working when logged as root?
ciao

wish it was then it would probably be permission error.

Quote:

What's in your /etc/bluetooth directory?

Quote:

bash-4.3$ cd /etc/bluetooth/
bash-4.3$ ls
input.conf main.conf network.conf proximity.conf uart.conf
bash-4.3$

Were there any logs similar to the ones that I had posted earlier in /var/log/messages?

nope not that I have seen but will double check

Quote:

Originally Posted by RandomTroll (Post 5723209)

I hate to be a wet blanket, but I could never get bluetooth to work in Linux.

It has worked fine for me for the last several years, that is, ever since I started
transferring photos from and to the various cellphones I've owned over the same period.

Quote:

Originally Posted by mrapathy (Post 5723837)

nope not that I have seen but will double check

The BNEP and RFCOMM stuff would be needed for BT to work.