- Joined
- Jan 13, 2010
- Messages
- 370
- Motherboard
- Gigabyte Aorus X570 Elite
- CPU
- Ryzen 7 5800X3DX
- Graphics
- RX 6800XT
- Mac
- Classic Mac
- Mobile Phone
Re: New ALC888 32/64-bit AppleHDA.kext!
Ok, I will try and clarify some issues.
- This kext is tested for ALC888, not ALC888b. Not saying it won't work with others, just that I have no access to the other variants.
- HDAenabler.kext is actually bundled into the AppleHDA.kext. To remove it simply show package contents Contents/PlugIns. I labelled it red for easy recognition. I also labelled the AppleHDA.kext red as well for the same reason.
- The reason I recommend manually removing AppleHDA and HDAenabler kexts is that often Kext Utility will only overwrite the files that need to change to reflect the Kext that it's changing to. (ie if HDAenebler is bundled into my AppleHDA.kext it will remain in plugins, even if you use Tony's 10.6.2 AppleHDA easy installer). Removing these Kexts manually then dragging the new Kext onto Kext Utility to install, is just a little safer. And yes, set and repair permissions after any Kext install. Again this is just playing it safe. Booting -v -f -r also sometimes resolves issues.
- The version of your BIOS may prevent things from working correctly as well.
Ok, I will try and clarify some issues.
- This kext is tested for ALC888, not ALC888b. Not saying it won't work with others, just that I have no access to the other variants.
- HDAenabler.kext is actually bundled into the AppleHDA.kext. To remove it simply show package contents Contents/PlugIns. I labelled it red for easy recognition. I also labelled the AppleHDA.kext red as well for the same reason.
- The reason I recommend manually removing AppleHDA and HDAenabler kexts is that often Kext Utility will only overwrite the files that need to change to reflect the Kext that it's changing to. (ie if HDAenebler is bundled into my AppleHDA.kext it will remain in plugins, even if you use Tony's 10.6.2 AppleHDA easy installer). Removing these Kexts manually then dragging the new Kext onto Kext Utility to install, is just a little safer. And yes, set and repair permissions after any Kext install. Again this is just playing it safe. Booting -v -f -r also sometimes resolves issues.
- The version of your BIOS may prevent things from working correctly as well.