Gigabyte X299X - Catalina Support

[Dogman]

hey @dolgarrenan

Thank you for your answer!
Let me provide some more information: I never used clover on this system. I've got one USB stick with your EFI and one with a fresh OC 0.5.9.
I added the compiled RTC0 to ACPI and config.plist
I enabled Above4G Decoding in BIOS
I enabled IncreasePciBarSize in config.plist
I tested the unmodified SSDT-X299X-DESIGNARE10G-THUNDERBOLT-SIMPLIFIED.aml
I cleaned the NVRAM
But still the same error:
IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Resistry (0xe00002be)

But I retried your EFI again and it boots. Unfortunately, my Radeon VII has a black screen or the system crashes as soon as the graphics should start :/
What else did you change to get Thunderbolt working?

EDIT:
I checked the logs with your EFI folder and that
IOThunderboltEEPROM::parseDROMData - Failed CRC8 Verification: 0xb != 0xd6 IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Resistry (0xe0000001)

EDIT2:
Do you have these annoying "BIOS crashes" while BIOS boot up or in OpenCore selection that leads to the "Boot Failure detected" -> "Load Optimized Defaults then boot", "Load Optimized Defaults then reboot" and "Enter BIOS"? Do you know how to solve this? Firmware is F3B with your settings.

 

[mark.ritchie]

G'day All, and special thanks to @dolgarrenan for this awesome and very informative writeup....

working away to get this build working also, seems to be running quite well though after flashing the modified thunderbolt firmware I've also lost DisplayPort encapsulation.

I've the Gigabyte X299X motherboard with a Radeon VII. prior to flashing I had the monitor plugged into the motherboard TB3.

Post flashing. I no longer have an image, though macOS does detect the USB devices connected to the monitors USB C output. (Speakers, iSight camera, mouse, keyboard etc are all functioning)

any hints in order to reactivate this lost feature?

 

[Aarongorga]

I don't know if you have two separate 970 EVO or it's just a replica of the same device, but that itself is a problem. Having Windows (unless you are on 0.5.8 n-d-k fork), you won't be able to boot any drive and you will get the error that you are being presented with.

Remove the Windows 10 drive, do a clean BIOS setup (CMOS) and try to boot from the 970 (if there is an EFI inside, or if you have a USB drive with the EFI then it might be just a little tricky if there is any trace of a boot in the main drive), if everything boots fine, then you will have make a OC 0.5.8 n-d-k fork EFI for your system for dual boot.

Reason is because the n-d-k fork has a special quirk to prevent ACPI tables or configuration overall to be loaded onto Windows boot (you don't want to load an SSDT changing IDs and stuff to Windows), that's why you couldn't boot Windows from OC in the first place.

That is the only solution I have found for dual booting on a GB X299X Designare 10G, or for booting anything else. Hope this helps.

I also had Windows on a NVMe and could not get the installer to launch. It would, but would restart after a few seconds.
I pulled the Windows drive, did a CMOS reset botted to the USB stick, but still just resets after 5 seconds.

I am not sure if I am missing some fundamental thing here, I've read through the guides, and several threads. I think I have a handle on the basics, but I still can't get past step one and it's driving me nuts.

Any suggestions would be appreciated.

Thanks

 

[dolgarrenan]

Everything related to BIOS corruption/reset/french language and what not, is mostly due to:

• Bad BIOS config.
  • Go through the painful process of configuring your BIOS.
• Dual boot detected while trying to use OC or clover.
  • Try to remove any other boot device, e.g. USB with bootloader, other drives with Linux, windows or whatever else is there. The important part is to not try to boot with other bootloaders attached to your system.
• Unsupported or non configured devices.
  • A PCI device might be giving you trouble to boot, check log.
• BIOS rev 3c, known to be buggy, I had to revert to 3b to get it stable again.
  • I attached the 3b in the first post if I recall.
• Switching from Clover to OC back and forth.
  • Every time you do that, you should also perform a CMOS and configure BIOS again, seriously, it can mess with your boot.

This sums up the issues we should try to avoid. For those of us with a multi boot I would recommend using n-d-k's fork of OC which currently sits at 0.5.8 since it has an option to block ACPI tables from loading on different partitions (which is what is happening every time you try to load e.g windows, from OC boot screen and fails), unless the main fork has added the feature embedded in and I'm not aware .

 

[dolgarrenan]

But I retried your EFI again and it boots. Unfortunately, my Radeon VII has a black screen or the system crashes as soon as the graphics should start :/
What else did you change to get Thunderbolt working?

EDIT:
I checked the logs with your EFI folder and that
IOThunderboltEEPROM::parseDROMData - Failed CRC8 Verification: 0xb != 0xd6 IOThunderboltEEPROM::getDROM - Error getting DROM from I/O Resistry (0xe0000001)

EDIT2:
Do you have these annoying "BIOS crashes" while BIOS boot up or in OpenCore selection that leads to the "Boot Failure detected" -> "Load Optimized Defaults then boot", "Load Optimized Defaults then reboot" and "Enter BIOS"? Do you know how to solve this? Firmware is F3B with your settings.

Have you followed @CaseySJ guide on thunderbolt DROM..? Might have missed something, I get no such errors at boot.
I certainly did have problems in the beginning, check previous post, it sums the issues as best I could

I've the Gigabyte X299X motherboard with a Radeon VII. prior to flashing I had the monitor plugged into the motherboard TB3.

Post flashing. I no longer have an image, though macOS does detect the USB devices connected to the monitors USB C output. (Speakers, iSight camera, mouse, keyboard etc are all functioning)

any hints in order to reactivate this lost feature?

What firmware have you used? Did you follow the CRC8 guide to the point? Perhaps you could try to change some BIOS settings and try on cold boot.. Take a pic of your TB settings in BIOS and post here.

I also had Windows on a NVMe and could not get the installer to launch. It would, but would restart after a few seconds.
I pulled the Windows drive, did a CMOS reset botted to the USB stick, but still just resets after 5 seconds.

I am not sure if I am missing some fundamental thing here, I've read through the guides, and several threads. I think I have a handle on the basics, but I still can't get past step one and it's driving me nuts.

Any suggestions would be appreciated.

Thanks

With two drives with bootloader, or even a USB drive, be it windows or any other OS you will get issues unless using n-d-k's fork of OC.

It is a requirement to boot only with one bootloader drive attached with this damn BIOS, I can't stress this enough.

 

[Dogman]

Hey @dolgarrenan!

Thank you for you explanation! For me, the BIOS corruption/reset/French happens, when I open the Boot Menu by pressing F12 (or F10? I forgot) to boot from my backup boot stick. I can select the OC entry but then the system reboots and I get the message. But if just boot my internal drive, everything works like a charm. Until I made a mistake and need to reboot by my Thumb drive again

As you can see, I managed to boot properly. My SSDT-AWAC.aml need to be altered. In fact, my _SB.PCI0 firmware entries are called _SB.PC00. Crazy, since we both use the Gigabyte X299X Designare 10G with BIOS version F3b and a i9-10900X.

One question: Does sleep and wakeup work for you? Going to sleep works for me, but when I wakeup to system, it kind of freezes: Fans go on and my mouse leds turn on and after a few seconds turn off again. The screen stays dark all the time. darkwake=0 is in my boot entry. Any other ideas?

Cheers
Dogman

 

[dolgarrenan]

Thank you for you explanation! For me, the BIOS corruption/reset/French happens, when I open the Boot Menu by pressing F12 (or F10? I forgot) to boot from my backup boot stick. I can select the OC entry but then the system reboots and I get the message. But if just boot my internal drive, everything works like a charm. Until I made a mistake and need to reboot by my Thumb drive again

And that is why you have the BIOS error, two bootloaders. I'm gonna give you a little tip, if you have another Apple OS computer, then you should remove your EFI from your main drive on your X299X build (completely delete what's inside your EFI folder, not the partition itself. To check everything has been deleted, do 'shift'+'command'+'.' at the same time, then you should be able to see invisible files, delete everything except trash folder -you won't be able to- and empty the bin, use the same key press to hide invisible files again) and move it to a USB drive, then make all the necessary changes inside the USB EFI folder, so that you can easily try configurations without having to unplug stuff from your mobo every time you make a bad config.

As you can see, I managed to boot properly. My SSDT-AWAC.aml need to be altered. In fact, my _SB.PCI0 firmware entries are called _SB.PC00. Crazy, since we both use the Gigabyte X299X Designare 10G with BIOS version F3b and a i9-10900X.

I believe you might have missed the renaming part of the .plist. Under ACPI (in your .plist) there should be a section called "Patch", there you should rename PC00 to PCI0, you should use a text to hex editor to get the values you need, there should be enough info around to get you going. An example below.

One question: Does sleep and wakeup work for you? Going to sleep works for me, but when I wakeup to system, it kind of freezes: Fans go on and my mouse leds turn on and after a few seconds turn off again. The screen stays dark all the time. darkwake=0 is in my boot entry. Any other ideas?

Sleep works for me, sleep is very related to USB, or even Thunderbolt (since thunderbolt also uses a USB bus), so I would start looking at the way you are approaching your USB functionality, kext, patches, SSDT tables loading with wrong device rename etc..

 

[mark.ritchie]

@dolgarrenan I don't suppose you still have a copy of the original thunderbolt firmware from the X299X motherboard rather than the TB3 AIC....

I'd like to flash my board back to original, but I downgraded my laptop back to 10.15 and lost the original firmware I had saved.

 

[dolgarrenan]

@dolgarrenan I don't suppose you still have a copy of the original thunderbolt firmware from the X299X motherboard rather than the TB3 AIC....

I'd like to flash my board back to original, but I downgraded my laptop back to 10.15 and lost the original firmware I had saved.

There you go

 

[mark.ritchie]

Many many thanks! I'll definitely keep an eye on this as in the future I'd like to revert back to those thunderbolt mods.. though at this point in time I've a TB3 monitor. see what unfolds in the near future.

in the mean time, I've bought the base model Mac Pro 7,1...
geez that 580x sucks... such a compromise.. I'll keep hackintoshing too though.