Contribute
Register

Confusion about Whatevergreen usage

Status
Not open for further replies.
Joined
May 14, 2017
Messages
67
Motherboard
Lenovo G50-80
CPU
5200U
Graphics
HD 5500, R5 330M(disabled)
Mobile Phone
  1. iOS
It is a common sense that we must use Whatevergreen and Lilu to patch Intel Graphics Framebuffer on macOS Mojave or greater. So, the primitive way that old patches use must be transmitted to Whatevergreen-powered way right now, like DVMT patches, connector patches, and so on.
When using new platform that Apple hasn't released on its genuine Mac, we have to Fake ID to get it work. We used to fill in the Config/Device/FakeIntelGFX blank to accomplish our task, but I don't know how to use it via Whatevergreen.kext.
Take UHD 620 for instance:
Used to do: ig-platform-id: 0x59170000 FakeIntelGFX: (0x)59160000
Now: Device/Property "AAPL,ig-platform-id: 00001759"; but what for FakeIntelGFX?
 
It is a common sense that we must use Whatevergreen and Lilu to patch Intel Graphics Framebuffer on macOS Mojave or greater. So, the primitive way that old patches use must be transmitted to Whatevergreen-powered way right now, like DVMT patches, connector patches, and so on.
When using new platform that Apple hasn't released on its genuine Mac, we have to Fake ID to get it work. We used to fill in the Config/Device/FakeIntelGFX blank to accomplish our task, but I don't know how to use it via Whatevergreen.kext.
Take UHD 620 for instance:
Used to do: ig-platform-id: 0x59170000 FakeIntelGFX: (0x)59160000
Now: Device/Property "AAPL,ig-platform-id: 00001759"; but what for FakeIntelGFX?

In config.plist/Devices/Properties/PciRoot(0)/Pci(2,0), add:
device-id=(data)<16590000>

Refer to the guide plists for examples:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/
 
Status
Not open for further replies.
Back
Top