Bluetooth doesn't work on ASUS Zenbook UX301LAA

[Vasya Pupkin]

It's not possible to make bluetooth work. Pressing Fn+F2 doesn't change anything. Sometimes a grey (inactive) bluetooth icon appears but disappears instantly after attempt to turn it on.

WORKAROUND: Set "XHCI Pre-Boot Mode" BIOS option to "Disabled".

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-21-generic 4.2.0-21.25
ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
Uname: Linux 4.2.0-21-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: shadowlmd 2409 F.... pulseaudio
 /dev/snd/controlC1: shadowlmd 2409 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Dec 5 18:03:20 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb
InstallationDate: Installed on 2015-10-22 (43 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: ASUSTeK COMPUTER INC. UX301LAA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-21-generic N/A
 linux-backports-modules-4.2.0-21-generic N/A
 linux-firmware 1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX301LAA.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX301LAA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX301LAA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Vasya Pupkin (shadowlmd)]

Also doesn't work with latest mainline kernel (4.3, 4.4rc3).

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Vasya Pupkin, could you please test for this via the latest mainline kernel (4.4-rc4) and advise to the results?

[Vasya Pupkin (shadowlmd)]

It doesn't work with 4.4rc4 as well.

[penalvch (penalvch)]

Vasya Pupkin, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Marcel Holtmann, Gustavo Padovan, and Johan Hedberg CC linux-bluetooth) ?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.

[Pilot6 (hanipouspilot)]

This issue is probably fixed by the last commits to btintel.c in 'linux-next'.
The device can't enter manufacturing mode correctly. This code has been updated there.
It should be supported by kernel 4.5.

[Vasya Pupkin (shadowlmd)]

Nice. Any chance it could be backported to 4.2?

[Vasya Pupkin (shadowlmd)]

Well, I just got 4.5rc1 and Bluetooth still doesn't work.

[Pilot6 (hanipouspilot)]

Good news is that I will soon receive this Intel WiFi+BT adapter. I will try to fix the issue some way or another.

[Pilot6 (hanipouspilot)]

I received and installed the adapter. BT works with ASUS laptops without any problems on a standard Ubuntu 4.2.

[Vasya Pupkin (shadowlmd)]

Maybe the problem is not with adapter itself but with Zenbook UX301LA. Fn+F2 hotkey used to enable/disable BT and Wi-Fi doesn't work too.

[Vasya Pupkin (shadowlmd)]

And of course everything works like a charm under Windows 10.

[Pilot6 (hanipouspilot)]

Try to use option "wapf=4" for asus_nb_wmi module.

2016-01-29 13:43 GMT+03:00 Vasya Pupkin <email address hidden>:
> And of course everything works like a charm under Windows 10.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1523108
>
> Title:
> Bluetooth doesn't work on ASUS Zenbook UX301LAA
>
> Status in linux package in Ubuntu:
> Triaged
>
> Bug description:
> It's not possible to make bluetooth work. Pressing Fn+F2 doesn't
> change anything. Sometimes a grey (inactive) bluetooth icon appears
> but disappears instantly after attempt to turn it on.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.10
> Package: linux-image-4.2.0-21-generic 4.2.0-21.25
> ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
> Uname: Linux 4.2.0-21-generic x86_64
> ApportVersion: 2.19.1-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: shadowlmd 2409 F.... pulseaudio
> /dev/snd/controlC1: shadowlmd 2409 F.... pulseaudio
> CurrentDesktop: Unity
> Date: Sat Dec 5 18:03:20 2015
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb
> InstallationDate: Installed on 2015-10-22 (43 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
> MachineType: ASUSTeK COMPUTER INC. UX301LAA
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.2.0-21-generic N/A
> linux-backports-modules-4.2.0-21-generic N/A
> linux-firmware 1.149.3
> SourcePackage: linux
> UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 06/05/2015
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: UX301LAA.211
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: UX301LAA
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK COMPUTER INC.
> dmi.chassis.version: 1.0
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
> dmi.product.name: UX301LAA
> dmi.product.version: 1.0
> dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523108/+subscriptions

[Vasya Pupkin (shadowlmd)]

Tried, didn't help.

$ cat /etc/modprobe.d/asus.conf
options asus_nb_wmi wapf=4

$ sudo modprobe -r asus_nb_wmi

$ sudo modprobe -v asus_nb_wmi
insmod /lib/modules/4.5.0-040500rc1-generic/kernel/drivers/platform/x86/wmi.ko
insmod /lib/modules/4.5.0-040500rc1-generic/kernel/drivers/input/sparse-keymap.ko
insmod /lib/modules/4.5.0-040500rc1-generic/kernel/drivers/platform/x86/asus-wmi.ko
insmod /lib/modules/4.5.0-040500rc1-generic/kernel/drivers/platform/x86/asus-nb-wmi.ko wapf=4

F2 key LED lighted up and BT icon disappeared from tray and I got this message in dmesg:

[39333.878246] usb 2-4: USB disconnect, device number 6

This happens without this option too.

Also, keyboard backlit stopped working with this option.

[Vasya Pupkin (shadowlmd)]

After rebooting, backlit returned, but still no reaction on Fn+F2 and no Bluetooth. This is dmesg after reboot:

$ dmesg | grep -i bluetooth
[ 8.795276] Bluetooth: Core ver 2.21
[ 8.795292] Bluetooth: HCI device and connection manager initialized
[ 8.795295] Bluetooth: HCI socket layer initialized
[ 8.795298] Bluetooth: L2CAP socket layer initialized
[ 8.795302] Bluetooth: SCO socket layer initialized
[ 8.829680] Bluetooth: hci0: read Intel version: 370710018002030d00
[ 8.831009] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[ 8.907934] Bluetooth: hci0 sending Intel patch command (0xfc8e) failed (-19)
[ 9.293108] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.293111] Bluetooth: BNEP filters: protocol multicast
[ 9.293116] Bluetooth: BNEP socket layer initialized
[ 10.903615] Bluetooth: hci0 command 0xfc8e tx timeout
[ 10.903629] Bluetooth: hci0 sending frame failed (-19)
[ 10.907603] Bluetooth: hci0: Exiting manufacturer mode failed (-110)

Some more stuff in syslog:

Jan 29 14:42:35 shadow-zenbook systemd[1]: Starting Bluetooth service...
Jan 29 14:42:35 shadow-zenbook bluetoothd[1414]: Bluetooth daemon 5.35
Jan 29 14:42:35 shadow-zenbook bluetoothd[1414]: Starting SDP server
Jan 29 14:42:35 shadow-zenbook kernel: [ 8.795276] Bluetooth: Core ver 2.21
Jan 29 14:42:35 shadow-zenbook kernel: [ 8.795292] Bluetooth: HCI device and connection manager initialized
Jan 29 14:42:35 shadow-zenbook kernel: [ 8.795295] Bluetooth: HCI socket layer initialized
Jan 29 14:42:35 shadow-zenbook kernel: [ 8.795298] Bluetooth: L2CAP socket layer initialized
Jan 29 14:42:35 shadow-zenbook kernel: [ 8.795302] Bluetooth: SCO socket layer initialized
Jan 29 14:42:35 shadow-zenbook kernel: [ 8.829680] Bluetooth: hci0: read Intel version: 370710018002030d00
Jan 29 14:42:35 shadow-zenbook kernel: [ 8.831009] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Jan 29 14:42:35 shadow-zenbook kernel: [ 8.907934] Bluetooth: hci0 sending Intel patch command (0xfc8e) failed (-19)
Jan 29 14:42:35 shadow-zenbook kernel: [ 9.293108] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 29 14:42:35 shadow-zenbook kernel: [ 9.293111] Bluetooth: BNEP filters: protocol multicast
Jan 29 14:42:35 shadow-zenbook kernel: [ 9.293116] Bluetooth: BNEP socket layer initialized
Jan 29 14:42:35 shadow-zenbook bluetoothd[1414]: Bluetooth management interface 1.11 initialized
Jan 29 14:42:35 shadow-zenbook systemd[1]: Started Bluetooth service.
Jan 29 14:42:35 shadow-zenbook systemd[1]: Reached target Bluetooth.
Jan 29 14:42:35 shadow-zenbook NetworkManager[1436]: <info> Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
Jan 29 14:42:36 shadow-zenbook kernel: [ 10.903615] Bluetooth: hci0 command 0xfc8e tx timeout
Jan 29 14:42:36 shadow-zenbook kernel: [ 10.903629] Bluetooth: hci0 sending frame failed (-19)
Jan 29 14:42:36 shadow-zenbook kernel: [ 10.907603] Bluetooth: hci0: Exiting manufacturer mode failed (-110)
Jan 29 14:42:36 shadow-zenbook systemd[1]: bluetooth.target: Unit not...

[Vasya Pupkin (shadowlmd)]

Doesn't work with 4.6rc1 kernel as well.

[Pilot6 (hanipouspilot)]

Vasya,

I have this adapter now. It detects the same

Intel version: 370710018002030d00

and it does load exactly same firmware file.

But in lsusb I have

8087:07dc

That must be some other revision of the chip.

I suggest writing a letter to the kernel maintainers.

[Vasya Pupkin (shadowlmd)]

Unfortunately, I don't know how to write a letter to kernel maintainers. I also don't know what exactly to write in this letter. Maybe you can help?

[Pilot6 (hanipouspilot)]

See this guide

https://wiki.ubuntu.com/Kernel/Bugs

2016-03-27 17:14 GMT+03:00 Vasya Pupkin <email address hidden>:
> Unfortunately, I don't know how to write a letter to kernel maintainers.
> I also don't know what exactly to write in this letter. Maybe you can
> help?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1523108
>
> Title:
> Bluetooth doesn't work on ASUS Zenbook UX301LAA
>
> Status in linux package in Ubuntu:
> Triaged
>
> Bug description:
> It's not possible to make bluetooth work. Pressing Fn+F2 doesn't
> change anything. Sometimes a grey (inactive) bluetooth icon appears
> but disappears instantly after attempt to turn it on.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.10
> Package: linux-image-4.2.0-21-generic 4.2.0-21.25
> ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
> Uname: Linux 4.2.0-21-generic x86_64
> ApportVersion: 2.19.1-0ubuntu5
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: shadowlmd 2409 F.... pulseaudio
> /dev/snd/controlC1: shadowlmd 2409 F.... pulseaudio
> CurrentDesktop: Unity
> Date: Sat Dec 5 18:03:20 2015
> EcryptfsInUse: Yes
> HibernationDevice: RESUME=UUID=4443577b-ebf9-4f35-bd95-660448592ddb
> InstallationDate: Installed on 2015-10-22 (43 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
> MachineType: ASUSTeK COMPUTER INC. UX301LAA
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic.efi.signed root=UUID=e7df807f-bc9b-4cdf-85ae-38b8a3c6f016 ro quiet splash rootfstype=ext4 vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.2.0-21-generic N/A
> linux-backports-modules-4.2.0-21-generic N/A
> linux-firmware 1.149.3
> SourcePackage: linux
> UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 06/05/2015
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: UX301LAA.211
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: UX301LAA
> dmi.board.vendor: ASUSTeK COMPUTER INC.
> dmi.board.version: 1.0
> dmi.chassis.asset.tag: No Asset Tag
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK COMPUTER INC.
> dmi.chassis.version: 1.0
> dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
> dmi.product.name: UX301LAA
> dmi.product.version: 1.0
> dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523108/+subscriptions

[penalvch (penalvch)]

Vasya Pupkin, the instructions to write a letter to bluetooth maintainers was provided in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523108/comments/6 .

Unfortunately, https://wiki.ubuntu.com/Kernel/Bugs is a legacy page. However, due to a recent flurry of permission restrictions in response to randomers abusing the openness of Ubuntu's infrastructure, I don't presently have access to fix this. Given a comprehensive strategy is actively being developed to address this, I'm patiently waiting for that to conclude.

[Ivan D. Sanders (vandelsand)]

So I think I managed to fix this bug with

systemctl enable bluetooth

then reboot. I don't seem to have the problem anymore.

[Vasya Pupkin (shadowlmd)]

In my case service is already enabled and issue is clearly with the kernel. Although with 4.10 kernel sometimes bluetooth starts working, mostly after laptop waking up from suspend.

[penalvch (penalvch)]

Vasya Pupkin, to keep this relevant to upstream, one would want to periodically check for, and test the latest mainline kernel (now 4.11-rc1) as it is released.

Could you please advise?

[Vasya Pupkin (shadowlmd)]

Setting "XHCI Pre-Boot Mode" BIOS option to "Disabled" fixes the problem. But it disables USB 3.0 entirely, so it's not a solution.

[Vasya Pupkin (shadowlmd)]

Actually, no, the real blocker is asus-nb-wmi. As soon as I do:

echo 0 | sudo tee /sys/devices/platform/asus-nb-wmi/rfkill/rfkill1/soft

my bluetooth device disconnects:

[ 77.045226] usb 1-4: USB disconnect, device number 5

This brings device back:

echo 1 | sudo tee /sys/devices/platform/asus-nb-wmi/rfkill/rfkill1/soft

But it's soft blocked. Unblocking with $(rfkill unblock bluetooth) causes device to disappear as well. But if I unload asus-nb-wmi module after bringing device back, I can unblock it using rfkill and use without any issue.

[Vasya Pupkin (shadowlmd)]

So it looks like there is a bug in asus-nb-wmi module. It should bring device down when it's soft blocked, but it does exactly opposite.

[Kai-Heng Feng (kaihengfeng)]

Please give mainline kernel >= v4.11-rc3 a try, it has a patch seemingly relevant to your case:

commit 71050ae7bf83e4d71a859257d11adc5de517073e
Author: João Paulo Rechi Vita <email address hidden>
Date: Mon Feb 20 14:50:22 2017 -0500

    platform/x86: asus-wmi: Detect quirk_no_rfkill from the DSDT

We can backport the patch if it works.

[Vasya Pupkin (shadowlmd)]

4.11 kernel seems to work, but instead of fixing test in asus-nb-wmi, they just removed /sys/devices/platform/asus-nb-wmi/rfkill/*, so now everything works as if I just unloaded asus-nb-wmi module. This means that F2 key doesn't light up when radio is on. But this is better than nothing.

[Kai-Heng Feng (kaihengfeng)]

Sounds like there's still something wrong here?

Can you elaborate what's the incorrect behavior in 4.11-rc3?

[Vasya Pupkin (shadowlmd)]

With 4.11rc3 bluetooth works. But F2 key doesn't light up when the radio is on. This is the result of removing rfkill switches from asus-nb-wmi module. This is not critical, it's only an indicator. Another minor issue is that bluetooth device can't be turned off and will consume power even when not used. I would say that 4.11rc3 has a workaround, but not a proper fix for the issue.

[Kai-Heng Feng (kaihengfeng)]

The commit log says:
    So when asus-wmi uses ASUS_WMI_DEVID_WLAN_LED (0x00010002) to store the
    wlan state, it drives the airplane-mode indicator LED (through the call
    to OWGD) in an inverted fashion: the LED is ON when airplane mode is OFF
    (since wlan is ON), and vice-versa.

    This commit skips registering RFKill switches at all for these laptops,
    to allow the asus-wireless driver to drive the airplane mode LED
    correctly through the ASHS ACPI device. Relying on the presence of ASHS
    and ASUS_WMI_DSTS_USER_BIT avoids adding DMI-based quirks for at least
    21 different laptops.

Sounds like the LED should be off when Airplane mode is off...

[Vasya Pupkin (shadowlmd)]

> Sounds like the LED should be off when Airplane mode is off

Well, under Windows LED is on when radios are on. And everything works as expected.

[Vasya Pupkin (shadowlmd)]

And on Linux after this commit LED is always off regardless of the Wi-Fi or Bluetooth states.

[Kai-Heng Feng (kaihengfeng)]

Okay, can you test if one of the following kernel parameter works:
'asus-nb-wmi.wapf=0'
'asus-nb-wmi.wapf=1'
'asus-nb-wmi.wapf=4'

[Vasya Pupkin (shadowlmd)]

Already tested, it doesn't seem to change anything.

[Kai-Heng Feng (kaihengfeng)]

Is there any Asus related led under '/sys/class/leds'?

[Vasya Pupkin (shadowlmd)]

$ ll /sys/class/leds/*asus*
lrwxrwxrwx 1 root root 0 апр 17 08:40 /sys/class/leds/asus::kbd_backlight -> ../../devices/platform/asus-nb-wmi/leds/asus::kbd_backlight/
lrwxrwxrwx 1 root root 0 апр 17 08:40 /sys/class/leds/asus-wireless::airplane -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4001:00/leds/asus-wireless::airplane/

[Jonathan Dumont (jdmnt)]

Dear all;

I had the same issue with Kubuntu 20.04LTS, yesterday and during the installation the bluetooth was working perfectly on my Asus UX305ua than, this morning, no bluetooth adapter found. I solved it by simply plugin in (power supply) my laptop. It appear to be an issue with the power management (energy saving). Something disable the bluetooth adapter to save energy.

So if you have this issue could you try to replicated the issue by
1. pluging the power cord
2. spinning an ubuntu live-cd

This might help the maintainer/developer to help us :)