Contribute
Register

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

Hi Guys,

after a long time running 10.15.6 absolutely flawlessly I decided to update to Big Sur today. Followed the Mini-Guides, updated OC from 0.6.1 to 0.6.8 and ran the software update.

After the first reboot I got the "MacOS Installer" option in OC Picker and chose it. Unfortunately process is stuck on the Apple Logo. Even after 30+ Mins. I can reboot, choose "Catalina" from the OC Picker and get into my "old" system without any issues. Apparently the Big Sur installer did not really start to do anything.

Any Suggestions? I had a Dual Boot System with WIN10 on a 2nd SSD (M2 Slot) which is still physically installed, but disk is formatted (EFI still exists though). The WINDOWS Boot Option still exists in Bios, since I dont know how to delete it from the UEFI Menue, but is set on disabled.
Boot Sequence ist OpenCore first. Bios is f9g.

Thank you
 
...

After the first reboot I got the "MacOS Installer" option in OC Picker and chose it. Unfortunately process is stuck on the Apple Logo. Even after 30+ Mins. I can reboot, choose "Catalina" from the OC Picker and get into my "old" system without any issues. Apparently the Big Sur installer did not really start to do anything.

...
When the process gets stuck at the Apple logo and you do a hard reboot, do you still see "Macintosh HD" as a boot option in OpenCore Picker? If so, select it and see if it goes through.
 
Do I recall correctly from a post a few pages back that you’re booting via Clover? If so, I recommend giving OpenCore a try. I just switched to CaseySJ’s EFI a few weeks ago, and it’s running great. I followed the conversion guide and used his EFI as-is.

However, I did have to do a fresh install of macOS; apparently there was some crud on my old drive that caused some GPU isses with OpenCore (described in my posts in this thread about a month ago). I hadn’t done a fresh install in years, so although it was tedious (I have lots of third-party audio apps and plug-ins to reinstall and authorize), it was worth it. I then did an in-place update from Mojave to Big Sur with no problems. I use one Ethernet port for internet (lucky to have gigabit fiber service) and the other for a Metric Halo ULN-8 audio interface with no issues.
Hey @bobmeister , I wanted to thank you for your great reply.

I have been inundated with tech issues ever since, plus the steep learning curve. Initially, things went deceivingly easy. So it was a bit disheartening when all of that evaporated, and I have been battling issues ever since. I followed through with the Clover method on post #1, as that seemed to be the preferred, out in front, mehtod (and I had some experience with Clover from years ago, so was more comfortable). But I have since learned that was the wrong choice. I should have jumped right to a Catalina or Big Sur with OC 0.6.8 install.

At any rate, I have a rather complex (convoluted!) setup, and apparently some things aren't playing nice with other things. I'm trying to sort it all out. I have been able to get Big Sur up and running stable on my test system. So my plan now is to document my process with EVERYTHING and every step I need to do in order to go from bare metal to full Hack, within my environment and equipment.

I have also verified that my two Thunderbolt F/W flashes were both successful. PRAISE JESUS (and I was)!! The issues I experienced REALLY made it seem like I had damaged my board during the F/W flash process.

Anyways, thank you!
 
@BOTMT,

Because Clover is installed on the M.2 drive in PCIEX4, have you gone into BIOS Setup --> BOOT section and changed 1st Boot Priority to the Clover disk?

Clover should be able to detect Windows and present you with the option to boot either OS.
Thanks @CaseySJ , just to close the loop on your kind reply; yeah, I had tried that and several other things, so thanks. Things spun way out of control since then. But I'm getting it all sorted out, and should be coming out of the woods here, hopefully as soon as tomorrow.

Thanks again, as always!
 
Your Thunderbolt SSDT missed a part for the aggregation of speed.
Your SSDT shows `Speed: Up to 20 Gb/s x2`.
add the following _DSM to your SSDT:
```asl
"pathcr",
Buffer (0x50)
{
/* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0008 */ 0x00, 0x00, 0x07, 0x00, 0x10, 0x00, 0x10, 0x00, // ........
/* 0010 */ 0x05, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0018 */ 0x00, 0x00, 0x07, 0x00, 0x10, 0x00, 0x10, 0x00, // ........
/* 0020 */ 0x01, 0x00, 0x00, 0x00, 0x0B, 0x00, 0x0E, 0x00, // ........
/* 0028 */ 0x0E, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0030 */ 0x02, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0038 */ 0x00, 0x00, 0x04, 0x00, 0x02, 0x00, 0x01, 0x00, // ........
/* 0040 */ 0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0048 */ 0x00, 0x00, 0x07, 0x00, 0x02, 0x00, 0x01, 0x00 // ........
},
```

After adding this:

Screen Shot 2021-04-30 at 3.46.15 PM.png


The aggregation allows to avoid some problems like Thunderbolt Display screen flash.
 
Does anyone know if there's any advantage to dropping in a 2nd (identical and in compute mode) Sapphire Pulse RX-580 into this build? I'm running my (single monitor, 19,1) build's i9 9900KS at 4.9 GHz.
Anyone?
 
Last edited:
your thunderbolt SSDT missed a part for the aggregation of speed.
your SSDT shows `Speed: Up to 20 Gb/s x2`.
add the following _DSM to your SSDT:
```asl
"pathcr",
Buffer (0x50)
{
/* 0000 */ 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0008 */ 0x00, 0x00, 0x07, 0x00, 0x10, 0x00, 0x10, 0x00, // ........
/* 0010 */ 0x05, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0018 */ 0x00, 0x00, 0x07, 0x00, 0x10, 0x00, 0x10, 0x00, // ........
/* 0020 */ 0x01, 0x00, 0x00, 0x00, 0x0B, 0x00, 0x0E, 0x00, // ........
/* 0028 */ 0x0E, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0030 */ 0x02, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0038 */ 0x00, 0x00, 0x04, 0x00, 0x02, 0x00, 0x01, 0x00, // ........
/* 0040 */ 0x03, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0048 */ 0x00, 0x00, 0x07, 0x00, 0x02, 0x00, 0x01, 0x00 // ........
},
```

after adding this:
View attachment 516956

the aggregation allows to avoid some problems like Thunderbolt Display screen flash.
Hello @xjn819,

Some questions:
  • Which motherboard or Thunderbolt add-in-card are you using?
  • Is the motherboard or Thunderbolt add-in-card flashed to enable Thunderbolt Bus?
  • Are you already using linkDetails in the _DSM Method of the SSDT?
  • For the Pro Display XDR, if you only disable or remove pathcr (no other changes), does Speed drop back to 20 Gb/s?
 
Hello again,

I installed Little Snitch. Now my hacki is a bit broken. Little Snitch changed the system Language. If I go to System Preferences -> Language & Region, I get this message "Could not load Language & Region preference pane." and some software didn't work anymore. They are not blocked by Little Snitch, they won't start (Ableton, Telegram). I deinstalled LS, but nothing changed. Most other programs (Adobe stuff, Reaper, Sononym) work normally. I tried to use Time Machine but it won't work. I have read in the forum that I should boot into Recovery Mode and then reinstall Mojave (14.4).

What's the best way to do? Should I upgrade to the newest version of Mojave (14.6) or should I just try to reinstall the current version? Are there any other things that I must consider? Or is there an easier way to fix this?

Thx for the help.
 
Hello again,

i installed Little Snitch, now my hacki is a bit broken. Little Snitch changed the system Language, if i go to System Preferences -> Language & Region, i get this message "Could not load Language & Region preference pane.) and some softwares didn't work anymore. They are not blocked by Little Snitch, they wont start (Ableton, Telegram). I deinstalled LS, but nothing changed. Most other programs (Adobe stuff, Reaper, Sononym) work normally. I tried to use Time Machine but it won't work. I have read in the forum, that i should boot into Recovery Mode and then reinstall Mojave (14.4).

What's the best way to do? Should i upgrade to the newest version of Mojave (14.6) or should i just try to reinstall the current version? Are there any other things that i must consider? Or is there an easier way to fix this?

Thx for the help
Ouch, sorry to hear that.
  • Do you have a relatively recent bootable backup (not Time Machine)?
    • If not, then boot into Mojave and run Carbon Copy Cloner to make a full bootable backup preferably to an external SATA SSD.
      • Format the external SATA SSD as:
        • Name: Anything
        • Format: APFS
        • Scheme: GUID Partition Map
      • Just clone the internal disk to the external SATA SSD.
      • Then mount EFI partition of (a) internal macOS SSD and (b) external SATA SSD, and use Finder to copy the EFI folder from (a) --> to --> (b).
    • Does Carbon Copy Cloner work right now?
  • If your only backup is Time Machine, are you booting into Recovery and then trying to restore from the Time Machine backup?
  • After making a full bootable backup, if you unable to restore the system using Time Machine, then go ahead and install either Mojave 14.4 or 14.6 without erasing the internal disk.
 
Hello @xjn819,

Some questions:
  • Which motherboard or Thunderbolt add-in-card are you using?
  • Is the motherboard or Thunderbolt add-in-card flashed to enable Thunderbolt Bus?
  • Are you already using linkDetails in the _DSM Method of the SSDT?
  • For the Pro Display XDR, if you only disable or remove pathcr (no other changes), does Speed drop back to 20 Gb/s?

Q1: Titan Ridge v1

Q2: Yes, I have to flash the modified firmware to enable Thunderbolt bus.

Q3: Yes.

Q4: If `patchcr` is removed, the speed goes down to `20x2` and makes my screen flashes randomly.

I have two Thunderbolt m.2 enclosures, one works will with `patchcr` removed, but another speed drop to 20GB/s speed, which lose half speed, implying `patchcr` is crucial. BTW, My SSDs are 970 EVO Plus and SN750.

I have an UltraFine 4K, works will with `patchcr` removed, since the bandwidth is not that high. I also have an UltraFine 5K; It works will with two DP 1.2 cables linked to Thunderbolt card, but not good with one DP 1.4 linked to thunderbolt card. my card is 6900XT. you know what I mean.

For those people who are not able to see BIOS and UEFI when using Thunderbolt Display and flashed Thunderbolt card, you can buy a `HDMI Virtual Display Adapter`. Plug it to your video card, and it allows you to use Windows and see BIOS.
 
Back
Top