bluetooth not working asus laptop 1604 fresh install

Bug #1713290 reported by Fernando
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I cannot make work the bluetooth in a laptop Asus K46CB=S46CB=S46CM with ubuntu 16.
I have read several forums like https://askubuntu.com/questions/787023/bluetooth-not-working-on-ubuntu-16-04-lts
https://ubuntuforums.org/showthread.php?t=2082152, https://www.vivaolinux.com.br/topico/Notebooks/Problemas-com-o-Bluetooth-no-Asus-S46CB.
https://bbs.archlinux.org/viewtopic.php?id=213841

I have tried several of the suggestions, but nothing worked. On a newer Asus, suggestion worked. Including installing blueman,
setting AutoEnable=true in /etc/bluetooth/main.conf, and
sudo apt-get install aptitude
sudo aptitude install firmware-atheros

dmesg | grep -i blue

[ 2.562304] usb 1-1.1: Product: Bluetooth USB Host Controller
[ 19.240585] Bluetooth: Core ver 2.22
[ 19.240597] Bluetooth: HCI device and connection manager initialized
[ 19.240600] Bluetooth: HCI socket layer initialized
[ 19.240601] Bluetooth: L2CAP socket layer initialized
[ 19.240607] Bluetooth: SCO socket layer initialized
[ 30.378757] usb 1-1.1: Product: Bluetooth USB Host Controller
[ 30.499220] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 30.499222] Bluetooth: BNEP filters: protocol multicast
[ 30.499225] Bluetooth: BNEP socket layer initialized
[ 32.540519] Bluetooth: hci0 command 0x0c52 tx timeout
[ 44.556244] Bluetooth: RFCOMM TTY layer initialized
[ 44.556248] Bluetooth: RFCOMM socket layer initialized
[ 44.556252] Bluetooth: RFCOMM ver 1.11
[ 609.719015] Bluetooth: hci0 command 0x0c52 tx timeout

journalctl -b | grep Bluetooth
Ago 26 21:30:51 fernando-K46CB kernel: usb 1-1.1: Product: Bluetooth USB Host Controller
Ago 26 21:31:00 fernando-K46CB kernel: Bluetooth: Core ver 2.22
Ago 26 21:31:00 fernando-K46CB kernel: Bluetooth: HCI device and connection manager initialized
Ago 26 21:31:00 fernando-K46CB kernel: Bluetooth: HCI socket layer initialized
Ago 26 21:31:00 fernando-K46CB kernel: Bluetooth: L2CAP socket layer initialized
Ago 26 21:31:00 fernando-K46CB kernel: Bluetooth: SCO socket layer initialized
Ago 26 21:31:12 fernando-K46CB kernel: usb 1-1.1: Product: Bluetooth USB Host Controller
Ago 26 21:31:12 fernando-K46CB systemd[1]: Starting Bluetooth service...
Ago 26 21:31:12 fernando-K46CB bluetoothd[1055]: Bluetooth daemon 5.37
Ago 26 21:31:12 fernando-K46CB systemd[1]: Started Bluetooth service.
Ago 26 21:31:12 fernando-K46CB systemd[1]: Reached target Bluetooth.
Ago 26 21:31:12 fernando-K46CB bluetoothd[1055]: Bluetooth management interface 1.14 initialized
Ago 26 21:31:12 fernando-K46CB kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Ago 26 21:31:12 fernando-K46CB kernel: Bluetooth: BNEP filters: protocol multicast
Ago 26 21:31:12 fernando-K46CB kernel: Bluetooth: BNEP socket layer initialized
Ago 26 21:31:14 fernando-K46CB kernel: Bluetooth: hci0 command 0x0c52 tx timeout
Ago 26 21:31:26 fernando-K46CB kernel: Bluetooth: RFCOMM TTY layer initialized
Ago 26 21:31:26 fernando-K46CB kernel: Bluetooth: RFCOMM socket layer initialized
Ago 26 21:31:26 fernando-K46CB kernel: Bluetooth: RFCOMM ver 1.11

sudo hciconfig

hci0: Type: BR/EDR Bus: USB
 BD Address: 2C:D0:5A:0E:E5:30 ACL MTU: 1022:8 SCO MTU: 183:5
 DOWN
 RX bytes:646 acl:0 sco:0 events:42 errors:0
 TX bytes:2175 acl:0 sco:0 commands:46 errors:4

lsmod | grep -i blue
bluetooth 557056 42 btrtl,btintel,bnep,btbcm,rfcomm,ath3k,btusb

printf "btrtl\nbtintel\nbnep\nbtbcm\nrfcomm\nath3k\nbtusb > newfile.txt

while read -r LINE; do echo "$LINE">>results2.txt;modinfo "$LINE" | grep ^desc>>results2.txt;modinfo "$LINE" | grep parm>> results2.txt; done < newfile.txt

results2.txt
btrtl
description: Bluetooth support for Realtek devices ver 0.1
btintel
description: Bluetooth support for Intel devices ver 0.1
bnep
description: Bluetooth BNEP ver 1.3
parm: compress_src:Compress sources headers (bool)
parm: compress_dst:Compress destination headers (bool)
btbcm
description: Bluetooth support for Broadcom devices ver 0.1
rfcomm
description: Bluetooth RFCOMM ver 1.11
parm: disable_cfc:Disable credit based flow control (bool)
parm: channel_mtu:Default MTU for the RFCOMM channel (int)
parm: l2cap_mtu:Default MTU for the L2CAP connection (uint)
parm: l2cap_ertm:Use L2CAP ERTM mode for connection (bool)
ath3k
description: Atheros AR30xx firmware driver

rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

lsb_release -rcd ; uname -r
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
4.10.0-32-generic

lspci -nnk | grep -iA2 net
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
 Subsystem: Lite-On Communications Inc AR9485 Wireless Network Adapter [11ad:6628]
 Kernel driver in use: ath9k
 Kernel modules: ath9k
--
...

ps aux | grep bluetooth
z 1462 0.0 0.0 349072 7872 ? Ssl 15:11 0:00 /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
z 1767 0.0 0.1 150304 10180 ? S 15:11 0:00 /usr/lib/bluetooth/obexd
root 5972 0.0 0.0 32056 4692 ? Ss 15:43 0:00 /usr/lib/bluetooth/bluetoothd
z 13852 0.0 0.0 14228 1020 pts/19 S+ 17:22 0:00 grep --color=auto bluetooth

bluetooth 557056 42 btrtl,btintel,bnep,btbcm,rfcomm,ath3k,btusb

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
 ## this is the bluetooth:
Bus 001 Device 003: ID 04ca:3005 Lite-On Technology Corp.
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 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

modinfo ath3k | grep -i 3005
alias: usb:v04CAp3005d*dc*dsc*dp*ic*isc*ip*in*

iwconfig
enp4s0f2 no wireless extensions.

lo no wireless extensions.

wlp3s0 IEEE 802.11 ESSID:"203"
          Mode:Managed Frequency:2.452 GHz Access Point: D4:2C:0F:27:75:AA
          Bit Rate=39 Mb/s Tx-Power=15 dBm
          Retry short limit:7 RTS thr:off Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=64/70 Signal level=-46 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:1 Invalid misc:41 Missed beacon:0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Aug 26 21:57:34 2017
InstallationDate: Installed on 2017-08-26 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Fernando (firthu) wrote :
affects: linux-hwe (Ubuntu) → linux (Ubuntu)
Revision history for this message
Fernando (firthu) wrote :

Workaround: Reinstall without any wireless USB keyboard connected.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1713290

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Fernando (firthu) wrote :

not possible to run apport-collect, already reinstalled.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.