Jump to content
WarDoc

WhatEverGreen Support Topic

1,022 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:

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)

Im on Dell XPS 9560. Kabylake. Intel HD 630 (591b0000). I have a 4k. The bootloader gets to the point of loading graphics acceleration to load the desktop, then never loads the desktop. It's just stuck in verbose black screen. I hear when i press buttons that the desktop is loaded, but im not able to see it. I have the latest Whatevergreen 1.3.0. I use the same Clover bootloader folder to load Catalina dp1 on its own partition and it loads. So, I don't know why it will not get me to the desktop in dp2. Adding "12345678" to ig-platform-id and fake graphics id only leads to a panic and reboot. The only way i get to the desktop (without acceleration) is in safe mode (-x). Can this be worked out in the next build or does it seem like something thats not related to Whatevergreen?

Edited by nytr0

Share this post


Link to post
Share on other sites
Posted (edited)
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

Share this post


Link to post
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

Share this post


Link to post
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.

Share this post


Link to post
Share on other sites
Posted (edited)
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

Share this post


Link to post
Share on other sites
Posted (edited)
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

Share this post


Link to post
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

Share this post


Link to post
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.

Share this post


Link to post
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 :)

Share this post


Link to post
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 :)

Share this post


Link to post
Share on other sites
Posted (edited)

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

Share this post


Link to post
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

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
Share on other sites

Hi guys, I'd like to know if it's possible, with whatevergreen, to control the gpu pstates, raise the idle frequencies and under load.

Share this post


Link to post
Share on other sites
On 7/6/2019 at 1:25 AM, maxb2000 said:

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

ASRock B365M Pro4

Intel UHD 630 (no dedicated GPU)

 

iMac 19.1 SMBIOS

 

For single CFL IGPU is better to use Macmini8,1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Aldaro
      I have been running macOS Mojave on my system for 3 months and everything was working pretty well.  After taking an update for clover, my entire system got wrecked, and I cannot even boot to an installation environment anymore (which I really need to do since I am starting back at square one).  I still have the old EFI folder backed up, but I know it'll only be a matter of time before Apple introduces an update that requires me to update Clover in order to work correctly.  I have tried all the available memory fixes, but none of them seem to work.  I was previously using the original osxaptiofix; so, I gave v2, and v3 a try, but to no success.  I read somewhere on the main discussion board for clover that AptioMemoryFix was no longer going to be supported and I therefor decided to skip over it (not to mention it isn't even available in newer clover installation packages).
       
      System specs:
      Motherboard: GIGABYTE Z390 M GAMING
      CPU Intel core i5 9600k @ stock 3.7GHz
      RAM 32GB DDR4 2667MHz
      GPU AMD Radeon RX 580 with 8GB of GDDR5
      SSD Intel 660p 512GB NVME
      NIC: Intel i210 10/100/1000 as it is natively supported in macOS
       
      I have been using the iMac 19,1 SMBIOs as I built this machine to match it as close as humanly possible.  As for my UEFI settings, I did the usual:
      Disabled Windows specific features and secure boot
      Enabled XHCI hand off
      Enabled Above 4G decoding
      Disabled onboard NIC since it is made irrelevant by my intel i210
       
      --INJECT KEXTS--
      FakeSMC
      Lilu
      WhateverGreen
      AppleALC
      USBInjectAll -- WITH PATCHED SSDT in /EFI/CLOVER/ACPI/patched
      Below are images of the errors I am receiving when trying to boot the macOS Mojave installer.
       
      with original osxaptiomemoryfix

       
      osxaptiofixv2

       
      osxaptiofixv3

       
      Anyway, if somebody can help me figure out what's going on, that'd be greatly appreciated.  My ultimate goal is to get an install with minimal clover patches as to be better prepared when the winds of change from Apple come roaring.
       
      p.s: I have also attached a copy of my EFI folder
       
       
      EFI.zip
    • By kalpesh2804
      Laptop Inbuilt Wifi and Battery Indicator not working in Catalina. (HP Pavilion 15t-au 100 Laptop)
       
       
      Laptop Config:
      HP Pavilion 15t-au100 * i7-7500u 2.90Ghz * Intel HD 620 Graphic Adapter * Intel Dual Band Wireless AC-3168 * Kingston SATA3 SSD 500 GB * HP Camera
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
      Mac Downloader (thanks to ricoc90)
       
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
×