[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

arkanis · Mar 3, 2021

Hey @CaseySJ, I've been running a Gigabyte Designare EX x299 for some time and pretty stable but never got hotplug to work.

Searching about the topic I stumbled on this post which was a godsend so I started experimenting with the AML you provided there for this motherboard. I'm somewhat puzzled because the results are "random"... sometimes everything appears properly under the thunderbolt tab in the system report and sometimes it doesn't (and this hotplug works or not).

Why ? I don't know...

Looking at the AML (without touching it) and trying to compile it, it's giving me the following error :

"Method local is set but never used (Local1)"

I feel we're almost there... if you could have a look or give me any hint I would greatly appreciate it. I've attached to this post my EFI folder and IOReg of the current config.

Thank you for all the hard work and advances made in this post.

P.S: I'm not running the PCI0 rename, so all my AMLs have that renamed to PC00, for unknown reasons renaming to PCI0 messes up something and the system gets unstable.

taegan · Mar 3, 2021

Hi CaseySJ,
is it possible to do CCC (carbon copy) with Big Sur?

CaseySJ · Mar 3, 2021

taegan said:
Hi CaseySJ,
is it possible to do CCC (carbon copy) with Big Sur?

Yes it's possible, but there are some issues to be aware of:

Use the latest version of CCC.
Allow CCC to erase the Destination disk when asked.
The first time you clone a particular version of macOS, CCC may erase the destination disk and copy both the System and User volumes.
- CCC will use Apple's APFS Replication tool, which will take a LONG time.
The next time you clone the same version of macOS, CCC will only clone the User volume. This will take relatively little time.
When a future update of macOS is installed, CCC may do one of the following:
- It may erase the Destination and clone everything from scratch again.
- It may only clone the User volume, which means the System volume will still be the previous macOS version.

CaseySJ · Mar 3, 2021

arkanis said:
Hey @CaseySJ, I've been running a Gigabyte Designare EX x299 for some time and pretty stable but never got hotplug to work.

Searching about the topic I stumbled on this post which was a godsend so I started experimenting with the AML you provided there for this motherboard. I'm somewhat puzzled because the results are "random"... sometimes everything appears properly under the thunderbolt tab in the system report and sometimes it doesn't (and this hotplug works or not).

Why ? I don't know...

Hello @arkanis,

This SSDT enables Thunderbolt Bus on Alpine Ridge systems. You have configured your config.plist correctly, but IOReg does not show Thunderbolt Bus. This might mean that IOReg you posted was generated with the previous SSDT (SSDT-X299-TB3HP).

What happens when you enable SSDT-TbtOnPch-Designare-X299-EX? It would be good to post the following two files are booting the system with this SSDT:

IOReg file
System DSDT (MaciASL --> File --> New from ACPI --> System DSDT)

arkanis said:
Looking at the AML (without touching it) and trying to compile it, it's giving me the following error :

"Method local is set but never used (Local1)"

"Method local is set but never used (Local1)" is perfectly fine and can safely be ignored. It simply means that the local variable Local1 was assigned a value that was not subsequently used.

arkanis said:
I feel we're almost there... if you could have a look or give me any hint I would greatly appreciate it. I've attached to this post my EFI folder and IOReg of the current config.

Thank you for all the hard work and advances made in this post.

P.S: I'm not running the PCI0 rename, so all my AMLs have that renamed to PC00, for unknown reasons renaming to PCI0 messes up something and the system gets unstable.

Your PCI base path is \_SB.PC00 instead of \_SB.PCI0, so the former is required and the latter will not work.

arkanis · Mar 3, 2021

CaseySJ said:
Hello @arkanis,

This SSDT enables Thunderbolt Bus on Alpine Ridge systems. You have configured your config.plist correctly, but IOReg does not show Thunderbolt Bus. This might mean that IOReg you posted was generated with the previous SSDT (SSDT-X299-TB3HP).

What happens when you enable SSDT-TbtOnPch-Designare-X299-EX? It would be good to post the following two files are booting the system with this SSDT:

IOReg file

System DSDT (MaciASL --> File --> New from ACPI --> System DSDT)

"Method local is set but never used (Local1)" is perfectly fine and can safely be ignored. It simply means that the local variable Local1 was assigned a value that was not subsequently used.

Your PCI base path is \_SB.PC00 instead of \_SB.PCI0, so the former is required and the latter will not work.

@CaseySJ thank you for replying, really appreciated.

Please find attached two extracted DSDT's and two IORegs, one when things work as they should and the other when they don't.

Using the TBH3 SSDT of course doesn't give me hotplug BUT on the other hand is "reliable", in the sense that every time I turn on my computer, hardware is detected and shows up. (in the PCI tab in system report and on the own hardware driver tab).

Now using the SSDT provided in this thread loads maybe once or twice, but otherwise fails in both scenarios (showing up under the Thunderbolt tab AND PCI, and the hardware isn't detected at all and is unusable). I also have to power reboot the TB3 Hardware (Blackmagic Design Ultra Studio 4K Mini).

Really puzzled about the "randomness" of it if I can call it like that but I'm no expert.

Thank you for helping me!

hitINdaGs · Mar 3, 2021

CaseySJ said:
Try this in Terminal:

Bash:

launchctl list | grep -v apple

Thank you. I actually managed to get rid of a few things that weren’t needed anymore. However, problem persists. I did notice that if I let the login screen linger for some time and the log in, the taskbar loads immediately. So it’s probably nothing connected to my specific user.

yabusa · Mar 3, 2021

I need some help.
I successfully switched to OpenCore from Clover, but I'm having a difficult time with iMessages.
I log in, then it shows a blank message, then goes back to the sign in screen.
I've attached my OC folder and the NVRAM check results.
I made sure the list appears in Everyman lookup, and negative response on apple coverage, but still doesn't work.
Any help would be great.
Thank you in advance

CaseySJ · Mar 3, 2021

yabusa said:
I need some help.
I successfully switched to OpenCore from Clover, but I'm having a difficult time with iMessages.
I log in, then it shows a blank message, then goes back to the sign in screen.
I've attached my OC folder and the NVRAM check results.
I made sure the list appears in Everyman lookup, and negative response on apple coverage, but still doesn't work.
Any help would be great.
Thank you in advance

Couple of suggestions:

Run Hackintool and scroll the default System window that appears until you see iMessage Keys. There will be 5 keys. Check the Value column to see if there are any question marks or other strange characters. The keys should be hexadecimal strings (0..9 and A..F).
Reset NVRAM from the OpenCore Picker by pressing space bar and selecting Reset NVRAM. This will also reset the Startup Disk so if you have multiple operating systems, go to System Preferences --> Startup Disk and select the default boot disk again.
If problem persists, try the suggestions here: