kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

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/


** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1595767

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1595767/+subscriptions