Contribute
Register

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

I don’t know what you mean. BIOS does not interfere with Thunderbolt. Even on-board Thunderbolt has its own firmware chip (it does not use BIOS chip).

In any case, your motherboard’s Thunderbolt firmware has not been changed.
Oh alright. I asked that because I read on this thread that newer BIOS versions (such as F9I) may not be compatible with TB3 HotPlug. In any case I'll let you know if I can succeed with the TBTFlash.exe, otherwise I'll try the SPI Flasher way.
Eventually can you please send me the latest available modded firmware?
 
Oh alright. I asked that because I read on this thread that newer BIOS versions (such as F9I) may not be compatible with TB3 HotPlug. In any case I'll let you know if I can succeed with the TBTFlash.exe, otherwise I'll try the SPI Flasher way.
Eventually can you please send me the latest available modded firmware?
The most recent modified firmware for this motherboard is located in the post below. We have two choices:
  • NVM33
  • NVM67 — for better compatibility with USB4 hubs
 
As you can see, Thunderbolt Bus is not getting activated on Asus EX-3. It is fully activated on GC-TR.

We always had a difficult time with the Asus EX-3. I even damaged mine after a botched firmware flashing attempt!

@CaseySJ , thank you for your fast reply! Can you tell me:

  • Has anyone been able at all to enable the Thunderbolt Bus with the ASUS ThunderboltEX3 Rev B yet or is it a technical limitation with Alpine Ridge, and I can stop trying?
  • Is there a reliable way to determine whether Thunderbolt Bus has been enabled? How can I see that in IOReg or is there another way to check that?
  • Is it only the firmware that decides about Thunderbolt Bus, and can I rely on the SSDT being totally error-free and does not require additional modification?
Best wishes
-cuemaxx
 
@CaseySJ , thank you for your fast reply! Can you tell me:

  • Has anyone been able at all to enable the Thunderbolt Bus with the ASUS ThunderboltEX3 Rev B yet or is it a technical limitation with Alpine ridge and I can stop trying?
  • Is there a reliable way to determine whether Thunderbolt Bus has been enabled? How can I see that in IOREG or is there another way to check that?
  • Is it only the firmware that decides about Thunderbolt Bus and can I rely on the SSDT being totally error-free and does not require additional modification?
Best wishes
-cuemaxx
For Alpine Ridge controllers we can try enabling Thunderbolt Bus with a SSDT. This may not yield the best results but it’s an alternative to flashing the firmware.

We have a compilation of these SSDTs and how to use them:

Please note however that it’s difficult to provide support for systems not listed there. The best solution by far is a GC-Titan Ridge so we encourage everyone to go that route.
 
It's already shared. Please see spoiler at the top of Post 1 labeled Quick Reference to Mini-Guides and Micro-Guides. In Section 1 of that you'll find a list of OpenCore releases.
Thanks for this. I have used this EFI folder but it has led to the ACPI error that @larrythedirtbag had listed out in his post. Trying to resolve that error and hoped he had made the right adjustment to his config.plist
 
Hello,

I'm having an issue trying to restore my main NVME drive from a backup I made a month ago. I'm running Big Sur.

I followed the steps in this mini guide for a Big Sur bootable backup last month and it worked great, as I am now running off that backup I made. I ran into a weird probably non-hackintosh related issue that made me want to revert to my backup. I took my USB SSD backup and connected it via SATA, erased my NVME drive and followed the same steps from the guide to clone my SSD to my NVME, but I can't seem to make the NVME bootable.

I've tried 2 versions of the EFIClone script, the first being EFIClone-v4 from here, the second being EFIClone from CaseySJ's github. I've tried it several times from both a failed clone and from a freshly erased drive, but there seems to be an issue with mounting the EFI.

When running `tail -f EFIClone.log`, I get `Mounting EFI source partition failed.` shown in the first image I've attached.

When running the script outside of CCC as instructed inside the script: `EFIClone.sh / /Volumes/Big\ Sur\ 2` I get the same error, shown in my second attachment.

I have set the test switch to off, I've made sure the CCC scripts folder is secured, I have changed basically no settings in the CCC task besides adding the script "postflight" and turning the safety net on/off, I've tried re-downloading the EFIClone script a few times just to make sure I didn't accidentally change something, and I've tried mounting the EFI of the source disk manually before running the task/script. Not really sure where to go from here. The only thing I can think of that I haven't tried is buying a new SSD and cloning to that in case the NVME drive is causing issues as a destination. I also haven't tried buying an NVME enclosure, just in case for some reason USB is required to do the clone.

Any ideas? Thanks :)
 

Attachments

  • tail.png
    tail.png
    43.7 KB · Views: 24
  • term.png
    term.png
    12 KB · Views: 17
Hello,

I'm having an issue trying to restore my main NVME drive from a backup I made a month ago. I'm running Big Sur.

I followed the steps in this mini guide for a Big Sur bootable backup last month and it worked great, as I am now running off that backup I made. I ran into a weird probably non-hackintosh related issue that made me want to revert to my backup. I took my USB SSD backup and connected it via SATA, erased my NVME drive and followed the same steps from the guide to clone my SSD to my NVME, but I can't seem to make the NVME bootable.

I've tried 2 versions of the EFIClone script, the first being EFIClone-v4 from here, the second being EFIClone from CaseySJ's github. I've tried it several times from both a failed clone and from a freshly erased drive, but there seems to be an issue with mounting the EFI.

When running `tail -f EFIClone.log`, I get `Mounting EFI source partition failed.` shown in the first image I've attached.

When running the script outside of CCC as instructed inside the script: `EFIClone.sh / /Volumes/Big\ Sur\ 2` I get the same error, shown in my second attachment.

I have set the test switch to off, I've made sure the CCC scripts folder is secured, I have changed basically no settings in the CCC task besides adding the script "postflight" and turning the safety net on/off, I've tried re-downloading the EFIClone script a few times just to make sure I didn't accidentally change something, and I've tried mounting the EFI of the source disk manually before running the task/script. Not really sure where to go from here. The only thing I can think of that I haven't tried is buying a new SSD and cloning to that in case the NVME drive is causing issues as a destination. I also haven't tried buying an NVME enclosure, just in case for some reason USB is required to do the clone.

Any ideas? Thanks :)
First of all, thank you for the clear description.

Some questions:
  • Are you able to mount the source EFI partition using EFI Agent, OpenCore Configurator, Hackintool, or any other app?
  • If so, does that partition contain a full EFI folder?
  • If so, one quick solution is to manually copy the EFI folder from source to destination.
 
First of all, thank you for the clear description.

Some questions:
  • Are you able to mount the source EFI partition using EFI Agent, OpenCore Configurator, Hackintool, or any other app?
  • If so, does that partition contain a full EFI folder?
  • If so, one quick solution is to manually copy the EFI folder from source to destination.

Thanks for the quick reply!

• Yes, I can mount the source EFI no problem with clover, opencore, hackintool, or EFI agent;
• The source drive appears to contain a full EFI folder. Here is the pastebin of 'tree -F' inside that folder, not sure if I'm missing anything, but at this point this is the only EFI partition in my PC that has anything in it, so that EFI folder does allow me to boot from the source:

./
├── EFI/
│ ├── BOOT/
│ │ └── BOOTx64.efi*
│ └── OC/
│ ├── ACPI/
│ │ ├── SSDT-DESIGNARE-Z390-NO-CNVW.aml*
│ │ ├── SSDT-DMAC.aml*
│ │ ├── SSDT-DMAR.aml*
│ │ ├── SSDT-DTPG.aml*
│ │ ├── SSDT-EC.aml*
│ │ ├── SSDT-NVRAM.aml*
│ │ ├── SSDT-PLUG.aml*
│ │ ├── SSDT-TB3-HackinDROM.aml*
│ │ ├── SSDT-UIAC-DESIGNARE-Z390-V7.aml*
│ │ ├── SSDT-USBW.aml*
│ │ └── SSDT-Z390-DESIGNARE-TB3HP-V4.aml*
│ ├── Drivers/
│ │ ├── AudioDxe.efi*
│ │ ├── CrScreenshotDxe.efi*
│ │ ├── HfsPlus.efi*
│ │ ├── OpenCanopy.efi*
│ │ ├── OpenLinuxBoot.efi*
│ │ ├── OpenRuntime.efi*
│ │ ├── OpenUsbKbDxe.efi*
│ │ ├── btrfs_x64.efi*
│ │ └── ext4_x64.efi*
│ ├── Kexts/
│ │ ├── AppleALC.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── AppleALC*
│ │ ├── BlueToolFixup.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── BlueToolFixup*
│ │ ├── BrcmFirmwareData.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── BrcmFirmwareData*
│ │ ├── BrcmPatchRAM3.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── BrcmPatchRAM3*
│ │ ├── BrightnessKeys.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── BrightnessKeys*
│ │ ├── CpuTscSync.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── CpuTscSync*
│ │ ├── IntelMausi.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── IntelMausi*
│ │ ├── Lilu.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── Lilu*
│ │ ├── NVMeFix.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── NVMeFix*
│ │ ├── RestrictEvents.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── RestrictEvents*
│ │ ├── SMCProcessor.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── SMCProcessor*
│ │ ├── SMCSuperIO.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── SMCSuperIO*
│ │ ├── SmallTree-Intel-211-82576.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ ├── MacOS/
│ │ │ │ └── SmallTreeIntel82576*
│ │ │ ├── Resources/
│ │ │ │ └── English.lproj/
│ │ │ │ └── InfoPlist.strings*
│ │ │ └── _CodeSignature/
│ │ │ └── CodeResources*
│ │ ├── USBInjectAll-071.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── USBInjectAll*
│ │ ├── USBInjectAll-076.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ ├── MacOS/
│ │ │ │ └── USBInjectAll*
│ │ │ └── _CodeSignature/
│ │ │ └── CodeResources*
│ │ ├── USBWakeFixup.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── USBWakeFixup*
│ │ ├── VirtualSMC.kext/
│ │ │ └── Contents/
│ │ │ ├── Info.plist*
│ │ │ └── MacOS/
│ │ │ └── VirtualSMC*
│ │ └── WhateverGreen.kext/
│ │ └── Contents/
│ │ ├── Info.plist*
│ │ └── MacOS/
│ │ └── WhateverGreen*
│ ├── OpenCore.efi*
│ ├── Resources/
│ │ ├── Audio/
│ │ │ ├── AXEFIAudio_Beep.mp3*
│ │ │ ├── AXEFIAudio_Click.mp3*
│ │ │ ├── AXEFIAudio_VoiceOver_Boot.mp3*
│ │ │ └── OCEFIAudio_VoiceOver_Boot.mp3*
│ │ ├── Font/
│ │ │ ├── Font_1x.bin*
│ │ │ ├── Font_1x.png*
│ │ │ ├── Font_2x.bin*
│ │ │ └── Font_2x.png*
│ │ ├── Image/
│ │ │ └── Acidanthera/
│ │ │ ├── Chardonnay/
│ │ │ │ ├── AppleRecv.icns*
│ │ │ │ ├── AppleTM.icns*
│ │ │ │ ├── BtnFocus.icns*
│ │ │ │ ├── Cursor.icns*
│ │ │ │ ├── Dot.icns*
│ │ │ │ ├── Enter.icns*
│ │ │ │ ├── ExtAppleRecv.icns*
│ │ │ │ ├── ExtAppleTM.icns*
│ │ │ │ ├── ExtHardDrive.icns*
│ │ │ │ ├── HardDrive.icns*
│ │ │ │ ├── Left.icns*
│ │ │ │ ├── Lock.icns*
│ │ │ │ ├── Password.icns*
│ │ │ │ ├── Restart.icns*
│ │ │ │ ├── Right.icns*
│ │ │ │ ├── Selected.icns*
│ │ │ │ ├── Selector.icns*
│ │ │ │ ├── SetDefault.icns*
│ │ │ │ ├── Shell.icns*
│ │ │ │ ├── ShutDown.icns*
│ │ │ │ ├── Tool.icns*
│ │ │ │ └── Windows.icns*
│ │ │ ├── GoldenGate/
│ │ │ │ ├── AppleRecv.icns*
│ │ │ │ ├── AppleTM.icns*
│ │ │ │ ├── BtnFocus.icns*
│ │ │ │ ├── Cursor.icns*
│ │ │ │ ├── Dot.icns*
│ │ │ │ ├── Enter.icns*
│ │ │ │ ├── ExtAppleRecv.icns*
│ │ │ │ ├── ExtAppleTM.icns*
│ │ │ │ ├── ExtHardDrive.icns*
│ │ │ │ ├── HardDrive.icns*
│ │ │ │ ├── Left.icns*
│ │ │ │ ├── Lock.icns*
│ │ │ │ ├── Password.icns*
│ │ │ │ ├── Restart.icns*
│ │ │ │ ├── Right.icns*
│ │ │ │ ├── Selected.icns*
│ │ │ │ ├── Selector.icns*
│ │ │ │ ├── SetDefault.icns*
│ │ │ │ ├── Shell.icns*
│ │ │ │ ├── ShutDown.icns*
│ │ │ │ ├── Tool.icns*
│ │ │ │ └── Windows.icns*
│ │ │ └── Syrah/
│ │ │ ├── AppleRecv.icns*
│ │ │ ├── AppleTM.icns*
│ │ │ ├── BtnFocus.icns*
│ │ │ ├── Cursor.icns*
│ │ │ ├── Dot.icns*
│ │ │ ├── Enter.icns*
│ │ │ ├── ExtAppleRecv.icns*
│ │ │ ├── ExtAppleTM.icns*
│ │ │ ├── ExtHardDrive.icns*
│ │ │ ├── HardDrive.icns*
│ │ │ ├── Left.icns*
│ │ │ ├── Lock.icns*
│ │ │ ├── Password.icns*
│ │ │ ├── Restart.icns*
│ │ │ ├── Right.icns*
│ │ │ ├── Selected.icns*
│ │ │ ├── Selector.icns*
│ │ │ ├── SetDefault.icns*
│ │ │ ├── Shell.icns*
│ │ │ ├── ShutDown.icns*
│ │ │ ├── Tool.icns*
│ │ │ └── Windows.icns*
│ │ └── Label/
│ │ ├── Apple.l2x*
│ │ ├── Apple.lbl*
│ │ ├── AppleRecv.l2x*
│ │ ├── AppleRecv.lbl*
│ │ ├── AppleTM.l2x*
│ │ ├── AppleTM.lbl*
│ │ ├── EFIBoot.l2x*
│ │ ├── EFIBoot.lbl*
│ │ ├── Other.l2x*
│ │ ├── Other.lbl*
│ │ ├── ResetNVRAM.l2x*
│ │ ├── ResetNVRAM.lbl*
│ │ ├── SIPDisabled.l2x*
│ │ ├── SIPDisabled.lbl*
│ │ ├── SIPEnabled.l2x*
│ │ ├── SIPEnabled.lbl*
│ │ ├── Shell.l2x*
│ │ ├── Shell.lbl*
│ │ ├── Tool.l2x*
│ │ ├── Tool.lbl*
│ │ ├── Windows.l2x*
│ │ └── Windows.lbl*
│ ├── Tools/
│ │ ├── BootKicker.efi*
│ │ ├── CFGLock.efi*
│ │ ├── ChipTune.efi*
│ │ ├── CleanNvram.efi*
│ │ ├── ControlMsrE2.efi*
│ │ ├── CsrUtil.efi*
│ │ ├── GopStop.efi*
│ │ ├── HdaCodecDump.efi*
│ │ ├── KeyTester.efi*
│ │ ├── MmapDump.efi*
│ │ ├── OpenControl.efi*
│ │ ├── OpenShell.efi*
│ │ ├── ResetSystem.efi*
│ │ ├── RtcRw.efi*
│ │ ├── TpmInfo.efi*
│ │ └── VerifyMsrE2.efi*
│ ├── config-AMD-GPU.plist*
│ └── config.plist*
└── tree2.txt*

74 directories, 176 files

• I just tried manually copying the whole EFI folder. It did show up in the bootloader as 'EFI', but when I try to boot from it I just get an endless black screen. Is there anything else I'd have to do besides manually copy it?
 
Last edited:
Hello everyone,

I just updated to opencore 083 utilizing HackinDROM and everything seems to work normally except a message at startup screen:

"OCS: No schema for LegacyEnable at 2 index, context <NVRAM>!"

My current OS Bigsur 11.7.1

I'm not sure what it is. Could you please advise? Thanks in advance!


UPD

I tried option Validate in oc 083 and the error message disappeared.
I'm not sure if it was the right move though. Just come across somebody's comments here suggesting that step.
So I checked the config.plist and could see that LegacyEnable entry has been removed.

Thank you!
 
Last edited:
@CueMaxX

Welcome to the forum, and thanks for the detailed post.

As you can see, Thunderbolt Bus is not getting activated on Asus EX-3. It is fully activated on GC-TR.

We always had a difficult time with the Asus EX-3. I even damaged mine after a botched firmware flashing attempt!

@NorthAmTransAm - do you have any recommendations for salvaging the Asus EX-3? I have always recommended GC-TR ever since damaging the Asus EX-3.
Hey old friend!

I have a feeling that that card mixed specifically with the ASUS Prime z370-a II and that single byte change in the firmware was a lucky combination. It was caveman math to figure all of that out and in the end I discovered that using SSDT's and patches to get a full Thunderbolt Bus was a more consistent method than patched firmware. The card also needed a header to work in any case.

As always, GC-Titan 2.0 is the way unless i've fallen behind. Its been such a busy year I might have missed something.
 
Back
Top