Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

I make use of the rather clumsy 'closed clam' mode of operation. I close up my macbook pro, bring it to work, and plug in a USB keyboard and a monitor.

80% of the time, all is well.

The other 20% of the time, things proceed as follows:

  1. Unlock box appears on external monitor
  2. Enter password
  3. System unlocks
  4. 30 second later ...
  5. Go to black screen with mouse cursor

It looks just like the 'unlock' environment, only, of course, missing the unlock dialog box.

I've also seen the system momentarily display the unlock dialog box. If the system was idle long enough to power-save the display, but not to go into lock, wiggling the mouse will sometimes result in my desktop reappearing with the unlock password box appearing, as well, and then disappearing.

Any ideas?

share|improve this question
    
Please tag accordingly, indicating your machine’s exact model and OS version. –  Martín Marconcini Oct 21 '10 at 13:26
    
I don't see a tag that corresponds to my model of macbookpro, and I don't have rep to create tags. –  bmargulies Oct 21 '10 at 17:29
    
[macbookpro] and [snow-leopard] are as precise as we have now. You can add more details to your question, though. –  Dori Oct 22 '10 at 2:21
    
Are you running the latest update (10.5.8 or 10.6.5?). Is 'bluetooth devices can wake up' enabled? –  glenstorey Dec 2 '10 at 2:40
    
@glen yes, 10.6.5. What does bluetooth have to do with a USB keyboard? –  bmargulies Dec 2 '10 at 3:07
show 3 more comments

1 Answer 1

up vote 1 down vote accepted

I'll take a stab at how to collect the data needed to come up with an answer as to what and why the system isn't waking up properly. The new unibody MacBook Pro have much more sophisticated modes of clamshell mode so I'll assume you have one of those for now.

The best place to see what is happening after the event happens is the console application (or logging into the mac remotely with ssh to tail the logs as you are debugging this issue).

Sleep / wake events get a lot of log messages and you will want to look over a normal sleep wake to get familiar with all the messages that happen in which specific order and what normal times to begin and end the wake from sleep take.

A lot happens when the machine wakes as it needs to detect what is connected, if the display is shut, which graphics mode to wake up - what the display options and layout are. Then it transmits that info to all the running apps and has to put it's stuff together.

One thing to simplify things would be to disable all sorts of screen savers, display time outs and such. I've seen my mac get confused and wake from sleep just to engage a screen saver which went missing because I didn't change it and don't normally use it.

There have been several firmware updates in the last two years to tighten up this process as there were (and potentially are still) situations when the system doesn't respond in time or at all correctly.

Lastly - a poor display cable contact or impending hardware failure could be a cause of this. Not likely, but worth checking if you really want to nail this down.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.