[ASUS ZENBOOK UX31A] Bluetooth problems

[Steeve Cottin]

Bluetooth is not always "up" after reboot.

When it is down", I need to open/close the screen several times in order to get it "up".

It was yet a problem before 16.04 LTS (new installation).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: stef 2266 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Mar 18 14:14:43 2017
HibernationDevice: RESUME=UUID=b9fad596-3f76-4c1a-bb2f-fb97d53143f0
InstallationDate: Installed on 2017-01-21 (55 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUSTeK Computer Inc. UX31E
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=926de407-6887-4e54-bf0a-7dfb2ff90e29 ro quiet splash rootfstype=ext4 acpi_osi=Linux pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-66-generic N/A
 linux-backports-modules-4.4.0-66-generic N/A
 linux-firmware 1.157.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31E
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.:bvrUX31E.213:bd06/21/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UX31E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3

[Steeve Cottin (stef-cottin)]

The bug seems to be fixed with the kernel upstream (v4.11-rc3).

I 'll try it a few days in order to confirm it.

See you soon.

[Steeve Cottin (stef-cottin)]

Tested with the latest v4.11 kernel ( http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3 )

The bug is fixed (tagged 'kernel-fixed-upstream' and marked as "Confirmed").