Leaderboard

It's entirely up to you. There's a chance you won't see much difference in terms of CPU power management and performance between patched kernel and unlocked CFG register/variable. But I guess, only experimentation can tell...

Built an Hackintosh Recently with the following Specs: Atermiter X79G motherboard 45$ Xeon E5-2650V2 ~50$ 64GB DDR3 ECC RAM Nvidia GT 710 graphic card: sanddisk 500GB SSD You can directly install Mojave without modifying anything in the bios... using this EFI.. But if you have to install/upgrade to Catalina 10.15.2, before installing or upgrading Disable Virtualization support - CPU configuration disable VTX-D - North bridge. Disable USB ECHI support Post installation you can enable them again. Had no issues with virtualization performance etc... Boots in less than 10 seconds. All working - except small static in AUDIO... (hardly noticeable, but goes away once you play something)... EFI_desktop.zip

You're extracting those raw vfiles out of a complete dev package. Download the complete package from parent level and you may compile the .asl files with the provided makefile. These .asl files are plain source code. You may rename the extension to .dsl to open them in MaciASL app. MaciASL uses .dsl extension for source code and .aml extension for compiled code. Here, the .asl files are meant to be compiled with the command line (Intel) iasl tool through the makefile. If you open up the makefile with a text editor, you'll see how it operates. As for errors, well they can depend on the ACPI version the code is based on and the ACPI version the compiler will be using. Check your MaciASL settings here. After a few years with good old DSDTEditor, I switched to rehabman's version of MaciASL several years ago and have been using that same version without problems ever since. Of course, I had to get into ACPI coding to be able to fix DSDT/SSDT when compiler returns errors... https://github.com/RehabMan/Intel-iasl https://github.com/RehabMan/OS-X-MaciASL-patchmatic

Yes, this may happen from time to time. Could be a bug in AppleALC, I'm not too sure. Solution is to put the laptop to sleep and wake it after a couple of seconds or reboot. Check that you use latest versions of Lilu, AppleALC and CodecCommander and update if required. You may use Clover Configurator app to that effect.