How should I do with MaciASL?I'm using QtiASL on Windows but I use MaciASL on macOS.
OMG, it nearly killed me...It's possibly reading it from a different ACPI table.
so far so good, I'm just complaint such weird motherboard...Do what exactly? Didn't you get it working?
MSI like to do there ACPI different to the point that Monterey from beta 3 onwards is unbootable with most if not all MSI X570 and B550 motherboards.so far so good, I'm just complaint such weird motherboard...
yes, it is different with the most of guide.MSI like to do there ACPI different to the point that Monterey from beta 3 onwards is unbootable with most if not all MSI X570 and B550 motherboards.
Nothing you can do about the double click to wake, It’s been that way since Bug Sur, In the past we used the dark wake boot argument to fix the problem but that method no longer works.
as for the sluggish performance after sleep well if you haven’t mapped usb properly then that would cause it or the nvram can also cause it too if it’s not working properly. Try resetting your nvram if you have a proper USBMap.kext.
That’s not going to fix darkwake Bud. There is no fix for that since the boot arguments for it stopped working when BigSur came out. You're flogging a dead horse trying to fix something that isn’t fixable. Just live with it like everybody else with a Intel or AMD hack does. LoLI find some topic here about the wakescreen issue, seems need to modify some patch based on SSDT which is beyond my knowledge, maybe you guys can try it and see if the problem can be solved. @AudioGod
OpenCore-HotPatching-Guide/10-PTSWAK Comprehensive Extension Patch at master · jsassu20/OpenCore-HotPatching-Guide
https://github.com/daliansky/OC-little | Daliansky's guide Translated into English - jsassu20/OpenCore-HotPatching-Guidegithub.com
Hi Bro, I am struggling with the same power management issue with you. Just one question, as I checked my device manager in Windows 10, there is a CPU Bios device name as "_SB.PR00" as well as a CPU's Bios device name as "_SB.PLTF.C000" (exactly same as yours). Why the CPU name is not the "_SB.PR00"?Thanks for the guide, but I failed in making a workable SSDT-PLUG.aml by following this guide. x86platformplugin not loaded properly as before and here are some problems:
1. there is no "processor" can be found from my dumped DSDT file;
2. I find the CPU name is "_SB.PLTF.C000" in Windows device manager, but when I create the SSDT-plug.aml by following the guide and add it into ACPI folder, x86platformplugin can not be loaded as expected.
attached my SSDT-plug for reference, please help to take a look at it.
I have no idea about this till now, maybe the ACPI table is different with Intel. Based on my experience, the x86platformplugin is not work for AMD platform, nothing happens even you make the driver loaded.Hi Bro, I am struggling with the same power management issue with you. Just one question, as I checked my device manager in Windows 10, there is a CPU Bios device name as "_SB.PR00" as well as a CPU's Bios device name as "_SB.PLTF.C000" (exactly same as yours). Why the CPU name is not the "_SB.PR00"?