5 Comments

Summary:

I can’t just bash Vista and ignore Mac problems when they arise and today for the first time one did on my MacBook Pro running Leopard.  I booted into Vista Ultimate using Boot Camp and played Call of Duty 4 for a while.  I am totally […]

BluetoothI can’t just bash Vista and ignore Mac problems when they arise and today for the first time one did on my MacBook Pro running Leopard.  I booted into Vista Ultimate using Boot Camp and played Call of Duty 4 for a while.  I am totally impressed with how well Vista runs on the MBP under both VMWare Fusion and natively with Boot Camp.

After I finished playing COD4 I restarted the MacBook Pro and booted into Leopard and was I surprised to find that not only was Bluetooth not working but the system didn’t realize there was a Bluetooth module installed.  I had a brief moment of panic thinking the hardware module must have been fried but I went online and in just a minute found a fix.  I shut down the MacBook and when it was time to start it up I held the Power Button down until I heard a loud beep from the system.  This signaled that a hard restart was coming up and sure enough the Bluetooth was running again when the system booted up.  Apparently from what I could tell the holding of the power button forces the power management system to reset which is the likely culprit.  Since I use the Bluetooth Apple keyboard and Mighty Mouse getting it working again was pretty important and I am thrilled that the fix was so simple.  So there you go, Macs can exhibit problems all of a sudden just like Vista, it just seems that the fix is much simpler.

You're subscribed! If you like, you can update your settings

  1. Unfortunately that is a common issue that has been around since Apple switched to Intel, and apparently wasn’t fixed with Leopard. I’ve had it happen twice in the last year on my macbook, once shortly after upgrading to Leopard.

    You can also solve the issue without a reboot by restarting the bluetooth daemon. Sorry, I don’t have the exact steps handy but you should be able to google it. One of the things I love about OS X (and all *nix/BSD systems) is that an awful lot of issues can be resolved without a reboot.

    Share
  2. Since upgrading to Leopard (and then doing a fresh Leopard install), I’ve had a few issues. The inability to find my wireless access point (both old one and new one) after waking up is annoying, and the inability to format an external disk (without partitioning) was a weird one.

    I also thought I was “upgrading” when I overpaid for the Airport Extreme, but it won’t maintain a connection with an “AirDisk” (not sure if it’s Leopard or router) and I have networking collisions/conflicts when running powerline adapters. After CES (when things calm down), I’m ebaying the base station if Apple hasn’t released any new firmware.

    Share
  3. Hi, well. I first upgraded to a Leopard Beta version. Then Re-upgraded with a genuene Leopard version. With both some problems where still there.
    After the first upgrade, some files on my Windows bootcamp partition wherent accesable via OS X anymore :S. And all kinds of small things also with the battery charger going from green to orange every 2 seconds and back.

    But recently I managed to free up enough space on my external drive and completely formatted my whole mac. Reinstalled Leopard from scratch and put back some stuff like ical, itunes library. I didnt use any system settings recovery.
    And now everything runs smoothly again. So I think a complete install of Leopard would be better than upgrading 10.4 to 10.5 if you have it running for some while.

    Share
  4. Thanks for the Bluetooth fix solution! Though it’s scary to hear that loud beep when the MacBook is re-starting it did the trick.

    Share
  5. Thank you so much, really helpful post. I thought I was going crazy when my MightyMouse wasn’t working.

    Share

Comments have been disabled for this post