Contribute
Register

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

@CaseySJ,

Thank you for your reply. Hard to believe that this build is already so old - must be on Pandemic time :)


View attachment 536066
Seems your OpenCore EFI Folder is 0.7.4 so please try the attached ZIP, which contains OpenCore 0.7.5. Inside the ZIP is a folder named EFI.

Simply add serial numbers into PlatformInfo --> DataHub section before use.

Some notes:
  • To enable verbose mode, press and release CMD-V at the OpenCore boot picker before selecting the Mojave boot disk.
  • I've made these changes:
    • Removed agdpmod=pikera
    • Disabled AppleVTD
    • Disabled SIP (system integrity protection)
    • Set SecureBootModel to Disabled
 

Attachments

  • OC-075-DESIGNARE-Z390-makonats.zip
    7.1 MB · Views: 34
Hi @CaseySJ ,

I did followed your instructions, reboot is OK and all USB ports are working properly!

Now, here is my IOreg to determine where Bluetooth is located ;-)

Frank
The IOReg file is very helpful, but it tells us that no Bluetooth device is connected to a USB port.

Some questions:
  • Which WiFi/BT device are you using? Fenvi FV-T919?
  • Is the Bluetooth USB data cable connected to one of the two internal F_USB headers on the motherboard?
Z390-Aorus-Pro.png
 
@faithie999,

I just attempted the procedure on my Monterey 12.1 Beta 3 installation. It works just fine...

Some suggestions:
  • Do not use sudo. I'll modify the guide momentarily.
  • After typing diskutil mount diskXsY where X and Y are determined from diskutil list, try the following:
Bash:
cd /Volumes
ls -l
  • What do you see? Is there a Preboot folder present?
  • If Preboot is present, type:
Bash:
cd Preboot
ls -l
  • What do you see? Do you see one or more UUIDs like this: a9b6e929-6158-4042-9fd4-cefd5e3cb57d ?
FWIW:

I reinstalled the latest Intel Power Gadget (SIP is disabled) with my recent BigSur CCC back-n-forth and it automatically updated the Preboot volume names to what I renamed the drive to (using disk utility) without having to do all this manual renaming trickery.

I don’t know if this works with Monterey, nor if IPG can still be used (and I’m sure any installer that updates the preboot info might do the same) but worked for me easy peasy.

J
 
The IOReg file is very helpful, but it tells us that no Bluetooth device is connected to a USB port.

Some questions:
  • Which WiFi/BT device are you using? Fenvi FV-T919?
  • Is the Bluetooth USB data cable connected to one of the two internal F_USB headers on the motherboard?
View attachment 536096
You're the man!

My DATA cable in the F_USB header wasn't plugged anymore ... oups sorry for this!

Everyhting works now!!! You're a king!!!
 
@faithie999,

I just attempted the procedure on my Monterey 12.1 Beta 3 installation. It works just fine...

Mea culpa. Mea culpa maxima.

when I read the guide my eyes immediately jumped to the code for terminal entries. I missed the "boot to Recovery".

I was ultimately successful. the only quirk I encountered was that once in the vi editor, after deleting the existing name, the newly-typed first 2 characters didn't show up on the screen. so I typed two characters then typed what I wanted the name to be, and exited.

thanks for your help and your patience!!

ken
 
Mea culpa. Mea culpa maxima.

when I read the guide my eyes immediately jumped to the code for terminal entries. I missed the "boot to Recovery".

I was ultimately successful. the only quirk I encountered was that once in the vi editor, after deleting the existing name, the newly-typed first 2 characters didn't show up on the screen. so I typed two characters then typed what I wanted the name to be, and exited.

thanks for your help and your patience!!

ken
I revamped that entire guide yesterday. It was too cluttered and outdated!

 
Hi CaseySJ and others,

My build has been running very well thanks to this thread. Thanks for the great support.

Since a few weeks though, 1 in 5 boots or so the Bluetooth is completely dead. A reboot usually solves the issue. My wireless mouse (Logitech 2.4GHz) works, but the apple keyboard and other BT devices don't.

I'm on Catalina and OpenCore. What info should I collect in order to find out what's causing the issue? I'm using the suggested Fenvi card.
 
I must be missing something. I followed these instructions and here is what happens:
The OpenCore Canopy does launch but after I select the EFI drive I want to boot from the screen goes black and I and I get a DoNot Symbol (circle with the slash across it) and the machine eventually shuts off.
If I select the other drive (which is what I am supposed to do) the screen goes black and the apple logo comes up with a thermometer going like it is doing a system restore I think. This gets halfway through and the screen just goes black.
I still have my backup so after F12 I select that boot drive. Clover runs and I select my initial drive. Things come back except my dual monitors are just one, iTunes wants to launch but doesn't have my credentials, and 1Password keeps trying to verify (which I cancel).

Removing that file has no effect, but any of these could have had a positive impact:
  • Cold boot
  • Reset NVRAM
  • Disable CFG-Lock in BIOS and configure the remaining parameters

I have this same problem and after these steps + "remove boot argument agdpmod=pikera." since I have a Vega 64, I still have instant stop-sign when trying to choose my boot drive. I'm on Catalina atm and Opencore 0.7.5.

Things that I'm thinking might impact:

• The USB stick is 64GB. Is that too big? Does it need to be <32gb?
• I have a Firewire 800 PCI card installed.
• Does the USB port matter for the stick if I get as far as the boot loader screen?

I cannot get Windows to boot from my other SATA SSD either via OpenCore. It sends me to the Windows repair screen. I click "Boot Windows 10" and then the computer just reboots. I have disabled AppleVTD.

What else can I have missed?
 
Last edited:
Hi,

I'm using Oc 0.74 and Monterey 12.01. with USB Bt module. I did the Bt fix. The mouse works well, but the Audio Midi Bt setting does not work. Unable to recognize Cme Widi master midi Bt. Is there any solution for this already?
 
Hello !! You can try, if you wish, this EFI Clover 5142 (necessary for Monterey) which I made for my pleasure. It is functional with my Designare Z390 configuration ... You just have to indicate in the SMBIOS section your serial numbers etc. I recommend to use the iMac19,1 SMBIOS ... because T2 SMBIOS chips (like iMacPro1,1) require, in the RTVariables section the addition of an HWTarget key. You can ask me if you want ...
To possibly modify the included config.plist I recommend you to use either Plist editor or Clover Configurator in its latest version (imperative) 5.19.0.0. because it allows in case of modification of the SMBIOS to keep the ExtendedFirmWares in the SMBIOS essential for the installation of Monterey.
PS : Look at the bootargs you are currently using, especially if there are any that are necessary for your graphics card ...par exemple...
PS2 : If necessary, and if he has the time, I would like to have the opinion of Casey the chief !!

If you want to continue using Clover (which is still a good choice from my point of view - I use OpenCore 0.7.5 or Clover 5142 indefinitely) you will have to update it in its 5142 version (with update day of UEFI drivers - OpenRuntime.efi in particular) and kexts as usual ...
It will also be necessary to modify the config.plist, using Plist Editor for example, by adding a Quirk in the "Quirks" section:
Key: ResizeAppleGpuBars, Type: Number, Value: -1
and,
to install or update Monterey, using Clover configurator (imperatively 5.19.0.0) :
in the SMBIOS section: check Update Firmware Only (to keep the serial numbers, Board Serial Number, SmUUID, etc.)
In the drop-down menu located next to this box, choose your SMBIOS, in this way two new items will be entered: Extended Firmware Features and Extended Firmware Features Mask.

If you use an SMBIOS corresponding to a Mac equipped with the T2 chip, you will also need to enter a new item entitled HWTarget in the Rt Variables section.

The HWTarget corresponding to the SMBIOS “T2” used is found in this table: (do not use parentheses)

MacBookPro 15.1 (J680AP) 15.2 (J132AP) 15.3 (J780AP) & 15.4 (J213AP)
MacBookPro16.1 (J152FAP) 16.3 (J223AP) & 16.4 (J215AP) MacBookPro16.2 (J214KAP)
MacBookAir8,1 (J140KAP) & 8,2 (J140AAP)
MacBookAir9,1 (J230KAP)
Macmini8,1 (J174AP)
iMac20.1 (J185AP) & 20.2 (J185FAP)
iMacPro1,1 (J137AP)
MacPro7,1 (J160AP)

EDIT : I forgot to say that Clover remains the best bootloader for Dual Boot (with Windows and macOs)

Attached is an example of config.plist for iMacPro1,1

Hey @zgonda . Thanks for this. I've decided to also try and see if if can get clover 5142 working. I downloaded your earlier EFI folder from this thread (see quote), because it also has the imac19.1 SMBIOS that I currently have. However, after setting everything up with my bootargs and serial/board numbers, I get this:
IMG_0242.jpeg


I get to the Clover 5142 boot screen though without problems. I have an RX Vega 64 and I'm on 10.15.7, Catalina. Any ideas?

Thanks!
 
Back
Top