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

[zedoc]

Hi,
For me keeping VT-d enabled in BIOS (F5) with or without AppleVTD active in OpenCore makes VirtualBox not booting VMs. (working fine with Vmware Fusion and VT-d)
As i saw that VirtualBox is working for some here with VT-d, i was asking myself if it could maybe be related to my BIOS version (F5)?

 

[MAC_OS]

Please note that Intel Bluetooth does not work in Monterey. If you refer to the OpenCore 0.7.8 mini-guide for this build you will see a section called “Monterey - What does not work”.

Thanks, @CaseySJ. My bad, I didn't read it properly. I decided install the Fenvi FV-T919 again as it's still definitive better option for now.

Another question, I use 'OC-078-Intel-Wireless-VISION-D' with OpenCore 0.8.1. I'm getting the annoying messages before arriving to the bootpicker. What is the easiest way to remove it?

 

[Feartech]

Thanks, @CaseySJ. My bad, I didn't read it properly. I decided install the Fenvi FV-T919 again as it's still definitive better option for now.

Another question, I use 'OC-078-Intel-Wireless-VISION-D' with OpenCore 0.8.1. I'm getting the annoying messages before arriving to the bootpicker. What is the easiest way to remove it?

post 1 explains on how to update opencore

 

[rd3500]

Hi, guys. I built this exact configuration over a year ago (only the case is different), and I have been using it with great success since then. Now I need to go back to boot directly into Windows ,and I have noticed that Windows cannot see Thunderbolt external drives when connected (like a Samsung x5).

I have reprogrammed the Thunderbolt chip at the time, maybe that's the problem under windows now? I tried to search this thread but could not find people with the same problem so I thought I would ask. Thanks a lot.

F05 BIOS and latest version of OpenCore.

 

[CaseySJ]

Hi, guys. I built this exact configuration over a year ago (only the case is different), and I have been using it with great success since then. Now I need to go back to boot directly into Windows ,and I have noticed that Windows cannot see Thunderbolt external drives when connected (like a Samsung x5).

I have reprogrammed the Thunderbolt chip at the time, maybe that's the problem under windows now? I tried to search this thread but could not find people with the same problem so I thought I would ask. Thanks a lot.

F05 BIOS and latest version of OpenCore.

When we flash the Thunderbolt firmware, it enables Thunderbolt Bus in macOS. But it causes problems in Windows and Linux. So if you no longer need to run macOS on this system, then it's highly recommended to flash back the original Thunderbolt firmware.

 

[rd3500]

thanks @CaseySJ, is the original bin available? I used my raspberry last time and since then I changed the image on it. I don't know if I have the original file.

 

[CaseySJ]

@rd3500 @cliffDeane

Attached is the original Thunderbolt NVM 50 for Gigabyte Z490 Vision D.

 

[CaseySJ]

Even modifying directly SSDT-5, dropping the OEM table and injecting the modified table still does not produce GFX0 attachment:
View attachment 548370

GPU device ID spoofing requires WhateverGreen.kext. It's also better to try the earlier, simpler SSDT such as the one I posted.

 

[rd3500]

@rd3500 @cliffDeane

Attached is the original Thunderbolt NVM 50 for Gigabyte Z490 Vision D.

thanks a lot Casey!

 

[slickdawg]

This is so strange. In Big Sur, it loads the dext and works fine. In Monterey, it loads the kext and does not work.

@jaymonkey would you mind sanitizing and sharing your config/EFI?