Gigabyte B550 Vision D (Thunderbolt 3) + AMD Ryzen 7 3700X + AMD RX 5600 XT

[CaseySJ]

** OpenCore 0.6.6 EFI for B550 Vision D **
Please do not quote this post in its entirely. Use a link instead.

Requires OpenCore Configurator 2.27.0.0 or Newer.

URGENT: Set OpenCore Configurator "Preferences" to OpenCore 0.6.6 Release Version

​

The formal release of OpenCore 0.6.6 has arrived, along with an update of Lilu, WhateverGreen, AppleALC, BrcmPatchRAM, and VirtualSMC.

This EFI contains the following changes:

Bootloader / Kexts:
All of the items listed below are official builds.

• OpenCore 0.6.6
• Lilu 1.5.1
• WhateverGreen 1.4.7
• AppleALC 1.5.7
• VirtualSMC 1.2.0
• BrcmBluetoothInjector 2.5.6
• BrcmFirmwareData 2.5.6
• BrcmPatchRAM3 2.5.6
• New and updated OpenCore "Resources" files (images, icons, audio, fonts) required by latest OpenCanopy
• All SSDTs are now wrapped inside if (_OSI ("Darwin")) blocks so that they don't interfere with Windows or Linux.

config.plist Changes:

• Misc --> Security --> SecureBootModel --> Disabled (change to Default for OpenIntelWireless)
• Misc --> Security --> BlackListAppleUpdate --> Enabled
• Misc --> Boot --> PollAppleHotKeys --> Enabled (allows Verbose mode to be enabled by pressing CMD-V at Picker)
• Misc --> Boot --> PickerAttributes --> 0x25 (allows mouse control in Picker)
• Misc --> Boot --> BootProtect --> This feature has been replaced by LauncherOption, which has been set to Full
• UEFI --> Drivers --> HfsPlus.efi replaced with OpenHfsPlus.efi <-- 4 Feb 2021: Reverted back to HfsPlus.efi because of serious problem found in OpenHfsPlus.efi

How to Use:

1. Find a USB flash disk with an EFI partition, or format the USB flash disk in Disk Utility with Scheme = GUID Partition Map and Format = MacOS Extended (Journaled).
2. Mount EFI partition of the USB flash disk.
3. Download the attached ZIP into the top level of the EFI partition of the USB flash disk. When the file is unzipped, there will be a folder called EFI-066-B550-VISION-D.
4. Rename this folder to EFI, otherwise the system will not boot.
5. Use HackinDROM to transfer PlatformInfo from existing OpenCore config.plist to new version. Please follow the guide by clicking here and referring to the screenshot below.

​

After the modified config.plist has been copied to the EFI/OC folder of the USB flash disk, proceed as follows:

1. Reboot and press F12 at the BIOS Splash Screen. When the BIOS Boot Menu (not OpenCore Picker) appears, select the USB flash disk.
2. At the OpenCore 0.6.6 Picker menu, select and boot the internal macOS disk.
3. If everything works correctly, copy the new OpenCore EFI folder from the USB flash disk to the EFI partition of the main macOS SSD.

CAUTION:

• If you are using a custom Thunderbolt SSDT or any other custom SSDTs or Kexts, please update your config.plist accordingly.

UPDATES:

• 06-Feb-2021: Modified the OpenCore 0.6.6 EFI with latest AMD-OSX kernel patches that support macOS 11.3.

 

[CaseySJ]

Greetings @CaseySJ ,

Just wanted to share that based on your good experience, I selected a Ryzentosh using X570 Taichi motherboard, as i had already built a Gigabyte system (Z390 Designare).

It's been a couple of weeks, and I must say it runs rock solid, with best power-management than any build i'd done. I am using fan cpu-cooler.

I am running Big Sur (latest RC ver. & patches), sleep/wakeup are so smooth.
Upon tapping kbd to wake, if i don't re-enter session, it will go back to sleep shortly like a *real* Mac!
BTW, AMD Power Gadget is a lot more useful than the Intel counterpart.

Sincere thanks to the comprehensive write-up
I share your passion for building a complete build (w/ Thunderbolt).
My first 2 PC builds, going back 20+ yrs, with Pentium II, and four were on boards with built-in SCSI ports. The precursor to Thunderbolt.
It was state-of-the-art back then which was a standard feature on high-end commercial Unix systems.

cheers

If sleep is working on your ASRock X570 Taichi, then you have piqued my interest...

Attached is the OpenCore 0.6.6 EFI folder from my own X570 Taichi, but with serial numbers removed. You're welcome to try this (with your serial numbers in PlatformInfo --> DataHub) to see if sleep/wake works.

I can do the same with your EFI folder.

 

[Draft]

@CaseySJ

I try to test installation with new BIOS B550 Vision D F13a (Update AMD AGESA ComboV2 1.2.0.0) but installation block during first loading USB flash disk with OpenCore 0.6.6 installer. Any idea? Thanks for your help.

 

[CaseySJ]

@CaseySJ

I try to test installation with new BIOS B550 Vision D F13a (Update AMD AGESA ComboV2 1.2.0.0) but installation block during first loading USB flash disk with OpenCore 0.6.6 installer. Any idea? Thanks for your help.

Hello @Draft,

In BIOS F13a please check the setting for Resizeable BAR (base address register) and disable it.

Also note that other users experienced problems with these newer firmware files and promptly went back to F10. So for the purposes of macOS installation, it might be a good idea to try F10 first, get macOS installed and working, and then see what happens with newer BIOS versions.

 

[centraljava]

If sleep is working on your ASRock X570 Taichi, then you have piqued my interest...

Attached is the OpenCore 0.6.6 EFI folder from my own X570 Taichi, but with serial numbers removed. You're welcome to try this (with your serial numbers in PlatformInfo --> DataHub) to see if sleep/wake works.

I can do the same with your EFI folder.

It's been a couple of weeks, and I must say it runs rock solid, with best power-management than any build I've done. I am using fan CPU cooler.

If sleep is working on your ASRock X570 Taichi, then you have piqued my interest...

Attached is the OpenCore 0.6.6 EFI folder from my own X570 Taichi, but with serial numbers removed. You're welcome to try this (with your serial numbers in PlatformInfo --> DataHub) to see if sleep/wake works.

I can do the same with your EFI folder.

Hi @CaseySJ, I adopted a publicly shared EFI (still verifying which one, tried quite a number).
But do give me some time.
Since I am putting system thru its paces to see how long it can stay up without reboot/crashing.
I am putting it to sleep as often as I can, even while stepping away for an egg roll snack, or bathroom breaks.
Just to see how robust it is.
Would love to give a hand at right time, perhaps taking it to another thread.

 

[Draft]

Hello @Draft,

In BIOS F13a please check the setting for Resizeable BAR (base address register) and disable it.

Also note that other users experienced problems with these newer firmware files and promptly went back to F10. So for the purposes of macOS installation, it might be a good idea to try F10 first, get macOS installed and working, and then see what happens with newer BIOS versions.

Thanks Casey,

I downgrade to F12 BIOS (2‎021/01/18) and everything working fine with Big Sur.
Original Bluetooth is OK.
Thunderbolt works only after fresh start (not reboot).
I have a dual boot with Windows 10 (separated NVMe).
I compare benchmark over Geekbench 5 and actually Windows score is better.
Did you test another SMBIOS than iMacPro1,1 to perform ?

And I hesitate to flash Thunderbolt because I need full functionality over Windows and macOS.
Is it very dangerous to flash it ? What is the consequences under Windows or Linux after this flash ?

Many thanks for your work! And your help

 

[sadeuko]

Hi,
There is a "breakthrough" on finding what could go wrong with my rig. To remind you, screen was going black in the middle of loading the OS. Usually, when it everything was going smooth the screen indeed went black (monitor turned off, fans on GPU stopped) but after few second my monitor would power up again, and i was greeted with login screen.

PS. It was connected via DVI to my Sapphire RX570 4GB, the blue one

Today it happened again. But, instead of going bananas, I hooked up an old LG screen, hooked up via DVI, and it works. While being blessed of finally seeing login screen, I've disconnected the LG monitor and hooked up the main one, and it didn't power up so what the hell ?!?!... Refresh rate, resolution glitch or just buy a monitor with Display Port and ditch this dead by now DVI interface.

@CaseySJ and rest of you dear folks, any of you stumbled upon issue like this ? And how crucial is proper naming your graphics card in OC as I'm still rocking the original EFI provided by Casey. Tbh at this point I'm so afraid of changing anything with my low skills/morals as i have some important projects on this rig.

So yeah, I'm still holding my breath while the OS is loading and my heart stops when there's a hiccup or some glitch.

Thanks for your time going thru my post, and any help on this one as I won't give up on this!

 

[CaseySJ]

Thanks Casey,

I downgrade to F12 BIOS (2‎021/01/18) and everything working fine with Big Sur.
Original Bluetooth is OK.
Thunderbolt works only after fresh start (not reboot).
I have a dual boot with Windows 10 (separated NVMe).
I compare benchmark over Geekbench 5 and actually Windows score is better.
Did you test another SMBIOS than iMacPro1,1 to perform ?

I would not worry about Geekbench differences between Mac and Windows. GPU performance under Windows will be faster due to AMD's optimized drivers.

Bottom line: If the applications you use in macOS are fast and doing the job in good time, then what's to worry?

And I hesitate to flash Thunderbolt because I need full functionality over Windows and macOS.
Is it very dangerous to flash it ? What is the consequences under Windows or Linux after this flash ?

Many thanks for your work! And your help

Thunderbolt firmware should not be flashed unless you have a Thunderbolt device that simply does not work with the standard firmware.

Once the firmware is flashed, Windows and Linux may not be able to work properly. What exactly does this mean? It depends on the device you use, but in general many or most Thunderbolt devices may not work reliably.

 

[CaseySJ]

... or just buy a monitor with Display Port and ditch this dead by now DVI interface.

Oh, you've struck a chord with this statement! Such a musically delicious chord. Yes ditch the dead DVI and walk through the door marked "21st Century".

@CaseySJ and rest of you dear folks, any of you stumbled upon issue like this ? And how crucial is proper naming your graphics card in OC as i'm still rocking the original EFI provided by Casey. Tbh at this point i'm so afraid of changing anything with my low skills/morals as i have some important projects on this rig.

So yeah, i'm still holding my breath while the OS is loading and my heart stops when there's a hickup or some glitch.

Thanks for your time going thru my post and any help on this one as i won't give up on this !

Naming the graphics card is purely informational and does not affect system performance. The OpenCore config.plist from this thread uses the name AMD R9 380X. I should change that to something like "TYPE YOUR NAME HERE".

You can safely change the following two items:

 

[sadeuko]

Well, so the DVI is faulty, could introduce glitches/crashes that I've mentioned and have bad reputation in Hackintosh community...this would be so simple ?

In my humble experience I've never came across this issue on forums + it was so random, happened without any particular event happening while working on it, before those major crashes (no gaming, video rendering, heavy GPU workload).

That's why I was sometimes nervous working on it as it could just freeze and so i had to reset it (could live with that) but recently even freeze/black screen could mean going bananas and writing emails "...sorry i need extra day to finish this project"

Thanks @CaseySJ for helping hand on this one.