Contribute
Register

[README] Common Problems in 10.13 High Sierra

Looks to be an EDID issue. Requires display override with patched EDID.

In fact, just setting the correct ig-platform-id on Clover already does the trick on some laptops.

Another thing I just figured out is that IntelGraphicsFixup.kext injects wrong EDID in some models (mine is included). Seems that external display EDID is injected instead of the regular built-in display, which leads to the display not waking up from sleep.

So using this kext to fix Intel Graphics issues, in this case, might not be a good solution.

Edit: HD5500 works fine with ig-platform-id = 0x16260006 and _WAK patch on DSDT.
 
In fact, just setting the correct ig-platform-id on Clover already does the trick on some laptops.

Another thing I just figured out is that IntelGraphicsFixup.kext injects wrong EDID in some models (mine is included). Seems that external display EDID is injected instead of the regular built-in display, which leads to the display not waking up from sleep.

So using this kext to fix Intel Graphics issues, in this case, might not be a good solution.

Edit: HD5500 works fine with ig-platform-id = 0x16260006 and _WAK patch on DSDT.

A quick search through IntelGraphicsFixup source reveals no code that injects EDID.
 
A quick search through IntelGraphicsFixup source reveals no code that injects EDID.

Hmm, interesting...

That means the problem could be fixed (at least in some cases) only setting the correct ig-platform-id on integrated video laptops. But what exactly ig-platform-id stands for? What is the equivalent for desktops with dedicated graphics cards?
 
Hmm, interesting...

That means the problem could be fixed (at least in some cases) only setting the correct ig-platform-id on integrated video laptops. But what exactly ig-platform-id stands for? What is the equivalent for desktops with dedicated graphics cards?

ig-platform-id is essentially points the graphics driver to configuration data.

Each set of graphics kexts differ in the way they deal with configuration data.
 
ig-platform-id is essentially points the graphics driver to configuration data.

Each set of graphics kexts differ in the way they deal with configuration data.

This is really interesting. Would it be possible to relate the current SMBIOS from the user setup with ig-platform-id's attempting to find the best match between these?
 
This is really interesting. Would it be possible to relate the current SMBIOS from the user setup with ig-platform-id's attempting to find the best match between these?

ig-platform-id has nothing to do with SMBIOS.
 
ig-platform-id has nothing to do with SMBIOS.

Sure, but what I'm trying to say is that, when the user chooses to use some SMBIOS "profile", it gives information about the type of machine he is trying to "emulate", so catching these informations (machine model, for example) and using it to determine the best ig-platform-id he should use, wouldn't it be possible and a better approach than users having to patch every time their EDID?
 
Sure, but what I'm trying to say is that, when the user chooses to use some SMBIOS "profile", it gives information about the type of machine he is trying to "emulate", so catching these informations (machine model, for example) and using it to determine the best ig-platform-id he should use, wouldn't it be possible and a better approach than users having to patch every time their EDID?

There is no way to automatically determine the "right" ig-platform-id.
The "right" one is the one that works best for the hardware at hand..
Determination is done via trial/error.
 
I am just making sure for my wireless card (just in-case if ever my current card is not supported, I can buy one right away), is the Atheros AR956x supported in High Sierra? Or should I get a different card?
 
Back
Top