Ubuntu

Bluetooth not working on MacbookPro 6,2

Reported by Mike Basinger on 2010-10-14
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Undecided
Unassigned

Bug Description

Bluetooth does not work out of the box on a MacbookPro 6,2 (mid 2010 15.3 i5 model). I believe the following needs to be added to the btusb.c in the kernel to get this working.

/* Apple MacBookPro6 BT device */
{ USB_DEVICE(0x05ac, 0x8218) },

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.34
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: Cirrus Analog [Cirrus Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dbasinge 1614 F.... pulseaudio
 /dev/snd/pcmC0D0p: dbasinge 1614 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xc1d00000 irq 45'
   Mixer name : 'Cirrus Logic CS4206'
   Components : 'HDA:10134206,106b0b00,00100301'
   Controls : 16
   Simple ctrls : 9
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xc1080000 irq 16'
   Mixer name : 'Nvidia GT220 HDMI'
   Components : 'HDA:10de000a,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Date: Thu Oct 14 12:53:40 2010
HibernationDevice: RESUME=UUID=139dc4dd-90a0-4c5d-ab7f-f4bf81f697f9
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Apple Inc. MacBookPro6,2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=e77c2c86-753f-4bc4-9d91-d819594d16d2 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 07/26/10
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP61.88Z.0057.B0C.1007261552
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22586C8
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22586C8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0C.1007261552:bd07/26/10:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
dmi.product.name: MacBookPro6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Mike Basinger (mike.basinger) wrote :
Mike Basinger (mike.basinger) wrote :

The following will be needed for MacBookPro 7,1 models

/* Apple MacBookPro7,1 */
{ USB_DEVICE(0x05ac, 0x8213) },

Jeremy Foshee (jeremyfoshee) wrote :

Hi Mike,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Mike Basinger (mike.basinger) wrote :

Does not work in upstream kernel either.

tags: removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → New
Book 'em Dano (heymrdjd) on 2010-11-09
tags: added: macbookpro
Julian Wiedmann (jwiedmann) wrote :

Patches for 6,2 and 7,1 were merged in 2.6.37.

Changed in linux:
status: New → Fix Released
Changed in linux (Ubuntu):
status: New → Fix Released
To post a comment you must log in.