Contribute
Register

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

Please see Post 1: Sidecar Patch for Unsupported Macs. This is in the section “Contributed Files and Tips”.
Thank you for your answer.

I Tried the tool, and made a mess :problem:. Sleeping too little does bad and funny things to our brains.

Among the several terminal manipulations,I overwrote the SidecarCore.bak file, giving me no file to fall back on. I tried several options. Now browsers crash on open and the modified SidecarCore file makes it so every app in focus crashes when using the arrow keys.
It seems the tool broke with the latest Catalina update as per this post: https://github.com/ben-z/free-sidecar/issues/59#issuecomment-603697315

Better still, the backup I had also overwritten the Catalina backup I had done, and only have one with Mojave and Clover.

Can I use MacOS recovery to re-install the OS? I am using your latest EFI with OpenCore 0.6.1.
If that isn't possible, is there anywhere to download the original and signed SidecarCore file?
 
Thank you for your answer.

I Tried the tool, and made a mess :problem:. Sleeping too little does bad and funny things to our brains.

Among the several terminal manipulations,I overwrote the SidecarCore.bak file, giving me no file to fall back on. I tried several options. Now browsers crash on open and the modified SidecarCore file makes it so every app in focus crashes when using the arrow keys.
It seems the tool broke with the latest Catalina update as per this post: https://github.com/ben-z/free-sidecar/issues/59#issuecomment-603697315

Better still, the backup I had also overwritten the Catalina backup I had done, and only have one with Mojave and Clover.

Can I use MacOS recovery to re-install the OS? I am using your latest EFI with OpenCore 0.6.1.
If that isn't possible, is there anywhere to download the original and signed SidecarCore file?
Sorry to hear that. I wanted to give you an alternative option instead of changing to iMac19,1. But switching to iMac19,1 might be the better option if the procedure to hack Sidecar no longer works.

If you can tell me the full pathname of the SidecarCore file, I can upload the original file from my system.
 
All is working now. Thanks for your precious help!
Btw I’m experiencing a kind of freeze at boot. As soon as I login, the system prepares startup items and I see some icons in the dock bouncing but then it freezes for a couple minutes.
Mouse pointer moves but cannot interact
Hello @Kooza25,

Some things to check:
  • Are you able to boot into Safe Mode?
    • In Clover, press <space bar> and you'll see Safe Mode (3rd item in the list).
    • Press <space> to toggle it on
    • Press <Esc> to return to main menu and boot macOS
  • If Safe Mode works, go to System Preferences --> Users & Groups --> Login Items and grab a screenshot or disable all of them.
 
It seemed indeed like a better option :)

The SidecarCore file is found here: /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/
Hopefully you're also running the latest 10.15.6 (19G2021)

Your file will hopefully fix my install. If it fails can I re-install the OS from MacOS Recovery mode? It seems some users still experienced issues after replacing their backed up SidecarCore files...

I'm also wondering if this could be related to not having a WIFI card installed. I connect to the internet either by USB tethering or Ethernet.
 
It seemed indeed like a better option :)

The SidecarCore file is found here: /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/
Hopefully you're also running the latest 10.15.6 (19G2021)

Your file will hopefully fix my install. If it fails can I re-install the OS from MacOS Recovery mode? It seems some users still experienced issues after replacing their backed up SidecarCore files...

I'm also wondering if this could be related to not having a WIFI card installed. I connect to the internet either by USB tethering or Ethernet.
Attached is the original SidecarCore from 19G2021. Let's hope it gets you back to a good working state. To switch to iMac19,1 we can just change the SMBIOS name without changing serial numbers. But some apps might require re-licensing. When I tried this a little while ago, the switch was surprisingly painless (but not completely pain free).
 

Attachments

  • SidecarCore.zip
    95.8 KB · Views: 70
Last edited:
Thanks very much Casey for pointing me in the right direction. I followed the procedures specified in the links for the ASUS Prime Z370A (my motherboard is the original Prime, not the Prime-II) and now have a working software-only TB bus and local node implementation - fantastic result! To improve things a bit, I tweaked the SSDT file SSDT-TbtOnPch-Asus-Z370-A.aml in the following ways:
Glad to hear it! That was half the battle...
1. Under device XHC2, added HS and SS support for the USB-C port on the card (note the default SSDT only enabled the Type A port using USB-C properties - I corrected this). I also added model, device_type, and slot naming so the TB USB Controller shows up in System Information under PCI. The names I used are taken from Hackintool patch info. In addition, I added _PRW and _RMV methods in case these were needed for power management of the USB ports for proper sleep and wake-up. I am not sure if these are necessary - perhaps you can comment.
Good to see you have some experience with this. Without HS and SS, did those devices not work at their rated speeds? It is a good idea to add _PRW and _RMV, but activation of USB-C varies with firmware and board/add-in-card. Have you tested the behavior with and without those methods?
2. Updated the ThunderboltDROM (using HackinDROM) since the default SSDT seemed to have a mismatch between the DROM length bytes and the overall DROM buffer size (ref your post "Thunderbolt ROM Decoded"). I also wanted to match the DROM 9-byte preamble to my SMBIOS choice of the iMac18,3 model. I am not sure if these changes were completely necessary, but I proceeded anyways for consistency. I also updated the Thunderbolt Controller model, device_type, and slot-name to match Hackintool patch info.
This was also a good idea. Whenever Thunderbolt Bus is activated (whether through SSDT or through firmware flash) a fully compliant DROM is necessary.
...
However, there are two significant failures/limitations:

7. The TB bus and local node do not appear to survive sleep and wake-up. TB-connected drives (i.e. my test Mac in Target Disk Mode) are force-ejected on sleep. After wake-up, I cannot reconnect the drives even by removing and reinserting the TB adaptor and/or cable. Clearly some of the Thunderbolt power management properties of the setup (hardware?, firmware?, SSDT?) are not working.
8. The TB bus and local node do not appear to come up at all if my test drive (i.e. Mac in Target Disk Mode) is attached to the TB card at boot time.

Note that I am using Clover 5107 with an iMac18,3 SMBIOS (very stable) and am running MacOS Mojave 10.14.6 (also very stable).
These are the issues we have struggled with and eventually we have accepted. The best Thunderbolt results we have yet obtained are with on-board controllers and in particular the Z390 Designare has the fewest Thunderbolt issues that I'm aware of.
 
Last edited:
Wow, that is annoying. So no truly practical workaround then. But now if you've tested this on a MacBook Pro model, then that basically makes this device technically incompatible with even a legitimate a Mac. So I am tempted to simply return the device, and get a simple SATA to USB dock, for way cheaper, and start saving up for a NAS.

I short addendum to this issues various problems, is that if my computer goes to sleep then the drives disconnect as well.

Thanks for your in-depth look into this.

@CaseySJ , what do you recommend that I do now? Is it something that's likely to be an issue with any toaster that I get? I need to figure out a better solution for this. Even if it means getting enclosures for each drive separately.
 
@CaseySJ , what do you recommend that I do now? Is it something that's likely to be an issue with any toaster that I get? I need to figure out a better solution for this. Even if it means getting enclosures for each drive separately.
Separate drive enclosures are plentiful and very inexpensive. They will not suffer from this problem.

On one system I'm using a pair of Mediasonic ProBox HF-2 4-Bay drive arrays connected via USB 3.0.
However, this array is meant for permanent or semi-permanent disk installation rather than frequent hot-swap. For frequent hot-swap it may be best to use single-bay devices.
 
Back
Top