bob2001 Posted August 7, 2014 Author Posted August 7, 2014 I was on r2774 so I have moved to r2795. I have added the option like this: <key>Devices</key> <dict> <key>Audio</key> <dict> <key>ResetHDA</key> <true/> <key>Inject</key> <true/> <key>Properties</key> But I am not sure if this is correct because now I get a KP on AppleIntelCPUPowerManagement!! EDIT: Ok, schoolboy error. I was missing after the now I can boot.. So now it looks like this: But still no audio.
bob2001 Posted August 7, 2014 Author Posted August 7, 2014 HOLY C**P! It's just sprung to life... I hadn't done a final repair permissions! That is with your latest Sub Woofer kexts that it is working... Haven't tested the woofer yet though. Will post back when I have checked the woofer EDIT: Well, I'm not sure if my sub is working, but I do have sound now... So I am pleased as punch Whatever you changed in your recent attachment did the trick.
oldnapalm Posted August 7, 2014 Posted August 7, 2014 I'm not sure about the woofer too. I can hear the bass in those youtube woofer tests, I think I couldn't with the previous kext. Have to test again. Can you identify if it works now because of ResetHDA or the new kext? -Guides and Tutorials HERE -Hackintosh Tutorial Database - HERE -The largest EFI folder collection for Hackintosh HERE -Support Olarila Vanilla Hackintosh by making a donation HERE -Professional Consulting for macOS Hackintosh since 2006 HERE
bob2001 Posted August 7, 2014 Author Posted August 7, 2014 I'm not sure about the woofer too. I can hear the bass in those youtube woofer tests, I think I couldn't with the previous kext. Have to test again. I have found that it's quite a naff subwoofer at best, so you may need to test several times to be sure. If you compare the subwooder in this model with, for example, the Dell L702X which has a JBL subwoofer.. it's bad. The Dell L702X is simply mind blowing! Can you identify if it works now because of ResetHDA or the new kext? I believe it is the AppleHDA.kext (and any associated DSDT edits etc) because when I first added ResetHDA to the config.plist it didn't work immediately. It was only once I did a permission repair that it kicked in and it was specifically the AppleHDA.kext that had permission errors. Now I have set ResetHDA to No, the sound is still working. I nearly always remember to do a complete permission repair when I change kexts, so I don't think it was an error on my part with previous attempts. But... could be both.. I swear I have some kind of bizarre model revision with a phantom in it.
Mirone Posted August 8, 2014 Posted August 8, 2014 Wow, good news. Could test with the kexts I sent you? for most people it works perfectly, Oldnapalm is one of those people, I think you are a case apart.
bob2001 Posted August 8, 2014 Author Posted August 8, 2014 Wow, good news. Could test with the kexts I sent you? for most people it works perfectly, Oldnapalm is one of those people, I think you are a case apart. Well this is weird.... If I test your AppleHDA and DSDT, I now get Audio! With and without ResetHDA! But I have switched back to the DSDT in the original package posted by old napalm with just the AppleHDAALC269.kext, without ResetHDA (and stock AppleHDA) and I lose audio... just rebooting with it back on.. will post back in a sec. EDIT: No audio with original kexts at all, with or without ResetHDA. So it must be kext related. But I find it hard to believe I forgot to repair permissions completely on both occasions.. even with the recent ones old napalm posted, I remembered like 3 mins later. I can only think that as well as being Kext related, I have some freak NVRAM values and ResetHDA helped. I think I will leave that on for now. Reminds me of using a Linux live CD to get backlit keys working with Chameleon... I could never get them working after sleep like everyone else on the insanely thread (I think maybe one other guy had the same issue), then I booted from a Linux live CD and they started working... definitely ghosts in the machine
bob2001 Posted August 11, 2014 Author Posted August 11, 2014 Just a quick post to say it's still going strong. I've had an uber busy weekend from hell, and have a ton on for the next few days so it's unlikely that I will get the time to try Yosemite until the back end of the week, but I will post as soon as I have.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now