Contribute
Register

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

I was experiencing an audio "pop" during macOS startup (before login prompt). Solution is to uninstall CLOVER's AudioDxe.efi driver. This change is included in the EliteDesk.zip archive attached to Post #1.

See note here.
 
Last edited:
EDIT: I resolved the slow NVMe SSD performance by replacing the ADATA NVMe SSD with a Western Digital NVMe SSD here. Leaving this post for historical purposes.
------------------------------------------------------

Did a quick test to see if I could figure out why Catalina boot times are slower from the M.2 NVMe SSD than from the 2.5" SATA6 SSD. Doesn't make sense. See attached performance comparisons of the two SSDs. The faster R/W times are for the M.2 NVME SSD.
 

Attachments

  • Screen Shot 2020-06-12 at 10.55.27 AM.png
    Screen Shot 2020-06-12 at 10.55.27 AM.png
    175.2 KB · Views: 131
  • Screen Shot 2020-06-12 at 11.00.00 AM.png
    Screen Shot 2020-06-12 at 11.00.00 AM.png
    188.7 KB · Views: 125
Last edited:
I have started to test the USB 3.1 Type C port using a Type C to standard USB 3 adapter. Attached is the updated SSDT-UIAC.aml with the added USB 3 mappings for the Type C port (HS10 and SS03). This update is included in the EliteDesk.zip archive attached to Post #1.
 

Attachments

  • SSDT-UIAC.zip
    819 bytes · Views: 134
Last edited:
I have created an initial draft of the Catalina install instructions here.
 
I have been looking at the IOReg / ACPI dump from a real MacMini8,1 to see if it offers any clues for improving my HackMini8,1 (just playing, since everything appears to be working perfectly). I have found the following IGPU property differences between my HackMini8,1 and a real MacMini8,1.

Real MacMini8,1 HackMini8,1 (HP EliteDesk 800 G4 Mini)
device-id 0x00003e9b (I7-8700B / UHD 630) 0x00003e92 (I7-8700T / UHD 630)
AAPL,ig-platform-id 0x3e9b0007 0x3e920000
compatible pci8086,3e9b pci8086,e392
AAPL,GfxYTile 0x00000001 not defined



If I want my HackMini8,1 to more closely mimic the IGPU device properties of a real MacMini8,1, I have found that the IGPU device properties from a real MacMini8,1 "work" with one exception: my HackMini8,1 boots to black screens if I use AAPL,ig-platform-id = 0x3e9b0007. I must use an AAPL,ig-platform-id that ends in 0x00 (e.g. 0x3e9b0000) which is consistent with what I determined here before.

I am currently running with the IGPU device properties below to see if there are any behavioral differences.

Actual Value Reverse byte order
device-id 0x00003e9b 0x9b3e0000
AAPL,ig-platform-id 0x3e9b0000 0x00009b3e
compatible pci8086,3e9b N/A
AAPL,GfxYTile 0x00000001 0x01000000


With this configuration (device-id 0x3e9b), my HackMini8,1's GeekBench 5 Metal score (attached) is slightly higher than the Metal Score I attached to Post #1 with my baseline (device-id 0x3e92) configuration. I think this slight difference is within the margin of error, so it probably doesn't indicate any change in performance.

Interesting Observations
Interesting observations in Hackintool: When I configure my CLOVER config.plist with IGPU properties device-id=0x00003e92, AAPL,ig-platform-id=0x3e920000, Hackintool shows the correct connector-types (DigitalDVI) for my patched display ports. When I configure my IGPU properties as device-id=0x00003e9b, AAPL,ig-platform-id=0x3e9b0000, Hackintool shows that my patched connector-types are not the DigitalDVI types that I have specified in my patched configuration. See attached screenshots.

I'm not certain, but this might offer clues for those who are having difficulty with their IGPU device properties, suggesting that experimentation with different device-ids is critical to achieving the optimal IGPU patch.

In my case, using the native device-id for my I7-8700T / UHD 630 (0x3e92) appears to be better than spoofing the device-id as 0x3e9b.
 

Attachments

  • Screen Shot 2020-06-14 at 11.15.13 AM.png
    Screen Shot 2020-06-14 at 11.15.13 AM.png
    76.8 KB · Views: 122
  • Screen Shot 2020-06-14 at 11.27.39 AM.png
    Screen Shot 2020-06-14 at 11.27.39 AM.png
    21.8 KB · Views: 115
  • Screen Shot 2020-06-14 at 11.24.19 AM.png
    Screen Shot 2020-06-14 at 11.24.19 AM.png
    20.2 KB · Views: 122
Last edited:
Hi,

Finally have my setup installed and working without flaw today. I finally did it through opencore way, but it would have worked either way. As I mentioned earlier, I had a (1) stuttering USB audio and (2) System not shutting down/restarting properly (every time needed hard reboot) as major issues. The first one was a real show stopper in my case.

Spend some decent time reading, created own SSDT from the dumps, tried addressing each issues. However finally found those two problems replicated as same. Did try many work arounds and none worked.

Finally found my Intel Pro 6000p NVMe was the culprit. Today replaced it with a SEAGATE SATA and everything working like a charm till now. Will know more when I use it for a couple of days.

Thanks for all support!

Regards,
Manoj
 
Hi,

Finally have my setup installed and working without flaw today. I finally did it through opencore way, but it would have worked either way. As I mentioned earlier, I had a (1) stuttering USB audio and (2) System not shutting down/restarting properly (every time needed hard reboot) as major issues. The first one was a real show stopper in my case.

Spend some decent time reading, created own SSDT from the dumps, tried addressing each issues. However finally found those two problems replicated as same. Did try many work arounds and none worked.

Finally found my Intel Pro 6000p NVMe was the culprit. Today replaced it with a SEAGATE SATA and everything working like a charm till now. Will know more when I use it for a couple of days.

Thanks for all support!

Regards,
Manoj

Congrats - glad this helped.
 
Congrats - glad this helped.
Hi,

To fix the BIOS clock reset issue, which bytes (00-FF) are you restricting write? For me i found DF and it is mostly working. But sometimes the issue is popping up (i i think it is still happening in case of shutdowns). Not sure if there are different area for shutdown/restart.

Regards,
Manoj
 
Hi,

To fix the BIOS clock reset issue, which bytes (00-FF) are you restricting write? For me i found DF and it is mostly working. But sometimes the issue is popping up (i i think it is still happening in case of shutdowns). Not sure if there are different area for shutdown/restart.

Regards,
Manoj

I'm using Clover, not OC. Please read my Known Issues for my solutions.

EDIT: @tkmanutk Just for fun, I installed RTCMemoryFixup.kext v1.0.6 from here, disabled "FixRTC" and "Apple RTC" in Clover config.plist and added boot-arg rtcfx_exclude=00-FF. Even when excluding the entire 00-FF range, I experience RTC CMOS reset problems.

Maybe one of the moderators in this forum can help you with OC / RTC.

In my opinion, if you want a working system, I would advise you to use CLOVER as I have done. I don't see any reason to use OC on this perfect HackMini8,1.
 
Last edited:
I have added a post here to track things that I'm investigating and that I have not yet added to my system baseline.
 
Back
Top