Sleep problem Kabylake Catalina Opencore

[leopardodenievee]

I´m trying to fix sleep and wake up following the dortanias guide:

GPRW/UPRW/LANC Instant Wake Patch | OpenCore Post-Install

I already do the usb mapping:

GitHub - corpnewt/USBMap: Python script for mapping USB ports in macOS and creating a custom injector kext.

Python script for mapping USB ports in macOS and creating a custom injector kext. - corpnewt/USBMap

github.com

and also the GPRW to XPRW Patch using the SSDT-GPRW but the error still there (related to usb)

universe@iMac-de-Universe ~ % pmset -g log | grep -e "Sleep.*due to" -e "Wake.*due to"
2022-05-31 18:49:25 -0500 Sleep Entering Sleep state due to 'Software Sleep pid=126': Using AC (Charge:0%) 25 secs
2022-05-31 18:49:50 -0500 Wake Wake from Normal Sleep [CDNVA] : due to XHC/HID Activity Using AC (Charge:0%)
2022-05-31 20:29:56 -0500 Sleep Entering Sleep state due to 'Software Sleep pid=128': Using AC (Charge:0%) 15 secs
2022-05-31 20:30:11 -0500 Wake Wake from Normal Sleep [CDNVA] : due to XHC/HID Activity Using AC (Charge:0%)
2022-05-31 20:55:53 -0500 Sleep Entering Sleep state due to 'Software Sleep pid=128': Using AC (Charge:0%) 27 secs
2022-05-31 20:56:20 -0500 Wake Wake from Normal Sleep [CDNVA] : due to XHC/HID Activity Using AC (Charge:0%)
2022-06-01 16:48:57 -0500 Sleep Entering Sleep state due to 'Software Sleep pid=129': Using AC (Charge:0%) 28 secs
2022-06-01 16:49:25 -0500 Wake Wake from Normal Sleep [CDNVA] : due to XHC/HID Activity Using AC (Charge:0%)
2022-06-03 03:38:31 -0500 Sleep Entering Sleep state due to 'Software Sleep pid=127': Using AC (Charge:0%) 34 secs
2022-06-03 03:39:05 -0500 Wake Wake from Normal Sleep [CDNVA] : due to XDCI/HID Activity Using AC (Charge:0%)

Any idea?
Thanks a lot

 

[Edhawk]

Logically if the issue is USB related you need to look at your USB mapping again, as it is probably wrong.

Just one port with an incorrect Connector Type can mess up the Usb configuration.

XHC/HID activity points to mouse, keyboard, webcam or Bluetooth module as the most likely suspects.

 

[leopardodenievee]

Logically if the issue is USB related you need to look at your USB mapping again, as it is probably wrong.

Just one port with an incorrect Connector Type can mess up the Usb configuration.

XHC/HID activity points to mouse, keyboard, webcam or Bluetooth module as the most likely suspects.

Thanks a lot, i will do the usb maping again, have a good sunday @Edhawk

 

[leopardodenievee]

I Remap again using the guide that Dortania tutorial recommends (usbmap by corpnewt), i fixed every conector type

but the error still the same

 

[Edhawk]

The three ports set with Connector Type '8' are incorrect. I know this as you are not mapping the USB port(s) from a phone, and that is the only place you will find a USB port that uses the Connector Type '8'.

No PC's or Mac's have a USB port with the Connector Type '8', ever! An easy way to tell this is wrong is the fact you have a mix of USB3 and USB2 ports, Connector Type '8' is only ever USB2.

You need to look at the physical port and set the type according to the following:

1. Physical USB2 ports with a black tang, should be set as connector Type 0 (USB2). These are the only ports that should be set as USB2.
2. Physical USB3 ports with a Red or Blue tang, should be set as Connector Type 3 (USB3). This goes for any physical USB3 port including 3.0, 3.1 and 3.2 ports, they all share the same Type.
3. Any USB2 ports (virtual ports) served from a USB3 physical port, should be set as Connector Type 3 (USB3), i.e. the same as the physical port.
4. Any ports at the front of the case served from a USB3 header on the motherboard, should be set as Connector Type '3' (USB3), including the virtual USB2 ports served from the header.
5. Any case front ports or Bluetooth connection to a USB2 header on the motherboard, should be set as Connector Type '255' (Internal).
6. A Type-C port that has two ports associated, i.e. when you insert the Type-C device a USB2 port is highlighted, when you remove the Type-C device, flip it 180° and reinsert the device and a USB3 port is highlighted should be set as Connector Type '10' (Type-c without Switch)
7. When you flip a Type-C device and the same port is highlighted then it should be set as Connector Type '9' (Type-c with Switch).

Setting your ports any differently to the list above will result in your kext not working correctly.

Your motherboard has the following USB ports:



You do not have to include the ASMedia USB ports in the USBMap.kext, you can, but they should work without being added to the kext. As they are working from a different USB controller and there are only

That leaves you with a maximum of 24 USB ports from the Chipset:

• 20 from the USB3 (10 x USB3 & 10 x USB2) 6 x ports & 2 x headers, located beside the 24-pin ATX power connector on the motherboard, and
• 4 x Internal ports from the 2 x USB2 headers, which are located along the base of the motherboard below the bottom PCIe x4 slot.

Of these 24 ports you can activate a maximum of 15.

• You may not be using all the Header connectors, so they are the first you should disregard.
• You have no USB2 physical ports, so you should never have a port set with Connector Type '0'.
• Only the ASMedia Type-c port should ever be set as Connector Type '9' or '10', and then only if you include the ASMedia ports in the USBMap.kext.
• 11 of the ports as a minimum will be set as Connector Type '3' (USB3), assuming you are using all 4 ports from the 2 x USB2 Headers.
• If you are not using all 4 ports from the 2 x USB2 Headers then the number of USB3 ports will increase by the number of ports you are not using from the 2 x USB2 headers.

Simples!

 

[leopardodenievee]

Thanks a lot for your time @Edhawk i will do it again

 

[leopardodenievee]

Good afternoon!
i change the usb type

But the error still there, i can see something about power on my boot log but i don´t know what it means

Sorry for being slow