Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled

Bug #1448566 reported by Jrddvs on 2015-04-26
This bug affects 12 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
linux (Ubuntu)

Bug Description

Fresh install of 15.04 on a Macbook Pro 12,1.

I get no Bluetooth icon in the status bar, and in System Settings > Bluetooth, everything is greyed out (i.e., can't turn it on).

$lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; lsmod | grep bluetooth; hciconfig -a; uname -a

Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
Bus 001 Device 004: ID 05ac:8290 Apple, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller
[ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7
[ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on usb-0000:00:14.0-3/input0
[ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8
[ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 Mouse [Broadcom Corp. Bluetooth USB Host Controller] on usb-0000:00:14.0-3/input1
[ 34.866186] Bluetooth: Core ver 2.20
[ 34.866205] Bluetooth: HCI device and connection manager initialized
[ 34.866751] Bluetooth: HCI socket layer initialized
[ 34.866754] Bluetooth: L2CAP socket layer initialized
[ 34.866759] Bluetooth: SCO socket layer initialized
[ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-9b] only partially covers this bridge
[ 35.003383] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
[ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 08:11:08 version (r540934) FWID 01-e4dc15b
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
bluetooth 491520 1 btusb
Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1448566/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Jrddvs (jrddvs) on 2015-04-26
affects: ubuntu → network-manager (Ubuntu)
affects: network-manager (Ubuntu) → bluez (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
Didier 'Ptitjes' (ptitjes) wrote :

Don't know if this can help but the bluetooth chip is a BCM20703 (chipset support BT 4.1) as part of the Broadcom BCM943602CS wifi/bluetooth combo.

See for references: https://wikidevi.com/wiki/Broadcom_BCM943602CS

Didier 'Ptitjes' (ptitjes) wrote :

BTW, mine on MacOS X is reported to be a BCM20703A1 (on a MacBookPro11,4)

Simon Fels (morphis) wrote :

Please see http://www.spinics.net/lists/linux-bluetooth/msg64098.html for details about this. It is obviously a problem with the driver which needs to be fixed. The mail thread has some pointers but a real solution seems to need quite some more work in the kernel bluetooth driver stack.

Changed in bluez (Ubuntu):
status: Confirmed → Invalid

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

apport-collect 1448566

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.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: vivid
Didier 'Ptitjes' (ptitjes) wrote :

@morphis Yep, I confirm the problem as described there by Marcel Holtmann is correct. I tried his test fix and it does indeed make the controller work. I was able to pair and use my keyboard and track-pad without problem.

Didier 'Ptitjes' (ptitjes) wrote :

I confirm the test fix described in the mailing-list thread pointed by @morphis makes the controller work almost correctly.
I was able to use my BT keyboard and trackpad without problem. However, I failed to use my phone as a remote connection.

Xavier (rxaviers) wrote :

Please, any updates on how this should be available to Ubuntu users? Any instructions on how to setting it up for now?

ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
 /dev/snd/controlC1: mjg 1409 F.... pulseaudio
 /dev/snd/controlC0: mjg 1409 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 15.10
HibernationDevice: RESUME=UUID=bc879a1f-ac27-48ae-82dd-3c81b7307dd0
InstallationDate: Installed on 2015-07-22 (92 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
 Bus 001 Device 004: ID 05ac:8290 Apple, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
 linux-restricted-modules-4.2.0-16-generic N/A
 linux-backports-modules-4.2.0-16-generic N/A
 linux-firmware 1.149
 2: phy2: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-16-generic x86_64
UpgradeStatus: Upgraded to wily on 2015-08-27 (56 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B07.1506051617
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

tags: added: apport-collected wily

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in bluez (Ubuntu):
importance: Undecided → Medium
Joe Barnett (thejoe) wrote :

this is also in the bluetooth (not bluetooth-next) repo: https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=22f8e9dbf671a2f36d90d3d8723a2a0c5227fa4b , would it be possible to include in the wily kernel as a SAUCE patch at this point?

Jean-Frédéric (jeanfred) wrote :

Posting this in case it would help someone else: I had the same issue with 15.10 (with kernel 4.2). I upgraded today to 16.04 (with kernel 4.4.0) and the buletooth is working like a charm.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers