Contribute
Register

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

Thanks :)

I always do it this way. An external SSD with a clone and an USB key with updated boot loader, in your case, OpenCore. Then, I do the update on the working clone. If it fails for whatever reason, you can fall back with a working computer.
So I have created the workable clone on an external drive as backup and then a second as a working copy to test upgrading to Sonoma. Is it better to put a new version of Opencore on a USB key and select this in BIOS then boot the clone drive to test? Or just try and upgrade Opencore on the test clone? I am a bit unsure how to do the USB key route? I assume I need to get Opencore and all the kexts etc upgraded first before going to Sonoma?
In case of success (for me, a couple of weeks running fine on the externals, MacOS and boot loader), you just have to CCC your external to the main (still having another backup somewhere, fruit cake happens) and dump the USB EFI to your main drive.
This sounds like an option. I was planning to test the upgrade on the external test drive, then do the same upgrade process on the main machine.
Only once I didn’t followed this procedure (my XPS in my signature) as I didn’t tested drive long enough (Ventura) and wiped my CCC backup once I thought that everything was fine! I had to rebuild my Big Sur drive from scratch (one day of labour)… The positive thing, at least, is that Big Sur was a clean install instead of my usual update procedure :).
 
...
Is it better to put a new version of Opencore on a USB key and select this in BIOS then boot the clone drive to test? Or just try and upgrade Opencore on the test clone?
Recommedation:
  • Boot the Testing clone as follows:
    • If the CCC procedure was followed completely, then both the Test and Backup clones will have their own EFI partitions, each with its own EFI folder
    • There will be 3 EFI folders:
      • Original EFI folder on NVMe SSD (Internal SSD)
      • Cloned EFI folder on Test Clone
      • Cloned EFI folder on Backup Clone
    • Because the 3 EFI folders are identical, just boot the system normally without pressing F12 at BIOS Splash Screen
    • OpenCore Boot Menu will appear
    • Select the Testing Clone
    • When macOS is up and running, mount the EFI partition of the Testing Clone
    • Run HackinDROM app and follow the instructions provided previously (link below) to update this EFI folder
  • Now reboot the computer
  • Press F12 at BIOS Splash Screen
  • Select the external Test Clone -- this will cause the new upgraded EFI folder to be used for boot
  • When OpenCore boot menu appears, look at the bottom right corner of the screen; do you see the new OpenCore version number?
  • Select the Testing Clone from OpenCore Boot Menu to ensure that macOS still boots up properly
  • If so, then copy EFI folder from Testing Clone to EFI partition of internal NVMe SSD (the original EFI folder on Internal NVMe SSD can be backed up or just renamed to something like EFI-OLD)
  • When macOS is up and running on the Testing Clone, perform an in-place upgrade to Sonoma
    • System will reboot several times during Sonoma installation, which is why it's good to have the new EFI folder on the Internal NVMe SSD so you don't have to press F12 and select external disk on each reboot
 
Last edited:
Recommedation:
  • Boot the Testing clone as follows:
    • If the CCC procedure was followed completely, then both the Test and Backup clones will have their own EFI partitions, each with its own EFI folder
    • There will be 3 EFI folders:
      • Original EFI folder on NVMe SSD (Internal SSD)
      • Cloned EFI folder on Test Clone
      • Cloned EFI folder on Backup Clone
    • Because the 3 EFI folders are identical, just boot the system normally without pressing F12 at BIOS Splash Screen
    • OpenCore Boot Menu will appear
    • Select the Testing Clone
    • When macOS is up and running, mount the EFI partition of the Testing Clone
    • Run HackinDROM app and follow the instructions provided previously (link below) to update this EFI folder
  • Now reboot the computer
  • Press F12 at BIOS Splash Screen
  • Select the external Test Clone -- this will cause the new upgraded EFI folder to be used for boot
  • When OpenCore boot menu appears, look at the bottom right corner of the screen; do you see the new OpenCore version number?
  • Select the Testing Clone from OpenCore Boot Menu to ensure that macOS still boots up properly
  • When macOS is up and running on the Testing Clone, perform an in-place upgrade to Sonoma
Fantastic thanks!!! :)
 
Hello! I am using Monterey right now with everything working! I was thinking updating to Sonoma. Is anything special I have to do?
I usually updated all the kext through HackinDROM and then updating the system.
I attached my config.plist.
 

Attachments

  • config.plist
    56.8 KB · Views: 18
Hello! I am using Monterey right now with everything working! I was thinking updating to Sonoma. Is anything special I have to do?
I usually updated all the kext through HackinDROM and then updating the system.
I attached my config.plist.
Please start here (top of Post 1):

Screenshot 2023-11-02 at 12.17.16 PM.png
 
Audio output is handled by AppleALC(U), not WEG. agdpmod=pikera is for Navi, not Vega, so your software configuration is strange.

It could also be a hardware issue with the (ageing?) Vega.
 
Audio output is handled by AppleALC(U), not WEG. agdpmod=pikera is for Navi, not Vega, so your software configuration is strange.

It could also be a hardware issue with the (ageing?) Vega.

Thanks for your response.

agdpmod=pikera was leftover from when I tried swapping the Vega for a 5700 XT (which also didn't work, leading me to think it's a config issue). I just removed it and rebooted, but of course AppleGFXHDA still loads.

Audio output is handled by AppleALC(U), not WEG.
Interesting. To be clear, I'm not trying to disable onboard audio, although I'm happy to do that as well. I'm trying to disable the audio over HDMI/DP from the graphics card. I have a USB Audio Interface.

This is what currently shows up in the log:
Code:
01:666 00:561 OC: Prelinked blocker (Disable) result 0 for com.apple.driver.AppleGFXHDA (Disable AppleGFXHDA) - Not Found

So if it can't find AppleGFXHDA, how is it still being loaded?

If there's anything else I can upload for people to look at let me know.
 
Last edited:
Interesting. To be clear, I'm not trying to disable onboard audio, although I'm happy to do that as well. I'm trying to disable the audio over HDMI/DP from the graphics card.
This is what I'm talking about: Audio output in display. And this is handled by AppleALC.kext.

What makes you think that blocking AppleGFXHDA would solve your issue?
If two different cards fail in the same way, you have either a configuration issue, or a hardware issue with the motherboard.
 
I've been running this build since 2018. Currently with an RX590 but I'm looking to squeeze out a little more gaming performance (in Windows) while preserving macOS compatibility as long as possible.

Is the 6600 the best choice? Like the user above I'm not looking to spend a fortune but can afford a few hundred CAD. I see 6650XTs on sale near me but I did a bit of poking around and it seems like getting that to play nice in macOS can be a pain. Basically, what are the best drop-in AMD cards for os 12 and onward?

I'm not obsessed with fps or the coolest new rendering features, I just want to buy a smoother gaming experience while I save up for a mac studio to ultimately replace this trusty rig. Frankly the RX590 has served me very well until just recently. Baldur's Gate 3 in particular is straining the system at higher resolutions.

EDIT:
This card in particular looks like good performance for the price:

This option is cheaper and maybe more readily compatible but won't perform as well:

I guess I'm looking for some assurance from someone who's more knowledgeable about this particular build and the new(er) batch of AMD cards.
 
Last edited:
Back
Top