IMPORTANT Darkwake=0 Flag can break auto-sleep in 10.8.1!

[Darrduck]

I also am having issues. I just built a hackintosh with the gigabyte z77-ds3h with mountain lion installed. My comp goes to sleep but when it tries to wake up my monitor does not come up even though my tower starts back up again. I tried darkwave=10 and darkwave=8 as well as the standard 0. Any ideas? I have my monitor plugged into my gt660 in the dvi input if that is any help. Y'all are rockstars.

 

[phaseshift]

Did you try another number, such as 8 or 9? I'd suggest trying 8.

I tried 8 same thing, haven't done 9 yet.

 

[camillionario]

Thanks for the heads up. When I get home I'm going to set "darkwake=8" and disable CPU PLL Overvoltage. From what I've been reading it can't hurt anything, so even if it doesn't fix the keyboard issues there shouldn't be any downsides.

try this, for me it worked. Fix keyboard problem

http://legacy.tonymacx86.com/viewtopic.php?f=7&t=22383&p=293096#p293096

 

[theshiv]

try this, for me it worked. Fix keyboard problem

http://legacy.tonymacx86.com/viewtopic.php?f=7&t=22383&p=293096#p293096

Thanks for that, but I stopped using a DSDT when I updated my BIOS to uEFI. I was able to get it to work by disabling XMP. Instead of 1600 memory, I now have 1333. I'll live with it!

 

[furbies]

This also works for me with a GA-B75N and i3-3225!

Could you clarify which DarkWake setting you're using ?

regards

furbies

 

[lollo78]

hi guys, my sleep works ok in manual mode but autosleep works partially: doesn't stop immediately the hard disk and the fan. i have tried darkwake 8, 0, 10... and tried to change energy setting to disable hard disk. My hackintosh before go to sleep the monitor and only after some minutes also fan and disk go to sleep. it's normal? why If I put manually in stop all go to sleep at first sight?

 

[the_gael]

hi guys, my sleep works ok in manual mode but autosleep works partially: doesn't stop immediately the hard disk and the fan. i have tried darkwake 8, 0, 10... and tried to change energy setting to disable hard disk. My hackintosh before go to sleep the monitor and only after some minutes also fan and disk go to sleep. it's normal? why If I put manually in stop all go to sleep at first sight?

There are other factors which can affect the sleep function as well - I have just in the last week had a look at someone's Hac which would not auto-sleep and nothing showed up when I ran pmset -g assertions.
I realised the machine had a LG CD Drive so I disconnected it and VOILA autosleep worked fine. The moral of the story is that issues with auto-sleep can sometimes be as basic as hardware that is not fully compatible. When I used to use internal optical drives I always used Sony Optiarc and never had an issue with them but other optical devices were hit and miss.

So if altering darkwake settings are having no effect maybe its something more basic. It might not be the optical drive in your case but worth checking.

Oh in case you have not run it
open a terminal window and issue the command
pmset -g assertions

does not have to be run as root.
If anything comes back as non zero check it out - a background task and external media would not always mean that they were preventing sleep but check if anything else is showing. If something looking like

pid 17(powerd): [0x000000090000012c] 04:04:30 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"

appears un-mount and disconnect any external media and see if that makes any difference.

 

[Say Heading]

My hackintosh before go to sleep the monitor and only after some minutes also fan and disk go to sleep. it's normal? why If I put manually in stop all go to sleep at first sight?

Just to make shure that it is not intentionally like this:
You are aware that you can set different timers in the energy saving control panel for monitor and computer?
As long as they are not set equal it would be normal behaviour to have the monitor dim first.

 

[lollo78]

Here I am! Sorry for the late answer but I was AFK for a couple of days.

Oh in case you have not run it
open a terminal window and issue the command
pmset -g assertions

This is my pmset -g assertions, captured after OS X boot, with no application started and no device connected:

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

Listed by owning process:
pid 1232(helpd): [0x0000000c00000175] 00:02:55 BackgroundTask named: "com.apple.helpd.sdmbuilding"

Kernel Assertions: 0x0388
* Kernel Assertion ID = 500
Created At = 19/09/13 22:21:02 CEST
Modified At = 19/09/13 22:26:08 CEST
Owner ID = 0xffffff80d15a8000
Level = 255
Assertions Set = None (4)

* Kernel Assertion ID = 501
Created At = 19/09/13 22:21:02 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d159e000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 502
Created At = 19/09/13 22:21:13 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff8011ffa000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 503
Created At = 19/09/13 22:22:44 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d157c000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 504
Created At = 19/09/13 22:22:44 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d1592000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 505
Created At = 19/09/13 22:22:44 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d158f000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 506
Created At = 19/09/13 22:22:55 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d1595000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 507
Created At = 19/09/13 22:22:55 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d159b000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 508
Created At = 19/09/13 22:22:55 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d1598000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 509
Created At = 19/09/13 22:22:55 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d15b2000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 510
Created At = 19/09/13 22:25:42 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff8012232600
Level = 255
Assertions Set = None (256)

* Kernel Assertion ID = 511
Created At = 19/09/13 22:37:22 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80122b1400
Level = 255
Assertions Set = None (128)

Just to make shure that it is not intentionally like this:
You are aware that you can set different timers in the energy saving control panel for monitor and computer?
As long as they are not set equal it would be normal behaviour to have the monitor dim first.

Same energy saver configuration for Monitor and Computer. Picture in attached!

 

[the_gael]

Here I am! Sorry for the late answer but I was AFK for a couple of days.



This is my pmset -g assertions, captured after OS X boot, with no application started and no device connected:

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

Listed by owning process:
pid 1232(helpd): [0x0000000c00000175] 00:02:55 BackgroundTask named: "com.apple.helpd.sdmbuilding"

Kernel Assertions: 0x0388
* Kernel Assertion ID = 500
Created At = 19/09/13 22:21:02 CEST
Modified At = 19/09/13 22:26:08 CEST
Owner ID = 0xffffff80d15a8000
Level = 255
Assertions Set = None (4)

* Kernel Assertion ID = 501
Created At = 19/09/13 22:21:02 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d159e000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 502
Created At = 19/09/13 22:21:13 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff8011ffa000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 503
Created At = 19/09/13 22:22:44 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d157c000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 504
Created At = 19/09/13 22:22:44 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d1592000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 505
Created At = 19/09/13 22:22:44 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d158f000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 506
Created At = 19/09/13 22:22:55 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d1595000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 507
Created At = 19/09/13 22:22:55 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d159b000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 508
Created At = 19/09/13 22:22:55 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d1598000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 509
Created At = 19/09/13 22:22:55 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80d15b2000
Level = 0
Assertions Set = None (4)

* Kernel Assertion ID = 510
Created At = 19/09/13 22:25:42 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff8012232600
Level = 255
Assertions Set = None (256)

* Kernel Assertion ID = 511
Created At = 19/09/13 22:37:22 CEST
Modified At = 01/01/70 01:00:00 CET
Owner ID = 0xffffff80122b1400
Level = 255
Assertions Set = None (128)




Same energy saver configuration for Monitor and Computer. Picture in attached!

@Lollo78

Looking at the output you received from the terminal command there is nothing there that would prevent autosleep.

I have gone back and read your post again and I think that what you are experiencing is quite normal behaviour which might vary dependent on hardware. For instance I have the brand new Apple Mac Mini I am writing this post on set to default power management and it behaves in the way that you describe. Even though the screen and the cpu/harddrive are set to sleep at the same time what actually happens is that the screen sleeps first and shortly afterwards the actual unit will sleep. As long as it is doing this without too long a time period and it always does go to sleep I would be quite happy with that.