RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,058
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Hmm, I'm using Toledo's HDA Clover patch which runs out of terminal. I think you're right in the way mine does it, but to Rehabman's point, "my way" uses the native AppleHDA kext with no dummy kexts/non native kexts in /S/L/E which gives it a much better chance of surviving updates.
Maybe something to consider in the new version. You're right in that it is "more compact" putting a dummy HDA kext in /S/L/E, but it is less "native".
The PBI-CE uses the native AppleHDA.kext. After you install, you should examine the files to have a better understanding. I think you're confused.
It is pure myth that adding kexts to /S/L/E somehow makes the system "less native". For example, my real Apple MacBookAir6,2 has kexts from 3rd parties in /S/L/E... for example, HP printer drivers. Should I instead use Clover to boot my Mac just so I can place the HP printer drivers in Clover/kexts and keep /S/L/E "more native"?
In fact, the runtime environment is "more native" with everything installed to /S/L/E. This way it can be included in cache, and placed in memory where OS X will naturally place them (as opposed to the tricks going on inside OsxAptioFix*.efi). This is proven by the fact that some kexts simply don't work when injected.