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

[CaseySJ]

Hi All

I upgraded to Ventura yesterday -- It was amazingly easy (upgrade to OC 8.5 and, prepare a flash stick and install) and pretty much everything seems to be working except for DRM. (I had this problem in Ventura also.)

I have the stock setup @CaseySJ recommends except my video card is a Vega 56, and I have a i9 with iGPU.

In looking through forum posts it seems like there is not a definitive way to enable DRM (for things like Apple Music and Apple TV+) in Ventura. Is that true?

With iMac19,1 we have a problem with DRM. But with MacPro7,1 it works fine. Some things to consider:

• MacPro7,1
  • tv+ and Music app (DRM) both work fine
  • Requires RestrictEvents.kext to avoid lots of unnecessary notifications
  • Sidecar will not work; if you don't use this, then no worries
• iMac19,1
  • tv+ and Music app (DRM) will not work (but if you subscribe to music, it will work)
  • Sidecar works with iGPU

 

[schlosrat]

@schlosrat,

Although you have a Z390 AORUS Pro and not the Designare, you can still try using the OpenCore 0.8.3 EFI folder from this post.

Do you have any Hackintosh kexts installed in Catalina's /Library/Extensions folder? Those will interfere with OpenCore.

Thanks @CaseySJ! That's a great looking guide!

I assume there are not Hackintosh kexts in the /L/E foler since I did a clean install wiping the drive with Disk Utility prior to installing. I think all that would be in /L/E is whatever the Monterey installer put there, and when I ran that it was after booting from an OC USB, so probably no Hackintosh kexts! Could I be wrong about this?

Can I use the latest version of OCC (2.63.0.0) with OC 0.8.5 and your guide? I assume if I copy EFI folder I'll be getting OC 0.8.3 with your OpenCore.efi file. This might be two questions. Can I use OCC 2.63.0, and can I replace the 0.8.3 OC efi with the 0.8.5 efi?

Using OCC 2.63.0, the only options I've got are for OC 0.8.5 Release and 0.8.6 Development, so I went with 0.8.5 Release and replaced the drivers with the corresponding 0.8.5 versions. Ditto for tools that shipped with 0.8.5.

I copied config-AMD-GPU.plist to config.plist since I've got an AMD GPU.

I populated screens per your guide, choosing Default for SecureBootModel, and 0 for SetApfsTrimTimeout since I've got a Samsung NVMe SSD. For my system product name I went with an iMac19,1 since that corresponds to my i9 processor. This gave me a ProcessorType of 4105.

With all that in there, I was suprised how quickly it booted and got to the OpenCanopy GUI. I selected my WSD500, and then it hung at an apple logo with no progress bar.

I'm going to try next with the 0.8.3 drivers and files in your EFI, SecureBootModel = Disabled, but still using OCC 2.63.0 and the iMac19,1 setting.

Can I use an iMacPro1,1 setting like you have when my CPU is not a Xeon?

 

[CaseySJ]

Thanks @CaseySJ! That's a great looking guide!

I assume there are not Hackintosh kexts in the /L/E foler since I did a clean install wiping the drive with Disk Utility prior to installing. I think all that would be in /L/E is whatever the Monterey installer put there, and when I ran that it was after booting from an OC USB, so probably no Hackintosh kexts! Could I be wrong about this?

You're right. On a fresh install of Monterey there's nothing to worry about!

Can I use the latest version of OCC (2.63.0.0) with OC 0.8.5 and your guide? I assume if I copy EFI folder I'll be getting OC 0.8.3 with your OpenCore.efi file. This might be two questions. Can I use OCC 2.63.0, and can I replace the 0.8.3 OC efi with the 0.8.5 efi?

Using OCC 2.63.0, the only options I've got are for OC 0.8.5 Release and 0.8.6 Development, so I went with 0.8.5 Release and replaced the drivers with the corresponding 0.8.5 versions. Ditto for tools that shipped with 0.8.5.

Yes this is also okay. Simply download the 0.8.3 EFI folder and replace both (a) OpenCore.efi and (b) BOOTx64.efi with those from 0.8.5. Then you can use OpenCore Configurator 2.63.0.0 set to 0.8.5 Release Version.

I copied config-AMD-GPU.plist to config.plist since I've got an AMD GPU.

I populated screens per your guide, choosing Default for SecureBootModel, and 0 for SetApfsTrimTimeout since I've got a Samsung NVMe SSD. For my system product name I went with an iMac19,1 since that corresponds to my i9 processor. This gave me a ProcessorType of 4105.

With all that in there, I was suprised how quickly it booted and got to the OpenCanopy GUI. I selected my WSD500, and then it hung at an apple logo with no progress bar.

At OpenCore boot picker we can press and release CMD-V to enable verbose logs. Then select the macOS installer. Note that CFG-Lock in BIOS must be disabled.

I'm going to try next with the 0.8.3 drivers and files in your EFI, SecureBootModel = Disabled, but still using OCC 2.63.0 and the iMac19,1 setting.

Can I use an iMacPro1,1 setting like you have when my CPU is not a Xeon?

Yes, no problem. But in that case, add RestrictEvents.kext.

 

[schlosrat]

You're right. On a fresh install of Monterey there's nothing to worry about!


Yes this is also okay. Simply download the 0.8.3 EFI folder and replace both (a) OpenCore.efi and (b) BOOTx64.efi with those from 0.8.5. Then you can use OpenCore Configurator 2.63.0.0 set to 0.8.5 Release Version.


At OpenCore boot picker we can press and release CMD-V to enable verbose logs. Then select the macOS installer. Note that CFG-Lock in BIOS must be disabled.


Yes, no problem. But in that case, add RestrictEvents.kext.

Got it, so use RestrictEvents.kext if set System Product Name is MacPro1,1.

Is the advantage to that product name just about tv+ and Music app (DRM), like you mentioned above for MacPro7,1? Just wondering what the advantages may be to going that route, but first I need it to boot all the way through an install!

 

[schlosrat]

Well that was weird...

I tired replacing just (a) OpenCore.efi and (b) BOOTx64.efi with the 0.8.5 versions, but all that got me was

BEP: Invalid revision 2 (!= 3) in loaded driver
Halting on critical error

So I went back to all 0.8.5 drivers, and stuffed in the release version of (a) and (b) above, so an 0.8.5 set of files like I had when it locked up, except now SecureBootModel is disabled, and CFG-Lock is diabled in the BIOS.

That got me to the screen where you pick your region, and I stayed there for quite some time! the keyboard was working (at least the arrow keys were), but now the mouse wasn't, and no amount of pressing Enter or using the Right arrow key would select the region. I could move up and down the list, but I couldn't select anything.

In the past when I've gotten this far the mouse always worked. Not sure what's wrong now, but it's a safe bet it's got something to do with USB.

Also, I apparently do not know what I'm doing with CMD + V. I've got a Windows keyboard, but I think the CMD equivalent is my Alt key (first key to the left of Space). Maybe it's the Windows key (between Ctrl and Alt). In any event I tried pressing a bunch of combos and never got a chance to pick a destination for the verbose logs - was I supposed to get something like that?

 

[Ponkass]

Updating to OC 0.8.5 caused my Windows 10 boot drive to brake. It's on a separate Sata SSD, macOS is on M.2. It shows up on the OC boot screen, but when I select it, screen goes black and computer immediately freezes. I can tell because holding down the power button makes it shut off within a second.

Picking the Windows drive from the F12 boot menu works fine though.

I haven't changed anything on the Windows EFI disk. Thanks for any help!

 

[schlosrat]

Got it booted! Just needed to move the mouse to another USB port. No doubt, I'll need to map my USB ports - that will be one of the next things I do along with sorting out why I don't have audio...

Is it safe to simply replace the /EFI folder on the root of my NVMe SSD (the one I just installed Monterey to) with a copy of the /EFI from my OC boot USB? I assume that's the procedure... Take the /EFI that works and got me booted from the USB and replace what's on the /EFI for the Monterey boot drive, right?

Here, hold my beer...

 

[CaseySJ]

Updating to OC 0.8.5 caused my Windows 10 boot drive to brake. It's on a separate Sata SSD, macOS is on M.2. It shows up on the OC boot screen, but when I select it, screen goes black and computer immediately freezes. I can tell because holding down the power button makes it shut off within a second.

Picking the Windows drive from the F12 boot menu works fine though.

I haven't changed anything on the Windows EFI disk. Thanks for any help!

This happens on some Windows systems when we enable AppleVTD. If we disable AppleVTD, it's possible that some devices such as Ethernet ports may not work. Feel free to try without AppleVTD.

 

[CaseySJ]

Got it booted! Just needed to move the mouse to another USB port. No doubt, I'll need to map my USB ports - that will be one of the next things I do along with sorting out why I don't have audio...

Yes this is a USB port map issue. We can use USBToolBox in Windows to map ports. Alas, that procedure is not particularly well documented. We also have a guide here on TonyMac:

The New Beginner's Guide to USB Port Configuration

Important: January 2023 Update It's been a while since this guide was written and Apple has changed their USB sub-system in several significant ways. So please bear in mind: 1) From Big Sur 11.3 onwards the OpenCore XhciPortLimit Quirk stopped working. It hasn't been fixed yet. So generally we...

www.tonymacx86.com

Is it safe to simply replace the /EFI folder on the root of my NVMe SSD (the one I just installed Monterey to) with a copy of the /EFI from my OC boot USB? I assume that's the procedure... Take the /EFI that works and got me booted from the USB and replace what's on the /EFI for the Monterey boot drive, right?

Here, hold my beer...

Yes, just replace the EFI folder.

 

[schlosrat]

Yes this is a USB port map issue. We can use USBToolBox in Windows to map ports. Alas, that procedure is not particularly well documented. We also have a guide here on TonyMac:

The New Beginner's Guide to USB Port Configuration

Important: January 2023 Update It's been a while since this guide was written and Apple has changed their USB sub-system in several significant ways. So please bear in mind: 1) From Big Sur 11.3 onwards the OpenCore XhciPortLimit Quirk stopped working. It hasn't been fixed yet. So generally we...

www.tonymacx86.com

Yes, just replace the EFI folder.

Yep, worked! On to the mapping of USBs...