Bluetooth not adapter not found [Solved]

Issues Related to Hardware (Sound, Video, Printers, Scanners, Webcams, Touchpads, Keyboards, Sensors, Drives, GRUB, etc.)

Moderator: Moderators

riyasmjgeo
Baby Hen
Posts: 15
Joined: Thu Jan 26, 2017 23:06

Bluetooth adapter not found

Post by riyasmjgeo » Mon Feb 06, 2017 5:59

Hi all,

Please help me to enable my Bluetooth driver. It is mentioning as "no bluetooth adapters have been found". Did all upgrades and updates.

Sabayon 16.11AMD64 KDE
Laptop: Lenovo G500
--------------------------------------------------

Code: Select all

sabayon xplorer # lspci -k
02:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
        Subsystem: Lenovo AR9485 Wireless Network Adapter
        Kernel driver in use: ath9k
        Kernel modules: ath9k
When tried to start

Code: Select all

sabayon xplorer # /usr/libexec/bluetooth/bluetoothd
D-Bus setup failed: Connection ":1.76" is not allowed to own the service "org.bluez" due to security policies in the configuration file
Another one

Code: Select all

sabayon xplorer # lsmod |grep btusb
btusb                  30984  0
btrtl                   4869  1 btusb
btbcm                   6139  1 btusb
btintel                 7303  1 btusb
bluetooth             420894  6 btrtl,btintel,btbcm,ath3k,btusb

Code: Select all

[email protected] ~ $ bluetoothctl
Waiting to connect to bluetoothd...
It is not blocked

Code: Select all

sabayon xplorer # rfkill list
0: ideapad_wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: ideapad_bluetooth: Bluetooth
        Soft blocked: no
        Hard blocked: no
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
6: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

When tried starting

Code: Select all

sabayon xplorer # systemctl start bluetooth
Job for bluetooth.service failed because the control process exited with error code. See "systemctl status bluetooth.service" and "journalctl -xe" for details.

sabayon xplorer # journalctl -xe
Feb 06 10:16:31 sabayon bluetoothd[3833]: D-Bus setup failed: Connection ":1.85" is not allow
Feb 06 10:16:31 sabayon bluetoothd[3833]: Unable to get on D-Bus
Feb 06 10:16:31 sabayon systemd[1]: bluetooth.service: Main process exited, code=exited, stat
Feb 06 10:16:31 sabayon systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
Feb 06 10:16:31 sabayon systemd[1]: bluetooth.service: Unit entered failed state.
Feb 06 10:16:31 sabayon systemd[1]: bluetooth.service: Failed with result 'exit-code'.
Feb 06 10:16:31 sabayon polkitd[2089]: Unregistered Authentication Agent for unix-process:382
Feb 06 10:16:42 sabayon su[3835]: Successful su for root by xplorer
Feb 06 10:16:42 sabayon su[3835]: + /dev/pts/2 xplorer:root
Feb 06 10:16:42 sabayon su[3835]: pam_unix(su:session): session opened for user root by xplor
Feb 06 10:16:42 sabayon su[3835]: pam_systemd(su:session): Cannot create session: Already run
Feb 06 10:16:44 sabayon polkitd[2089]: Registered Authentication Agent for unix-process:3841:
Feb 06 10:16:44 sabayon systemd[1]: Starting Bluetooth service...
-- Subject: Unit bluetooth.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit bluetooth.service has begun starting up.
Feb 06 10:16:44 sabayon bluetoothd[3847]: Bluetooth daemon 5.43
Feb 06 10:16:44 sabayon bluetoothd[3847]: Unable to get on D-Bus
Feb 06 10:16:44 sabayon bluetoothd[3847]: D-Bus setup failed: Connection ":1.88" is not allow
Feb 06 10:16:44 sabayon systemd[1]: bluetooth.service: Main process exited, code=exited, stat
Feb 06 10:16:44 sabayon systemd[1]: Failed to start Bluetooth service.
-- Subject: Unit bluetooth.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit bluetooth.service has failed.
-- 
-- The result is failed.
Feb 06 10:16:44 sabayon systemd[1]: bluetooth.service: Unit entered failed state.
Feb 06 10:16:44 sabayon systemd[1]: bluetooth.service: Failed with result 'exit-code'.
Feb 06 10:16:44 sabayon polkitd[2089]: Unregistered Authentication Agent for unix-process:384
Feb 06 10:17:17 sabayon plasmashell[2531]: QXcbConnection: XCB error: 2 (BadValue), sequence:
Feb 06 10:17:17 sabayon plasmashell[2531]: QXcbConnection: XCB error: 2 (BadValue), sequence:
# My bluetooth.conf (/etc/dbus-1/system.d/bluetooth.conf) looks like
-----------------------------------------------------------------
<busconfig>

<!-- ../system.conf have denied everything, so we just punch some holes -->

<policy group="root">
<allow own="org.bluez"/>
<allow send_destination="org.bluez"/>
<allow send_interface="org.bluez.Agent"/>
<allow send_interface="org.bluez.PasskeyAgent"/>

</policy>
-----------------------------------------------------------------

# My bluetooth.service (/usr/lib64/systemd/system/bluetooth.service) is
-----------------------------------------------------------------
[Unit]
Description=Bluetooth service
Documentation=man:bluetoothd(8)
ConditionPathIsDirectory=/sys/class/bluetooth

[Service]
Type=dbus
BusName=org.bluez
ExecStart=/usr/libexec/bluetooth/bluetoothd
NotifyAccess=main
#WatchdogSec=10
#Restart=on-failure
CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
LimitNPROC=1
ProtectHome=true
ProtectSystem=full

[Install]
WantedBy=bluetooth.target
Alias=dbus-org.bluez.service

<policy at_console="true">
-----------------------------------------------------------------

# Another try

Code: Select all

sabayon xplorer # hciconfig -a
hci0:   Type: Primary  Bus: USB
        BD Address: 48:D2:24:3F:82:60  ACL MTU: 1022:8  SCO MTU: 183:5
        DOWN
        RX bytes:574 acl:0 sco:0 events:30 errors:0
        TX bytes:368 acl:0 sco:0 commands:30 errors:0
        Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF
        Link mode: SLAVE ACCEPT 
I made it UP by

Code: Select all

sabayon xplorer # hciconfig hci0 up
sabayon xplorer # hciconfig -a
hci0:   Type: Primary  Bus: USB
        BD Address: 48:D2:24:3F:82:60  ACL MTU: 1022:8  SCO MTU: 183:5
        UP RUNNING
        RX bytes:1148 acl:0 sco:0 events:60 errors:0
        TX bytes:736 acl:0 sco:0 commands:60 errors:0
        Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF
        Link mode: SLAVE ACCEPT
        Name: 'Bluetooth USB Host Controller'
        Class: 0x000000
But after restarting system it gets back to DOWN.
Also I felt weird on two lines of the above, which are

Code: Select all

Class: 0x000000
Name: 'Bluetooth USB Host Controller'
I am suffering with this problem since long time please please please help me get rid of this. I love this OS, I don't want to change it but bluetooth is necessary for me. :(
Advance thanks

riyasmjgeo
Baby Hen
Posts: 15
Joined: Thu Jan 26, 2017 23:06

Re: Bluetooth adapter not found

Post by riyasmjgeo » Tue Feb 07, 2017 12:15

Hello Guys,

Please help me to get out of this.. I am trying since weeks.

I found the bluetooth is showing under USB. Didn't understand whether this is having some connection with driver issue.

Code: Select all

sabayon xplorer # lsusb
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 003 Device 008: ID 0cf3:3004 Qualcomm Atheros Communications AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 5986:0294 Acer, Inc 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Somebody please help

Stupot
Sagely Hen
Posts: 1677
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: Bluetooth not adapter not found

Post by Stupot » Tue Feb 07, 2017 23:16

What is the output of this:

Code: Select all

# systemctl status bluetooth.service

Stupot
Sagely Hen
Posts: 1677
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: Bluetooth adapter not found

Post by Stupot » Tue Feb 07, 2017 23:51

Please don't open multiple threads about the same issue. I realize it's frustrating not getting a quick answer, but it isn't always easy to provide help.

riyasmjgeo
Baby Hen
Posts: 15
Joined: Thu Jan 26, 2017 23:06

Re: Bluetooth adapter not found

Post by riyasmjgeo » Wed Feb 08, 2017 3:10

Dear Stupot,

Sorry for that. But I thought this topic is more related to the Hardware issues so posted in this group other than Newbie group hoping there will be more experts to help. Didn't mean to disturb in any ways.

riyasmjgeo
Baby Hen
Posts: 15
Joined: Thu Jan 26, 2017 23:06

Re: Bluetooth not adapter not found

Post by riyasmjgeo » Wed Feb 08, 2017 3:24

Failed to start Bluetooth service :(

Code: Select all

[email protected] ~ $ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib64/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2017-02-08 07:47:11 IST; 1min 51s ago
     Docs: man:bluetoothd(8)
  Process: 2662 ExecStart=/usr/libexec/bluetooth/bluetoothd (code=exited, status=1/FAILURE)
 Main PID: 2662 (code=exited, status=1/FAILURE)
   Status: "Starting up"

Feb 08 07:47:11 sabayon systemd[1]: Starting Bluetooth service...
Feb 08 07:47:11 sabayon bluetoothd[2662]: Bluetooth daemon 5.43
Feb 08 07:47:11 sabayon bluetoothd[2662]: D-Bus setup failed: Connection ":1.54" is not allowed to own the service "org.bluez" due to security policies in the...ation file
Feb 08 07:47:11 sabayon systemd[1]: bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 07:47:11 sabayon systemd[1]: Failed to start Bluetooth service.
Feb 08 07:47:11 sabayon systemd[1]: bluetooth.service: Unit entered failed state.
Feb 08 07:47:11 sabayon systemd[1]: bluetooth.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.

Code: Select all

[email protected] ~ $ systemctl status bluetooth.service -l
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib64/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2017-02-08 07:47:11 IST; 2min 1s ago
     Docs: man:bluetoothd(8)
  Process: 2662 ExecStart=/usr/libexec/bluetooth/bluetoothd (code=exited, status=1/FAILURE)
 Main PID: 2662 (code=exited, status=1/FAILURE)
   Status: "Starting up"

Feb 08 07:47:11 sabayon systemd[1]: Starting Bluetooth service...
Feb 08 07:47:11 sabayon bluetoothd[2662]: Bluetooth daemon 5.43
Feb 08 07:47:11 sabayon bluetoothd[2662]: D-Bus setup failed: Connection ":1.54" is not allowed to own the service "org.bluez" due to security policies in the configuration file
Feb 08 07:47:11 sabayon systemd[1]: bluetooth.service: Main process exited, code=exited, status=1/FAILURE
Feb 08 07:47:11 sabayon systemd[1]: Failed to start Bluetooth service.
Feb 08 07:47:11 sabayon systemd[1]: bluetooth.service: Unit entered failed state.
Feb 08 07:47:11 sabayon systemd[1]: bluetooth.service: Failed with result 'exit-code'.

riyasmjgeo
Baby Hen
Posts: 15
Joined: Thu Jan 26, 2017 23:06

Re: Bluetooth not adapter not found

Post by riyasmjgeo » Wed Feb 08, 2017 8:00

I was following a link
I feel the firmware is good.

Code: Select all

sabayon xplorer # cd /lib/firmware/ar3k && ls
1020200      AthrBT_0x01020001.dfu  AthrBT_0x31010100.dfu    ramps_0x01020201_40.dfu
1020201      AthrBT_0x01020200.dfu  AthrBT_0x41020000.dfu    ramps_0x11020000_40.dfu
1020201coex  AthrBT_0x01020201.dfu  ramps_0x01020001_26.dfu  ramps_0x11020100_40.dfu
30000        AthrBT_0x11020000.dfu  ramps_0x01020200_26.dfu  ramps_0x31010000_40.dfu
30101        AthrBT_0x11020100.dfu  ramps_0x01020200_40.dfu  ramps_0x31010100_40.dfu
30101coex    AthrBT_0x31010000.dfu  ramps_0x01020201_26.dfu  ramps_0x41020000_40.dfu

Code: Select all

sabayon xplorer # ls -l /lib/firmware | grep ar3k
drwxr-xr-x  8 root root    4096 Feb  4 13:26 ar3k
-rw-r--r--  1 root root    2708 Jan  8 13:29 LICENSE.QualcommAtheros_ar3k
But they mentioned like
AR3012 over USB is supported through CONFIG_BT_ATH3K, merged upstream as of 3.0.9. Like AR3011 with SFLASH configuration, you need to add the VID/PID of your device in both the btusb.c blacklist and the ath3k.c support list to load AR3012 firmware. You can refer to what it's done for 0x0cf3/0x3004 one.

I don't understand this. Need some help

User avatar
Fitzcarraldo
Sagely Hen
Posts: 8113
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom
Contact:

Re: Bluetooth adapter not found

Post by Fitzcarraldo » Wed Feb 08, 2017 21:25

Moderator post: I merged the thread in the Beginners|Newbies Area with the thread in this shed (Hardware) and deleted duplicate posts. Posting the same problem in two different sheds causes unnecessary confusion.

riyasmjgeo
Baby Hen
Posts: 15
Joined: Thu Jan 26, 2017 23:06

Re: Bluetooth adapter not found

Post by riyasmjgeo » Thu Feb 09, 2017 16:32

Anyone please re-write the sentence in a form I could understand. So that I could try doing something from that. Sorry for the creation of multiple threads.

"AR3012 over USB is supported through CONFIG_BT_ATH3K, merged upstream as of 3.0.9. Like AR3011 with SFLASH configuration, you need to add the VID/PID of your device in both the btusb.c blacklist and the ath3k.c support list to load AR3012 firmware. You can refer to what it's done for 0x0cf3/0x3004 one."
Didn't understand anything out of it

riyasmjgeo
Baby Hen
Posts: 15
Joined: Thu Jan 26, 2017 23:06

Re: Bluetooth adapter not found

Post by riyasmjgeo » Sat Feb 11, 2017 3:01

Hurreeeeey,

It is started properly now. Don't know which got worked well.

Tried
1) echo "blacklist ath3k" | sudo tee /etc/modprobe.d/ath3k.conf
2) Reinstall bluez
3) Did something in /etc/bluetooth/main.conf
4) Many things before this boot

I feel it was SYSTEMD issue because after reinstalling bluez it prompted to update the file before reboot. (Thanks to sabayon auto-do things, love it)

Thanks to all. Thanks for all helps..Love SABAYON

Post Reply