You are not logged in.

#1 2017-01-22 20:42:26

LazyLucretia
Member
Registered: 2016-01-28
Posts: 39

Bluetooth issues on my laptop

I have an Asus K56CB laptop with integrated Bluetooth. I don't even know where to start since this computer suprises me with a new problem every time I try to connect something with Bluetooth.
Let's start with a new example. I just booted up my laptop, wireless light which indicates both wi-fi and bluetooth is on. I tried to enable Bluetooth from the Bluetooth Settings in Gnome and nothing happened, it just stayed disabled.

systemctl status bluetooth.service :

● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2017-01-22 22:16:53 +03; 41min ago
     Docs: man:bluetoothd(8)
 Main PID: 663 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─663 /usr/lib/bluetooth/bluetoothd

Oca 22 22:17:08 K56-CB bluetoothd[663]: Failed to obtain handles for "Service Changed" characteristic
Oca 22 22:17:08 K56-CB bluetoothd[663]: Sap driver initialization failed.
Oca 22 22:17:08 K56-CB bluetoothd[663]: sap-server: Operation not permitted (1)
Oca 22 22:17:08 K56-CB bluetoothd[663]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Oca 22 22:17:08 K56-CB bluetoothd[663]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSource
Oca 22 22:17:08 K56-CB bluetoothd[663]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSink
Oca 22 22:17:08 K56-CB bluetoothd[663]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource
Oca 22 22:17:08 K56-CB bluetoothd[663]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink
Oca 22 22:57:29 K56-CB bluetoothd[663]: Failed to set mode: Blocked through rfkill (0x12)
Oca 22 22:57:42 K56-CB bluetoothd[663]: Failed to set mode: Failed (0x03)

Since it complatin about rfkill I cheked it.

rfkill list :

0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: asus-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: asus-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

Nothing seems blocked. Then I disabled Bluetooth(which was already not enabled) from Gnome Bluetooth Settings by clicking to the enable/disable button again. Wireless led on laptop went off but wi-fi is still working. I checked bluetooth.service again but there wasn't anything new other than some "Endpoint unregistered" logs. I checked rfkill again.

rfkill list :

0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: asus-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: asus-bluetooth: Bluetooth
	Soft blocked: yes
	Hard blocked: no

3: hci0: Bluetooth entry is gone and asus-bluetooth is soft blocked now. I pressed Fn+F2 twice to get the wireless led back on. Then I checked rfkill again and got the exact same result in my first rfkill list output above. Then I tried to disable/enable Bluetooth from Settings again and got the exact same results all over again. So this time I executed "rfkill ublock all" instead of pressing Fn+F2.

rfkill list :

0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: asus-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: asus-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no

All seems ok. Then I just closed Bluetooth Settings window without changing anything.

rfkill list :

0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: asus-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: asus-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
5: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no

I don't understand. I didn't change anything and "rfkill list" output has changed again. I executed "rfkill unblock all" again.

rfkill list :

0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: asus-wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: asus-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
5: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

Okay this time it should work. I tried to enable Bluetooth from settings again aaand, nothing happened. I  checked "rfkill list"s output again and it was same as the last output I gave above. So I checked bluetooth.service.

systemctl status bluetooth.service :

● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2017-01-22 22:16:53 +03; 1h 1min ago
     Docs: man:bluetoothd(8)
 Main PID: 663 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─663 /usr/lib/bluetooth/bluetoothd

Oca 22 23:12:45 K56-CB bluetoothd[663]: Sap driver initialization failed.
Oca 22 23:12:45 K56-CB bluetoothd[663]: sap-server: Operation not permitted (1)
Oca 22 23:12:45 K56-CB bluetoothd[663]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Oca 22 23:12:45 K56-CB bluetoothd[663]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSource
Oca 22 23:12:45 K56-CB bluetoothd[663]: Endpoint registered: sender=:1.68 path=/MediaEndpoint/A2DPSink
Oca 22 23:12:45 K56-CB bluetoothd[663]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource
Oca 22 23:12:45 K56-CB bluetoothd[663]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink
Oca 22 23:14:04 K56-CB bluetoothd[663]: Failed to set mode: Blocked through rfkill (0x12)
Oca 22 23:16:22 K56-CB bluetoothd[663]: Failed to set mode: Failed (0x03)
Oca 22 23:17:53 K56-CB bluetoothd[663]: Failed to set mode: Failed (0x03)

I returned to where I started... And "rfkill list" still says nothing is blocked. Then I tried to enable bluetooth with bluetoothctl. However, whatever command I use at bluetoothctl, the output is same: "No default controller available".

Output of "lspci" at this point:

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 740M] (rev ff)
03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01)
04:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)

I'm not sure if there is a Bluetooth controller here.
Before this trial, to get rfkill to unblock all wireless devices after boot, I enabled rfkill-unblock@all.service like it was said in this thread: https://bbs.archlinux.org/viewtopic.php?pid=1210751

systemctl cat rfkill-unblock@all.service :

# /usr/lib/systemd/system/rfkill-unblock@.service
[Unit]
Description=RFKill-Unblock %I
After=rfkill-block@all.service

[Service]
Type=oneshot
ExecStart=/usr/bin/rfkill unblock %I

[Install]
WantedBy=multi-user.target

# /etc/systemd/system/rfkill-unblock@all.service.d/override.conf
# /usr/lib/systemd/system/rfkill-unblock@.service
[Unit]
Description=RFKill-Unblock %I
After=rfkill-block@all.service
After=bluetooth.service
Requires=bluetooth.service

[Service]
Type=oneshot
ExecStart=/usr/bin/rfkill unblock %I

[Install]
WantedBy=multi-user.target

systemctl status rfkill-unblock@all.service :

● rfkill-unblock@all.service - RFKill-Unblock all
   Loaded: loaded (/usr/lib/systemd/system/rfkill-unblock@.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/rfkill-unblock@all.service.d
           └─override.conf
   Active: inactive (dead) since Sun 2017-01-22 22:16:51 +03; 1h 20min ago
 Main PID: 483 (code=exited, status=0/SUCCESS)

Oca 22 22:16:51 K56-CB systemd[1]: Starting RFKill-Unblock all...
Oca 22 22:16:51 K56-CB systemd[1]: Started RFKill-Unblock all.

This is just a summary of my last try. I got many different errors at my previous trials. I even got it working a few times but right after bluetooth got disabled/enabled, laptop went to sleep or got rebooted, it never worked again. I'm about to lose my mind here I can't find anything that could be the cause of the issue. Bluetooth works flawlessly on Windows and Ubuntu. Also it was working on Arch some time ago but I can't recall when it started to act weird like this. Can anyone help me diagnose the issue?

Offline

#2 2017-01-22 21:28:46

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,740

Re: Bluetooth issues on my laptop

I am concerned that there may be a lack of controls on this experiment.  Are you running these commands from a terminal inside Gnome?

I am not a fan of Gnome, or, to a lesser degree, of KDE -- too many things happen at the will of an invisible hand.  Any chance of trying this from a console?  Or at the least a terminal under a more benign environment like Openbox?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2017-01-23 05:07:56

Zorbik
Member
Registered: 2016-08-09
Posts: 42

Re: Bluetooth issues on my laptop

I am also having bluetooth issues. Well, at least I am getting errors for it ever since I put a new wifi-card in my laptop that supports Bluetooth 4.2. Previous wifi-card did not AFAIK (Intel 7260, currently have Intel 8260)

Here's the result of

systemctl status bluetooth.service
â bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2017-01-22 22:02:33 EST; 1h 55min ago
     Docs: man:bluetoothd(8)
 Main PID: 539
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           ââ539 /usr/lib/bluetooth/bluetoothd

Jan 22 22:02:33 olympus-r systemd[1]: Starting Bluetooth service...
Jan 22 22:02:33 olympus-r bluetoothd[539]: Bluetooth daemon 5.43
Jan 22 22:02:33 olympus-r systemd[1]: Started Bluetooth service.
Jan 22 22:02:33 olympus-r bluetoothd[539]: Starting SDP server
Jan 22 22:02:33 olympus-r bluetoothd[539]: Bluetooth management interface 1.13 initialized
Jan 22 22:02:33 olympus-r bluetoothd[539]: Failed to obtain handles for "Service Changed" characteristic
Jan 22 22:02:33 olympus-r bluetoothd[539]: Sap driver initialization failed.
Jan 22 22:02:33 olympus-r bluetoothd[539]: sap-server: Operation not permitted (1)

As far as I can tell, bluetooth still seems to work. I was able to pair with my phone and connect to it, so I have ignored it since then.

Offline

#4 2017-01-23 10:20:26

LazyLucretia
Member
Registered: 2016-01-28
Posts: 39

Re: Bluetooth issues on my laptop

ewaller wrote:

I am concerned that there may be a lack of controls on this experiment.  Are you running these commands from a terminal inside Gnome?

I am not a fan of Gnome, or, to a lesser degree, of KDE -- too many things happen at the will of an invisible hand.  Any chance of trying this from a console?  Or at the least a terminal under a more benign environment like Openbox?

I followed your suggestion and did everything on tty2 this time. I booted up my computer and right after I got into the GDM, I switched to tty2 and started bluetoothctl. Results were different.

[umut@K56-CB ~]$ bluetoothctl
[NEW] Controller 6C:71:D9:5B:18:96 K56-CB [default]
[NEW] Device DC:2C:26:E9:60:11 Bluetooth keyboard
[NEW] Device C4:2C:03:AC:F8:B2 aliutkuyazgan's Mouse
[NEW] Device B8:09:8A:EB:4B:54 Ali Utku Yazgan's Keyboard
[NEW] Device 30:85:A9:31:84:5A Nexus 7
[NEW] Device 40:B8:37:1B:73:54 Xperia Z5 Compact

At this point I pressed the button on my Bluetooth Keyboard(DC:2C:26:E9:60:11). Bluetooth LED started blinking.

[bluetooth]# scan on
Discovery started
[CHG] Controller 6C:71:D9:5B:18:96 Discovering: yes
[CHG] Device DC:2C:26:E9:60:11 LegacyPairing: yes
[CHG] Device DC:2C:26:E9:60:11 RSSI: -69
[bluetooth]# connect DC:2C:26:E9:60:11
Attempting to connect to DC:2C:26:E9:60:11
[CHG] Device DC:2C:26:E9:60:11 Connected: yes
Connection successful
[CHG] Device DC:2C:26:E9:60:11 ServicesResolved: yes

It printed "Connection successful" but the keyboard wasn't working. None of the keys I pressed was captured. Bluetooth LED was off(which is always off unless it's waiting for a connection). I tried to disconnect and reconnect.

[Bluetooth keyboard]# disconnect DC:2C:26:E9:60:11 
Attempting to disconnect from DC:2C:26:E9:60:11 
[CHG] Device DC:2C:26:E9:60:11 ServicesResolved: no
Successful disconnected
[CHG] Device DC:2C:26:E9:60:11 Connected: no
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[CHG] Device DC:2C:26:E9:60:11 RSSI: -78
[bluetooth]# connect DC:2C:26:E9:60:11
Attempting to connect to DC:2C:26:E9:60:11
[CHG] Device DC:2C:26:E9:60:11 Connected: yes
Connection successful
[Bluetooth keyboard]# [  623.664419] hid-generic 0005:05AC:023C.0001: unknown main item tag 0x0
[Bluetooth keyboard]# y[  644.773079] Bluetooth: hci0 corrupted ACL packet
[CHG] Device DC:2C:26:E9:60:11 ServicesResolved: yes
[Bluetooth keyboard]# [  667.506678] Bluetooth: hci0 ACL packet for unknown connection handle 0

This time keyboard was working, it captured all my button presses. That last error, "unknown connection handle" was repeated like 15-20 times. I guess it repeated every time I pressed a button. I switched to GDM and to my i3 desktop from there, in order to copy/paste tty2's output to a text file from /dev/vcs2 (it was horribly formatted so I had to copy it line by line, which I coudn't do from a terminal). Then I switched back to tty2, tried to type with the keyboard and after each button I pressed, another line of error like the one above appeared. After a ~30 seconds delay, all buttons I pressed was captured and printed to the terminal. After this point whatever I try to type with the bluetooth keyboard was typed after ~30 seconds delay. I started Gnome and keyboard was still working with same delay. I checked bluetooth.service:

[umut@K56-CB ~]$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2017-01-23 12:14:54 +03; 18min ago
     Docs: man:bluetoothd(8)
 Main PID: 569 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─569 /usr/lib/bluetooth/bluetoothd

Oca 23 12:15:59 K56-CB bluetoothd[569]: device_request_pin: Operation not permitted
Oca 23 12:16:23 K56-CB bluetoothd[569]: Endpoint registered: sender=:1.70 path=/MediaEndpoint/A2DPSource
Oca 23 12:16:23 K56-CB bluetoothd[569]: Endpoint registered: sender=:1.70 path=/MediaEndpoint/A2DPSink
Oca 23 12:16:23 K56-CB bluetoothd[569]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Oca 23 12:16:29 K56-CB bluetoothd[569]: DC:2C:26:E9:60:11: error updating services: Input/output error (5)
Oca 23 12:24:02 K56-CB bluetoothd[569]: Can't get HIDP connection info
Oca 23 12:25:11 K56-CB bluetoothd[569]: Can't get HIDP connection info
Oca 23 12:25:12 K56-CB bluetoothd[569]: No agent available for request type 0
Oca 23 12:25:12 K56-CB bluetoothd[569]: device_request_pin: Operation not permitted
Oca 23 12:25:53 K56-CB bluetoothd[569]: DC:2C:26:E9:60:11: error updating services: Connection timed out (110)

There seems to be many different errors and I have no idea which one I should start troubleshooting with. I also chekced dmesg and journalctl for bluetooth releated entries. There was no entries in dmesg. However in journalctl, there was like hundreds of entries about bluetooth and I'm not sure which are the relevant ones.
Since I can connect the keyboard using bluetoothctl, issues in my first post seems like Gnome releated issues. However, using bluetoothctl to connect this keyboard doesn not seem like a solution either since it takes quite a bit of configuration after each time I connect my keyboard and there is also thie weird 30 second delay thing.
Soo, where should I go from here? Do you have any advice?

Offline

#5 2017-02-15 12:27:11

cribari
Member
From: Recife, Brazil
Registered: 2016-01-28
Posts: 83
Website

Re: Bluetooth issues on my laptop

This could be related to the following bug:  https://bugzilla.kernel.org/show_bug.cgi?id=190831

See also  https://bugs.archlinux.org/task/51271


Linux, street photography and Baroque music enthusiast.

Offline

#6 2017-02-16 23:45:09

jeremy31
Member
Registered: 2015-11-01
Posts: 149

Re: Bluetooth issues on my laptop

Please post results for

lsusb

There have been issues in newer kernels with Atheros bluetooth devices

Offline

#7 2017-03-01 18:59:24

LazyLucretia
Member
Registered: 2016-01-28
Posts: 39

Re: Bluetooth issues on my laptop

jeremy31 wrote:

Please post results for

lsusb

There have been issues in newer kernels with Atheros bluetooth devices

Sorry I have been really bussy for last few weeks. Here:

[umut@K56-CB ~]$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 13d3:5165 IMC Networks 
Bus 001 Device 003: ID 13d3:3362 IMC Networks Atheros AR3012 Bluetooth 4.0 Adapter
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c246 Logitech, Inc. Gaming Mouse G300
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It's an Atheros chip.

Offline

#8 2017-03-01 19:08:15

LazyLucretia
Member
Registered: 2016-01-28
Posts: 39

Re: Bluetooth issues on my laptop

cribari wrote:

I have an Atheros bluetooth device and kernel 4.9.11-1 so I don't think its releated to this bug. hmm

Offline

#9 2017-03-02 20:35:11

LazyLucretia
Member
Registered: 2016-01-28
Posts: 39

Re: Bluetooth issues on my laptop

UPDATE: I tried using an old USB Bluetooth dongle and it's working flawlessly. This proves that the issue is related to Atheros Bluetooth chip inside my laptop.

Offline

#10 2017-03-06 15:47:03

jeremy31
Member
Registered: 2015-11-01
Posts: 149

Re: Bluetooth issues on my laptop

LazyLucretia wrote:
jeremy31 wrote:

Please post results for

lsusb

There have been issues in newer kernels with Atheros bluetooth devices

Sorry I have been really bussy for last few weeks. Here:

[umut@K56-CB ~]$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 13d3:5165 IMC Networks 
Bus 001 Device 003: ID 13d3:3362 IMC Networks Atheros AR3012 Bluetooth 4.0 Adapter
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c246 Logitech, Inc. Gaming Mouse G300
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It's an Atheros chip.

And not the one with the unusual problem with asking for firmware that doesn't exist. There was a delay timer added to ath3k to prevent the module from trying to upload firmware during the USB reset.  This timer may need to be longer now

http://git.kernel.org/cgit/linux/kernel … th/ath3k.c the timer settings are on lines 208 and 209 in the bluetooth-next tree- shouldn't be many lines away in the Arch kernel source

Offline

Board footer

Powered by FluxBB