cubswinfllclssic

Good morning! I'd like to add my two cents here, since I'm also trying to get sleep working in El Capitan 10.11.1 with Clover. I have an older LGA775 board (GA-P35-DS3L) and NVIDIA GTX 650 graphics. I'm seeing very similar behavior: I can put the machine to sleep and wake it up with my bluetooth mouse/keyboard, but the screen is completely black (no cursor or anything, though). I get the same experience with one of several DSDT.aml files, two of them built from my F9 BIOS, or even if I don't use a DSDT and rely on Clover to patch it at runtime. However, I noticed one strange thing that I'm hoping is a clue: if the machine falls asleep on its own, I am occasionally able to wake it up without issue (after a short amount of time, like 20 minutes to an hour-- waiting more than a couple hours causes the same black screen issue). If I manually sleep it (Apple menu --> Sleep), I consistently am able to wake it but to a black screen. I did some digging and tried disabling hibernate using pmset in terminal, assuming that after a couple of hours it hibernates (same when I manually sleep it), but so far no luck. I have played with many configurations in Clover and thus far am unable to get the machine to wake up. I'm hoping that the fact that I'm able to get the machine to sleep and wake up when it falls asleep on its own is a good sign. Any ideas?

Alright, I've had some straaaaaaaaange network behavior after updating to 10.7.2. I was running 10.7.1 with Chameleon r755 and updated to 10.7.2, which caused me to be unable to log into iCloud, as well as some graphics issues. As such, I made the following changes to my system: (Probably not the issue) Removed the EFI string for my graphics card and instead used NVEnabler. Updated to Chameleon r1627, and it was after this that I started noticing the network difficulties. A couple things you should know: I use 10.6.8 IONetworkingFamily.kext in /Extra/Extensions I have <EthernetBuiltIn><Yes> in org.chameleon.boot.plist The strangest thing happens if I look at Network in System Preferences-- even though I have Wifi connected and active (and working), it shows "Ethernet" as the one with the IP address and "active", and shows Wifi as "disconnected." Will post screenshot later. Any thoughts? I'll update tonight after I test some things, but I wanted to know if anyone else is experiencing something similar.

I'll re-post my reply from a similar topic: I have a GTS 250 (512MB) card and upon booting OS X following the 10.7.2 update, I was also greeted by a black screen. I had been using an EFI string in my com.apple.boot.plist to inject the graphics card, but this apparently was causing the system to fail. I tried the following: Removed my DSDT just in case it was causing problems-- I don't have graphics injection in my DSDT so this didn't make a difference. For the remaining attempts, the DSDT remained in /Extra. Removed EFI String from com.apple.boot.plist, but kept <GraphicsEnabler><No> key in com.apple.boot.plist-- this allowed OS X to boot into the GUI, but without proper resolution or accelerated graphics. Removed EFI String, changed <GraphicsEnabler> key to <Yes> -- this booted with "full" QE/CI and proper resolution, but it was extremely choppy with intermittent white flashes on the screen and buggy animations. Removed EFI string, changed <GraphicsEnabler> key to <No>, and added NVEnabler.kext (64-bit) to /Extra/Extensions-- a verbose boot indicated that the extension wasn't being loaded, so no dice. Removed EFI string, changed <GraphicsEnabler> key to <No>, and added NVEnabler.kext (64-bit) to /System/Library/Extensions and repaired with KextUtility-- VOILA! Hope that helps somebody. Check my signature for more details on the rest of my hardware. Feel free to PM me if you have a similar card and can't get it to work! Now, if we can take care of this iCloud business of my Apple ID not being recognized as an iCloud ID... grr...

I have a GTS 250 (512MB) card and upon booting OS X following the 10.7.2 update, I was also greeted by a black screen. I had been using an EFI string in my com.apple.boot.plist to inject the graphics card, but this apparently was causing the system to fail. I tried the following: Removed my DSDT just in case it was causing problems-- I don't have graphics injection in my DSDT so this didn't make a difference. For the remaining attempts, the DSDT remained in /Extra. Removed EFI String from com.apple.boot.plist, but kept <GraphicsEnabler><No> key in com.apple.boot.plist-- this allowed OS X to boot into the GUI, but without proper resolution or accelerated graphics. Removed EFI String, changed <GraphicsEnabler> key to <Yes> -- this booted with "full" QE/CI and proper resolution, but it was extremely choppy with intermittent white flashes on the screen and buggy animations. Removed EFI string, changed <GraphicsEnabler> key to <No>, and added NVEnabler.kext (64-bit) to /Extra/Extensions-- a verbose boot indicated that the extension wasn't being loaded, so no dice. Removed EFI string, changed <GraphicsEnabler> key to <No>, and added NVEnabler.kext (64-bit) to /System/Library/Extensions and repaired with KextUtility-- VOILA! Hope that helps somebody. Check my signature for more details on the rest of my hardware. Feel free to PM me if you have a similar card and can't get it to work! Now, if we can take care of this iCloud business of my Apple ID not being recognized as an iCloud ID... grr...

Slightly, I suppose-- the extensions in /Extra/Extensions are injected at boot-time, meaning that they are loaded and processed individually. Using a kextcache, the extensions in /System/Library/Extensions are cached. If you have LOTS of extensions in/Extra/Extensions, just build an Extensions.mkext in that folder as well and Lion will load it like the one in /System/Library/Extensions, rather than loading each kext individually.

Worked for me! Still loads the ones in /Extra/Extensions/ as well, which is good because I was worried that it wouldn't. Note: You DON'T need to place all your extensions in /System/Library/Extensions in order for this to work. Chameleon loads the kexts in /Extra/Extensions first, then OS X boots the kextcache.

Thanks to all who worked on this! Running the latest patch on AppleRTC fixed my sleep problem. GA-P35-DS3L Rev 2.0 with a DSDT created from DSDT Auto-Patcher. Thank you!

As aforementioned, this is a result of Lion not detecting a built-in ethernet interface on en0. I tried all of the workarounds mentioned in many posts concerning this subject, but to no avail. My DSDT was constructed to include built-in ethernet on LAN0, but Lion refused to recognize it-- even with "EthernetBuiltIn=YES" and "PCIROOT=0" in my com.apple.boot.plist. Tried removing /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist and then re-adding the network interfaces following a reboot, but that didn't work either; still no ethernet showing up. Then I tried something out of complete desperation: I placed IONetworkingFamily.kext from Snow Leopard (version 10.6.7) into /Extra/Extensions on Lion. Deleted /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist, rebooted. Opened Network Preferences and--voila!-- Ethernet detected. Added the ethernet interface first (so it was assigned "en0" in the NetworkInterfaces.plist) and then re-added my WiFi interface. Logged into App Store just fine after that. Hope this helps! TL;DR: Added 10.6.7 IONetworkingFamily.kext to /Extra/Extensions and then deleted NetworkInterfaces.plist and it did the trick. And, for those of you concerned about the App Store not recognizing the GM as a legitimate App Store purchase:

Some people that have had success with DVI to HDMI seem to have used a dongle along with an HDMI cable. I am using a single cable that has DVI on one end and HDMI on the other. Could this be my issue? Could there be a problem with the specific cable I'm using?

Good morning everyone! I'm a pretty seasoned OSx86 junkie, and after a couple of weeks digging around this forum, the forum on ProjectOSX dedicated to the NVEnabler project, and various other forums dedicated to modifying kexts with a device ID, I am still in a bit of a conundrum. I have gotten NVEnabler 64.kext to partially work; that is, it is properly identifying my NVidia GeForce 8600 GT card, injecting the ROM, and booting wonderfully. The problem is that I STILL am getting a black screen ONLY when I use a DVI-to-HDMI cable. I have taken the following steps: 1. Removed the graphics portion of my DSDT configuration-- this didn't work anyway, as I was forced to use an EFI string. 2. Removed the EFI string from my com.apple.boot.plist-- this was working with QE/CI, but would boot into a black screen when I used a DVI-to-HDMI cable. Hence my attempt at using NVEnabler. 3. Like many before me, NVEnabler 64.kext would not load at boot when placed in /Extra/Extensions, so I placed it in /System/Library/Extensions and performed the proper permissions fixes. 4. I added my device ID to NVDANV50Hal.kext and NVDAResman.kext 5. I read in the NVEnabler forum (http://www.projectosx.com/forum/index.php?showtopic=370) that I should play around with different strings in the @0,display-cfg and @1,display-cfg keys in the plist. I tried different values here to no avail (I noticed that these only exist in the NVEnabler 0.1b kext, but no the NVEnabler 64 kext-- can someone verify which is more recent? I have tried both...) NVEnabler now correctly identifies my card and injects the video ROM at boot; I have full QE/CI when I boot with a DVI-to-VGA dongle, as well as with straight up DVI. The problem: As soon as I try booting with a DVI-to-HDMI cable, BOOM, black screen at boot. Details on my rig: -Gigabyte GA-G41M board -NVidia GeForce 8600GT graphics card with two DVI and one S-Video port -Chameleon RC2 (could this be part of the problem? Kind of nervous to update Chameleon to RC4, as RC2 has served me well thus far!) -Patched DSDT w/o graphics patch -No EFI strings in com.apple.boot.plist, and <GraphicsEnabler> key set to "n" Long story short (too late), I'm building this machine to run as an HTPC to stream media from my other homebrew system. Everything works wonderfully, but I would prefer to output a purely digital signal (hence the need for DVI-to-HDMI; my TV only has a VGA input or HDMI, no DVI...). The TV is 58", which means I am seeing significant signal degradation using a digital-to-analog conversion (DVI-to-VGA). Any help will be greatly appreciated. If you know of another forum thread besides the two that I've mentioned, I would be more than willing to read through it. Thank you!

A noble post. iStat is a culprit for sure, especially if you're using a modified FakeSMC.kext that allows iStat to show temperature readings. The following have also caused my system to fail to enter automatic sleep: -Temperature Monitor -Remote Buddy (? I can't verify this...) -Mira

I agree. And in many cases, there's no point to go out and purchase the OS (especially if you're just using it in a sandbox environment and not using it as your main OS). I just wanted to get a feel for how many of us bought Snow Leopard, due mostly to the fact that it's the first release where we already had tried and tested methods in place to boot the retail DVD.

Good point. I will edit my original post.

With the rise of retail-booting methods, I'm wondering how many of us are actually buying retail DVDs. Kudos to everyone who is able to run a vanilla installation and therefore purchased their copy of Snow Leopard (EDIT: I was alerted to the fact that just because you can't run a pure vanilla system doesn't mean you didn't purchase a legal copy of Snow Leopard-- even more kudos to anyone who purchased the intellectual property anyway without being able to run a vanilla installation).

I'm a n00b with DSDTs unfortunately. But I've read that if you use a "blank" DSDT like the one that you mentioned, you can add ethernet and video via EFI strings. Have you tried that?