Ubuntu
linux-lts-xenial package

  1. Bug #1220146
  2. Comment #213

Comment 213 for bug 1220146

Revision history for this message
james (thejamesbradwell) wrote :

So after I tried Spessotto's suggestion, I left it, then tried blacklisting btusb (/etc/modprobe.d/blacklist), rebooted, removed btusb from blacklist, removed asus.conf, rebooted, once again entered the command

# echo "options asus_nb_wmi wapf=4" > /etc/modprobe.d/asus.conf

Rebooted... and, suddenly,

# hciconfig -a
hci0: Type: BR/EDR Bus: USB
 BD Address: EC:0E:C4:69:DA:C2 ACL MTU: 1021:4 SCO MTU: 128:2
 DOWN
 RX bytes:558 acl:0 sco:0 events:28 errors:0
 TX bytes:355 acl:0 sco:0 commands:28 errors:0
 Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x5b 0x87
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT

# hciconfig hci0 up

This brought bluetooth up... But gnome-bluetooth was not recognizing it. It turned out that I needed to roll back bluez5 to bluez4. I did so and now it's working. So that leaves only the high cpu load.