ASRock Z270 Gaming can't wake from Sleep

[Deleted member 188658]

Problem is that I can't wake from sleep. I'm on OS Version 10.3.4.

I believe my problem is some conflict - that I can't resolve - between my NVidia GFX950 and IGPU - HD630 when waking. Because the OS seems to wake but the display/graphics does not appear to wake correctly.

I have extracted the .aml using the Clover F4/F5 functions and attempted to get the patchmatic test to run, but get a

ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20171110/psobject-371)

error but no indication of what device / symbol is in conflict, so I can't resolve it.


Here is the terminal result of my iasl version 3.1 compile:

Tonys-iMac:patchmatic_extraction tonyo$ which iasl
/usr/bin/iasl
Tonys-iMac:patchmatic_extraction tonyo$ iasl -dl -da *.aml

Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20171110(RM)
Copyright (c) 2000 - 2017 Intel Corporation

Input file DSDT.aml, Length 0x2391D (145693) bytes
ACPI: DSDT 0x0000000000000000 02391D (v02 ALASKA A M I    01072009 INTL 20160422)
External object resolution file         SSDT.aml
Input file SSDT.aml, Length 0x377 (887) bytes
ACPI: SSDT 0x0000000000000000 000377 (v01 SataRe SataTabl 00001000 INTL 20160422)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
External object resolution file       SSDT-9.aml
Input file SSDT-9.aml, Length 0x53 (83) bytes
ACPI: SSDT 0x0000000000000000 000053 (v01 PmRef  CpuPm    00003000 INTL 20120320)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
External object resolution file       SSDT-8.aml
Input file SSDT-8.aml, Length 0x103 (259) bytes
ACPI: SSDT 0x0000000000000000 000103 (v01 toleda amihdas1 00003000 INTL 20141107)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
External object resolution file       SSDT-7.aml
Input file SSDT-7.aml, Length 0x2BB (699) bytes
ACPI: SSDT 0x0000000000000000 0002BB (v02 hack   UIAC-ALL 00000000 INTL 20100331)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
External object resolution file       SSDT-6.aml
Input file SSDT-6.aml, Length 0x180 (384) bytes
ACPI: SSDT 0x0000000000000000 000180 (v01 toleda 200s630  00003000 INTL 20160422)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
External object resolution file       SSDT-5.aml
Input file SSDT-5.aml, Length 0x1CA (458) bytes
ACPI: SSDT 0x0000000000000000 0001CA (v01 toleda ami789n  00003000 INTL 20141107)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
External object resolution file       SSDT-4.aml
Input file SSDT-4.aml, Length 0xEDE (3806) bytes
ACPI: SSDT 0x0000000000000000 000EDE (v02 CpuRef CpuSsdt  00003000 INTL 20160422)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
External object resolution file       SSDT-3.aml
Input file SSDT-3.aml, Length 0xA2D (2605) bytes
ACPI: SSDT 0x0000000000000000 000A2D (v02 INTEL  xh_rvp08 00000000 INTL 20160422)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
External object resolution file       SSDT-2.aml
Input file SSDT-2.aml, Length 0x23CB (9163) bytes
ACPI: SSDT 0x0000000000000000 0023CB (v02 PegSsd PegSsdt  00001000 INTL 20160422)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
External object resolution file       SSDT-1.aml
Input file SSDT-1.aml, Length 0x3154 (12628) bytes
ACPI: SSDT 0x0000000000000000 003154 (v02 SaSsdt SaSsdt   00003000 INTL 20160422)
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Pass 1 parse of [DSDT]
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20171110/psobject-371)

I believe it may be something to do with my GFX0 definitions in the *.aml files. But I am too dumb to understand all the instructions in the Forums on how to resolve it.

I have attached my latest debug capture to help.

 

[Deleted member 188658]

Seems like my posting is a /dev/null event.

Just as another data point my Hackintosh on the GA-Z97X-Gaming-5 motherboard with the same GFX-950 Nvidia graphics, goes to sleep/wake cycles like a champ on all the 10.13.x releases up to 10.13.4. ( I have yet to try upgrade to 10.13.5)

Naturally I have tried to clone all my config.plist choices/settings to the ASRock Z270-ITX MB but I can't get that machine to wake reliably. It will perhaps wake once correctly every now and then, but 99% if the time the wake causes a reset/reboot sequence.

So I think it is possible to have High Sierra support sleep/wake cycles. It's our motherboards and our DSDT or ACPI definitions that are the culprits. IMHO.