Jump to content

WhatEverGreen Support Topic


MattsCreative
1,504 posts in this topic

Recommended Posts

On 6/15/2019 at 3:27 PM, Matgen84 said:

 

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

whatevergreen panic.jpg

 

Today, the new WEG 1.3.0 solve this issue. Thanks for developers :thumbsup_anim:

Link to comment
Share on other sites

On 6/17/2019 at 7:27 AM, Matgen84 said:

 

Today, the new WEG 1.3.0 solve this issue. Thanks for developers :thumbsup_anim:

Can you post the compiled new WEG? Or you can compile yourself? If it's download-and-compile-done process I would be more happy do it myself.

 

Update:

It seems quite easy to compile those kexts. Here it is if anyone needs

Lilu+WEG.zip

Edited by lisai9093
  • Like 1
Link to comment
Share on other sites

40 minutes ago, lisai9093 said:

Can you post the compiled new WEG? Or you can compile yourself? If it's download-and-compile-done process I would be more happy do it myself.

 

New WEG in attachement

 

If you want to compile by yourself:

 

  • Download Lilu master from Acidanthera in Github
  • Compile latest Lilu.debug (Xcode)
  • Download Whatevergreen master from Acidanthera in Github
  • Put Lilu.debug in your  Whatevergreen folder
  • Compile WEG (before edit scheme to release) in Xcode

 

Sorry about my bad English

1.3.0 (RELEASE).zip

  • Like 1
Link to comment
Share on other sites

10 minutes ago, Matgen84 said:

 

New WEG in attachement

 

If you want to compile by yourself:

 

  • Download Lilu master from Acidanthera in Github
  • Compile latest Lilu.debug (Xcode)
  • Download Whatevergreen master from Acidanthera in Github
  • Put Lilu.debug in your  Whatevergreen folder
  • Compile WEG (before edit scheme to release) in Xcode

 

Sorry about my bad English

1.3.0 (RELEASE).zip

Yes that what I found when compiled it. Thanks for the detail.

  • Like 1
Link to comment
Share on other sites

On 6/17/2019 at 9:27 PM, Matgen84 said:

 

Today, the new WEG 1.3.0 solve this issue. Thanks for developers :thumbsup_anim:

You don't need -lilubetaall as boot argument,, Lilu.kext and all plugin are compatible now with Catalina DP2. Just reCompiled all Lilu.kex and plugin :)

Edited by Andres ZeroCross
  • Like 1
Link to comment
Share on other sites

10 minutes ago, Andres ZeroCross said:

You don't need -lilubetaall as boot argument,, Lilu.kext and all plugin are compatible now with Catalina DP2. Just reCompiled all Lilu.kex and plugin :)

 

Yes, you're right. All my kexts are up to date :) The first WEG 1.3.0 don't work on my config i7 9700K. The developer add new commit for 1.3.0, 5 days ago. With this new WEG 1.3.0, there is no more panic in my system.

 

Take a look

https://github.com/acidanthera/WhateverGreen/commit/e5e78bf07dff483fd4bc78d6355a65d08a8960ee

Edited by Matgen84
  • Like 1
Link to comment
Share on other sites

1 minute ago, Matgen84 said:

 

Yes, you're right :) The first WEG 1.3.0 don't work on my config i7 9700K. The developer add new commit for 1.3.0, 5 days ago. With this new WEG 1.3.0, there is no more panic in my system.

 

Take a look

https://github.com/acidanthera/WhateverGreen/commit/e5e78bf07dff483fd4bc78d6355a65d08a8960ee

 

I always check commit from several github kext everyday :) And make a new compiled kext if there is new change

image.thumb.png.58207524c3171cb5683719e79205bdac.png

  • Like 2
Link to comment
Share on other sites

2 minutes ago, Andres ZeroCross said:

 

I always check commit from several github kext everyday :) And make a new compiled kext if there is new change

image.thumb.png.58207524c3171cb5683719e79205bdac.png

 

I use several tools. Can you post your script, please.

Link to comment
Share on other sites

Just now, Matgen84 said:

 

I use several tools. Can you post your script, please.


First make git clone many github source into one directory, eg "ManualBuild"

After that open your terminal and "cd ManualBuild" press enter, then type "find . -type d -depth 1 -exec git --git-dir={}/.git --work-tree=$PWD/{} pull origin master \;" and press enter,, automatic check now :)

  • Thanks 1
Link to comment
Share on other sites

1 minute ago, Andres ZeroCross said:


First make git clone many github source into one directory, eg "ManualBuild"

After that open your terminal and "cd ManualBuild" press enter, then type "find . -type d -depth 1 -exec git --git-dir={}/.git --work-tree=$PWD/{} pull origin master \;" and press enter,, automatic check now :)

 

Thanks a lot :)

  • Like 1
Link to comment
Share on other sites

Hello, I have an issue which I wonder if could be fixable via WhateverGreen, or at least maybe an idea of what's going on.

- My system is a Z390, with an Nvidia card. Both iGPU and NVIDIA are enabled via BIOS. Primary card set is iGPU.

- I have a displayport switch, that helps me connect the monitor to one of the GPUs.

- With iGPU selected via the switch, after rebooting or shutting down from Windows, when system reboots or turns on, POST appears normally via iGPU. So far so good.

- For OSX, I disabled NVidia (using WhateverGreen, or DSDT - I tried both methods), as no driver is available. After rebooting from OSX (booted with iGPU), system reboots successfuly (I hear the startup "beep"), but no POST appears via iGPU. This will persist even if I turn off the system and turn it back on. I must switch to nVIDIA to see POST.

However this happens only after OSX was loaded. Any idea what's going on?

Edited by Pene
Link to comment
Share on other sites

Hi

 

If I disable my Optimus graphics card with disable-external-gpu property, I don't have any video output through my usb c displayport (connector-type in ioreg seems correct: 00040000).

With Nvidia GPU enabled, I see the external monitor at display @1 under IGPU@2, so the port is wired to the integrated GPU.

The only difference between the two configurations is the one line used to disable the DGPU.

I attach ioreg + log with both DGPU on and off along with my config.plist and kext folder.

Laptop specs:

Dell G3 8750H with Intel UHD 630 + GTX 1060 MaxQ

Let me know if you need more info.

info.zip

Link to comment
Share on other sites

Hi! I have a lenovo kaby lake laptop. Framebuffer set to 32mb in bios and can't be set higher. Bios is locked and rewrite protected. Framebuffer memory is also set to 32mb with whatevergreen. Does minstolensize patch still work since that was the (only) way to enable 4k30 output before whatevergreen or is there an alternative way to enable 4k output? -cdfon boot flag doesn't do anything and graphics memory is already set to 2048mb.

Link to comment
Share on other sites

On 6/22/2019 at 5:04 PM, Matgen84 said:

 

Yes, you're right. All my kexts are up to date :) The first WEG 1.3.0 don't work on my config i7 9700K. The developer add new commit for 1.3.0, 5 days ago. With this new WEG 1.3.0, there is no more panic in my system.

 

Take a look

https://github.com/acidanthera/WhateverGreen/commit/e5e78bf07dff483fd4bc78d6355a65d08a8960ee

 

I am using latest WEG and I am still getting panic when I am using primary as an IGPU. Without WEG after finished the verbose monitor goes to sleep.

Link to comment
Share on other sites

6 hours ago, telepati said:

 

I am using latest WEG and I am still getting panic when I am using primary as an IGPU. Without WEG after finished the verbose monitor goes to sleep.

 

I use IGPU primary despite of my RX580 connected to my monitor: now without issues (panic). Can you post screenshot so WEG developers answers to you.

Link to comment
Share on other sites

9 hours ago, Matgen84 said:

 

I use IGPU primary despite of my RX580 connected to my monitor: now without issues (panic). Can you post screenshot so WEG developers answers to you.

 

Which settings are you using for IGPU? Could you please share with me? I tried without WEG and monitor goes to sleep after finishing the verbose.

Link to comment
Share on other sites

1 minute ago, telepati said:

 

Which settings are you using for IGPU? Could you please share with me? I tried without WEG and monitor goes to sleep after finishing the verbose.

 

Sorry, I don't use IGPU at all. I try IGPU connected to my monitor, with and without WEG. I've a panic. I don't understand why.

  • Thanks 1
Link to comment
Share on other sites

Hi,

 

I have a strange pink flash on different sections of the website when I scroll. It also happens on random websites like Apple documentation website.

 

Config:

 

Intel Core i5 9600K (Device ID: 3e98)

ASRock B365M Pro4

Intel UHD 630 (no dedicated GPU)

 

iMac 19.1 SMBIOS, ig-platform-id: <07009b3e> (injected via Device-> Properties), clover injection off, all renaming in DSDT are turned off as per instructions from the Github page.

Link to comment
Share on other sites

for those who have problems with ATIController::TestVRAM crashes during boot, i've created a patch for clover for solving this problem. second patch removes magenta-colored lines which appears at screen during video driver startup.

 

	    <dict>
		<key>Comment</key>
		<string>ATIController TestVRAM boot failure patch</string>
		<key>Disabled</key>
		<false/>
		<key>Find</key>
		<data>
		uapVqlU7DJA=
		</data>
		<key>InfoPlistPatch</key>
		<false/>
		<key>Name</key>
		<string>AMDSupport</string>
		<key>Replace</key>
		<data>
		uapVqlU5yZA=
		</data>
	    </dict>
	    <dict>
		<key>Comment</key>
		<string>ATIController TestVRAM magenta-colored lines patch</string>
		<key>Disabled</key>
		<false/>
		<key>Find</key>
		<data>
		xwSxqlWqVQ==
		</data>
		<key>InfoPlistPatch</key>
		<false/>
		<key>Name</key>
		<string>AMDSupport</string>
		<key>Replace</key>
		<data>
		kJCQkJCQkA==
		</data>
	    </dict>
		

Insert this is KextsToPatch section.

PS: patch is beta version, tested only with 10.14.5 + Vega64, but must be compatible with any AMD card.

 

TestVRAM fills memory with 0xaa55aa55 bytes (it's magenta pixels you see at screen), and it's tries to test too much of address space, writing this bytes to framebuffer memory. If you have verbose mode enabled (as i have), there are possibility that framebuffer will scroll during this test, and TestVRAM will write 0xaa55aa55, but read 0x00000000 (because magenta-colored pixels are scrolled up).

 

Edited by vladie
  • Like 5
Link to comment
Share on other sites

hi. latest WEG is not working framebuffer patch. very strange. i can't disable port and patch hdmi(00 08 00 00)

나의 SM-N960N 의 Tapatalk에서 보냄
 

here is proved pic

56430869_2019-07-1810_57_27.thumb.png.f66030599842a24ff9697a047a1fb68d.png

1151651732_2019-07-1810_58_56.thumb.png.650353d62c8383f42bda57eefbe6c307.png

 

previous lilu 1.3.7 + WEG 1.3.0 are no problem.

 

lastest other kexts source are no problem. now only WEG happens this issue.

Edited by Sherlocks
Link to comment
Share on other sites

37 minutes ago, Sherlocks said:

hi. latest WEG is not working framebuffer patch. very strange. i can't disable port and patch hdmi(00 08 00 00)

나의 SM-N960N 의 Tapatalk에서 보냄
 

here is proved pic

56430869_2019-07-1810_57_27.thumb.png.f66030599842a24ff9697a047a1fb68d.png

1151651732_2019-07-1810_58_56.thumb.png.650353d62c8383f42bda57eefbe6c307.png

 

previous lilu 1.3.7 + WEG 1.3.0 are no problem.

 

lastest other kexts source are no problem. now only WEG happens this issue.

 

WEG 1.3.1 no problem with framebuffer patch.

Link to comment
Share on other sites

×
×
  • Create New...