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

[CaseySJ]

I did have a USB stick inserted when I did the IOReg file. I've been doing some more testing, and it's very random and weird. I did suddenly get the T3 SSD to show up when all three devices were plugged in (the other two did not show up), but then when I withdrew one of the USB sticks, the SSD drive also disconnected. Then I pulled the SSD out and plugged in another stick, then that one showed up. I can't seem to find a pattern except for that I need to plug several drives in to get any to show up, but I can only get one to show up at a time.

I am using a USB 3.1 Type C extender cable to connect this to the computer, but it's very high quality, and when I plug in my one USB-type C stick straight to the extender cable it shows up, no problem. I have double-sided taped the hub to the underside of my desk and would love to not have to tare it down, otherwise I would have tested to stick it straight into the back of the motherboard.

Have you tested the same hub on a Windows machine or real Mac? I wonder if the hub itself is misbehaving. What happens if you plug 2 or 3 USB flash disks (not SSDs)? Flash disks have lower power requirements than SSDs.

Another suggestion is to use a USB Type C to Type A adapter and see if it works on a Type A port on the Designare or even on a Windows laptop.

 

[CaseySJ]

OH GOD IT IS WORKING !!!! thank you !
So now, how to be sure I have really 128 gram activated? a terminal command?

You can check About this Mac from the Apple menu on very top left of monitor.

 

[digumo]

@digumo @heythisisdave

Between lines 501 and 762 there are almost no other kernel log messages ("almost no other" means there are about 5-6 kernel messages), but 261 messages from other process IDs. So the kernel is stuck waiting for this...

Line 501:
2019-12-21 08:51:41.456670-0500 0x15d Default 0x0 0 0 kernel: ifnet_attach: Waiting for all kernel threads created for interface XHC0 to get scheduled at least once.
Line 762:
2019-12-21 08:51:56.780930-0500 0x3a1 Default 0x0 0 0 kernel: ifnet_attach: All kernel threads created for interface en0 have been scheduled at least once. Proceeding.

Of course there may be other delays, but this is the first and most obvious one. Because en0 and ifnet are mentioned, I agree that it's network related.

Hey @CaseySJ out of curiosity I got sucked down into the "learn more stuff" tunnel. Are you familiar with this log parser called Consolation? I just found it in the rabbit tunnel. Pretty cool tool. He's got some other stuff too like a xattr UI.

 

[jiffyslot]

"Everyone is encouraged to switch to the new set, which consists of two files named (a) OcQuirks-4.efi and (b) FwRuntimeServices.efi."

Okay, I'm confused. Are we using Clover or Open Core? Are "(a) OcQuirks-4.efi and (b) FwRuntimeServices.efi" dependent on OpenCore, or can they be placed into the EFI that is Clover-based?

 

[digumo]

[...]or can they be placed into the EFI that is Clover-based?

Yes

 

[hairyconipiton]

OH GOD IT IS WORKING !!!! thank you !
So now, how to be sure I have really 128 gram activated? a terminal command?

I opened activity monitor and just opened lots of windows playing different youtube videos until I could see that I was actually using all that ram.. It will report in About This Mac as well though.

 

[CaseySJ]

"Everyone is encouraged to switch to the new set, which consists of two files named (a) OcQuirks-4.efi and (b) FwRuntimeServices.efi."

Okay, I'm confused. Are we using Clover or Open Core? Are "(a) OcQuirks-4.efi and (b) FwRuntimeServices.efi" dependent on OpenCore, or can they be placed into the EFI that is Clover-based?

Yes

From the author of OcQuirks:

---

---

FwRuntimeServices.efi is part of the OpenCore Package. As such, it is invoked directly by OpenCore, but not by Clover. This is where OcQuirks comes in. It bridges the gap between Clover and FwRuntimeServices, hence both OcQuirks-4.efi and FwRuntimeServices.efi must be copied to the Clover drivers folder.

 

[CaseySJ]

Hey @CaseySJ out of curiosity I got sucked down into the "learn more stuff" tunnel. Are you familiar with this log parser called Consolation? I just found it in the rabbit tunnel. Pretty cool tool. He's got some other stuff too like a xattr UI.

Just took a look at Consolation. It's a good start, but it seems to lack some features:

• Last Boot option
• Specifying a Predicate

 

[Sapricot]

Wanted to pop in and say a big thank you to CaseySJ for the guide and Hylkepylke for the DSDT.

I built my first hack in 10 years a couple of weeks ago. Managed to get Catalina 10.15.2 installed (first by installing 10.15.1 and updating, without problem) using an EFI folder from forum and iMac19,1. But every time I installed a new kext or something else that rebuilt the kernel cache it would get stuck with "couldn't allocate" at boot. Tried calculating slide value (twice, reset CMOS and cleared the memory map in between) but it just didn't have enough space. Switched to OpenCore while trying and got that running fine at first too, but same thing.

So I gave up and turned off the iGPU and went for iMacPro1,1 instead. That made it stable but a few things missing. Most importantly NVRAM. I just couldn't get the emulation to work and of course it didn't work natively. Thanks to Hylkepylke's DSDT it's now working! That also fixed the PCI device list in System Info (which previously only showed the Titan Ridge).

 

[samtimbaud]

Oops, after 2nd reboot, I have a "couldn't allocate runtime.."