Kasakka Posted July 2, 2011 Share Posted July 2, 2011 The one and *only* think that sleep enabler does is tell XNU that it can *try* to sleep. *snip* In other words. SleepEnabler tells XNU that it can go to sleep. It doesn't tell it how to sleep. It doesn't tell it how to wake. In other words, it won't hep you out. You have a different issue (which can probably be fixed with some dsdt tweeks). That's pretty much it. Thanks for the informative post. Been trying to figure out the sleep thing without much luck. Link to comment Share on other sites More sharing options...
BuXb Posted July 2, 2011 Share Posted July 2, 2011 Thanks for the informative post. Been trying to figure out the sleep thing without much luck.Disable in the DSDT what you can until you find the culprit. Look here. Please don't continue this discussion here in this thread because from now on it would be OT. Instead you can post to the thread I linked to, after fiddling with your DSDT. Good luck, fingers crossed. This is the last release for the day, honest. .. but 3 - is the magic number .. Link to comment Share on other sites More sharing options...
fumoboy007 Posted July 2, 2011 Share Posted July 2, 2011 Sleep still does not work with my Asus M2N68-LA (NARRA2) motherboard even with SleepEnablerNG 1.0.2. My DSDT is attached if somebody wants to help me. HP_Pavilion_a6110n.dsl.zip Link to comment Share on other sites More sharing options...
TIMMAYOSX Posted July 2, 2011 Author Share Posted July 2, 2011 To use SleepEnablerNG, you must first disable anything that is already handling PM (not needed if it does not work anyhow). What you need to do is simply put NullCPUPowerManagement.kext in /Extra/Extensions along with SleepEnablerNG.kext, and you should be sleep-able. Also look at pmset (terminal app) which lets you tune your PM settings, but this should not be nessesary. Link to comment Share on other sites More sharing options...
fumoboy007 Posted July 3, 2011 Share Posted July 3, 2011 To use SleepEnablerNG, you must first disable anything that is already handling PM (not needed if it does not work anyhow). What you need to do is simply put NullCPUPowerManagement.kext in /Extra/Extensions along with SleepEnablerNG.kext, and you should be sleep-able. Also look at pmset (terminal app) which lets you tune your PM settings, but this should not be nessesary. Not for me. The kernel I am using already has built-in power management disabling, and I even used NullCPUPowerManagement.kext to be sure. My computer seems to go into an S1 sleeping state because the power button light turns yellow, the hard drive spins down, and the video feed turns off, but the fan is still running, which means something is still powered (the only thing left is the CPU and the RAM). I need it to go into S3. In addition, I am unable to power back up; I have to do a hard reboot. Link to comment Share on other sites More sharing options...
TIMMAYOSX Posted July 3, 2011 Author Share Posted July 3, 2011 The PM resides in external kexts, and not internal to the kernel unless your custom kernel offers more functionality than the vanilla varients. One thing you can do is look at the boot up log, and ensure SleepEnabler is loaded (will be near the top). You may also try a vanilla kernel, which may prove to work better in this case (unless you are an AMD user of course). When you put your system to sleep, does it show anything in the kernel log (dmesg under the Terminal)? Link to comment Share on other sites More sharing options...
fumoboy007 Posted July 3, 2011 Share Posted July 3, 2011 custom kernel offers more functionality than the vanilla varients. Yep. One thing you can do is look at the boot up log, and ensure SleepEnabler is loaded (will be near the top). Yep, it's loaded. (unless you are an AMD user of course). Yep. When you put your system to sleep, does it show anything in the kernel log (dmesg under the Terminal)? Nope. Link to comment Share on other sites More sharing options...
unimatrix725 Posted July 31, 2011 Share Posted July 31, 2011 SleepEnablerNG 1.0.2 (i386 & x64) - July 2, 2011 v1.0.1+ has full Lion GM support. SleepEnablerNG is based on SleepEnabler by Meklort, but updated for full Snow Leopard (10.6.0 - 10.6.8), and Lion. This version differs in that it takes care of buffer overflow issues present in the existing SleepEnabler that can, for some users present issues such as random KPs, specifically in Lion and newer, untested kernels. I am now part of the SleepEnabler project, and as such this will be one of my last release of SleepEnablerNG. Future updates will be on the official SleepEnabler project. (makes things much easier for users) This version will auto detect the pmVersion on Snow Leopard (up to 10.6.8), and Lion (10.7.0). If you are using a release outside of this, you will need to specify a pmVersion parameter. Version 1.0.2 (did a much needed rewrite, but otherwise functionally identical to 1.0.1) kext SleepEnablerNG1.0.2.zipsource SleepEnablerNG1.0.2_src.zip Version 1.0.1 kext SleepEnablerNG1.0.1.zipsource SleepEnablerNG1.0.1_src.zip I appreciate your work, but there are allot of Kernel Dev's working to put the "PMVersion" detect/override into the newer kernels. There are 2 major SleepEnabler.kexts out there all ready. One for 10.6.8 and Lower ( http://blog.nawcom.com/SleepEnabler.kext.10.6.8.zip ) and then there is one that is 10.7 and above, which by the way works on all snow editions.( http://blog.nawcom.com/SleepEnabler.kext.10.7.x.zip ). I kinda agree with NawCom in the fact that you are just wanting to make a contribution using others work (Meklort?) just to get your name "Out There" on the scene. I know allot of others that have done similar, like PyStar and GeoHot (aka Geo Douche the oh so infamous PS3/iPhone Hacker... please). This is NOT A Flame, but an observation. I MAY MISUNDERSTAND and if so PLEASE CLEARLY STATE WHAT YOU ARE DOING IN DETAIL. The only detail is "This version will auto detect the pmVersion on Snow Leopard (up to 10.6.8), and Lion (10.7.0). If you are using a release outside of this, you will need to specify a pmVersion parameter." I am believe if someone is going to install a new OS version, that they will at least Google what version powermanagement is needed/used and most use Chameleon, some Chimera and it is all to easy to pass the pm=# in the boot. When one has the right # in there just add it to the com.apple.Boot.plist . I really don't get it, I have enough KEXTs to last till im reincarnated. Link to comment Share on other sites More sharing options...
buoo Posted July 31, 2011 Share Posted July 31, 2011 I say excuse to the users for the unpleasant situation that was been created. I'm sorry. Link to comment Share on other sites More sharing options...
radishs Posted August 18, 2011 Share Posted August 18, 2011 Any idea for 10.7.1? In 1.0.2 can't fully sleep and wake for sleep. Link to comment Share on other sites More sharing options...
karloz61 Posted March 18, 2013 Share Posted March 18, 2013 this work very well on GA-z77-d3h and snow 10.6.8 ivy bridge i7 3770k (whit pmversion=23) very very thanks the next question is... work on same mother and mountain lion? whats pmversion we need to put ? Link to comment Share on other sites More sharing options...
Slice Posted March 18, 2013 Share Posted March 18, 2013 this work very well on GA-z77-d3h and snow 10.6.8 ivy bridge i7 3770k (whit pmversion=23) very very thanks the next question is... work on same mother and mountain lion? whats pmversion we need to put ? For 10.8.2 pmversion=102 if it helps. Have no sources 10.8.3 yet to check new version. Link to comment Share on other sites More sharing options...
nawcom Posted March 19, 2013 Share Posted March 19, 2013 Latest from the google code page should work just fine. https://code.google....-sleep-enabler/ It's been 102 since 10.7. There's no need to manually enter it in as it defaults to it if the version is 10.7+ and not coded in as being changed. If anything the kext may need to be updated with new headers in 10.8.3 but probably not. EDIT The version on googlecode that I last updated in July 2012 still works perfectly in 10.8.3. Just did a test run on my laptop, and it slept and woke without issues. nawcom$ kextstat|grep [sN][lu][el] 12 0 0xffffff7f807f9000 0x2000 0x2000 org.tgwbd.driver.NullCPUPowerManagement (1.0.0d2) <7 4 3> 17 0 0xffffff7f80870000 0x2000 0x2000 sk.triaxis.kext.SleepEnabler (1.0.0) <7 4 3> You also do not need to enter in pmVersion=102 as like i said, it assumes that's the default version for any Darwin version equal or newer than 11 (OS 10.7). I don't know what this whole SleepEnablerNG thing was about but whatever. The vanilla kext works fine with 10.7/10.8. Grab it from the googlecode link above. Also it's important to understand that if your system isn't sleeping, it's not the fault of the SleepEnabler kext. It's ACPI related in your firmware, which you can fix up via modding your DSDT. Link to comment Share on other sites More sharing options...
Recommended Posts