Fix no sound after sleep on 1150 - other method (may work for other realtek's aswell)
Preface:
No sound after sleep is a common issue for afaik all realteks. Some people reload the kext using audio reset apps but others feel this is dangerous or a bad solution. A better solution is using codec-commander but it's harder to wrap your head around and some motherboards are even worse to get working. I had one of those and this is a guide to how I solved it.
So how the hell do I fix this?
There are a few threads on this topic but I spent days with them and still didn't get codec-commander to work on my 1150-enabled motherboard (Gigabyte GA-Z79MX-gaming 5). At last I was pointed to a few closed issues where I puzzled out the answer. I've uploaded the pre-compiled kext here for others to find with the same issue. It seems the 1150 on this and similar motherboards is a particularly tough one to fix.
This kext should work on motherboards with a similar setup to the Z79mx-gaming 5. If that seems like what you have, go ahead and just try the kext attached first. Install it using kextbeast or similar to S/L/E and set darkwake to 8. (See bottom of post for links)
If my kext doesn't work, or you have another realtek, I'll also provide the updated instruction on how to (probably/possibly) get it working. These instructions assume some general previous knowledge, let me know if you need more details about any particular step in the process. Most guides are not correct, telling you to find device id's in a plist that doesn't exist. Codec-commander was updated but the guides were not. What you do is download codec-commander and compile it with xcode (yes you need to download and install xcode). On some motherboards, as I understand it, this is all you need to do. Just install the kext in S/L/E and set darkwake to 8 and bam, sound after sleep.
Some aren't as lucky due to some amplifier chip as I understand it. If that's your case, after compile go into the build-folder and find the release-version of the kext. Open the container and find the .plist inside. Open this file with an editor or plist editor for convenience. Look up the section for your realtek and find the value for update nodes. Edit this to true and possibly increase the delay to the same as in the default section (I think it was 300). Save and install the kext into S/L/E, set darkwake=8 and reboot. Sleep and wake the computer, holding your thumb as we do in Sweden. Hopefully you now have working audio after sleep.
If you still do not, there's probably some other mysterious setting inside the .plist that you need to edit for your realtek and I cannot help you on that. Look through the conversations at git (link below). Wish I had the answer for everybody but at least I have it for those on 1150 and maybe a few others.
ready-made kext for 1150 on Gigabyte GA-Z79MX-gaming 5 and similar motherboards.
View attachment 146742
Link to download codec-commander:
https://github.com/Dolnor/EAPD-Codec-Commander (click download zip)
Other tools needed/useful in the process:
Xcode: app store, search for xcode, free, takes a lot of space.
Plist editor pro (easier way of editing that .plist):
http://www.fatcatsoftware.com/plisteditpro/
kextbeast: easy way of installing kext's:
http://www.tonymacx86.com/downloads.php?do=file&id=32
Issues-conversation at codec-commander page:
https://github.com/Dolnor/EAPD-Codec-Commander/issues?q=is:issue+is:closed
(last resort if nothing above help you)
Maybe this should be pinned if it's considered worthwhile. Cheers!
EDIT 1:
Oh and if you get any kp's try installing the audio driver as a patched kext = use multibeast. Injected stuff here is apparently a bad idea. Don't ask me why, it's above my pay-grade!
EDIT 2:
Setting darkwake=8 is apparently not required but recommended by some user somewhere sometime in combination with this. I tried going back to what I had before (default setting). You do as you see fit!
EDIT 3:
There's another guide with a downloadable codec-commander but this will not work for the 1150.
EDIT 4:
This was tested on 10.10.4 and 10.10.5. Have not tried on anything pre-yosemite but it may work. Remember before 10.9.2 (I think, somewhere there) you no longer need this fix as it's needed due to a change made by apple at the builds after that.