Sleep/wake issues Big Sur/OpenCore/TUF Gaming Pro/Radeon 5700

[zumsel66]

Hello, I have a a well working config that only gives me one headache: when the machine goes to sleep, it does not wake up again.
Before I moved to OpenCore I had a well working config under Catalina/Clover, where sleep/wake was working fine.
I have gone through a number of EFIs/config.plist that claimed sleep/wake would be fine, but I always ended up with issues.
I have also reset NVRAM and have done the USB Port mapping.
My config.plist is attached. Is there anything that is fundamentally wrong?

ASUS TUF Gaming Pro Z390
Intel i7 8700 @ 3.2GHz
PowerColor Radeon 5700
32 GB RAM

 

[scottkendall]

Hello, I have a a well working config that only gives me one headache: when the machine goes to sleep, it does not wake up again.
Before I moved to OpenCore I had a well working config under Catalina/Clover, where sleep/wake was working fine.
I have gone through a number of EFIs/config.plist that claimed sleep/wake would be fine, but I always ended up with issues.
I have also reset NVRAM and have done the USB Port mapping.
My config.plist is attached. Is there anything that is fundamentally wrong?

ASUS TUF Gaming Pro Z390
Intel i7 8700 @ 3.2GHz
PowerColor Radeon 5700
32 GB RAM

The problem may not be your config but a program or an app preventing sleep:

Check your Activity Monitor to see what apps are preventing sleep.

Also running the following command in the terminal to see what is preventing sleep: pmset -g assertions

You can use hackintool to rest your sleep image.

 

[zumsel66]

Thanks, but when sleep time comes, the machine actually goes to sleep: hard disks spin down, monitor goes off, etc. But then I hear a reboot beep and then nothing. Monitor stays off, machine is not accessible.

 

[scottkendall]

Thanks, but when sleep time comes, the machine actually goes to sleep: hard disks spin down, monitor goes off, etc. But then I hear a reboot beep and then nothing. Monitor stays off, machine is not accessible.

Sorry for my mistake, I ran a checker on your config and the first error that came up was:

You might need something like SSDT-EC.aml or SSDT-EC-USBX-DESKTOP.aml. See the [Acpi Docs]

It also showed a few other errors, you can use the conf checker in OC Configurator or do a search on google for Sanity checker and use that to check your config for errors and correct them. I can not say that fixing the errors will fix your sleep problem but it is a good place to start.

Also, I remember using Darkwake with Catalina but I have not needed it with Big Sur.

 

[zumsel66]

Yes, I have tried configs with SSDT-EC-USBX-DESKTOP.aml as well. I have explicit USB port mapping, that should do I thought.
The actual error seems to be this (from pmset -g log):
2021-01-04 23:06:52 +0100 Sleep Entering Sleep state due to '': Using AC (Charge:0%)
2021-01-04 23:06:52 +0100 Failure Failure during wake: PEG0(),IGPU() : Some drivers failed to handle setPowerState panic
Sleep/Wakes since boot at 2021-01-04 23:02:50 +0100 :0 Dark Wake Count in this sleep cycle:1

I have a 630UHD as iGPU and the Radeon 5700 as dGPU. Both my screens are connected to the Radeon.

Any idea what causes the issues with PEG0() and IGPU()?

 

[scottkendall]

Yes, I have tried configs with SSDT-EC-USBX-DESKTOP.aml as well. I have explicit USB port mapping, that should do I thought.
The actual error seems to be this (from pmset -g log):
2021-01-04 23:06:52 +0100 Sleep Entering Sleep state due to '': Using AC (Charge:0%)
2021-01-04 23:06:52 +0100 Failure Failure during wake: PEG0(),IGPU() : Some drivers failed to handle setPowerState panic
Sleep/Wakes since boot at 2021-01-04 23:02:50 +0100 :0 Dark Wake Count in this sleep cycle:1

I have a 630UHD as iGPU and the Radeon 5700 as dGPU. Both my screens are connected to the Radeon.

Any idea what causes the issues with PEG0() and IGPU()?

Do you have the latest open core 0.6.4 and associated kext? Try removing dark wake. Try turning off the igpu. That is where I would start.

 

[jhax01]

I suspect you're running into a combination of things. You need the EC ssdt regardless of the USB portion to disable your actual EC device and create a fake one. I'd start with that before experimenting in other areas.

 

[starchild2]

Hello, I have a a well working config that only gives me one headache: when the machine goes to sleep, it does not wake up again.
Before I moved to OpenCore I had a well working config under Catalina/Clover, where sleep/wake was working fine.
I have gone through a number of EFIs/config.plist that claimed sleep/wake would be fine, but I always ended up with issues.
I have also reset NVRAM and have done the USB Port mapping.
My config.plist is attached. Is there anything that is fundamentally wrong?

ASUS TUF Gaming Pro Z390
Intel i7 8700 @ 3.2GHz
PowerColor Radeon 5700
32 GB RAM

I have almost the identical system and am having trouble getting bigsur install to even load. Would you mind please sharing your EFI folder from the install usb?

Many thanks.

 

[scottkendall]

I suspect you're running into a combination of things. You need the EC ssdt regardless of the USB portion to disable your actual EC device and create a fake one. I'd start with that before experimenting in other areas.

Yes, they should have it but it not what is causing their sleep issue, their issue is related to the GPU as the PMSET output shows!

Could it be caused by the lack of an EC ssdt? Maybe but as the OP stated they had it previously and it did not resolve the issue. Maybe once the OP sorts the GPU & IGPU interference with wake they will receive a different error caused by the lack of EC SSDT.

 

[jhax01]

My point is that if you want to be successful, correcting the known problems first is the best course of action. Some things aren't always obviously interrelated.