Contribute
Register

Gigabyte X299X - Catalina Support

Joined
Aug 6, 2013
Messages
44
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10900X
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
Just FYI - setting ConnectDrivers=false under 0.6.6 fails validation.
My configuration is different though. I suppose it'll only work if no drivers are loaded in /UEFI/Drivers, unless something changed in OC from 0.6.6 to 0.6.7
On the other hand, I load OpenRuntime.efi as a driver, to speed up boot process.
Set ConnectDrivers to false. That's it. :)

I've only tested it a couple of times, and only in the latest OpenCore 0.6.8. But I've booted from both USB and SSD using this change, and it boots absolutely fine with normal BIOS settings. No reset after 10 seconds, no safe mode.
 
Joined
Sep 8, 2010
Messages
235
Motherboard
Gigabyte X299X-Designare-10G
CPU
i9-10980XE
Graphics
Radeon Pro WX 7100
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
All good news, I have almost all the components, just the CPU and RAM :D
 
Joined
Mar 28, 2019
Messages
121
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
Some good news from me as well:
- The ConnectDrivers thing seems to work on my end, too, haven't encountered the previous issues thus far. Fingers crossed.
- I finally got around to mapping my USB ports properly, which resolved most of my USB issues. I used Hackintool for this, which made the process very simple.
 
Joined
Mar 6, 2013
Messages
274
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
AMD 6900XT
Mobile Phone
  1. Android
Just FYI - setting ConnectDrivers=false under 0.6.6 fails validation.
My configuration is different though. I suppose it'll only work if no drivers are loaded in /UEFI/Drivers, unless something changed in OC from 0.6.6 to 0.6.7
On the other hand, I load OpenRuntime.efi as a driver, to speed up boot process.
Yes, true:
Code:
HFS+ filesystem driver is loaded at UEFI->Drivers[1], but UEFI->ConnectDrivers is not enabled!

I have three drivers loaded via UEFI -> Drivers:
  • HFSPlus.efi - for loading HFS filesystems, eg DMG Recovery images
  • OpenRuntime - vital for many UEFI related tasks
  • OpenCanopy - the OC GUI
The OpenCore logs claims that all are loading fine:

Code:
00:293 00:001 OCABC: Awaiting rendezvous with OpenRuntime r12
00:299 00:001 OC: Driver OpenRuntime.efi at 0 is being loaded...
00:305 00:003 OCABC: Got rendezvous with OpenRuntime r12
00:309 00:001 OC: Driver OpenRuntime.efi at 0 is successfully loaded!
00:310 00:001 OC: Driver HfsPlus.efi at 1 is being loaded...
00:315 00:002 OC: Driver HfsPlus.efi at 1 is successfully loaded!
00:316 00:001 OC: Driver OpenCanopy.efi at 2 is being loaded...
00:327 00:001 OC: Driver OpenCanopy.efi at 2 is successfully loaded!

However I just checked my EFI logs from before I set ConnectDrivers=false, and I see there's an extra log line in those related to HfsPlus:
Code:
00:302 00:001 OC: Driver HfsPlus.efi at 1 needs connection.

So yes, as ocvalidate says, HfsPlus.efi can't load with ConnectDrivers=false, which is why "Install macOS Big Sur" can't be found: that's an HFS+ filesystem. Whereas the main OS Recovery can be loaded, because that comes from the APFS Recovery partition, and APFS support is built-in to OC.

Fortunately our system doesn't need any other UEFI drivers, but yes it is a bit of an annoyance not to be able to load HFS+ support for when it's occasionally required.

I looked through the OC code and confirmed that ConnectDrivers=false disables the code that JTR had to patch in order to fix the problem (Library/OcDriverConnectionLib/OcDriverConnectionLib.c), so it's obvious in hindsight that ConnectDrivers=false would also resolve the problem (albeit with a downside) if the system remained bootable, which fortunately it does.

- I finally got around to mapping my USB ports properly, which resolved most of my USB issues. I used Hackintool for this, which made the process very simple.
Glad you got it working finally. You could have used the USBMap.kext I included in my 0.6.7 EFI a month or so ago, but yes it's better to know how to do it oneself as well :) (Personally I prefer USBMapper to Hackintool though.)
 
Joined
Mar 28, 2019
Messages
121
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
I had a different SMBIOS, which I believe prevents that from being an option IIRC. I also had less ports active which I actually needed. I did try yours, but it didn't help with my particular situation, so I figured I'd bite the bullet and attempt my own version, which did eventually lead to a good result. Either way, thanks for all the hard work you've put into this already!
 
Joined
Sep 8, 2010
Messages
235
Motherboard
Gigabyte X299X-Designare-10G
CPU
i9-10980XE
Graphics
Radeon Pro WX 7100
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
only thing I now need to complete the system: the CPU xD
 
Joined
Nov 22, 2010
Messages
51
Motherboard
Gigabite X299X DESIGNARE 10G
CPU
i9-10940X
Graphics
Gigabyte RX5700XT
Mac
  1. Mac Pro
Mobile Phone
  1. iOS
Anyone know how to control the fan? I already set the the fan in bio to 'Silent' but when I do even just some simple graphic and iStats only show cpu just around 40 degree, but the fan run so loud, some say this board is noisy is that true?
 
Joined
Sep 8, 2010
Messages
235
Motherboard
Gigabyte X299X-Designare-10G
CPU
i9-10980XE
Graphics
Radeon Pro WX 7100
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
@TheBloke what are you’re bios settings?

got the CPU, so I can finish the system finally
 
Joined
Sep 8, 2010
Messages
235
Motherboard
Gigabyte X299X-Designare-10G
CPU
i9-10980XE
Graphics
Radeon Pro WX 7100
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
I'm getting 'System Clock Problem' errors.
I guess that's RTC problem?

What's the fix for it ?
 
Joined
Sep 8, 2010
Messages
235
Motherboard
Gigabyte X299X-Designare-10G
CPU
i9-10980XE
Graphics
Radeon Pro WX 7100
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac mini
Mobile Phone
  1. iOS
Never mind, that I fixed.

But here comes the Thunderbolt issue.
So I'm using an Avid HDX Card in a Sonnet Echo III Chassis,
this is the new version with an internal switch specific for HDX.

What I'm having of issues with the old system system, that if an SSDT for Hotplug is enabled,
the drivers can't see the card.
But when disabling the SSDT the drivers see the card.

So for some reason the SSDT is making issues.

Is there someone who can help me out...
 
Top