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

[hoeveler]

Damn. I checked and SIP was actually disabled. So I used openCore hackindrom app to change the code for that based on @CaseySJ original post to disable SIP. But now my system is throwing an error on the bios screen, and the Big Sur install won't boot past the Apple logo. Short of removing the boot m2 drive, mounting it on my other Mac, getting into the EFI partition that way and changing it back... Is there an easier way to undo my setting using the UEFI shell from the openCore boot selection screen?

 

[Middleman]

Damn. I checked and SIP was actually disabled. So I used openCore hackindrom app to change the code for that based on @CaseySJ original post to disable SIP. But now my system is throwing an error on the bios screen, and the Big Sur install won't boot past the Apple logo. Short of removing the boot m2 drive, mounting it on my other Mac, getting into the EFI partition that way and changing it back... Is there an easier way to undo my setting using the UEFI shell from the openCore boot selection screen?

Right. You could try to create a separate USB stick with the EFI and see if you could boot with that. What version of OC are you using?

 

[hoeveler]

Right. You could try to create a separate USB stick with the EFI and see if you could boot with that. What version of OC are you using?

OC 0.7.1
I popped the M2 out, put it into my M2>USB adaptor and used Hackindrom on my Macbook Air running Big Sur to reinstall OC 0.7.1 on the M2's EFI partition, but now it's got more problems with BIOS and secure boot I'll need to iron out.

EDIT 1: I went thru my BIOS settings to make sure they are correct. Other than the fact that I'm running F11 (I didn't realize/notice F10 was preferred, but I've been running F11 for a while without too much trouble), the settings are correct. I'm attaching a a pic of the error that shows up before the OC boot selection screen. It's several error lines about wrong dict value... and now Big Sur partition won't boot past the apple after several minutes.
@CaseySJ Is there any way I can access the EFI partition and edit the config from Windows so that I don't have to physically remove the M2 drive when this happens in the future?
Maybe I can try the M2 removal method again? Windows, running on the other M2 drive, is able to be selected and boots from the OC boot selector screen.

EDIT 2: I managed, using Windows and MiniTool Partition Tool plus Explorer++ to replace the EFI folder with the unzipped and renamed EFI zip for Vision D 0.7.1 in this thread. Now I'm back up and running, thanks!
I did find out after using those tools, that I can also edit via the UEFI console:

In the clover boot menu, you find an option: UEFI console.
(In this console you find the different available commands by issuing the command “Help” alternatively “Help -b” that breaks for every full screen.)
Normally your EFI boot partition will be fs0.
You make this filesystem the current by the command:
“fs0:”
To make the directory containing the config.plist the current directory you use the commands:
“cd EFI”
“cd clover”
To validate that you are in the right place you may list the files in this directory by issuing the command:
“ls”
which will list all files in the current directory.
Now to edit the config.plist-file use the following command:
“edit config.plist”
Make any necessarry alteration to the file and save with the F2-button and the exit the editor with F3-button.
Exit the UEFI-console with the command:
“Exit”.
The reboot your computer.

 

[MESwan]

feel like the lone wolf here, wish someone else had this board. I could try Catalina as well.

I picked this board up intending to upgrade from my 9900K + Designare to a 3950X and Vision D-P. I've run through all available BIOS for the D-P, including 10. Nothing so much as a peep from Thunderbolt itself, though my TBT docks are acting as USB 3 hubs. Hackintool correctly recognizes the docks (and even a 10GBe Thunderbolt 3 NIC) but Thunderbolt is never properly initialized.

@CaseySJ is there anything top of mind you think we should try here?

 

[hoeveler]

After Effects runs very well with just the patch.

Could someone point me to a guide for all these Adobe patches, etc. I keep reading things like "the patch" without a link to what we're talking about here. I have tried everything from the earlier automator method, to the Adobe 2021 AMD Patch.command to the process on this thread, but none of the patches are fixing anything for me the way they seem to be for others. Not a single one has worked, unfortunately, and there doesn't seem to be any definitive guide for this.
THANKS!

EDIT1: I finally got "The Italian Job" to work using these steps that are not mentioned anywhere so I thought I'd leave them here:
1. I disabled SIP from OpenCore configurator using 67000000 in the csr-active-config parameter, then reboot.
2. Because I had already been trying methods, I deleted those files mentioned in the above link (libfakeintel.dylib & environment.plist), then uninstalled Photoshop and AE from CC but chose to keep my settings, so I needed to delete the residual app while keeping my plugins folders, etc. then reboot.
4. Installed Photoshop. Then reboot.
5. NOW I had a clean slate to start with again. So I followed the Italian Job method again, placing those two files in the correct places, but didn't do the AE contents replacement yet. Then... reboot... again.
6. I opened Photoshop. First time, it stalled and needed to be force quit. Then I opened it again and it worked. Liquify works, neural filters work!

I tried fixing AE earlier, but it didn't fix it - probably will fix correctly if I follow my steps above, rebooting between steps. But AE has been working without any problems for me. Is it really just the camera tracker and warp stabilizer that don't work on AMD hackintosh? I have not needed to use those two features lately, and all my other plugins and such work, so why fix what isn't broken?... I might re-approach fixing AE later but my experience has been that the more I mess with the patches and fixes, the more unstable things can become. That said, so far The Italian Job method seems to be easiest.

 

[CaseySJ]

I picked this board up intending to upgrade from my 9900K + Designare to a 3950X and Vision D-P. I've run through all available BIOS for the D-P, including 10. Nothing so much as a peep from Thunderbolt itself, though my TBT docks are acting as USB 3 hubs. Hackintool correctly recognizes the docks (and even a 10GBe Thunderbolt 3 NIC) but Thunderbolt is never properly initialized.

@CaseySJ is there anything top of mind you think we should try here?

Unfortunately it seems that Gigabyte’s BIOS for the D-P board is causing all of these headaches. Short of a BIOS fix I’m not sure if there’s a solution.

I’ll put a warning at the top of Post 1 to avoid this board because of Thunderbolt problems in macOS.

 

[dehjomz]

WHat's the difference between the B550 Vision D-P and Vision D? Is it that the D-P is just a newer iteration?

 

[MESwan]

Unfortunately it seems that Gigabyte’s BIOS for the D-P board is causing all of these headaches. Short of a BIOS fix I’m not sure if there’s a solution.

I’ll put a warning at the top of Post 1 to avoid this board because of Thunderbolt problems in macOS.

I was expecting this answer, as much of a bummer as it is. As always, I certainly appreciate your ongoing efforts and incredible responsiveness.

WHat's the difference between the B550 Vision D-P and Vision D? Is it that the D-P is just a newer iteration?

D-P is a newer iteration with a USB-C header on board, and bum Thunderbolt 3 support for some unknown reason. For the most part, the rest of the board is functionally identical. Just enough in there to bork things

 

[dehjomz]

I was expecting this answer, as much of a bummer as it is. As always, I certainly appreciate your ongoing efforts and incredible responsiveness.

D-P is a newer iteration with a USB-C header on board, and bum Thunderbolt 3 support for some unknown reason. For the most part, the rest of the board is functionally identical. Just enough in there to bork things

Seems that Gigabyte has been having some trouble with either BIOSes or certain motherboard products released late 2020 to mid 2021.

Z490 f20 beta BIOSes were a complete disaster, z590 vision d had early BIOSes that were complete garbage. Now the latest beta BIOS fixed most of the issues but still doesn’t have Thunderbolt hot-plug ability in macOS (unless you first enter s3 sleep mode), now this with the B550 Vision D-P.

Quality control took a hit. Maybe the effects of the virus? Hopefully they sort it out soon or I’m going to abandon Gigabyte whenever I upgrade again.

 

[CaseySJ]

I was expecting this answer, as much of a bummer as it is. As always, I certainly appreciate your ongoing efforts and incredible responsiveness.
...

I was so looking forward to the B550 Vision D-P myself. It's a solid upgrade over the B550 Vision D, but alas the BIOS does not cooperate with us...