How to set ig-platform-id?

[jaymonkey]

I also have 4790k and have put this config.plist code, set the igpu to enable and voila, everything works ... I have left the ig-platform-id under graphics section empty, is that ok?

+could you suggest if I do the same for my wife's computer or there should be other code for her computer (8500k / rx580)

@miquedique,

When using Device Properties to configure the IGPU via Lilu + WhatEverGreen you should remove/zero out all Clover IGPU options, failure to do so can cause a conflict with lilu and/or WEG, the process is detailed in Chapter 4 of this guide :-

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

An iDiot's Guide To Lilu and its Plug-in's Last Update: 22nd Jan 2021 (Add note about OpenCore config.plist modifications) About this Guide Note: This guide was written when Clover was the boot loader of choice as such the config.plist examples in this guide are mostley Clover specific ... if...

www.tonymacx86.com

Intel i5 8500K has a UHD 630 IGPU so the PlatformID's to use are 0x3E920003 or 0x3E910003 or 0x3E980003.

This info is also in the above linked guide.

Cheers
Jay

 

[miquedique]

@miquedique,

When using Device Properties to configure the IGPU via Lilu + WhatEverGreen you should remove/zero out all Clover IGPU options, failure to do so can cause a conflict with lilu and/or WEG, the process is detailed in Chapter 4 of this guide :-

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

An iDiot's Guide To Lilu and its Plug-in's Last Update: 22nd Jan 2021 (Add note about OpenCore config.plist modifications) About this Guide Note: This guide was written when Clover was the boot loader of choice as such the config.plist examples in this guide are mostley Clover specific ... if...

www.tonymacx86.com

Intel i5 8500K has a UHD 630 IGPU so the PlatformID's to use are 0x3E920003 or 0x3E910003 or 0x3E980003.

This info is also in the above linked guide.

Cheers
Jay

thanks mate! much appreciated

 

[NorthAmTransAm]

@jaymonkey since updating to 10.14.6 I've noticed that my iGPU setup works without any device properties or platform ID info. Is this normal? If so I'm really digging that more native feeling.

 

[jaymonkey]

@jaymonkey since updating to 10.14.6 I've noticed that my iGPU setup works without any device properties or platform ID info. Is this normal? If so I'm really digging that more native feeling.

@NorthAmTransAm,

I assume you still have Lilu + WhatEverGreen installed ?

If so then Lilu + WhatEverGreen will use a default/best guess if no Device Properties are defined for the IGPU in your config.plist. In the past this used to be quite random but in more recent releases of Lilu + WhatEverGreen its best guess/default has got much better but it still does not always get it right ... looks like in this case its worked ok.

Personally I prefer to always explicitly define the Device Properties for the IGPU rather than leaving the decision to Lilu + WEG as you can never be 100% sure that it will always work due to the fast development/release rate of Lilu + WhatEverGreen code does get released that does not always work as intended.

Cheers
Jay

 

[NorthAmTransAm]

@NorthAmTransAm,

I assume you still have Lilu + WhatEverGreen installed ?

If so then Lilu + WhatEverGreen will use a default/best guess if no Device Properties are defined for the IGPU in your config.plist. In the past this used to be quite random but in more recent releases of Lilu + WhatEverGreen its best guess/default has got much better but it still does not always get it right ... looks like in this case its worked ok.

Personally I prefer to always explicitly define the Device Properties for the IGPU rather than leaving the decision to Lilu + WEG as you can never be 100% sure that it will always work due to the fast development/release rate of Lilu + WhatEverGreen code does get released that does not always work as intended.

Cheers
Jay

That make sense to me. So each time I update Lilu and WEG (each OS update for me) I'm rolling the dice again? I guess I could take a peek at what it's using and plug it into Clover.

 

[jaymonkey]

That make sense to me. So each time I update Lilu and WEG (each OS update for me) I'm rolling the dice again? I guess I could take a peek at what it's using and plug it into Clover.

@NorthAmTransAm,

Its a safer bet in my opinion, not saying that leaving it all to Lilu + WEG is a bad idea ... but the less you leave the chance the least likely you are to experience issues in the future .. thats just the way my mind works.

You can use hackintool to see what values are currently being used and then genearte the Device Properties based on those settings.

Cheers
Jay

 

[Bingdotcom]

read the clover documentation
https://clover-wiki.zetam.org/Contents

dead link

 

[itwas]

dead link

Clover EFI bootloader / Wiki / Home

sourceforge.net

 

[jikz]

@nkoun,

When running Mojave it is recommended to use WhatEverGreen to configure the IGPU. I have a very similar system spec to yours in my White Knight system (specs in my sig).

I use FCPX with no issues at all (its the primary use of that system)

Recommend the following configuration :-

• SMBIOS iMac15,1
• IGPU enabled in BIOS,
• dGPU set as Primary Display Adapter
• Configure IGPU as Headless :-
• Set "AAPL,ig-platform-id" to use PlatformID 0x0x0412000B by using 0B001204 as Device Property
• Set "device-id" to use 12040000 as Device Property

Both the above Device Properties should be assigned against the Device PCI key PciRoot(0x0)/Pci(0x2,0x0)
All the information you need is detailed in the Lilu + Plug-in's guide.

I've added the Device Properties to your example copy.plist (attached) :-

View attachment 383199

Code for Devices section of your config.plist

<key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                CwASBA==
                </data>
                <key>device-id</key>
                <data>
                EgQAAA==
                </data>
            </dict>
        </dict>

All you need to do is install the latest version of Lilu + WhatEverGreen in /L/E using the Install Method detailed in the
Lilu + Plug-in's guide and add the above changes to your config.plist, be sure to uncheck Inject Intel, as stated in the guide you need to remove all IGPU related flags from the Devices & Graphics sections of your config.plist.

If you want to understand more read the Headless PlatformID's section of the guide, although I recommend reading the Introduction if you have not used Lilu before, and the whole of the WhatEverGreen Chapter.

Cheers
Jay

Hey Jay. Thank you for putting so much time & effort to help users like me. I´m doing my first hackintosh and haven´t been able to use FCPX with my CPU in headless mode and found all of this information. I´m currently using a 4790k & a Vega64 just like you and installed 10.14.6 with uni/multibeast. If I install everything from scratch and only install internet kext & choose 15,1 SMBios in multibeast, can I then install the latest WEG, Lilu and AppleALC kexts via hackintool and just use your config.plist instead of the autogenerated? Of course I would use the recommended BIOS with it.
Again, thank you for your time & effort

 

[jaymonkey]

If I install everything from scratch and only install internet kext & choose 15,1 SMBios in multibeast, can I then install the latest WEG, Lilu and AppleALC kexts via hackintool and just use your config.plist instead of the autogenerated? Of course I would use the recommended BIOS with it.

@jikz,

There is nothing special about my config with regards to the Vega dGPU and headless IGPU. WEG's auto detect/auto configure features have improved massively in the last year or so and I found on my system that the latest version of WEG correctly auto detects the VEGA dGPU and IGPU and configures them without having to define any device properties in the config.plist. You can of course choose to over ride this and use Hackintool to generate the device properties as a belt and braces approach to the config or if the auto detect/auto configure does not work for you.

I do have some Hot Patch SSDT's to take care of the DSDT ACPI fixes and patches but those are specific to my ASRock Z87 motherboard which has a modded BIOS and would not work on your Gigabyte motherboard.

Cheers
Jay