WhatEverGreen Support Topic

[DmitryX82]

6 hours ago, mitch_de said:

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 я начал ради собственного интереса немного погуглил... ничего настоящего не найдено. много людей говорят о PCIe Слот версии / UEFI BIOS vs Leagancy BIOS ... в случае запуска новых GPU. Но настоящий "Валид" ответа не нашел. Возможно, это не само гнездо 775 / CPU, его, возможно, отсутствует UEFI BIOS и / или какая-то версия PICE Slot (к старой) проблеме, которая cam от чипсета и, из-за возраста, нет 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.

I just wanted to attract the attention of the creators of WhatEverGreen kext,   
because I'm not alone, but all the owners of motherboards on socket 775 are watching the black screen

in High Sierra/Mojave Mac os x 13-14.

the problem is driver \ kext. 
NVIDIA work good on the same hardware.

Is it possible to contact the creators?

Edited September 3, 2018 by DmitryX82

[LockDown]

The creator monitor this thread

[Slice]

I think the problem may be in bus speed which is 100MHz on Sandy and up but 200 and more on 775 socket chipset. High Sierra AMD graphics driver don't see this.

[DmitryX82]

11 hours ago, ellaosx said:

The creator monitor this thread

I really hope so, and to solve the problem.

[maleorderbride]

Is there a boot-arg for WEG to set the AMD framebuffer? I can inject it via SSDT, but it seems like it would be an obvious nice to have for WEG.

 

 

[Pavo]

10 minutes ago, maleorderbride said:

Is there a boot-arg for WEG to set the AMD framebuffer? I can inject it via SSDT, but it seems like it would be an obvious nice to have for WEG.

 

 

The main purpose of using WEG is not to inject a framebuffer.

[maleorderbride]

29 minutes ago, Pavo said:

The main purpose of using WEG is not to inject a framebuffer.

OK, but FCPX and QT require an AMD framebuffer in order to export certain codecs.

 

With WEG in place you get a system-wide freeze instead requiring me to add the framebuffer via SSDT instead.

[Pavo]

1 minute ago, maleorderbride said:

OK, but FCPX and QT require an AMD framebuffer in order to export certain codecs.

 

With WEG in place you get a system-wide freeze instead requiring me to add the framebuffer via SSDT instead.

Well I am not sure about those but from looking at your system specs in your profile, I am not seeing a AMD GPU. Exporting codecs should not be effected by not using a frame buffer. That would limit the application to only support certain GPUs that have that frame buffer.

[maleorderbride]

This is on that X299 ASRock system, but I put in an RX 580 for testing since FCP X tends to work better with AMD cards. While OpenCL does work better with AMD, obviously this 264/265 encoding is unfortunate. 

 

The issue definitely exists. You can find other threads if you google for H264 or H265. Everyone solves it by injecting a FB, which again, makes it seem like an obvious thing to allow with WEG.

 

On a real Mac system the AMD GPU is almost always paired with an Intel processor that has an IGPU. 

[Pavo]

57 minutes ago, maleorderbride said:

This is on that X299 ASRock system, but I put in an RX 580 for testing since FCP X tends to work better with AMD cards. While OpenCL does work better with AMD, obviously this 264/265 encoding is unfortunate. 

 

The issue definitely exists. You can find other threads if you google for H264 or H265. Everyone solves it by injecting a FB, which again, makes it seem like an obvious thing to allow with WEG.

 

On a real Mac system the AMD GPU is almost always paired with an Intel processor that has an IGPU. 

On my real Mac (MacPro 5,1 no iGPU because the CPUs are Xeons) with a RX 580 has working hardware encoding functioning perfectly fine without a frame buffer. Also my hack has Xeon CPUs again no iGPU and using Vega 64 without a frame buffer and hardware encoding is working. I use latest Lilu and WEG as always.

[maleorderbride]

14 minutes ago, Pavo said:

On my real Mac (MacPro 5,1 no iGPU because the CPUs are Xeons) with a RX 580 has working hardware encoding functioning perfectly fine without a frame buffer. Also my hack has Xeon CPUs again no iGPU and using Vega 64 without a frame buffer and hardware encoding is working. I use latest Lilu and WEG as always.

 

Hmmm..perhaps SMBIOS related as well. I'll mess around with it, but since adding a framebuffer fixes the issue...

[yamahahornist]

Is there a way to keep Whatevergreen from changing PEGP to GFX0? I am trying to use SSDT patches but they wont apply because of the name change and I tried changing my SSDT patches to the GFX0 path but it doesn;t work. If I don't use whatevergreen kext then my SSDT will patch... rip..

[Pavo]

3 minutes ago, yamahahornist said:

Is there a way to keep Whatevergreen from changing PEGP to GFX0? I am trying to use SSDT patches but they wont apply because of the name change and I tried changing my SSDT patches to the GFX0 path but it doesn;t work. If I don't use whatevergreen kext then my SSDT will patch... rip..

Use Clover Rename Devices feature to rename PEGP to GFX0, then have your SSDT patch for GFX0. But if you are doing patching with a SSDT, there really is no need to use WEG.

[yamahahornist]

4 minutes ago, Pavo said:

Use Clover Rename Devices feature to rename PEGP to GFX0, then have your SSDT patch for GFX0. But if you are doing patching with a SSDT, there really is no need to use WEG.

Thanks for the reply; the issue I am having is whatevergreen is messing up my laptop displays connector and connector flag. My laptop uses eDP and whatevergreen is injecting LVDS which is causing EDID issues (color banding). If I don't use whatevergreen I can get it working with the SSDT patches, but I have to inject a framebuffer and modify conenctors.. then my laptop screen isn't seen as internal.. and my HDMI ou tport has low bandwidth. 

 

If I use whatevergreen, it changes PEPG to GFX0, and even if I use a SSDT patch to rename PEGP to GFX0 in clover my SSDT patches don't work... :/ haha 

[SquallATF]

7 hours ago, yamahahornist said:

Thanks for the reply; the issue I am having is whatevergreen is messing up my laptop displays connector and connector flag. My laptop uses eDP and whatevergreen is injecting LVDS which is causing EDID issues (color banding). If I don't use whatevergreen I can get it working with the SSDT patches, but I have to inject a framebuffer and modify conenctors.. then my laptop screen isn't seen as internal.. and my HDMI ou tport has low bandwidth. 

 

If I use whatevergreen, it changes PEPG to GFX0, and even if I use a SSDT patch to rename PEGP to GFX0 in clover my SSDT patches don't work... :/ haha 

if enable device properties the clover edid inject will not work, I found a solution,

add 'AAPL00,override-no-connect' with patched edid data to device properties like clover done.

Edited September 5, 2018 by SquallATF

[yamahahornist]

Hmm.... So I have been spending some with different configurations.. and one thing I am working through is (side note: I have a mobile amd gpu);

My laptops display doesn't inject EDID correctly so I have to manually inject it; but injection of EDID will only work if I am Injecting an AMD framebuffer (buri in my case). Also EDID injecting doesn't seem to work if I use LVDS on @0; my laptop use eDP and the best working combo I have found is 04000000 14020000 which is dual link DVI; why that works.. I don't know haha.

 

What I am trying to do is get brightness adjustment and laptop lid close to work; with native whatever green it works, but EDID won't inject... unless I inject ATI with a framebuffer... weird...

[gujiangjiang]

I tested on macOS10.14 (18A389) and the 2 patches need to be updated and fixed.

• CoreDisplay 4K Patch
• DVMT Patch

 

On macOS 10.13 we can use -cdfon to use CoreDisplay 4K Patch but when I update to macOS10.14 (18A389) and the patch failed  and I must use FakeID=0x12345678 to boot into macOS.

I think the CDF Patch code don't work with the latest macOS 10.14 and we need to update the patch code because when I use the original CoreDisplayFixup and still can't use.

Now both WEG and CDF are all failed in macOS 10.14(18A389) so I hope to fix this.

 

And the DVMT patch since 10.13 and 10.14 are all with no use and I must use the original DVMT kext to patch DVMT.

Edited September 13, 2018 by gujiangjiang

[apfelnico]

I have an X299 system, two VEGA64 with four framebuffers each. Everything works as far as correct. But one of the two graphics cards uses 6 instead of 4 frambuffers. And it changes. Sometimes it's GFX0, sometimes it's GFX1. Both graphics cards are identical. I can define four framebuffers for each graphics card via SSDT, then it works:

                    "@0,name", 
                    Buffer (0x0D)
                    {
                        "ATY,Kamarang"
                    }, 
...

What is "WhatEverGreen" doing wrong?

[Einknall]

On 8/16/2018 at 2:51 PM, headkaze said:

 

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.

 

Can anyone explain me how to enable-hdmi20 IGPU in devices/properties inside clover configurator? Simply adding bootleg -cdfon does not do the trick for my GA-Z370N-Wifi i3 8100 setup.

[headkaze]

On 9/13/2018 at 1:00 AM, gujiangjiang said:

Now both WEG and CDF are all failed in macOS 10.14(18A389) so I hope to fix this.

I have 4K patch working fine on macOS 10.14 (18A389) using enable-hdmi20 IGPU in devices/properties.

 

34 minutes ago, Einknall said:

Can anyone explain me how to enable-hdmi20 IGPU in devices/properties inside clover configurator? Simply adding bootleg -cdfon does not do the trick for my GA-Z370N-Wifi i3 8100 setup.

You can always read the guide or use Intel FB-Patcher

Edited September 15, 2018 by headkaze

[gujiangjiang]

Just now, headkaze said:

I have 4K patch working fine on macOS 10.14 (18A389) using enable-hdmi20 IGPU in devices/properties.

 

You can always read the guide or use [url=https://www.insanelymac.com/forum/topic/335018-intel-fb-patcher-v135/]Intel FB-Patcher[/url]

 

I have tried -cdfon and add enable-hdmi20 IGPU in properties but still have no use.

 

On 10.13 i just use -cdfon to make my 4k work but on 10.14 it donesnt work anymore.

 

Here are the topic:

https://github.com/Floris497/mac-pixel-clock-patch-V2/issues/280

 

And now i am waiting for a new patch for CoreDisplay on 10.14 with 4k support.

[gujiangjiang]

39 minutes ago, headkaze said:

I have 4K patch working fine on macOS 10.14 (18A389) using enable-hdmi20 IGPU in devices/properties.

 

You can always read the guide or use Intel FB-Patcher

 

@vit9696

The new CoreDisplay patch come out by @Floris497 and i test it works well witn 4K 60hz on 10.14 (18A389).

I want to commit this new patch to WEG on github.

Thanks.

CoreDisplay-patcher.command.zip

Edited September 15, 2018 by gujiangjiang

[headkaze]

44 minutes ago, gujiangjiang said:

on 10.14 it donesnt work anymore

 

Not sure why? It works for me.

[gujiangjiang]

6 minutes ago, headkaze said:

 

Not sure why? It works for me.

 

I have tested one day and I can sure the old patch is not comptiable for 10.14 and now the new patch comes out so I want to merge the new patch to the github.

 

I am using XPS 15 9550 with 4K display and Intel HD530 Graphic Card and I don't use any resolution tools.

 

I am using -cdfon and using IntelFBTools to add enable-hdmi20 and with no use so I can confirm it not work and some people have same problem with me when updated to 10.14 and now the new patch comes out and the old patch with no use but the new patch works perfectly and these two patch are different.

 

Your can workaround the cdf code you can see it just support 10.13.x patch code and with no 10.14.x patch code and 10.14 the CoreDisplay was rewritten by swift and the patch changed so I don't know why old patch still can use in your laptop.

 

Thanks for your work in this problem.

Edited September 15, 2018 by gujiangjiang

[headkaze]

CoreDisplay-patcher.command and WEG cdf patches don't appear to work the same.

 

Both patch /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay

 

CoreDisplay-patcher.command:

Find: 4D 8B 36 4D 85 F6 0F 85 29 FD FF FF 31 DB EB 47
Replace: 4D 8B 36 48 85 C0 0F 84 29 FD FF FF 31 DB EB 47

WhateverGreen cdf:

Find: BB 01 00 00 00 A8 01 0F 85
Replace: 31 DB 90 90 90 90 90 90 E9

 

The WEG cdf patch still appears to be valid in macOS (18A389)

 

Maybe you needed to reboot a few times? Sometimes I have to do that after an update for 4K to work again.

Edited September 15, 2018 by headkaze