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

[CaseySJ]

Hi! Thanks for the excellent guide. Is there a Gigabyte 550 board that is identical, minus the Thunderbolt? Thanks

Hello @tdcam,

Ryzen motherboards are a little more difficult to configure for macOS due to multiple USB controllers, the need for kernel patches, etc. Although there are several good Gigabyte B550 motherboards, perhaps a close cousin of the B550 Vision D would be the B550 AORUS PRO AX (click here for link) for US$170 on Amazon. Some EFI changes will be required to address the following differences:

• No Thunderbolt (just need to disable the Thunderbolt SSDT)
• 2.5GbE Ethernet (if it uses Intel i225-V controller, we will need to add FakePCIID kexts like we do for Z490 Vision D)
• USB Ports (some changes to USB port mapping is needed)

 

[Gigamaxx]

Hello @tdcam,

Ryzen motherboards are a little more difficult to configure for macOS due to multiple USB controllers, the need for kernel patches, etc. Although there are several good Gigabyte B550 motherboards, perhaps a close cousin of the B550 Vision D would be the B550 AORUS PRO AX (click here for link) for US$170 on Amazon. Some EFI changes will be required to address the following differences:

• No Thunderbolt (just need to disable the Thunderbolt SSDT)
• 2.5GbE Ethernet (if it uses Intel i225-V controller, we will need to add FakePCIID kexts like we do for Z490 Vision D)
• USB Ports (some changes to USB port mapping is needed)

I have the Pro AC it has killer 2.5 Ethernet, Lucy kext.
It also has a Thunderbolt header on the motherboard so a PCI card should work. BIOS lists the Thunderbolt header.

 

[RyanC]

The latest patches have fixed and caused the audio stuttering. The last few patches for fixPAT are duplicated. One is from Algrey, the other from Shaneee. It is advised to disable one of the patches. Test to see which one gives the best result.

Ok cool. Is it verified by any user that it's working for TB3 audio for DAW/low-latency use?

 

[Gigamaxx]

Ok cool. Is it verified by any user that it's working for TB3 audio for DAW/low-latency use?

I don’t have either but @CaseySJ may know? Probably a good idea to get ALCkext working first then test.

 

[CaseySJ]

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

Requires OpenCore Configurator 2.22.0.0 or Newer

​

The formal release of OpenCore 0.6.5 has arrived, along with an update of WhateverGreen, AppleALC, and NVMeFix.

This EFI contains the following changes:

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

• OpenCore 0.6.5
• WhateverGreen 1.4.6
• AppleALC 1.5.6
• NVMeFix 1.0.5

config.plist Changes:

• Misc --> Security --> SecureBootModel --> Disabled (change to Default for OpenIntelWireless)
• Contains latest AMD-OSX kernel patches for 17H processor family

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-065-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.5 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.

 

[vana.nz]

Thanks for the update CaseySJ.
Unfortunately, when I boot from this 065 EFI my TB bus fails to initiate from a cold boot, or from an hot-plug.
Moreover, when I then boot from the 064 EFI internal SSD, the result is the same - no TB connection. I need to boot to Windows which does initialize the TB bus, after which the TB connection is re-established on booting Big Sur.
(BTW I am looking at my legacy Sapphire Pro Firewire connection led to tell me if the TB bus has initialized.)

Two questions while I am here:
1. Does flashing the TB chip change its behavior in Windows, and
2. Is it wise to update Big Sur via the built in software update service?

Many thanks
Ivan

 

[Ploddles]

Thanks for the update CaseySJ.
Unfortunately, when I boot from this 065 EFI my TB bus fails to initiate from a cold boot, or from an hot-plug.
Moreover, when I then boot from the 064 EFI internal SSD, the result is the same - no TB connection. I need to boot to Windows which does initialize the TB bus, after which the TB connection is re-established on booting Big Sur.
(BTW I am looking at my legacy Sapphire Pro Firewire connection led to tell me if the TB bus has initialized.)

Two questions while I am here:
1. Does flashing the TB chip change its behavior in Windows, and
2. Is it wise to update Big Sur via the built in software update service?

Many thanks
Ivan

If you flash the TB controller then it may or may not work in Windows. It depends on what you are connecting to it.

Yes, just use the built in software updater but make sure you have a full bootable backup before you do the update.

 

[CaseySJ]

Thanks for the update CaseySJ.
Unfortunately, when I boot from this 065 EFI my TB bus fails to initiate from a cold boot, or from an hot-plug.
Moreover, when I then boot from the 064 EFI internal SSD, the result is the same - no TB connection. I need to boot to Windows which does initialize the TB bus, after which the TB connection is re-established on booting Big Sur.
(BTW I am looking at my legacy Sapphire Pro Firewire connection led to tell me if the TB bus has initialized.)

Two questions while I am here:
1. Does flashing the TB chip change its behavior in Windows, and
2. Is it wise to update Big Sur via the built in software update service?

Many thanks
Ivan

Hello Ivan,

Welcome to the forum. Please see the table below (from Post 1). If you've flashed the Thunderbolt firmware based on NVM 33 (the last column below) then Thunderbolt Bus and connected devices should work on Power On (both cold power on and warm power on). But as highlighted in the red box, it won't work after a "Reboot" from within macOS.

Behavior in Windows is unpredictable. Some devices will work and others won't. We have placed warnings to this effect in various Thunderbolt flashing posts.

 

[anthera93]

Hello community!

Anybody having problems with FireWire? I have a FW card with VIA chip on it, it used to work on my last MOBO i had, but no luck on Catalina. Today i got this interface but no luck still. https://www.amazon.de/gp/product/B000WCT5HK/?tag=tonymacx8603-21

Also I can't connect UAD Apollo Firewire with Thunderbolt 2 via Apple TB3-TB adapter (on windows as well, FW on windows works like a charm)


OC 0.6.5
Catalina 10.15.7

Thanks in advance!
my ioreg is in attachements

 

[xtreem.p]

You should look into selling all Firewire, UAD seems to be leaving Firewire and it seems that Big Sur dropped support for Firewire.

You should look over UAD forum thread for more info.

Oh, Firewire UA products are incompatible with Big Sur!!

Just read that in the notes. So, EOL for my Satellite Quad FW. What should I do with it? Recycle? Big Sur will have to wait over here... Blink

uadforum.com