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

[imcalledandy]

@CaseySJ I just wanted to give you an update as I've finally solved why the eGPUs were conflicting.

I had to remove npci=0x2000 from my boot-args and now all is well. This was probably conflicting with Above 4G Encoding (which is enabled).

I just wanted to say thanks again and I couldn't have got this far without your help. I've learnt a lot more by going through the struggle.

The final piece of the puzzle is the Speed value in the Thunderbolt Device Tree – it's still 20Gb/s x2 so that will continue to flex my grey matter...

 

[CaseySJ]

@CaseySJ I just wanted to give you an update as I've finally solved why the eGPUs were conflicting.

I had to remove npci=0x2000 from my boot-args and now all is well. This was probably conflicting with Above 4G Encoding (which is enabled).

Oh yes, two those parameters are mutually exclusive!

I just wanted to say thanks again and I couldn't have got this far without your help. I've learnt a lot more by going through the struggle.

The final piece of the puzzle is the Speed value in the Thunderbolt Device Tree – it's still 20Gb/s x2 so that will continue to flex my grey matter...

Let's see if we can make a last stand against this affliction:

• First, some reminders:
  • You're using the on-board Titan Ridge controller on the X299X Designare 10G?
  • You've flashed that controller with NVM 33 from the Designare Z390?
  • You're running Big Sur?
  • There are no other Thunderbolt controllers (add-in-cards) in the system?
• Next, some data:
  • Latest IOReg file (IORegistryExplorer --> File --> Save As...)...
    • With both eGPUs connected
    • With both eGPUs disconnected
  • Screenshot of System Information --> Thunderbolt...
    • With both eGPUs connected
    • With both eGPUs disconnected
  • Copy of Thunderbolt SSDT currently in use

 

[imcalledandy]

Let's see if we can make a last stand against this affliction:

Thanks @CaseySJ!

• You're using the on-board Titan Ridge controller on the X299X Designare 10G?
  • Yes
• You've flashed that controller with NVM 33 from the Designare Z390?
  • Yes
• You're running Big Sur?
  • 11.1
• There are no other Thunderbolt controllers (add-in-cards) in the system?
  • No

Next, some data:

All attached.

 

[telicha]

Hello @telicha

Yes please upgrade the BIOS to F9i from Gigabyte's website. Then configure all BIOS parameters starting with F7 (Load Optimized Defaults). In BIOS F9i the Boot section contains a parameter called CFG-Lock, which we need to manually Disable. This is necessary, otherwise the OpenCore EFI will not boot.

Because CFG-Lock can be disabled simply through BIOS Setup, we can ignore all steps related to manually unlocking MSR 0xE2.

Thanks so much for the guidance!!! It worked like a charm .... first got the F9i firmware update from the gigabyte website. The only thing to note is that you need to save your BIOS params to an external disk, as a firmware update destroys that data. Not a big deal. So I re-did BIOS params setup, F7, disable VT-d, enable internal graphics, enable above 4G, set TB security level to no security, enable TB USB support, enable GPIO3 Force Pwr, enabled USB XHCI Handoff, window features set to Other OS, CSM support disabled and CFG-Lock disabled. On the USB EFI partition I copied over CaseySJ's OC 0.6.5, copied AMD to config.plist, edited the ROM, MLB, UUID, Serial Number and System type. Then copied over SSDT-GPRW.aml from Clover's EFi, and used the OC configurator to add a reference to it, and also created a patch for that SSDT. Except from some strange message about Deduplicate something when EFI boots - not sure what is - or if it matters, Catalina seems to be working perfect booting from OC. I'll play with the system a few days, make sure is completely stable, and I guess I can just use the System Preferences -> Software Update to update to Big Sur, after making a Catalina backup.

Thanks so much CaseySJ and all the other people that kindly helped me!

 

[ramjammer]

Get some sleep and we’ll help you when you wake. The devil is in the details so every step in the guide should be read twice.

So I followed the guide at every step and this is the screen I got when I tried installing Big Sur. Tried both with Opencore 0.6.3 according to the guide and 0.6.5. I'm also installing Big Sur 11.1 since that's what is available through the App Store.

Thinking it was Apple thwarting Hack installs with the latest version of Big Sur, I then tried to install Catalina with OC 0.6.5 and followed the same steps and got this screen upon installation.

 

[xp3rienc]

Anyone have experience with the Alpine Ridge Card? I'm trying to get my Thunderbolt Display to work properly.
The display itself work just fine, but no USB, Camera, Speaker or Mic. My LacCie Big2 daisychained also works.

 

[CaseySJ]

So I followed the guide at every step and this is the screen I got when I tried installing Big Sur. Tried both with Opencore 0.6.3 according to the guide and 0.6.5. I'm also installing Big Sur 11.1 since that's what is available through the App Store.

View attachment 504081

Thinking it was Apple thwarting Hack installs with the latest version of Big Sur, I then tried to install Catalina with OC 0.6.5 and followed the same steps and got this screen upon installation.

View attachment 504082

Please enable “verbose” mode by pressing and releasing CMD-V at the OpenCore Picker window, then select the option to install macOS Big Sur. Now you should see detailed log messages on screen. Post a photo of the screen if/when the log messages stop flowing.

 

[CaseySJ]

Anyone have experience with the Alpine Ridge Card? I'm trying to get my Thunderbolt Display to work properly.
The display itself work just fine, but no USB, Camera, Speaker or Mic. My LacCie Big2 daisychained also works.

Apologies if the following is unpleasant to read, but I have to point out Note 7C at the top of Post 1:

“NOTE 7c: Thunderbolt monitors must also be avoided. They may not turn on in BIOS or in the boot loader. They may also not wake from sleep. Their on-board devices may not work either. Too many problems are being reported and there are no solutions. No support will be provided for issues with Thunderbolt monitors.”

 

[ramjammer]

Please enable “verbose” mode by pressing and releasing CMD-V at the OpenCore Picker window, then select the option to install macOS Big Sur. Now you should see detailed log messages on screen. Post a photo of the screen if/when the log messages stop flowing.

For some reason all my install attempts don't show the Opencore picker. When I push F12, I'll get the dialog for the UEFI folder but it goes straight into trying to install Big Sur. At that point I get the Apple logo then the X like in the photo in my last post. Is the config.plist in the zip set not go to into verbose mode?

By the way, my apologies if I'm missing something. I didn't have this issue when I first installed Mojave on another computer but that was a couple years ago using Clover. For some reason, it seemed easier back then.

 

[CaseySJ]

For some reason all my install attempts don't show the Opencore picker. When I push F12, I'll get the dialog for the UEFI folder but it goes straight into trying to install Big Sur. At that point I get the Apple logo then the X like in the photo in my last post. Is the config.plist in the zip set not go to into verbose mode?

By the way, my apologies if I'm missing something. I didn't have this issue when I first installed Mojave on another computer but that was a couple years ago using Clover. For some reason, it seemed easier back then.

Please list the steps you took to create the USB install disk. Just use a bullet list to briefly describe each step.