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

[CaseySJ]

Yes, the Z390 Designare with latest F7 BIOS.
EVO 970 Plus M2 500GB with latest firmware
Mojave 10.14.6
Whichever version of Clover that Multibeast installs, can’t remember off hand.

The real cause of the error is probably something before the "keybag" error message. In any case, some things to try:

• Use MultiBeast 11.3.0. If this is already the version that was used, update Clover by download and running this file. It may be necessary to boot from the USB install disk or mount the NVMe into a different working system.
• In BIOS:
  • Is IGFX (IGPU) enabled?
  • If so, is DVMT-PreAlloc set to 64MB or larger?
  • Is Above 4G Decoding enabled?

 

[CaseySJ]

no luck.
I adjusted the TB bios settings per the guide.
installed the alpine ridge card in the X4 slot
connected the card to the THB_C header.
plugged the apple TB3 to TB2 adapter into the card
plugged the Seagate TB1 HD dock into the adapter
booted
HD not recognized.
attached are IO reg before and after.
where in io reg should the alpine ridge card show up?
thanks!!


edit--to test the display ability of the alpine ridge, I plugged a DP to miniDP from my rx590 output to the DPin on the alpine ridge, and the HDMI port of the alpine ridge properly drives my monitor.

I have a project to do for my daughter, but later today I'll boot to windows and see how the card responds. there is a windows driver I will need to install.

full disclosure: because I'm thrifty (cheap?) I bought a "like-new" alpine ridge from Amazon at about half the cost of new. I thought it was new, since there was still an intact factory-type seal on the box. but the header connector was wrapped with a rubber band, and the first owner very carefully removed the seal on the anti-static bag so that looked new, too. and no install manual nor windows driver CD. hopefully if the card were defective the returner would have said so to amazon and they wouldn't have put in into their "warehouse" section. we'll see.

The GC-Alpine Ridge is on PCI0.PEG1. The two attached files should be copied to CLOVER/ACPI/patched folder and will take effect after a reboot. These files should:

• Enable hot plug
• Inject device name information to System Information --> PCI

However, because I don't have a copy of your motherboard's original DSDT.aml, there is a small chance that the hot plug SSDT will not work. We can tackle that problem once we get there...

 

[rondark]

@CaseySJ

Are you planning to do an update thread for Catalina? This thread was so good that I am sure many, many people would welcome it.

 

[CaseySJ]

@CaseySJ

Are you planning to do an update thread for Catalina? This thread was so good that I am sure many, many people would welcome it.

Yes absolutely! My intention is to update the existing build guide (post #1) as follows:

• Keep Mojave instructions intact, but move selected sections inside of spoilers to reduce clutter.
• Refocus the build guide towards Catalina -- that is, Catalina will take center stage.

I should also point out two different audiences when it comes to Catalina:

• Audience 1: Upgrades from Mojave --> Catalina
  • This should be easy (famous last words) to do via the App Store, but there may be some preparation steps needed such as:
    • Do we need to update Clover first?
    • Do we need to update VirtualSMC first (very likely)?
    • Do we need to update Lilu, WhateverGreen, AppleALC first?
  • I expect to do a Mini-Guide for this, but link it from post #1.
• Audience 2: Fresh Install of Catalina.
  • The build guide itself (post #1) is primarily concerned with fresh installs.
  • This also depends on UniBeast and MultiBeast being ready for Catalina.

 

[rj510]

Yes absolutely! My intention is to update the existing build guide (post #1) as follows:

• Keep Mojave instructions intact, but move selected sections inside spoilers to reduce clutter.
• Refocus the build guide towards Catalina -- that is, Catalina will take center stage.

I should also point out two different audiences when it comes to Catalina:

• Audience 1: Upgrades from Mojave --> Catalina
  • This should be easy (famous last words) to do via the App Store, but there may be some preparation steps needed such as:
    • Do we need to update Clover first?
    • Do we need to update VirtualSMC first (very likely)?
    • Do we need to update Lilu, WhateverGreen, AppleALC first?
  • I expect to do a Mini-Guide for this, but link it from post #1.
• Audience 2: Fresh Install of Catalina.
  • The build guide itself (post #1) is primarily concerned with fresh installs.
  • This also depends on UniBeast and MultiBeast being ready for Catalina.

While I've not tried Catalina on the Designare build, I have run a 2nd SSD with Catalina on my X299 build. It was absolutely straight forward: same kexts, drivers and SSDT files. Even sequential updates from ß6 to now ß10 have been seamless. I've used both OpenCore (v050 and 051) and Clover (v5070).

One significant change I noticed with Catalina is that it does not seem to require EC injection for power management (I made a post about it here).

There are some interesting security changes with Catalina that are nicely described here and here with some SIP background here and here (this site, The Eclectic Light Company, has some really interesting art history too and I was then off reading about Charlemagne). On the same site, there's one post that deals with upgrading to Catalina here (of course, not from a Hackintosh perspective, but still useful to read).

 

[mobi]

Yes absolutely! My intention is to update the existing build guide (post #1) as follows:

• Keep Mojave instructions intact, but move selected sections inside spoilers to reduce clutter.
• Refocus the build guide towards Catalina -- that is, Catalina will take center stage.

I should also point out two different audiences when it comes to Catalina:

• Audience 1: Upgrades from Mojave --> Catalina
  • This should be easy (famous last words) to do via the App Store, but there may be some preparation steps needed such as:
    • Do we need to update Clover first?
    • Do we need to update VirtualSMC first (very likely)?
    • Do we need to update Lilu, WhateverGreen, AppleALC first?
  • I expect to do a Mini-Guide for this, but link it from post #1.
• Audience 2: Fresh Install of Catalina.
  • The build guide itself (post #1) is primarily concerned with fresh installs.
  • This also depends on UniBeast and MultiBeast being ready for Catalina.

I guess must people that uses its build as DAW most be careful about this update, I've received many emails from audio developers advising to not do it , still many issues not yet figured out for many developers.

 

[Zip1]

I guess must people that uses its build as DAW most be careful about this update, I've received many emails from audio developers advising to not do it , still many issues not yet figured out for many developers.

32-bit apps (and plug-ins?) will NOT work. No way to make 32-bit software work.
Keep a Mojave partition/drive until you are SURE everything you need is working.
Personally, I'm not changing. I use my computer to make a living.

 

[faithie999]

The GC-Alpine Ridge is on PCI0.PEG1. The two attached files should be copied to CLOVER/ACPI/patched folder and will take effect after a reboot. These files should:

• Enable hot plug
• Inject device name information to System Information --> PCI

However, because I don't have a copy of your motherboard's original DSDT.aml, there is a small chance that the hot plug SSDT will not work. We can tackle that problem once we get there...

I added the two SSDT's to api/patched, to no avail.

I'm thinking 2 things:
1) this seagate adapter just doesn't like the TB3 card
2) the alpine ridge needs slightly different BIOS settings than the Designare requires.


maybe someone out there has the alpine ridge with a non-designare mobo that can tell me what their TB bios settings are.

ken

 

[CaseySJ]

While I've not tried Catalina on the Designare build, I have run a 2nd SSD with Catalina on my X299 build. It was absolutely straight forward: same kexts, drivers and SSDT files. Even sequential updates from ß6 to now ß10 have been seamless. I've used both OpenCore (v050 and 051) and Clover (v5070).

One significant change I noticed with Catalina is that it does not seem to require EC injection for power management (I made a post about it here).

There are some interesting security changes with Catalina that are nicely described here and here with some SIP background here and here (this site, The Eclectic Light Company, has some really interesting art history too and I was then off reading about Charlemagne). On the same site, there's one post that deals with upgrading to Catalina here (of course, not from a Hackintosh perspective, but still useful to read).

I think the article you linked to (see link below) should be mandatory reading for everyone that is planning to upgrade to Catalina, especially Pro users.

Take 10 minutes to read this. Don't say we didn't warn you!

Preparing to upgrade to Catalina

Coming in just a few weeks now, if you’re going to upgrade early to Catalina, now’s the time to start preparing with these tips.

eclecticlight.co

 

[CaseySJ]

I added the two SSDT's to api/patched, to no avail.

I'm thinking 2 things:
1) this seagate adapter just doesn't like the TB3 card
2) the alpine ridge needs slightly different BIOS settings than the Designare requires.


maybe someone out there has the alpine ridge with a non-designare mobo that can tell me what their TB bios settings are.

ken

Please post IOReg file again. I'd like to examine the new device tree under PEG1. Do you have any Thunderbolt 3 devices other than monitor?