Recent content by bman4789

Thanks @ukulele01, this worked perfectly for me too! I haven't had Clover issues in so long that I forgot there was a backups folder made on every install :):thumbup:

My AppleHDA.kext Info.plist does contain <key>com.apple.iokit.IOACPIFamily</key> <string>1.2.0a1</string> <key>com.apple.iokit.IOPCIFamily</key> <string>1.1</string> in the OSBundledLibraries dictionary. Output from kextcahe: [brianmitchell@terra ~]$ kextcache...

I replaced the vanilla AppleHDA.kext from the 10.11.4 installer using Kext Wizard and then tried the audio_cloverALC-110 command again, it returns the same thing as before.

This is using a vanilla AppleHDA.kext Info.plist My original comment is the output of running audio_cloverALC-110_v1.0q10.command with a vanilla AppleHDA.kext

I added the following to /EFI/CLOVER/kexts/10.11/realtekHDA.kext/Contents/Info.plist but it didn't seem to work. <key>OSBundleLibraries</key> <dict> <key>com.apple.iokit.IOPCIFamily</key> <string>1.1</string> <key>com.apple.iokit.IOACPIFamily</key>...

Audio stopped working for me after this update. Usually run audio_cloverALC-110, however it didn't work on OS X 10.11.4. I've tried reading http://www.tonymacx86.com/el-capitan-laptop-support/188853-fix-10-11-4-broken-audio-applehda-injector-dummyhda.html, but I don't know how to adapt it for...

I was able to get audio back after sleeping by dragging in the unmodified CodecCommander.kext into S/L/E on OS X 10.11.2. This is in combination of using cloverALC. The speakers came back to life immediately after dropping in the kext and authenticating it. I use Clover, and ALC892 EDIT...

I use the Logitech Z623. They're fairly inexpensive and have a really powerful sub for all the bass. :D

I am also having this issue. I read somewhere that NVRAM is broken in Yosemite, so we will see what happens.

I have the problem too. I'm going to try reinstalling over my current setup (on USB 2 instead of 3), and then also try not installing boot options in MultiBeast. My build is listed in my builds. EDIT: I reinstalled via USB 2, but I realized that I set it to EasyBeast, instead of DSDT Free the...

This started happening with me as well. I unplugged the SATA power cable from my internal 1 TB HDD used only for Time Machine, and then Chimera loaded instead of being stuck on "-" or "\".

I don't know if it'll really help, but try setting GUI to No. That may give you a little more info as to what's going on.

I figured out what was breaking it. I was hiding and renaming partitions from org.chameleon.Boot.plist, and apparently one or both of these features doesn't work. This is what I had in my plist (worked through Chimera 2.2.1): <key>Hide Partition</key> <string>hd(1,2) hd(1,6)</string>...

Deleting the /Extra folder, and doing a clean install with Chimera 3.0.1 works, however there is no GUI and no org.chameleon.Boot.plist. Copying back the Themes folder and the plist that I had from Chimera 2.2.1 resulted in the same issue as before. I am currently slowly adding things back in...

I was able to downgrade to Chimera 2.2.1, however I'd like to figure out what the problem was, and how to fix it.