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

[ChromeGuy]

I have exactly the same problem but with different brands; 1 Evo+ 1TB in first slot, 1 Evo+ 250GB in slot 2. As soon as I put my WD 1TB in slot 3, can't post or boot. The WD does not have to be in the 3rd slot but as soon as I have 3 NMVe SSDs installed on the MB, I can't boot. Only solution I found was to get a PCIEx4 NVMe card installed on the PCIEx4 slot which shared the bandwitdh with the M2 slot #3 but I have nothing installed in slot #3

@emistral Good to know I'm not the only one!

Is it only the WD that makes the #3 slot not work? Have you tried with one of the EVO's in the #3 slot and the WD in #1 or 2?

Are you able to link the PCIEx4 NVMe card you ended up using, just in case I have to go that route?

 

[CaseySJ]

@ChromeGuy,

Is the top M.2 slot empty (M2A)? As @emistral mentioned above, it seems using all three at the same time causes problems in some cases.

 

[ChromeGuy]

@ChromeGuy,

Is the top M.2 slot empty (M2A)? As @emistral mentioned above, it seems using all three at the same time causes problems in some cases.

I've tried with using only M2P, using M2A and M2P, and using M2M and M2P.

Only time it "worked" with the M2P slot occupied, was when only M2P was used. And even then it had the problems mentioned, so I don't consider it working.

I only have the 2 drives, so unable to test all 3 slots used at once.

 

[inapis.crazy]

On Vision G, I sometimes get

OCB StartImage Failed
Halting on CriticalError.

It's like 2 out of every 10 times.

Has anyone else got this error?

Running OC 0.6.0 with 10.15.6

Update here - https://www.tonymacx86.com/threads/...olt-3-i5-10400-amd-rx-580.298642/post-2163098

 

[CaseySJ]

On Vision G, I sometimes get



It's like 2 out of every 10 times.

Has anyone else got this error?

Running OC 0.6.0 with 10.15.6

On my Vision D, both Catalina and Big Sur boot up properly every time (OpenCore 0.6.0). Has this problem been around since the beginning or did it start recently?

 

[jimbojingle]

I haven't got as far as installing Big Sur yet.

Please find a screenshot of my disk volumes.

I notice that my Catalina Volumes are APFS (Encrypted) and the Catalina Backup Volumes are not. Looks Ok otherwise. Not sure if this is how it should be!

But the Catalina Volume still appears named as 'parallels' on the OpenCore Boot Screen. I have tried changing its name but without success. Still shows as 'parallels'.

Feeling a bit confused here!

I have now managed to successfully install Big Sur on a separate SSD as you suggested.

The Big Sur Disk is showing up on the OpenCore Boot GUI named as 'Preboot'. Also when I boot Catalina I just see a folder called update and no Big Sur Disk.

I am still seeing my Catalina Disk named a 'parallels' on the OpenCore Boot GUI.

Where are these strange names being stored?

Also, I have noticed a long pause after the Gigabyte Splash Screen and sometimes it gets stuck there.

 

[inapis.crazy]

On my Vision D, both Catalina and Big Sur boot up properly every time (OpenCore 0.6.0). Has this problem been around since the beginning or did it start recently?

It happened with 0.5.9 with 10.15.5 but way fewer times than 0.6.0 with 10.15.6.

I have Filevault enabled could that be the reason? 10.15.5 gave similar issues without FV2 though.

I am currently staring at it again.

Gooling is pointing to a NVRAM issue though. Let me verify.

EDIT - For those who have this error read this - https://www.tonymacx86.com/threads/...olt-3-i5-10400-amd-rx-580.298642/post-2163098

 

[inapis.crazy]

Well, NVRAM seems to be working fine. Time to check with FV2 disabled.

 

[lightmanrt]

I have now managed to successfully install Big Sur on a separate SSD as you suggested.

The Big Sur Disk is showing up on the OpenCore Boot GUI named as 'Preboot'. Also when I boot Catalina I just see a folder called update and no Big Sur Disk.

I am still seeing my Catalina Disk named a 'parallels' on the OpenCore Boot GUI.

Where are these strange names being stored?

Also, I have noticed a long pause after the Gigabyte Splash Screen and sometimes it gets stuck there.

I've tried with using only M2P, using M2A and M2P, and using M2M and M2P.

Only time it "worked" with the M2P slot occupied, was when only M2P was used. And even then it had the problems mentioned, so I don't consider it working.

I only have the 2 drives, so unable to test all 3 slots used at once.

I have all three M2 slots filled and I am having constant problems with boot. The vision D hangs either right before the bios setup message or after. I usually need to turn off the power supply to get it to boot. At first boot in the morning it starts up normally. From cpu slot to last; Samsung 970 1 TBwindows, Sabret 2 TB, Catalina, Samsung 970 2TB, AV drive. Last PCEI Slot, M2adapter with 500GB Sabret NVMe.

 

[crossmoid]

Understood. Can you quantify the stalls and describe where in the startup sequence they're occurring. For example:

• From power-up to Gigabyte splash screen. How much time?
• From splash screen to OpenCore Picker menu. How much time?
• From OpenCore to macOS Login window. How much time?
• From Login window to when computer is fully responsive and usable. How much time?

Hi Casey,

Ran a few tests using OC 0.6.1 RELEASE and the averages are follows:

From cold boot to Picker Menu (I've got the splash screen disabled) : 20s
From OC to Login: 44s
From Login to Desktop: <15s

According the the logs the main culprit appears to be IONVMeFamily (23s). I'm using a 1tb 970 evo for the Mac side of things - could that be the issue?