Contribute
Register

An iDiot's Guide To Lilu and its Plug-ins

There have been reports of some issues with the IGPU on CFL CPU's that don't seem to play nice with WEG and required the use of Clover to resolve the issue. I believe the WEG developers are working on those issues.

That may explain it then for certain builds. Having a KabyLake build and on iMac18,3 SysDef, all I have to do is enable iGPU, set dGPU as primary, and Lilu + WEG. I don't have to set ig-platform-id in Clover.

Maybe worth mentioning in the guide to verify the PlatformID (whether using Hackintool or IORegistryExpoler) first before going down the path of config.plist changes? I for one enjoyed learning more about this setting, and what I learned along the way. However, I know there are those out there that start messing around in config.plist, and make things worse than before!
 
Maybe worth mentioning in the guide to verify the PlatformID (whether using Hackintool or IORegistryExpoler) first before going down the path of config.plist changes?


@manHands,

The issue is not PlatformID related but more likely down to the BIOS and/or ACPI Tables implementation on certain CFL systems. It's not just headless configurations that are effect but also many solo IGPU CFL systems are having a difficult time running MacOS with UHD 630 IGPU ... many of those issue's can be resolved by injecting additional WEG Device Properties to further patch the frame buffer but others seem to only work with Clover + ig-platform-id.

The situation is slowly improving as more debug and testing work is done and fixes being found which should eventually find their way into a future version of WEG.

Cheers
Jay
 
I really appreciated this well written guide. In a headless system, which I have set up, is there any benefit to increasing the vram to 2048? I assume it is only for monitors connected to the igpu.

Hackintool shows everything as expected. Videoproc shows the expected settings and WhatEverGreen has correctly renamed the HECI device (see images)
 

Attachments

  • Screen Shot 2019-02-22 at 6.19.47 PM.png
    Screen Shot 2019-02-22 at 6.19.47 PM.png
    93.8 KB · Views: 137
  • Screen Shot 2019-02-22 at 6.49.13 PM.png
    Screen Shot 2019-02-22 at 6.49.13 PM.png
    6.7 KB · Views: 131
  • Screen Shot 2019-02-22 at 7.03.13 PM.png
    Screen Shot 2019-02-22 at 7.03.13 PM.png
    66.3 KB · Views: 128
Last edited:
I really appreciated this well written guide. In a headless system, which I have set up, is there any benefit to increasing the vram to 2048? I assume it is only for monitors connected to the igpu.


@stlouisz,

Glad you found the guide useful, increasing VRAM will have no beneficial effect on the IGPU as when configured headless the IGPU is only used to execute Open CL code and specific IGPU functions such as Intel QuickSync (IQS) which are not effected by VRAM size.

Cheers
Jay
 
I have a Vega 56 and planned will be a 10.14.2 Hackintosh.

If I disable the integrated Intel GPU completely (I don't need it and Quick-Sync, as I can use the hardware acceleration of my Vega 56), do I still need WhateverGreen or any of the graphic related configs?
 
I have a Vega 56 and planned will be a 10.14.2 Hackintosh.

If I disable the integrated Intel GPU completely (I don't need it and Quick-Sync, as I can use the hardware acceleration of my Vega 56), do I still need WhateverGreen or any of the graphic related configs?


@flocked,

Its best to enable the IGPU and configure it as headless as this is how real mac's are configured, IQS is baked into MacOS and is used by the operating system by default, there are some system services such as finders quick look feature that will only use the IGPU even though a GPU is available. MacOS also load balances certain tasks across the IGPU and GPU.

Your system will run smother and be more efficient if you use the IGPU in headless mode alongside the Vega GPU, it is the recommended and correct method.

All dual GPU desktop macs (such as most iMacs) use the IGPU in headless mode, think of it as a co-processor for certain tasks, the only exceptions are desktop macs that use Server class CPU's (XEON) as those CPU's do not have a IGPU.

Cheers
Jay
 
Last edited:
@flocked,

Its best to enable the IGPU and configure it as headless as this is how real mac's are configured, IQS is baked into MacOS and is used by the operating system by default, there are some system services such as finders quick look feature that will only use the IGPU even though a GPU is available. MacOS also load balances certain tasks across the IGPU and GPU.

Your system will run smother and be more efficient if you use the IGPU in headless mode alongside the Vega GPU, it is the recommended and correct method.

All dual GPU desktop macs (such as most iMacs) use the IGPU in headless mode, think of it as a co-processor for certain tasks, the only exceptions are desktop macs that use Server class CPU's (XEON) as those CPU's do not have a IGPU.

Cheers
Jay

That's why I want to configure my Hackintosh as iMacPro1,1 as it doesn't have an iGPU. Wouldn't that work and even have better performance than a shared iGPU + Vega setup? I don't want MacOS to use my iGPU when I have a much faster GPU inside my Hackintosh.
And if I deactivate the iGPU, I might have one possible factor less that could cause problems with updates or e.g. Final Cut Pro.
 
I am unable to get Netflix or iTunes to play videos with Lilu + Whatevergreen. I have an i73770K with HD 4000 with a GTX 760 card. I have set my platform ID to be headerless and have changed the SMBIOS to iMac 13,2 (which fixed quicklook/preview issues I was having).

I have tried various combinations of the shikivga boot argument in the guide with no success.
Most of the times iTunes crashes, sometimes it's just a black screen. Netflix usually takes me to the help page, but sometimes it will play but be a green screen.

Any help would be appreciated. As far as I can tell, this is the only thing I can't get working on my build.
 
That's why I want to configure my Hackintosh as iMacPro1,1 as it doesn't have an iGPU. Wouldn't that work and even have better performance than a shared iGPU + Vega setup?


@flocked,

Bad idea to use iMac Pro1,1 SMBIOS on a non server (XEON) class CPU hackingtosh. MacOS contains CPU optimisations for XEON based systems which desktop class CPU's simply don't have ... you'll run it to issues if you go that path.

I don't understand why you think disabling the IGPU will result in a quicker system, the exact opposite is true. MacOS will run smother and more efficient with the IGPU enabled and configured as headless.

But your free to configure your system however you like ...

Cheers
Jay
 
Back
Top