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

xtrell said:

Thanks for this.

@brousseau6933 thank you for these diagrams and all your input, perfect. My case does have a USB-C on the front but it doesn't work.. I've got the scarlett working simply by plugging it into a USB A port with an adapter cable. Functional but I do need those extra ports.

Was there always a 15 port limit on macOS or is this new?? I had no issues with any ports on my previous set-up using all the same build hardware.

Click to expand...

Since Sierra or El Capitan, my memory is a bit shady! Do you have a Fractal case? On the first page of this thread, there is a specific file for the USB-C connector on top of the case.

If you don’t have a Bluetooth Wifi card, you could disable this one, as an example.

I removed agdpmod=pikera for boot args and things seem to be working for the moment.
Out of curiosity, will i need to put it back when I upgrade to Catalina or above?

CaseySJ said:

Hello @cshaw340,

I should start by saying that such boot-to-black issues can be very tricky to resolve. Sometimes we resort to performing a fresh install and migrating or reinstalling our apps. But before we consider anything that drastic, let’s get some background:

• What is the make/model of your monitor?
• Are you using straight HDMI to HDMI cable? Or straight DP to DP cable?
• Which version of OpenCore are you on? If you look at bottom right corner of OpenCore boot picker you will see the REL or release number.
• Are you using only one monitor or multiple monitors?

Click to expand...

I removed agdpmod=pikera from my boot args and things seem to be working at the moment.
Will I need to put it back for Catalina and higher?

cshaw340 said:

I removed agdpmod=pikera for boot args and things seem to be working for the moment.
Out of curiosity, will i need to put it back when I upgrade to Catalina or above?

Click to expand...

No. This boot-arg is for Navi cards and never needed for Polaris—that may well have been the cause of your boot-to-black issue.
You'll only ever need if you upgrade to a RX 5500/5700/6600/6800/6900 GPU.

etorix said:

No. This boot-arg is for Navi cards and never needed for Polaris—that may well have been the cause of your boot-to-black issue.
You'll only ever need if you upgrade to a RX 5500/5700/6600/6800/6900 GPU.

Click to expand...

Thanks for the info. I assumed that the instructions applied to the original components of the build in post 1.
Do I need any boot arg for the RX570? It seems to be fine without one and hardware acceleration is working (clear dock / image quick-look).
I'm just so happy I don't need to do a clean install on this Pro Tools rig with hundred of plugins

Hi @CaseySJ , looking to upgrade my current build to Monterey (finally) but held off till UAD(using Apollo Twin X) officially supported the macOS . I am just going to keep my Samsung 970 in place for now and just do an upgrade. Running 0.8.2 OC and wondering what else I should consider before doing the upgrade? Good post to follow? Oh, and yes I backed up my system.

cshaw340 said:

Do I need any boot arg for the RX570?

Click to expand...

No boot-arg for Polaris or Vega. It just works out of the box.

jeff.m.ruth said:

Hi @CaseySJ , looking to upgrade my current build to Monterey (finally) but held off till UAD(using Apollo Twin X) officially supported the macOS . I am just going to keep my Samsung 970 in place for now and just do an upgrade.

Click to expand...

Hello @jeff.m.ruth,

Samsung 970 will experience slow boot speed in Monterey due to incompatible "trim" function. However, if you upgrade first to OpenCore 0.8.3 and then upgrade to Monterey, you can disable the trim function in OpenCore as follows:

Disabling trim can reduce write speeds and induce a bit more wear on the longevity of an NVMe SSD. We recommend switching to WD SN 7xx series or even the cheaper SN 5xx series. But it's also okay to stay with Samsung and keep an eye on the NVMe "remaining lifespan".

jeff.m.ruth said:

Running 0.8.2 OC and wondering what else I should consider before doing the upgrade?

Click to expand...

If you are using Intel WiFi/BT, some extra work is necessary to enable the drivers. There's a post about that here:

jeff.m.ruth said:

... Oh, and yes I backed up my system.

Click to expand...

Bravo!! Hopefully it's a bootable backup rather than a Time Machine backup. Time Machine backups don't include EFI partitions...

CaseySJ said:

Samsung 970 will experience slow boot speed in Monterey due to incompatible "trim" function. However, if you upgrade first to OpenCore 0.8.3 and then upgrade to Monterey, you can disable the trim function in OpenCore as follows:

Click to expand...

Great! Thanks @CaseySJ. One question, I have the latest HackinDROM v2.1.3, however I am not getting the option to update to OC 0.8.3 Will give the upgrade a go tomorrow.

CaseySJ said:

One more easy experiment is to shutdown the system, disconnect the VGA power cables from NVidia GPU, the boot up and see if shutdown works from macOS.

Click to expand...

Sorry for the delay on this. Ended up needing to pull the GPU entirely otherwise the machine wouldn't boot.
Removed the Nvidia card, and the same problem occurs.