WhatEverGreen Support Topic

[viktr]

Hi!

 

Just upgraded to 10.14.5 and have a problem. I have 560 4gb with 2 displays connected via DP (1st, 5k) and hdmi (second, 4k). Everything was working fine till upgrade. DP display is "primary" and bios setup and boot log is displayed on it. Now, after boot, DP display turns off on the second boot stage, and only hdmi display is active till I turn HDMI display off. After HDMI display is off, DP display starts to work fine and I am able to turn HDMI display back on then, and use them both. Please help - how can I fix that? Tried to disable AGDC (using <00>, <00 00 00 00> and "false") - DP monitor still does not work after boot, but UI transparency has gone. Tried to explicitly define connectors priority with <010405> - nothing changed

Here's the ioreg dump with one display working (right after boot), ioreg with both displays working (after I turned HDMI monitor off then back on) and WEG log. It's larger than 10m so I cannot upload it here https://etogo.net/infiles/displays.tgz

 

Thank you

[Matgen84]

Hi

 

I try latest Whatevergreen 1.2.9 (remove NoVPAJpeg.kext) but it don't work. I don't understand why?

 

 

[Andrey1970]

6 hours ago, Matgen84 said:

Hi

 

I try latest Whatevergreen 1.2.9 (remove NoVPAJpeg.kext) but it don't work. I don't understand why?

 

 

 

Simply use IGPU for IQSV only, as on real iMac13,2 

https://applelife.ru/threads/zavod-intel-quick-sync-video.817923/

 

[warty]

Is the FAQ on GeForce at the WhateverGreen manual on Github outdated?

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.GeForce.en.md

It refers to using IntelGraphicsFixup and Shiki, but the post pinned to the top of this forum topic from a year ago says, "IntelGraphicsFixup, NvidiaGraphicsFixup, and Shiki are now officially dead and are part of WhateverGreen. Using them together is not supported and will lead to undefined behaviour."

 

Am I missing something? Or is there a better/more up-to-date usage guide somewhere else?

 

 

[vandroiy2012]

22 minutes ago, warty said:

Am I missing something? Or is there a better/more up-to-date usage guide somewhere else?

 

Thanks. Fixed.

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.GeForce.en.md

[vladie]

Have mouse lag problem with reference Vega64 + Mojave. Mouse cursor freezes for a ~0.1 second every 3 seconds. Mojave versions tried are 10.14.3 and 10.14.5 (x299, with KGP's config). If i'm using VesaGraphicsFixup instead of Whatevergreen, problem is gone - cursor runs smoothly (but VesaGraphicsFixup have another problems with 10.14.5). Is there are any chances to fix this ? Thanks.

[iCanaro]

VesaGraphicsFixup????

[Pavo]

12 minutes ago, vladie said:

Have mouse lag problem with reference Vega64 + Mojave. Mouse cursor freezes for a ~0.1 second every 3 seconds. Mojave versions tried are 10.14.3 and 10.14.5 (x299, with KGP's config). If i'm using VesaGraphicsFixup instead of Whatevergreen, problem is gone - cursor runs smoothly (but VesaGraphicsFixup have another problems with 10.14.5). Is there are any chances to fix this ? Thanks.

Only thing that VegaGraphicsFixup does is mangle the board-id that apple graphics device policy looks for, which prevents it from loading. This same effect can be achieved by WEG alone by just adding the bootarg

agdpmod=pikera

 

[vladie]

14 hours ago, Pavo said:

Only thing that VegaGraphicsFixup does is mangle the board-id that apple graphics device policy looks for, which prevents it from loading. This same effect can be achieved by WEG alone by just adding the bootarg

agdpmod=pikera

 

 

ok, but after upgrading to 10.14.5 i have a problem with VegaGraphicsFixup. Approximately one of ten boots video driver didn't start, i see hundreds of errors in log (screenshot attached). I needed VegaGraphicsFixup because i have two 5k monitors attached.

 

 

 

[viktr]

 
ok, but after upgrading to 10.14.5 i have a problem with VegaGraphicsFixup. Approximately one of ten boots video driver didn't start, i see hundreds of errors in log (screenshot attached). I needed VegaGraphicsFixup because i have two 5k monitors attached.
 
 
 

Looks like I have the similar problem - 5k monitor is not detected at boot. Did you try to use wag without any parameters and unplug monitor power after boot then plug it back again?


Sent from my iPhone using Tapatalk

[vladie]

1 hour ago, viktr said:

 

Looks like I have the similar problem - 5k monitor is not detected at boot. Did you try to use wag without any parameters and unplug monitor power after boot then plug it back again?


Sent from my iPhone using Tapatalk

 

 

my both monitors detected without a problem and works. WAG works but with mouse lagging. VegaGraphicsFixup works fine but sometimes i see TestVRAM failures at boot.

[viktr]

 
my both monitors detected without a problem and works. WAG works but with mouse lagging. VegaGraphicsFixup works fine but sometimes i see TestVRAM failures at boot.

Could you please share what monitors do you use?


Sent from my iPhone using Tapatalk

[vladie]

Just now, viktr said:

 

Could you please share what monitors do you use?


Sent from my iPhone using Tapatalk

 

 

i'm tried dell up2715k and planar ix2790, no problems with both (connection made by displayport).

[JoQ]

I got 3 monitors hooked up to my AMD R9 290 (1xDVI, 2xHDMI). And I can only get picture on the 2xHDMI monitors unless I unplug one HDMI cable, then DVI + HDMI works.

I don't need 3 monitors in Mac OS, but I use the third monitor in Windows and I don't want to keep plugging in and out it.

Is it possible to disable ports?

The card has 1xDVI, 1xDP and 2xHDMI and I want to disable 1 of the HDMI ports.

Read trough the WIKI and found this:

Quote

When and how should I use custom connectors?

In general automatic controller detection written in Apple kexts creates perfect connectors from your VBIOS. The logic of that can be found in reference.cpp. However, some GPU makers physically create different connectors but leave the VBIOS unchanged. This results in invalid connectors that are incompatible with your GPU. The proper way to fix the issues is to correct the data in VBIOS, however, just providing custom connectors can be easier.
For some GPUs (e.g. 290, 290X and probably some others) WhateverGreen incorporates automatic connector correction that can be enabled via -raddvi boot argument. For other GPUs you may specify them as a GPU device property called connectors, for example, via SSDT. You could pass your connectors in either 24-byte or 16-byte format, they will be automatically adapted to the running system. If you need to provide more or less connectors than it is detected automatically, you are to specify connector-count property as well. Please note that automatically detected connectors appear in the debug log to give you a good start.

Is this something I can use?

[gothickitty93]

Anyone know where I can get a working 1.3.0 kext? I compiled it myself, but i cant load it. I get "Failed to load /Library/Extensions/WhateverGreen.kext - (libkern/kext) link error."

[eSaF]

23 minutes ago, gothickitty93 said:

Anyone know where I can get a working 1.3.0 kext? I compiled it myself, but i cant load it. I get "Failed to load /Library/Extensions/WhateverGreen.kext - (libkern/kext) link error."

Here you are.

Hackintool_Kexts.zip

[gothickitty93]

ok i must be missing somthing here. I tried this kext, and even was able to successfully load my own WG+Lilu. I'm on a Mac mini  2012 running 10.14.5 trying to do the pixel clock patch to drive my 4k display at 30hz. I've successfully used these kexts with Lilu Helper on 10.14.4 and lower, but it's not working now. 

[vladie]

I've migrated to WhateverGreen (x299 + Vega64), but i still have random TestVRAM errors at boot (near one time at a week). I think mac os powerplay profile is not fully compatible with reference Vega64 card. Is anyone know how to migrate powerplay profile from windows 10 to mac os ? Thanks

[Matgen84]

HI

 

I can't use WEG 1.3.0 under Catalina Beta. Ever with -wegbeta or -lilubetaall. (i7 9700K config). There is a solution?

 

Please

 

EDIT: this afternoon, 1.3.0 won't compile (Xcode 10.2 under Mojave): Kernel version error "Catalina"

Edited June 14, 2019 by Matgen84

[vandroiy2012]

4 hours ago, Matgen84 said:

HI

 

I can't use WEG 1.3.0 under Catalina Beta. Ever with -wegbeta or -lilubetaall. (i7 9700K config). There is a solution?

 

Please

 

EDIT: this afternoon, 1.3.0 won't compile (Xcode 10.2 under Mojave): Kernel version error "Catalina"

Replace with newest (build from sources) debug Lilu.kext in WEG folder, then build WEG.  

[Matgen84]

10 hours ago, vandroiy2012 said:

Replace with newest (build from sources) debug Lilu.kext in WEG folder, then build WEG.  

 

Thanks 

 

Always kexts panic instead of Desktop. I've to block this kext to launch correctly

 

Sorry for my bad english

Edited June 15, 2019 by Matgen84

[vandroiy2012]

The panic report is much more earlier. I can't see what is the problem. 

 

You should build WEG with latest Debug Lilu.kext in WEG folder sources. 

[JoQ]

I use WhatEverGreen with my AMD R9 290. And it works great in Mac OS. But I have one issue.

If I put my computer to sleep, and wake it up with Wake On LAN. The display will still be off (no signal) until I press the mouse button.

This does not happen if I put it to sleep and wake it up with the mouse/keyboard (no Wake On LAN).

 

Is this related to WhatEverGreen?

[Matgen84]

5 hours ago, vandroiy2012 said:

The panic report is much more earlier. I can't see what is the problem. 

 

You should build WEG with latest Debug Lilu.kext in WEG folder sources. 

 

Hi

 

Need help please!

 

I've issue with latest WEG 1.3.0 on my config i7 9700K - RX 580. See image in attachment

 

Catalina start only if I block WEG with Clover

 

Any solutions

[newsguytor]

How can I disable DP audio?? It so damn annoying, it always switches audio output automatically to the horrible speakers built in the monitor each time it turns on.