MaciASL VS SSDTTime

If you have access to macOS than you can download and open this tool https://github.com/acidanthera/MaciASL/releases. Right after you open this tool will show you your DSDT and than you can search for whatever the guide tells you to search for.

Then I assumed that I need an editor that can open .aml/.dsl files and use it to find some text in the DSDT.aml, which then I have to paste into the FixShutdown-USB-SSDT.dsl. For this purpose I used MaciASL (which is also not mentioned in the instructions).

Can't emphasize enough for anyone new - take the time and get a basic understanding of how ACPI tables work. Tools used - OpenCore 0.7.8, ProperTree, ssdtprgen, iASL (MaciASL), SSDTTime, and Hackintool for exploring the Hardware and IOReg. i'm averaging 2:45 on battery; for reference - it's roughly 4 in Windows, and less than 2 in Kubuntu 22.04

Note that do NOT use iasl or maciASL by Rehab (they are old and not updated) instead use the ones by acidanthera, iasl-stable, maciASL

Also make sure to use MaciASL by Acidanthera (link)

You need proper software to do that. Download maciASL: https://github.com/acidanthera/MaciASL

Build SSDT-EC, SSDT-USBX, SSDT-XOSI, SSDT-PLUG, and SSDT-HPET from SSDTTime instead of manually https://github.com/corpnewt/SSDTTime

I'm trying to do a fresh install of Ventura. I tried using SSDTTime from my Catalina at first, only to discover that the option to dump DSDT is disabled by design because that'll not give me the unadulterated DSDT which makes sense.

Precisely, I went through the guide once more, discovered some new tools (like USBToolBox for example) then I did USB mapping + SSDTs (using SSDTTime) by hand (I was not sure that I did them properly in the first place, 3 years ago). Then with those clean SSDTs & kext, I used my old EFI and OCAT to merge everything together. Double checked everything at the end just to be sure that I did not forget a thing and that OCAT did not mess up anything.

I couldn't get past this point in mine without running https://github.com/corpnewt/SSDTTime and enabling `SetupVirtualMap` in Booter Quirks

It's a must though. Every PC is different, even 2 identical models might not have the same ACPI tables.. I would Start here.. There's only a few things you'll really need, especially on these machines. While there's many methods, a clean install of windows NOT booted through OpenCore, using SSDTime is the easiest for most.

I built my own SSDTs using SSDTTime.

OpenCore 0.8.7 / Dumping DSDT use SSDTTime for generate ACPI Tables / Use genSMBIOS for generate MLB (Board Serial), ROM (Mac Address), SystemSerialNumber (Serial), SystemUUID (SmUUID)

[1]: https://www.youtube.com/watch?v=DhN35HNsYDg [2]: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-long.html [3]: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-easy.html [4]: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-easy.html#running-ssdttime [5]: https://github.com/corpnewt/SSDTTime [6]: https://dortania.github.io/Getting-Started-With-ACPI/Universal/ec-methods/manual.html#pnp0c09-already-has-an-sta-method

try mapping usb drive on windows first using USBToolBox as USBInjectAll isn't fully working anymore on Monterey. Also I suggest creating your own SSDT/acpi patches via SSDTTime.

If so, switch back to AppleALC and add SSDT-HPET.aml with the patches in the patches.plist generated in SSDTTime (https://github.com/corpnewt/SSDTTime).