- Joined
- May 27, 2010
- Messages
- 2,364
- Motherboard
- Dell Optiplex 9030 All in One
- CPU
- i5-4690K
- Graphics
- HD 4600
- Mac
- Classic Mac
- Mobile Phone
I'm more confident about Rehabmans' injector than for (toleda) standard injector : it's not just a .plist embedded in a .kext you have a alias for every component of AppleHDA.kext inside the injector so your don't need to put it in S/L/E (I guess ...).
That a pretty good news if your modifications are the same in config.plist !
I've been digging in the xml to spot obvious differences, but I don't know what I'm looking for ... so I'm stuck here
(Comparaison of your xml files and rehabmans' in the archive.zip file)
Do you have codec dump from linux so I can give a closer look ?
If you read the post from Rehabman you will see that you still need to put the injector into S/L/E - it does not work from the Clover/Kexts folder.
And all contributions welcome as far as digging around are concerned! I wasted way too much time on that element of this build trying so many different variations in patching configdata, different layouts etc.
Unless you actually have a working build in an NUC to test things on though you are pretty much stuck (in my view) as there is so much experimenting without you being able to completely define the working configuration by logic alone.
If you have read any of the patching guides you will notice that they all read logically enough, BUT there is no substitute for tedious experimentation unless you have a comprehensive knowledge of the subject to start with.
Things to note to get you started:
Be consistent with "layouts" "platforms" "codecIDs". The layout we patch - is layout 1 for simplicity and consistency with SSDT/DSDT we work with - Rehabman used 86 in his kext. You can change this of course, in your SSDT/DSDT to migrate to layout 86 or you can use revogirls script to decompress the zlib files,change layouts to 1 and recompress if you want to experiment more with his injector.
Sources of help and advice: Toleda and RehabMan will help (but you will have to meet them more than half way as this is a self help forum and they are extremely busy) and also Mirone who is very helpful but lives on another forum which we are not allowed to link to….
In my own opinion AppleHDA.kext is not a huge concern because (a) the boot loader automatically takes care anyway of HDMI and DP patching of the vanilla AppleHDA.kext (so if you use HDMI or DP there is already nothing to do!); (b) While AppleHDA.kext changes on most updates it is in the vast majority of cases okay to use a previously patched version without any perceivable downside and (c ) Once you are into the groove of patching - and if you REALLY need to work with the latest versions - it is a relatively simple matter to transfer your configdata, layouts and platforms from one kext to the next.
Edit: Please note first post updated with a patched AppleHDA.kext for 10.9.4 - this kext does not include the binary patches as they are done on the fly by Clover.
[If anyone wants to try turning the patched kext into an "injector" please note the three relevant kext specific information parts to include in an injector kext may be found in AppleHDA.kext/Contents/Resources/Layout1.xml.zlib; AppleHDA.kext/Contents/Resources/Platforms.xml.zlib and in AppleHDA.kext/Contents/Plugins/AppleHDAHardwareConfigDriver.kext/Info.plist "Codec ID 283902595"]