- Nov 11, 2018
- Gigabyte Z490 Vision D
- RX 580
- Classic Mac
- Mobile Phone
Before we can enable our own DMAR table, we must delete the preexisting one. To delete the preexisting one we can just use Signature = DMAR or we can be even more cautious and use both Signature = DMAR and OemTableId = <Oem Table ID>. This second case is only necessary when there are multiple tables with the same name, but they differ in OemTableID. In other words, using both Signature and OemTableId fields provides a stricter match against the table we wish to delete.Interesting. I missed this part on z590. I'm still confused as to how this is supposed to work.
On my z590 system it appears that the OEM DMAR loads. I say this because under Maciasl->File->New From ACPI, the OEM DMAR is in the list of loaded SSDTs. So adding SSDT-DMAR (which is basically a carbon copy of the OEM DMAR) results in two DMARs loading; (1) the OEM one, and then (2) SSDT-DMAR. So do I even need to load SSDT-DMAR? What's the purpose of SSDT-DMAR when the OEM one is loading? Should I disable the OEM one from loading (don't know how to do that)?
And regarding OEM Table ID, is the strategy here to just delete the OEM Table ID value from the SSDT, using ACPI->delete in OC? These are the values in my OEM DMAR for 'OEM ID' and 'OEM Table ID':
[00Ah 0010 6] Oem ID : "INTEL "
[010h 0016 8] Oem Table ID : "EDK2 "
So do I delete "EDK2 " (with the spaces) using the the ACPI->delete method in OC? In hex, this is: 45 44 4B 32 20 20 20 20.
Just trying to understand what we are to trying to accomplish here.
tinymacx86 is an alias for tonymacx86. The former resolves to the latter.Second unrelated question is “tinymacx86” an official mirror of Tonymac or is that an unaffiliated party? Its showing up in the Google results of content on this site. Never saw it before.