Contribute
Register

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

Hi @CaseySJ !
I recently switched from Clover to OC and updated to Big Sur following your guides. i used the latest OC package from the Mini-Guide in this threat. Problem is that now my Blackmagic PCI card ist not recognised by the system anymore. Has there been any change in the config of the PCI slots? I am new to OC so I am not really sure where to start my investigation. Thank you in advance!
Some questions:
  • Were you using Catalina previously?
  • If so, did you make a bootable backup of that?
  • If so, have you tried booting that Catalina disk through OpenCore 0.6.4?
    • The same OpenCore EFI folder you use for Big Sur can also be used for Catalina.
  • Then see if the Blackmagic PCIe card is recognized.
My guess is that the Blackmagic driver might not be compatible with Big Sur. So this may not be an OpenCore issue, but a Big Sur issue.
 
I see. You can certainly switch to Clover as follows:
  • First rename or backup the existing OpenCore EFI.
  • Then locate your Clover EFI folder and copy it to the EFI partition of a USB flash drive in order to do a test boot through Clover.
  • Because you are using Catalina, do not install any third-party kexts in /Library/Extensions folder.
  • Instead, just confirm that all necessary kexts are in the CLOVER/kexts folder.
  • Insert USB flash drive in the computer, boot the machine, and press F12 at BIOS splash screen to open the BIOS boot menu. Select the USB flash disk.
  • Now Clover Boot Menu should appear. Boot Catalina.
Thank you! And again, thanks for all of your hard work - the community is grateful for someone like you!
 
Thank you for pointing this out.

If @cheetoh had followed the mini-guide he would not have run into this. I do not recommended the use of ProperTree's "blind self-configuration" option for reasons like this.

We experiment with different EFI drivers and we keep some of those drivers in the EFI folder in case someone wants to enable them. There may even be superfluous kexts in the EFI folder, but they are not referenced in config.plist.

Bottom Line: Do not use ProperTree's self-configuration option.

Consider me then as someone who has elected to enable OpenUsbKbDxe.efi, and am now reporting to you that this driver is not recommended and even harmful. Are you still going to keep this driver in your reference EFI? For what reason would anyone else want to enable it, unless he has a pre-Ivy Bridge system and wants to use a Z390 Designare EFI.

With all due respect, why don't you just delete it, and prevent someone else, who doesn't follow your mini-guide and uses ProperTree, from stepping on the booby trap.
 
Consider me then as someone who has elected to enable OpenUsbKbDxe.efi, and am now reporting to you that this driver is not recommended and even harmful. Are you still going to keep this driver in your reference EFI? For what reason would anyone else want to enable it, unless he has a pre-Ivy Bridge system and wants to use a Z390 Designare EFI.

With all due respect, why don't you just delete it, and prevent someone else, who doesn't follow your mini-guide and uses ProperTree, from stepping on the booby trap.
The driver has no negative effect in my system.
 
** Preliminary Update on Big Sur Public Beta **

I've been encountering a persistent problem when installing Big Sur Public Beta 1 directly on Designare Z390. Using the OpenCore 0.6.0 EFI from the Mini-Guide (no changes) and standard BIOS parameters (no changes), the Big Sur installer starts up and I can (a) format the destination disk and (b) begin installation. But about 30 seconds into the process, the following error occurs (simply open the Installer Log from the menu and select "Show all Messages" from the pop-up on the right side of the log window):
...
Hello!
Seems like I'm having the same problem what you did back in the Summer.
My detailed problem is written here:
LINK
Do you have a workaround for me? I don't have another SSD, sadly, however 2 NVMe I cannot install Big Sur on.

Thank you so much!
 
Hello!
Seems like I'm having the same problem what you did back in the summer.
My detailed problem is written here:
LINK
Do you have a workaround for me? I dont have another SSD sadly however 2 NVMe I cannot install Big Sur on.

Thank you so much!
Sorry to hear that. I have still not solved this puzzle, but I do have a workaround:
  • Because I have several other Hacks and Macs, I do the following:
    • Clone the NVMe SSD to a SATA SSD mounted in an external USB 3.0 enclosure.
    • Connect the SATA SSD to another Hackintosh (or Mac).
      • Boot the Hack using its own EFI folder.
      • From the OpenCore Picker, boot the external SATA SSD.
      • Login to macOS and perform in-place update through System Preferences --> Software Update.
      • Shutdown the system and remove the SATA SSD.
    • Connect the SATA SSD to the original Hackintosh.
      • Boot the Hack and select the SATA SSD.
      • Login to macOS.
      • Make sure everything is okay.
      • Then clone the SATA SSD to the internal NVMe SSD.
        • Always good to make a backup clone of the NVMe SSD before doing this.
 
Some questions:
  • Were you using Catalina previously?
  • If so, did you make a bootable backup of that?
  • If so, have you tried booting that Catalina disk through OpenCore 0.6.4?
    • The same OpenCore EFI folder you use for Big Sur can also be used for Catalina.
  • Then see if the Blackmagic PCIe card is recognized.
My guess is that the Blackmagic driver might not be compatible with Big Sur. So this may not be an OpenCore issue, but a Big Sur issue.
I just tested several things. The card is even not responding on Catalina anymore. Even when booted via Clover. Switched it with the Wifi-Adapter. Still nothing. So I think the PCI card is fried.. Must be the case.
 
I just tested several things. The card is even not responding on Catalina anymore. Even when booted via Clover. Switched it with the Wifi-Adapter. Still nothing. So I think the PCI card is fried.. Must be the case.
Have you tried doing a CMOS Reset and then configuring BIOS parameters again (starting with F7 -- Load Optimized Defaults)?
 
The driver has no negative effect in my system.
True, until you enable it.


I don't mean to meddle myself into this. But I just want to mention my opinion and what I think regarding this. I hope people take certain things in mind.

I'm not saying I know heck of a lot. I do not. I learn from people on this forum, on other forums, reading myself. Reading stuff perhaps many other hackintoshers do not read, such as UEFI specifications, ACPI specifications and USB specifications etc. I'm not saying people should read thousands of pages. However, people should read the OpenCore documentations when dealing with OpenCore.

One can clearly understand that CaseySJ's OpenCore 0.6.4 folder was meant to be "as is", the only part he has mentioned to change was sn, board sn, UUID etc. The mini guide does not refer to ProperTree at all. It is assumed people will not use it if it is not mentioned.

I myself prefer to do stuff manually, I just use a simple plist editor (an app called Smultron). I don't vouch for OpenCore Configurator or ProperTree. But that is my opinion.

Anyhow. This said, OpenUsbKbDxe.efi is not a problem if it is not activated, and it is assumed that CaseySJ's OC 0.6.4 folder is meant "as it is".

Of course, someone’s hackintoshing experience becoming bad, does not hold the guide-maker liable. It is hackintoshing. I don't find anything wrong with how the OpenCore Mini-guide is.

Don't want OpenUsbKbDxe.efi, great, don't use it.

No hard feelings, I hope. I just want people to know that one should clearly understand here that OpenCore is beta. The OpenCore devs still consider it beta, regardless of how well it works. Read the documentations so your experience can be good to the max possible level.

Happy Hackintoshing!
 
Back
Top