Slashdot Mirror

← Back to Stories (view on slashdot.org)

Apple OS X 10.5.6 Update Breaks Some MacBook Pros

Posted by Soulskill on from the somebody-just-got-fired dept.

Newscloud writes "As PC Mag reported last week, Apple OS X 10.5.6 can break some MacBook Pros leaving some users (like me) with a dead backlit black screen after the Apple logo appears. While I initially thought I had a hardware failure, it turns out that there is a fix as long as you have an external display, keyboard and mouse. The problem only appears on the second restart, so if you sleep your MacBook a lot as I do, you might not realize the problem is related to the OS update you did the week before. The problem was related to older, incompatible firmware that Software Update wasn't flagging before the upgrade. This definitely gives weight to the argument for waiting a bit to run software upgrades."

9 of 313 comments (clear)

  1. Re:More bricked computers by noidentity · · Score: 4, Insightful

    Yet another misuse of the term "brick".

  2. How does Apple's QA miss problems like these... by Assmasher · · Score: 4, Insightful

    ...when they have such a small hardware deployment environment? Seriously... Linux runs on TONS of hardware, Windows runs on TONS of hardware. Apple's OSX runs (in a supported fashion ;)) on VERY little hardware.

    --
    Loading...
    1. Re:How does Apple's QA miss problems like these... by similar_name · · Score: 4, Insightful

      Exactly, I thought the whole point of Apple tightly controlling all the hardware was so this wouldn't happen. In agreeing with you I would add that Windows and Linux have nothing to very little to do with the hardware side of things.

    2. Re:How does Apple's QA miss problems like these... by Dogtanian · · Score: 5, Insightful

      the problem was it was a faulty firmware that slipped through software update and was pulled a half hour later. It was replaced with the right firmware but a few people needing to be on the BLEEDING EDGE of updates never reapplied the right firmware, and thus are the ones complaining now.

      Cut out the apologist bullshit.

      Was it an official Apple update? Was it reasonable that those users would install an official update with no indication that there was a risk to their system?

      Perhaps occasional f***-ups are inevitable, but it was still Apple's fault. Trying to imply that those users are to blame is fanboyish cult-defence of the worst order.

      --
      "Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
  3. Re:No one is safe from the "oops" bug by cnettel · · Score: 4, Insightful

    Well, you would suppose that the limited flexibility in configurations where you can get OS X would mean that those configurations that are supported are tested properly.

    Apple machines may be overpriced or not, but it's hard to deny that the company tries to make the argument that it provides an integrated environment.

  4. this sounds like user error to me by v1 · · Score: 4, Insightful

    Hooray, my MacBook Pro is working again. And this seems to confirm for me that the 10.5.6 update breaks some systems if you are running older firmware.

    Sorry but if you're skipping a firmware update, and running a major OS update on old firmware, you deserve a headache.

    The Software Update presents updates in the order Apple recommends you install them. Skipping one update to run another is a stupid thing to do. The worst combination I can imagine is a firmware and an os update being installed out of order.

    --
    I work for the Department of Redundancy Department.
    1. Re:this sounds like user error to me by v1 · · Score: 4, Insightful

      I would amend this by saying Apple probably shouldn't have let him do this. There is a firmware update required to update to mac os 9 (from 8.6) and another on some machines before upgrading from 9.1 to 9.2. (imacs only I think?) Apple will not ALLOW those OS's to install until the firmware update is applied. Some machines also required a firmware update before installing OS X.

      --
      I work for the Department of Redundancy Department.
  5. Re:No one is safe from the "oops" bug by Tanman · · Score: 4, Insightful

    So, how's that 'just workin' for ya?

    Sorry, I don't mean to be flamebait, but this story is irritating. If it were a Windows story, it would be, "Microsoft update bricks user pc's" with the summary "Microsoft, in yet another example of shoddy programming, has managed to brick billions of users' pc's with their latest auto-update. With most users unaware they can even disable these updates, is it really any surprise that they've screwed their customer once again?"

    Instead, we get this, "Ah gee golly look, I guess this little update means we should let someone else work the kinks out before we update our macs!" Nevermind that Apple has a history of shutting down their hardware via updates.

    NOTE: I believe brick == unrecoverable. I'm merely stating what I think the summary would have been, not what it should have been/etc.

  6. Re:Here we go by ToasterMonkey · · Score: 4, Insightful

    I don't see defensive Apple zealots, in fact, here are ALL the posts above, including yours..

    Yet another FW update that bricks machines.

    So, when you discouvered your Mac had what you thought was a hardware failure, who talked you back from the ledge? Are you in therapy?

    Hi, I'm a Mac! Look at me, I can update myself! Hi, I'm a PC! Wow look at that, he's updating himself! So how's the update going, Mac? Hello? Hello? Hellooooo!

    Haha :-D

    Apple zealots defending this lack of testing to their death. Imagine the trolls that would be out if this were a Vista update ;-)

    I know which system slashtarded trolls mostly support, and it's not Vista either. It's the one system that doesn't get idiotic comments like all the above, because updates _neeeeeever_ break it, and bad things just don't happen to it (that Slashdot reports). Quit making the rest of that community look bad.