New (2005) powerbooks bluetooth problem

[puggy]

Could everyone with a new revision powerbook please report back here with the output of

Code: Select all

# lsusb

(part of usbutils - you may want to update to version 0.71 here) and

Code: Select all

# lsusb -v

and whether or not bluetooth is working for you. Alternatively, please please, email me the results at puggy@gentoo.org.

[puggy]

In case anyone else actually knows the answer: My bluetooth device doesn't seem to be recognised.
I have:

Code: Select all

Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 004: ID 05ac:020f Apple Computer, Inc.
Bus 002 Device 003: ID 05ac:1000 Apple Computer, Inc.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

while someone with (apparently) the exact same powerbook (and working bluetooth) gets

Code: Select all

Bus 004 Device 001: ID 0000:0000  
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 004: ID 046d:c016 Logitech, Inc. Optical Mouse
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 007: ID 05ac:8205 Apple Computer, Inc.     # This is the bluetooth device on his
Bus 001 Device 006: ID 05ac:020e Apple Computer, Inc. 
Bus 001 Device 001: ID 0000:0000 

Not only is the trackpad/keyboard device one digit different on our respective powerbooks (020f on mine, 020e on his) but his bluetooth device is 8205 as it should be (which is what OSX states mine to be) but I don't get that in linux, only the 1000 one which I've no idea what it is. Also, our usb buses are numbered differently, I'm not sure if that's a problem or not.
My lsusb -vv output

I would still appreciate reports of working and non-working bluetooth along with usb ids from lsusb to see if I'm alone on this or not.

Cheers

[Fat Bastard]

Do you dual boot Gentoo/OS X? Have you upgraded your Bluetooth firmware? If so then the following cautionary note should apply to both external and internal USB to Bluetooth adapters:

Important: Applying this firmware updater to a D-Link USB to Bluetooth adapter will make it incompatible with non-Macintosh systems.

net-wireless/bluez-utils provides hid2hci which may be helpful.

[puggy]

Do you dual boot Gentoo/OS X? Have you upgraded your Bluetooth firmware? If so then the following cautionary note should apply to both external and internal USB to Bluetooth adapters:

Important: Applying this firmware updater to a D-Link USB to Bluetooth adapter will make it incompatible with non-Macintosh systems.

net-wireless/bluez-utils provides hid2hci which may be helpful.

I think mine came with that update installed (Or OSx did it automatically) judging by the firmware revision number. Do you know if it is possible to devolve this?

Although, I do not think that is the problem at all as it states in that warning:

The Bluetooth Firmware Updater is for D-Link USB Adapters (revision B2 or later), and Apple internal Bluetooth modules on PowerBooks, PowerMacs, iMacs, iBooks, and eMacs.

...and then it states that:

Important: Applying this firmware updater to a D-Link USB to Bluetooth adapter will make it incompatible with non-Macintosh systems.

This suggests to me that only the D-Link USB adapters are rendered unusable by non-Mac systems, not the internal bluetooth module. Also, that suggests to me that it becomes unusable to non-mac systems, not unusable to linux on a mac system.

[Fat Bastard]

Do you dual boot Gentoo/OS X? Have you upgraded your Bluetooth firmware? If so then the following cautionary note should apply to both external and internal USB to Bluetooth adapters:

Important: Applying this firmware updater to a D-Link USB to Bluetooth adapter will make it incompatible with non-Macintosh systems.

net-wireless/bluez-utils provides hid2hci which may be helpful.

I think mine came with that update installed (Or OSx did it automatically) judging by the firmware revision number. Do you know if it is possible to devolve this?

Although, I do not think that is the problem at all as it states in that warning:

The Bluetooth Firmware Updater is for D-Link USB Adapters (revision B2 or later), and Apple internal Bluetooth modules on PowerBooks, PowerMacs, iMacs, iBooks, and eMacs.

...and then it states that:

Important: Applying this firmware updater to a D-Link USB to Bluetooth adapter will make it incompatible with non-Macintosh systems.

This suggests to me that only the D-Link USB adapters are rendered unusable by non-Mac systems, not the internal bluetooth module. Also, that suggests to me that it becomes unusable to non-mac systems, not unusable to linux on a mac system.

I think the internal adapter is also affected. There was a discussion about this on debian's powerpc mailinglist a while back. I'll see if I can find it.

Edit: clickety-click.

[mattdenner]

In case anyone else actually knows the answer: My bluetooth device doesn't seem to be recognised.
I have:

Code: Select all

Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 004: ID 05ac:020f Apple Computer, Inc.
Bus 002 Device 003: ID 05ac:1000 Apple Computer, Inc.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

I have the same Powerbook as you (UK version right?) and bluetooth was working for me back in 2.6.11-something. I had gnome phone manager working with my t810 but I seem to remember that I had to give the USB stuff a kick by rmmod'ing the ochi_hcd and immediately reinstalling it, i.e. do this all on one line:

Code: Select all

rmmod ohci_hcd ; modprobe ohci_hcd

Otherwise when you rmmod it you'll use the keyboard (because it's USB).

I'll give it another go in a minute to see whether 2.6.12-r3 is working; I haven't tried it since I upgraded my kernel.

[mattdenner]

I'll give it another go in a minute to see whether 2.6.12-r3 is working; I haven't tried it since I upgraded my kernel.

Right, here's what I get:

Code: Select all

powerbook matt # /etc/init.d/bluetooth start
 * Caching service dependencies ...     [ ok ]
 * Starting Bluetooth ...
 *     Starting hcid ...    [ ok ] 
 *     Starting sdpd ...    [ ok ] 
 *     Starting rfcomm ...    [ ok ]
powerbook matt # hcitool dev
Devices:
powerbook matt # hid2hci
Switching device 05ac:1000 to HCI mode was successful
powerbook matt # hcitool dev
Devices:
        hci0    00:11:24:66:16:CB
powerbook matt # hcitool scan
Scanning ...
        00:0A:D9:E4:81:D8       T610

Note that I've had these devices paired before this and I haven't applied any updates to my bluetooth hardware. My kernel is 2.6.12-r3. I'll post my lsusb output for you when I've upgraded it to the version you recommend.

Edit:
Here's something interesting for you: cleanly booted my system and done this:

Code: Select all

matt@powerbook ~ $ /usr/sbin/lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 006: ID 05ac:020f
Bus 001 Device 005: ID 05ac:1000
Bus 001 Device 001: ID 0000:0000
matt@powerbook ~ $ sudo /etc/init.d/bluetooth start
 * Starting Bluetooth ...
 *     Starting hcid ...  [ ok ]
 *     Starting sdpd ...      [ ok ]
 *     Starting rfcomm ...   [ ok 
]matt@powerbook ~ $ /usr/sbin/lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 006: ID 05ac:020f
Bus 001 Device 005: ID 05ac:1000
Bus 001 Device 001: ID 0000:0000
matt@powerbook ~ $ sudo hid2hci
Switching device 05ac:1000 to HCI mode was successful
matt@powerbook ~ $ /usr/sbin/lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 007: ID 05ac:8205
Bus 001 Device 006: ID 05ac:020f
Bus 001 Device 001: ID 0000:0000
matt@powerbook ~ $

The device changed ID! Still haven't upgraded usbutils yet though.

[puggy]

I think the internal adapter is also affected. There was a discussion about this on debian's powerpc mailinglist a while back. I'll see if I can find it.

Edit: clickety-click.

That isn't the same issue as back in May 2004 there were only pci bluetooth devices, not usb.

[puggy]

I upgraded to bluez-* 2.18 and the problem went away, I'm suspecting there was some weirdness in my 2.17 install as when I emerged that again, it also worked. Gah.

Cheers for the help.

Puggy