Previous 1 2 Next 27 Replies Latest reply: Jun 19, 2014 9:09 AM by alterationbrick Go to original post
  • qbmarketing Level 1 Level 1

    I'm having this same issue after the latest update of Mountain Lion. Just thought I'd chime in here to monitor the thread for a suggestion that a fix is coming.

  • VoidBR Level 1 Level 1

    hi guys, i'm having same problem after upgrade to mountain lion. What can i do? I have a MAcbook Pro 13'. If I restore a backup to Lion, the problem disappear, but I want use the MTL.

  • schtuff Level 1 Level 1

    Just adding mine to the list. My mid-2010 MacBook Pro won't wake up IF I close my laptop to put it to sleep. Seems to be a problem since I ran the update for Lion last week. Now running  Mac OS X Lion 10.7.5 (11G56). I'll keep an eye out for any new solution ideas.


    Bumming me out as my iphone speaker is not working this week either and I feel like my Apple products are all giving up this week!

  • The Dubs Level 1 Level 1

    So pushing the power button once will wake my machine up.  It is a slow process, ~1 min. but will wake. 

  • schtuff Level 1 Level 1

    Does not work for mine. I have to hold the power button and do a full re-boot.

  • RanRoc2012 Level 1 Level 1

    Pushing power button once does not work for me either. I must do full re-boot.


    Just now, my MBP was in sleep...sleep light indicator working as normal...I plugged by iphone 4 into USB without waking machine and then it went into that unwakeable state! Sleep light indicator went black, display black, machine not responsive to built-in keyboard, but I can hear the computer  running. I had to hold power button down and re-boot.

  • The Dubs Level 1 Level 1

    So I fixed the slow startup when my laptop goes to sleep.  I changed the hybernate mode in Terminal.  My setting was 25.  I changed it to 3 but also could have done 0. 


    Check to see what your setting is: pmset -g | grep hibernatemode


    To change the setting: sudo pmset -a hibernatemode X


    Make sure X is either 0, 3, or 25. 


    Here is the explanation on what each number is:


    hibernatemode = 0 (binary 0000) by default on supported desktops.

    The system will not back memory up to persistent storage.

    The system must wake from the contents of memory; the system will lose context on power loss.

    This is, historically, plain old sleep. 

    hibernatemode = 3 (binary 0011) by default on supported portables.

    The system will store a copy of mem-ory memory ory to persistent storage

    (the disk), and will power memory during sleep. The system will wake from memory,

    unless a power loss forces it to restore from disk image. 

    hibernatemode = 25 (binary 0001 1001) is only settable via pmset.

    The system will store a copy of mem-ory memory ory to persistent storage

    (the disk), and will remove power to memory. The system will restore from

    disk image. If you want "hibernation" - slower sleeps, slower wakes, and

    better battery life, you should use this setting.

  • Advoccat Level 1 Level 1

    Thank you, The Dubs, It solved my problem with MacBook Unibody

  • shorewoodnick Level 1 Level 1

    The Dubs solution worked for me, but I had to change the default 3 to 25. Waking takes longer than before ML because, I assume, it has to get the disk image... but at least it wakes again. Any bets on what would happen if I changed back to 3?

  • artiebob Level 1 Level 1

    My machine has the same issue in that it takes a long time to wake up in mountain lion.

    I think it might be related to time machine and power nap. I posted a screenshot and additional information to the problem I am having in this post

  • Amy Guskin Level 1 Level 1

    Yet another person with this problem. I installed Mountain Lion last night on my mid 2011 27" iMac, which was running Snow Leopard completely successfully. The install *seemed* to go well, but I woke up this morning to a Mac that would not wake up, no matter how many keys I hit, how much I moved the mouse, and I even did the light touch on the power button trick. That failed, so I held the power button down for a hard reset. No go. I had to unplug, which makes me crazy. Before I got to that point I read a lot of posts here in the support communities, and since I really didn't want to monkey with PRAM and throwing out preferences, I just changed my Computer Sleep setting in the Energy Saver tab to "never." My understanding is that this problem is only after a long (i.e. overnight) sleep, so I won't know until tomorrow whether that "fixed" it (I use the term "fixed" loosely).


    Come on, Apple, get on the stick: this is unacceptable! Most of us having this problem aren't trying to run Mountain Lion on older, marginal systems with lots of hinky 3rd party apps. This should just work on most of our systems.

  • KQMac Level 1 Level 1

    Add me to the long list, same problem. Brand new iMac (less than 6 months old) has Mountain Lion, will not wake up from overnight sleep. I click the mouse, keyboard, tap the power button, nothing. Screen seems to light up a little (turns a lighter shade of black), but does not come back on at all. Only choice is to force shutdown the computer. This is extremely obnoxious for a brand new computer that costs this much.

    I tried the fix to set the screensaver to turn on quicker than the sleep mode, which does the make the computer wake up from short naps. But when it's asleep overnight or while I'm work, there's no getting it to wake up from sleep.I'm going to haul the computer to the genius bar this weekend and see what they say; I can't believe I have to deal with this on a brand new computer  

  • alterationbrick Level 1 Level 1

    It's been a while, but I have this problem too, and am equally frustrated. This black screen happens 100% of the time when waking the computer, now. I don't know what steps you took, or whether you fixed the problem, but if you did I am really interested to learn how. My current solution is to press a volume button; for some reason, the appearance of that gray rectangle will jolt the computer out of its black-screen state, and then I'll be able to log in. Quick, but not ideal; the way this problem has grown and progressed has me worried that some integral part of the software or hardware is degrading, but I have no idea what.

Previous 1 2 Next