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

[CaseySJ]

Thankyou @Inqnuam for that explanation, makes sense. Either way, I disabled 'DisableIOMapper', removed dart=0 from boot args, enabled VTD in bios and then rebooted, first boot into BigSur and everything was playing up, for example, top menu bar was only showing if I opened an application, Shutdown was not working, restart was not working and I had to manually power of the system. I turned power off to the PSU for about 5 mins and then powered the machine back up and all worked fine....... except...... my wifi indicator in the top menu bar had a line through it and I could not enable wifi.. Will this be caused by the AppleVTD or the corresponding settings?

I would really like to enable AppleVTD however not at the expense of wifi

Hopefully there is a simple solution to this

There are five things to check that are listed in the first 5 bullets of this post:

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

That totally sounds like a plan! Thanks — will try shortly. I'm using it on Monterey and looks like it fixed the issues when AirDrop Continuity Handoff, Connection to AirPods Pro, RSSI stopped working after wake-from-sleep If Apple gives us back Bluetooth API in next Monterey versions I can...

www.tonymacx86.com

 

[Lukey1979]

There are five things to check that are listed in the first 5 bullets of this post:

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

That totally sounds like a plan! Thanks — will try shortly. I'm using it on Monterey and looks like it fixed the issues when AirDrop Continuity Handoff, Connection to AirPods Pro, RSSI stopped working after wake-from-sleep If Apple gives us back Bluetooth API in next Monterey versions I can...

www.tonymacx86.com

Thank you @CaseySJ, they were the exact 5 points I followed, although I never had to delete DMAR from the Delete section as it was never there in the first place. Also I didn't touch this (OpenCore --> Add SSDT-DMAR.aml (attached) to ACPI --> Add section as shown) as it was placed in the ACPI section automatically with the OC 0.7.2 update through HackinDROM

I hope all that made sense

 

[CaseySJ]

Thank you @CaseySJ, they were the exact 5 points I followed, although I never had to delete DMAR from the Delete section as it was never there in the first place. Also I didn't touch this (OpenCore --> Add SSDT-DMAR.aml (attached) to ACPI --> Add section as shown) as it was placed in the ACPI section automatically with the OC 0.7.2 update through HackinDROM

I hope all that made sense

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.

 

[Lukey1979]

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 @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.

 

[CaseySJ]

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.

 

[jrebergen]

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)

 

[jiffyslot]

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.

 

[CaseySJ]

** 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

 

[BOTMT]

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!

 

[BOTMT]

** 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

Might this be the answer to my #32,988 post?