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

[CaseySJ]

Alright cool, so do I need to do anything else before upgrading to 10.15.7 / Big Sur / upgrading OpenCore ?
It's recommended in this post to update kexts:

As long as you're using the OpenCore 0.6.2 or 0.6.3 EFI folders from this build guide you are ready for both 10.15.7 and Big Sur. OpenCore 0.6.3 is preferred.

 

[m4rk0]

Guys,

How's the situation with the i225 chip? Does it work? I was thinking to get a Vision G but need it to be working at 2.5G.

 

[SpinRD]

Correct. Once the M.2 SSD in the caddy is formatted at APFS and GUID Partition Map, and the EFI folder is copied to the EFI partition, then it will become bootable. Just follow the build guide in Post 1 and you should be okay.

Amen.

Hi Casey

I am having all sorts of problems, I fortunately backed up my original system drive and reinstalled a new one but I am still getting random freezes while trying to do basic installation of things.

Is it possible that the RAM could be an issue?

 

[bider]

Hey @CaseySJ, I've updated my OC to the newest 0.6.4 build hoping it will solve the issue with TB hot plug, but the problem still persists. I've tried both SSDT versions and in both cases my RP05 section looks exactly the same. Take a look at my IORegistryExplorer dump. You're our only hope

EDIT: Attached screenshot - SSDT-TB3HP-V2.aml disabled in config.plist

 

[NCMacGuy]

@nss @byteminer,

I found some issues last night with EFIClone and/or Carbon Copy Cloner. Please try the attached experimental script. First remove the quarantine flag in Terminal:

• sudo xattr -d com.apple.quarantine EFIClone-CaseySJ.sh
• chmod +x EFIClone-CaseySJ.sh

From CCC --> Utilities menu, select Reveal CCC's Scripts Folder and copy EFIClone-CaseySJ.sh into that folder. Then, from CCC --> Utilities menu, select Secure CCC's Scripts Folder.

Lastly, attach the new script to your CCC task, from ADVANCED SETTINGS --> AFTER COPYING FILES.

@CaseySJ

I haven't been using a EFIClone script with CCC, but decided to give your experimental script a shot with Big Sur 11.0.1

It cloned the EFI folder correctly, but also created a System Volume Information folder containing two empty folders AadRecoveryPasswordDelete and ClientRecoveryPasswordRotation:





(BTW non-beta Carbon Copy Cloner 5.1.23 (6121) has been released for making bootable Big Sur clones. )

 

[CaseySJ]

@CaseySJ

I haven't been using a EFIClone script with CCC, but decided to give your experimental script a shot with Big Sur 11.0.1

It cloned the EFI folder correctly, but also created a System Volume Information folder containing two empty folders AadRecoveryPasswordDelete and ClientRecoveryPasswordRotation:

View attachment 499082

View attachment 499085

(BTW non-beta Carbon Copy Cloner 5.1.23 (6121) has been released for making bootable Big Sur clones. )

Because EFIClone does not create any new content, those folders already existed in the EFI partition. MacOS does in fact create or store content in the EFI partition.

 

[CaseySJ]

Hey @CaseySJ, I've updated my OC to the newest 0.6.4 build hoping it will solve the issue with TB hot plug, but the problem still persists. I've tried both SSDT versions and in both cases my RP05 section looks exactly the same. Take a look at my IORegistryExplorer dump. You're our only hope

EDIT: Attached screenshot - SSDT-TB3HP-V2.aml disabled in config.plist

Was the IOReg file created with SSDT-TB3HP-V2.aml enabled? But the screenshot was taken with the same SSDT disabled?

We should just use SSDT-TB3HP-V2.aml henceforth. If you have Thunderbolt or USB-C devices, do they work when (a) connected prior to boot, and (b) when hot-plugged?

 

[CaseySJ]

Hi Casey

I am having all sorts of problems, I fortunately backed up my original system drive and reinstalled a new one but I am still getting random freezes while trying to do basic installation of things.

Is it possible that the RAM could be an issue?

Just to be clear...

• You performed a fresh installation of macOS Catalina on the new SSD?
• You did not install either Pro Tools or Cubase on the new system?
• Instead, you just used the new system with stock macOS apps (Safari, TextEdit, Terminal, Music, Photos, Messages, FaceTime, News, Stocks, etc.) and found that even the fresh unmodified installation of macOS is unstable and freezes randomly?
  • If this is the case, then it certainly points to a hardware issue. Checking RAM would certainly be the first thing to do.
  • Also, have you connected an 8-pin power cable to the ATX_12V_4X2 header on the top left of the motherboard?

 

[SpinRD]

Just to be clear...

• You performed a fresh installation of macOS Catalina on the new SSD?
• You did not install either Pro Tools or Cubase on the new system?
• Instead, you just used the new system with stock macOS apps (Safari, TextEdit, Terminal, Music, Photos, Messages, FaceTime, News, Stocks, etc.) and found that even the fresh unmodifiedinstallation of macOS is unstable and freezes randomly?
  • If this is the case, then it certainly points to a hardware issue. Checking RAM would certainly be the first thing to do.
  • Also, have you connected an 8-pin power cable to the ATX_12V_4X2 header on the top left of the motherboard?

This is correct...

the thing I find most puzzling, is trying to figure what is all of a sudden causing these issues? I built my Hack back in August and it has run beautifully, with no issues (OC 0.6.0/ OS10.15.6). Then in the last fortnight or so, it has become unstable. It would sometimes work for hours, then sometimes 10 minutes? I'm generally one of those sorts of people who believe in the 'If it ain't broke' camp and not fussed about latest OS's. I just want a stable system again.

Based on what you have asked here

I have reseated the RAM, as well as doing the same with the power cable.
I have now left it on to see whether it stays on for the day while I am at work.

I will report back on this later (fingers crossed)

 

[emistral]

Ah, that’s a different symptom from the blue screen of death (BSOD) in which an ACPI error message appears.

If Windows boots up properly through F12 (BIOS Boot Menu), then there might be some other conflict happening in OpenCore configuration. It would be necessary to check all the Quirks and Misc settings in OpenCore Configurator.

@CaseySJ, yes, Windows 10 boots fine if I press F12 and select the Windows 10 NVMe drive. I have compared 0.6.1 and 0.6.3 config.plist and here is what I have found:
set in 0.6.3 but not in 0.6.1:

Boot-arg in 0.6.3 has the extra igfxfw=2: agdpmod=pikera alcid=11 keepsyms=1 debug=0x100 dart=0 igfxfw=2
Set in 0.6.3 but not in 0.6.1:

In 0.6.3 the device id has a # in front where it does not in 0.6.1:

In 0.6.3 I have entries in NVRAM->delete whereas I have nothing in 0.6.1:

And that's it. Those are the only differences. The only one I could think of causing the issue is the igfxfw=2. I don't remember exactly why I added it but it is after reading a post in one of those pages.