You are not logged in.
Hello friends,
my internal bluetooth card doesn't power up although it should be usable following this post:
https://wiki.archlinux.org/index.php/De … _(4th_Gen)
Using an external card works, but this is somehow undesirable with such a fancy machine with KDE Plasma. Bluetooth was working under Windows 10 Home.
Kindly do the needful at the earliest! joking
Really appreciate any help !
[ ~]$ uname -a
Linux archbook 4.8.6-1-ARCH #1 SMP PREEMPT Mon Oct 31 18:51:30 CET 2016 x86_64 GNU/Linux
[ ~]$ lsmod | grep ath
ath10k_pci 45056 0
ath10k_core 282624 1 ath10k_pci
ath 28672 1 ath10k_core
mac80211 667648 1 ath10k_core
cfg80211 495616 3 mac80211,ath,ath10k_core
[~]$ lsmod | grep blue
bluetooth 487424 43 btrtl,hci_uart,btintel,btqca,bnep,btbcm,rfcomm,btusb
rfkill 20480 10 bluetooth,dell_laptop,cfg80211
crc16 16384 2 bluetooth,ext4
[ ~]$ lspci | grep At
3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
[ ~]$ lsusb | grep At
Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
[ ~]$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
[~]$ sudo hciconfig hci0 up
Can't init device hci0: Input/output error (5)
[ ~]$ pacman -Qs lue
local/bluedevil 1:5.8.3-1 (plasma)
Integrate the Bluetooth technology within KDE workspace and applications
local/bluez 5.43-1
Daemons for the bluetooth protocol stack
local/bluez-libs 5.43-1
Deprecated libraries for the bluetooth protocol stack
local/bluez-qt-git r424.359b02a-1 (kf5)
Qt wrapper for Bluez 5 DBus API
local/bluez-utils 5.43-1
Development and debugging utilities for the bluetooth protocol stack
local/geoclue2 2.4.4-1
Modular geoinformation service built on the D-Bus messaging system
local/perl 5.24.0-2 (base)
A highly capable, feature-rich programming language
local/pulseaudio-bluetooth 9.0-1
Bluetooth support for PulseAudio
local/qt5-connectivity 5.7.0-2 (qt qt5)
Provides access to Bluetooth hardware
local/sbc 1.3-1
Bluetooth Subband Codec (SBC) library
[ ~]$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Mi 2016-11-02 20:42:45 CET; 1h 29min ago
Docs: man:bluetoothd(8)
Main PID: 581 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
└─581 /usr/lib/bluetooth/bluetoothd
Nov 02 20:42:45 archbook bluetoothd[581]: Bluetooth daemon 5.43
Nov 02 20:42:45 archbook bluetoothd[581]: Starting SDP server
Nov 02 20:42:45 archbook systemd[1]: Started Bluetooth service.
Nov 02 20:42:45 archbook bluetoothd[581]: Bluetooth management interface 1.13 initialized
Nov 02 20:42:45 archbook bluetoothd[581]: Failed to obtain handles for "Service Changed" characteristic
Nov 02 20:42:45 archbook bluetoothd[581]: Sap driver initialization failed.
Nov 02 20:42:45 archbook bluetoothd[581]: sap-server: Operation not permitted (1)
Nov 02 20:42:51 archbook bluetoothd[581]: Endpoint registered: sender=:1.34 path=/MediaEndpoint/A2DPSource
Nov 02 20:42:51 archbook bluetoothd[581]: Endpoint registered: sender=:1.34 path=/MediaEndpoint/A2DPSink
Nov 02 20:44:53 archbook bluetoothd[581]: Failed to set mode: Failed (0x03)
Anyone with a clue?
Last edited by jinglejungle (2016-11-03 22:09:58)
Offline
No device is shown in hcitool:
[ ~]$ hcitool dev
Devices:
HCI0 is down:
~]$ hciconfig -a hci0
hci0: Type: Primary Bus: USB
BD Address: 9C:B6:D0:11:17:72 ACL MTU: 1024:8 SCO MTU: 50:8
DOWN
RX bytes:603 acl:0 sco:0 events:32 errors:0
TX bytes:375 acl:0 sco:0 commands:32 errors:0
Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Beeing funny:
[ ~]$ hcitool scan
Device is not available: No such device
Failing to access otp - whatever that means...
[~]$ dmesg | grep -i blue
[ 8.844149] Bluetooth: Core ver 2.21
[ 8.844158] Bluetooth: HCI device and connection manager initialized
[ 8.844160] Bluetooth: HCI socket layer initialized
[ 8.844161] Bluetooth: L2CAP socket layer initialized
[ 8.844164] Bluetooth: SCO socket layer initialized
[ 8.854386] Bluetooth: HCI UART driver ver 2.3
[ 8.854387] Bluetooth: HCI UART protocol H4 registered
[ 8.854388] Bluetooth: HCI UART protocol BCSP registered
[ 8.854388] Bluetooth: HCI UART protocol LL registered
[ 8.854389] Bluetooth: HCI UART protocol ATH3K registered
[ 8.854389] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 8.854412] Bluetooth: HCI UART protocol Intel registered
[ 8.854422] Bluetooth: HCI UART protocol BCM registered
[ 8.854422] Bluetooth: HCI UART protocol QCA registered
[ 8.854423] Bluetooth: HCI UART protocol AG6XX registered
[ 10.202728] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000302.bin
[ 10.202728] Bluetooth: hci0: QCA: patch rome 0x302 build 0x138, firmware rome 0x302 build 0x111
[ 10.230660] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin
[ 10.626494] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 10.626496] Bluetooth: BNEP filters: protocol multicast
[ 10.626498] Bluetooth: BNEP socket layer initialized
[ 16.761201] Bluetooth: RFCOMM TTY layer initialized
[ 16.761207] Bluetooth: RFCOMM socket layer initialized
[ 16.761210] Bluetooth: RFCOMM ver 1.11
[ 322.382183] Bluetooth: hci0: Failed to access otp area (-108)
Last edited by jinglejungle (2016-11-04 11:34:19)
Offline
Turns out it was related to Power Saving Software.
Namely TLP in this case.
Deactivating it solved it for me.
Cheers!
Offline
Hi,
I find uninstalling TLP for this reason a bit overkill. I would rather blacklist the device from TLP configuration (as suggested in TLP FAQ).
> $ tlp-stat -u | grep -i btusb
Bus 001 Device 002 ID 0cf3:e300 control = on, autosuspend_delay_ms = 2000 -- Qualcomm Atheros Communications (btusb)
Add the device ID to USB blacklist from TLP:
> $ grep ^USB_BLACKLIST= /etc/default/tlp
USB_BLACKLIST="0cf3:e300"
Reboot or apply the new setting:
> # tlp usb
Your bluetooth adapter should be working fine now.
Offline
Thank you gilbs!
I'll put the nuke back in its missile silo.
Offline