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

[CaseySJ]

Let me start by thanking everyone on this forum. I've learned a lot from the posts and I usually am able to solve most of the problems I run into by researching the forum.

I updated to 0.72 OC. No problem running Monterey or Big Sur. Now Windows will not boot under OC. If I choose Windows from the picker, it boots into Windows but hangs on the Windows logo. I'm using Windows 11 and there was no problem under 0.71. Windows boots if I boot directly from BIOS. I'm sure its a simple setting in OC but I am at a loss as to what that might be. Internet searches came up with solutions I already tried but did not work. Windows 11, Monterey and Big Sur have their own drives with Windows in the m2 slot closest to the CPU.

Any help will be appreciated.

I can also confirm that OC 0.7.2 will not boot Windows 10 with VT-d disabled and DMAR enabled. I disabled DMAR. Kernel Quirk "DisableIOMapper" was already enabled. Now that DMAR is disabled OC 0.7.2 will boot Windows 10. I have 64GB and WiFi and Ethernet both continue to work. Running Mac OS X 11.4.

I haven't encountered this problem on my Z490 Vision D or Z390 Designare. In both of these systems:

• Windows 10 is installed on its own SSD and has its own EFI partition with the Windows boot loader installed in that partition.

Is your Windows setup the same? Namely, does your Windows SSD contain its own EFI partition with the Windows boot loader?

 

[RandC]

I haven't encountered this problem on my Z490 Vision D or Z390 Designare. In both of these systems:

• Windows 10 is installed on its own SSD and has its own EFI partition with the Windows boot loader installed in that partition.

Is your Windows setup the same? Namely, does your Windows SSD contain its own EFI partition with the Windows boot loader?

Hey Casey,

My Windows and Mac installs are on two different SSD's with their own EFI partition. Board is Z490 Vision D. Before I made the change to disable DMAR I could boot into Windows 10 using F12 and selecting "Windows Boot Manager", but if I let OC boot Widows 10 I would get a black screen. I checked and VT-d was disabled in BIOS. I did notice that I did not have the DMAR setting in the DELETE section of ACPI to disable so I only disabled SSDT-DMAR.aml in the Add section (maybe that is the reason?). Also Kernel Quirk "DisableIOMapper" was already enabled. I'm using the USBMAP.ktext which is different than your release. Other than that I'm not sure what else might be different, so I've enclosed a copy of the OC 0.7.2 config.plist, with serial numbers removed, that will now boot Windows 10. I may have messed up my configuration somehow so that it doesn't work with the modified DMAR table and Windows.

Maybe the reason is my setup is not exactly as described to turn DMAR off. I didn't have DMAR in the DELETE section of ACPI and Kernel Quirk "DisableIOMapper" was enabled?

Rand

 

[CaseySJ]

Hey Casey,

My Windows and Mac installs are on two different SSD's with their own EFI partition. Board is Z490 Vision D. Before I made the change to disable DMAR I could boot into Windows 10 using F12 and selecting "Windows Boot Manager", but if I let OC boot Widows 10 I would get a black screen. I checked and VT-d was disabled in BIOS. I did notice that I did not have the DMAR setting in the DELETE section of ACPI to disable so I only disabled SSDT-DMAR.aml in the Add section (maybe that is the reason?). Also Kernel Quirk "DisableIOMapper" was already enabled. I'm using the USBMAP.ktext which is different than your release. Other than that I'm not sure what else might be different, so I've enclosed a copy of the OC 0.7.2 config.plist, with serial numbers removed, that will now boot Windows 10. I may have messed up my configuration somehow so that it doesn't work with the modified DMAR table and Windows.

Maybe the reason is my setup is not exactly as described to turn DMAR off. I didn't have DMAR in the DELETE section of ACPI and Kernel Quirk "DisableIOMapper" was enabled?

Rand

The OpenCore 0.7.2 EFI folder enables AppleVTD in macOS, which enhances Thunderbolt, but is not strictly necessary unless we're using a Thunderbolt device that requires AppleVTD such as Antelope Audio devices and Apple's own Thunderbolt-to-Gigabit Ethernet adapter.

Enabling AppleVTD requires the following (every single item below is necessary):

1. Kernel --> Quirks --> DisableIoMapper --> check off (affects macOS only)
2. ACPI --> Add --> SSDT-DMAR.aml --> check on (affects all operating systems)
3. ACPI --> Delete --> DMAR --> check on (affects all operating systems)
4. BIOS Setup --> VT-d --> Enabled

Items 1, 2, and 3 affect config.plist and are already present in the OpenCore 0.7.2 EFI. But item 4 has to be done manually. With these changes, OpenCore 0.7.2 has no problem booting my Windows 10 SSDs.

However, AppleVTD is optional. To disable AppleVTD we can do the following:

1. Kernel --> Quirks --> DisableIoMapper --> check on
2. ACPI --> Add --> SSDT-DMAR.aml --> check off
3. ACPI --> Delete --> DMAR --> check off
4. BIOS Setup --> VT-d --> this can be left enabled at all times

 

[RandC]

Hey Casey,

My Windows and Mac installs are on two different SSD's with their own EFI partition. Board is Z490 Vision D. Before I made the change to disable DMAR I could boot into Windows 10 using F12 and selecting "Windows Boot Manager", but if I let OC boot Widows 10 I would get a black screen. I checked and VT-d was disabled in BIOS. I did notice that I did not have the DMAR setting in the DELETE section of ACPI to disable so I only disabled SSDT-DMAR.aml in the Add section (maybe that is the reason?). Also Kernel Quirk "DisableIOMapper" was already enabled. I'm using the USBMAP.ktext which is different than your release. Other than that I'm not sure what else might be different, so I've enclosed a copy of the OC 0.7.2 config.plist, with serial numbers removed, that will now boot Windows 10. I may have messed up my configuration somehow so that it doesn't work with the modified DMAR table and Windows.

Maybe the reason is my setup is not exactly as described to turn DMAR off. I didn't have DMAR in the DELETE section of ACPI and Kernel Quirk "DisableIOMapper" was enabled?

Rand

Casey,

It occurred to me that I had your DMAR enabled but I did not have VT-d enabled in BIOS. So I enabled DMAR again, added the DMAR to the Delete section of ACPI on the Flash Drive. Booted from the Flash Drive and selected Windows 10 again. This time it started booting and told me that it had to do an Automatic repair which didn't work and put me into Troubleshoot Window. I restored Windows from my last restore point and booted again. This time Windows 10 booted. I shut down and booted from Flash Drive again and selected Windows 10 and it booted again.

So the issue appears to be that I did not have VT-d enabled. That may be my mistake. I don't need VT-d and maybe didn't see where I was supposed to enable it in the BIOS of OC 0.7.2.

Rand

 

[RandC]

The OpenCore 0.7.2 EFI folder enables AppleVTD in macOS, which enhances Thunderbolt, but is not strictly necessary unless we're using a Thunderbolt device that requires AppleVTD such as Antelope Audio devices and Apple's own Thunderbolt-to-Gigabit Ethernet adapter.

Enabling AppleVTD requires the following (every single item below is necessary):

1. Kernel --> Quirks --> DisableIoMapper --> check off (affects macOS only)
2. ACPI --> Add --> SSDT-DMAR.aml --> check on (affects all operating systems)
3. ACPI --> Delete --> DMAR --> check on (affects all operating systems)
4. BIOS Setup --> VT-d --> Enabled

Items 1, 2, and 3 affect config.plist and are already present in the OpenCore 0.7.2 EFI. But item 4 has to be done manually. With these changes, OpenCore 0.7.2 has no problem booting my Windows 10 SSDs.

However, AppleVTD is optional. To disable AppleVTD we can do the following:

1. Kernel --> Quirks --> DisableIoMapper --> check on
2. ACPI --> Add --> SSDT-DMAR.aml --> check off
3. ACPI --> Delete --> DMAR --> check off
4. BIOS Setup --> VT-d --> this can be left enabled at all times

Exactly the issue as I finally figured out. Thanks so much for your guidance.

 

[canyondust]

Instead of switching SMBIOS I did this and have Apple Music Lossless working.

defaults write com.apple.AppleGVA gvaForceAMDKE -boolean yes

I will keep an eye out for unintended side effects.

MAJOR SIDE EFFECT: can no longer do QuickTime screen recordings. This is a dealbreaker for my workflow, so I'll likely explore switching to iMacPro 1,1

 

[UtterDisbelief]

MAJOR SIDE EFFECT: can no longer do QuickTime screen recordings. This is a dealbreaker for my workflow, so I'll likely explore switching to iMacPro 1,1

Yes, it may be a system-definition issue. I just tested my Z490 with i5-10600k which uses the AppleGVA Terminal command to restore DRM playback. Using QuickTime to record the screen still works as it should. GPU is an RX560.

 

[canyondust]

Yes, it may be a system-definition issue. I just tested my Z490 with i5-10600k which uses the AppleGVA Terminal command to restore DRM playback. Using QuickTime to record the screen still works as it should. GPU is an RX560.

and you're on SMBIOS iMacPro1,1? Did you use just `defaults write com.apple.AppleGVA gvaForceAMDKE -bool YES` or all of the commands?

 

[UtterDisbelief]

and you're on SMBIOS iMacPro1,1? Did you use just `defaults write com.apple.AppleGVA gvaForceAMDKE -bool YES` or all of the commands?

No, not iMacPro1,1.

That was my point.

You may need to experiment (while disconnected from the Internet to avoid Apple getting suspicious) because the Terminal command does not necessarily affect QuickTime directly. I'm running Mojave and iMac18,3. Many will tell me this is wrong. I disagree, everything works well and reliably. However it is possible that special use cases, such as yours, may need a different definition.

I am using only the one Terminal command you highlight, yes. This is purely because the official Whatevergreen guidance suggests this is all that is needed - and it is for me.

 

[bazzevo]

I switched my SMBIOS to iMacPro1,1 and all problems with Apple music that I described earlier are gone. Apple music is not skipping songs anymore, I can play Lossless and Atmos, all radio shows in Apple music, stream to Airplay devices...

@CaseySJ: I'm pretty sure it's not obvious to everybody that switching the SMBIOS can solve these kind of problems. I even wondered if the problems were tied to my Hackintosh or not. It probably makes sense to add this information to the FAQ.