HD4000 black screen on 10.14.6

[Hervé]

2nd config remains incorrect since it still contains wrong properties injection for device PciRoot(0)/Pci(0x2, 0), i.e. the HD4000 iGPU:

 

And you've not provided the rest of your Clover EFI folder so God only knows what may lie there too...

 

Here, try this config. Call it from Clover main menu->Options->configs.

config_RV.plist.zip

 

You'll also need to generate your CPU-specific power management SSDT using Pike R Alpha's well-known generator tool/script.

 

[liemhatang]

Thanks for replay, but black creen if user ig-platform-id laptop.

 

i try change ig-platform-id to 0a006601 but not boot. idon't know why?

my Clover.

[Hervé]

If black screen using layout 0x01660004, try other mobile layouts shown on p1 such as 0x01660009. You may then need to apply the following LVDS patch to the Capri framebuffer:

         \/\/
Find:    010000000200000030000000    --> vanilla LVDS outpout layout 0x016600 00/01/02/08/09
Replace: 050300000200000030000000    --> patched LVDS output
         /\/\

 

Did you use DualLink with layout 0x01660004? I forgot to add it in the config I provided.

 

Anyway, just conduct your own experiments/tryouts with the various Capri layouts. You should get there eventually.

[liemhatang]

On 3/28/2020 at 10:09 PM, Hervé said:

If black screen using layout 0x01660004, try other mobile layouts shown on p1 such as 0x01660009. You may then need to apply the following LVDS patch to the Capri framebuffer:

         \/\/
Find:    010000000200000030000000    --> vanilla LVDS outpout layout 0x016600 00/01/02/08/09
Replace: 050300000200000030000000    --> patched LVDS output
         /\/\

 

Did you use DualLink with layout 0x01660004? I forgot to add it in the config I provided.

 

Anyway, just conduct your own experiments/tryouts with the various Capri layouts. You should get there eventually.

I don't understand what you mean

means I have to replace layouts from 00 to 09 with the patch below

Quote

Find:  010000000200000030000000

Replace: 050300000200000030000000

I'm not very good at this patch because my English is very bad

[Hervé]

It means that if you try and use any of the following layouts:

• 0x01660000
• 0x01660001
• 0x01660002
• 0x01660008
• 0x01660009

you may also have to try them with the Clover on-the-fly patch detailed above (applicable to AppleIntelFramebufferCapri kext). Altogether, that's 10 x tests to make potentially (each layout with and without the patch).

[liemhatang]

i try all layouts with SMBIOS Macmini 6,1 and MBP9,2 but don't work, blackcreens all

[Hervé]

Then look into injecting the screen's EDID info.

[liemhatang]

I always check inject edid

[Hervé]

Be a little creative:

• try without "Inject Edid"...
• obtain your screen's EDID from Windows, then inject the whole Hex chain in Clover...

[arsradu]

For as far as I know, Clover is already doing a pretty good job at injecting the correct EDID. Also, if I'm not mistaken (which I could be), the "Inject EDID" option refers to a Custom EDID you provide. If you don't have one, or if you're planning to inject the original one, it's not gonna make much of a difference.

One other thing you can try is updating WEG. Yours seems a bit old, whereas Lilu is newer. It's usually best to keep them both updated since one relies on the other to work.

In this case, WEG is a plugin for Lilu. Same for AppleALC for sound.

 

Take a look at the Intel Framebuffer patching page here: https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md

 

For Laptop (Capri Framebuffer), the recommended values are: 0x01660003 (default), 0x01660009, 0x01660004.

 

Also, if I'm not mistaken, when you add AAPL,ig-platform-id to Device Properties, you need to do it with reversed bytes.

 

Meaning: 0x01660003 becomes 03 00 66 01 (type Data).

Same for the other ones.