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

[ZiZet]

** OpenCore 0.7.7 EFI for Z490 Vision D and G **
Supports Catalina, Big Sur, and Monterey
Please do not quote this post in its entirely. Use a link instead.​

...​

Hi there CaseySJ regarding
"
Windows Users:
If you are unable to boot Windows through OpenCore, try disabling AppleVTD by following the bottom half of this post"

I have noticed that on 2 SSD setup Mac+Windows - when AppleVTD is enabled through OpenCore the EFI folder is on Mac SSD, and, when you turnoff AppleVTD, the EFI folder is swapped to the Windows SSD. I don't know why that's the case but it strangle happens. Particularly the setting:

"ACPI --> Delete --> DMAR --> check off"

Can you please check or someone else so when can confirm this?

 

[CaseySJ]

Thanks @CaseySJ I updated my config as per your suggestion and only selected v2 because that is the only one I see any information on your page 1 description. What is v3 for then? I couldn't find anything that gave info on which of the 3 options should be chosen given the VISION-D board.

What's frustrating is that now I can't get either of my two USB front header ports on my case to recognize my USB keyboard, even when I reboot and am just seeing the BIOS loading. It would seem that since this is before OC and MacOS that these USB devices would be recognized. And they were prior to my making the change to only select v2 of the USB SSDT. Ugh. My new Logitech keyboard and mouse come tomorrow so I expect that will resolve my BT kb and mouse going away from wake.

Given my using the VISION-D and a Fenvi T919, is v1, v2, or v3 the recommended SSDT option? Thanks again for all your help. Seems I am close to working out the kinks here.

With V2 we must also enable XhciPortLimit kernel quirk in the Kernel section of config.plist. V2 enables all USB 2 and USB 3 ports, but it exceeds the 15 port limit, hence XhciPortLimit needs to be enabled.

 

[CaseySJ]

Hi there CaseySJ regarding
"
Windows Users:
If you are unable to boot Windows through OpenCore, try disabling AppleVTD by following the bottom half of this post"

I have noticed that on 2 ssd setup mac+windows - when AppleVTD is enabled trough Opencore the EFI folder is on mac ssd and when you turnoff AppleVTD the EFI folder is swapped to the windows ssd. I dont know why thats the case but it strangle happens. Particulary the setting:

"ACPI --> Delete --> DMAR --> check off"

Can you please check or someone else so when can confirm this?

Hello @ZiZet,

The EFI folder should definitely not get swapped. But it is possible that Windows has installed its boot loader on both disks. We can check this as follows:

• Boot into macOS
• Mount EFI partitions of (a) macOS SSD and (b) Windows SSD
• Open each one in Finder and expand just the EFI folder
• Capture screenshot of each one, and post

Screenshot can be captured by pressing CMD-SHIFT-5 then clicking the window. It will be saved to Desktop.

 

[ZiZet]

Hello @ZiZet,

The EFI folder should definitely not get swapped. But it is possible that Windows has installed its boot loader on both disks. We can check this as follows:

• Boot into macOS
• Mount EFI partitions of (a) macOS SSD and (b) Windows SSD
• Open each one in Finder and expand just the EFI folder
• Capture screenshot of each one, and post

Screenshot can be captured by pressing CMD-SHIFT-5 then clicking the window. It will be saved to Desktop.

You are right, silly me... Switching off and on AppleVTD changes Disk order - When Apple VTD is turned ON - mac is Disk0 and windows Disk1 in my case- And Windows doesnt load. When I switch it OFF trough OPC mac is Disk1 and Windows is Disk0 - Windows loads . Does this makes sense?

 

[CaseySJ]

You are right, silly me... Switching off and on AppleVTD changes Disk order - When Apple VTD is turned ON - mac is Disk0 and windows Disk1 in my case- And Windows doesnt load. When I switch it OFF trough OPC mac is Disk1 and windows is Disk0 - windows loads . Does this makes sence?

Disk identifiers can change. We can see these identifiers by running this command in Terminal:

diskutil list

It would be interesting to run this command and post the output with AppleVTD enabled and disabled.

 

[ZiZet]

Disk identifiers can change. We can see these identifiers by running this command in Terminal:

diskutil list

It would be interesting to run this command and post the output with AppleVTD enabled and disabled.

They do change - maybe this could hint a possible fix, hense thats the reason windows not loading

 

[CaseySJ]

They do change - maybe this could hint a possible fix, hense thats the reason windows not loading

Interesting. Couple of questions/comments:

• macOS and Windows are both installed on 512GB SSDs
• Is macOS on NVMe SSD?
  • If so, which slot on motherboard?
• Is Windows also on NVMe SSD?
  • If so, which slot on motherboard?

 

[ZiZet]

Interesting. Couple of questions/comments:

• macOS and Windows are both installed on 512GB SSDs
• Is macOS on NVMe SSD?
  • If so, which slot on motherboard?
• Is Windows also on NVMe SSD?
  • If so, which slot on motherboard?

Both are 512GB NVMe Sabrent SSD same from your guide.
As I recall first slot is mac - second slot is windows. My kids are sleeping I can open it tommorow to confirm but I am 99% sure that was the order.

 

[CaseySJ]

Both are 512GB NVMe Sabrent SSD same from your guide.
As I recall first slot is mac - second slot is windows. My kids are sleeping I can open it tommorow to confirm but I am 99% sure that was the order.

If that's the case, consider doing this:

• Install Windows NVMe into M.2 slot closest to CPU (slot 1)
• Install macOS NVMe into next slot

 

[CaseySJ]

@Karkh,

Welcome to the forum! Please note that most of the guides in this thread say:

"Please do not quote this guide in its entirety."

Please re-post your question, but no need to quote the guides.