Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Thank you @CaseySJ, I will give this a go shortly :) Just confirming, with the deleting of the original DMAR, Do I type DMAR under Table Signature in OC Configurator or do I type the code <444D4152> as show if I open the config-AMD-GPU.plist file in a PLIST editor.
Both of those options are okay. Simplest would be to use OpenCore Configurator and select DMAR from the drop-down menu in the ACPI —> Delete section. Ensure that OpenCore Configurator is set to 0.7.2 Release Version.
 
I've recently upgraded to MacOS 11.5.1. Which was a breeze with OpenCore Configurator and HackinDROM! Everything is up-to-date (OC 0.7.1). Only the memory of the RX580 was always maxed out, even when doing nothing. I checked HackinDROM and there was an update voor OpenCore to 0.7.2. I ran the update and it seems a little better, but memory usage is still climbing. Is this something to worry about, or something I can do to prevent it?

(Screenshot up to 14:28 was OC 0.7.1)
 

Attachments

  • iStat-menu.png
    iStat-menu.png
    1.5 MB · Views: 53
I've recently upgraded to MacOS 11.5.1. Which was a breeze with OpenCore Configurator and HackinDROM! Everything is up-to-date (OC 0.7.1). Only the memory of the RX580 was always maxed out, even when doing nothing. I checked HackinDROM and there was an update voor OpenCore to 0.7.2. I ran the update and it seems a little better, but memory usage is still climbing. Is this something to worry about, or something I can do to prevent it?

(Screenshot up to 14:28 was OC 0.7.1)
I think you're okay. The GPU RAM usage and GPU load are two different things. Launch Activity Monitor and the GPU History window.
 

Attachments

  • Activity Monitor + GPU History.png
    Activity Monitor + GPU History.png
    122.4 KB · Views: 47
** HackinDROM 1.5.0 Released **
Credit: @Inqnuam
  • Can be used to upgrade to OpenCore 0.7.2 safely
  • Catalina and Mojave users will need to manually set APFS MinDate and MinVersion to -1 after the update is done
  • OpenCore 0.7.2 Mini-Guide has been updated
 
The original DMAR table must be deleted. In hindsight, I should have noted that upgrades to 0.7.2 should not be done through the upgrade mechanism of HackinDROM App because of the extra differences in config.plist.

It’s best to perform the upgrade using HackinDROM’s “Create EFI” function or to do it manually by downloading the EFI zip and transferring PlatformInfo credentials into the appropriate config.plist.

In your case, however, simply add the delete entry to ACPI section. If you download the EFI zip file from the mini-guide and look at config-AMD-GPU.plist, you will see how to add the Delete entry.
Thank you for this info @CaseySJ

I used HackinDROM 1.4.9 to upgrade from OC 0.7.1 to 0.7.2, and for my machine and current config, it was a disaster (I could no longer boot into either of my two Windows 10 installations.) So I went back, and am currently stuck on 0.7.1.

Do we have an updated/current guide to assist n00bes (like myself) on this complete process? Ideally I would like to use such a process to rebuild my entire configuration based on current knowledge, to date, so that I would have a "clean machine" and then be able to go up to 0.7.2. I have several small issues and oddities I've just been living with (such as NOT being able to get any updates from Apple to ever show up in software update), and I haven't dealt with the AppleVTD thing yet, but want to as well.

As always, thank you for everything!
 
Hello @khaoskosmos,

The ports HS08 and HS13 allow USB 2.0 devices to connect to your Thunderbolt ports. This means you can connect an iPhone or iPad to those ports using the appropriate cable (i.e. Lightning-to-USB-C or USB-C to USB-C for iPad Pro).

There is no downside to enabling HS08 and HS13 as long as you expect to connect a USB 2.0 device to those ports. However, by enabling HS08 and HS13 we had to disable two other ports in order to retain the 15-port limit.

Thanks @CaseySJ

I think the issue is that I have a Dell U3818DW monitor that also has USB 3.1 Ports, and now most of my accessible USB 3.1 ports only recognize USB2 devices. Even my Fractal Design front USB C gen 2 port is only USB2 now (it did not work with USB2 devices before). Is there a good way to get this sorted out?

Screen Shot 2021-08-07 at 9.21.18 AM.png

Screen Shot 2021-08-07 at 9.25.48 AM.png
 
Might this be the answer to my #32,988 post? :O
Yes the new version (1.5.0) should be the answer. Give it a try, and to be safe you can do something like this:
  • Insert a USB flash disk that has an EFI partition
  • Copy your existing (working) OpenCore 0.7.1 EFI folder to the EFI partition on the USB flash disk
  • Now update the USB flash disk via HackinDROM to 0.7.2
  • If you're running Mojave or Catalina, be sure to change APFS MinDate and MinVersion to -1 (in UEFI --> APFS section)
  • Boot from the USB flash disk (press F12 at BIOS splash screen to open the BIOS boot menu and choose the USB Disk)
  • Check if everything is okay
 
Thanks @CaseySJ

I think the issue is that I have a Dell U3818DW monitor that also has USB 3.1 Ports, and now most of my accessible USB 3.1 ports only recognize USB2 devices. Even my Fractal Design front USB C gen 2 port is only USB2 now (it did not work with USB2 devices before). Is there a good way to get this sorted out?
Please refer to attached PDF. The following ports are enabled in your USB SSDT:
  • USB 2.x ports
    • HS05, HS06, HS07, HS08, HS09, HS10, HS11, HS12, HS13
  • USB 3.x ports
    • SS01, SS03, SS04, SS05, SS06, SS07

Referring to the attached PDF, to which USB port is your Dell monitor connected?
 

Attachments

  • Designare Z390 and Fractal Design Define R6 Connect D1.pdf
    515.8 KB · Views: 68
@CaseySJ
I have a strange issue I haven't been able to find online.
I updated to macOS 11.5.1 after updating to OC 0.7.2 using HackinDROM v1.5.0
When I boot into OC, I select my windows 10 drive, and it stays at a black screen.
After 2-3 reboots it displays the "Preparing Automatic Repair" and just freezes at that screen.
I thought maybe it takes a while, but I left it overnight, and it's still at that message.
I set my BIOS to boot into windows 10 directly, and that actually worked.
For some reason I can't log into windows from OC boot menu. I have override in BIOS.
I tried both resetNVRAM and cleanNVRAM. I'm not sure of the difference, so I tried both.
Any idea?

EDIT: I also updated windows to latest update
 
Back
Top