NVMeFix VS SSDTTime

NVMeFix 1.1.1

Maybe... https://github.com/acidanthera/NVMeFix/releases

Add NVMeFix from here: https://github.com/acidanthera/NVMeFix

All the reasons listed here are the same reasons I would give you as to why you should use NVMeFix: https://github.com/acidanthera/NVMeFix/blob/master/README.md

You just have to do an oc snapshot of the config.plist after u add the nvmefix.kekt ( https://github.com/acidanthera/NVMeFix )

UPDATE: I reread the Hardware Limitations, and it seems my nvme drive is causing the issue, i'm gonna try with the NVMEFix to check if it works

That might be your issue, samsung ssd's and apple. Don't get along. Add nvme to fix to your efi https://github.com/acidanthera/NVMeFix/releases/tag/1.1.0

NVMeFix

You didn’t list anything you've already tried, so - Have you tried Fixing Sleep? Even though your 660p is supported, i'd try NVMeFix after going through the list in troubleshooting section.

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).