Balthasar Schopman wrote:
I'm having similar problems on my Powerbook. Running OS 10.5.2.
Many other dutch people have the same problem. It is discussed in a topic on tweakers.net (forum: got.tweakers.net). Some of them found the problem was solved after removing their iStat widget and/or menu bar tool. It seems to have something to do with the memory monitor of iStat.
I don't run iStat. However, recently I found that it's something else people have been talking about in the same topic. When you let your laptop go to sleep with the power cable attached, detach the power cable and try to wake it up, it doesn't work. So a
solution (
couch) is to keep the power cable plugged or unplugged when the laptop is asleep.
Can you guys try these tips? *Maybe report what works?*
I experienced also that problem, after the 10.5.2 upgrade, but since I did "something" on my MBP, this problem has never happened again. I guess it's been a month now.
What I did is to disable Deep (Safe) Sleep.
I had noticed that I got the problem after having closed the lid and tossed the laptop in my backpack. I've been using Mac laptops since the first iBook. The sleep mode was by default the "light" sleep mode. When Safe Sleep mode got introduced, it was an opt-in option. I've not noticed when Apple made it the default.
So, the issue was that the 2GB of memory image was still dumped to the disk while I literally tossed the Mac in my backpack. The accelerometer most certainly has captured this and protected the drive ... resulting in a corrupt memory image.
Now that I've turned off Safe Sleep mode, there is no risk in rushing grabbing - and shacking - the laptop to my next meeting, or home.
As for the recent firmware upgrade, my MBP is excluded from this upgrade (B05). I believed it's because that firmware upgrade is for a specific processor design. My MBP is a 2.6GHz MacBookPro3,1 (I believe it's not a Penryn)