- May 30, 2014
- ASUS WS X299 Sage 10G
- Vega 64
- Mobile Phone
@Thireus I'm not using any additional kext outside of what @kgp provided in the EFI folder. Came home to a panic with the same acpi error.
*Note. I noticed as well once disabled the xcpm_core_scope_msrs © Pike R patch, it prevented my system from sleeping. the display would turn off but not the system. I can tell you now that since enabling, the computer actually responds to sleep again and wakes no problem. Runs fine like when I first was successful with my initial install.
Only thing I changed I believe yesterday was a new lilu kext I seen was released recently which I don't believe has anything to do with this issue. Just though I let you know of all kext changes outside of what @kgp provided
@AnaktuvGod, seems that you are addressing now a different issue and I think I already have the solution.
You are running an Nvidia GPU, right?
In all my previous EFI-Folder distributions, I checked the "nv_spanmodepolicy=1" boot flag in Clover Configurator. The latest release has this boot flag unchecked, as I was made ridiculous by somebody to use this boot flag meant for 5K Displays.
However, as expected from my side, it seems absolutely mandatory to check this boot flag in order to avoid a black screen with Nvidia GPUs on Wake.
If your system is accessible via remote access and the mainboard display shows 30, the issue is definitely your GPU!
Can you please try to check "nv_spanmodepolicy=1" in Section "Boot" of Clover Configurator and see if this solves your new issue.
I am convinced that will work.
I just checked it myself.
Using boot flag "nv_spanmodepolicy=1", everything works as expected.
Not using boot flag "nv_spanmodepolicy=1", black screen on Wake with Nvidia..