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

[MacGeoDoc]

@CaseySJ - I just recently built my system using OC 0.6.4. I'm on the latest version of Big Sur. Everything is working flawlessly! Truly the smoothest hack I have ever built. Is there any reason I need to upgrade to OC 0.6.5 at the present time? I noticed that some people have encountered problems. Am I missing any functionality? I understand that future Apple updates may make updating OC necessary.

 

[CaseySJ]

@CaseySJ - I just recently built my system using OC 0.6.4. I'm on the latest version of Big Sur. Everything is working flawlessly! Truly the smoothest hack I have ever built. Is there any reason I need to upgrade to OC 0.6.5 at the present time? I noticed that some people have encountered problems. Am I missing any functionality? I understand that future Apple updates may make updating OC necessary.

Congratulations! You are the second inductee into the Society of Problem Free Builders! Well, the society has only been around since yesterday so there are more than two problem free builders out there.

In general we should try to keep current with OpenCore releases, but this is not strictly necessary. However, OpenCore Configurator only supports the current release of OpenCore and the next development version. So if you wanted to edit your 0.6.4 config.plist with OpenCore Configurator, you will find that it no longer supports 0.6.4. Instead, it will migrate the config.plist to 0.6.5 format automatically. If you then boot 0.6.4 with this modified config.plist you will encounter OCS: Schema errors/warnings.

You can, however, edit config.plist with a user-unfriendly tool such as PlistPro, XCode, ProperTree, etc.

 

[rtw]

If you have another Bluetooth device in the system such as Fenvi FV-T919 or Bluetooth USB dongle, please physically remove that device.

If you don't have another Bluetooth device, please compress and post your EFI folder, but remove serial numbers from PlatformInfo section of config.plist.

Here's my EFI.

 

[taconugget]

Please describe the glitch:

• It happens only at the macOS Big Sur login screen?
• Is it just a flicker or two (i.e. the screen goes blank for a second or two then comes back)?
• Does it happen just once or does it happen every X minutes?

Thanks for the reply @CaseySJ

-Yes this only happens on the login screen for BigSur. The start up black screen with white apple are fine, then the screen goes black and comes back like this. It only happens when rebooting from Windows.

-I have attached a screenshot so you can see what it does. It's a 2 monitor system. Only happens on the main display. Both monitors are 24" LED Cinema Displays. Both connected via display port.

-The glitch is continuous. Once it starts it continues. I logged in once hoping it would correct itself but not the case.

I thought maybe it was some sort of power issue, so thought maybe power down from windows and then restart, but this didn't correct it either. Basically any time coming from windows, The first start does this till I power down and reboot. Its very strange...

 

[CaseySJ]

Thanks for the reply @CaseySJ

-Yes this only happens on the login screen for BigSur. The start up black screen with white apple are fine, then the screen goes black and comes back like this. It only happens when rebooting from Windows.

-I have attached a screenshot so you can see what it does. It's a 2 monitor system. Only happens on the main display. Both monitors are 24" LED Cinema Displays. Both connected via display port.

-The glitch is continuous. Once it starts it continues. I logged in once hoping it would correct itself but not the case.

I thought maybe it was some sort of power issue, so thought maybe power down from windows and then restart, but this didn't correct it either. Basically any time coming from windows, The first start does this till I power down and reboot. Its very strange...

Does it correct itself if you...

• Disconnect and reconnect the DisplayPort cable from the main display?
• Power cycle the main display?

 

[CaseySJ]

Here's my EFI.

Please try the attached config.plist after copying serial numbers back into PlatformInfo. I changed SecureBootModel to Default instead of Disabled.

 

[rtw]

Please try the attached config.plist after copying serial numbers back into PlatformInfo. I changed SecureBootModel to Default instead of Disabled.

Unfortunately BT still not coming up

 

[CaseySJ]

Unfortunately BT still not coming up

Have you tried resetting NVRAM?

I tested the 0.6.5 version yesterday after physically removing my Fenvi FV-T919, and Intel Bluetooth module activated and worked right away.

 

[darkenergy2020]

Have you tried resetting NVRAM?

I tested the 0.6.5 version yesterday after physically removing my Fenvi FV-T919, and Intel Bluetooth module activated and worked right away.

Can I ask why you removed the fenvi fv-t919, I just bought one.

 

[taconugget]

Does it correct itself if you...

• Disconnect and reconnect the DisplayPort cable from the main display?
• Power cycle the main display?

Yes pulling the display port cable and reconnecting seems to work. At least this time...
No easy way to power cycle the monitor other than yanking the power cord.

Both of these options can work, just have to pull the desk out, and the computer to do them. Wish I could figure out the underlying issue here though...