[GUIDE] Catalina on HP EliteDesk 800 G4/G5 Mini - The Perfect MacMini8,1 Hackintosh - CLOVER & OC

[deeveedee]

Looks like my recent changes have fixed my OC performance. My OC Geekbench 5 benchmarks match my CLOVER benchmarks. I have attached my latest OC EFI and GB5 screenshot here. I can only speculate that incorrect use of RtcMemoryFixup was adversely impacting my rig's performance. With OC, my EliteDesk 800 G4 Mini seems to be running perfectly (CPU power management, Geekbench5 benchmarks, sleep, wake, shutdown... everything) with no need for CPUFriend.

 

[rafale77]

The rpcsvchost problem only occurs if you used RtcMemoryFixup.kext with the wrong rtc-exclude range. I am currently running without RtcMemoryFixup (see here and here).

If you want help with USBPorts.kext, please post your EFI (with USBPort.kext).

Here you go

 

[deeveedee]

Here you go

Your config.plist is still looking for USBInjectAll.

 

[rafale77]

Indeed... Been tinkering and came out with a new hybrid version which gets rid of the USBInjectAll and the CPUFriend kexts.
I kept my previous ACPI section. Not expert enough to understand the difference between the two versions.
I have not observed any changes in performance. If anything it seems to have degraded a little.
This version has HDMI audio and BT/Wifi enabled.

The geekbench scores seem to be inline or better than what I am seeing for others for single thread i9 9900 (~1300) but the multithread ones are rather disappointing at ~6900. I tested also with an iMac19,1 ID and it made no difference.

Edit: Ok I read more about the ACPI patches being handled by SSDT so the version attached is actually the more "by the book one". I also enabled the graphical OS picker.

 

[deeveedee]

HP has released BIOS update 02.14.01 Rev.A that addresses security vulnerabilities for our HP EliteDesk 800 G4 Minis. I have not yet tested with this firmware update. I'd welcome test results from anyone who wants to be adventurous and try the update.

 

[rafale77]

HP has released BIOS update 02.14.01 Rev.A that addresses security vulnerabilities for our HP EliteDesk 800 G4 Minis. I have not yet tested with this firmware update. I'd welcome test results from anyone who wants to be adventurous and try the update.

I think this is what I installed on the G5 corresponding to 02.07.01... It worked just fine. There is also an ME update as part of it.

 

[rafale77]

Yeah I am working on the OC bootup chime and got it working from the onboard speakers.

And attached my current EFI with a couple of more fixes as my config.plist was a bit dated. Added sound support for OC. Can even enable audio assist if interested for visual impaired, I've tested it but disabled it. Warning: the EFI is more than 100MB due to all the sound files.

 

[deeveedee]

Yeah I am working on the OC bootup chime and got it working from the onboard speakers.

And attached my current EFI with a couple of more fixes as my config.plist was a bit dated. Added sound support for OC. Can even enable audio assist if interested for visual impaired, I've tested it but disabled it. Warning: the EFI is more than 100MB due to all the sound files.

Great stuff. To the extent possible, I'd like to standardize on one EFI, so whatever you can do to adopt my ACPI and config.plist would be great. Also, when you post your EFI, sanitize the config.plist so it doesn't include your MLB, Serial Number and UID.

 

[rafale77]

Great stuff. To the extent possible, I'd like to standardize on one EFI, so whatever you can do to adopt my ACPI and config.plist would be great. Also, when you post your EFI, sanitize the config.plist so it doesn't include your MLB, Serial Number and UID.

Sorry for this newb question: What are the pros and cons of the two ACPI approaches? SSDT Vs. Patching in the config?
It seems like the OC preferred approach is to use the SSDT but I don't know what benefits they bring.

On Big Sur... I am trying to download it but boy... the apple server seems to be hammered... Seems like it will take me another day.

 

[deeveedee]

Sorry for this newb question: What are the pros and cons of the two ACPI approaches? SSDT Vs. Patching in the config?
It seems like the OC preferred approach is to use the SSDT but I don't know what benefits they bring.

On Big Sur... I am trying to download it but boy... the apple server seems to be hammered... Seems like it will take me another day.

I didn't mean to say or imply that your solution was wrong - if it works, it's right. And it's perfectly ok (and encouraged) to have more than one solution floating around. It just might be less confusing (and save us all work) if we minimize the amount of conversion that needs to take place between EFI versions as we propose fixes and enhancements. If we're posting EFIs that resemble each other, they will be much easier for each of us to adopt.

I can only provide you with my personal preferences - there isn't one "right" way to do this. There are many in this forum who know WAY more about this stuff than I do. My goal with each hack is to make it look to macOS like a real Mac. I find that the hack is much more likely to be compatible with new releases of MacOS. For example, I had a Device (EC) in my Dell E6410 Laptop DSDT patches before it was actually required in Catalina. As a result, upgrade to Catalina was simple. My ACPI patches (SSDTs) are intended to mimic a real MacMini (based on my review of a real MacMini ACPI extraction and my review of a real MacMini IORegistry dump).

I'm new to the OC config.plist, so I am open to the very likely possibility that I did something wrong in the config.plist. I have a lot to learn about Quirks and other elements of the OC config.plist.

Some points about my ACPI patches (SSDTs)

1. Some of my SSDTs inject Devices from a real MacMini (XSPI, PPMC, USBX)
2. There are "generic" SSDTs floating around that are not specific to the MacMini and may actually inject incorrect values (e.g. taking a USBX with higher USB power properties from a desktop may not be "healthy" for our HackMini's which are more like a laptop than a desktop. My USBX is extracted from a real MacMini. I'm not sure where the other USBX's came from).
3. SSDT-XOSI and SSDT-HPET are based on patching techniques that I've adopted from many ACPI patching trials. They're based on best practices that have worked for me and that have resulted in very stable / reliable builds.
4. MCHC, SBUS and PLUG are standard patches. SSDT-MCHC is equivalent to CLOVER's "Add MCHC." SSDT-PLUG is equivalent to CLOVERs "PluginType." Device (MCHC) is present in a real MacMini DSDT. The SBUS patch is as old as hackintoshing.
5. SSDT-AWAC is new for me - I only adopted it after reading about it in the Dortania guide. I'm not even sure our hacks need it.
6. Since our HP EliteDesk Mini's are designed for Windows, there are branches in the DSDT that are only executed when the appropriate Windows OS version is running. I've seen comments that SSDT-XOSI is a kluge that should be avoided. I don't agree and believe SSDT-XOSI is necessary. In my previous hacks (where I manually patched the DSDT and didn't use the bootloader's "on-the-fly patching), I have modified the DSDT to mimic a specific Windows version when MacOS was running (just like others have done). This is my first hack that uses on-the-fly DSDT patching. I've asked for advice here and didn't get feedback, so I currently have no reason to believe that my SSDT-XOSI is wrong.

Since all of this is my opinion, I'm open to constructive criticism and suggested changes. We're all here to learn!