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

[jaymonkey]

changed to 17,1 SMBIOS definition. rebooted, logged back into icloud, everything seems working as before, added that SSDT-XCPM.aml patch to the folder you mentioned. verified that P AND C states are disabled.

@HackintoshNoobie,

iMac 17,1 is the correct SMBIOS to use for a Skylake CPU based system, and the use of the X86PlatformPlugin via the SSDT-XCPM.aml hot patch should be all that is required to enable Native CPU Power management in MacOS.

What files or debug logs could I attach to have you take a look? Perhaps I have an old fix that got my 14,2 SMBIOS running still in there that's messing my setup up.

As per the sites FAQ, if you require help you most supply the Proper Problem Reporting Files (PPRF) using the debug tool detailed in this post :-

[TOOL] [Generate Proper Problem Reporting Files]

Last update: 04 Mar 2018 Current Version: 4.2 Hello guys, I have seen many instances where people start a thread with the problem they are facing on their hack. They try to describe the issue in their own way that most of the times, is not able to properly describe what's going wrong with...

www.tonymacx86.com

Intel GPU PM- Rename GFX0 to IGPU" as i do have discrete and IGPU.. so to me it didnt make sense to do that when i do really want both working? hope that makes sense

In most instances WhatEverGreen will take care of the ACPI device re-names so there is no need to specify them in your config.plist unless you have a specific case like the dGPU being in the wrong slot, you can check that the renames are being done by using IORegistryExplorer :-

[Guide] How to Make a Copy of IOReg

IORegistryExplorer aka IOReg Apple Developer Tool Xcode How to Make a Copy of IOReg (Note 1) 1. IORegistryExplorer/File/Save a Copy As…. (no extension required) 2. Open file to verify (Note 2) 3. Attach to post (Note 3) Where To Get IOReg 1. Download Interim, link below Installation 1, Open...

www.tonymacx86.com

Which you need installed in any case in-order to generate the PPRF's detailed above ...

Cheers
Jay

 

[arpaterson]

@arpaterson,

I take it you have already tried installing Lilu + NightShiftUnlocker as detailed in the Other plugins chapter of the guide ?

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

An iDiot's Guide To Lilu and its Plug-in's Last Update: 20th Aug 2020 (Add Comet Lake Desktop Headless PlatformID) About this Guide This guide is written as a helping hand to those users who have some understanding of using legacy hackintosh methods but are considering using Lilu as a means...

www.tonymacx86.com

Your post does not make this clear ....

Cheers
Jay

Yes I have tried placing nightshiftunlocker in /l/e and also /s/l/e (with kextutility)
*all my other kexts including latest Lilu are installed in /clover/kexts/other.
I had it on my to do list to check what best practice was regarding /c/k/o and /s/l/e and /l/e

Any input appreciated. My understanding up to now was that smbios 18,3 is late enough that nightshift should work, and 10.14.5 should allow it on external displays too. But no cigar.

It did work when this machine was running iGPU only with an older graphics configuration from when I first used an EFI from a guide, perhaps InjectIntel, I dont remember now and tbh i didnt understand it back then.

 

[jaymonkey]

Yes I have tried placing nightshiftunlocker in /l/e and also /s/l/e (with kextutility)*all my other kexts including latest Lilu are installed in /clover/kexts/other.I had it on my to do list to check what best practice was regarding /c/k/o and /s/l/e and /l/e

@arpaterson,

You should never install kexts in /S/L/E on MacOS El-Capitan or later as it breaks SIP (System Integrity Protection)
For MacOS El-Capitan or later 3rd party kexts should be installed in /L/E .. see this guide for how & why :-

[GUIDE] Installing 3rd Party Kexts - El Capitan, Sierra, High Sierra, Mojave, Catalina

Installing 3rd Party Kexts in /Library/Extensions 1. What Versions of MacOS does this guide cover ? The methods detailed in this guide will work on the following versions of MacOS MacOS 10.11.X - El Capitan MacOS 10.12.X - Sierra MacOS 10.13.X - High Sierra MacOS 10.14.X - Mojave MacOS...

www.tonymacx86.com

Also if you have Lilu + WhatEverGreen in /Clover/Kexts/Other but have installed nightshiftunlocker in /L/ E then it may not be able to link to Lilu as that will be outside of MacOS kernel memory because you are injecting it via Clover.

I personally recommend installing all 3rd Party kexts in /L/E (including FakeSMC) as per the linked guide above.

Make sure you set Clover Inject Kexts to Detect and only copy critical kexts required to run Installer, updater and recovery to /Clover/Kexts/Other.

Cheers
Jay

 

[kochfede]

A dummy question, I need to add the boot argument -raddvi , where I put in the boot argument in clover? how? thanks for the patience.

 

[jaymonkey]

A dummy question, I need to add the boot argument -raddvi , where I put in the boot argument in clover? how? thanks for the patience.

@kochfede,

Edit your config.plist using a code or plist editor and find the section called "boot" in that section you should have a <Key> type called "Arguments" add -raddvi to the existing <string> type or create it as a new one :-

    <key>Boot</key>
    <dict>
        <key>Arguments</key>
        <string>-raddvi</string>

You can also add it using Clover Configurator if you are not familiar with editing plists.



Cheers
Jay

 

[kochfede]

Thxks! I use that argument with no luck. keep without the dvi-d on RX 580 working properly

 

[HackintoshNoobie]

@HackintoshNoobie,

iMac 17,1 is the correct SMBIOS to use for a Skylake CPU based system, and the use of the X86PlatformPlugin via the SSDT-XCPM.aml hot patch should be all that is required to enable Native CPU Power management in MacOS.




As per the sites FAQ, if you require help you most supply the Proper Problem Reporting Files (PPRF) using the debug tool detailed in this post :-

[TOOL] [Generate Proper Problem Reporting Files]

Last update: 04 Mar 2018 Current Version: 4.2 Hello guys, I have seen many instances where people start a thread with the problem they are facing on their hack. They try to describe the issue in their own way that most of the times, is not able to properly describe what's going wrong with...

www.tonymacx86.com

In most instances WhatEverGreen will take care of the ACPI device re-names so there is no need to specify them in your config.plist unless you have a specific case like the dGPU being in the wrong slot, you can check that the renames are being done by using IORegistryExplorer :-

[Guide] How to Make a Copy of IOReg

IORegistryExplorer aka IOReg Apple Developer Tool Xcode How to Make a Copy of IOReg (Note 1) 1. IORegistryExplorer/File/Save a Copy As…. (no extension required) 2. Open file to verify (Note 2) 3. Attach to post (Note 3) Where To Get IOReg 1. Download Interim, link below Installation 1, Open...

www.tonymacx86.com

Which you need installed in any case in-order to generate the PPRF's detailed above ...

Cheers
Jay

Hi Jay, thanks again. I have attached my PPRF report. I am not certain if the SSDT aml patch is working or the GFX rename is or is not enabled. I have the dGPU in the normal DGPU slot so that should be fine.

Maybe something is obvious to you in the report:

many thanks!

 

[jaymonkey]

Hi Jay, thanks again. I have attached my PPRF report. I am not certain if the SSDT aml patch is working or the GFX rename is or is not enabled. I have the dGPU in the normal DGPU slot so that should be fine.

@HackintoshNoobie,

You are using Clover to enable the X86PlatFormormPlugin as well as using SSDT-XCOM.aml hot patch, use one method only not both as it may cause issues.



I would disable (uncheck) the option in Clover and let the Hot Patch do the work ...

You are Injecting all your Kexts via Clover see this guide for info on how to install kexts correctly and why :-

[GUIDE] Installing 3rd Party Kexts - El Capitan, Sierra, High Sierra, Mojave, Catalina

Installing 3rd Party Kexts in /Library/Extensions 1. What Versions of MacOS does this guide cover ? The methods detailed in this guide will work on the following versions of MacOS MacOS 10.11.X - El Capitan MacOS 10.12.X - Sierra MacOS 10.13.X - High Sierra MacOS 10.14.X - Mojave MacOS...

www.tonymacx86.com

Cheers
Jay

 

[HackintoshNoobie]

@HackintoshNoobie,

You are using Clover to enable the X86PlatFormormPlugin as well as using SSDT-XCOM.aml hot patch, use one method only not both as it may cause issues.

View attachment 408797

I would disable (uncheck) the option in Clover and let the Hot Patch do the work ...

You are Injecting all your Kexts via Clover see this guide for info on how to install kexts correctly and why :-

[GUIDE] Installing 3rd Party Kexts - El Capitan, Sierra, High Sierra, Mojave, Catalina

Installing 3rd Party Kexts in /Library/Extensions 1. What Versions of MacOS does this guide cover ? The methods detailed in this guide will work on the following versions of MacOS MacOS 10.11.X - El Capitan MacOS 10.12.X - Sierra MacOS 10.13.X - High Sierra MacOS 10.14.X - Mojave MacOS...

www.tonymacx86.com

Cheers
Jay

Hi Jay,

thanks again, one step closer. Here's what I've done:

• Unchecked X86Platformplugin in clover
• Installed kexts to L/E using the guide you wrote (left old ones in Clover/kexts/other though)
  • interestingly with the kexts only in Clover/... and system parameters set to detect, i had no mouse and keyboard at the login screen. That got solved once i installed the kexts to L/E
• I tried verifying if my SSDT-XCOM is working as it should. I dont think i have native power management.
  • Reasons I think so:
    • Output from Hackintool tools output after:

    • IGPU Info:
      ------------------------------------------
      IGPU Current Frequency.................. :    0 MHz
      IGPU Minimum Frequency.................. :  350 MHz
      IGPU Maximum Non-Turbo Frequency........ :  350 MHz
      IGPU Maximum Turbo Frequency............ : 1150 MHz
      IGPU Maximum limit...................... : 3000 MHz

    • Not sure if P-states are normal. seemed different from example given in the official guide:

    • P-State ratio * 100 = Frequency in MHz
      ------------------------------------------
      CPU P-States [ 38 (40) ] iGPU P-States [ ]
      CPU C3-Cores [ 0 4 5 6 ]
      CPU C6-Cores [ 0 1 2 3 4 5 ]
      CPU C7-Cores [ 2 3 4 5 6 7 ]
      CPU P-States [ (8) 25 38 40 ] iGPU P-States [ ]
      CPU C3-Cores [ 0 1 4 5 6 7 ]
      CPU C6-Cores [ 0 1 2 3 4 5 6 7 ]
      CPU P-States [ 8 25 31 38 (40) ] iGPU P-States [ ]
      CPU C3-Cores [ 0 1 3 4 5 6 7 ]
      CPU P-States [ (8) 25 27 31 38 40 ] iGPU P-States [ ]
      CPU C3-Cores [ 0 1 2 3 4 5 6 7 ]
      CPU P-States [ (8) 25 27 29 31 38 40 ] iGPU P-States [ ]
      CPU P-States [ 8 25 27 29 31 38 (40) 41 ] iGPU P-States [ ]
      CPU P-States [ 8 25 27 29 31 38 39 (40) 41 ] iGPU P-States [ ]
      CPU P-States [ 8 25 27 29 31 37 38 39 (40) 41 ] iGPU P-States [ ]
      CPU P-States [ 8 25 27 29 31 36 37 38 39 (40) 41 ] iGPU P-States [ ]
      CPU P-States [ 8 25 27 29 31 36 37 38 39 40 41 (42) ] iGPU P-States [ ]
      CPU P-States [ (8) 25 27 29 30 31 36 37 38 39 40 41 42 ] iGPU P-States [ ]
      CPU P-States [ 8 25 27 29 30 31 33 36 37 38 39 (40) 41 42 ] iGPU P-States [ ]

    • Finally the Intel Power Gadget further shows same GFX values.. 0 baseline and not pegged when using..

Attached a current debug log. Do you have any ideas of what I can try to get the IGPU working correctly with my dGPU?

Much appreciated.

 

[jaymonkey]

Attached a current debug log. Do you have any ideas of what I can try to get the IGPU working correctly with my dGPU?

@HackintoshNoobie,

Why are you enabling the 2048MB VRAM patch for the IGPU ?, it will have no beneficial effect and is just wasting system RAM as the IGPU does not use VRAM when run in headless mode. I'm not sure if that is contributing to the problem or not but you should remove these lines from your config.plist.

                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-unifiedmem</key>
                <data>
                AAAAgA==
                </data>

Intel Power Gadget does not always show the correct readings for the IGPU .. it's a know issue and has got worse with more recent versions of IPG, for example it doesn't show anything on my White Knight build (HD 4600) but the IGPU is working just fine in headless mode.

With the 2048MB VRAM patch removed reboot and then open Activity Monitor, then Click on the "Window" menu and select "GPU History"



In your case you should get two graphs one for the IGPU and one for the dGPU, do some IGPU intensive tasks such as previewing jpegs and videos in Finder ... etc, watch the GPU History graphs for activity.

More info on Activity Monitor GPU History here :-

How to View GPU Usage in macOS via Activity Monitor

macOS and many applications heavily utilize the GPUs in your Mac. Wouldn't it be great to see exactly how much each GPU is being used? Instead of turning to third party apps, check out this tip on using Activity Monitor to see GPU usage.

www.tekrevue.com

Cheers
Jay