Jump to content
mod55

El Capitan - Problems with sleep

30 posts in this topic

Recommended Posts

Hi all,

I have installed El Capitan on the following hardware:

 

Intel Core i7 4790K
Gigabyte GA-H97-D3H
16 GB RAM
Palit Super JetStream 980 GTX
2 x Samsung 250 GB SSD

 

So far the system runs fine. The only thing I would like to have is a running sleep Mode. If I put the system to sleep it takes 1-2 Minutes until all LEDs are off. I wait and hit the space key to wake up. The display stays dark an I have no picture. I have to do a hard reset to bring the system back to life. Unfortunately after this some of the BIOS settings have changed (e.g. the SATA Config switched to RAID instead of AHCI.

 

I attached my config.plist.

 

I use the following kexts:

Fakesmc

IntelMausiEthernet

VoodooHDA

 

Currenty I really don't know where to start to get the sleep mode working.

 

I highly appreciate any help.

 

Thanks 

 

MOD55

config.txt

Share this post


Link to post
Share on other sites
Advertisement

Hi, searched the console and regarding wake and sleep I get the following entries:

 

wake:

03.10.15 22:36:24,325 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()

03.10.15 22:36:35,690 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,692 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,694 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,697 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,700 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,703 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,706 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,707 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,709 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,728 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,744 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:36,566 apsd[73]: Peer [pid=338] requested push wake but lacks APSPushWakeEntitlement
03.10.15 22:36:44,402 com.apple.photomoments[415]: Photomoments process awakened.
 
sleep:
03.10.15 22:33:39,000 kernel[0]: ACPI: sleep states S3 S4 S5
03.10.15 22:33:53,259 GoogleSoftwareUpdateAgent[303]: 2015-10-03 22:33:53.193 GoogleSoftwareUpdateAgent[303/0xa2f6f000] [lvl=2] -[KSAgentApp setupLoggerOutput] Agent settings: <KSAgentSettings:0x60e490 bundleID=com.google.Keystone.Agent lastCheck=2015-10-03 19:27:36 +0000 checkInterval=18000.000000 uiDisplayInterval=604800.000000 sleepInterval=1800.000000 jitterInterval=900 maxRunInterval=0.000000 isConsoleUser=1 ticketStorePath=/Users/rknabe/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore runMode=3 daemonUpdateEngineBrokerServiceName=com.google.Keystone.Daemon.UpdateEngine daemonAdministrationServiceName=com.google.Keystone.Daemon.Administration logEverything=0 logBufferSize=2048 alwaysPromptForUpdates=0 productIDToUpdate=(null) lastUIDisplayed=(null) alwaysShowStatusItem=0 updateCheckTag=(null) printResults=NO userInitiated=NO>
03.10.15 22:34:13,151 AirPlayUIAgent[317]: 2015-10-03 10:34:13.151397 PM [AirPlayUIAgent] BecomingInactive: NSWorkspaceWillSleepNotification
03.10.15 22:34:13,361 WindowServer[150]: no sleep images for WillPowerOffWithImages
03.10.15 22:34:56,000 kernel[0]: Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 1
03.10.15 22:36:23,000 kernel[0]: ACPI: sleep states S3 S4 S5
03.10.15 22:36:23,000 kernel[0]: Sleep failure code 0x00000000 0x1f006700
03.10.15 22:36:36,308 GoogleSoftwareUpdateAgent[302]: 2015-10-03 22:36:36.305 GoogleSoftwareUpdateAgent[302/0xa2f6f000] [lvl=2] -[KSAgentApp setupLoggerOutput] Agent settings: <KSAgentSettings:0x70ff80 bundleID=com.google.Keystone.Agent lastCheck=2015-10-03 19:27:36 +0000 checkInterval=18000.000000 uiDisplayInterval=604800.000000 sleepInterval=1800.000000 jitterInterval=900 maxRunInterval=0.000000 isConsoleUser=1 ticketStorePath=/Users/rknabe/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore runMode=3 daemonUpdateEngineBrokerServiceName=com.google.Keystone.Daemon.UpdateEngine daemonAdministrationServiceName=com.google.Keystone.Daemon.Administration logEverything=0 logBufferSize=2048 alwaysPromptForUpdates=0 productIDToUpdate=(null) lastUIDisplayed=(null) alwaysShowStatusItem=0 updateCheckTag=(null) printResults=NO userInitiated=NO>
 
 
I tried to find a solution, but I can not find a good hint.
 
Thanks for help
 
MOD55
 
 

Share this post


Link to post
Share on other sites

I am having kinda same problem with sleep mode. My hack goes to sleep and wake up immediately all the time when I press the sleep button. Power management kext from Yosemite do not work. Any ideas how to fix it? my config in the attachment. 


 

Hi, searched the console and regarding wake and sleep I get the following entries:

 

wake:

03.10.15 22:36:24,325 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()

03.10.15 22:36:35,690 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,692 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,694 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,697 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,700 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,703 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,706 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,707 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,709 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,728 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:35,744 apsd[73]: Attempt to set push wake topics without dark wake enabled: ()
03.10.15 22:36:36,566 apsd[73]: Peer [pid=338] requested push wake but lacks APSPushWakeEntitlement
03.10.15 22:36:44,402 com.apple.photomoments[415]: Photomoments process awakened.
 
sleep:
03.10.15 22:33:39,000 kernel[0]: ACPI: sleep states S3 S4 S5
03.10.15 22:33:53,259 GoogleSoftwareUpdateAgent[303]: 2015-10-03 22:33:53.193 GoogleSoftwareUpdateAgent[303/0xa2f6f000] [lvl=2] -[KSAgentApp setupLoggerOutput] Agent settings: <KSAgentSettings:0x60e490 bundleID=com.google.Keystone.Agent lastCheck=2015-10-03 19:27:36 +0000 checkInterval=18000.000000 uiDisplayInterval=604800.000000 sleepInterval=1800.000000 jitterInterval=900 maxRunInterval=0.000000 isConsoleUser=1 ticketStorePath=/Users/rknabe/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore runMode=3 daemonUpdateEngineBrokerServiceName=com.google.Keystone.Daemon.UpdateEngine daemonAdministrationServiceName=com.google.Keystone.Daemon.Administration logEverything=0 logBufferSize=2048 alwaysPromptForUpdates=0 productIDToUpdate=(null) lastUIDisplayed=(null) alwaysShowStatusItem=0 updateCheckTag=(null) printResults=NO userInitiated=NO>
03.10.15 22:34:13,151 AirPlayUIAgent[317]: 2015-10-03 10:34:13.151397 PM [AirPlayUIAgent] BecomingInactive: NSWorkspaceWillSleepNotification
03.10.15 22:34:13,361 WindowServer[150]: no sleep images for WillPowerOffWithImages
03.10.15 22:34:56,000 kernel[0]: Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 1
03.10.15 22:36:23,000 kernel[0]: ACPI: sleep states S3 S4 S5
03.10.15 22:36:23,000 kernel[0]: Sleep failure code 0x00000000 0x1f006700
03.10.15 22:36:36,308 GoogleSoftwareUpdateAgent[302]: 2015-10-03 22:36:36.305 GoogleSoftwareUpdateAgent[302/0xa2f6f000] [lvl=2] -[KSAgentApp setupLoggerOutput] Agent settings: <KSAgentSettings:0x70ff80 bundleID=com.google.Keystone.Agent lastCheck=2015-10-03 19:27:36 +0000 checkInterval=18000.000000 uiDisplayInterval=604800.000000 sleepInterval=1800.000000 jitterInterval=900 maxRunInterval=0.000000 isConsoleUser=1 ticketStorePath=/Users/rknabe/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore runMode=3 daemonUpdateEngineBrokerServiceName=com.google.Keystone.Daemon.UpdateEngine daemonAdministrationServiceName=com.google.Keystone.Daemon.Administration logEverything=0 logBufferSize=2048 alwaysPromptForUpdates=0 productIDToUpdate=(null) lastUIDisplayed=(null) alwaysShowStatusItem=0 updateCheckTag=(null) printResults=NO userInitiated=NO>
 
 
I tried to find a solution, but I can not find a good hint.
 
Thanks for help
 
MOD55

 

for your problem, try to add darkwake boot flag to your config and also try to add this to your config:

 

 

 

<key>InjectEDID</key>

<true/> 

 

and 

 

 

<key>HaltEnabler</key>

<true/> 

Share this post


Link to post
Share on other sites

Hi,

I tried darkwake, InjectEDID and HaltEnabler.

Nothing changed.

 

Any other suggestions.

Thanks 

 

MOD55

Share this post


Link to post
Share on other sites

I am having similar problems with similar chips, only my sleep WAS working and now does not. I have loaded the NVIDIA web drivers, as my 750 Ti only wanted to display 1280x1024 without this. I also reinstalled some software last night (fresh installs). Still sleep seemed to work until this morning's restart after more software install work. I will be following any suggestions that seem to work for you.

 

After each restart now, my NVIDIA web drivers list OS X Default Graphics Driver, no matter what I choose before the restart. Also, even thought it shows this, all graphics seem to work fine. I have the nvda_drv=1 boot flag active in Clover.

Share this post


Link to post
Share on other sites

Just updating you guys with fresh information. According to the last clover ticket http://sourceforge.net/p/cloverefiboot/tickets/179/almost everyone has troubles with sleep. This is the bug of El Capitan. Tmrw I will try to dig it deeply. Will try to configure power management kext to our systems. Cheers!

Share this post


Link to post
Share on other sites

I have the same problem. The machine goes in sleep mode, but when I press the keyboard it starts with screen off. If I wait without do anything it goes sleep again. If I press the keyboard repeatedly, it starts as normal with screen on. I did not have this problem with Yosemite.

I have Clover 3277 EFI on legacy bios.

Share this post


Link to post
Share on other sites

Hi guys,

I don't really know if I am facing a El Capitan Problem. I just installed Windows 10 for some testings, and I faced the same problem with the wake from Stand by.

Additionally I tested the Hacki with the OnBoard Grafik with El Capitan and Windows, and I have the same issue.

If I start MacIASL and try to compile the DSDT which I have in standard, I get a lot of errors. I thin there is for me something strange going on.

 

If you have an idea I am open for everything 

Share this post


Link to post
Share on other sites

I noticed that Gigabyte released new BIOSes the past couple of months, featuring "better Haswell compatibility". Probably worth a shot.

Share this post


Link to post
Share on other sites

Hello again, looks like power management with NullCpuPM.kext not work anymore in El Capitan. anyone know some options? Thank u for ur ideas

Share this post


Link to post
Share on other sites

Hi all,

I have installed El Capitan on the following hardware:

 

Intel Core i7 4790K

Gigabyte GA-H97-D3H

16 GB RAM

Palit Super JetStream 980 GTX

2 x Samsung 250 GB SSD

 

So far the system runs fine. The only thing I would like to have is a running sleep Mode. If I put the system to sleep it takes 1-2 Minutes until all LEDs are off. I wait and hit the space key to wake up. The display stays dark an I have no picture. I have to do a hard reset to bring the system back to life. Unfortunately after this some of the BIOS settings have changed (e.g. the SATA Config switched to RAID instead of AHCI.

 

I attached my config.plist.

 

I use the following kexts:

Fakesmc

IntelMausiEthernet

VoodooHDA

 

Currenty I really don't know where to start to get the sleep mode working.

 

I highly appreciate any help.

 

Thanks 

 

MOD55

 

I have the same mobo as you, but with a HD6870 I have exactly the same simptons and problem!

 

Can't come back from sleep, reset is always needed.

 

I just use Fakesmc, IntelMausiEthernet, and a USB Fix.

Share this post


Link to post
Share on other sites

I have the same problem. If I put my machine to sleep.. and as soon as it goes off, I click mouse or keyboard.. it will wake up. But if I wait until I hear a relay activated sound, I can only do a hard reset. 

I kind of solve the problem by changing the power control mode in BIOS from S3 to S1 only... it is not perfect but it works.

Share this post


Link to post
Share on other sites

Hi all,

does anybody have some news on this issue?

@allenwkk: What exactly you have changed. I cannot find inside BIOS options like this.

 

Thanks 

 

MOD55

Share this post


Link to post
Share on other sites

MOD55, it is under POWER - SUSPEND MODE - S1, S3 , or AUTO... S3 is suspension to RAM, S1 is only putting display and CPU to sleep (fans are all on).

 

good luck 

Share this post


Link to post
Share on other sites

I am having similar problems with similar chips, only my sleep WAS working and now does not. I have loaded the NVIDIA web drivers, as my 750 Ti only wanted to display 1280x1024 without this. I also reinstalled some software last night (fresh installs). Still sleep seemed to work until this morning's restart after more software install work. I will be following any suggestions that seem to work for you.

 

After each restart now, my NVIDIA web drivers list OS X Default Graphics Driver, no matter what I choose before the restart. Also, even thought it shows this, all graphics seem to work fine. I have the nvda_drv=1 boot flag active in Clover.

 

Yeah, I'm quoting myself...but I have new information.

 

The NVIDIA web driver was fixed with the latest update, so that issue is solved. Also, sleep is mostly working again now – possibly completely, but still needs more time to test. I think tracking down this issue is what did it:

 

 

[How To] Remove Extra Clover BIOS Boot Entries & Prevent Further Problems

Share this post


Link to post
Share on other sites

Well, did some changes, and now the system is operating very well, except for sleep. Setting darkwake=1 or 8 in Clover seems to do nothing. I think this is a problem with El Capitan. Currently, my computer "wakes" and shows a mouse pointer on a black screen. The computer is completely unresponsive from the keyboard or mouse at this point and must go through a hard reset. Also, I have a DVR operating on this system, and it seems to record properly even though it will not wake properly when I come home. I get the same "dark wake not enabled" messages in the console whether I set the dark wake boot flags in Clover or not.

 

No darkwake boot flag:

10/20/15 10:38:16.213 PM WindowServer[151]: CGXDisplayDidWakeNotification [123691820922]: posting kCGSDisplayDidWake
10/20/15 10:38:22.703 PM ntpd[182]: wake time set +0.810983 s
10/20/15 10:39:23.738 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.491 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.493 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.495 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.496 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.498 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.499 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.500 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.502 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.503 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:43.568 PM apsd[76]: Attempt to set push wake topics without dark wake enabled: ()
10/20/15 10:39:45.280 PM apsd[76]: Peer [pid=337] requested push wake but lacks APSPushWakeEntitlement
10/20/15 10:39:49.797 PM com.apple.photomoments[393]: Photomoments process awakened.



Last login: Tue Oct 20 22:39:42 on console
Argons-iMac:~ Argontantalum$ pmset -g
Active Profiles:
AC Power		-1*
Currently in use:
 hibernatemode        0
 womp                 0
 networkoversleep     0
 sleep                10
 Sleep On Power Button 1
 ttyskeepawake        1
 hibernatefile        /var/vm/sleepimage
 disksleep            10
 displaysleep         10
Argons-iMac:~ Argontantalum$ 

 With darkwake=8, there is only a small change at the end of the console messages:

10/20/15 10:48:25.151 PM apsd[76]: Peer [pid=338] requested push wake but lacks APSPushWakeEntitlement
10/20/15 10:48:25.824 PM apsd[76]: Peer [pid=338] requested push wake but lacks APSPushWakeEntitlement

Share this post


Link to post
Share on other sites

I've noted that under pmset -g, there is no "powernap" flag - so I assume that your Energy system prefs are generic.

 

I believe that this is because you haven't been using a custom SSDT.

 

I am currently testing a similar setup (and, up until your recent update), hoping it may solve the "deep sleep" memory corruption issue.

 

Just so that we all know what's going on, can you please check:

 

- is AppleIntelCPUPowerMgt loaded

- how about AppleLPC?

 

Good luck.

Share this post


Link to post
Share on other sites

I've noted that under pmset -g, there is no "powernap" flag - so I assume that your Energy system prefs are generic.

 

I believe that this is because you haven't been using a custom SSDT.

 

I am currently testing a similar setup (and, up until your recent update), hoping it may solve the "deep sleep" memory corruption issue.

 

Just so that we all know what's going on, can you please check:

 

- is AppleIntelCPUPowerMgt loaded

- how about AppleLPC?

 

Good luck.

 

 

Nope. Check out the list of loaded kexts in the text file, generated from a kextstat -l terminal command. No AppleIntelCPUPowerMgt or AppleLPC to be found.

 

Even more interesting, is that the extensions are in the S/L/E folder. Something must be preventing them from loading.

 

post-985174-0-62522500-1445746995_thumb.jpg

 

 

post-985174-0-18753300-1445746997_thumb.jpg

 

I also found this extension that may play a part, and is also not loading according to kextstat:

 

post-985174-0-81020800-1445746998_thumb.jpg

 

 

I think you are on to something here. Let me know what you find. I would love to do this without a custom DSDT or SSDT, since I don't currently have any of that (and really don't know anything about them other than the letters). Would a change in system definition get them to load. Currently, mine is a MacPro 3,1 (but the terminal insists it is an iMac – see attached text file).

extensions.txt

Share this post


Link to post
Share on other sites

Writing from the top of a mountain, so can't really provide a lot of input.

 

Just the basics:

- don't worry about terminal insisting that's an iMac

- About this Mac:System Report should state it's a MacPro (under "Hardware" I believe), as specified in your SMBIOS

- System Report: Extensions (further down) should give a kextstat list that's easier on the eyes (with a Yes/No "Loaded" indicator)

- all the Kexts mentioned above are genuine Apple; their state indicates whether you have proper (for the Mac model you've chosen) power management

- "power management" when used in this context (smbios, SSDT generation, etc) mostly refers to CPU power management, i.e. speed stepping, C7 sleeping, and all that mumbo jumbo

- without a custom SSDT (which includes "faking" the LPC device -deals with power managing your system) well, you DON'T have power management

- not having proper power management "leads to many problems, esp. relating to sleep" (I'm quoting Rehabman, a true expert on this field)

- a quick and dirty way to see CPU PM in action in to run "Intel Power Gadget"

 

Well, having said that, I should add that dealing with power management as best that I can (Pike's SSDT generation script, Clover's flags in the ACPI section) HASN'T allowed me to solve the reboot after sleep / freeze / memory corruption problem.

 

That's the reason why your travails (which had an entirely fresh approach) enthused me so much!

 

The bottom line: this problem appears to be unsolvable for some setups, and it is just impossible to figure out why, or to fix it.

 

In my case, it has been going on ever since I switched to a Z97 system a year ago - I should add that it is DRIVING ME CRAZY!

 

On a daily basis, I keep trying new approaches - currently testing MacBookPro smbioses.

 

Not happy. Thanks, though, for the glimmer of hope you provided - and the follow up information.

 

Take care.

 

Addendum:

- bdmesg (a Clover terminal command, if present) will provide a lot of cryptic information

- myterminalprompt$ ioreg -l | grep board-id

(will output the Mac model that's used by the OS to decide based on plists, e.g. the ones inside the graphics kext you mentioned

(Sorry for the typos, esp. on the terminal commands - beware)

 

Regarding whether a change in SMBIOS alone will load the appropriate Kexts:

 

- the LPC gets loaded when an appropriate LPC device is present in your ioreg (whatever that means)

- as a rule, you need to fix that: Google "toleda's 9-series LPC"

- since Clover makes a lot of nice decisions by itself, I bet that changing SMBIOS alone will affect power management favorably - who knows, probably MacPro3,1 isn't supposed to load these kexts (furthermore, with an empty config.plist, Clover will set you up as an iMac14,2)

 

If you don't mind me giving you advice, I would spend some time trying Pike's SSDT generation script on sourceforge, WITH your current MacPro3,1 SMBIOS, perhaps include toleda's LPC snippet (it's actually an extra SSDT), and take it from there.

Share this post


Link to post
Share on other sites

Writing from the top of a mountain, so can't really provide a lot of input.

 

Just the basics:

- don't worry about terminal insisting that's an iMac

- About this Mac:System Report should state it's a MacPro (under "Hardware" I believe), as specified in your SMBIOS

- System Report: Extensions (further down) should give a kextstat list that's easier on the eyes (with a Yes/No "Loaded" indicator)

- all the Kexts mentioned above are genuine Apple; their state indicates whether you have proper (for the Mac model you've chosen) power management

- "power management" when used in this context (smbios, SSDT generation, etc) mostly refers to CPU power management, i.e. speed stepping, C7 sleeping, and all that mumbo jumbo

- without a custom SSDT (which includes "faking" the LPC device -deals with power managing your system) well, you DON'T have power management

- not having proper power management "leads to many problems, esp. relating to sleep" (I'm quoting Rehabman, a true expert on this field)

- a quick and dirty way to see CPU PM in action in to run "Intel Power Gadget"

 

Well, having said that, I should add that dealing with power management as best that I can (Pike's SSDT generation script, Clover's flags in the ACPI section) HASN'T allowed me to solve the reboot after sleep / freeze / memory corruption problem.

 

That's the reason why your travails (which had an entirely fresh approach) enthused me so much!

 

The bottom line: this problem appears to be unsolvable for some setups, and it is just impossible to figure out why, or to fix it.

 

In my case, it has been going on ever since I switched to a Z97 system a year ago - I should add that it is DRIVING ME CRAZY!

 

On a daily basis, I keep trying new approaches - currently testing MacBookPro smbioses.

 

Not happy. Thanks, though, for the glimmer of hope you provided - and the follow up information.

 

Take care.

 

Addendum:

- bdmesg (a Clover terminal command, if present) will provide a lot of cryptic information

- myterminalprompt$ ioreg -l | grep board-id

(will output the Mac model that's used by the OS to decide based on plists, e.g. the ones inside the graphics kext you mentioned

(Sorry for the typos, esp. on the terminal commands - beware)

 

Regarding whether a change in SMBIOS alone will load the appropriate Kexts:

 

- the LPC gets loaded when an appropriate LPC device is present in your ioreg (whatever that means)

- as a rule, you need to fix that: Google "toleda's 9-series LPC"

- since Clover makes a lot of nice decisions by itself, I bet that changing SMBIOS alone will affect power management favorably - who knows, probably MacPro3,1 isn't supposed to load these kexts (furthermore, with an empty config.plist, Clover will set you up as an iMac14,2)

 

If you don't mind me giving you advice, I would spend some time trying Pike's SSDT generation script on sourceforge, WITH your current MacPro3,1 SMBIOS, perhaps include toleda's LPC snippet (it's actually an extra SSDT), and take it from there.

 

Changed to SMBIOS 14,2 and now sleep is working [for now only? I will continue to monitor]. Also, my system starts up much better and more consistently since the change. AppleIntelCPUPowerManagement.kext is not loading, but apparently this is not a problem (see Xnu CPU Power Management | Pike's Universum link below). AppleSMBusController.kext is loading, but AppleLPC.kext is not loading. Both of these are supposed to be necessary, so I may need an SSDT to get AppleLPC.kext to load and run properly.

 

Xnu CPU Power Management is active, as shown by the terminal:

Anachronauts-iMac:~ anachronautscomputer$ sysctl machdep.xcpm.mode
machdep.xcpm.mode: 1

Really, I don't know why sleep is working well now and was not before the change. It is true that the iMac 14,2 hardware specs are much closer to mine, so maybe something changed that I am unaware of (perhaps this Xnu CPU Power Management stuff, I didn't check before). Also, Pike R. Alpha seems to be a great source of knowledge, but he has not posted about power management in a while. For now if sleep continues to work, I may just put this issue to rest (bad joke intended) for  while until more definitive El Capitan power management posts appear, as it is an active area of current research in the Hackintosh community.

 

Reference Link (Please note that this is OLD, most of the information is written about Mavericks. While useful for some background, I think I may wait until more is available about El Capitan power management):

 

Xnu CPU Power Management | Pike's Universum

 

This may also be of some use, but I don't have the time for it right now:

 

http://www.insanelymac.com/forum/topic/304369-how-to-check-your-states-–-using-aicpminfo-msrdumper-or-appleintelinfo/

 

For what it's worth, this problem may not be limited to hacks – see this discussion:

 

https://discussions.apple.com/thread/6610693?start=75&tstart=0

Share this post


Link to post
Share on other sites

Thanks for the feedback!

 

Although I'm actually across the globe from you, I monitor your writings very closely (hope that doesn't sound creepy).

 

Question: "sleep is working" means what? How many days without reset?

Share this post


Link to post
Share on other sites

Thanks for the feedback!

 

Although I'm actually across the globe from you, I monitor your writings very closely (hope that doesn't sound creepy).

 

Question: "sleep is working" means what? How many days without reset?

 

Question: "sleep is working" means what? How many days without reset?

 

Sleep is working means that I can leave the computer and it goes into lower power mode – no fans, hard drives, screen display, and the "sleep" light on my case blinks. This always has worked this way, the change is that now it properly wakes up after sleep. Previously, the screen would stay black except for the mouse pointer which would not move after sleep (sometimes just after longer sleep periods, recently after any sleep). To get it out of the "black screen" state required a hard reset.

 

I no longer get Console messages like "Attempt to set push wake topics without dark wake enabled," so something is definitely different. I had previously set Darkwake=8 in my Clover config.plist, but it did not make any difference after having tried no darkwake flag, darkwake=0 and darkwake=1. In fact, before changing to iMac 14,2, it seemed that the darkwake boot flag was not accepted by the system at all. After the change it does seem to be working properly with the previously set darkwake=8. I don't plan to mess with it at the moment unless something changes. Here is what the terminal says:

anachronauts-iMac:~ anachronautscomputer$ sysctl -a | grep -iE "dark|wake"
kern.waketime: { sec = 1446477693, usec = 502 } Mon Nov  2 09:21:33 2015
kern.wakereason: XHC
kern.hibernatewakenotification: 0
kern.bootargs: dart=0 darkwake=8 nvda_drv=1 
net.link.generic.system.rxpoll_wakeups_lowat: 10
net.link.generic.system.rxpoll_wakeups_hiwat: 100
debug.darkwake: 8
anachronauts-iMac:~ anachronautscomputer$ 
I just changed to iMac 14,2 yesterday after finally getting my digital audio outputs to work (steep learning curve, but I managed to figure it out with Toleda's help). Honestly, from past experience, this state will work forever, for as many days as I keep the computer on. The challenge seems to be after system or program updates and/or multiple restarts. Also, I want to make sure that my DVR program records properly after a period of sleep, and that I can wake it up when needed to watch the program. Previously, the DVR program would record properly, but I would not be able to wake the computer without a hard reset. If I wanted a complete recording and happened to get back in the middle of it, I would have to wait until the recording was finished before I reset the computer to watch it. (Normally I would just restart the computer and then restart the recording, missing a few minutes of the program which was no big deal.)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×