Jump to content
KGP-iMacPro

iMac Pro X299 - live the future new with macOS 10.14 Mojave [Successful Build/Successful Guide]

142 posts in this topic

Recommended Posts

17 hours ago, PunkNugget said:

You got it. I was wondering where is "C.7)?" I couldn't find here. All I could find was C.5) then it went straight to C.9). Maybe I'm looking at the wrong section. :rofl:

 

Sorry, my bad... I should have referred to C.4!... :wink_anim: 

Share this post


Link to post
Share on other sites
Advertisement
14 hours ago, KGP-iMacPro said:

 

Sorry, my bad... I should have referred to C.4!... :wink_anim: 

Thank you. I read through this and noticed that I have to do a clean install. Do I have to do a clean install or do I start on D.6) to nstall this over my existing OS (like I did on the last upgrade)? Let me know, thanks again.

Share this post


Link to post
Share on other sites
7 hours ago, PunkNugget said:

Thank you. I read through this and noticed that I have to do a clean install. Do I have to do a clean install or do I start on D.6) to nstall this over my existing OS (like I did on the last upgrade)? Let me know, thanks again.

 

concerning 10.14, I would rather recommend to perform a clean install..  

Share this post


Link to post
Share on other sites
On 7/11/2018 at 1:33 PM, KGP-iMacPro said:

 

concerning 10.14, I would rather recommend to perform a clean install..  

Really? Wow! I have so many programs to have to reinstall if I go that route. You sure that I can't install this over my existing OS (10.13.2)? Let me know what you can. By the way, I know you won't be able to answer this until the July 23rd. I'll wait to hear back from you then. :)

Share this post


Link to post
Share on other sites
2 hours ago, PunkNugget said:

Really? Wow! I have so many programs to have to reinstall if I go that route. You sure that I can't install this over my existing OS (10.13.2)? Let me know what you can. By the way, I know you won't be able to answer this until the July 23rd. I'll wait to hear back from you then. :)

 

Well you can also just do the update.. but are you sure that all of these programs are already  compatible with 10.14? 

Share this post


Link to post
Share on other sites
On 7/19/2018 at 2:23 AM, KGP-iMacPro said:

 

Well you can also just do the update.. but are you sure that all of these programs are already  compatible with 10.14? 

I'm not sure, I usually don't ever worry about that as I've never had that issue. I typically use all the Adobe and Microsoft apps and they've always worked with updates.

 

Aside from that I had a question that I emailed you, but can also ask here...

 

I know you mentioned to update the bios to 140 on the X299 board. Will 10.1 3.2 still work under the newer bios update? I just want to find out before I update it. Part of the reason why am asking is because I'm building a backup system and that new set up is going to be:

Asus Prime X299-Deluxe Mobo
Trident 32GB 3200MHz RAM
AMD Pro Duo 32GB (Polaris) GPU
i9-7960X CPU
EVGA T2 1200W PSU 

Again, it’s very similar to my other set up, with the exception that I’m currently using a 1600 W power supply, 64 gigs more RAM, and an i9-7980XE CPU. So all I should have to do is pull out one of my backup hard drives and attach it to that system after I set the bios the same exact way that I have my current bios set up and it should work. That’s reason why I want to find out if I should update the bios? I look forward to your reply here very soon.
 
Lastly, I just purchased a AMD Radeon Pro Duo 32GB (Polaris) GPU. I'm hoping it performs better than the AMD Radeon Vega Frontier 16GB GPU. I have two links that give you all the specs. How do you think it will perform?
 
 
The only issue that I possibly see is that the Vega has a Memory Bus of: 2048 bit, While the Pro Duo has a Memory Bus of: 512 bit. Do you know anything about that?

Share this post


Link to post
Share on other sites
2 hours ago, PunkNugget said:

I'm not sure, I usually don't ever worry about that as I've never had that issue. I typically use all the Adobe and Microsoft apps and they've always worked with updates.

 

Aside from that I had a question that I emailed you, but can also ask here...

 

I know you mentioned to update the bios to 140 on the X299 board. Will 10.1 3.2 still work under the newer bios update? I just want to find out before I update it. Part of the reason why am asking is because I'm building a backup system and that new set up is going to be:

Asus Prime X299-Deluxe Mobo
Trident 32GB 3200MHz RAM
AMD Pro Duo 32GB (Polaris) GPU
i9-7960X CPU
EVGA T2 1200W PSU 

Again, it’s very similar to my other set up, with the exception that I’m currently using a 1600 W power supply, 64 gigs more RAM, and an i9-7980XE CPU. So all I should have to do is pull out one of my backup hard drives and attach it to that system after I set the bios the same exact way that I have my current bios set up and it should work. That’s reason why I want to find out if I should update the bios? I look forward to your reply here very soon.
 
Lastly, I just purchased a AMD Radeon Pro Duo 32GB (Polaris) GPU. I'm hoping it performs better than the AMD Radeon Vega Frontier 16GB GPU. I have two links that give you all the specs. How do you think it will perform?
 
 
The only issue that I possibly see is that the Vega has a Memory Bus of: 2048 bit, While the Pro Duo has a Memory Bus of: 512 bit. Do you know anything about that?

 

To answer your question concerning the 1401 BIOS update I need to know whether or not you are currently using patched BIOS 1301. 

 

The Radeon Pro Duo Polaris looks promising.. However one needs to ensure native OS support and a memory bus of 512 bit looks like a bottle neck though.. 

Share this post


Link to post
Share on other sites
15 hours ago, KGP-iMacPro said:

 

To answer your question concerning the 1401 BIOS update I need to know whether or not you are currently using patched BIOS 1301. 

 

The Radeon Pro Duo Polaris looks promising.. However one needs to ensure native OS support and a memory bus of 512 bit looks like a bottle neck though.. 

I couldn't find the BIOS Version until I finally looked at the bottom of the screen:

 

Version 2.17.1246

 

So it looks like (according to the Asus Tech Support person), I'm using: 1246. if that's the case, am I safe to update to 1301 or even 1401? Remember I'm using Mac OS X 10.13.2.

 

Now about the GPUs, I did think about that and also thought about the Memory Bus limit on the Pro Duo card (512 bit). Hopefully that won't be a hinderance. If it is, I'll just sell it for what I paid for it and just stick to the Vega Frontier cards. I look forward to your reply on the BIOS stuff. Thanks... :)

Share this post


Link to post
Share on other sites
On 7/26/2018 at 1:26 AM, PunkNugget said:

I couldn't find the BIOS Version until I finally looked at the bottom of the screen:

 

Version 2.17.1246

 

So it looks like (according to the Asus Tech Support person), I'm using: 1246. if that's the case, am I safe to update to 1301 or even 1401? Remember I'm using Mac OS X 10.13.2.

 

Now about the GPUs, I did think about that and also thought about the Memory Bus limit on the Pro Duo card (512 bit). Hopefully that won't be a hinderance. If it is, I'll just sell it for what I paid for it and just stick to the Vega Frontier cards. I look forward to your reply on the BIOS stuff. Thanks... :)

 

This is not the BIOS version.. The latter you find in the upper left half of the BIOS screen.. 

Share this post


Link to post
Share on other sites
1 hour ago, KGP-iMacPro said:

 

This is not the BIOS version.. The latter you find in the upper left half of the BIOS screen.. 

Alright I'll check, but do you know the amazing thing is about this? I got this info from the tech guys at Asus directly. How sad is that? That's really jacked up! In any case, the current Bios Version that I'm using is: 0802

 

I even told André (the Tech Support person at Asus) and he said that was not it. I knew I was right. Anyway, will it be safe for me to update my Bios to 1301 or 1401? Let me know what you can, thank you.

Share this post


Link to post
Share on other sites
5 hours ago, PunkNugget said:

Alright I'll check, but do you know the amazing thing is about this? I got this info from the tech guys at Asus directly. How sad is that? That's really jacked up! In any case, the current Bios Version that I'm using is: 0802

 

I even told André (the Tech Support person at Asus) and he said that was not it. I knew I was right. Anyway, will it be safe for me to update my Bios to 1301 or 1401? Let me know what you can, thank you.

 

I see.. really ancient and totally outdated BIOS version..  and I guess the BIOS is unpatched?

 

Once you update the BIOS you have to set all BIOS settings from scratch.. You know that, right?

 

For Mojave you will need my recent EFI-Folder where you have to add TSCAdjustRest.kext adopted for your CPU. Else you will also have to add recent versions of Lilu and AppleALC.. 

 

Most difficult problem for you might be the correct implementation of my system SSDT, which however is not strictly mandatory... 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
8 hours ago, KGP-iMacPro said:

 

I see.. really ancient and totally outdated BIOS version..  and I guess the BIOS is unpatched?

Now that I don't know much about that; weather it's patched or unpatched. Is that going to be an issue?

 

Once you update the BIOS you have to set all BIOS settings from scratch.. You know that, right?

Yes, I know that I'll have to reset all the BIOS back to their custom settings. I'll have to keep everything the same correct? Or are their any other changes within the BIOS that I need to be aware of?

 

For Mojave you will need my recent EFI-Folder where you have to add TSCAdjustRest.kext adopted for your CPU. Else you will also have to add recent versions of Lilu and AppleALC.. 

Will this new TSCAdjustRest.kext file work with i9-7980-XE as well as the i9-7960X CPU? I will also follow your instructions on downloading the Lilu and AppleALC files as well.

 

Most difficult problem for you might be the correct implementation of my system SSDT, which however is not strictly mandatory... 

When it comes to the correct implementation of my system SSDT, I don't know how to do that. So I hope that's going to become an issue.

 

Lastly, for some reason, when I shut down my system and took out my NVMe 960 PRO M.2 SSD and put it away (when I went on vacation), I came back and put it back in and now my Mobo doesn't even "see" it in the system at all. I can only use my regular (backup) SSD. Is there are any reason why this is happening?

 

By the way, I just sent you an email. Please check it and let me know your thoughts. Thanks... B)

 

Share this post


Link to post
Share on other sites

well I stuck at the end of "End RandomSeed" 

dunno what wrong, I think I have been followed step by step the instruction

any suggestion?

thank you

Share this post


Link to post
Share on other sites
8 minutes ago, fireedo said:

well I stuck at the end of "End RandomSeed" 

dunno what wrong, I think I have been followed step by step the instruction

any suggestion?

thank you

 

Reflash mainboard BIOS...

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
49 minutes ago, KGP-iMacPro said:

 

Reflash mainboard BIOS...

thank you for your fast reply, ok I have flashed BIOS to 1503 but still stuck at End RandomSeed

Share this post


Link to post
Share on other sites
15 minutes ago, fireedo said:

thank you for your fast reply, ok I have flashed BIOS to 1503 but still stuck at End RandomSeed

 

Upload a screenshot please! Did you adopt and add TSCAdjustReset.kext? 

Share this post


Link to post
Share on other sites
3 hours ago, KGP-iMacPro said:

 

Upload a screenshot please! Did you adopt and add TSCAdjustReset.kext? 

I have reconfigured BIOS setting after flashing to the 1503 BIOS version

and I also put and use TSCAdjustReset.kext in the CLOVER/kext/Other on the EFI Partition folder 

SMBIOS I have edited as your installation guide instruction also has been adjust as my working High Sierra, but no luck with mojave

 

here my screenshot

 

guilty here, I'm really sorry for the trouble 

that is one option in BIOS that I forgot to disable --->b.) MSR Lock Control: Disabled

 

ok, I choose to not going clean install but rather using upgrade from my high Sierra

Mojave now has been installed and also updated to the latest developer beta 11

 

 

Edited by fireedo

Share this post


Link to post
Share on other sites
43 minutes ago, fireedo said:

is rx vega 64 worth it ? is it working OOTB with Mojave at this stage?

With Whatevergreen >1.2.1, Lilu.kext >1.2.6 and my Vega SSDT..  

On 9/16/2018 at 7:09 AM, fireedo said:

I have reconfigured BIOS setting after flashing to the 1503 BIOS version

and I also put and use TSCAdjustReset.kext in the CLOVER/kext/Other on the EFI Partition folder 

SMBIOS I have edited as your installation guide instruction also has been adjust as my working High Sierra, but no luck with mojave

 

here my screenshot

 

guilty here, I'm really sorry for the trouble 

that is one option in BIOS that I forgot to disable --->b.) MSR Lock Control: Disabled

 

ok, I choose to not going clean install but rather using upgrade from my high Sierra

Mojave now has been installed and also updated to the latest developer beta 11

 

 

Well then it is clear why it did not work. 

Share this post


Link to post
Share on other sites

@KGP-iMacPro, amazing work you have here

Today my Radeon RX Vega 64 has arrived, after I uninstalled Nvidia Webdriver then replaced my GTX1080Ti to RX Vega 64, and boom lol ...it works flawlessly, my dual monitor setup work out of the box, I don't do anything, just plug and play, not plug and Pray :D

 

Thank you

 

 

Screen Shot 2018-09-17 at 20.15.52.png

Share this post


Link to post
Share on other sites

well, after couple of minutes playing my Mojave Desktop with new RX Vega 64 always freeze/stuck/halt for no reason at all, I have try to use with/without -lilubetaall but still no effect

and become worse, everytime I reboot and freeze just after a couple of second entering the desktop, I try to reboot, and keep fail, fail and fail.

 

then I found a thread about Vega FE , so it looks like I have try to play about table power or something, so patched/edited AMD10000Controller.kext and now seems like working fine

been playing and fooling around almost 6 hours and no crash or freeze now

 

maybe any other tips beside to edit AMD10000Controller.kext?

 

this is my working kext (at least for me), testing using LuxMark, Rise of the tomb raider and Fortnite, no lag, no freeze and no crash...hope will be "fixed" by apple with the final Mojave

 

AMD10000Controller.kext.zip

Share this post


Link to post
Share on other sites

Hi KGP

your two exhaustive guides about X299 should be updated in some parts

 

I will point some parts where I have personal experiences if you do not mind! ;)

 

1)

Gigabyte Designare Ex bios parameters part

When you have a "right" EFI for your system you can boot with or without CSM (I boot with it for a multi monitor configuration, but I can boot also without it."Right" EFI is very basic and this motherboard with latest kext could boot and work perfectly without SSDT or DSDT addiction

It is the same also for many parameters like fast boot or other you have mentioned with the help of two Designare EX users..one of this have to study also the real meaning of some kext for his rig as I read in other forum..He seems to much confused about its use on his motherboard (TSCAdjustReset.kext)

I am not interested to discuss about this point because I have too much distance from his thoughts. I can boot with or without this kext problem with or without it are the same

2)

APPLEALC kext

with latest release of it and of lilu Kext...you can in many case avoid ssdt or dsdt or config.plist patches to have a DP audio from Nvidia GFX DP port (I am not interested in HDMI audio, DP is working well also removing SSDT/DSDT related part

also lilubetaall flag should be deprecated by now (not sure about it but I am not using in Mojave beta and all is working as should be)

3)

ngfxcompat=1 with latest WhateverGreen.kext

this boot arg could help to have a  working driver (Nvidia on unsupported OSX till Nvidia release a correct driver) without patching anything (obviously same actual limitation)

 

Have nice day

 

 

579510629_ScreenShot2018-09-23at3_39_27PM.png.47440eb8a911f71e416e85ad5602b7a1.png

Edited by fabiosun

Share this post


Link to post
Share on other sites
5 hours ago, fabiosun said:

Hi KGP

your two exhaustive guides about X299 should be updated in some parts

 

I will point some parts where I have personal experiences if you do not mind! ;)

 

1)

Gigabyte Designare Ex bios parameters part

When you have a "right" EFI for your system you can boot with or without CSM (I boot with it for a multi monitor configuration, but I can boot also without it."Right" EFI is very basic and this motherboard with latest kext could boot and work perfectly without SSDT or DSDT addiction

It is the same also for many parameters like fast boot or other you have mentioned with the help of two Designare EX users..one of this have to study also the real meaning of some kext for his rig as I read in other forum..He seems to much confused about its use on his motherboard (TSCAdjustReset.kext)

I am not interested to discuss about this point because I have too much distance from his thoughts. I can boot with or without this kext problem with or without it are the same

2)

APPLEALC kext

with latest release of it and of lilu Kext...you can in many case avoid ssdt or dsdt or config.plist patches to have a DP audio from Nvidia GFX DP port (I am not interested in HDMI audio, DP is working well also removing SSDT/DSDT related part

also lilubetaall flag should be deprecated by now (not sure about it but I am not using in Mojave beta and all is working as should be)

3)

ngfxcompat=1 with latest WhateverGreen.kext

this boot arg could help to have a  working driver (Nvidia on unsupported OSX till Nvidia release a correct driver) without patching anything (obviously same actual limitation)

 

Have nice day

 

 

579510629_ScreenShot2018-09-23at3_39_27PM.png.47440eb8a911f71e416e85ad5602b7a1.png

 

Yes... today I started updating the guides and I will continue with the update during the next days.. 

 

Thanks for providing your points above. 

 

Short quick comment though for clarification: SSDTs or DSDTs are not required for "BOOTING" X299 systems. This does not only state for the Designare EX but for all X299 mainboards.  From the new SSDT library on Github you can select and implement whatever you like or consider as necessary. For booting a system, only a complete and properly adopted EFI-Folder is necessary..   

 

Ciao,

 

KGP

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites

hi,

I am currently using High Sierra on a Asus Rampage VI Apex with a patched 1301 BIOS.

I intend on upgrading to Mojave soon.

 

Before doing so, I wish to have the latest BIOS [1503] installed (to improve stability).

 

Would anyone be to able the patch this BIOS (attached) for me, please?

 

Thanks in advance.

ROG-RAMPAGE-VI-APEX-ASUS-1503.zip

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By NikTheNoob
      Hi,
       
      I'm rather new to Hackintosh and trying my first build with OpenCore on AMD, but I run into issues causing OpenCore to crash before even loading the macOS installer. As I'm not sure which one is causing the crash, I'm trying to resolve all of them and one of the error messages has to do with WhateverGreen, which I was able to see in this slow-mo loading video. Basically I'm getting an error that I'm running an unsupported processor, even though I think I was following this guide by the step.
      What could be causing this and what do I need to do to resolve it?
       
      CPU: AMD Ryzen 2700X
      MB: Gigabyte Aorus X470 Ultra Gaming
      Memory: 4x8 GB HyperX Predator, 3000 MHz Cl15
      Storage: Samsung Evo 970 Nvme 512 GB, Crucial MX500 500GB SATA
      GPU: MSI Radeon RX580 GamingX 8GB
    • By hiprynce
      Hey guys,
       
      I'm trying to install my second Hackintosh system now for like 2 days (first one was Z370, super easy, super stable) with Vanilla Install, but I just can't get the X299 system working.
      I followed the Vanilla Hackintosh Guide strictly and just changed the SMBIOS to iMacPro1,1 in the config.plist.
       
      After selecting the macOS Installer drive on Clover boot menu I never get to the installation process of Catalina... most of the time I get the progress bar to load up until 100% but it never goes further.
       
      Going into verbose mode I got that message at last: IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0 error.
       
      I tried also using the same EFI with a Mojave installer which let me actually install it but the installation process was super slow and laggy - I had to cancel it.
       
      It's now my third day trying to get this done and I'm really feeling frustrated about it as I've been doing nothing else than trying out various solutions I could google.
       
      My kexts:
      AppleALC Lilu WhateverGreen USBInjectAll XHCI-Unsupported IntelMausiEthernet VirtualSMC  
      My system:
      CPU: Intel Core i9-10900X
      Motherboard: ASUS X299 Prime Deluxe II
      CPU Cooler: NZXT Kraken X62
      RAM: 32GB DDR4-3600 CL16 G.Skill Trident Z Royal
      GPU: Sapphire RX5700 XT Nitro+ SE
      PSU: Corsair HX750i
      SSD: 2x 500GB Samsung 970 Evo Plus (both firmwares updated!)
       
      I really hope someone can help me out!
    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app, using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issue DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not show you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
       
      /!\NOTE: There have been reports saying that using this method (switching SMBIOS to a MacPro one) with newer versions of MacOS may cause iTunes to crash.
      So...keep that in mind and better try some of the other methods mentioned here.
       
      A simple Lilu plugin
       
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
       
      More info can be found in this post here.
       
      UPDATE:
       
      According to Vulgo, NoVPAJpeg.kext is now deprecated.
      In case its functionality is needed, use WhateverGreen.kext (alongside Lilu.kext) and add the following boot arguments:
      shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs (tested on my old MSi GTX 650)
       
      This is what I needed for my NVIDIA GPU and the MSI motherboard in the signature (*since then, I upgraded my GPU to my current RX 580). Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
       
      Thanks to @gjw for the tip.
       
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
       
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from dGPU to iGPU and vice-versa.
       
      Cheers!
    • By PlutoDelic
      Hi guys,
       
      I have been running a High Sierra 13.6 build with KGP's Guide for quite a while, until i witnessed a heavy freeze which seemed to have corrupted a complete drive to uselessness. I initially installed KGP's Mojave Guide, which i later found out that my GTX 1050 would make no use for it.
       
      Since i ended up on the beginning, i chose to go Mojave again and got myself a RX 580 Nitro+ from Sapphire.
      I cant make it past to the installer no matter what. It either gives me a KP or goes to the blur screen with the last indicator saying still waiting for root device.
      From what i am understanding is (clearly pointed in KGPs guide too), that RX 580 does not play well along without an IGPU around, which i obviously dont have with a Skylake-X CPU.
      In some cases it stops after com.apple.xpc.launchd process, which pretty much made me isolate this to the GPU.
       
      My EFI is literary KGP's reference one, only differing with the modified TCS kext for my i9-7900x. Even added Lilu 1.4.1 and WEG 1.3.6 to try out different Shiki options. I also strictly used Mojave 10.14.4 for this as KGP is, well retired.
       
      Also note that i have exactly the same issue even if i try out High Sierra 10.13.6 too, for the sake of trying out.
       
      I've hit a big wall with this one.
       
      Build Summary:
      i9-7900x
      Asus Prime X299 Deluxe (B 1503) (configured exactly through KGP's guide, with MSR Disabled).
      Sapphire Radeon RX 580 Nitro+ 8GB
      128 GB 3000mhz DDR4
      Empty Samsung 970 PRO waiting on the first M.2.
      GC Alpine Ridge TB (i know the drills with these).
×