OK, there are a few issues with your CLOVER folder that can be sorted relatively easily.
Clover Version:
You are using an old version of Clover, pre - Clover_r4986. I would recommend you update the version of Clover you are using to Clover_r5119 or r5120, as these were the last two releases before the developers tried to incorporate some fo the OpenCore entries. Copy of Clover_r5119 attached below.
SSDT's:
You should in my opinion be using the following SSDT's:
- SSDT-XOSI.aml, with corresponding Clover config.plist rename patch.
- SSDT-IMEI.aml - Needed to add a missing IMEI device on Ivy Bridge CPU with 6 series motherboards
- SSDT-EC.aml
- SSDT-HPET.aml
The last two should be generated from your DSDT.aml with Corpnewt's SSDTTime script.
These should be placed in the /CLOVER/ACPI/patched folder alongside your SSDT.aml (CPU power management SSDT).
Kexts:
You are using a number of unnecessary/obsolete and problematic kexts:
- AppleIntelE1000e.kext - Other Intel Ethernet kext should be used, as mentioned below.
- AtherosE2200Ethernet.kext - I doubt very much if you have an Atheros Ethernet port on your Intel motherboard
- CodecCommander.kext - Not sure this is required
- GenericUSBXHCI.kext - Obsolete since El Capitan was released, causes more problems than it solves
- NullCPUPowerManagement.kext - not required as you have an SSDT.aml for CPU PM
The kexts listed above can be removed from the /CLOVER/kexts/Other folder.
IntelMausiEthernet.kext should work with your Intel Ethernet port. But check which of the two Intel kexts is working in your system, before you delete AppleIntelE1000e.kext.
You have AirPortAtheros40.kext and IO80211Family.kext in the /CLOVER/kexts/Other folder. Can you confirm which WiFi card you are using. As you may not need both of these kexts, especially as the rolled back IO80211Family.kext, (assumed from High Sierra or Mojave) contains a number of plugins that may work with your WiFi card.
Kext & driver update:
Personally I would recommend replacing FakeSMC.kext and SMCHelper.efi with VirtualSMC.kext and VirtualSMC.efi. FakeSMC.kext is no longer being developed, whereas VirtualSMC.kext is still in the reasonably early stages of development, compared to FakeSMC.kext.
Config.plist:
This required quite a few changes, additions and omissions. Sorry but I am not in the mood to detail all the changes I made to your config.plist.
The changes include additional rename patches, boot arguments, IGPU settings, IMEI, HPET, RTC fixes. changing the SMBIOS to a better match with your Ivy Bridge system, checking new Serial Number, populating MLB and ROM fields so iMessage should work, plus other items.
I have changed the SMBIOs to iMac 13.2 as that is the SMBIOS recommended for an Ivy Bridge system like yours. It will run Catalina with no issues. I have checked the new serial with Apple Support, it is not being used by a real Mac, so shouldn't cause any issues with iMessage, iCloud etc.
The IGPU (HD4000) is supported in Catalina, but not beyond this OS. I have removed the 'Inject Intel=true' option from the config.plist as it is not required when using WhateverGreen.kext. I have added the IGPU Device Properties to the config.plist, so the IGPU runs headless to match the setup on a real Mac, with the RX480 running/powering the display(s).
To Do:
iMessage - Messages
Before you try using Messages, iCloud etc. again, I would recommend you have a read of this guide by P1LGRIM -
https://www.tonymacx86.com/threads/an-idiots-guide-to-imessage.196827/, especially the part where he goes through the removing old plists etc., as your previous failures may hinder any future chance of these services working with the new config.plist/setup.
I would confirm the new config.plist contains all the necessary Serial, MLB, ROM etc for Messages to work. So do not change or mess them up.
USB config
You need to create a USB config kext or SSDT for your system, as your motherboard contains more than the 15 ports allowed by Apple. Read and follow UtterDisbelief's USB configuration guide -
https://www.tonymacx86.com/threads/the-new-beginners-guide-to-usb-port-configuration.286553/.
Ask for help if you get stuck or don't understand what is being asked when following the USB configuration guide.
CLOVER folder
If/when you upgrade your Clover installation, you can then try the attached CLOVER folder in place of your current one. I do not think this Clover folder will work with the current version of Clover you are using, as the new version will look for the /CLOVER/drivers/UEFI folder for the drivers. This new CLOVER folder doesn't contain the old/obsolete drivers64 and drivers64UEFI folders, which your current CLOVER folder uses.
When you do try to use this CLOVER folder you should not simply replace your current CLOVER folder. But rather use a spare USB pen drive to test the folder first.
Follow these steps:
- Format the spare USB as HFS+ with a single partition, doesn't matter size of USB, 1GB drive will do.
- Install Clover_r5119 in UEFI mode to the USB.
- Replace the CLOVER folder on the USB with the one attached below.
- Boot your system with the USB,
- Press F10 key (repeatedly) when your system starts, to bring up the Boot Menu.
- Select the UEFI partition on the USB pen drive as the boot drive.
- System should boot in to Clover, where you can select your macOS Catalina drive.
- You will be able to tell you have booted in to the USB as the Clover boot screen will be different, the attached CLOVER folder and config.plist call the 'Catalina' boot theme not the 'Embedded' theme your config calls.
Hope this helps.
