I've mentioned that DSDT patching is only a part of what we are going to do to achieve as vanilla OSX as possible. But vanilla /S/L/E and minimal amount of custom kexts in /E/E significantly raise your chances of successful update.
IS KEXT UTILITY SAFE UPDATE
With hackintoshes one always has to read what other people saying about a fresh system update before proceeding. Of course, since you are not using original Mac, there's no 100% guarantee that any future system updates won't break your setup. And if you put a custom kext to /S/L/E it's hard to find it later if you suddenly need to remove it or change (our memory is a tricky thing).Īs an example, current patched version of IOATAFamily.kext that works well with 10.6.2 is reported to raise kernel panic in 10.6.3 beta, so there you go, already a problem.ĭSDT patching makes your system look to OSX more Mac-like. And you will then need to look for newer versions of those kexts, and also need to remember what you have to patch in /S/L/E. Yes, they work in a given OSX version, but when Apple releases an upgrade, all patched kexts in /S/L/E are overwritten and some kexts in /E/E might stop working or even raise kernel panics. The problem with patched kexts is that they are not upgrade-proof. So, let me start with a brief explanation why should you bother with that DSDT patching and entirely 100% vanilla /S/L/E folder when there's a bunch of guides with patched kexts available, which work without too much hassle. It can be stored in both /E/E and /S/L/E, but in the latter case it doesn't replace anything.