bluetooth HW not initialized Dell XPS 15 9530 (Ubuntu 16.04)

[Ken Pratt]

Ubuntu 16.04 desktop edition does not properly initialize the bluetooh hardware in the Dell XPS 15 9530. lsusb show the hardware as:

Bus 003 Device 004: ID 0a5c:216f Broadcom Corp. BCM20702A0 Bluetooth

Running bluethoothctl as root show only a driver named:

[bluetooth]# list
Controller AC:D1:B8:C0:CE:E4 ChromeLinux_7236 [default]

I don't know what ChromLinux_7236 is. It does not seem related to Broadcom but rather Google.

Scanning for bluethooth devices just timeout - assuming the ChromLinux_7236 is acting as some sort of stub answering the API but not providing any actual bluetooth device scanning.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: kjpratt 3218 F.... pulseaudio
 /dev/snd/controlC0: kjpratt 3218 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=8424daf7-084c-4639-93a0-00fd243164b4
InstallationDate: Installed on 2016-06-15 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. XPS 15 9530
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-generic N/A
 linux-firmware 1.157
Tags: xenial
Uname: Linux 4.4.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 10/15/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: XPS 15 9530
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/15/2014:svnDellInc.:pnXPS159530:pvrA07:rvnDellInc.:rnXPS159530:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 15 9530
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1595767

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.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 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.7-rc4-yakkety/

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[Ken Pratt (kenpratt)]

apport information

[penalvch (penalvch)]

Ken Pratt, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]