Dell Latitude 7300: hibernation/sleep not working

[Cropester]

Hey together,

 

I can't get hibernation/sleep on my DELL Latitude 7300 (Big Sur) to work.

Can someone help me to get this fixed?

 

Intel i7-8665U

Realtek ALC295 audio

Intel Wireless-AC 9560 160MHz

13.3" FHD 1920x1080 LCD

240GB Samsung PM981a NVMe Sams SSD

Intel Cannon Point-LP PCH - USB 3.1 xHCI Host Controller

Intel Cannon Point-LP, Intel Whiskey Lake-U chipset

 

Here is my EFI folder.

https://mega.nz/file/vBIBEBJS#4ErOeUGYt7yc4UZjvhJtoYO05mh2sojOEj05C2U2kF8

 

[Jazzoo]

I wonder your system even boots with the current SSD. It's reported that PM981/a is not working correctly in MacOS. I would start with replacing the ssd first and then continue the troubleshooting.

[Cropester]

I was equally surprised that it works with the SSD. I don't need the hibernation/sleep feature. I just didn't want the laptop to panic every time I closed it. 

I have enabled "Block Sleep" in the BIOS under Power Management. That is enough for me so far. Now it goes into lockscreen when I close the lid. Thanks anyway for the quick reply.

[Jake Lo]

What error did you encounter when you sleep or close the lid?

[Hervé]

OP's setup is not optimised and partly contradictory. For instance:

• SSDT-UIAC patched table and USBPorts kext -> should only have one or the other
• SSDT-EC-USBX_Laptop and SSDT-USBX patches tables -> each with different power settings for USB ports
• SSDT-AC patched table -> really required?

There are probably more patched tables than really necessary and a clean-up needed.

 

SSDT-EC-USBX_Laptop table:

    Scope (\_SB)
    {
        Device (USBX)
        {
            Name (_ADR, Zero)  // _ADR: Address
            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                If (LEqual (Arg2, Zero))
                {
                    Return (Buffer (One)
                    {
                         0x03                                           
                    })
                }
                Return (Package (0x04)
                {
                    "kUSBSleepPortCurrentLimit", 
                    0x0BB8, 
                    "kUSBWakePortCurrentLimit", 
                    0x0BB8
                })
            }

            [...]

}

SSDT-USBX table:

    Scope (\_SB)
    {
        Device (USBX)
        {
            Name (_ADR, Zero)  // _ADR: Address
            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                If (LEqual (Arg2, Zero))
                {
                    Return (Buffer (One)
                    {
                         0x03                                           
                    })
                }
                Return (Package (0x08)
                {
                    "kUSBSleepPowerSupply", 
                    0x13EC, 
                    "kUSBSleepPortCurrentLimit", 
                    0x0834, 
                    "kUSBWakePowerSupply", 
                    0x13EC, 
                    "kUSBWakePortCurrentLimit", 
                    0x0834
                })
            }
        }
    }

 

Disabling sleep functionality in BIOS is a pretty poor workaround to a broken but most useful feature on a laptop...

[Cropester]

I have remapped the USB ports and cleaned up my EFI. I also disabled SSDT-AC and re-enabled sleep in the BIOS. Unfortunately I still run into a kernel panic.

 

Here is my EFI:

https://mega.nz/file/CI5RGTZD#oCdSkJXPxHjD-bY30H7Kw3TPvvNA_LUBZWmua47QizM

 

Thank you for the detailed answer. Do you have any other idea how I can get this fixed?

[Hervé]

Could you try and run without this IOElectrify kext to see if it makes any changes? Remember to reset NVRAM on rebooting after you disable this kext in your OC config.

[Jake Lo]

Post the KP

[Cropester]

Thank you for the quick feedback. I have disabled the IOElectrify.kext and reseted the NVram. But it still runs into a kernel panic. 

"thunderbolt power on failed 0xffffffff\n".

I have uploaded the KP as well. Thanks already.

KP.zip

[Cropester]

After some googling and testing I got it fixed by disabling the SSDT-TB3_RP05.aml. Thanks for the quick help, I will check tomorrow if all functions of the USB-C port still work.