MacBook not sleeping when I close the lid?

[DisplacedMic]

Hi guys,
My Macbook 5,1 is not sleeping when i close the lid anymore? Is there a setting i am missing in ML? I have changed quite a few variables lately (installed a SSD in place of the old HDD which i put in a data doubler in the optical drive slot) and upgraded the ram to 8 gigs.

i suspected that the data doubler might be the culprit, but "ejecting the disc" doesn't fix the problem. i can make the computer sleep manually, but just closing the lid doesn't do anything. doesn't even turn the screen off.

any ideas?

thanks!

Assertion status system-wide:
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
PreventUserIdleSystemSleep 0
ExternalMedia 0
UserIsActive 0
ApplePushServiceTask 0
BackgroundTask 0

Listed by owning process:
pid 72(mds): [0x0000000c0000012e] 00:00:34 BackgroundTask named: "com.apple.metadata.mds"
pid 160(helpd): [0x0000000c00000131] 00:00:25 BackgroundTask named: "com.apple.helpd.sdmbuilding"

Kernel Assertions: None


both of those processes could prevent sleep, right?

 

[DisplacedMic]

tried clearing the assertions, but it's still not sleeping when i close the lid. in fact the screen isn't even turning off.

 

[DisplacedMic]

i just removed the data doubler to see if that was the culprit and the mac is still not sleeping, so that wasn't the culprit.

any ideas anyone?

 

[madmacfan]

It could well be a hardware issue. If all else fails, I would recommend you book a genius bar appointment and get them to diagnose the fault.

 

[DisplacedMic]

It could well be a hardware issue. If all else fails, I would recommend you book a genius bar appointment and get them to diagnose the fault.

i might have to...although it worked fine in Snow Leopard. For yucks i might try installing snow leopard tonight and see how it does.

 

[madmacfan]

i might have to...although it worked fine in Snow Leopard. For yucks i might try installing snow leopard tonight and see how it does.

Before you go back to Snow Leopard, Try doing a SMC reset, to see if that helps matters. Also repair disk permissions in disk utility as this may help as well.

 

[DisplacedMic]

Before you go back to Snow Leopard, Try doing a SMC reset, to see if that helps matters. Also repair disk permissions in disk utility as this may help as well.

did that, and pram for S&Gs...

 

[madmacfan]

did that, and pram for S&Gs...

If you've already done that, then theres not much else you can do. You'll more than likely have to book an appointment at the genius bar, and have them diagnose the fault. The only other thing is doing a clean install, but i'd take it to the genius bar first before doing that as a last resort.

 

[DisplacedMic]

If you've already done that, then theres not much else you can do. You'll more than likely have to book an appointment at the genius bar, and have them diagnose the fault. The only other thing is doing a clean install, but i'd take it to the genius bar first before doing that as a last resort.

yeah - it's definitely the SSD not the OS. i'm a dope.

i wiped and installed leopard and then SL and no dice.
doing some google investigation now to see what's up but it looks like the lack of a traditional hard drive causes people problems with the OS recognizing the lid closing as a sleep trigger.

 

[DisplacedMic]

If you've already done that, then theres not much else you can do. You'll more than likely have to book an appointment at the genius bar, and have them diagnose the fault. The only other thing is doing a clean install, but i'd take it to the genius bar first before doing that as a last resort.

so i got it working for a while, but now when i close the lid the computer sleeps for a few seconds, but then turns back on, and the cycles rapidly between sleep and wake indefinitely. when i open the lid, the screen is locked but the machine is definitely not sleeping.

there are no programs running that i can tell and nothing is plugged into it.

i suppose it might be bullet-biting time re genius bar

 

[DisplacedMic]

Ok, so here's what's happening: for some reason the mac is thinking i'm opening the lid when it's closed.

if i manually put the machine to sleep, it sleeps indefinitely. if i close the lid, it cycles rapidly through sleeping waking which obviously is not a good thing.

syslog |grep -i "Wake reason"

yields

Jun 16 14:23:07 MacBook kernel[0] <Debug>: Wake reason: OHC1
Jun 16 14:24:37 MacBook kernel[0] <Debug>: Wake reason: EC LID0
Jun 16 14:24:53 MacBook kernel[0] <Debug>: Wake reason: EC LID0
Jun 16 14:25:09 MacBook kernel[0] <Debug>: Wake reason: EC LID0
Jun 16 14:25:24 MacBook kernel[0] <Debug>: Wake reason: EC LID0
Jun 16 14:29:29 MacBook kernel[0] <Debug>: Wake reason: EC LID0
Jun 16 14:37:02 MacBook kernel[0] <Debug>: Wake reason: EC LID0
Jun 16 14:37:13 MacBook kernel[0] <Debug>: Wake reason: EC LID0
Jun 16 14:39:18 MacBook kernel[0] <Debug>: Wake reason: OHC1
Jun 16 15:44:33 MacBook kernel[0] <Debug>: Wake reason: OHC1
Jun 16 15:45:17 MacBook kernel[0] <Debug>: Wake reason: EC LID0
Jun 16 15:45:28 MacBook kernel[0] <Debug>: Wake reason: EC LID0

from 2:24 until 2:39 the computer was "sleeping" with the screen closed but obviously it thinks the lid is opening which is what "EC LID0" means

i put the computer to sleep at 2:39 and woke it and then put it to sleep for an hour, but didn't close the lid. it slept fine until i pushed a button (OHC1)

then i closed the lid and it started the sleep/wake cycle again.

So my theory is either there is some weird process running or there's a physical problem. If it's a physical problem my only idea is that it's either the magnets failing or (far more likely) a loose wire connecting the monitor to the logic board.

but before i go poking around in there does anyone have any ideas given this info?

the reason i am hesitating just going to Apple is because i'm leaving the country Tuesday and i'd rather not have to mess with that. if i have to i can just shut it down every time i'm not using it and worry about it when i get back. but any help in the mean time would be much appreciated.

 

[chown33]

So my theory is either there is some weird process running or there's a physical problem.

To test the "weird process" hypothesis, do a Safe Boot, then see if it sleeps properly.

If it's a physical problem my only idea is that it's either the magnets failing or (far more likely) a loose wire connecting the monitor to the logic board.

Test the magnet. Use a steel ruler or something similar to find the location of the magnets on the edge of the screen. Then get another powerful magnet and place it near the sensor on the lower body. It will be next to the magnet when the lid is closed, so use the knowledge of the magnet's location to locate the sensor.

 

[DisplacedMic]

To test the "weird process" hypothesis, do a Safe Boot, then see if it sleeps properly.



Test the magnet. Use a steel ruler or something similar to find the location of the magnets on the edge of the screen. Then get another powerful magnet and place it near the sensor on the lower body. It will be next to the magnet when the lid is closed, so use the knowledge of the magnet's location to locate the sensor.

thank you so much for the wonderful suggestions, especially the magnet - i had not at all considered doing that myself but maybe i'll give it ago. Magnets, how do THEY work?

as it were, we had family over last night for father's day and i closed my laptop after showing someone something stupid on youtube and it slept through the night. no idea why it's now working when it wasn't yesterday. obviously i am going to have to figure this out as i can't be worrying every time i put my laptop in my bag.

I thought i'd created a "controlled environment" while trying to sort this out yesterday but obviously something changed. i don't spotlighting was still going and my assertions were "blank" but it could certainly be something like that and i'm sure it's obvious i'm in a bit over my head on this issue

i'll keep at it - thank you both for your help!

 

[chown33]

I thought i'd created a "controlled environment" while trying to sort this out yesterday but obviously something changed. i don't spotlighting was still going and my assertions were "blank" but it could certainly be something like that and i'm sure it's obvious i'm in a bit over my head on this issue

When you post things like "my assertions were blank", please describe exactly what you did to determine that fact. For example, if it was a command in Terminal, post the exact command-line and its output (select in Terminal, then copy and paste).

Accuracy is important. "i don't spotlighting was still going" seems to be missing a word or two, and I can't tell what it means or whether it's significant.

 

[Jesla]

Took two magnets and tried to make my rMBP go to sleep…
…didn't work although it sleeps when the lid is closed….
…Tried both on the screen and the body….no go…

just say'n….

 

[DisplacedMic]

When you post things like "my assertions were blank", please describe exactly what you did to determine that fact. For example, if it was a command in Terminal, post the exact command-line and its output (select in Terminal, then copy and paste).

Accuracy is important. "i don't spotlighting was still going" seems to be missing a word or two, and I can't tell what it means or whether it's significant.

Hi there,
Sorry I wasn't clear.

I don't THINK spotlight was still building the index as I checked by clicking and option-clicking on the icon and didn't see any activity, but I can't say for certain.

Regarding the command line for determining assertions i used:

pmset -g assertions

and it returned:

Assertion status system-wide:
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   PreventUserIdleSystemSleep     0
   ExternalMedia                  0
   UserIsActive                   0
   ApplePushServiceTask           0
   BackgroundTask                 0

Kernel Assertions: None

 

[DisplacedMic]

Took two magnets and tried to make my rMBP go to sleep…
…didn't work although it sleeps when the lid is closed….
…Tried both on the screen and the body….no go…

just say'n….

thanks for trying that

 

[DisplacedMic]

So it was working fine, and then i ran the battery down and it stopped working.
A few reboots and it's back to working again.

I find this very concerning. If there was something that i could fix then i could fix it and be done with it. if there was something broken then i could learn to deal with it by just shutting the computer down every time i pack it up. But having it work sometimes and not others is obviously going to make me worry every time i pack it up in my bag.

I guess what I don't understand is what possible reason a rapid sleep/wake cycle would ever be an option.

if PreventUserIdleSystemSleep =1 then it should Prevent sleep, not let it sleep for 5 seconds, wake it up, put it to sleep, wake it up in an infinite loop until the battery runs down. Obviously that isn't right...