Re: [SOLVED] Re: albook 15": bluetooth stopped working after firmware upgrade to 1.1
Pierre, Sebastian,
thanks a lot for your verbose answers, which seems to really help. After
I heard from the toothing hype in the UK
<http://news.google.com/news?hl=en&edition=us&q=toothing&btnG=Search+News>
I became interested and was on the verge of buying a bluetooth adapter
(which seems to be necessary, if I understand correctly, if one has a
Titanium IV as I do) as the news came in on that Apple Firmware update.
So given the fact that I usually do not use a mobile phone and probably
therefore didn't have the slightest knowledge on the bluetooth
technology, your postings were really helpful. Especially as I also
didn't know anything until know on how to cvs files.
Seems to be my big knowledge day .. :)
Thanks again. Thanks, too, to those who didn't receive my answers for
their help they provided in other threads here the last time.
Best Regards
Wolfgang
On Mon, 2004-04-26 at 10:37, Sebastian Henschel wrote:
> * Pierre N <pierren@mac.com> [2004-04-26 09:25 +0200]:
> > On Sun, 2004-04-25 at 12:24, Wolfgang Pfeiffer wrote:
> > > On Wed, 2004-04-21 at 14:58, Sebastian Henschel wrote:
> > >
> > > [...]
> > >
> > > apple.com, on its "Bluetooth Firmware Updater 1.1":
> > >
> > > "Important: Applying this firmware updater to a D-Link USB to Bluetooth
> > > adapter will make it incompatible with non-Macintosh systems."
> > > <http://www.apple.com/support/downloads/bluetoothfirmwareupdater.html>
>
> note: they talk about the external adapter here (at least, that is how i
> understood it). perhaps they should mention that it is valid for the
> internal adapter as well.
>
> > > Anybody out there who knows more on that in the meantime, i.e. is there
> > > already a fix for it, or workaround, or whatever?
> > > Or is there even someone out there with a working bluetooth on Linux ppc
> > > after upgrading the machine to the new Buetooth Firmware?
> > >
> > I do have such a device working yes. It's a D-Link DBT 120 bluetooth USB
> > adapter updated to firmware 1.1. To get it working you have to get the
> > new utils from the CVS tree of bluez.
> >
> > 1) mkdir bluez
> > 2) cd bluez
> > 3) cvs -d:pserver:anonymous@cvs.bluez.org:/cvsroot/bluez login
> > 4) cvs -d:pserver:anonymous@cvs.bluez.org:/cvsroot/bluez co libs2
> > 5)cvs -d:pserver:anonymous@cvs.bluez.org:/cvsroot/bluez co utils2
> > 6) cd libs2
> > 7) ./bootstrap; ./configure; make; sudo make install
> > 8) cd ../utils2
> > 9) ./bootstrap; ./configure; make; sudo make install
> > 10) "Insert your usb adapter now"
> > 11) cd hid
> > 12) ./hid2hci
>
> the same applies to the internal device.
> that tool should output:
>
> Switching device 05ac:1000 to HCI mode was successful
>
> debian users do not have to do the "configure" thingy. libs2 and utils2
> ship with a debian directory where you can just
>
> fakeroot debian/rules binary
>
> in them. although it seems that the debian stuff is rather old,
> it works for me and my dial-up/sync profile. beware that you have to
> remove some other debian-bluetooth packages (bluez-pan,
> libbluetooth1-dev).
>
> bye,
> sebastian
--
Profile, Links: http://profiles.yahoo.com/wolfgangpfeiffer
Reply to: