Contribute
Register

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

Thanks,
probably there was a misunderstanding: I would like to install (if possible) macOS Catalina in a second APFS Volume in the same system drive where macOS Mojave is installed as suggested by the Apple documentation:
so I think "option 1" that you suggest is suitable in this case.
Yes, option 1 is the only choice for this. Adding a new APFS volume is a good idea!
Therefore, if I understand correctly, after installing macOS Catalina in the second APFS Volume I should replace the EFI folder created after installing macOS Mojave with the EFI folder that you provide in your installation guide for macOS Catalina and delete the kexts installed in /Library/Extensions of macOS Mojave drive.
Correct, but backup the system first. It's better (but not required) to delete Hackintosh kexts from Mojave's /Library/Extensions folder while you're running Mojave. This allows you to run Kext Utility to rebuild Mojave's kernel cache.
This is the situation of the current /library/extension folder in the system drive with macOS Mojave:
View attachment 457429
This is the situation of the EFI folder you provided in the macOS Catalina installation guide:
View attachment 457430
so i have some questions:

Which files in the / Library / Extensions folder among those that I have highlighted should I move to the EFI/CLOVER/kexts/Other folder?
You have correctly identified all the Hackintosh kexts in those blue boxes. But you should delete them and then run Kext Utility to rebuild kernel cache. You won't be able to reboot into Mojave until Catalina installation is done, because we'll use Catalina's kexts to boot both Mojave and Catalina.
Which files should I replace using the VirtualSMC.kext file instead of the FakeSMC.kext file?
Don't worry about this. When Catalina is installed, VirtualSMC will be automatically used.
Which SMBIOS entries should i copy from Mojave config.plist to Catalina config.plist?
All of them. Like this:
  • Open the Mojave config.plist in Clover Configurator.
  • Then click Text Mode.
  • Now scroll down until you see RtVariables.
  • Select everything from RtVariables to the end of the SMBIOS section as shown.
  • Press CMD-C to copy that to Clipboard.
    Screen Shot 2020-03-27 at 8.08.54 AM.pngScreen Shot 2020-03-27 at 8.09.54 AM.pngScreen Shot 2020-03-27 at 8.09.59 AM.png
  • Now open the Catalina config.plist in Clover Configurator.
  • Switch to Text Mode.
  • Scroll down to RtVariables.
  • Select everything from RtVariables to the end of the SMBIOS section (same as above).
  • But this time press CMD-V to Paste the clipboard.
  • Save the Catalina config.pilst.
During the post-installation phase of macOS I had inserted the file SSDT-UIAC-DESIGNARE-Z390-FD-DEFINE-C-TG.aml (which I have attached) that you kindly provided me for my case: I can use it again or I have to replace it?
Yes you can definitely use it. Just delete the SSDT-UIAC... that is in the Catalina ZIP file. There can be only one USB SSDT at a time.
In this dualboot installation it is better to install Clover RC Scripts or enable native NVRAM?
Much better to enable native NVRAM.
 
Hello Everyone!

Last night I decided to do a fresh install of 10.15.4 using the mini-guide that was very successful for 10.15.3 for me a few months ago. But I am getting the dreaded:

"An error occcurred while preparing the installation. Try running this application again."

I even tried preparing another (new) USB 32GB drive and the same thing. For kicks I went back to my 10.15.3 prepared USB drive (which now has been updated to Clover 5107 as well) and...no problem! Works perfectly.

Also, in both cases (the .3 and the .4 USB drives) Lilu, WG, VSMC and AppleALC are all at the latest.

I don't want to experiment around too much but if I have to I'll just go back to 10.15.3 and wait until we see the first update to .4.

Any thoughts? Thanks!

Lam
  • If you have not switched to native NVRAM, it might be a good idea to do that first.
  • Also try resetting NVRAM by pressing F11 at the Clover Boot Menu, and then attempt the 10.15.4 update.
 
Hello @CaseySJ , I followed your instructions and now, with the "more EFIclone" code it seems to work until the mounting of the EFI partition. After this step I mounted the partition with Clover Configurator but when I open the folder nothing appears inside. I don't understand because I think I followed all the steps. I left you my screenshot of the log messages and the finazl steps that I do in attached files, in case you have any advice ! Thanks a lot !
Hello @mazop89,

Are you using the latest EFIClone.sh from @byteminer's GitHub repository? The "Easy Bootable Backup" guides for Mojave and Catalina were updated a couple of weeks ago with pointers to that repository.
 
  • If you have not switched to native NVRAM, it might be a good idea to do that first.
  • Also try resetting NVRAM by pressing F11 at the Clover Boot Menu, and then attempt the 10.15.4 update.

Hi CaseySJ,

On a new install, isn't the NVRAM file created for the first time? Since I completely reformatted my 2TB NVMe (960 Pro) drive would that factor in? BTW. I wasn't using native NVRAM on my 10.15.3 install and all was fine, but I'm happy to move over to it once I can get this installed.

Can I do that on initial install? I know you were recommending to move to native, post-install.

Thanks,
Lam
 
Is anyone else on the z390 Designare having wake issues? I have followed nearly every guide to try and fix wake codes that I am showing in log and nothing seems to be working.

I have successfully built a z390 Designare / i9 / rx5700xt Hackintosh on open core and the only issue that I am having is a constant wake of the PC. (The monitor stays off but the fans and CPU all wake up for about 30 seconds and turn back off)
I have checked for wake reason in terminal with: log show --style syslog | fgrep "Wake reason"
The errors seem to be the below four from most common:
  1. AppleACPIPlatformPower Wake reason: PEG1 PEGP PEG2 PEGP PXSX RP03 PXSX UPSB DSB0 NHI0 DSB1 DSB2 XHC5 DSB4 RP06 PXSX RP07 PXSX RP08 PXSX PXSX RP10 PXSX RP11 PXSX R
  2. [powerd:sleepWake] Wake reason: "private” identity: "private”
  3. (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: XDCI
  4. AppleACPIPlatformPower Wake reason: RTC (Alarm)
I have tried doing some research, but I haven't been able to find anything that works or what is exactly causing these
I’ve done the below per guides:
Disable Hibernation:
  • sudo pmset -a hibernatemode 0
  • sudo rm /var/vm/sleepimage
  • sudo mkdir /var/vm/sleepimage
Disable other hibernation options:
  • sudo pmset -a standby 0
  • sudo pmset -a autopoweroff 0
Turned off in settings:
  • Allow Bluetooth devices to wake up this machine
  • Enable power nap
  • Wake for network access
Does anyone have any idea what could be causing these 4 constant wake up codes and ideas on how to fix?
667681775_ScreenShot2020-03-26at5_15_33PM.png.964a8d117a6a118f89febbf92ad88baf.png

I am on opencore 0.5.6 / Catalina 10.15.4 and built a USBMAP.KEXT
USB Setup.png

I have gone through every guide that I can find on Z390 Designare to try and isolate these sleep problems, but nothing that I am doing seems to be fixing these.
 
Step 5: Use flashrom to read and create backup of the original contents of the SPI Flash chip.
  • Lauch the Linux Terminal and use the commands below.
  • First we read the existing contents of the SPI Flash ROM and save it. It is critical to make this backup!
  • We read the contents three times and compare their checksums to ensure that all three files are identical. This ensures that the chip was read successfully.
  • The syntax for the read function is as follows (the spispeed parameter is essential):
sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r test1.bin

Code:
pi@raspberrypi:~/Documents $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r Backup1.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.

Hello @CaseySJ
So I have got all the necessary material to read and lash the GC-titan Ridge Card (Raspberry Pi, SOIC8 clip and wires).
I connected evrything as per the guideline but I always get this error message in terminal:
Code:
pi@raspberrypi:~ $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r test1.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Error: Extra parameter found.
Please run "flashrom --help" for usage info.

Could this error maybe due to bad positioning of the SOIC8 clip to the Winbond Chip?

Thank you very much!
 
Hello @CaseySJ , I followed your instructions and now, with the "more EFIclone" code it seems to work until the mounting of the EFI partition. After this step I mounted the partition with Clover Configurator but when I open the folder nothing appears inside. I don't understand because I think I followed all the steps. I left you my screenshot of the log messages and the finazl steps that I do in attached files, in case you have any advice ! Thanks a lot !

It is highly likely that you forgot to flip TEST_SWITCH to "N", as indicated by the all-caps notice of this being a dry-run.
While the output looks correct, please validate that these are indeed the files you intend to copy before flipping this switch.
 
Hello @CaseySJ
So I have got all the necessary material to read and lash the GC-titan Ridge Card (Raspberry Pi, SOIC8 clip and wires).
I connected evrything as per the guideline but I always get this error message in terminal:
Code:
pi@raspberrypi:~ $ sudo flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r test1.bin
flashrom  on Linux 4.19.97-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Error: Extra parameter found.
Please run "flashrom --help" for usage info.

Could this error maybe due to bad positioning of the SOIC8 clip to the Winbond Chip?

Thank you very much!
Have you tried typing the entire command sequence manually instead of copying-and-pasting? I wonder if copy-and-paste might be introducing some issues.
 
Back
Top