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

[Fabrizzioa04]

Hello @Fabrizzioa04,

Some suggestions...

• We cannot use AptioMemoryFix. Please delete and replace that with OsxAptioFix2Drv.free2000.efi, which is available from Post-Install Files.zip in post #1.
• Also check that slide=0 is set in the Boot section of your config.plist.
• Have you tried using FakeSMC instead of VirtualSMC to see whether that makes any difference regarding Vt-d and dart=0?

I get the same with both FakeSMC and VirtualSMC, slide=0 its also checked

 

[CaseySJ]

I get the same with both FakeSMC and VirtualSMC, slide=0 its also checkedView attachment 417356

This may be a silly question, but are you sure you need to disable Vt-d for the VRS8 audio interface? Maybe it also needs Thunderbolt Bus?

 

[Fabrizzioa04]

This may be a silly question, but are you sure you need to disable Vt-d for the VRS8 audio interface? Maybe it also needs Thunderbolt Bus?

According to @luckyal the Vt-d has to be enable, hows the Thunderbolt Bus? The interface is connected via pcie

 

[FriFlo]

• You can also try reseting CMOS by shorting 2 pins on the motherboard with a flathead screwdriver. The procedure is easy and it will allow the firmware to fully re-scan the system for devices and rebuild all internal data structures and device trees. It's a way of "detoxifying" the system and restoring good health

So, the way I understand this, I will try putting back the 128Gb-kit and then reset CMOS and see if that will helps ... by the way, what I already noticed editing the BIOS, with the 128-GB kit installed, the X.M.P. option was not available anymore ... probably, because the speed is different for that kit?

 

[CaseySJ]

According to @luckyal the Vt-d has to be enable, hows the Thunderbolt Bus? The interface is connected via pcie

The VRS8 has two Thunderbolt 2 ports according to this:

Slate Digital VRS8 Thunderbolt Audio Interface

8 x 8 Thunderbolt Audio Interface, with 8 VMS-ONE Mic Preamps, 2 Instrument/Line Inputs, 8 Line Outputs, 2 Headphone Outputs, and Built-in Monitor Switching - Mac

www.sweetwater.com

The Slate Digital website does not seem to have a Technical Spec page so I'm not sure what the "PCIe" interface is. Thunderbolt is an extension of PCIe.

Edit: After rereading @luckyal's post here, I agree you should follow his configuration closely, which means:

• Use VirtualSMC instead of FakeSMC
• Use AptioMemoryFix instead of OsxAptioFix2Drv-free2000
• Keep "slide=0" in Boot Arguments
• Unlock MSR 0xE2 register
  • Have you confirmed that 0xE2 is unlocked?
    

 

[CaseySJ]

So, the way I understand this, I will try putting back the 128Gb-kit and then reset CMOS and see if that will helps ... by the way, what I already noticed editing the BIOS, with the 128-GB kit installed, the X.M.P. option was not available anymore ... probably, because the speed is different for that kit?

You can reset CMOS with 64GB or 128GB. It should not matter.

However, the most important thing is Firmware Version. Are you running F6 or F7? There is no support for 32GB UDIMMs before F6.

 

[kwalter]

First a thank you for your efforts on this one - I managed to get a working Designare system working from this thread with no problems at
Then I thought I'd resurrect my Maximus ROG Hero X MB with Mojave
Now having made a complete backup of my Designare system, I thought I'd try booting my Hero X system from it
Well, what do you know - it runs perfectly. Sound, Ethernet, all USB, Graphics, WiFi, Bluetooth. I can't find anything that doesn't work perfectly

 

[CaseySJ]

First a thank you for your efforts on this one - I managed to get a working Designare system working from this thread with no problems at
Then I thought I'd resurrect my Maximus ROG Hero X MB with Mojave
Now having made a complete backup of my Designare system, I thought I'd try booting my Hero X system from it
Well, what do you know - it runs perfectly. Sound, Ethernet, all USB, Graphics, WiFi, Bluetooth. I can't find anything that doesn't work perfectly

Seems you hit the BOGO lottery! Buy One Get One free -- or rather, Build One Get One free. But are you sure the USB ports are correct? Chances of custom USB SSDT from Designare working fully on Asus Maximus Hero are less than 10%

 

[FriFlo]

You can reset CMOS with 64GB or 128GB. It should not matter.

However, the most important thing is Firmware Version. Are you running F6 or F7? There is no support for 32GB UDIMMs before F6.

I am running Version F6 (confirmed that in the BIOS) and I have performed the CMOS reset after putting back the 128GB kit. With the 128Gb I can neither boot the former installation, nor enter a new Mac OS install. What else could be tried to get the larger kit working? Should I try installing F7? I have no idea at this point. With F6, however, the RAM is properly working on Windows on the same PC.

Edit: I now tried running the installer with only two 32-GB sticks installed, to check, if the problem is related to the complete capacity. But it seems, it is rather related to the modules themselves ... any ideas on this?

 

[CaseySJ]

I am running Version F6 (confirmed that in the BIOS) and I have performed the CMOS reset after putting back the 128GB kit. With the 128Gb I can neither boot the former installation, nor enter a new Mac OS install. What else could be tried to get the larger kit working? Should I try installing F7? I have no idea at this point. With F6, however, the RAM is properly working on Windows on the same PC.

Edit: I now tried running the installer with only two 32-GB sticks installed, to check, if the problem is related to the complete capacity. But it seems, it is rather related to the modules themselves ... any ideas on this?

So with two 32GB DIMMs (total 64GB) you see the same startup error message with macOS? Are the 2 DIMMs installed in the correct 2 DIMM slots (cannot be installed in adjacent slots; must skip a slot)?

Sure, you can try upgrading BIOS to F7. This will reset BIOS settings, so they must be re-configured after the update.

But of course no problems with Windows on the same machine with all 128GB... So it's not technically a firmware issue or a power supply issue or a faulty DIMM issue.

Something more radical to consider (but only after trying the above):

• Replace FakeSMC and its sensors with VirtualSMC (this also requires VirtualSMC.efi to be copied into CLOVER/drivers64UEFI).
• Replace OsxAptioFix2Drv-free2000 with AptioMemoryFix-64.