Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ash06

macrumors member
Original poster
Dec 13, 2007
37
1
Hey guys, i recently bought 2 new macs, one being a imac and the current computer i'm on, which is a macbook pro. Both are heavenly computers and i and very happy with them:)

However, my MacBook Pro has one problem that occurs occasionally after i put the machine in sleep mode; the display doesn't work. It will remain black. No pixels, no backlight, nothing. Just as if the machine was off. However the machine is clearly on.
Any ideas??

Please someone, help me out there?:confused::confused:

Sorry, if i posted this on the wrong place, of is its already afound problem, i am not a frequesnt user of this forum. But i find its a great place for friendly help though :)
 
there are various causes (as I have searched on web) but none applied to my case...

things like putting the MBP back to sleep, plug the DVI adaptor, press power button and press some shortcut to force a reboot... all don't work

I had to hold the power button to force a shutdown to get it back (I have done this twice now, and the last time I did it the verify disk process reported error...had to reinstall the OS)
 
I have no idea if this is your problem, but I had the exact same thing and traced it to the MacAlly ICEKey keyboard driver. The one on their website will cause this problem, but if you email support they'll email you an updated version that fixes it.

Goodness knows why they don't just post the updated version on their website....

Obviously this advice only applies if you have a MacAlly ICEKey keyboard...
 
A lot of people around here have been having the same problem - MBPs being slow to awaken or not awakening at all. The 10.5.2 update is due to come out on Friday, and there's some speculation that it will fix the bug. So, maybe wait it out for a few days?
 
I had the same problem except with my Macbook ..... and honestly one day it just turned back on after being put to sleep. I dont know how it "fixed" itself but apparently it did, i tried everything and couldnt find a solution.... perhaps it just sensed my frustration and started doing what it was supposed to do ..
 
I have this problem as well, and the update seems to have only made it worse... Maybe re-installing OSX will help? Does anyone know if applecare would cover this?

Ace
 
I've been dealing with this problem for months; my hack of a solution is to just only put it to sleep if I absolutely must. Nothing seems to help.

Apple seriously needs to fix this because it kills one major point of having a laptop and I REALLY don't want to force my laptop to shut down. It can cause disk corruption and data loss...

10.5.2 didn't fix this, and on top of that, I now have an unstable wireless connection over 802.11n 5Ghz to an Airport station. Resorted to connecting to my older 820.11g Airport.
 
I had this problem too.. turns out the iStat Pro widget was the problem, I uninstalled that and it was fine.
 
I do use the iStat Pro widget but one of the reasons I DO use it is for the network monitoring.

Is it the whole networking section of iStat that does it? Or can you disable the IP address fetching and get a fix.

Edit: It seems they have a fixed version of iStat Pro for Santa Rosa MBPs in this thread:
http://forums.mactalk.com.au/showthread.php?t=39612

Going to try it out. The developer did say it was a bug in OS X though that they were trying to work around in the thread.
 
I do use the iStat Pro widget but one of the reasons I DO use it is for the network monitoring.

Is it the whole networking section of iStat that does it? Or can you disable the IP address fetching and get a fix.

Edit: It seems they have a fixed version of iStat Pro for Santa Rosa MBPs in this thread:
http://forums.mactalk.com.au/showthread.php?t=39612

Going to try it out. The developer did say it was a bug in OS X though that they were trying to work around in the thread.

Yeah they said they fixed it, but unfortunately the problem still exists.

Please disable the networking portion see if your problem goes away. If it does then we both know the answer ;)

I have a Santa Rosa machine myself and already went through this painful mess. Don't waste anymore of your time waiting for your machine to be useable after sleeping.
 
I turned off airport b4 I put my MBP to sleep, and that seemed to stop the problem of it not waking, so turning off the network portion in iStat just might be the solution. Ill try that instead and see how it goes.
 
Well I don't want to keep opening and shutting my MBP, but doing it a few times now and it came back from sleep fine. This is after installing their "SR" iStat Pro.

A point of interest though, it doesn't seem to be going fully into sleep. The light comes on but doesn't pulse and I can still hear the HD spinning....
 
Myself, I'm not using an external display. Just a power cord here.


I think I discovered a totally new problem for myself. I don't want to thread hijack, so if I don't figure this out I'll start my own thread.

My MBP won't go fully to sleep apparently. When I shut the lid the light comes on, the HD is still spinning and it doesn't pulse. If I pull the plug, it goes fully into sleep.

Also, if I put it to sleep without being plugged in, it does the same thing. If I connect the power and then disconnect it, it goes to sleep.

I've also tried this completely logged out, same issue.

Edit: Resetting PMU/PRAM didn't solve anything. meh


After a few tries with iStat Pro opened in my widgets (with network enabled), I've still had success coming back from sleep (after forcing it to totally go to sleep) however.
 
I'm having this issue too. Persists after uninstalling iStat as well.

At least the keyboard still works so I can press the Power button, then Return to safely power down the computer. Still annoying though.
 
Sleep problem with MB Pro

I have this issue. I put MB Pro SR 10.5.2 to sleep and close the lid. BUT MBP sometimes wakes from sleep with lid closed! Than after 10 seconds it return back to sleep. -> when i oped lid and MBP wakes, screen remains black.

But display issus is not big problem. I think, that big problem is that MBP weaks from sleep with closed lid. So i had to start using DeepSleep widget and can't use regular Apple sleep, which i really like. I curious what cause that waking up. 1) contact between keyboard and display. In MBP design, there is not big gap <- that means that if you squeeze MBP a little (something like in bag with books) MBP wakes. 2) SMS senzor on harddrive
 
Frak me!

10.5.2 or Graphic update broke external-only display functionality. Now... when i plug in external monitor and usb keyboard, close MBP lid and than wake up it with usb keyboard -> i got picture on external display for 5s, than MBP returns to sleep.

I tried reset PMRAM -> no help

now when i start MBP (shutdown before this) with external monitor (primary) pluged-in by DVI. Only lcd display (secondary) works. External not (primary). When i plug off external dislay... screen refreshes, but MBP's lcd remains as secondary display. But there is NO primary external display pluged in!
 
I'm just coming back to post my experience I've had so far.

After updating my iStat Pro I haven't had a single problem waking from sleep, it's come back fine every single time so far.

I also finally got my SMC to reset, I wound up holding the power button down for a really long time and just waited a few extra moments with everything unhooked (battery, power etc). So my MBP now also sleeps properly.

I don't want to declare it fixed yet, but so far so good for me. *knocks on wood*
 
I also have this problem on my SR MBP. I upgraded to 10.5.2 the day it came out but didn't have this problem occur until two days ago. Since then it has happened everytime I try to wake my machine. I disabled the network part of iStat and I'll see how that does with it (though it didn't make a difference for others).

I also just disabled Bluetooth devices being able to wakeup my MBP - I use Apple's Bluetooth Keyboard, not a Bluetooth mouse though. Seems like a longshot, but who knows...
 
Same problem, just a blank screen while the computer is functioning perfectly fine behind it. This was either caused by 10.5.2 or the Leopard Graphics Update that came right after it. I'm not sure which.

grrrr
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.