WhatEverGreen Support Topic

Andrey1970 · February 13, 2019

41 minutes ago, nijhawank said:

So that's exactly was my question. Is there any use of WEG for Intel 1st Gen Graphics? And you are saying "No".

So any protected video playback fixes (inherited from Shiki) or fixing second stage boot glitch etc. are not applicable or not performed by WEG when using Intel 1st Gen Graphics. Is that a correct statement?

Shiki too did not support Intel 1st Gen Graphics.

Shiki for protected video playback on IVY and newer.

Sandy and older has no problems with protected video playback.

Badruzeus · February 14, 2019

11 hours ago, nijhawank said:

So any protected video playback fixes (inherited from Shiki) or fixing second stage boot glitch etc. are not applicable or not performed by WEG when using Intel 1st Gen Graphics. Is that a correct statement?

"Fix Second Stage Boot Glitch" is working fine with WEG for IntelHD 1st Gen (Arrandale), I've tested on 10.13.6 & 10.14.3.

nijhawank · February 14, 2019

Thanks @Badruzeus

Somehow I'm not able to get rid of that second stage graphics glitch. I tried your suggested KTP, statically pre-patched IOGraphicsFamily kext and WEG v1.2.4 (of course one by one and only one method at a time)

is there any specific section that you put in your config.plist for WEG? I'm asking this because any thread for WEG only talks about Intel 2nd Generation and above and how to enable Framebuffer patching by adding the properties section. Can you share your EFI folder or config.plist for your 1st Gen Graphics laptop.

Badruzeus · February 14, 2019

2 minutes ago, nijhawank said:

Somehow I'm not able to get rid of that second stage graphics glitch. I tried your suggested KTP, statically pre-patched IOGraphicsFamily kext and WEG v1.2.4 (of course one by one and only one method at a time)

is there any specific section that you put in your config.plist for WEG? I'm asking this because any thread for WEG only talks about Intel 2nd Generation and above and how to enable Framebuffer patching by adding the properties section. Can you share your EFI folder or config.plist for your 1st Gen Graphics laptop.

As for 2nd stage boot glitch; could be not related with WEG, but your System Configuration: check Pref - Users & Groups - Login Options. Make sure Automatic login is "OFF".

For backlight; since WEG also included AppleBacklight patches; I use "applbkl=0" boot-arg bcoz I have Rehabman's IntelBacklight.kext loaded. And #OFC not using another KextToPatch related to IOGraphicsFamily.

nijhawank · February 14, 2019

Yes I'm not using auto login. I get a login screen once the system boots.

I am in the same boat as you as I'm also using IntelBacklight and Bergdesign's Brightness aap (my machine, Lenovo T410, probably doesn't expose IGPU PWM registers). However the latest version of WEG break that even if using applbkl=0 or even -wegoff.

Also I checked the config.plist that you attached in the other thread and I noticed that you have no WEG specific configuration and Inject Intel is also false. So how does system know which GPU kext to load? Did you add some device properties in your DSDT/SSDT, can you share that (I know it won't be directly useful but just would like to see any thing graphics related you might have added).

The other difference is using MBP6,2 (mine) vs MBP10,1 (your). I don't want to mess with that because I have perfectly running iMessage/icloud.

Much appreciated for bearing my non-stop questions.

Badruzeus · February 14, 2019

36 minutes ago, nijhawank said:

Yes I'm not using auto login. I get a login screen once the system boots.

I am in the same boat as you as I'm also using IntelBacklight and Bergdesign's Brightness aap (my machine, Lenovo T410, probably doesn't expose IGPU PWM registers). However the latest version of WEG break that even if using applbkl=0 or even -wegoff.

I have 2 options which are working, I only use 1 of them for sure:

1. KextToPatch method (for 2nd Stage Boot Glitch) + IntelBacklight.kext

2. WEG (for 2nd Stage Boot Glitch) + "applbkl=0" boot-arg + IntelBacklight.kext

Option [1] is easier on my case. Both of them are with patched DSDT related Graphics + Brightness (PNLF)

36 minutes ago, nijhawank said:

Also I checked the config.plist that you attached in the other thread and I noticed that you have no WEG specific configuration and Inject Intel is also false. So how does system know which GPU kext to load?

I believe you're referring to this post, it was when I use Option [1] < w/o WEG. No need injectIntel=true for Intel Graphics 1st Gen, but only PatchVBios=true (but it' s still useful for pre-install with Fake IntelGfx to reach installation).

Terminal: kextstat will tell you which GPU kext loaded. Terminal: bdmesg also give you info which kexts loaded on preboot (\efi\clover\kexts\xxxx)..

36 minutes ago, nijhawank said:

Did you add some device properties in your DSDT/SSDT

Nothing special, just following @GhostRaider guide for patching DSDT (Graphics), and old @mnorthern topic for brightness.

36 minutes ago, nijhawank said:

The other difference is using MBP6,2 (mine) vs MBP10,1 (your). I don't want to mess with that because I have perfectly running iMessage/icloud.

No difference about which SMBios version used related to IntelHD Graphics 1st Gen. On my case is using MBP10,1 bcoz MBP6,2 has been dropped since Mojave (I use 10.14.3 on my case). No need changing SMBios on 10.13.x or lower.

#OP: Sorry if my reply contains OffTopic.

Edited February 14, 2019 by Badruzeus

Andrey1970 · February 14, 2019

6 hours ago, nijhawank said:

using IntelBacklight and Bergdesign's Brightness aap (my machine, Lenovo T410, probably doesn't expose IGPU PWM registers). However the latest version of WEG break that even if using applbkl=0 or even -wegoff.

I already spoke to you about IOProbeScore 5500, but you did not hear.

Maybe this post for you will be more clear.

nijhawank · February 14, 2019

I thought that ioprobescore is for specifically setting in custom backlight injector but I will try adding it for intelbacklight and state my results.

reece394 · February 14, 2019

First off thanks for the information in this thread @Andrey1970 and @Pavo. When I was reading through it helped me understand Shiki a bit better. I am trying to get iTunes DRM working and I have been hitting a lot of brick walls. However with the information on this thread it is closer to working than ever. I am trying to get the DRM to work on an internal screen here. I am using an XPS 9550 with HD530 integrated graphics (Skylake). With your information with downloaded iTunes content I can now get it to display for a few seconds on iTunes before it complains that "The selected film won't play on your display." HDCP error. For main SMBIOS I am using MacBookPro13,3 as that is closest to my laptops configuration. For Shiki I set the board ID to Mac-4B682C642B45593E (iMac18,1) and used shikigva=40. Attached is my config.plist, Kexts and System report from Kext Updater, screenshots of the error and results of VDADecoderChecker. Graphics acceleration is active and working and DRM is working on the internal screen through Firefox just Safari and iTunes are the problem. I have tried different shikigva numbers etc and I am no closer to figuring out why this is happening. Any help would be greatly appreciated. Any additional attachments I will provide if required. With Hackintool I saw in Displays there is an option to inject EDID to an iMac or MacBook Air display as my screen is 16:9. Is this maybe a potential solution?

Thanks in advance

Reece

Systemreport.zip

Andrey1970 · February 14, 2019

2 hours ago, reece394 said:

With your information with downloaded iTunes content I can now get it to display for a few seconds on iTunes before it complains that "The selected film won't play on your display." HDCP error.

This problem on all IGPU(Ivy Bridge and newer) in solo mode.

Edited February 15, 2019 by Andrey1970

reece394 · February 14, 2019

1 minute ago, Andrey1970 said:

This problem on all IGPU in solo mode.

Ah okay so no fix for it. I am glad I didn’t make a stupid error thanks for the quick reply @Andrey1970

Andrey1970 · February 14, 2019

3 minutes ago, reece394 said:

Ah okay so no fix for it. I am glad I didn’t make a stupid error thanks for the quick reply @Andrey1970

On notebooks not to solve it.
On desktops it is possible to solve it - use dGPU and IGPU for IQSV only.

uglyJoe · February 16, 2019

On 2/14/2019 at 10:37 PM, reece394 said:

First off thanks for the information in this thread @Andrey1970 and @Pavo. When I was reading through it helped me understand Shiki a bit better. I am trying to get iTunes DRM working and I have been hitting a lot of brick walls. However with the information on this thread it is closer to working than ever. I am trying to get the DRM to work on an internal screen here. I am using an XPS 9550 with HD530 integrated graphics (Skylake). With your information with downloaded iTunes content I can now get it to display for a few seconds on iTunes before it complains that "The selected film won't play on your display." HDCP error. For main SMBIOS I am using MacBookPro13,3 as that is closest to my laptops configuration. For Shiki I set the board ID to Mac-4B682C642B45593E (iMac18,1) and used shikigva=40. Attached is my config.plist, Kexts and System report from Kext Updater, screenshots of the error and results of VDADecoderChecker. Graphics acceleration is active and working and DRM is working on the internal screen through Firefox just Safari and iTunes are the problem. I have tried different shikigva numbers etc and I am no closer to figuring out why this is happening. Any help would be greatly appreciated. ...

Just a thought, but if the film is playing on an external display, it may helps to patch the framebuffer to mimic an external display.

To have DP-Audio with my display, I patched the flags of con2 from 11 to 87.

With the default value of 11, my display is shown as internal and didn't offer any audio via DP.

After patching the flags to 87 (the value was copied from the other connectors) my display becomes to be an external with DP-Audio available.

As an example, these are my injected device properties

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Properties</key>
	<dict>
		<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
		<dict>
			<key>AAPL,ig-platform-id</key>
			<data>AwAiDQ==</data>
			<key>device-id</key>
			<data>EgQAAA==</data>
			<key>framebuffer-con2-enable</key>
			<data>AQAAAA==</data>
			<key>framebuffer-con2-type</key>
			<data>AAQAAA==</data>
			<key>framebuffer-con2-flags</key>
			<data>hwAAAA==</data>
			<key>framebuffer-con1-enable</key>
			<data>AQAAAA==</data>
			<key>framebuffer-con1-type</key>
			<data>AAgAAA==</data>
			<key>framebuffer-con0-enable</key>
			<data>AQAAAA==</data>
			<key>framebuffer-con0-type</key>
			<data>AAgAAA==</data>
			<key>framebuffer-patch-enable</key>
			<data>AQAAAA==</data>
		</dict>
	</dict>
</dict>
</plist>

Monkey303 · February 16, 2019

Hi,

This is my first Hackintosh and I need some info please.

I am running RX 560 with Intel IGPU enabled to fix thumbnails , 8700k, Z390-i, NVME SSD.

So I was streamlining my kexts and got it down to 5 in the EFI/clover/kexts/other folder, just leaving AppleALC, FakeSMC, IntelMAUSIethernet, lilu, usbinjectall. All was working well and then I found that I had whatever green and some others, FakeSMC and it's accompanying files in my library/extensions folder, so I deleted them. After that I couldn't boot. I've managed to get it back to a bootable state again, but I am having 75-100% GPU usage when doing nothing and also around 75% GPU men usage when doing nothing, too.

As far as I was aware, the RX 560 should work OOB, so do I need lulu and whatevergreen? If it is safe to get rid of them, what is the easiest way to effectively do it for a complete noob, such as me! I have removed it from my refi/clover/kexts/other, but last time I removed it from library extensions, I could not boot.

Could anyone please help? Thanks :)

vit9696 · February 16, 2019

On 1/25/2019 at 10:06 AM, gujiangjiang said:

I found -cdfon or hdmi-20 must use SIP(Allow Unrestricted FS) or it will not work.

But with classic CDF kexts dont need use this SIP(Allow Unrestricted FS).

Fixed in Lilu master. Enjoy.

nijhawank · February 16, 2019

On 2/14/2019 at 6:20 AM, Andrey1970 said:

I already spoke to you about IOProbeScore 5500, but you did not hear.

Maybe this post for you will be more clear.

I updated the IOProbeScore to 5500 in IntelBacklight and updated to WEG v1.2.6.

Rebuilt kextcache and added applbkl=0 to boot Params.

Rebooted and macos never reached the login screen.

So guess IOProbeScore=5500 trick is only for custom AppleBacklightInjector and doesn't work with IntelBacklight.

Edited February 16, 2019 by nijhawank

Hackmodford · February 17, 2019

Can anyone help me to get iTunes DRM playback to work with my GTX 760 and i7 3770k HD4000? Right now, iTunes just crashes if I try to play a downloaded tv show. And Netflix in the browser just displays a green screen.

I have Lilu + Whatevergreen and have injected platform-id via clover.

Is there anything else I should be doing?

Pavo · February 17, 2019

50 minutes ago, Hackmodford said:

Can anyone help me to get iTunes DRM playback to work with my GTX 760 and i7 3770k HD4000? Right now, iTunes just crashes if I try to play a downloaded tv show. And Netflix in the browser just displays a green screen.

I have Lilu + Whatevergreen and have injected platform-id via clover.

Is there anything else I should be doing?

If you are on Mojave there isn't any Nvidia web drivers for Mojave yet.

Hackmodford · February 17, 2019

1 minute ago, Pavo said:

If you are on Mojave there isn't any Nvidia web drivers for Mojave yet.

Does this mean that, theoretically, the NVIDIA web drivers would solve the issue? Because I seem to be running fine without them.

reece394 · February 17, 2019

On 2/16/2019 at 8:58 AM, uglyJoe said:
Just a thought, but if the film is playing on an external display, it may helps to patch the framebuffer to mimic an external display.

To have DP-Audio with my display, I patched the flags of con2 from 11 to 87.

With the default value of 11, my display is shown as internal and didn't offer any audio via DP.

After patching the flags to 87 (the value was copied from the other connectors) my display becomes to be an external with DP-Audio available.

As an example, these are my injected device properties
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Properties</key>
	<dict>
		<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
		<dict>
			<key>AAPL,ig-platform-id</key>
			<data>AwAiDQ==</data>
			<key>device-id</key>
			<data>EgQAAA==</data>
			<key>framebuffer-con2-enable</key>
			<data>AQAAAA==</data>
			<key>framebuffer-con2-type</key>
			<data>AAQAAA==</data>
			<key>framebuffer-con2-flags</key>
			<data>hwAAAA==</data>
			<key>framebuffer-con1-enable</key>
			<data>AQAAAA==</data>
			<key>framebuffer-con1-type</key>
			<data>AAgAAA==</data>
			<key>framebuffer-con0-enable</key>
			<data>AQAAAA==</data>
			<key>framebuffer-con0-type</key>
			<data>AAgAAA==</data>
			<key>framebuffer-patch-enable</key>
			<data>AQAAAA==</data>
		</dict>
	</dict>
</dict>
</plist>

Thanks for the response @uglyJoe I tested it on an external display and the same messages appeared. I expected that. Sadly WhatEverGreen and Shiki can't be used for just iGPU DRM fixing. Maybe in future if someone figures out why it doesn't work. For now I will just deal with not using iTunes or Safari. I still appreciate the awesome work as it means I no longer have to manually patch my 4K screen. Apple Backlight Injection is handled too and WhatEverGreen is improving all the time.

Alex HQuest · February 27, 2019

On 2/6/2019 at 5:11 PM, dreamwork said:

Yes, I have the same KP with IGP enable. Tryed different framebuffers,but without luck.

I decided to give this another go today, with updated Clover and LiLu plug-ins. And it worked! My Preview app is recovered as well, so it might be worth a shot for you too.

Hackmodford · February 27, 2019

4 minutes ago, Alex HQuest said:

I decided to give this another go today, with updated Clover and LiLu plug-ins. And it worked! My Preview app is recovered as well, so it might be worth a shot for you too.

I changed my SMBIOS def to 13,2 and got preview working. But I'm still getting black/green screens in iTunes/Netflix (iTunes usually just crashes).

bodun242-1 · March 2, 2019

Hello! Have an bug - when i'm turning off my Hack (booted in verbose mode) - i'm getting some strange stripes instead of normal text. It's not critical, but not nice too. Have any solution for this? Thank you.

And yes - i'm using latest version of whatevergreen and lilu

Edited March 2, 2019 by bodun242-1

Tusskan · March 2, 2019

How to get two monitors to work with R9 290X on ozmosis with WEG? I tried tweaking the SSDT example but I failed many times, the secenario here is that when I boot with two monitors one (DP) two(DVI) I get the verbose text but when I reach the desktop point it shows black screen, I know the solution with this is an SSDT, does anyone one have that one to save me the hassle of relearning the SSDT Patching ? thank you. The one from the first post doesn't work, and the one from the page 7 works but only one screen works which has the DVI connector the other one which is DP connector doesn't work it gives no signal

Edited March 3, 2019 by Tusskan

Hameer Abbasi · March 7, 2019

On 1/30/2019 at 1:58 PM, Alex HQuest said:

Did anybody else lost IGP after installing 10.14.4 beta? My discrete VGA is working like a champ but I had to disable IGP on BIOS to go past KP. Booting recovery, using an invalid graphics id and/or invalidating/creating new kernel cache did not helped at all. Only missing feature (I noticed) is the display mirroring option.

Mojave 10.14.4 Beta 18E174f, Lilu 1.3.1, WhateverGreen 1.2.6, Clover 4862

debug_228.zip

Can confirm. Mine didn't KP but WEG definitely isn't working. It's not injecting the iGPU, and pretty sure it's not injecting the dGPU (wrong framebuffer), but the kext is listed in kextstat.

Okay, so I did some digging... It seems the Kamarang framebuffer only loads if there are 4 or fewer ports, it doesn't load for 5 or higher. I played around with SSDT injection and editing to test this. I'm assuming this can be handled with a binary patch, and can fix issues with those Vega 64's that have 6 ports.

Alternatively, we can patch the number of ports to 4, which would disable some ports. I didn't need VegaTab or any other hacks with my ports limited to 4. @vit9696, this time I will tag you (again, sorry if it's unwelcome), I have no idea how binary patching works, so I can't patch the kext for more than 4 ports.

Edited March 9, 2019 by Hameer Abbasi

WhatEverGreen Support Topic

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites