[solved] Black Screen after 10.12 -> 10.12.4 update

[RehabMan]

Ok, there was a few, that was wit 0x0ad9..
But, as I understand, there is no way to bring 16260006 back to life?(
And the question is, what connects all the values, that don't work..

Too hard to answer your question due to not enough information.

For example, no idea what you really mean by "laggy"...
If you have a a short duration lag at startup and after login, it is not unexpected since we've seen it elsewhere (with Haswell). And the solution to that is simply to trim the ports in the framebuffer down to the ones you actually have....

It is possible that even 0x16260006 may work if you trim the ports to only the physically present ports...
That would certainly be something to test, as soon as you determine what those ports are...

 

[fr0n1k]

Too hard to answer your question due to not enough information.

For example, no idea what you really mean by "laggy"...
If you have a a short duration lag at startup and after login, it is not unexpected since we've seen it elsewhere (with Haswell). And the solution to that is simply to trim the ports in the framebuffer down to the ones you actually have....

It is possible that even 0x16260006 may work if you trim the ports to only the physically present ports...
That would certainly be something to test, as soon as you determine what those ports are...

Ok, hope you will help me, as usual)
yes, by the laggy i meant frezees.. But there was 1 value, that does me 3-4 frames per minute... And this was awfull)
OK, as i understand, i should pick the right one for the brightness and then follow the haswell guide?)

 

[fr0n1k]

Too hard to answer your question due to not enough information.

For example, no idea what you really mean by "laggy"...
If you have a a short duration lag at startup and after login, it is not unexpected since we've seen it elsewhere (with Haswell). And the solution to that is simply to trim the ports in the framebuffer down to the ones you actually have....

It is possible that even 0x16260006 may work if you trim the ports to only the physically present ports...
That would certainly be something to test, as soon as you determine what those ports are...

Bad news, I was mistake..
There are only 9914, a107, 6c05..
D90a only for 16260005(6)

UPD. Could you please help me with the unused ports? It seems to me, that yours different from mine)

 

[RehabMan]

Bad news, I was mistake..
There are only 9914, a107, 6c05..
D90a only for 16260005(6)

Yup.
And note that you could also simply patch the 9914 or a107 or 6c05 to d90a...
For example (0x1499 -> 0xad9):
Find: 99 14 00 00 99 14 00 00
Replace: D9 0A 00 00 D9 0A 00 00

UPD. Could you please help me with the unused ports? It seems to me, that yours different from mine)

The patches depend on which ig-platform-id you're using, whether you have HDMI or DP, and which port the HDMI/DP is connected to (0105/0204/0306).

 

[fr0n1k]

Yup.
And note that you could also simply patch the 9914 or a107 or 6c05 to d90a...
For example (0x1499 -> 0xad9):
Find: 99 14 00 00 99 14 00 00
Replace: D9 0A 00 00 D9 0A 00 00



The patches depend on which ig-platform-id you're using, whether you have HDMI or DP, and which port the HDMI/DP is connected to (0105/0204/0306).

For example, if I want to try for 16260006, hdmi only, how can I check it? Via ioreg?)

 

[RehabMan]

For example, if I want to try for 16260006, hdmi only, how can I check it? Via ioreg?)

To determine which port your HDMI is connected to, use an ig-platform-id that allows your HDMI port to work... then connect a device to the HDMI port, then check ioreg to see with framebuffer connector it actually connected to. The port/framebuffer relationship is positional with respect to the ports defined in the framebuffer ig-platform data. So, as an example, if you were using ig-platform-id 0x16260006, and found that your HDMI device had connected to AppleIntelFramebuffer@2, it would mean it was connected to the 0204 port.

Because the connector data for 0x16260006 is:
00000800 02000000 30020000 -> LVDS @0
01050B00 00040000 07050000 -> DP @1
02040B00 00040000 07050000 -> DP @2
FF000000 01000000 40000000 -> undefined

So, let's say you decided you wanted to patch to have only LVDS and 0204:

Find: 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000 FF000000 01000000 40000000
Replace: 00000800 02000000 30020000 02040B00 00040000 07050000 FF000000 01000000 40000000 FF000000 01000000 40000000

And you would also need to update the port count:
Find: 06002616 01030303
Replace: 06002616 01030202

 

[fr0n1k]

Yup.
And note that you could also simply patch the 9914 or a107 or 6c05 to d90a...
For example (0x1499 -> 0xad9):
Find: 99 14 00 00 99 14 00 00
Replace: D9 0A 00 00 D9 0A 00 00



The patches depend on which ig-platform-id you're using, whether you have HDMI or DP, and which port the HDMI/DP is connected to (0105/0204/0306).

Hi again, if I use now the 16260002 with 6c05, where should I add this in clover?
Find: D9 0A 00 00 D9 0A 00 00
Replace: 6C050000 6C050000

 

[RehabMan]

Hi again, if I use now the 16260002 with 6c05, where should I add this in clover?
Find: D9 0A 00 00 D9 0A 00 00
Replace: 6C050000 6C050000

What you have there is nonsense.
0x16260002 uses 0x056c, not 0xad9.
If you're to patch it, you would patch for 0xad9.

Name: AppleIntelBDWGraphicsFramebuffer
Find: 6C 05 00 00 6C 05 00 00
Replace: d9 0a 00 00 d9 0a 00 00

Kext patches go in config.plist/KernelAndKextPatches/KextsToPatch.

 

[fr0n1k]

What you have there is nonsense.
0x16260002 uses 0x056c, not 0xad9.
If you're to patch it, you would patch for 0xad9.

Name: AppleIntelBDWGraphicsFramebuffer
Find: 6C 05 00 00 6C 05 00 00
Replace: d9 0a 00 00 d9 0a 00 00

Kext patches go in config.plist/KernelAndKextPatches/KextsToPatch.

Hope this correct, first one under kexts (0).

UPD. Maybe problem may be caused by apple backlight injector, and I should thry to delete it and try 16260006?)

 

[RehabMan]

Hope this correct, first one under kexts (0).

Yes.

UPD. Maybe problem may be caused by apple backlight injector, and I should thry to delete it and try 16260006?)

No description of problem.
No "Problem Reporting" files.