Monday, December 13, 2010

Troubleshooting MacBook wake from sleep problems

Our 3 yo Dual USB MacBook (Intel dual core) is having intermittent wake from sleep problems. It's on a WiFi network and running Leopard - 10.5. On lifting the lid it spins up then hangs with a faint blue screen. There's no cursor.

I haven't found a fix yet, but here's a list of what I've tried [4]. They're listed in the order I'd suggest. Of course the first thing to do with any ill-behaved machine is to check that your backups are good...

  1. Run Safe Mode start, (aka Safe Boot) then restart [2]
  2. Remove share mounts
  3. Login items - remove all
  4. Clean out list of remembered WiFi networks - Network:AirPort:Advanced. [5]
  5. Do not inactivate the ethernet port - even if you don't use it. Delete all Locales. [6]
  6. Disable Bluetooth
  7. Update Flash (or consider removing it forever)
  8. Input Managers - remove all. They are Satan's tool.
  9. StartupItems - remove all from Library\StartupItems and ~\Library\StartupItems if it exists. Do not mess with System\Library.
  10. Onyx: check corrupted preferences, check disk, delete caches including font caches
  11. Onyx: Repair Permissions :-) [1]
  12. Install disk, run disk utility check disk
  13. Reset SMC [3]
  14. Zap PRAM [2]
  15. Run hardware test in loop mode on install DVD
  16. Remove or update any low level software
    1. Look in /System/Library/Extensions for ideas, but dont' mess with /System. Look in Library/Extensions.
    2. Cisco VPN for example - uninstall requires terminal
    3. Retrospect Client [7]
    4. Fusion is another - it loads early. Update it.
  17. Look for messages on startup. Unfortunately Console captures a vast number of warnings and error messages even in a "healthy" system.
  18. Disable Safe Sleep (more a Leopard than Snow Leopard option?)
  19. Look for more ideas here: Tutorial: Dealing with Wake-from-sleep issues | MacFixIt - 2006
  20. Reinstall OS X (desperation move). If you're on Leopard, might as well upgrade to Snow Leopard.
  21. Send out for repairs - likely a hardware issue. Bad memory can do this and problems may not show up in the hardware test.

I'll update this post with the eventual outcome. As of this moment I'm trying Permissions [1] and SMC reset (more likely to help) and I'll try run the hardware test tonight in loop mode.

Update 12/18/10: The hardware test worked. The problem is much better. I wouldn't say it is perfect, but clearly some of the above measures helped. The two I'd most favor are "clean out list of remembered WiFi networks" and "reset SMC". I suspect this problem is less common with 10.6 and that, at least with 10.5, there are many contributing factors to "wake from sleep" failure. The fixes I made reduced the frequency, but it will still occur.

By way of comparison, there were NEVER any issues with the pre-hibernate sleep mode of 10.3 and MacOS Classic, but XP sleep mode is completely unusable. (I've no experience with Win 7 sleep.)

Update 6/17/11: This problem resolved. I think it was finally fixed in 10.6

See also:

-- footnotes

[1] OS X has reams of permission related issues. I have never, however, seen repair permissions help with any of them, much less anything else. It always finds things to "repair", but the "repairs" fix nothing. Repair Permissions is the OS X equivalent of a disconnected thermostat. It's there to distract the customer. Still, when all else fails, I suppose it's worth trying. Onyx will conveniently run Repair Permissions.

[2] Safe Boot, loop mode hardware test and zap PRAM all need a wired keyboard. There are terminal workarounds for Safe Boot.

[3] An Apple identified cause of wake from sleep issues - Intel-based Macs: Resetting the System Management Controller (SMC): "A portable Mac doesn't appear to respond properly when you close or open the lid." I have noted that sometimes the green light on my magsafe connector doesn't come on ...

[4] An infamous Discussion thread on MacBook Pro problems is a good source of ideas.

[5] I had at least 20-30 in my machine. I removed every one.

[6] I have done this in the past, but not on this machine.

[7] I had a leftover version from when I used a Win XP Retrospect Pro backup server. I had to find an old installer to safely uninstall this low level app that runs on startup.

1 comment:

us vpn said...

I think that would be fixed if you'd update your firmware.