Constant Wake From Sleep Issues

[tcolborg]

Hello everyone I recently upgraded some hardware on my unit, and freshly installed Big Sur. I mapped my USB ports and followed the open-core guide for wake issues, but my computer is constantly waking up. I ran the terminal command "grep "Wake Reason" and got the below information but can't figure out what is causing it. Attached is my EFI folder, and would love some help getting this resolved.

 

[Feartech]

Hello everyone I recently upgraded some hardware on my unit, and freshly installed Big Sur. I mapped my USB ports and followed the open-core guide for wake issues, but my computer is constantly waking up. I ran the terminal command "grep "Wake Reason" and got the below information but can't figure out what is causing it. Attached is my EFI folder, and would love some help getting this resolved.

View attachment 535389

XhciPortLimit should be disabled

you seem to have quite a few ports set to internal?

 

[tcolborg]

XhciPortLimit should be disabled

you seem to have quite a few ports set to internal?

I thought I had that disabled. I will have to look.

Are you referring to ports sent to internal in my SSDT files?

 

[Feartech]

I thought I had that disabled. I will have to look.

Are you referring to ports sent to internal in my SSDT files?

your usbports.kext

 

[tcolborg]

Okay this is what I have changed my USB Map kext, you see any issues?

 

[Feartech]

Okay this is what I have changed my USB Map kext, you see any issues?

not sure, will have to see a picture of your hackintool usb section using this configuration...

 

[UtterDisbelief]

Okay this is what I have changed my USB Map kext, you see any issues?

Hi there.

Yes, please check as @Feartech suggested.

Also it is unusual for a motherboard like yours to have HS04 and HS05 set as 'internal' BUT SS04 and SS05 as standard USB3 ports.

Not impossible but unlikely. This would cause instant wakes ...

 

[tcolborg]

Okay, I have redone my kext file for USB mapping but still getting wake issues. Here is my current USB map. Also my terminal "Wake Reason" log.

The only other thing I can think of doing is disabling the BT on the motherboard.

 

[Edhawk]

After a brief review of your EFI folder I would comment as follows:

ACPI:
Current contents of ACPI folder

• You shouldn't have any *.dsl tables in this folder. They are not used.
• As you have a USBPorts.kext you don't need the SSDT-UIAC.aml. You should not have both the USB configuration kext and SSDT present in your setup.
• SSDT-UIAC.aml requires a copy of USBInjectAll.kext to be present in the /OC/Kexts folder. The kext also needs to be enabled in the config.plist if you are using SSDT-UIAC.aml in place of USBPorts.kext.

This is what your revised APCI folder should contain.

• You are missing the SSDT-PLUG.aml, required for native CPU Power Management

Drivers:
You do not need the OpenPartitionDxe.efi driver. This driver is required to boot recovery on OS X 10.7 through 10.9. With your Z490 system I doubt you are using a version of macOS that is as old as Mavericks, never mind Lion.

config.plist:

1. Once you have revised your ACPI and Drivers folders you need to make sure the SSDT's and drivers you removed are also removed from the config.plist. IF you use Corpnewt's ProperTree plist editor then just use the OC Clean Snapshot tool, which can be found in the ProperTree > File dropdown menu.
2. If you are using an SSD (not NVME/M.2) you might want to enable Kernel > Quirks > ThirdPartyDrives. So Trim is enabled for the SSD.
3. If you are wanting to use the OC GUI in place of the Text Picker List, which I assume you are as you have populated the /OC/Resources folder. Then you need to change Misc > Boot > PickerMode to enabled/true.
4. You have Misc > Debug > ApplePanic set to False, this should normally be set as True.
5. OpenPartitionDxe.efi is not enabled in your config.plist so it can be deleted, with no impact on your setup.
6. you have NVRAM > APFS > MinDate and MinKernel set with '0'. These two APFS settings should be '-1' not '0' when running Big Sur or Monterey.

Error screenshot:
This is confusing as the image you provided shows errors and wake calls from a CNVW device, which your motherboard doesn't contain.

A CNVW/CNVI connector usually contains the builtin Intel WiFI/BT card. The CNVW connector also has a USB 2.0 port associated, so the Bluetooth device can connect correctly. This USB port being set incorrectly in the USBPorts.kext is a common cause for systems having instant wake issues.

The RTC (Alarm) calls are usually caused by the lack of an SSDT-AWAC.aml. The SSDT-AWAC.aml in your ACPI folder looks correct, so I am at a loss as to why these two RTC entries are in the list of wake calls.

Assumptions:

• You are using OpenCore 0.7.5 (latest).
• You are running Big Sur or Monterey.

Hope this helps.

 

[tcolborg]

@Edhawk thanks for the information. I went ahead and made the changes you suggested and created the SSDT-Plug File. I also went back through my config.plist and tried to enable the OC GUI. However, now I am having issues even getting it to boot. I then have to go back and boot from my USB drive instead. Not sure what is causing it. Also I am getting the following OCValidate Errors.


OCS: Missing key Comment, context <Drivers>!

OCS: Missing key Comment, context <Drivers>!

OCS: Missing key Comment, context <Drivers>!

OCS: Missing key ReconnectGraphicsOnConnect, context <Output>!

OCS: Missing key UIScale, context <Output>!

Serialization returns 5 errors!

I also get stuck here when rebooting.




Any help would be appreciated.