CaseySJ
Moderator
- Joined
- Nov 11, 2018
- Messages
- 22,040
- Motherboard
- Asus ProArt Z690-Creator
- CPU
- i7-12700K
- Graphics
- RX 6800 XT
- Mac
- Classic Mac
- Mobile Phone
Hi Jay,Hi CaseySJ,
I enabled AppleVTD a while a go and its working fine on my 490 Vision G using the methods detailed earlier in the thread, no issues with memory or network devices.
However i'm wondering if injecting SSDT-DMAR with the Reserved Memory Regions removed is going to cause issues when booting Windows 10 via OpenCore ?
As you know with most SSDT's we can create a _STA method to check for "Darwin" and return a status flag accordingly (eg: SSDT-DMAC), however as SSDT-DMAR is a memory mapping table as opposed to a device or method based table we can't use the _STA solution.
For now i'm booting Windows 10 (on the very rare occasions i have to) via F12 - boot device override and booting Windows via the Microsoft Boot Manager. It's quite possible that the modified SSDT-DMAR table wont cause issues with Windows 10 but i have not tried it yet.
Just wondering if you or anyone else has considered this and if so found a work around ?
I've tried trawling the internet to see if i can find an answer but so far nothing ....
Cheers
Jay
Good question. Although I've used Windows successfully with the modified DMAR (Direct Memory Address Remap) table, I've not encountered any issues. But I am not using Thunderbolt audio interfaces or any other particularly complex device.
One anecdotal piece of evidence is this:
- Many of us who modified our DMAR tables run dual boot systems (Window and macOS).
- So far no one has reported any issue in Windows...so far.