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

[AlienHrGig]

@AlienHrGig,

It is not possible to passthrough dGPU to IGPU ports (or vice-versa) on MacOS, if you want to stick with your Nvidia GPU then your best bet would be to use High Sierra with latest Nvidia web drivers, connect your displays to the Nvidia card and configure IGPU as headless.

If you want to run Mojave with your current hardware then your only option is to use IGPU and disable the Nvidia via software method :-

Cheers Jay, thank you for the answer.
I'm not trying to use my Nvidia dGPU, I'm quite ok with my iGPU, this runs buttery smooth.
My real issue is getting dual screen output since my motherboard has only DVI+VGA and I cannot use this combo to output to newer screens because of the VGA port.

But I guess that maybe the only solution would be to buy either a new motherboard or a new dGPU.

thank you for the help anyways. And thank you for the amazing guide.

 

[jaymonkey]

I'm not trying to use my Nvidia dGPU, I'm quite ok with my iGPU, this runs buttery smooth.My real issue is getting dual screen output since my motherboard has only DVI+VGA and I cannot use this combo to output to newer screens because of the VGA port.

@AlienHrGig,

Ahh I see ... yes thats a dilemma ... as you say that IGPU port combo is quite limiting.

Maybe pick up a used RX 580/590 on eBay ?
If you want to spend a little more you can pick up a Vega 56/64 cheaply on ebay if you look around a bit.

I got my Vega 64 LC on eBay ... works great and i do not regret switching to AMD one bit.

Cheers
Jay

 

[AlienHrGig]

@AlienHrGig,

Ahh I see ... yes thats a dilemma ... as you say that IGPU port combo is quite limiting.

Maybe pick up a used RX 580/590 on eBay ?
If you want to spend a little more you can pick up a Vega 56/64 cheaply on ebay if you look around a bit.

I got my Vega 64 LC on eBay ... works great and i do not regret switching to AMD one bit.

Cheers
Jay

Jay, sorry to bother.
I started using my mackintosh now and started to realise not all is ok.

I noticed that certain processes fire up the CPU usage and the temperature raises quickly to over 90ºC.
I'm assuming this is related to Power States, I found a advice you gave on another thread about installing SSDT-XCPM.aml and I have done so. I tried iMac 15,1 and Mac Pro 5,1 SMBIOS settings. Disabled the generate p and c states in clover configurator but even though performance is even smoother the cpu still fires up with some tasks.

Typically video conversion, compile tasks that are done on first run of certain apps and so on. I might just be randomly doing normal usage and he starts overheating and either I have to reset my machine or try to open Activity Monitor quickly and close the task causing it not to damage my hardware. (issue is not the cooler, its the factory one bundled with the cpu and it works fine in windows 10 playing games and so on)

I noticed you have a i7 4790K, same as me. Difference is that I'm not overclocking and I have a Z97x Gigabyte instead of ASRock. Can you provide some tips on how you configured your P and C States and if you had any issue similar?

My processes show apps going up to 900% cpu usage if it helps.

Edit:
Strangest thing I noticed, I can run a geekbench with no issues. Power goes up and temperature within normal limits.
If I convert H264 video with handbrake it spikes slowly, if I convert H265 it spikes in 2 seconds.
I can't figure out what can cause this.

 

[jaymonkey]

I noticed you have a i7 4790K, same as me. Difference is that I'm not overclocking and I have a Z97x Gigabyte instead of ASRock.

@AlienHrGig,

Using SSDT-XCPM.aml to force MacOS to use X86PlatformPlugin should be all that is needed ... you can check to see if its worked by running IORegistryExplorer and searching for "X86PlatformPlugin" if its found then the SSDT-XCPM.aml is doing its job and MacOS should be using native Intel Power management.

Of course it also depends on how well your motherboard and BIOS supports the feature, some motherboards work better than others ... I had a few hick-ups with mine until I updated the BIOS to the latest version which included an update to the Intel ME (Management Engine) ... so check to see if there is an update for your BIOS.

Failing that you could fall back to using Intel Speed Step using Pike Alpha's ssdtPRGen script to generate a custom SSDT, if you do remember to delete SSDT-XCPM.aml and effectively replace it with the SSDT.aml that the script generates.

@RehabMan has a good guide on using Pike Alpha's ssdtPRGen script in this post :-

[Guide] Native Power Management for Laptops

Overview Power Management should be one of the first things implemented when trying to install OS X on a laptop. Because of heat/noise and battery life issues, using NullCPUPowerManagement is not a realistic option on a laptop. Fortunately, with Clover, NullCPUPowerManagement is never needed...

www.tonymacx86.com

See the section titled "Custom SSDT.aml using ssdtPRGen.sh"

Cheers
Jay

 

[djashjones]

I don't know what I've done but I've lost hardware decoding. This setup was working, any ideas?

 

[jaymonkey]

I don't know what I've done but I've lost hardware decoding. This setup was working, any ideas?

@djashjones,

Thats usually caused by WhatEverGreen not loading correctly or a bad configuration in your config.plist.

Try deleting Lilu + WhatEverGreen from /L/E then re-download and re-install.

Cheers
Jay

 

[djashjones]

The issue was when I updated my bios, it changed how the IGPU and DGPU was set up. I only have 2 options now.

primary set to PEG and enable multiple monitors.

Ran through the Hackintool again and had to re-tweak it but it's all finally working again.

 

[jaymonkey]

The issue was when I updated my bios, it changed how the IGPU and DGPU was set up. I only have 2 options now.

primary set to PEG and enable multiple monitors.

Ran through the Hackintool again and had to re-tweak it but it's all finally working again.

@djashjones,

Yeha, I had that a few years ago on my ASRock motherboard, where the IGPU options where replaced with "Enable IGPU Multi-Monitor Mode" .. I read it as allow more than one monitor plugged into the IGPU but it actually means enable the IGPU alongside the dGPU ... bit confusing i think but it seems to have become the standard term these days.

Glad your backup and running.

Cheers
Jay

 

[AlienHrGig]

@AlienHrGig,

Using SSDT-XCPM.aml to force MacOS to use X86PlatformPlugin should be all that is needed ... you can check to see if its worked by running IORegistryExplorer and searching for "X86PlatformPlugin" if its found then the SSDT-XCPM.aml is doing its job and MacOS should be using native Intel Power management.

Indeed enough it was Jay.
Already found the issue, my MB in the latest firmware does not apply correct power settings for the Intel Cooler and since Mac OS pulls more performance it becomes more evident the heat generation. Already fixed by limiting the watts and amps for the cores on turbo.

But i found another issue, my MB does have 3 display ports, 1x DVI, 1x VGA and 1x HDMI so i can actually connect two displays.
Thing is, if i boot in safe mode he mirrors the image to both screens, but if i boot with the iGPU working with hardware acceleration i get garbage on the DVI port and normal image on HDMI. As soon as i disconnect the HDMI cable the DVI port starts working again with no issues. (i tried applying the Intel HDMI fix and also selecting type of port and injecting it in the patch but got same results).

Any idea what i can do to fix this?

Attached image with what happens in the DVI port when both are connected:

 

[jaymonkey]

if i boot with the iGPU working with hardware acceleration i get garbage on the DVI port and normal image on HDMI. As soon as i disconnect the HDMI cable the DVI port starts working again with no issues. (i tried applying the Intel HDMI fix and also selecting type of port and injecting it in the patch but got same results).

@AlienHrGig,

When patching the IGPU frame buffer connectors the "Pipe" number and "flags" can have an effect on how well that port works, i had something similar on one of my systems, in addition to patching the connectors "type" to HDMI I also changed the "pipe" to 0x12 on both ports and the "flags" to 0x06 ..

                <key>framebuffer-con1-enable</key>
                <integer>1</integer>
                <key>framebuffer-con1-flags</key>
                <data>
                BgAAAA==
                </data>
                <key>framebuffer-con1-pipe</key>
                <data>
                EgAAAA==
                </data>
                <key>framebuffer-con1-type</key>
                <data>
                AAgAAA==
                </data>
                <key>framebuffer-con2-enable</key>
                <integer>1</integer>
                <key>framebuffer-con2-flags</key>
                <data>
                BgAAAA==
                </data>
                <key>framebuffer-con2-pipe</key>
                <data>
                EgAAAA==
                </data>
                <key>framebuffer-con2-type</key>
                <data>
                AAgAAA==
                </data>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-unifiedmem</key>
                <data>
                AAAAgA==
                </data>
            </dict>

The value of "12" for the pipe i got from @rehabmans HDMI audio guide and the flag value of "06" i got from a system where HDMI was already working ....

You could try changing the "pipe" to 12 on both the HDMI and DVI port and set the HDMI flag value to "06" as for the flag value of your DVI port .. I cant help you that ..

Cheers
Jay