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

CaseySJ said:

It should still operate in Windows, but hot plug may not work as well. The nice thing is we can always flash the original firmware back if necessary.

Click to expand...

As you said, I lost the hot plug function on Windows. The only way I have to make it work on windows again is boot first on OSX. Then reboot to Windows directly. The same thing I used to do before to make it work on OSX: start first Windows, and then reboot. Maybe it's possible to fix this hot plug problem on Windows with BootCamp driver?

Hot plug in macOS can be achieved with a SSDT. The custom firmware is for activating the Thunderbolt bus, to have Thunderbolt networking or plugging a DAS. What's your use case for Thunderbolt in macOS and Windows?

etorix said:

Hot plug in macOS can be achieved with a SSDT. The custom firmware is for activating the Thunderbolt bus, to have Thunderbolt networking or plugging a DAS. What's your use case for Thunderbolt in macOS and Windows?

Click to expand...

Thanks for your interest. I explain it better. I have a dual boot system, Windows and OSX. I have UAD Apollo Twin Mk2 with TB3 to TB2 adapter, and I use it on both systems for DAW and audio system, of course . Before flashing the firmware, I had the problem that hot plug didn't work on OSX unless I booted Windows first, and then reboot to OSX. Now, after flashing the firmware, it's inverted .
Hot plug with SSDT didn't work on my build. I think because of the dual boot. But, now with the new firmware, it does so it's fine. If I need to use it on Windows, I will start first OSX and then reboot, it's not a problem.
It was a strange behavio,r no?

Vorshim92 said:

It was a strange behavior no?

Click to expand...

Strange indeed… I see that this UAD Apollo Twin II uses Thunderbolt 2, so there is also an adapter in the mix. Maybe it is an issue with properly connecting with the older TB2 controller? Unfortunately, it is likely impossible to investigate without owning an Apollo.

Short of running two Thunderbolt cards, one for each OS, it seems you have to decide which OS is most important and is allowed to work better.

etorix said:

Strange indeed… I see that this UAD Apollo Twin II uses Thunderbolt 2, so there is also an adapter in the mix. Maybe it is an issue with properly connecting with the older TB2 controller? Unfortunately, it is likely impossible to investigate without owning an Apollo.

Short of running two Thunderbolt cards, one for each OS, it seems you have to decide which OS is most important and is allowed to work better.

Click to expand...

Initially I think too it was something related to tb2 adapter but from what I saw it's more like something related to the initialization of the controller at the boot because on windows I noticed that there is the "ejection function" on the try icon of the controller when it's working. Of course I need a tb3 device to confirm this but unfortunately I can't right now. If you can advise me something, like an ssd or something.
I also noticed that I saw on z390 designare that there is the Force GPIO3 Pwr in BIOS. Don't know if there is something also on this b550...

Vorshim92 said:

Thanks for your interest. I explain it better. I have a dual boot system, windows and osx. I have UAD Apollo twin mk2 with tb3to2 adapter and I use it on both system, for DAW and audio system of course . Before flashing the firmware I had the problem that Hotplug didn't work on OSX unless I booted Windows first, and then reboot to osx. And now after flashing the firmware it's inverted .
Hotplug with ssdt didn't work on my build I think because of the dual boot but now with the new firmware it does so it's fine. If I need to use it on windows I will start first osx and then reboot, it's not a problem.
It was a strange behavior no?

Click to expand...

We struggled with this problem in the early days of the COVID pandemic. Hard to believe that all this firmware flashing excitement began at about the same time as the lockdowns began!

The problem is this:

• When we flash the Titan Ridge firmware, we force it into something called OS Connection Management mode. This means whenever a device is connected or disconnected, the Operating System has to manage the link setup and link teardown functions. macOS is designed for this. This is what enables Thunderbolt Bus. But Windows and Linux do not like this mode.
• The other mode is Internal Connection Management mode or ICM. In this mode the firmware of the Thunderbolt controller manages link setup and link teardown. It prevents the operating system from gaining full control over these functions, which means macOS cannot activate Thunderbolt Bus. But Windows and Linux prefer this mode.

But if you connect and power on your UAD devices before boot, they should work in Windows.

CaseySJ said:

But if you connect and power on your UAD devices before boot, they should work in Windows.

Click to expand...

Yes Casey, I already knew about that. And that exactly what I expected but it doesn't happen

Hi guys! Just here with a problem with my Apollo Twin Thunderbolt 2 and macOS. I'm trying to figure out where the problem may be coming from. I have spike lag "render" only when I use a DAW, and I put just a plugin in a track for my guitar for example. I think is something related the CPU. (Right now I have a Ryzen 5 5800X, but I had also this issue with 5600X.) I don't know how I already fix this problem in the past but now I can't remember how. Maybe something in BIOS or something in the EFI... Any advice?

I'm making a list of things to try: 1) CPU's BIOS settings. 2) Try different TB port or adapter 3to2. 3) Check something wrong in EFI (maybe kernel patches).

P.S. I see on the CPU monitor in the DAW that, when there is the stuttering, the CPU goes from 1% to 9% and then immediately goes back down.

EDIT: PROBLEM SOLVED. IT WAS THE PORT!

Hello friends!
I ask for your help, I can't figure out what the problem is. I updated OpenCore to 0.8.7 from 0.8.5 and am trying to upgrade from Monterey to Ventura and get a bootloop. Security booth changed, updated kext, the error that I have time to see is related to ACPI

Fanuil said:

Hello friends!
I ask for your help, I can't figure out what the problem is. I updated OpenCore to 0.8.7 from 0.8.5 and am trying to upgrade from Monterey to Ventura and get a bootloop. Security booth changed, updated kext, the error that I have time to see is related to ACPI

Click to expand...

Hello @Fanuil,

We need to install the latest AMD-OSX kernel patches, which can be downloaded from here:

• Click the green Code button and download the ZIP
• Inside the ZIP is a file called patches.plist
• Use a text editor such as BBEdit or a plist editor to copy those patches to your config.plist
• Then modify the first 3 patches according to the number of physical CPU cores

I've made these changes for you in the attached file. Remember to copy serial numbers back into PlatformInfo before use.