Contribute
Register

ASUS N56JN (Haswell, Deep Sleep causes Reboot) [DSDT/SSDT attached]

DSDT warning/optimization count

  • 0

    Votes: 0 0.0%
  • 0-30

    Votes: 0 0.0%
  • 30-100

    Votes: 0 0.0%
  • >100

    Votes: 1 100.0%

  • Total voters
    1
Status
Not open for further replies.
Thank you for help very much.

Moved, PStates/Cstates - False.
Got 0 for Power Management, yeah. My aim is for disabling discrete right now.
Shame on me, as a programmer, but I'm really stuck with this one.

Code:
            <string>SSDT-0.aml</string>
            <string>SSDT-1.aml</string>
            <string>SSDT-2.aml</string>
            <string>SSDT-3x.aml</string>
            <string>SSDT-4x.aml</string>
            <string>SSDT-5x.aml</string>
            <string>SSDT-6.aml</string>
            <string>SSDT-7.aml</string>
            <string>SSDT-8.aml</string>
            <string>SSDT-9.aml</string>
            <string>SSDT-10.aml</string>
            <string>SSDT-11.aml</string>

New order.
Is it okay?

Moved from -8 to DSDT, still nothing.
New DSDT/SSDT (changed only) attached, new IOreg attached

It is nonsense to include dynamic SSDTs in ACPI/patched since they shouldn't be in ACPI/patched.

Seems like you didn't read my note regarding the EC related code in SGOF.

In any case, need all files requested in "Problem Reporting"
 
It is nonsense to include dynamic SSDTs in ACPI/patched since they shouldn't be in ACPI/patched.

Seems like you didn't read my note regarding the EC related code in SGOF.

In any case, need all files requested in "Problem Reporting"

Thanks for help.
EC - done.
Moved from -8 to DSDT, that's why I included it.

Attached.
--removed dynamic ssdt's, just ignore it, please---
 

Attachments

  • 1708WED155.zip
    4.3 MB · Views: 51
EC - done.
Moved from -8 to DSDT, that's why I included it.

Attached.

ACPI is not patched correctly. There is no accommodation for _OSI("Darwin") for example (OS Check Fix patches).

You should probably attempt to debug the _OFF code (and things it calls) with ACPIDebug.kext.

Note: I'm not sure why you think it isn't working... From ioreg, I see no second (Nvidia) GPU.
 
Note: I'm not sure why you think it isn't working... From ioreg, I see no second (Nvidia) GPU.
But System Profiler says it does work :( Screenshot attached.

Thank you.
I'm not good at reverse engineering, can't debug this, sorry.

About ACPI patches: Well, OS Check Fix made some struggle with DSDT. For example - sleep didn't work.
 

Attachments

  • Снимок экрана 2016-08-17 в 2.06.59.png
    Снимок экрана 2016-08-17 в 2.06.59.png
    105.5 KB · Views: 119
But System Profiler says it does work :( Screenshot attached.

Thank you.
I'm not good at reverse engineering, can't debug this, sorry.

About ACPI patches: Well, OS Check Fix made some struggle with DSDT. For example - sleep didn't work.

You need to patch ACPI as per guide. Many times, _OFF behavior is dependent on Windows version.

ACPIDebug can be useful in determining what the problem is. But you'll need to have the motivation to learn it. I can't do it for you.
 
You need to patch ACPI as per guide. Many times, _OFF behavior is dependent on Windows version.

ACPIDebug can be useful in determining what the problem is. But you'll need to have the motivation to learn it. I can't do it for you.
Done.
Still nothing.


I'll try, as I'll return to my city.

IDEA: If you don't see it on IOreg, maybe it's done after start? For example, maybe I left traces somewhere on _WAK?
Or it's stupid?
 
IDEA: If you don't see it on IOreg, maybe it's done after start? For example, maybe I left traces somewhere on _WAK?
Or it's stupid?

Keep in mind sometimes it requires a *specific* version of Windows....

I found it in ioreg. It was hiding a bit (partially disabled).

You should trace the methods with ACPIDebug.kext. It will help you determine where the mistake is...
 
Keep in mind sometimes it requires a *specific* version of Windows....

I found it in ioreg. It was hiding a bit (partially disabled).

You should trace the methods with ACPIDebug.kext. It will help you determine where the mistake is...


Thank you.
Figured it out.
ACPIDebug is actually useful.
 

Attachments

  • Снимок экрана 2016-08-20 в 21.31.24.png
    Снимок экрана 2016-08-20 в 21.31.24.png
    54.4 KB · Views: 124
Thank you.
Figured it out.
ACPIDebug is actually useful.

For others with the same laptop, you might want to detail your findings/solution.
 
Status
Not open for further replies.
Back
Top