MBP often won't wake after sleep.

Since keeping an eye on my swapfiles I've been able to use both VMWare and Parallels without issue. Before I close my lid I just verify that my swapfile is less than 1gb in size. If not I start quitting programs (safari, iTunes, Fireworks, etc) until I get my swapfile size down. This method has worked for me for several weeks now.

Call me mr thick im still new to Mac how do I do that ?

Just to add to this puzzle:

Just today I called tech support, they seemed stumped.

I filed an RMA to get this replaced, and a replacement Macbook pro is on it's way.

I've been plagued with this 'wake' problem since day 1 (which was 2 weeks ago). Today, my macbook wouldn't turn on at all after waking from sleep.

Usually if I left it plugged in after opening the lid for 10 minutes or so, it would finally boot up.


This afternoon was interesting. I was fiddeling around with it and thought to place my ear to the system to see if anything was trying to fire up.

Turns out.. something was clicking to the right of the mouse pad. I figured It was the hard drive. So, I lightly tapped underneath the laptop where the noise was coming from, and the **** thing turned on!

I think it has something to do with the hard drive. Next time I can't get it to wake up, i'm going to tap it again to see if that does the trick.

saintmonkey wrote:
... apple should come up with their own VMware solution that doesnt cause this fault ...

They did. It's called

Bootcamp. Free with the purchase of Leopard or Snow.
No sleep wake problems using it.
Dale

Dale Weisshaar wrote:
They did. It's called

Bootcamp. Free with the purchase of Leopard or Snow.
No sleep wake problems using it.
Dale

Really??? Since when did Apple change bootcamp support virtualization. That would be huge if they did. Dual-booting Windows on a Mac is a useless feature for many, completely useless for me personally. However, virtualizing Windows (and other OSes as well) on a running Mac OS X is a different animal altogether that I use often.

I see what you mean, but I would rather dual boot and not have any issues. Just a personal opinion and preference. And I rarely use Windows....actually just to access one Ill. State website that is not Mac friendly.

I didn't mean to imply Bootcamp was virtualization (but it came off that way ;)).

Bootcamp is fine for me but I can see why others would rather have instant access.

But, it's the cheapest way to go! No additional software.

Dale

Dale Weisshaar wrote:
I see what you mean, but I would rather dual boot and not have any issues. Just a personal opinion and preference. And I rarely use Windows....actually just to access one Ill. State website that is not Mac friendly.

I didn't mean to imply Bootcamp was virtualization (but it came off that way ;)).

Bootcamp is fine for me but I can see why others would rather have instant access.

But, it's the cheapest way to go! No additional software.

Dale

Yes, but the point is that Bootcamp is not a viable alternative to virtualization for many people. If the host OS is not running, one can't use it for anything nor interact with it from Windows. For many that matters and Bootcamp just doesn't compare in that use case. It's apples and oranges.

Thanks Dale

I use boot camp, but you have to logout of Snow leopard and boot up windows, I meant they should bring out their own Virtual Machine to run within OSX.

Message was edited by: saintmonkey

Wakeup black screen problem has not been observed since 10.6.4 was installed. (late '09 MPB 15"). Swap size observed as high as 2.7G.

I have 10.6.4 on my new (MacBookPro6,2, i5 2.4Ghz, 4G ram, 320G hdd, SMC ver. 1.58f16) and have the same problem, even with nothing in Swap.

The computer wakes fine if it's only been sleeping for a minute or so, but if it's been sleeping longer than that, then I can hear the HDD spinning up, and the LED on the front goes out, but the keyboard doesn't light up and the screen remains black. The only way to get the computer to wake is to press and hold the power button for a bit - after which the computer resumes from the hibernated state (all the running applications are there still and everything is fine again).

Very frustrating as I've only had the computer for 3 days!!

Bejap, that was exactly my problem on a same generation MBP. I solved it by disabling putting the harddisk to sleep when possible on both battery and power adapter tabs in the energy saver prefs panel. That's not like it should be, but as long as it works I'm fine with it.

I have the same model as Benjab, just purchased it at the beginning of this week. Photograper, do you know if disabling putting the hard disk to sleep when possible have any potential risks, eg burning out the disks significantly faster?

Hi Photographer - thanks for the suggestion, but disabling "putting the harddrive to sleep" isn't really a satisfactory "fix" for me.

I'm taking my MBP to a "genius bar" on Sunday to see what the Apple guys say. I'm hoping for either a new motherboard or a replacement machine, but seeing as so many other people are having the same problem, is it perhaps a design flaw in this particular model? Or is it just a software bug that they haven't fixed yet? We shall see...

So, I took my MBP to the "Apple Genius Bar", they had a look and acknowledged that there is a problem. I had also experienced a number of Kernel panics, and so it was decided that a new Logic Board (motherboard) was the ticket. 24 hours later and the repair was done....

But...

The problem is still there! So I've spoken to Apple again and have re-formatted the drive, and re-installed OSX 10.6.3. I've tried it just now and it's still not waking properly if it's slept for more than about 5 mins.

Very disappointing. Anyway, I'll keep testing it on 10.6.3, then I'll try doing an update to 10.6.4 and any other outstanding updates and see how we go.

Anyone else had any wins?

I had this same issue on my white MacBook. Phone Tech Support couldn't figure it out...BUT a guy at the local Genius Bar fixed it no problem!
I had made "inactive" the ethernet port. I never use it, so I didnt think twice about it. The machine always looks at that for a wakeup call, and it freaks when it's not there. My Screen was blank and the Hard drive was spinning and a lot of heat generated.
So He just made it active again, *and it has never done it since*. It was a real problem for me, but good as new now, for about a year.