Using bluez-4.96, things work fine on:
dell latitude d430
Bus 002 Device 004: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth
..but don't work on:
2011 unibody mac mini server
Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
"bluetoothd -nd" does not throw up any error messages, but "hcitool scan" fails with a "no device" found message.
Is there any further troubleshooting I could try?
Regards
John
On Sun, 2011-09-04 at 21:12 +0300, Luiz Augusto von Dentz wrote:
> Hi John,
> >>
> >> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c index
> >> 91d13a9..16abfd1 100644
> >> --- a/drivers/bluetooth/btusb.c
> >> +++ b/drivers/bluetooth/btusb.c
> >> @@ -75,6 +75,9 @@ static struct usb_device_id btusb_table[] = {
> >> /* Apple MacBookPro8,2 */
> >> { USB_DEVICE(0x05ac, 0x821a) },
> >>
> >> + /* Apple Mac Mini */
> >> + { USB_DEVICE(0x05ac, 0x4500) },
> >> +
> >> /* AVM BlueFRITZ! USB v2.0 */
> >> { USB_DEVICE(0x057c, 0x3800) },
> >>
> >>
> > Thanks, I recompiled the 3.0.3 kernel with the patch, but my machine crashed as soon as the driver tried to load..
>
> Maybe it needs more changes, iirc this new mac minis have BT 4.0
> controllers... Can you get any logs where it is crashing?
>
>
Hi,
I've sent the needed patch to the list a couple of hours ago.
Jurgen
Hi John,
On Sun, Sep 4, 2011 at 6:55 AM, John Frankish <[email protected]> wrote:
>> -----Original Message-----
>> From: Luiz Augusto von Dentz [mailto:[email protected]]
>> Sent: Thursday, 01 September, 2011 13:53
>> To: John Frankish
>> Cc: [email protected]
>> Subject: Re: Is bluetooth supported on lastest mac-mini?
>>
>> Hi John,
>>
>> On Thu, Sep 1, 2011 at 11:38 AM, John Frankish <[email protected]> wrote:
>> > Using bluez-4.96, things work fine on:
>> >
>> > dell latitude d430
>> > Bus 002 Device 004: ID 413c:8140 Dell Computer Corp. Wireless 360
>> > Bluetooth
>> >
>> > ..but don't work on:
>> >
>> > 2011 unibody mac mini server
>> > Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub
>> > (part of BCM2046 Bluetooth)
>> >
>> > "bluetoothd -nd" does not throw up any error messages, but "hcitool scan"
>> > fails with a "no device" found message.
>> >
>> > Is there any further troubleshooting I could try?
>>
>> It might need some change in the kernel to able to load the proper driver,
>> something like the following should do it:
>>
>> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c index
>> 91d13a9..16abfd1 100644
>> --- a/drivers/bluetooth/btusb.c
>> +++ b/drivers/bluetooth/btusb.c
>> @@ -75,6 +75,9 @@ static struct usb_device_id btusb_table[] = {
>> ? ? ? ? /* Apple MacBookPro8,2 */
>> ? ? ? ? { USB_DEVICE(0x05ac, 0x821a) },
>>
>> + ? ? ? /* Apple Mac Mini */
>> + ? ? ? { USB_DEVICE(0x05ac, 0x4500) },
>> +
>> ? ? ? ? /* AVM BlueFRITZ! USB v2.0 */
>> ? ? ? ? { USB_DEVICE(0x057c, 0x3800) },
>>
>>
> Thanks, I recompiled the 3.0.3 kernel with the patch, but my machine crashed as soon as the driver tried to load..
Maybe it needs more changes, iirc this new mac minis have BT 4.0
controllers... Can you get any logs where it is crashing?
--
Luiz Augusto von Dentz
> -----Original Message-----
> From: Luiz Augusto von Dentz [mailto:[email protected]]
> Sent: Thursday, 01 September, 2011 13:53
> To: John Frankish
> Cc: [email protected]
> Subject: Re: Is bluetooth supported on lastest mac-mini?
>
> Hi John,
>
> On Thu, Sep 1, 2011 at 11:38 AM, John Frankish <[email protected]> wrote:
> > Using bluez-4.96, things work fine on:
> >
> > dell latitude d430
> > Bus 002 Device 004: ID 413c:8140 Dell Computer Corp. Wireless 360
> > Bluetooth
> >
> > ..but don't work on:
> >
> > 2011 unibody mac mini server
> > Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub
> > (part of BCM2046 Bluetooth)
> >
> > "bluetoothd -nd" does not throw up any error messages, but "hcitool scan"
> > fails with a "no device" found message.
> >
> > Is there any further troubleshooting I could try?
>
> It might need some change in the kernel to able to load the proper driver,
> something like the following should do it:
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c index
> 91d13a9..16abfd1 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -75,6 +75,9 @@ static struct usb_device_id btusb_table[] = {
> /* Apple MacBookPro8,2 */
> { USB_DEVICE(0x05ac, 0x821a) },
>
> + /* Apple Mac Mini */
> + { USB_DEVICE(0x05ac, 0x4500) },
> +
> /* AVM BlueFRITZ! USB v2.0 */
> { USB_DEVICE(0x057c, 0x3800) },
>
>
Thanks, I recompiled the 3.0.3 kernel with the patch, but my machine crashed as soon as the driver tried to load..
Hi John,
On Thu, Sep 1, 2011 at 11:38 AM, John Frankish <[email protected]> wrote:
> Using bluez-4.96, things work fine on:
>
> dell latitude d430
> Bus 002 Device 004: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth
>
> ..but don't work on:
>
> 2011 unibody mac mini server
> Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
>
> "bluetoothd -nd" does not throw up any error messages, but "hcitool scan" fails with a "no device" found message.
>
> Is there any further troubleshooting I could try?
It might need some change in the kernel to able to load the proper
driver, something like the following should do it:
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 91d13a9..16abfd1 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -75,6 +75,9 @@ static struct usb_device_id btusb_table[] = {
/* Apple MacBookPro8,2 */
{ USB_DEVICE(0x05ac, 0x821a) },
+ /* Apple Mac Mini */
+ { USB_DEVICE(0x05ac, 0x4500) },
+
/* AVM BlueFRITZ! USB v2.0 */
{ USB_DEVICE(0x057c, 0x3800) },
--
Luiz Augusto von Dentz