etorix

I did it by hand. To simplify, I begin by temporarily commenting out the Operation CPVS declaration, so that all further references to its objects show up as errors and then track them one by one: Find one, jump to the corresponding object in the tree in MaciASL left panel, go to the next object to find the closing bracket, delete it, go back to the opening section and complete the deletion, check, rinse and repeat. It's somewhat tedious, and not made easier by the many warnings produced when recompiling the base DSDT. (AMD ACPI tables are an awful mess compared with those from Intel systems.) The new inner conditional statements are worse, as they can be quite long, which makes it difficult to find the closing bracket. But it's maybe not necessary to remove these. Anyway, if the patches by @corpghost keep working these are a much, much, better way to go forward.

@kosmos Here are two patched DSDT you may try. The first one follows strictly the method in the first post; 'patched2' then further removes conditional statements on G002 and G001 inside declarations. @Lorys89, please have a look into this. patched.zip

Have you tried ACPI patches in OpenCore instead? This is getting naughty, as I now see conditional statements inside declarations, in addition to conditionational statements wrapping full declarations.

On AM5, security updates in BIOS also brought some breaking changes in DSDT; maybe similar issues are at play here? Have you tried to compare ACPI tables from the older and nwer BIOS, or re-checked memory whitelisting?

There's a non-escaped space in the application path. Do not type paths! Use shell autocompletion (<TAB> key). Something like /A<TAB>Au<TAB>A<TAB>A<TAB> should give the correct syntax ( AutoCAD\ 2022 ). Or wrap the path in quotes.

My proposal: DSDT_patched.aml.zip

"Custom" is your key to disabling Secure Boot. PS. In my experience with Xeons, serial ports are no issue at all. macOS is happy to boot with them, and to display "Serial" among networking possibilities. (I haven't dug up my 33.6k modem to check whether they actually work.)

Do we know what this field is, and what are the expected values for those G0xx? Not all conditions can be met simultaneously (G000): If (((G002 != 0x03) && (G000 == One))) { Scope (\_SB.PCI0.GPP7) { Device (UP00) { If (((G002 != 0x03) && (G000 == 0x02))) { Scope (\_SB.PCI0.GPP7) { Device (XH00) so deleting all the conditions create more ACPI objects than would exist if CPVS were properly processed. Possibly more worryingly, there is some debug-like code (calls to M460) and empty stubs If (((G002 != 0x03) && ((G000 == One) && (G002 == 0x04)))){} so there's a risk that the code will further evolve in future BIOS revisions. Maintaing a database of patched DSDTs for successive BIOS versions of boards of interest is going to be cumbersome.

More fundamentally, I wonder why this extra code prevents macOS from booting. Is macOS unable to read the CPVS region and initialise these G0xx variables? Is it a general issue with macOS? A memory mapping issue? An AMD-specific issue?

If I got it right from @Lorys89, this should be it: patched.zip