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

[byteminer]

OK, here's the terminal output and the log file.

Alright, this *might* be the last round of this call-and-response thing, so fingers crossed.
I've attached an ever-so-slightly tweaked version of the previous debug script to this post which might fix this issue. It would be good if you could try it out once more if you have time and report back with the terminal output.

 

[CaseySJ]

Also @CaseySJ had a question, or more I should say a weird occurrence and how can I check it?

So I have a Plex server on the build, and Plex allows for hardware acceleration for encoding using intel quicksync from the newer intel processors, however to my knowledge I assume I don't have IGPU enabled because its not registered anywhere in the system. However when I turned the feature on I noticed I was getting the tag on the encodings that it was using hardware acceleration for the encoding process. Is there a way to test whether I have hardware acceleration or was it possibly using the GPU somehow? the Plex support page mentions

"The following are required in general for Hardware-Accelerated Streaming, regardless of your operating system:

• A recent Intel CPU meeting these requirements:
  • 2nd-generation Intel Core (Sandy Bridge, 2011) or newer (we recommend 5th-gen Broadwell or newer for the best experience; Sandy Bridge, in particular, is known to sometimes have poor visual output on some systems)
  • Supports Intel Quick Sync Video (Not sure? Look up your processor)
• Plex Media Server 1.9.3 or later
• An active Plex Pass subscription"

So I don't know how it could have been the GPU

If IGPU is disabled in BIOS, then of course it's out of the picture. But if it's enabled in BIOS, we can check whether it's also available in macOS by running IORegistryExplorer and scrolling the device tree on left side until we get to IGPU@2. The first sub-node under this should be AppleIntelFramebuffer...

 

[CaseySJ]

For those of you that have your home folder on a separate drive from your OS, what are your backup/restore steps? I have a third drive I would like to carbon copy clone and make it a bootable backup but I'm not sure exactly how it works with two separate drives housing my data. Or, do I only clone the system drive (EFI folder included) and not backup my home folder drive? How do you all handle this?

With Home and System folders separated onto different drives, we use Carbon Copy Cloner to backup the System drive. To backup the Home drive, we have several options:

• Create a new task in Carbon Copy Cloner and backup the Home drive to another disk.
• Use any other backup software of your choice. I personally use Acronis True Image to back up the entire computer (Home and System and EFI) to a Netgear ReadyNAS.
• Use TimeMachine.

 

[CaseySJ]

so i just tried your open core mini guide and cant beleive how easy that was. is it really just the serial numbers and everything works? no more kexts etc? man this is great if so.

just realized the kexts are installed... is it the same method to upgrade? just replace kext and reboot?

Yes. But OpenCore requires each kext to be individually specified in its config.plist, otherwise it will not load the kext. So if you add a new kext, you must also add a new entry in config.plist. And if you delete a kext, you should either (a) delete the corresponding entry in config.plist, or (b) set the disabled field to true.

first thing i did was test nvram

sudo nvram TestVar=HelloWorld
reboot
sudo nvram -p | grep 'TestVar'
no output

what do i need to look at here? trying to go through this thread but haven't come across and suggestions yet

If your system originally had (or has) Clover, it would be necessary to check if "rc scripts" are installed, and to delete them. If you're not familiar with the procedure, I would advise against doing it at this time. OpenCore is still in its infancy, and the OpenCore Mini-Guide is for brave souls willing to tread on thin ice! (That is, we cannot offer a lot of support for OpenCore at this time.)

 

[CaseySJ]

I'm running CLover r4961 and am looking to get current (5103) and know there have been some changes I need to be aware of before updating. I've looked thru the threads on this post but was wondering of there was any guide somewhere
I may have missed for this update as I know things have moved around since r4961. I'm also aware that should replace replace OsxAptioFix2Drv-free2000 with OcQuirks-4 and FwRuntimeServices. Is there anything else I should know?

Thanks in Advance.

• We can follow Step 1, Bullet #4 in the Catalina Mini-Guide to update Clover.
• After the update, download the ZIP file from the same Catalina Mini-Guide and copy the kexts and drivers from the ZIP to the corresponding folders in CLOVER.
• The SSDTs have not changed so no need to modify the ACPI/patched folder.
• Note that we are now using:
  • OcQuirks.efi
  • OcQuirks.plist
  • FwRuntimeServices.efi
  • These 3 files will be copied into the new CLOVER/drivers/UEFI folder.
• After making these changes, delete the old CLOVER/drivers64UEFI folder (or move it to someplace else such as your Documents or Downloads folder).

 

[manfriday]

so i just tried your open core mini guide and cant beleive how easy that was. is it really just the serial numbers and everything works? no more kexts etc? man this is great if so.

just realized the kexts are installed... is it the same method to upgrade? just replace kext and reboot?


first thing i did was test nvram

sudo nvram TestVar=HelloWorld
reboot
sudo nvram -p | grep 'TestVar'
no output

what do i need to look at here? trying to go through this thread but haven't come across and suggestions yet

It looks like you and are are pretty close to the same place in our OC experiment.
You need to have Emulated nvram set up with the LogoutHook command.

I am pretty sure I have LogoutHook running, and it seems to be writing to nvram.plist. however, the variables are not being read back on in reboot. Im not sure why that is.

 

[EliM]

Alright, this *might* be the last round of this call-and-response thing, so fingers crossed.
I've attached an ever-so-slightly tweaked version of the previous debug script to this post which might fix this issue. It would be good if you could try it out once more if you have time and report back with the terminal output.

No worries, happy to do it! The terminal results are attached below. I used the same terminal command as before but with the name of the script changed.

sudo /Library/Application\ Support/com.bombich.ccc/Scripts/EFIClone-v3-DEBUG.sh / "/Volumes/Catalina Clone - Data" 0 ""

I don't claim to understand how this works, but just to confirm, it should say .../Volumes/Catalina Clone - Data... with Catalina Clone being the destination volume?

Thanks again for working on this. I really appreciate it!

 

[EliM]

With Home and System folders separated onto different drives, we use Carbon Copy Cloner to backup the System drive. To backup the Home drive, we have several options:

• Create a new task in Carbon Copy Cloner and backup the Home drive to another disk.
• Use any other backup software of your choice. I personally use Acronis True Image to back up the entire computer (Home and System and EFI) to a Netgear ReadyNAS.
• Use TimeMachine.

Thanks @CaseySJ! I'm interested in this as well. What are your restore steps if the user folder is on a separate drive?

 

[CaseySJ]

No worries, happy to do it! The terminal results are attached below. I used the same terminal command as before but with the name of the script changed.

sudo /Library/Application\ Support/com.bombich.ccc/Scripts/EFIClone-v3-DEBUG.sh / "/Volumes/Catalina Clone - Data" 0 ""

I don't claim to understand how this works, but just to confirm, it should say .../Volumes/Catalina Clone - Data... with Catalina Clone being the destination volume?

Thanks again for working on this. I really appreciate it!

This output looks correct!

 

[byteminer]

No worries, happy to do it! The terminal results are attached below. I used the same terminal command as before but with the name of the script changed.

sudo /Library/Application\ Support/com.bombich.ccc/Scripts/EFIClone-v3-DEBUG.sh / "/Volumes/Catalina Clone - Data" 0 ""

I don't claim to understand how this works, but just to confirm, it should say .../Volumes/Catalina Clone - Data... with Catalina Clone being the destination volume?

Thanks again for working on this. I really appreciate it!

As far as the path to the clone volume goes, your assumption is correct, though you could also just point it straight at "/Volumes/Catalina Clone" instead, the script can figure out the actual data location on its own (when it works). I specifically instructed you to do it this way because I want to emulate the exact arguments that CCC hands to the script, to replicate the actual situation as faithfully as possible. Hence we do it with the "- Data" suffix for now.

The output of the script looks better now, it correctly identifies the two EFI partitions without doubling up on anything, we can see that the entire process ran through without failure, which is good.
I would thus now suggest we try the original script with this slight modification (and the test switch still turned on!) and closely examine its output to determine whether everything is now fixed or whether there's still something off.

To this end I would suggest you try and run the attached modified version of the full EFIClone-v3 script (via Terminal, again) and upload:
- The terminal output
- The EFIClone log file
- The output of the command diskutil list

These three combined will allows us to assess whether everything is now kosher.