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

[Lukey1979]

After having saved your BIOS preferences, try a clear CMOS, then optimized settings, reboot, load your Bios preferences, reboot, select your boot disk and try again reset NVRAM ... it is, can be a solution

Ok so all it took was for me to 1. Set Boot Disk in preferences again 2. reboot 3. reset NVRAM again and all works A-OK now. Showing 0.6.7

Thanks for your help

 

[daver111]

And to follow up my post here: https://www.tonymacx86.com/threads/...olt-3-i7-9700k-amd-rx-580.267551/post-2232513

It was booting both Big Sur and Mojave fine, so I decided to wipe the Big Sur install and copy over the Catalina install from my 2012 Retina MacBook Pro, basically my main working setup, onto that drive using Carbon Copy Cloner, then upgraded it after copying it to Big Sur (initially to 11.2 via Install Big Sur, then via system preferences to 11.2.2). After briefly testing how the original Catalina install worked (fine), and then a whole bunch restarts, it appears to be working very well. And these NVMe drives (even the I guess mid-range WD Blue ones I have) are smoking fast, even compared to WD Blue SATA SSDs...

And the "Install" volume that was on the Big Sur drive (wasn't bootable, but would show up on the desktop) is gone after doing this. Perhaps it happened due to when I was upgrading the original Big Sur install from 11.2 to 11.2.2, the two NVMe drives had very different EFI folders, and with one or more of the reboots, it booted using the wrong EFI folder, causing some problem with how it cleaned up after itself (which didn't happen this time, as both EFI folders are the same, and it has native NVRAM working).

As a bonus, I noticed another store had the monitor I bought for this system (Samsung LC32G55T) on sale for $100 less than what I paid for it a couple weeks ago, and the store did a price match.

Now I need to setup a backup system for it, and away we go.

@CaseySJ I did see some posts about using an internal USB splitter to connect both the FENVI card and the front USB 2 ports to the motherboard, but at least some people were having problems with using them, and the computer has more than enough working USB ports that I can use. If anything, I'm looking for a multiport USB3 hub I can have on my desk to conveniently plug/unplug devices as needed, as I prefer to not leave drives connected to the computer when I'm not actively using them (a habit from when they were much easier to corrupt if the computer crashed or the drive was unplugged at the wrong time).

 

[CaseySJ]

I just upgraded to OC 0.6.7 using the files provided and HackinDROM. Everything worked out successfully, but both OpenCore Configurator and Hackintool still report that I'm on 0.6.6? I did delete the old EFI folder and emptied the trash before moving the new one over onto the main drive...

When I run

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

I get:

REL-066-2021-02-02

Can anyone who has installed the update via the zip file provided check whether they actually have version 0.6.7 running?

I seem to be having the same issue. NVRAM does not appear to be able to reset and though OC 0.6.7 is installed, Hackintool sees the correct kext versions, but it thinks OpenCore is still set to 0.6.6.

Sure did reset NVRAM. Its not just Hackintool its also OCC that thinks I still have OC 0.6.6

@CaseySJ Any ideas on what has happened here?

After having saved your BIOS preferences, try a clear CMOS, then optimized settings, reboot, load your Bios preferences, reboot, select your boot disk and try again reset NVRAM ... it is, can be a solution

** To Fix OpenCore Version Reporting **

Please make the following change to config.plist and reboot. Will add this to all OC 0.6.8 EFIs next month (April).

 

[pit512]

Ok so all it took was for me to 1. Set Boot Disk in preferences again 2. reboot 3. reset NVRAM again and all works A-OK now. Showing 0.6.7

Thanks for your help

Maybe you have 2 EFI volumes, one with 0.6.6 and the other with 0.6.7...

 

[jleahy2]

** To Fix OpenCore Version Reporting **

Please make the following change to config.plist and reboot. Will add this to all OC 0.6.8 EFIs next month (April).

That fixed it! Thanks Casey!

 

[yabusa]

I'm having a confusing issue.
I updated to Big Sur, and came to perform a clone using Carbon Copy Cloner.
The cloned hard drive is named "Clone" in disk utility and CCC, however when I boot in, OpenCore shows two macOS drives.
Any idea what I've done?

 

[CaseySJ]

I'm having a confusing issue.
I updated to Big Sur, and came to perform a clone using Carbon Copy Cloner.
The cloned hard drive is named "Clone" in disk utility and CCC, however when I boot in, OpenCore shows two macOS drives.
Any idea what I've done?

Please see:

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

CaseySJ's Comet Lake-S in BeQuiet! Pure Base 500DX: Gigabyte Z490 Vision-D - i5-10400 - UHD 630 - AMD RX 580 (Please do not quote this guide in its entirety. Post a link instead.) (See this post for how to refer to a Guide or Mini-Guide.) Refer to the Z390 Designare thread for answers to a...

www.tonymacx86.com

 

[memomemonline]

Platform ID is not right. Can you please post your config.plist with serial numbers removed from SMBIOS section?

Hey @CaseySJ, here is attached, thank you so much for your help

 

[docfiru]

** To Fix OpenCore Version Reporting **

Please make the following change to config.plist and reboot. Will add this to all OC 0.6.8 EFIs next month (April).

Sadly, this didn't work for me Hackintool and OpenCoreConfigurator still see 0.6.7 despite doing the above and resetting NVRAM.

I think I'll just run as is until next month when 0.6.8 hits. Everything seems to be working fine.

 

[CaseySJ]

Hey @CaseySJ, here is attached, thank you so much for your help

Please try the attached config.plist:

• Copy serial numbers back into SMBIOS
• Rename to config.plist or leave the name as-is and choose it explicitly from Clover Boot Menu