Two new eGPU solutions on macOS 10.13.4: pure EFI and hybrid
 
Notifications
Clear all

Two new eGPU solutions on macOS 10.13.4: pure EFI and hybrid  

 of  19
  RSS

goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@PaperHeart Okay, I thought so. Isn't there any user interface lag while the AMD dGPU is activated? We know that eGPU spans the screen across both displays and apps launched from the eGPU monitor (or headless ghost adapter) will continue running on the internal display, accelerated by the eGPU, if you move the window.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 3 years ago
 
Posted by: goalque
Posted by: LeoLeal

@goalque Does this mean It has little chance of working with latest drivers? Since I still need the EGPUSupport kext installed... I take the Hybrid mode is the EFI Boot added to kext solution, right? If that's the case I have the answer regarding Bootcamp - Just boot into windows as normal, right?

Thank you for the development!

I don't own 750M, guessing the problem lies in the Nvidia web driver itself. You don't need NVDAEGPUSupport.kext with my Hybrid solution, it's a new codeless automate-eGPU.kext (a plain Info.plist in /Library/Extensions/ if you look into "Show Package Contents"). I will organize and clarify the main post of this thread later. If you don't use the internal disk "Macintosh HD" as an installation target, and boot from the USB stick, your Boot Camp installation stays as it is and you can use it as before. No Boot Camp eGPU support yet.

I would think It was with the kext because The problem only happened when driver was paired with the Kext... the Internal display stopped working with the pair even without eGPU plugged In... and without the Kext the Latest driver worked well with dGPU.

Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970


ReplyQuote
PaperHeart
(@paperheart)
Active Member
Joined: 2 years ago
 
Posted by: goalque

@PaperHeart Okay, I thought so. Isn't there any user interface lag while the AMD dGPU is activated? We know that eGPU spans the screen across both displays and apps launched from the eGPU monitor (or headless ghost adapter) will continue running on the internal display, accelerated by the eGPU, if you move the window.

@goalque Yes you are completely correct. There is no UI lag or glitch at all when internal display is driven by dGPU, the system works perfectly fine, better than I expected. I've just done a quick test, if I set the internal display as the primary one and launch a application on it, the application is run on dGPU even if I drag the window to the display connected to the eGPU (and of course, vise versa).

Another thing I noticed is that when the internal screen is driven by iGPU, i.e. eGPU connected before system boot. If there is a dynamic icon, for instance, a syncing dropbox icon (only dynamic one, a dropbox icon without the spinning arrow does not cause this problem) or a real time network traffic monitor, on the system status bar, the whole system will become extremely slow (~1 frame per 2 seconds). Once I quit that application or set it as a static icon in the preferences of that application, the OS goes back to normal in few seconds.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@PaperHeart Interesting. You can edit the config.plist file and also try setting ForceIntegrated to <false/>. If there is a need for forcing AMD dGPU in the future, I might implement a new key "ForceDedicated", or maybe a key with an integer value (do nothing=0, ForceIntegrated=1, ForceDedicated=2). Now, if you set ForceIntegrated=false, the app doesn't control the gmux in any way.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
PaperHeart
(@paperheart)
Active Member
Joined: 2 years ago
 
Posted by: goalque

@PaperHeart Interesting. You can edit the config.plist file and also try setting ForceIntegrated to <false/>. If there is a need for forcing AMD dGPU in the future, I might implement a new key "ForceDedicated", or maybe a key with an integer value (do nothing=0, ForceIntegrated=1, ForceDedicated=2). Now, if you set ForceIntegrated=false, the app doesn't control the gmux in any way.

@goalque I did some quick test with ForceIntegrated set to false.

Results:
-Plug before system boot. iGPU drive internal display on idle. When application requires high performance GPU launched, internal screen was turned off although at that time dGPU was powering it. UI lag when switching GPUs. Dynamic status bar icon caused system slow.

-Hot plug. iGPU drive internal display on idle. dGPU was driving internal display when application requiring high performance GPU launched (internal screen not turned off). No UI lag when switching GPUs. No dynamic icon influence. Internal screen acceleration worked ok.

In comparison, with ForceIntegrated set to true. The internal screen is always driven by iGPU when cold plugged and by dGPU when hot plugged regardless of whether there is an application requiring high performance GPU is running.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

Maybe the firmware remembers the default gmux state in the preboot environment, once set to integrated and "automatic graphics switching" turned on. Anyway, ForceIntegrated=true solved the problem where both screens were black (when cold plugged), so that is now default when the installer detects a dGPU equipped Mac. Useful in "Pure EFI" mode as well.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 3 years ago
 

@goalque Since Bootcamp Support is still unavailable with this solution, It would be nice To make It clear in the original post too... some of us are gamers and need windown runnign with the eGPU to play games.

Grats on the results tho... It is very exciting that we have an alternative for eGPU without tainting(somewhat) the SO.

Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970


ReplyQuote
kingbri
(@kingbri)
Eminent Member
Joined: 2 years ago
 

@leoleal, do we really need the script. In my personal experiece I use my egpu for gaming on windows because windows natively supports most nvidia cards or amd cards (mac supports AMD better). I only use the egpu on mac for editing and VMs. Or are you talking about forcing an igpu over a dgpu because that needs to be fixed. This script looks really cool and I cannot wait to try it on my TB1 mac!

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Riss
 Riss
(@riss)
Eminent Member
Joined: 3 years ago
 
Posted by: goalque

Just select the "EFI Boot" disk image on the Apple's startup manager screen. You need the USB on every startup, then can unplug it. Another install option is the internal "Macintosh HD" and its EFI partition, no need for USB stick. The installer is able to uninstall everything from the internal disk as well, but this is at beta stage so I recommend USB.

It is very unlikely that something can go wrong because there is strong preinstall validation. The EFI app doesn't support AMD eGPU at the moment, only Nvidia 900 and 1000 series cards.

What about Quadro Pascal? Have one P2000 (along with old flashed GTX 780)

mid 2014 MBP 15" GT750m | Mac mini 2012 | Akitio Thunder 2 & 3 | GTX 780 3GB (flashed) | GTX Black Titan 6GB (stock) | Quadro P2000 (stock)


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago
 
Posted by: LeoLeal

@goalque Since Bootcamp Support is still unavailable with this solution, It would be nice To make It clear in the original post too... some of us are gamers and need windown runnign with the eGPU to play games.

Grats on the results tho... It is very exciting that we have an alternative for eGPU without tainting(somewhat) the SO.

Would this effect booting into windows though? On boot select screen selecting Bootcamp means you bypass this script surely? 

@goalque will delete and reinstall, see where I end up, the promise of accelerating my Ultrafine is too tempting... have updated to 10.14.5 too, was previously on .4.

edit: have I made a mistake updating to .5?

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@Riss, I can provide a new version without eGPU validation for those who want to test Nvidia cards which aren't on the list atm. Once confirmed, I will add it. There seems be a possible vBIOS problem with the Titan X Pascal, not even pci scanning in EFI detects this card with @shrapnl's nMP, has anyone else the Titan X to confirm?

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
hkoster1
(@hkoster1)
Eminent Member
Joined: 2 years ago
 

Interesting development with great potential, thanks @goalque
Here is my experience with Pure EFI installations on the Macintosh HD; Sonnet 550 + GTX1070 + Dell P2415Q:

  • Mac Mini 2014 (iGPU via HDMI-cable, eGPU via DP-cable). This worked once (great Valley score and FPS), but resulted in dark (though live) screens ever after. Wanted to mod "config.plist", but could not find this file.
  • MacBook Pro 2017 15-inch TB RP560. After EFI Boot the Apple logo plus boot progress bar appears first on MBP screen, then switches to eGPU screen, and finally results in "Critical software component missing" message which fails to install.

So close, so close... I'll keep watching this thread.

~

Radeon RX 5700 XT + Razer Core X + LG 23.7" 4K UltraFine + Huawei VR2 DP/USB to USB-C cable
Mac Mini 2018 always latest public macOS build


goalque liked
ReplyQuote
lexine
(@lexine)
Trusted Member
Joined: 2 years ago
 

Dear all,

I can confirm that the hybrid solution is working for me as design on MBP 13" TouchBar 2017 + Aorus Gaming Box 1070 + latest NVIDIA Drivers with SkipSetupDataForOSX=false in config.plist. I did not tried the Pure EFI...

The issue I encountered previously - Clover boot hang, was related to issue with the default boot entry not found. ( I installed solution on local drive)
unlocking 'Startup Disk' in system preferences fixed the problem for next reboot, but subsequent reboots still hang at Clover.

This is consistent with the following line from the Clover Wiki:

OS X Startup Disk can be used to reboot into another volume, but for the following reboot DefaultVolume will be used again.

0:617 0:002 === [ GetEfiBootDeviceFromNvram ] =========================
0:618 0:000 Default boot entry not found​

more info available at: https://www.tonymacx86.com/threads/solved-clover-wont-boot-from-default-boot-volume.221421/

I can confirm that this issue is not presented when the solution is installed on the external drive and it will boot properly.

2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@hkoster1 "Critical software component missing" is part of Apple's security mechanism in the newer firmwares, it seems that High Sierra checks the firmware against Apple's database:

https://www.macrumors.com/2017/09/25/macos-high-sierra-weekly-efi-security-check/

even if the patch is done on the fly.

As said, Pure EFI isn't recommended approach, please choose the Hybrid.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
Gnim
 Gnim
(@gnim)
Active Member
Joined: 2 years ago
 

It worked very well on my git:
Macbook Pro 15 2016
Razer Core X
Msi Gtx 970
I still have a few issues:
1. I use DisableMonitor to shut down the internal display. But the internal one keeps coming back whenever I quit from a full screen app.
2. Not sure if it is an issue. I got onely 2003 on the Unigine Valley Benchmark(Preset: Extreme HD).
3. When I try to watch 4k movie by Movist, it quits to the login screen.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@lexine When you installed the software on the "local drive", was it named "Macintosh HD" or something else, and what kind of Boot section was generated to the config.plist? The installer could pick up the unique volume ID instead of using volume name as it does now. Or might be easier to rewrite the boot logic all from scratch...

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
firestarter451f
(@firestarter451f)
Active Member
Joined: 2 years ago
 

hello,

has anyone tryed this with redshift3d, octane, premiere or davinci resolve? if so, does it work fine?

thanks

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
lexine
(@lexine)
Trusted Member
Joined: 2 years ago
 

I don't have a backup of config.plist available now from those tests, but the default boot volume was set to Macintosh HD, I tried to change it for a disk UUID but no luck ... I noticed now that even when the solution is on USB stick I still need to select the start-up disk ... This is a complete new topic for me as I don't have so much experience with the Clover ... but anyway I noticed that it might have something to do with my nvram maybe? As the efi-boot-device is empty, but as soon as I setup the startup disk the variable will be created ... For sure I would need to study it a more to find out what is the problem ... but maybe someone else will already know 😉

Libors-MBP:~ lbaca$ nvram efi-boot-device

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>FF9F4F5A-ADC7-44E0-955C-8C17095488E0</string></dict></dict><key>BLLastBSDName</key><string>disk1s2</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\E7609E06-9D8A-334B-9214-8A4D5231957F\System\Library\CoreServices\boot.efi</string></dict></array>

Libors-MBP:~ lbaca$ 


2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


ReplyQuote
lexine
(@lexine)
Trusted Member
Joined: 2 years ago
 

Here is the boot section which has been generated : 

<key>Boot</key>
<dict>
<key>Debug</key>
<false/>
<key>DefaultLoader</key>
<string>boot.efi</string>
<key>DefaultVolume</key>
<string>Macintosh HD</string>
<key>Fast</key>
<true/>
<key>ForceIntegrated</key>
<false/>
<key>SkipSetupDataForOSX</key>
<false/>
<key>Timeout</key>
<integer>0</integer>
</dict>

and here the disklist, I tried to used the UUID of the Macintosh HD and Preboot as recommended on other sites, but I did not had luck 

Libors-MBP:~ lbaca$ diskutil list

/dev/disk0 (internal):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                         500.3 GB   disk0

   1:                        EFI EFI                     314.6 MB   disk0s1

   2:                 Apple_APFS Container disk1         500.0 GB   disk0s2

 

/dev/disk1 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +500.0 GB   disk1

                                 Physical Store disk0s2

   1:                APFS Volume Macintosh HD            140.2 GB   disk1s1

   2:                APFS Volume Preboot                 22.6 MB    disk1s2

   3:                APFS Volume Recovery                518.1 MB   disk1s3

   4:                APFS Volume VM                      1.1 GB     disk1s4

2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: lexine

 I noticed now that even when the solution is on USB stick I still need to select the start-up disk ... This is a complete new topic for me as I don't have so much experience with the Clover ... but anyway I noticed that it might have something to do with my nvram maybe? As the efi-boot-device is empty, but as soon as I setup the startup disk the variable will be created ... For sure I would need to study it a more to find out what is the problem ... but maybe someone else will already know 😉

A quick look at the source revealed that there is a huge amount of code that will never be needed. I found the right spot:

UEFI boot: get gEfiBootDeviceGuid from NVRAM.
// if present, ScanVolumes() will skip scanning other volumes
// in the first run.
// this speeds up loading of default macOS  volume.
   GetEfiBootDeviceFromNvram();
}

Got the same error at some point once, I will try to reproduce the problem and then can fix it.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: Eightarmedpet

edit: have I made a mistake updating to .5?

Not a mistake. Just remember to use installer's "Uninstall" option, don't do anything manually, otherwise the automate-eGPU.kext might be still in the cache. You might have the same issue as @lexine, regarding the default boot volume and nvram.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
lexine
(@lexine)
Trusted Member
Joined: 2 years ago
 

@goalque I just connected the eGPU while I was already working in MacOS (booted from EFI) and got the black screen on external monitoring, no surprise, it was the usual, so I logged of and back in but still black screen ... ok rebooted with EGPU connected, black screen ... change the SkipSetupDataForOSX back to true, rebooted now working ... so just to let you know that the screen is working for me with this value as well ... not sure what is going on, maybe my setup like to make fun of me ; -) ... I anyway I will enable debug log for next time .... I did not noticed anything special in the console log though ... any other place I can look next time to pin-point the problem ? 

2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: lexine

@goalque I just connected the eGPU while I was already working in MacOS (booted from EFI) and got the black screen on external monitoring, no surprise, it was the usual, so I logged of and back in but still black screen ... ok rebooted with EGPU connected, black screen ... change the SkipSetupDataForOSX back to true, rebooted now working ... so just to let you know that the screen is working for me with this value as well ... not sure what is going on, maybe my setup like to make fun of me ; -) ... I anyway I will enable debug log for next time .... I did not noticed anything special in the console log though ... any other place I can look next time to pin-point the problem ? 

Logging off isn't always enough, you might need to hot plug the eGPU monitor as well. SkipSetupDataForOSX=false is the last thing to try. Since it has something to do with hibernation and SMC, this Clover section will be skipped as default always (=true). Anyhow, seems to be beneficial in awakening the eGPU screen with some Mac models, especially in pure EFI mode, so I left this optional. SMC reset should clear everything, I suppose.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago
 

Worked a charm second time around.
10.14.5, SIP Disabled (fully - had custom settings previously, kext signing?), Hybrid. Wasn't able to get internal screen accelerated but will continue to play.
DaVinci studio used the 1070 I think.. its activity was identical to my iGPU which I found a bit odd...

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@Eightarmedpet, congratulations! Smile The EFI boot sets SIP to 0x3:
https://clover-wiki.zetam.org/Configuration/RtVariables#rtvariables_csractiveconfig
for loading the unsigned automate-eGPU.kext from the cache. It could be also value 0x11 in hybrid but 0x3 should handle all combinations (including SkipSetupDataForOSX=false). When I have time, I will summarize everything on the first post.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
(@magistr_avsh)
New Member
Joined: 2 years ago
 

Error "Your eGPU [0x1c0210de] is not supported.".
MBP 13 2017, GTX 1060, TB3->TB2 connector.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
protogon
(@protogon)
Active Member
Joined: 2 years ago
 

So, what is the expected behaviour from Hybrid EFI?

Right now (MBP 2017 Touch, TB3, Sonnet, TitanXP) it works like it used to with fr34k's script (just a bit worst in some cases) but feels more stable.
Installed at 1st in a usb stick and then in Macintosh HD:

  • the unmount icon does not appear on the menubar.
  • still need to hot plug while in login screen and once the fps where at 30 had to logout/in for it to come back.
  • hot unplug panics.
  • "Critical software component missing" msg.
  • It does not appear as an option to make it default startup disk

Are these normal symptoms or does it misbehave in my system?
Amazing work BTW @goalque.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: Magistr AVSH

Error "Your eGPU [0x1c0210de] is not supported.".
MBP 13 2017, GTX 1060, TB3->TB2 connector.

Thanks for reporting. GTX 1060 3GB is not on the supported list atm. Only the 6GB version is, I will add.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: protogon

So, what is the expected behaviour from Hybrid EFI?

Right now (MBP 2017 Touch, TB3, Sonnet, TitanXP) it works like it used to with fr34k's script (just a bit worst in some cases) but feels more stable.
Installed at 1st in a usb stick and then in Macintosh HD:

  • the unmount icon does not appear on the menubar.
  • still need to hot plug while in login screen and once the fps where at 30 had to logout/in for it to come back.
  • hot unplug panics.
  • "Critical software component missing" msg.
  • It does not appear as an option to make it default startup disk

Are these normal symptoms or does it misbehave in my system?
Amazing work BTW @goalque.

Hmm... "Critical software component missing" in hybrid. Maybe after all, this is due to some bug when rsyncing EFI folder to the internal EFI partition, and not related to Apple's EFI security check with newer firmwares? Did you get the same message when using the USB stick? This is still beta. I am in the process of examining secondary APFS partition, if possible to use it as a bootable volume. The unmount icon is removed on purpose (hot plugging still works).

Glad to hear that Titan Xp worked!

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
protogon
(@protogon)
Active Member
Joined: 2 years ago
 
Posted by: goalque  Did you get the same message when using the USB stick?

No, have not seen this before neither when using it from USB nor after I installed it in HD.
Just rebooted after kernel panic (forgot to press alt at startup) and there it was :/

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: protogon
Posted by: goalque  Did you get the same message when using the USB stick?

No, have not seen this before neither when using it from USB nor after I installed it in HD.
Just rebooted after kernel panic (forgot to press alt at startup) and there it was :/

What was the cause for the kernel panic? If you boot without the alt, errors can pop up. Clover's "DefaultVolume" isn't perfect. I am thinking about rewriting it, by simply looping through all volumes and searching for boot.efi match at /System/Library/CoreServices/.

EDIT: misunderstood, so the cause was that you forgot to press alt and choose "EFI boot". automate-eGPU.kext alone, without EFI boot selection will always result in kernel panic if the eGPU is connected.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


protogon liked
ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

Ok I reinstalled 10.13.5 and Installed in USB Drive Hybrid mode.  First boot up I had success, I was able to get fully accelerated OpenGL/Metal/OpenCL, video output to my external monitor, and ran some benchmarks.  Had some of the odd UI lagginess when running programs which could talk to the dGPU, if patient it normally went away after 10-15 seconds or so.  I wanted to make sure my windows install still worked, and that I could boot MacOS and have it work properly undocked.  

I rebooted to Boot Camp, everything went as normal.  I booted into MacOS with no peripherals attached, everything worked as normal.  I shut down, plugged back in and tried BOOT EFI Again.  Got a black internal display and no external display.  Forcibly shut down with power button, booted into Boot Camp, Got only windows logo on internal display but external worked fine, gmux must be set wrong, which accounts for the black screens on BOOT EFI boot also.  Unplugged everything, booted into normal MacOS, then shutdown, plugged in egpu and booted Windows, both screens active and working as normal.

Seems to be an issue with gmux setting when I switch between bootcamp and EFI-Automated USB boot, is there something I need to do to make both work?

This is on my 2016 15" +Core v2 +gtx 1080

2019 16 Macbook Pro + Core v2 + Radeon VII MacOS 10.15.1
Core X Chroma + RTX 2080 Windows 10 1909
Asrock X570 Phantom Gaming ITX/TB3, Ryzen 5 3400G + Core v2 + Radeon VII Win10 1909


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

How about subsequent boots into macOS, did you get constant eGPU screen output? Which SkipSetupDataForOSX setting? Booting into BootCamp disables the iGPU, apple_set_os.efi keeps it active (requires integrated gmux state). Already supported, but you need a different config.plist to boot into Windows. Details later.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

Subsequent boots into egpu enabled MacOS did not work and yielded a black screen on internal display and no boot logo/progress bar.  If I boot from Macintosh HD directly with nothing plugged in it works fine, if I boot without the EFI USB but the egpu plugged in the system shuts down halfway through MacOS boot.  Did not try EFI BOOT and hot plugging (the USB drive is plugged into the core v2, and the one I used doesn't work with Apple's USB-A to C adapter.)  My boot camp installation is naked with PCI Root 1905 disabled and everything plugged into right hand ports, not using any additional software.

Also I have FileVault enabled, not sure if that causes problems too.

SkipSetupDataForOSX is enabled.

I've uninstalled the kext for now, I need this mac fully operational for tomorrow.  Will reinstall when I have time to play around with it.

2019 16 Macbook Pro + Core v2 + Radeon VII MacOS 10.15.1
Core X Chroma + RTX 2080 Windows 10 1909
Asrock X570 Phantom Gaming ITX/TB3, Ryzen 5 3400G + Core v2 + Radeon VII Win10 1909


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

I meant subsequent boots into macOS before the Windows Boot camp disabled the iGPU. Apple's firmware keeps only the dGPU active, and turns off the iGPU which affects the state. To keep them both active on Windows, apple_set_os.efi is required even if the AMD dGPU + Nvidia eGPU combo is operational (as with my M370X).

Yep, might be. FileVault off state should be the default with eGPUs.

SkipSetupDataForOSX=false gives 100% success for me but not recommended as I want to minimize all hackintoshing stuff, and accessing the SMC might be risky.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


ReplyQuote
 Tav
(@tav)
New Member
Joined: 2 years ago
 

Update: Now works again if I cold boot into EFI mode, it seems leaving FileVault enabled was causing it to not work on subsequent boots. Interestingly however hot plugging does not work despite having hybrid mode installed, after I log in I get a black screen with a movable cursor on both internal and external display.

TL;DR: First try hybrid mode worked fine last night. Booting today into EFI option gives a black (backlit) screen, booting regularly gives a kernel panic-y message when both hot and cold plugging. 

I have a base model 13" 2017 MBP without touchbar, connected to a Razer Core X with a gtx1070. After installing the hybrid option of the latest release, I rebooted into EFI mode and connected to the Core X without any issues. No disconnect option in the top bar, but it seems like other are people are experiencing this as well, so I didn't worry. When I was done I shut down and rebooted to use laptop mode. 

Today, after both hotplugging and coldplugging, my computer restarts (I don't know if it was a kernel panic, as it looked different from when my 2015 MBP kernel panicked) and I get a kernel panic-y message about a problem. Part of me makes me think I am missing something and that I just don't know what it is, given that it worked last night. I disabled SIP, but did not turn FileVault off (doing so atm), and made sure all apps were halted. It seems other users have edited their config.plist options to make their builds work, but idk if that would be related to my issue. I assume I am intended to boot regularly during this process, as trying to boot back into EFI mode gives a black (backlit) screen. 

As many other people in this thread have said, thank you Goalque (and everyone else helping) for this amazing work! I almost couldn't believe it when I saw it connect last night. Smile

Edit: Forgot to mention I'm on 10.13.5 and installed the pkg to my internal ssd.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
 of  19