Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I have this problem too. For those of you still looking, I called and this is what they said-
1. Remove power adapter, battery.
2. Press and hold Power button for 5 good seconds.
3. Replace battery, and your done.
He said this "repairs system settings".
I haven't tested yet but he said if that doesn't work, call back.
 
I have this problem too. For those of you still looking, I called and this is what they said-
1. Remove power adapter, battery.
2. Press and hold Power button for 5 good seconds.
3. Replace battery, and your done.
He said this "repairs system settings".
I haven't tested yet but he said if that doesn't work, call back.

Yeah, they haven't learned much over the past several months. That is what I was told to do back in November when this all started. That didn't work neither did any of the "fixes" Applecare had for me over the next month or so. Finally got a new machine, only to have it do the same things until I disable the networking portion of iStat.

Odd thing is that the "fix" doesn't seem to be the same for every instance. The iStat worked for me, but may(probably) won't work for all.

good luck!

JS
 
MacBook Pro Won't Wake from Sleep

Yeah, they haven't learned much over the past several months. That is what I was told to do back in November when this all started. That didn't work neither did any of the "fixes" Applecare had for me over the next month or so. Finally got a new machine, only to have it do the same things until I disable the networking portion of iStat.

Odd thing is that the "fix" doesn't seem to be the same for every instance. The iStat worked for me, but may(probably) won't work for all.

good luck!

JS

What is iStat and how do you disable it?
 
iSat... doesn't matter

Yeah, they haven't learned much over the past several months. That is what I was told to do back in November when this all started. That didn't work neither did any of the "fixes" Applecare had for me over the next month or so. Finally got a new machine, only to have it do the same things until I disable the networking portion of iStat.

Odd thing is that the "fix" doesn't seem to be the same for every instance. The iStat worked for me, but may(probably) won't work for all.

good luck!

JS

iSat has no effect on my sleep problem... still wakes up with a black screen
 
What is iSat?

I bought my MacBook pro in February and had no problems with sleeping until I added an external monitor. Apple's instruction tell you to close the lid of your MacBook Pro and then his a key from your external keyboard to wake it up so that you can see your external monitor. that's when I have the same problem everyone else has described. I don't have any problems with any of the things I have attached via USBs, which includes an external keyboard, mouse and back-up hard drive, only the monitor.

I would like to try the iStat thing suggested but don't know what iStat is or where to find it. Any suggestions?

iSat is a monitoring widget. Just google it... or go to the add widget page (through manage widgets)
 
just the version...

...too early to know if this is a real fix yet.

Been following the thread (from beginning to end). So i'm optimistic. But then posting #195 seems to already assert that it's a non-fix. Plbbbt. Only time (and perhaps lots of it) will really tell... and then we can still all be anxious that it's still in there, lurking, waiting for the most in-opportune time to rear back up and bite one's a**.

'Not sure of how to correlate "v1.5" that the firmware installer called itself with what SystemProfiler says. 'Whatever.

The install process went OK for me. Forafireescape, can you confirm that the update is definitely installed for you?... check SystemProfiler.

To be clear(er), SystemProfiler says i now have "Boot ROM Version: MBP31.0070.B07", on a 2.2 GHz MBP, 15".

--

BTW, can someone enlighten me to (the difference between) "SantaRosa" and "Penryn".


Thanks,
pax,
Karl
*----->

Penryn is the current version of MBP on the market, Santa Rosa is the last one. So far, it SEEMS that the Santa Rosa MBPs have the sleep problem - anybody with a new Penryn having problems?
 
I just wait the minute as my computer loads all the data it has cached in deep sleep back into RAM and everything works. Sure it looks like the computer doesn't wake up immediately, but just take a break or something and the computer will wake up.

doesn't work for me either
 
So, I'm running on a MacBook Pro with Boot ROM version ending in B05, just had the issue where the system refused to come out of sleep -- the only way I could get my screen to turn back on was with the DVI-to-VGA adapter, and then it was a black screen with a mouse pointer.

I've noticed something similar with all of the occurrences I had with this so far... this error is in the Console at the time it happens originally:

Apr 12 23:40:57 -macbook-pro kernel[0]: NVDA::setPowerState(0x46e7800, 0 -> 2) timed out after 45124 ms
 
error message, eh?

So, I'm running on a MacBook Pro with Boot ROM version ending in B05, just had the issue where the system refused to come out of sleep -- the only way I could get my screen to turn back on was with the DVI-to-VGA adapter, and then it was a black screen with a mouse pointer.

I've noticed something similar with all of the occurrences I had with this so far... this error is in the Console at the time it happens originally:

Apr 12 23:40:57 -macbook-pro kernel[0]: NVDA::setPowerState(0x46e7800, 0 -> 2) timed out after 45124 ms

Hmm. That is interesting. So if there is an error message, then there should be a way to fix the problem.
My MBP has the same Boot ROM as you... 0070.B05, and it says it does not need the firmware update.
I've had the same experience with the DVI adapter too... if you hook up an external display, you can get it to work that way too - and you can see everything you are supposed to see. So it seems that there is some sort of hangup with the MBP telling the graphics card to change it's power state (turn on I presume), and hooking up an external display helps it out of it's confusion.
I'll check my Console next time it happens and see what I get for messages.
UPDATE: So - I can duplicate the sleep problem pretty much at will by interrupting the sleep or wake process by closing or opening the lid too soon, and here is the message I get at the time of the stuck screen:
(Date & time) ScreenSaverEngine[1008] Screen Saver is running in blackout mode
I've seen other's report the same mesage.
I can type in my password, wait a second or two, push the power button... then R, and it re-boots. I have a disturbing number of error messages in boot up as well... but that is another topic. None that I see seem to have anything to do with graphics or screen savers or sleep... mostly to do with software I've installed and un-installed - so obviously there are some leftover bits. Have to work on that....
 
The problem got bad enough that I had to install Mac OS X Tiger on my MacBook Pro until I have time to sit down and figure out what the heck is going on with Leopard, I don't know if I'm going to wind up with 10.5.1 or what. Maybe I'll just stay on Tiger until 10.5.3 or 10.5.4 comes around, hopefully by then these annoying little problems will be ironed out.
 
back to ...

The problem got bad enough that I had to install Mac OS X Tiger on my MacBook Pro until I have time to sit down and figure out what the heck is going on with Leopard, I don't know if I'm going to wind up with 10.5.1 or what. Maybe I'll just stay on Tiger until 10.5.3 or 10.5.4 comes around, hopefully by then these annoying little problems will be ironed out.

So you did it, did you?
I've been seriously considering going back to tiger too. The only thing holding me back is the backup and saving of all my files and emails...
I just had a kernel panic and osx shut down when I tried to wake it. I plugged in a usb mouse and the power cord while it was asleep - and in the wake up process it woke and then went back to sleep when I entered the password, the second wake it hung - not to be recovered until I did a hard re-start. Bleh. I didn't have tiger long enough to know if there were any problems with it... but I'm pretty sure it wasn't this full of bugs.
 
back to Tiger

Well - I did it too.
Did an erase and install, back to Tiger. Have tried to make it hang in the wake process, and so far it has woken up. One time I thought maybe it was stuck at the black screen, but I just closed the lid, waited a few seconds till it was asleep again, opened it and viola - back in business. Haven't had to re-set it yet. I'll post if I do.. but it most certainly seems to be a leopard (probably 5.2 and/or graphics update) problem.
I do have to get used to Tiger again - a few different ways of doing things - but it "JUST WORKS."
I find the current Mac commercial (with the therapist - it's not my fault) amusing. Since it is actually Leopard not playing nice with the MBP.... exactly opposite of what they are trying to get accross in the advertising. My Windows PCs have never had such a weird problem... XP Home on a P4 3.0... runs great.
Oddly enough, XP Runs better on my MBP than Leopard does right now. The only thing I can't do in Windows on the mbp is control the fan speeds - if I could do that without using OS X...... well I'll leave it there.
 
firmware fix it for anyone?

Has the 1.5 (or 1.5.1) firmware fixed this problem for anyone??? Thread has been quiet all of a sudden - maybe the problem went away? Is it safe to load leopard again yet?
 
thankfully this hasn't happened to me, i'm in 10.5.2 but i don't think i'd want to upgrade to the graphics update. i'll wait a while before i install the latest updates.

any updates on this problem's cure?
 
Has the 1.5 (or 1.5.1) firmware fixed this problem for anyone??? Thread has been quiet all of a sudden - maybe the problem went away? Is it safe to load leopard again yet?

Hasn't fixed this issue for me. Just when I think it went away, it strikes again. I also never received the software update, but I heard it was only for certain processors. Not positive on any of this, just speaking from my personal experience. The problem still lingers, however, not as pertinent.
 
Penryn is the current version of MBP on the market, Santa Rosa is the last one. So far, it SEEMS that the Santa Rosa MBPs have the sleep problem - anybody with a new Penryn having problems?

I had a SR with this exact issues so I had mine exchanged for Penryn and havent had a single issue.
 
I had a SR with this exact issues so I had mine exchanged for Penryn and havent had a single issue.

Hmm. That would be nice - I doubt they'll exchange mine - I've had it for about 6 months now... I'll try the firmware update, go back to leopard, and maybe even wait for 5.3... but if it still has the sleep problem after that, I will be calling applecare and asking for an exchange.
 
It's the display only

I've been having this problem for a while now, but tonight I'd previously enabled the 'Share Screen' and 'Connection' facilities in Leopard before putting the MacBook Pro to sleep. It wouldn't wake up, so I tried to share the screen from my iMac. On the 'shared screen' window I saw the 'screen unlock' request for my user name and password, even though the MacBook Pro screen was blacked out.

I found I could also remotely connect and extract the file I wanted from my MacBook onto the iMac. This shows that the disk, memory and processor of the MacBook were functioning OK and not in sleep mode. I suspect some graphics display software or firmware.
 
i upadated with the firmware
and today it happened 3 times.
at first it was waking very fast actually but after a couple it went to the *******

i do not have enough anger to add this problem to my list. :eek:
 
i upadated with the firmware
and today it happened 3 times.
at first it was waking very fast actually but after a couple it went to the *******

i do not have enough anger to add this problem to my list. :eek:

UUGGH! And I was hoping that this firmware was going to fix it. Some have reported that it did - but obviously if you're still having the problem... IT'S NOT FIXED YET APPLE!!! I've re-installed leopard again - but I am NOT updating it until I hear some good reports about 5.3. It was 5.2 and the graphics update that wrecked mine... so far with just 5.0 it is sleeping and waking just fine.
 
spot on...

I've been having this problem for a while now, but tonight I'd previously enabled the 'Share Screen' and 'Connection' facilities in Leopard before putting the MacBook Pro to sleep. It wouldn't wake up, so I tried to share the screen from my iMac. On the 'shared screen' window I saw the 'screen unlock' request for my user name and password, even though the MacBook Pro screen was blacked out.

I found I could also remotely connect and extract the file I wanted from my MacBook onto the iMac. This shows that the disk, memory and processor of the MacBook were functioning OK and not in sleep mode. I suspect some graphics display software or firmware.

Yep - it is definitely the display... or the card... that's been confirmed and well documented... ;)
 
Sorryy!

Hi, sorry
but i'm a newbie here

and i have a problem with my mbp lid.
how do i start a new thread??:confused::confused::confused:

please help. thank you
 
Hi, sorry
but i'm a newbie here

and i have a problem with my mbp lid.
how do i start a new thread??:confused::confused::confused:

please help. thank you

first
research
then
once you do that enough you will figure out how to post a thread if the issue still is around
 
did you read the whole thread?

Hi, sorry
but i'm a newbie here

and i have a problem with my mbp lid.
how do i start a new thread??:confused::confused::confused:

please help. thank you

Hi - yes, as stated, do some research first before starting new threads - if you're having the same "wake to black screen" issue that is discussed at length on this thread, don't start a new one! It's well documented, and so far the ONLY definitive solution seems to be downgrading OS X to 10.4.11 or 10.5.0 by backing up your data and doing a full erase & re-install. Some have had luck with an archive and install... but not me. I went to Tiger first, confirmed that it did not have the issue, and am now running 10.5.0. I will NOT UPDATE leopard until I hear some good things about 10.5.3 after its release. It seems to be the 5.2 or the graphics update that triggered it for most.
I was hoping that the latest firmware would fix it - but by reports, some are still having the problem after updating. All the other ideas like remove iSat pro, reset the power management, other minor tweaks have had limited success.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.