Hi Sniki,
Thank you for updating and simplifying the guide.
Can I ask a couple of questions?
You are welcome, hope you enjoy it.
Yes ofc you can.
About the new philosophy of installing all kexts in Clover/Kexts/Other...
1. Is it correct that the System Parameters > Injects Kexts should be set to Detect (as opposed to Inject)?
To be honest i get your idea and that's how it should be but the reason why i left it like that is because:
Im not sure if any kext is present on Library/Extensions and we set to "Inject", what will happen if system loads the same kext from installation and bootloader tries to inject it as well ? Probably unwanted things may happen, i have to read documentation of Clover to confirm you that, if im wrong i will change that in config.plist if not i will leave a not so everyone should remove kext installed into /Library/Extensions. Thank you for raising this important question.
2. Will installing the Kexts there make a difference when Apple requires all Kexts to be approved
starting in February?
Since macOS Catalina, installing kexts or other things into system partition has become much harder, you can't even mount File System as Read and Write unless you have SIP disabled as for as i know, even if you do that, it is not recommended.
On Rehabman era, Kexts were needed to be installed into /Library/Extensions but Bootloaders have advanced and so have kexts as well, so recently it's just better in every way to keep kexts into EFI partition only.
It doesn't touch system integrity and if any failure due to kext, you simply can drop it anytime.
As for kexts needed to be signed, well that may be another reason to not install them to /Library/Extensions anymore as well.
Not sure what will happen with kexts loaded from bootloader, i don't think they will get affected, even if they do, im sure kext developers will find a workaround soon after.
About power management using ssdtPRGen...
1. Do I need to drop any tables like CpuPm or Cpu0lst?
No, you don't need to drop any tables, you leave them as they do their job, SSDT.aml only inject the necessary additional stuff for Power Management to work under macOS, CpuPM and Cpu0Ist do their hardware related job.
2. How do I change the settings for ssdtPRGen when using a different SMBOIS definition like iMacPro1,1?
If you have already a SSDT.aml you simply remove it, reboot with the new SMBIOS and generate a new one from the script so it does get generated with iMacPro1,1 SMBIOS instead.
Keep in mind that you need to do the same with USBPorts.kext
(simply search in info.plist for Macmini6,1 and replaced it with iMacPro1,1 instead for USB Ports to work correctly.
Any specific reasons why you use iMacPro1,1 - Just curious nothing else
Thanks again for your help.
Lisa
You are always welcome,
It's for you people that i make this guide, to make everyones life easier with these machines.
At the same time whoever knows something that i don't seem to know, constructive suggestions are always welcome
Thanks !