WhatEverGreen Support Topic

[Michelinu]

DP audio still not working.

I have to use the old 1.1.7

[wujek_bogdan]

On 7/24/2018 at 3:35 PM, wujek_bogdan said:

@vit9696

I've just replaced the NvidiaGraphicsFixup kext with the new version of WhatEverGreen and I think I found a bug.

 

So far I've been using NvidiaGraphicsFixup + ngfxpatch=pikera boot arg that solved a High Sierra black screen after wake-up problem. Now, after replacing NvidiaGraphicsFixup with WhatEverGreen, the screen does not wake up properly after sleep. No matter is it auto-sleep or manual sleep (chosen from the Apple menu).

 

I see that ngfxpatch=pikera became agdpmod=pikera - I tried both, just in case, but it doesn't help.

 

// EDIT:

I've just found some weirdness. When I use the agdpmod=pikera flag (which, I assume, is a replacement for the ngfxpatch=pikera flag) then, on a log-in screen I have full HD resolution instead of 4K res. When I use the ngfxpatch=pikera (which is deprecated, I guess) then the log-in screen resolution is fine.

 

---

macOS 10.13.6, MSI GTX960 running 4k res, Nvidia Web Driver 387.10.10.10.40.105, Z87M-PLUS

Clover config: https://pastebin.com/ByDwhW8z

Kexts:

AppleALC.kext

FakeSMC_CPUSensors.kext

FakeSMC_LPCSensors.kext

RealtekRTL8111.kext

WhateverGreen.kext
FakeSMC.kext

FakeSMC_GPUSensors.kext Lilu.kext

Lilu.kext

SATA_Legacy.kext

 

All kexts up to date. Including Lilu.

 

I'd like to confirm that the wakeup issue is gone after updating WhateverGreen to v1.2.1, but the login screen resolution issue still remains. 

[jaymonkey]

On 8/13/2018 at 9:11 PM, gujiangjiang said:

With the latest WhateverGreen1.2.1 there is no use in CoreDisplay Fix with high resolution support.

I downgrade the WhateverGreen to 1.2.0 and get the CDF Patched support again.

 

Update:

Now i tried to add bootarg with [-cdfon] and the cdf patch come back and works well.

 

Can confirm the same happens on my 2017 15" HP Spectre X360.

 

With WEG 1.2.0 installed the 4K display on my laptop was 60Hz, after updating to WEG 1.2.1 the 4K refresh rate was down to 40Hz

Added the -cdfon boot flag and rebooted and the refresh rate was back to 60Hz

 

Maybe this change is by design ?

 

Cheers

Jay

[headkaze]

49 minutes ago, jaymonkey said:

Maybe this change is by design ?

 

WhateverGreen disables CDF patch by default. Now you must add -cdfon boot-arg or enable-hdmi20 IGPU entry in Devices/Properties

On 7/29/2018 at 1:26 PM, vit9696 said:
Regarding black screen issues, it looks like CDF code was causing issues, and it is now optional in the latest master.

Edited August 16, 2018 by headkaze

[jaymonkey]

5 hours ago, headkaze said:

 

WhateverGreen disables CDF patch by default. Now you must add -cdfon boot-arg or enable-hdmi20 IGPU entry in Devices/Properties

 

@headkaze,

 

Many thanks for the clarification .... 

 

Cheers

Jay

[jaymonkey]

@headkaze,

 

I'm still unable to use WhatEverGreen on my desk top system that has a single Nvidia 980 TI GPU ...

Detailed report of the issue is in this post on the previous page

 

Since then I've tried building WEG from the source's as suggested by pavo but it gave the same result as both official release versions 1.2.0 and the recently released 1.2.1.

 

As stated in that post using NvidiaGraphicsFixUp works fine .... deleting it and installing WEG results in a KP, I am using the latest Lilu kext (1.2.6)

Have not had any issues with WEG on all my other systems but those are using Intel IGPU.

 

Nvidia HDMI Audio is working via AppleALC so i don't think its a frame buffer issue.

 

Do you have any thoughts on the issue or how best to go about debugging the problem ?

 

Cheers

Jay

[Pavo]

3 hours ago, jaymonkey said:

@headkaze,

 

I'm still unable to use WhatEverGreen on my desk top system that has a single Nvidia 980 TI GPU ...

Detailed report of the issue is in this post on the previous page

 

Since then I've tried building WEG from the source's as suggested by pavo but it gave the same result as both official release versions 1.2.0 and the recently released 1.2.1.

 

As stated in that post using NvidiaGraphicsFixUp works fine .... deleting it and installing WEG results in a KP, I am using the latest Lilu kext (1.2.6)

Have not had any issues with WEG on all my other systems but those are using Intel IGPU.

 

Nvidia HDMI Audio is working via AppleALC so i don't think its a frame buffer issue.

 

Do you have any thoughts on the issue or how best to go about debugging the problem ?

 

Cheers

Jay

This might not be the case but with all the issues you have been having with using WEG, AppleALC and among other things, it might be best to wipe your system and start from scratch. It sounds like you have done to many changes for anything to actually work.

[jaymonkey]

On 8/17/2018 at 4:24 PM, Pavo said:

This might not be the case but with all the issues you have been having with using WEG, AppleALC and among other things, it might be best to wipe your system and start from scratch. It sounds like you have done to many changes for anything to actually work.

 

@Pavo,

 

Two completely different systems buddy ... The AppleALC issues have been on my laptop which is Intel IGPU ... and those where specifically to do with getting audio working with the Mojave beta, which is booted on a external SSD and a completely different build to the stable 10.13.6 build that i run on it .. its my daily driver so it has to be 100% stable.

 

The WEG issue that I reported on the previous page is on my Desktop Video Editing System running High Sierra 10.13.6 .. its a very stable system used for video editing and content creation, I will not be testing Mojave beta on this system. I will only update it to Mojave when the final release is made in September and Nvidia get around to releasing web drivers for Mojave. I might even wait until 10.14.2. 

 

However as i have migrated my other Hackingtosh systems (I have 4 in total) successfully to WEG I decided to give WEG ago on my video editing system, all i did was update Lilu to 1.2.6, remove NvidiaGraphicsFixUp and install WEG which resulted in the KP. Removing WEG and re-installing NvidiaGraphicsFixUp and the system is fine (with Lilu 1.2.6 installed)

 

Its not critical to get WEG running on this system right away for the reasons i mentioned above, I just thought it would be good to migrate it to WEG as you've dropped all development on NvidiaGraphicsFixUp and having WEG working on it should help when the time does come to update to Mojave.

 

It seemed odd that simply replacing NvidiaGraphicsFixUp with WEG did not work on this system as all the WEG install criteria have been met as such I reported it here as I would have thought many users who are currently using NvidiaGraphicsFixUp will be doing the same in anticipation of Mojave and due to NvidiaGraphicsFixUp being depreciated.

 

Cheers

Jay

 

Update: Problem now solved, found a rouge copy of NvidiaGraphicsFixUp in Clovers Kext folder ... my bad

Edited August 23, 2018 by jaymonkey

[Guest]

Hi,

my specs are 
i5 2500S

8GB RAM
GTX 950
1TB HDD

I'm on 10.13.6 , all I have now is able to boot to desktop with integrated graphics(8mb vram) not acceleration obviously.
When using Latest Lilu 1.2.6 and WhatEverGreen 1.2.1 with Web drivers installed and turned on it just gives me this screen here during the part where the login should appear. I can see my cursor move in that garbled screen and blindly logging in would bring me to a garbled desktop. (I've searched a bit on this and no it's not the Wallpaper too)

[bronxteck]

have you tried sleeping then waking the machine when you get that screen issue

[Guest]

3 hours ago, bronxteck said:

have you tried sleeping then waking the machine when you get that screen issue

I couldn't really make it sleep, but I let it run like that and I think it did sleep but when I tried "waking" it up , no signal from the monitor but I can hear it responding to my keyboard press and mouse.

I even tried  unplugging HDMI and plugging it back again but same results

[derek.zhu]

using whatevergreen doesn't seem to support clover's edid patch.
not sure if it is more of clover issue or whatevergreen, it might have something to do with clover 'inject intel' being unselected, the system failed to recognize a patched edid ("horizontalsync pulsewidth") which results in a garbled screen (on my hd4600)

I can do manually inject a patched edid using properity or dsdt apporach, however I don't think hard coding it is the best way to go.

I have no idea why did horizontalsync pulsewidth make such differences, but it is indeed effective. I'm not skilled enough to dig into framebuffer file and reverse engineer so I'll have to count on you talented people.

attached is my display properity file, notice the edid are different

P.S. the default device id:0x0D26 from the patcher also gives me a garbled screen (much server than the one without edid patch), with unpatched edid, I can still use vnc and see a perfectly fine screen, with 0x0D26 deviceid, even vnc connected remote desktop is garbled for some reason. device id that worked for me is <12 04 00 00>

 

whatevergreep_display_properity.zip

[gujiangjiang]

Hello

 

The DVMT patch is not functional on macOS 10.13.6 i have tested yet.

 

I tested with latested WEG and delete DVMT and it in kernel panic.

 

When i add DVMT kext again and it be well.

 

Does it should any boot-arg for DVMT patch and i tried -cdfon but no use.

 

 

[headkaze]

2 hours ago, gujiangjiang said:

The DVMT patch is not functional on macOS 10.13.6 i have tested yet.

 

If you need to patch DVMT pre-alloc to 32 MB then add the following to your config.plist/Devices/Properties for IGPU:

                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-fbmem</key>
                <data>AACQAA==</data>
                <key>framebuffer-stolenmem</key>
                <data>AAAwAQ==</data>

Edited August 24, 2018 by headkaze

[gujiangjiang]

23 minutes ago, headkaze said:

 

If you need to patch DVMT pre-alloc to 32 MB then add the following to your config.plist/Devices/Properties for IGPU:

                <key>framebuffer-patch-enable</key>
                <data>AQAAAA==</data>
                <key>framebuffer-fbmem</key>
                <data>AACQAA==</data>
                <key>framebuffer-stolenmem</key>
                <data>AAAwAQ==</data>

 

Thanks for your help.

I use IntelGraphicsDVMTFixup to fix the DMVT problem and now this kext was replaced by WhateverGreen but test failed.

When i get back to the IntelGraphicsDVMTFixup and it works well with no problem.

 

https://github.com/acidanthera/Lilu/blob/master/KnownPlugins.md

 

So i supposed that the WhateverGreen have problem in DVMT patch so we still need IntelGraphicsDVMTFixup to solve the DVMT problem.

[headkaze]

1 hour ago, gujiangjiang said:

So i supposed that the WhateverGreen have problem in DVMT patch so we still need IntelGraphicsDVMTFixup to solve the DVMT problem.

 

I just showed you how to patch DVMT using WhateverGreen.

[XantheFIN]

I ended up getting Whatevergreen.kext working with hd4600 but it feels like same as itunes freezes playback as because of hdcp problem. I believe it was not needed FakeID setting in clover config.plist which ended up not loading up driver.

[hguandl]

Hi, I've met a problem that I the monitor which rotates 90º would not display properly about the computer boots.

It can be seen that there are strange black blocks on the left screen. The image is not rotated, but the mouse moves normally. It seems that the screen is not rotated even if the system regards it as rotated screen.

 

After I come to the preferences and set the rotation again, it becomes normal. But if I reboot the computer, this issue would happen again.

I wonder if this is a bug since whatevergreen v1.2.0. It works well before this version.

 

My graphic card is ASUS RX 580.

Kexts:

AppleALC

Lilu

Whatevergreen

XHCI-200-series-injector

USBInjectAll

RealtekRTL8111

FakeSMC

Edited September 1, 2018 by hguandl

[Roger Smith]

Than you for implementing lilucpu=N option in lilu. Much appreciated.

[DmitryX82]

Hello, I am the owner of the motherboard socket 775 ga-ep35ds3l and AMD RX560, 
I get a black screen when I try to boot to the desktop in High Sierra 13.4-13.6. 
Please, tell me if I can make a video card on my motherboard? 
Is there anyone who managed to get AMD RX560 and socket 775?

Edited September 1, 2018 by DmitryX82

[yamahahornist]

Hey, I need some help. I am dealing with a head scratcher... So my laptop uses an AMD R9 375 (firepro w5170m)(device ID 6820, native in AMD7000Controller). And I am having some issues with ssdt patching with whatevergreen. So I am trying to inject an EDID, model name, and custom connectors because my laptop uses eDP not LVDS. 

 

On my ssdt my graphics card is at _sb.pci0.peg0.pegp not _sb.pci0.peg0.gfx0. Well whenever I use whatevergreen it changes pegp to gfx0. Which I think is causing issues when I try to modify my ssdt. 

 

If I use the path _sb.pci0.peg0.pegp, the model name will change to what I set it, but EDID and the connectors will not change.  IOREG will say the connecter type is still 0x2 (LVDS), and the EDID is incorrect which causes low color depth for my system. 

 

If I use path _sb.pci0.peg0.gfx0 nothing will apply in my patch... 

 

Also I thought maybe it's not getting my video bios. So I extracted the .rom file (62kb, so I know I need to pad at the end 2kbs of zeros) but I am unsure on how to get it in the correct format for the SSDT patch, the .rom is thousands of lines; I doubt it all goes into the SSDT patch.??

 

Any help would really be awesome, thanks in advance. 

Edited September 1, 2018 by yamahahornist

[mitch_de]

13 hours ago, DmitryX82 said:

Hello, I am the owner of the motherboard socket 775 ga-ep35ds3l and AMD RX560, 
I get a black screen when I try to boot to the desktop in High Sierra 13.4-13.6. 
Please, tell me if I can make a video card on my motherboard? 
Is there anyone who managed to get AMD RX560 and socket 775?

Hi, i use LILU+WEG since long time with mx RX 460 (similar to RX 560). Should work.

In MB-BIOS AMD GPU should be primary.

Which port do you use for monitor? Sometimes not all ports (DVI, DP, HDMi) works out of the box, even with WEG.

First try change to other port (if you can) to verify if its an port problem and WEG works in general.

Also check if you have any DSDT /SSDT files in use wich belong to the GPU (for naming, setting ports etc.) can interfernence to WEG.

Also check if you use RADEINIT (an clover option, i think in the gpu section) if set, disable that.

 

 

[Slice]

1 hour ago, mitch_de said:

Hi, i use LILU+WEG since long time with mx RX 460 (similar to RX 560). Should work.

In MB-BIOS AMD GPU should be primary.

Which port do you use for monitor? Sometimes not all ports (DVI, DP, HDMi) works out of the box, even with WEG.

First try change to other port (if you can) to verify if its an port problem and WEG works in general.

Also check if you have any DSDT /SSDT files in use wich belong to the GPU (for naming, setting ports etc.) can interfernence to WEG.

Also check if you use RADEINIT (an clover option, i think in the gpu section) if set, disable that.

 

 

Radeon will not work on 775 socket (chipset) on system 10.13.

whatever options you use. The help may be in replacing graphics kexts.

[DmitryX82]

11 hours ago, mitch_de said:

Hi, i use LILU+WEG since long time with mx RX 460 (similar to RX 560). Should work.

In MB-BIOS AMD GPU should be primary.

Which port do you use for monitor? Sometimes not all ports (DVI, DP, HDMi) works out of the box, even with WEG.

First try change to other port (if you can) to verify if its an port problem and WEG works in general.

Also check if you have any DSDT /SSDT files in use wich belong to the GPU (for naming, setting ports etc.) can interfernence to WEG.

Also check if you use RADEINIT (an clover option, i think in the gpu section) if set, disable that.

 

 

Hello, please tell the model of your motherboard?

socket?

[mitch_de]

Its an newer socket  for ix-3xxx Cpu. So SLICE post about Chipset (Socket / minimum CPU type) may avoid running that AMD gpu on 775 Socket / Chipset for that type.

But i think you may get answer by google about that, because then the no go for that GPU type would  bei also for WIN / LINUX 775-socker- systems 

EDIT I started for my own interest a bit googling... nothing real found. lot people talk about PCIE Slot Version / UEFI BIOS vs Leagancy BIOS ... in case running newer gpus. But no real "valide" answer found. Maybe its not the 775 Socket / CPU itself, its perhaps missing UEFI BIOS and/or some PICE Slot Version (to old) problem which cam from Chipset  and, because of age, no UEFI BIOS.

EDIT2: If you cold boot, do you have the BIOS Bootscreen (from mainboard)? If not then i think card has no dual bios (legancy + UEFI).

EDIT3: maybe its UEFI problem, like posts here: https://www.reddit.com/r/Amd/comments/4rnslu/uefi_bios_for_rx_4xx_series_of_cards/

And it may that some vendors (Saphhire) put dual bios ons some newer AMD cards. In general non UEFI system seems to be a problem.