Jump to content

HP Envy 17t-j000 Quad (Haswell) + 10.8.5/10.9.5/10.10.x/10.11.x/10.12.x/10.13.x/10.14.x

gygabyte666

By gygabyte666,
in Laptops

 Share
1,321 posts in this topic

Recommended Posts

gygabyte666
gygabyte666
Posted
  • Author
Posted

Yes, post #282...

 

Attached is the SSDT in the ioreg from that post with added debugging info only. And maybe I didn't make this clear last time, this SSDT is to *replace* the same SSDT in your CLOVER/ACPI/patched folder, *not* to be added as an additional SSDT.

 

Please reply with ACPIDebug output in system.log (hopefully not all FFFs).

Apologizes for the late reply. Just got some time to do this. Anyway, yes, I knew that I had to replace my GFX SSDT with the one you sent me. I did that with the previous SSDT you sent as well as the new one. Results are below. On a side note, here are two ioregs one of them was made with my display injector (with working brightness) and both debug kexts, the other includes the same but also has ACPIBacklight too. envy_02022014.zip

 

I also ran another set of tests but they all sadly look very familiar to me. I'll post them anyway since I went through the hassle and maybe there is something in there that means something to you that I can't see.

 

TEST#1 (includes working display injector, both debug kexts)

PRE-DISPLAY-SLEEP:

2/2/14 4:26:52.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810243becc)
2/2/14 4:26:52.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:26:53.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102aa3ecc)
2/2/14 4:26:53.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:26:54.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102a73ecc)
2/2/14 4:26:54.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:26:55.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff80f8cebecc)
2/2/14 4:26:55.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:26:56.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810298becc)
2/2/14 4:26:56.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:26:57.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102453ecc)
2/2/14 4:26:57.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:26:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810298becc)
2/2/14 4:26:58.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:26:59.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff80f8cebecc)
2/2/14 4:26:59.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:00.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810243becc)
2/2/14 4:27:00.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:01.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff80f8cebecc)
2/2/14 4:27:01.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:02.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102aa3ecc)
2/2/14 4:27:02.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:03.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff81020d3ecc)
2/2/14 4:27:03.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:04.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102453ecc)
2/2/14 4:27:04.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:05.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102ac3ecc)
2/2/14 4:27:05.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:06.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff81029fbecc)
2/2/14 4:27:06.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:07.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102a3becc)
2/2/14 4:27:07.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:08.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102a23ecc)
2/2/14 4:27:08.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:09.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102183ecc)
2/2/14 4:27:09.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:10.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810243becc)
2/2/14 4:27:10.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:11.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102a33ecc)
2/2/14 4:27:11.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:12.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810298becc)
2/2/14 4:27:12.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:13.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff81029fbecc)
2/2/14 4:27:13.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:14.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8113abbecc)
2/2/14 4:27:14.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:15.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff80f8c93ecc)
2/2/14 4:27:15.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:16.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102183ecc)
2/2/14 4:27:16.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:17.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810297becc)
2/2/14 4:27:17.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:27:18.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff81021cbecc)
2/2/14 4:27:18.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }

AFTER-DISPLAY-SLEEP:

2/2/14 4:28:45.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810243becc)
2/2/14 4:28:45.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:46.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102a3becc)
2/2/14 4:28:46.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:47.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff81021d3ecc)
2/2/14 4:28:47.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:48.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8113acbecc)
2/2/14 4:28:48.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:49.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810297becc)
2/2/14 4:28:49.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:50.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102aabecc)
2/2/14 4:28:50.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:51.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8113abbecc)
2/2/14 4:28:51.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:52.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff80f8c93ecc)
2/2/14 4:28:52.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:53.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff81021cbecc)
2/2/14 4:28:53.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:54.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810243becc)
2/2/14 4:28:54.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:55.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff80f8c93ecc)
2/2/14 4:28:55.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:56.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff81020d3ecc)
2/2/14 4:28:56.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:57.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff81029ebecc)
2/2/14 4:28:57.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff8102a33ecc)
2/2/14 4:28:58.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:28:59.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802284d300, 0xffffff810243becc)
2/2/14 4:28:59.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }

TEST#2 (includes working display injector, both debug kexts AND ACPIBacklight)

PRE-DISPLAY-SLEEP:

2/2/14 4:36:04.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8101ea3ecc)
2/2/14 4:36:04.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:05.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81021dbecc)
2/2/14 4:36:05.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:06.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81029e3ecc)
2/2/14 4:36:06.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:07.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8101ea3ecc)
2/2/14 4:36:07.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:08.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810066becc)
2/2/14 4:36:08.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:09.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8102a43ecc)
2/2/14 4:36:09.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:10.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81021f3ecc)
2/2/14 4:36:10.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:11.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81005f3ecc)
2/2/14 4:36:11.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:12.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810063becc)
2/2/14 4:36:12.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:13.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8102633ecc)
2/2/14 4:36:13.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:14.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8102a13ecc)
2/2/14 4:36:14.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:15.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810066becc)
2/2/14 4:36:15.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:16.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81005b3ecc)
2/2/14 4:36:16.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:17.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81005f3ecc)
2/2/14 4:36:17.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:18.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810247becc)
2/2/14 4:36:18.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:19.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810248becc)
2/2/14 4:36:19.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:20.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810248becc)
2/2/14 4:36:20.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:21.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:21.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8102a03ecc)
2/2/14 4:36:22.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810248becc)
2/2/14 4:36:22.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:23.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810248becc)
2/2/14 4:36:23.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:24.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8102a03ecc)
2/2/14 4:36:24.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:25.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81024abecc)
2/2/14 4:36:25.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:26.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810251becc)
2/2/14 4:36:26.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:27.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8102633ecc)
2/2/14 4:36:27.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:28.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81005f3ecc)
2/2/14 4:36:28.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:29.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81005f3ecc)
2/2/14 4:36:29.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:36:30.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8103693ecc)
2/2/14 4:36:30.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }

AFTER-DISPLAY-SLEEP:

2/2/14 4:37:43.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810249becc)
2/2/14 4:37:43.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:44.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810249becc)
2/2/14 4:37:44.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:45.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81005b3ecc)
2/2/14 4:37:45.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:46.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81005b3ecc)
2/2/14 4:37:46.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:47.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81005b3ecc)
2/2/14 4:37:47.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:48.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810249becc)
2/2/14 4:37:48.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:49.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810066becc)
2/2/14 4:37:49.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:50.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810252becc)
2/2/14 4:37:50.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:51.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81024abecc)
2/2/14 4:37:51.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:52.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810067becc)
2/2/14 4:37:52.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:53.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810249becc)
2/2/14 4:37:53.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:54.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8103693ecc)
2/2/14 4:37:54.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:55.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff80f8d8becc)
2/2/14 4:37:55.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:56.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff8102a1becc)
2/2/14 4:37:56.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:57.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810251becc)
2/2/14 4:37:57.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810247becc)
2/2/14 4:37:58.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:37:59.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81024abecc)
2/2/14 4:37:59.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:38:00.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810249becc)
2/2/14 4:38:00.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:38:01.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810368becc)
2/2/14 4:38:01.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:38:02.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:38:02.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff80f8d8becc)
2/2/14 4:38:03.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810251becc)
2/2/14 4:38:03.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:38:04.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff810247becc)
2/2/14 4:38:04.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:38:05.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff80228c3300, 0xffffff81021dbecc)
2/2/14 4:38:05.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }

TEST#1a (includes both debug kexts, NO working display injector)

PRE-DISPLAY-SLEEP:

2/2/14 4:43:36.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff81024e3ecc)
2/2/14 4:43:36.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:37.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810067becc)
2/2/14 4:43:37.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:38.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:38.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff81021cbecc)
2/2/14 4:43:39.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102b7becc)
2/2/14 4:43:39.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:40.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff80f8dbbecc)
2/2/14 4:43:40.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:41.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102693ecc)
2/2/14 4:43:41.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:42.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102573ecc)
2/2/14 4:43:42.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:43.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff81157bbecc)
2/2/14 4:43:43.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:44.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff81006e3ecc)
2/2/14 4:43:44.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:45.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff81006e3ecc)
2/2/14 4:43:45.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:46.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102693ecc)
2/2/14 4:43:46.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:47.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff81033b3ecc)
2/2/14 4:43:47.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:48.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810060becc)
2/2/14 4:43:48.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:49.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff81024f3ecc)
2/2/14 4:43:49.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:50.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102b7becc)
2/2/14 4:43:50.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:51.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8103803ecc)
2/2/14 4:43:51.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:52.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102683ecc)
2/2/14 4:43:52.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:53.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102b73ecc)
2/2/14 4:43:53.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:54.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102b73ecc)
2/2/14 4:43:54.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:55.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8103803ecc)
2/2/14 4:43:55.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:56.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102b7becc)
2/2/14 4:43:56.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:57.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102693ecc)
2/2/14 4:43:57.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102bbbecc)
2/2/14 4:43:58.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:43:59.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102c03ecc)
2/2/14 4:43:59.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:00.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102b73ecc)
2/2/14 4:44:00.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:01.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102b7becc)
2/2/14 4:44:01.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:02.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810062becc)
2/2/14 4:44:02.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:03.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102bbbecc)
2/2/14 4:44:03.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:04.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810067becc)
2/2/14 4:44:04.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, } 

AFTER-DISPLAY-SLEEP:

2/2/14 4:44:46.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:46.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810069becc)
2/2/14 4:44:47.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810069becc)
2/2/14 4:44:47.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:48.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102c03ecc)
2/2/14 4:44:48.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:49.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810250becc)
2/2/14 4:44:49.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:50.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff80f2d43ecc)
2/2/14 4:44:50.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:51.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810067becc)
2/2/14 4:44:51.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:52.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810067becc)
2/2/14 4:44:52.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:53.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102523ecc)
2/2/14 4:44:53.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:54.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff80f8dcbecc)
2/2/14 4:44:54.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:55.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810225becc)
2/2/14 4:44:55.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:56.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff81006e3ecc)
2/2/14 4:44:56.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:57.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810250becc)
2/2/14 4:44:57.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810069becc)
2/2/14 4:44:58.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:44:59.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810069becc)
2/2/14 4:44:59.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:45:00.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff810250becc)
2/2/14 4:45:00.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:45:01.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff8102b7becc)
2/2/14 4:45:01.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:45:02.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff80f2d43ecc)
2/2/14 4:45:02.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:45:03.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff80f2d43ecc)
2/2/14 4:45:03.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:45:04.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff8022923300, 0xffffff81024f3ecc)
2/2/14 4:45:04.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, } 

TEST#2a (includes both debug kexts, NO working display injector)

PRE-DISPLAY-SLEEP:

2/2/14 4:49:56.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8113aebecc)
2/2/14 4:49:56.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:49:57.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81025ebecc)
2/2/14 4:49:57.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:49:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8100653ecc)
2/2/14 4:49:58.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:49:59.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029abecc)
2/2/14 4:49:59.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:00.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029a3ecc)
2/2/14 4:50:00.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:01.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029fbecc)
2/2/14 4:50:01.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:02.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8102423ecc)
2/2/14 4:50:02.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:03.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff80f8ccbecc)
2/2/14 4:50:03.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:04.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029ebecc)
2/2/14 4:50:04.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:05.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8102473ecc)
2/2/14 4:50:05.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:06.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8102473ecc)
2/2/14 4:50:06.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:07.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029ebecc)
2/2/14 4:50:07.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:08.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029abecc)
2/2/14 4:50:08.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:09.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:09.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029ebecc)
2/2/14 4:50:10.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff810059becc)
2/2/14 4:50:10.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:11.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8100653ecc)
2/2/14 4:50:11.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:12.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff810059becc)
2/2/14 4:50:12.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, } 

AFTER-DISPLAY-SLEEP:

2/2/14 4:50:56.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8102bbbecc)
2/2/14 4:50:56.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:57.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff80f8cbbecc)
2/2/14 4:50:57.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff80f8cbbecc)
2/2/14 4:50:58.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:50:59.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff80f8ccbecc)
2/2/14 4:50:59.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:00.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff810056becc)
2/2/14 4:51:00.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:01.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8102a1becc)
2/2/14 4:51:01.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:02.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8102a1becc)
2/2/14 4:51:02.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:03.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8100583ecc)
2/2/14 4:51:03.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:04.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff80f8d2becc)
2/2/14 4:51:04.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:05.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81025ebecc)
2/2/14 4:51:05.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:06.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029ebecc)
2/2/14 4:51:06.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:07.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8100653ecc)
2/2/14 4:51:07.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:08.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8100603ecc)
2/2/14 4:51:08.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:09.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff80f8d2becc)
2/2/14 4:51:09.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:10.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff8102a1becc)
2/2/14 4:51:10.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:11.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029ebecc)
2/2/14 4:51:11.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:12.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff81029abecc)
2/2/14 4:51:12.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
2/2/14 4:51:13.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff802286e300, 0xffffff80f8d2becc)
2/2/14 4:51:13.000 PM kernel[0]: ACPIDebug: { "POLL.FCPU", 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, }
Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

Apologizes for the late reply. Just got some time to do this. Anyway, yes, I knew that I had to replace my GFX SSDT with the one you sent me. I did that with the previous SSDT you sent as well as the new one. Results are below. On a side note, here are two ioregs one of them was made with my display injector (with working brightness) and both debug kexts, the other includes the same but also has ACPIBacklight too. attachicon.gifenvy_02022014.zip

 

I also ran another set of tests but they all sadly look very familiar to me. I'll post them anyway since I went through the hassle and maybe there is something in there that means something to you that I can't see.

 

...

Out of ideas here... Something is wrong with your DSDT/SSDT setup where the BAR1 address is maybe not calculated correctly (you could print it from the traces and compare to the value on Windows). Or the SystemMemory is not being wired up correctly, or your system deals very differently with the backlight (not likely).

 

So far, there's a lot of success using the patches + ACPIBacklight (personally, just got a new Lenovo U430, Haswell i7-4500U and it works great).

Link to comment
Share on other sites
gygabyte666
gygabyte666
Posted
  • Author
Posted
Out of ideas here... Something is wrong with your DSDT/SSDT setup where the BAR1 address is maybe not calculated correctly (you could print it from the traces and compare to the value on Windows). Or the SystemMemory is not being wired up correctly, or your system deals very differently with the backlight (not likely).

 

So far, there's a lot of success using the patches + ACPIBacklight (personally, just got a new Lenovo U430, Haswell i7-4500U and it works great).

 

Well, that sucks. Honestly though, I'm not terribly worried about it since the AppleBacklight method is working well and that's better than having no backlight support at all.

 

That said, I'll look into it when I can. That's very odd considering I had to get my display's BAR1 for my original display injector. Perhaps I overlooked something or maybe having a second GFX card is causing a mixup somehow. I'm wondering too if my 10.9.1 update using the model-specific update is causing trouble now too. Guess I won't know until 10.9.2 is out.

 

What would be the best way for me to check the BAR1 with Windows? Same question for the wiring of SystemMemory? Thanks.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

Well, that sucks. Honestly though, I'm not terribly worried about it since the AppleBacklight method is working well and that's better than having no backlight support at all.

 

That said, I'll look into it when I can. That's very odd considering I had to get my display's BAR1 for my original display injector. Perhaps I overlooked something or maybe having a second GFX card is causing a mixup somehow. I'm wondering too if my 10.9.1 update using the model-specific update is causing trouble now too. Guess I won't know until 10.9.2 is out.

 

What would be the best way for me to check the BAR1 with Windows? Same question for the wiring of SystemMemory? Thanks.

I would add some debug traces that print the value of BAR1 from the POLL.FCPU method. Just a debug trace:

                \rmdt.p2("IGPU.BAR1", \_SB.PCI0.IGPU.BAR1)
Then you can see if it is reading the BAR1 value from the PCI_config for IGPU correctly. Compare BAR1 value against the value you see in Windows.

 

I had the 11,2 10.9.1 update on my Haswell and this stuff was working fine there too...

 

Have you looked at my DSDT/SSDT patching repo? I've got a slick setup there (if a bit developer oriented... using shell scripts and make) that automates the process of patching DSDT/SSDT from Linux native and installing it. It would need some adaptation for your setup as you have nvidia, and that might throw off where the GFX0 SSDT is as far as numbering.

 

And yes, I suppose it is possible that your attempts to get your nvidia recognized could be causing issues.

Link to comment
Share on other sites
Demonbane
Demonbane
Posted
Posted

Hi gygabyte666,

 

how did you config your clover to load the ssdt-1/2. i found that even if i set <dropoem> in SSDT, clover didn't load my own ssdt. could i have a look at your config.plist? 

 

thanks in advance


and another question, do you now already shut off the nvidia graphic card? i checked your ssdt-1.amd(11.07.2013), and haven't seen any implementation of that.

 

i found that the _OFF method exists in clean_ssdt-0, but you haven't integrated it into your ssdt?

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

Hi gygabyte666,

 

how did you config your clover to load the ssdt-1/2. i found that even if i set <dropoem> in SSDT, clover didn't load my own ssdt. could i have a look at your config.plist?

Clover will load SSDT-1.aml or SSDT-2.aml (and so on) if placed in /EFI/CLOVER/acpi/patched. There is no special configuration required in config.plist to control what SSDTs load from that directory.

Link to comment
Share on other sites
Demonbane
Demonbane
Posted
Posted

Clover will load SSDT-1.aml or SSDT-2.aml (and so on) if placed in /EFI/CLOVER/acpi/patched. There is no special configuration required in config.plist to control what SSDTs load from that directory.

 

okay, i'll check the log if it's loaded.

 

btw, Rehabman, i have tried your method to dissamble the dsdt&ssdt, but when i run "./iasl5 -e SSDT-1.aml SSDT-2.aml SSDT-3.aml SSDT-4.aml -d DSDT.aml" to dissabmle my DSDT, but the result turns to be SSDT-1.dsl + SSDT-2.dsl + SSDT-3.dsl + SSDT-4.dsl, but not the DSDT.dsl as supposed. Why? 

 

here is the log.

Demonbanes-MacBook-Air:DSDT+SSDT-2.24 Demonbane$ ./iasl5 -e SSDT.aml SSDT-1.aml SSDT-2.aml SSDT-3.aml SSDT-4.aml -d DSDT.aml 

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20130725-64 [Jul 30 2013]
Copyright (c) 2000 - 2013 Intel Corporation

Binary file appears to be a valid ACPI table, disassembling
Loading Acpi table from file SSDT-1.aml
Acpi table [SSDT] successfully installed and loaded
Loading Acpi table from file SSDT.aml
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    SSDT-1.dsl - 13122 bytes
Loading Acpi table from file SSDT-2.aml
Acpi table [SSDT] successfully installed and loaded
Loading Acpi table from file SSDT.aml
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed

Found 6 external control methods, reparsing with new information
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    SSDT-2.dsl - 90636 bytes

iASL Warning: There were 6 external control methods found during
disassembly, but only 0 was resolved (6 unresolved). Additional
ACPI tables are required to properly disassemble the code. The
resulting disassembler output file may not compile because the
disassembler did not know how many arguments to assign to the
unresolved methods.
Loading Acpi table from file SSDT-3.aml
Acpi table [SSDT] successfully installed and loaded
Loading Acpi table from file SSDT.aml
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    SSDT-3.dsl - 15320 bytes
Loading Acpi table from file SSDT-4.aml
Acpi table [SSDT] successfully installed and loaded
Loading Acpi table from file SSDT.aml
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    SSDT-4.dsl - 9631 bytes
Could not open input file -d
Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

okay, i'll check the log if it's loaded.

 

btw, Rehabman, i have tried your method to dissamble the dsdt&ssdt, but when i run "./iasl5 -e SSDT-1.aml SSDT-2.aml SSDT-3.aml SSDT-4.aml -d DSDT.aml" to dissabmle my DSDT, but the result turns to be SSDT-1.dsl + SSDT-2.dsl + SSDT-3.dsl + SSDT-4.dsl, but not the DSDT.dsl as supposed. Why? 

 

here is the log.

Demonbanes-MacBook-Air:DSDT+SSDT-2.24 Demonbane$ ./iasl5 -e SSDT.aml SSDT-1.aml SSDT-2.aml SSDT-3.aml SSDT-4.aml -d DSDT.aml 

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20130725-64 [Jul 30 2013]
Copyright (c) 2000 - 2013 Intel Corporation

Binary file appears to be a valid ACPI table, disassembling
Loading Acpi table from file SSDT-1.aml
Acpi table [SSDT] successfully installed and loaded
Loading Acpi table from file SSDT.aml
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    SSDT-1.dsl - 13122 bytes
Loading Acpi table from file SSDT-2.aml
Acpi table [SSDT] successfully installed and loaded
Loading Acpi table from file SSDT.aml
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed

Found 6 external control methods, reparsing with new information
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    SSDT-2.dsl - 90636 bytes

iASL Warning: There were 6 external control methods found during
disassembly, but only 0 was resolved (6 unresolved). Additional
ACPI tables are required to properly disassemble the code. The
resulting disassembler output file may not compile because the
disassembler did not know how many arguments to assign to the
unresolved methods.
Loading Acpi table from file SSDT-3.aml
Acpi table [SSDT] successfully installed and loaded
Loading Acpi table from file SSDT.aml
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    SSDT-3.dsl - 15320 bytes
Loading Acpi table from file SSDT-4.aml
Acpi table [SSDT] successfully installed and loaded
Loading Acpi table from file SSDT.aml
Acpi table [SSDT] successfully installed and loaded
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Pass 1 parse of [SSDT]
Pass 2 parse of [SSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    SSDT-4.dsl - 9631 bytes
Could not open input file -d

 

Probably too old a version of iasl.

 

I build my own version from sources: https://github.com/RehabMan/acpica

Link to comment
Share on other sites
Demonbane
Demonbane
Posted
Posted

Clover will load SSDT-1.aml or SSDT-2.aml (and so on) if placed in /EFI/CLOVER/acpi/patched. There is no special configuration required in config.plist to control what SSDTs load from that directory.

 

Hi Rehabman, sorry to bother you again, 

 

because my graphic card's information exists in SSDTs, thus i edited one of them, which contains _OFF method, and call _OFF in INIT. and saved as SSDT-1.aml

and i also injected the ig-platform-id in another SSDT, which contains GFX0 device. and saved it as SSDT-2.aml.

finally i generate a SSDT by using ssdtPRGen for my own CPU.(SSDT.aml)

 

So with these 3 SSDT, which were put /ACPI/patched, i started my Laptop with those SSDTs and a clean DSDT, but it seems that the SSDTs were totally not loaded.

 

Could you find out, in which step i probably made a mistake... 

 

Thanks!

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

yeah! thanks for your advice, updated and works fine. now i run "./iasl -e *.aml -d *.aml", is it also a right pattern?

I don't think that works.

 

For dissembling the SSDTs, you need to specify all SSDTs (+DSDT), *except* the one that you're disassembling.

 

It is why I use this construct in a script I wrote to disassemble everything:

list=`echo *.aml`
for aml in $list; do
    iasl -e ${list//$aml/} -d $aml
done

Hi Rehabman, sorry to bother you again, 

 

because my graphic card's information exists in SSDTs, thus i edited one of them, which contains _OFF method, and call _OFF in INIT. and saved as SSDT-1.aml

and i also injected the ig-platform-id in another SSDT, which contains GFX0 device. and saved it as SSDT-2.aml.

finally i generate a SSDT by using ssdtPRGen for my own CPU.(SSDT.aml)

 

So with these 3 SSDT, which were put /ACPI/patched, i started my Laptop with those SSDTs and a clean DSDT, but it seems that the SSDTs were totally not loaded.

 

Could you find out, in which step i probably made a mistake... 

 

Thanks!

If you want me to look, upload an ioreg, captured with IORegistryExplorer v2.1. You can see the SSDTs injected in the ioreg under AppleACPIPlatformExpert -> ACPI Tables.

Link to comment
Share on other sites
pokenguyen
pokenguyen
Posted
Posted

I don't think that works.

 

For dissembling the SSDTs, you need to specify all SSDTs (+DSDT), *except* the one that you're disassembling.

That command works for me RehabMan, the decompiled files are the same (tested with diffmerge). I think iasl finds definition from all the files to correctly parse External methods, and include the disassembling one won't have any effect.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

That command works for me RehabMan, the decompiled files are the same (tested with diffmerge). I think iasl finds definition from all the files to correctly parse External methods, and include the disassembling one won't have any effect.

Doesn't work for me when I tried it... The problem is iasl sees the same file twice. As an example, let's say you have the files SSDT1.AML, SSDT2.AML, SSDT3.AML, and DSDT.AML. You do this:

iasl -e *.AML -d DSDT.AML
The shell expands it to:

iasl -e SSDT1.AML SSDT2.AML SSDT2.AML SSDT3.AML DSDT.AML -d DSDT.AML
It causes iasl to load DSDT.AML twice and an error results. iasl does create output (in DSDT.dsl), but consists of:

Could not parse ACPI tables, AE_ALREADY_EXISTS
Link to comment
Share on other sites
Demonbane
Demonbane
Posted
Posted
hi, i have just checked the ioreg and found that 3 ssdts were indeed loaded, Demonbane’s MacBook Air.zip

 

but it should work... because the graphic card informations are in ssdt but not dsdt so couldn't be parsed? or because there are problems with my ssdt... 

i just added a _DSM methode and added _OFF into INIT :( here is my dsdt+ssdt patched.zip

 

and even config.plist for Clover config.zip

Link to comment
Share on other sites
pokenguyen
pokenguyen
Posted
Posted

Doesn't work for me when I tried it... The problem is iasl sees the same file twice. As an example, let's say you have the files SSDT1.AML, SSDT2.AML, SSDT3.AML, and DSDT.AML. You do this:

iasl -e *.AML -d DSDT.AML
The shell expands it to:

iasl -e SSDT1.AML SSDT2.AML SSDT2.AML SSDT3.AML DSDT.AML -d DSDT.AML
It causes iasl to load DSDT.AML twice and an error results. iasl does create output (in DSDT.dsl), but consists of:

Could not parse ACPI tables, AE_ALREADY_EXISTS

 

Maybe different iasl? I'm using the latest version here:

http://www.osx86.net/files/download/3680-iasl-intel-acpi-tools-x64/

 

And it works with this:

./iasl -e *.aml -d DSDT.AML
but this will gives me error AE_Already_Exists

./iasl -e *.aml -d ./DSDT.AML
Link to comment
Share on other sites
gygabyte666
gygabyte666
Posted
  • Author
Posted

and another question, do you now already shut off the nvidia graphic card? i checked your ssdt-1.amd(11.07.2013), and haven't seen any implementation of that.

 

i found that the _OFF method exists in clean_ssdt-0, but you haven't integrated it into your ssdt?

No, I haven't disabled my GeForce through the SSDT. Since i'm still hoping to get it working at some point and considering I don't typically run the machine as a laptop, I don't see the point in disabling it.

 

Interesting to note that since i've updated to 10.9.2 (13C48) My GeForce is natively recognized by the stock Nvidia drivers and boots just fine without me having to remove NVDAStartup as I needed to in the past. It's more than likely due to my current SSDT edits and I haven't had a chance yet to test it without the edits to see if it persists but this is still very good news. :D

 

The thread's first post got updated with my most recent/current Maverick ENVY files. It includes my latest DSDT/SSDTs. To reduce the size I omitted everything that wasn't updated. Both the new and old archives are available and both are REQUIRED to get everything for a fresh install. I also removed support for Chameleon since I haven't used it since I first started the thread.

Link to comment
Share on other sites
warlikewings
warlikewings
Posted
Posted

Hi Gygabyte,

I've finally had a chance to really sit down and spend a few weeks working on this, I've managed to follow your guid to the letter, and came away with a rather great WIP install. I've got clover booting default, and I'm tripple booting windows 8.1, osx 10.9.1, and Gnome Ubuntu :) I couldn't have done it without you man! I still have a few links to iron out (icloud, patching the mach kernel following rehabman's guide has yet to work for me, and sound even with any voodoo hda I've tried just isn't there) I also have to focus on learning dsdt editing, I'd like my lid sleep to work, and even with evoreboot I'm having trouble rebooting or putting the laptop to sleep for some reason. But, my post isn't meant to be a "why isn't this or that" working post, it's literally an expression of my thanks to you and everyone else who's been so helpful along the way. Before I do anything more to this thing, I'm going to make a complete system image, that way I can reimage the drive and have everything as it is now if anything fails. I'm going to really dig through this thread some more and see if I can find anything I may have missed that will help. Thanks for being so helpful to people like myself, who aren't totally new to this, but are still learning when it comes to not using any tools and crutches in the process.

 

Quick question, and yes I have been over a ton of google links thus far to no avail. Have you ever used a usb wifi receiver with this laptop? If so, did you have any luck with icloud/AppStore? If I can't iron it out I may buy a native mini card.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

Maybe different iasl? I'm using the latest version here:

http://www.osx86.net/files/download/3680-iasl-intel-acpi-tools-x64/

 

And it works with this:

./iasl -e *.aml -d DSDT.AML
but this will gives me error AE_Already_Exists

./iasl -e *.aml -d ./DSDT.AML

 

I'm using the latest built from Intel sources. It could be that it used to work and is now broken in the latest code. Or there is some dependency on how the arguments are expanded or a casing issue.

Link to comment
Share on other sites
pokenguyen
pokenguyen
Posted
Posted

I'm using the latest built from Intel sources. It could be that it used to work and is now broken in the latest code. Or there is some dependency on how the arguments are expanded or a casing issue.

I'm using iasl_20140114_64 build, hope you can test because that command is much easier. I used to use bash script to get list of *.aml, until I tried that command.

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

I'm using iasl_20140114_64 build, hope you can test because that command is much easier. I used to use bash script to get list of *.aml, until I tried that command.

As I stated before, I've already tried it with the latest version of iasl (I build from Intel sources). It does not work.

 

YMMV.

Link to comment
Share on other sites
nrjmadan
nrjmadan
Posted
Posted
I'm trying to run 10.9 maverick on HP 15t-j100 Select Edition.

Specs: i5-4200M (Haswell), Intel HD4600, Nvidia GeForce GT 740M 2GB.

Chameleon svn2266, SMBios: MacBook Pro 11,1

 

I've got Intel HD4600 running with IntelAzulFB=12

I want to put ig-platform-id under Device (GFX0) in DSDT (have GFX0 instead of IGPU)

 

Problem: GFX0 is defined in one SSDT (not in DSDT) and I've somehow managed to fix its errors.

But, _DSM method that i need to modify, is in another SSDT (Under GFX0's scope), which has like 2 (set of 5) similar errors I can't fix.

Could someone please tell me what's wrong with this piece of code:




Method (MXMX, 1, Serialized)

    {

        If (LEqual (Arg0, Zero))

        {

            \_SB.PCI0.PEG0.PEGP.SGPO (\_SB.PCI0.PEG0.PEGP.ESEL, Zero)

            P8XH (One, 0x77, One, P8XH (Zero, Zero, One, Return (One), 

                If (LEqual (Arg0, One))

                {

                    P8XH (One, 0x77, One, P8XH (Zero, One, One, Return (One), 

                        If (LEqual (Arg0, 0x02))

                        {

                        P8XH (One, 0x77, One, P8XH (Zero, 0x02, One, Return (LNot (

                        \_SB.PCI0.PEG0.PEGP.SGPI (\_SB.PCI0.PEG0.PEGP.ESEL))), Return (Zero)))

                        }))

                }))

        }

    }


Errors: 

line 01: warning: Not all control paths return a value (MXMX)

line 06: parse error, expecting "," or ")"

line 09: parse error, expecting "," or ")"

line 12: parse error, expecting "," or ")"

line 13: parse error

line 13: parse error

line 13: warning: Statement is unreachable

line 13: warning: Called method may not always return a value

 

definitions (if req):

Method (SGPO, 2, Serialized) {...}


Method (SGPI, 1, Serialized) {...}


Scope (\_SB.PCI0.PEG0.PEGP)

    {

        OperationRegion (SGOP, SystemMemory, 0x9CF77F18, 0x00000050)

        Field (SGOP, AnyAcc, Lock, Preserve)

        {

            // ... 

            DSEL,   8, 

            ESEL,   8,

// ...

        }

    }

 

Method (P8XH, 3, Serialized) {...}

also, all calls of P8XH in dsdt have 3 arguments, eg: P8XH (0x04, 0x53, Zero), however this one has 5.

 

Clean DSDT and SSDTs are attached.

Please tell me what to do, I want to fix it myself.

Clean DSDT-SSDT HP Envy 15t-j100 Select Edition.zip

Link to comment
Share on other sites
nrjmadan
nrjmadan
Posted
Posted 
Method (MXMX, 1, Serialized)
    {
        If (LEqual (Arg0, Zero))
        {
            \_SB.PCI0.PEG0.PEGP.SGPO (\_SB.PCI0.PEG0.PEGP.ESEL, Zero)
            P8XH (One, 0x77, One, P8XH (Zero, Zero, One, Return (One), 
                If (LEqual (Arg0, One))
                {
                    P8XH (One, 0x77, One, P8XH (Zero, One, One, Return (One), 
                        If (LEqual (Arg0, 0x02))
                        {
                        P8XH (One, 0x77, One, P8XH (Zero, 0x02, One, Return (LNot (
                        \_SB.PCI0.PEG0.PEGP.SGPI (\_SB.PCI0.PEG0.PEGP.ESEL))), Return (Zero)))
                        }))
                }))
        }
    }

 

Guys could you please take a look at this

I have no idea how ACPI syntax works, I'm just formatting the code by observing patterns.

Do you think this is what it meant?  :unsure:

Method (MXMX, 1, Serialized)
    {
        If (LEqual (Arg0, Zero))
        {
            \_SB.PCI0.PEG0.PEGP.SGPO (ESEL, One)
            P8XH (One, 0x99, One)
            P8XH (Zero, Zero, One)
            Return (One)
        }
        If (LEqual (Arg0, One))
        {
            P8XH (One, 0x99, One)
            P8XH (Zero, One, One)
            Return (One)
        }
        If (LEqual (Arg0, 0x02))
        {
            P8XH (One, 0x99, One)
            P8XH (Zero, 0x02, One)
            Return (\_SB.PCI0.PEG0.PEGP.SGPI (ESEL))
        }
        Return (Zero)
    }

This does remove errors and warnings and I've seen some methods use similar definition (with ifs).

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

 

I'm trying to run 10.9 maverick on HP 15t-j100 Select Edition.
Specs: i5-4200M (Haswell), Intel HD4600, Nvidia GeForce GT 740M 2GB.
Chameleon svn2266, SMBios: MacBook Pro 11,1
 
I've got Intel HD4600 running with IntelAzulFB=12
I want to put ig-platform-id under Device (GFX0) in DSDT (have GFX0 instead of IGPU)
 
Problem: GFX0 is defined in one SSDT (not in DSDT) and I've somehow managed to fix its errors.
But, _DSM method that i need to modify, is in another SSDT (Under GFX0's scope), which has like 2 (set of 5) similar errors I can't fix.
...
 
Clean DSDT and SSDTs are attached.
Please tell me what to do, I want to fix it myself.

 

Disassemble your SSDTs/DSDT properly and you'll have less errors.  You need to use iasl with '-e' param in Terminal:

 

# disassemble DSDT
iasl -e SSDT*.aml -d DSDT.aml
# disassemble an SSDT, specify all SSDTs (except the one you're disassembling) and DSDT 
iasl -e SSDT1.aml SSDT2.aml SSDT3.aml SSDT4.aml SSDT6.aml DSDT.aml -d SSDT5.aml

 

Some report you can do this, although it hasn't worked for me:

 

iasl -e *.aml -d *.aml
Link to comment
Share on other sites
nrjmadan
nrjmadan
Posted
Posted

 

Disassemble your SSDTs/DSDT properly and you'll have less errors.  You need to use iasl with '-e' param in Terminal:

 

Thanks for the suggestion.  :)

I did go through few posts suggesting the same,

But I couldn't figure out how to install iasl on windows. Still going through google results.  :wallbash:

No prior experience with command prompt and installing make file, etc.

I don't have linux installed, and device lacks optical drive for a live boot.

Is there some kind of guide, instructions, or walkthrough for installing it on windows?

 

also, I tried modifying SSDT with _DSM.

But, although Sys.Info. shows Intel HD4600, with only platform-id specified, QE/CI isn't working; neither kext loaded.

Question: Does it make a difference to use IGPU instead of GFX0?

Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

Thanks for the suggestion.  :)

I did go through few posts suggesting the same,

But I couldn't figure out how to install iasl on windows. Still going through google results.  :wallbash:

No prior experience with command prompt and installing make file, etc.

I don't have linux installed, and device lacks optical drive for a live boot.

Is there some kind of guide, instructions, or walkthrough for installing it on windows?

 

also, I tried modifying SSDT with _DSM.

But, although Sys.Info. shows Intel HD4600, with only platform-id specified, QE/CI isn't working; neither kext loaded.

Question: Does it make a difference to use IGPU instead of GFX0?

I recommend you use iasl on OS X.  But there is Windows builds of iasl on Windows too.  You might look here for Windows builds: https://www.acpica.org/

For Ubuntu boot, use a USB, no need for optical.

 

System Info does not show ig-platform-id.  You can see that only in ioreg (use IORegistryExplorer).  For injecting ig-platform-id it is easier to use the bootloader mechanisms.

 

Changing from GFX0 to IGPU gives you GPU power management.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...