Contribute
Register

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

And as for the "Just have to copy your serial numbers into PlatformInfo --> DataHub. "

I'd do that via propertree after the boot correct?
Follow the guide below, but adapt it for OpenCore 0.7.6. Step 11 shows which PlatformInfo credentials need to be copied.
 
@CaseySJ As ever, I am thankful for your help - I am the guy with the Z390 Aurous Xtreme from the very early days of this thread. I had been stable on 0.6.7 and then 0.7 OC for some time but decided yesterday to upgrade from Big Sur to Monterray and update OC. I started with OC and was able to update to 0.7.6 but I broke wifi and bluetooth (I have a Broadcom WiFi card that should be native, I suspect USB problem). So I figured I would fix that after upgrading to Monterray, which I installed and then I can no longer get the system to boot. The last time I updated my system, we were all using open core configurator and HackinDROM doesn't have a thing for my Z390 Xtreme. Can you take a look at my EFI / config.plist here to see what dumb thing I am sure that I have done? Thank you as always.
I’ll take a look soon. Some immediate comments:
  • VT-d should be enabled in BIOS if t you’re dropping the original DMAR table and replacing it with a modified version.
  • BlueToolFixup.kext is necessary in Monterey for any kind of Bluetooth operation (both Broadcom and Intel).
Update:
  • Please try attached EFI folder, but copy serial numbers into PlatformInfo --> DataHub before use.
 

Attachments

  • EFI-frickergg.zip
    2.8 MB · Views: 49
Last edited:
If Monterey is installed on Samsung NVMe SSDs, boot time can increase by 60-100 seconds due to "trim" incompatibilty.
  • This can be addressed by cloning the Samsung NVMe SSD to another disk, erasing the Samsung NVMe SSD with Disk Utility, and cloning macOS back. Please be careful with this process if you decide to do it.
Hi Casey!

Do you know the reasoning for why this fix should work? I would like to try this but I'd like to understand the fix a bit better before I dive in :)
 
Hi Casey!

Do you know the reasoning for why this fix should work? I would like to try this but I'd like to understand the fix a bit better before I dive in :)
This may not be a good idea actually. Trim delays will come back after some period of time. It's best to replace the Samsung NVMe with a different brand. WD SN750 is a good choice.
 
This may not be a good idea actually. Trim delays will come back after some period of time. It's best to replace the Samsung NVMe with a different brand. WD SN750 is a good choice.
Too bad. I was hoping to get away with opening up the case as it's well hidden under a bunch of other equipment :) Thanks for the response. I will wait for a bit to see if the situation gets worse first. So far it's only boot times, but I guess it will get worse with time?
 
Last edited:
This may not be a good idea actually. Trim delays will come back after some period of time. It's best to replace the Samsung NVMe with a different brand. WD SN750 is a good choice.

Hi everyone.
I'm planning to upgrade to Monterrey from Mojave soon. Apart from the slower boot times, does anyone know if there are any performance problems with a Samsung NMVe 980 Pro after booting completed, like slower write/read speeds?
 
Hi everyone.
I'm planning to upgrade to Monterrey from Mojave soon. Apart from the slower boot times, does anyone know if there are any performance problems with a Samsung NMVe 980 Pro after booting completed, like slower write/read speeds?
@edunon

Once Monterey boots up, disk read/write speeds should be normal, but over time speed may degrade. It's more important, however, to read the sections Background and Operation here:
 
Follow the guide below, but adapt it for OpenCore 0.7.6. Step 11 shows which PlatformInfo credentials need to be copied.
This is just not working for me...I'll get to the graphical boot picker and once I hit my MacOS disk it'll fail with a critical error. I even tried going into the reinstall and it failed to load that page.

One big problem that I can see right now is that I'm booting off a backup EFI because I was stuck before. When I opened my Hackintool it showed me what you usually see before going through GenSMBIOS and getting your S/N. So I took the info from the EFI that's living on my main SSD via propertree (and not OC since its from 2020).


Lmk if you see anything that I did up top but at this point I dont mind just starting from scratch but with Big Sur. Should I start with the OC-076-DESIGNARE-Z390 EFI?
 
This is just not working for me...I'll get to the graphical boot picker and once I hit my MacOS disk it'll fail with a critical error. I even tried going into the reinstall and it failed to load that page.

One big problem that I can see right now is that I'm booting off a backup EFI because I was stuck before. When I opened my Hackintool it showed me what you usually see before going through GenSMBIOS and getting your S/N. So I took the info from the EFI that's living on my main SSD via propertree (and not OC since its from 2020).


Lmk if you see anything that I did up top but at this point I dont mind just starting from scratch but with Big Sur. Should I start with the OC-076-DESIGNARE-Z390 EFI?
Yes it might be best to try a fresh Big Sur installation with OC-076-DESIGNARE-Z390. It is absolutely essential to configure BIOS according to Post 1 because some settings in config.plist will cause boot failure otherwise.
 
Back
Top