Contribute
Register

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

I believe it still looks like a single 4096x2304 signal instead of two 2560x2880 signals.

If we look at the bottom of the log from a 2016 MacBook Pro (thanks to @bluepr0) we see two sets of outputs as follows:

View attachment 422811 View attachment 422812

The same entries from GC-Alpine Ridge look like this:

View attachment 422813 View attachment 422814
Looks like it’s not working at 5k

Have you tried connecting it to the mobo? Maybe it needs that. Or is your mobo not supported?.

Strange based on what @joevt said it should work. Maybe he got an idea on how to fix it, if possible.

That's quite upsetting, at this point I think I'll rebuild the system on another mobo with a Thunderbolt header (no header on Designare Z390). It now seems that Thunderbolt header is required for macOS to recognise the display and understand how to handle it.

Thanks!
 
My bad, I must have deleted it for some reason after my last SMBIOS change... I'm hoping this will be my last upgrade/tinkering till the bugs are shaken out of "Catalina" sometime around Thanksgiving by my best guess.

Be Well Casey.
No worries. Incidentally, now would be a good time to update the system backup.
 
Casey, you can add to the Thunderbolt compatibility list the Focusrite Red 4 Pre Thunderbolt/Dante interface. I replaced my MOTU 1248 with it, and it works fine with the Startech 3 to X converter including hot plug/power cycling while Hack is still running.
Thanks! Done.
 
Hi. Sorry for my late reply. I don't often get on TonyMac. I do have a 0.0.4 version. However, I advise people who Hackintosh to actually read up and do their hackintoshing, having a solid good knowledge from the documentation. from each step. I will still upload the OC-EFI folder.
I've also been having a play with OC, version 0.04. This started because my Gigabyte Aorus Pro Wifi was having boot issues with OsxAptioFix2Drv-free2000.efi in Clover (about 1 in 6 boots would end in a black screen). I'd also read forum posts warning against using this driver.

As you mention, it's best to read the accompanying Configuration.pdf before starting with OpenCore. I also found these guides quite useful as well:
I would also recommend reading up on the OpenCore Discussion thread on InsanelyMac:
I'm happy to report, I now have a fully functional Hackintosh (wake, sleep, shutdown, no more black-screens) using OpenCore, though it took a few nights of hard work to get working. I also found it difficult trying to understand what each quirk did (and whether it was needed) in config.plist. And would follow your recommendation of using Xcode to edit config.plist.

EDIT: [NVRAM]If anyone else uses OC with Z390 Designare, let me know if their NVRAM works, that way we'd truly know about NVRAM in correlation with this board and OC.
Regarding native NVRAM for Z390 motherboards, as far as I understand (and my knowledge on this is sketchy), FwRuntimeServices.efi was first introduced in OpenCore 0.04. This replaced the previous AptioMemoryFix.efi & VariableRuntimeDxe.efi drivers. In OpenCore, VariableRuntimeDxe.efi acted in a similar way to EmuvariableUEFI.efi in Clover, allowing emulated NVRAM.

So, NVRAM is still emulated with OpenCore on Z390 systems. It's just that emulation comes working out of the box (so to speak) with version 0.04 of OpenCore. I've also read that the Logouthook.command, which is included in the newest OpenCore releases, also needs to be setup for native NVRAM to fully work. More info here:
As I say, my knowledge on this is pretty sketchy, so hopefully someone can confirm or update this, and I'm going to keep on trying to learn more about how to use OpenCore.
 
I've also been having a play with OC, version 0.04. This started because my Gigabyte Aorus Pro Wifi was having boot issues with OsxAptioFix2Drv-free2000.efi in Clover (about 1 in 6 boots would end in a black screen). I'd also read forum posts warning against using this driver.

As you mention, it's best to read the accompanying Configuration.pdf before starting with OpenCore. I also found these guides quite useful as well:
I would also recommend reading up on the OpenCore Discussion thread on InsanelyMac:
I'm happy to report, I now have a fully functional Hackintosh (wake, sleep, shutdown, no more black-screens) using OpenCore, though it took a few nights of hard work to get working. I also found it difficult trying to understand what each quirk did (and whether it was needed) in config.plist. And would follow your recommendation of using Xcode to edit config.plist.


Regarding native NVRAM for Z390 motherboards, as far as I understand (and my knowledge on this is sketchy), FwRuntimeServices.efi was first introduced in OpenCore 0.04. This replaced the previous AptioMemoryFix.efi & VariableRuntimeDxe.efi drivers. In OpenCore, VariableRuntimeDxe.efi acted in a similar way to EmuvariableUEFI.efi in Clover, allowing emulated NVRAM.

So, NVRAM is still emulated with OpenCore on Z390 systems. It's just that emulation comes working out of the box (so to speak) with version 0.04 of OpenCore. I've also read that the Logouthook.command, which is included in the newest OpenCore releases, also needs to be setup for native NVRAM to fully work. More info here:
As I say, my knowledge on this is pretty sketchy, so hopefully someone can confirm or update this, and I'm going to keep on trying to learn more about how to use OpenCore.

I recently made the switch myself but on 370. LOVE IT.
 
In the immortal word(s) of Mr. Spock, “Fascinating!” :)

The UPSB device should have a property called PCIThunderbolt. The DSB0 device should have a property called PCIHotplugCapable. Both of these are injected by DSM methods so the absence of these properties indicates that those methods did not run or that OSDW() returned ‘false’.

If you can double-check or post a screenshot of the ACPI/patched folder, it would be helpful. Also, because these files are still a work-in-progress, there’s no need to spend too much more time on them.

Sending the EFI in case that's easier.
 

Attachments

  • EFI.zip
    15.2 MB · Views: 133
I recently made the switch myself but on 370. LOVE IT.
Yes, I've enjoyed following your progress over on the discussion thread on InsanelyMac - thanks, I found it very useful & informative :thumbup:

There's a steep learning curve with OpenCore (at least for me) and as mentioned, it's yet to reach beta status, so each update has plenty of changes. I also wonder if it's like when we made the move from Chameleon to Clover many years ago, to take advantage of our new UEFI motherboards. Anyway, I'm rapidly going off-topic now... :)
 
I recently made the switch myself but on 370. LOVE IT.
Yes, I've enjoyed following your progress over on the discussion thread on InsanelyMac - thanks, I found it very useful & informative :thumbup:

There's a steep learning curve with OpenCore (at least for me) and as mentioned, it's yet to reach beta status, so each update has plenty of changes. I also wonder if it's like when we made the move from Chameleon to Clover many years ago, to take advantage of our new UEFI motherboards. Anyway, I'm rapidly going off-topic now... :)
Do you mind sharing what are the main advantages of using it vs Clover?
 
With the price of Samsung 970 EVO's what they are, has anyone found issues in running two M.2 drives to separate OS and Home folders, as CaseySJ suggests?
 
Back
Top