Setup & Software Discussions
Two new eGPU solutions on macOS 10.13.4: pure EFI and hybrid
 

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
 

@mac_editor, please test again and give understandable feedback 🙂 I cannot help anyone here if my questions are not answered 🙂

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago
 

@goalque Initial tests with automate-eGPU EFI 1.0.0 - doesn't seem to work for me either. Same symptoms as @dannyvegas. Attempted to set it as I had in earlier testing, but the results did not change. System seems to crash in presence of eGPU, and the panic log is very familiar - GPUWrangler and GeForceWeb in the backtrace with a kernel trap. This used to happen when plugging in the eGPU with the TB2 patch + web drivers if I recall correctly.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


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

@mac_editor Thanks. Does the config.plist look correct and chosen patches? The same config works with the M370X (ForceIntegrated=true).

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago
 

@goalque They looked correct in my opinion. Also verified automate-eGPU.kext. Plist was in order. There are 4 main things to do in the new patch (2 in plist, 2 injected) - seemed correct. In my earlier tests, ForceIntegrated made no difference. It may seem that the older NVIDIA patch (via EFI) worked better. Yet to test that. The link on the main page is the most up-to-date installer right?

There are a couple of problems:

  • DefaultVolume - not set correctly and boots the wrong system first-time in some cases
  • SIP - if someone had it already disabled, that changes to a custom config (0x3)

 

Webdrivers were installed correctly and functional. 

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


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

Yes, there is only one publicly available version at the moment, the link on the main page. The DefaultVolume is known issue and fixed already, not released. 0x3 is one value for both, "Pure EFI" and "Hybrid". A bit annoying if someone tries to uninstall and it prompts about the wrong SIP status (requires 0x67, fully disabled, or rebooting from the recovery partition and typing csrutil disable).

I would turn on the debug log to see what is going on.

EDIT: What about the SkipSetupDataForOSX? I recall that you tested a version at some point where this wasn't in use, or @itsage... I hope you don't have to set it to false, better if there is another solution.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago
 

@goalque Tested with false as well - same problem. Since its a KP, likely something else. Will test on fresh test install.

Baffled why it doesn't work when PW uses exactly the same modifications that the kext + injection do.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


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

@goalque Tested with false as well - same problem. Since its a KP, likely something else. Will test on fresh test install.

Much appreciated. One more question, was the DefaultVolume value written incorrectly to the config.plist Boot section or did you mean that the Clover did not choose the default boot disk correctly? The postinstall script changes that value, so there might be a bug.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago
 

@goalque Both in the case of DefaultVolume. Allow me to expand on my boot environment:

  • External Drive with 2 partitions (Games - NTFS, macOS Test - HFS+ - Target Volume, No encryption)
  • Pen Drive SanDisk 16GB with 2 partitions (AUTOMATE-EG - FAT32 - Target Install Disk for EFI, macOS 10.13.5 Installer - HFS+)
  • Internal drive with 2 partitions (macOS - APPS - No encryption, Windows - NTFS)

 

I was running macOS Test (10.13.5) where I downloaded the package.

  • Chose target disk as AUTOMATE-EG.
  • Installed web drivers as well.
  • Install successful.

 

Initial config state:

  • DefaultVolume = Macintosh HD
  • ForceIntegrated = YES (either should do)
  • Rest hybrid configuration as expected with no SSDT dropping

 

When I installed the package, my boot disk had just been set to macOS Test (through Boot Manager EFI holding control to make it permanent). After fixing default volume setting, I rebooted, but it went to boot macOS. So I went into Prefs > Startup, chose macOS Test, then proceeded to boot from EFI stick. This time it targeted the correct disk -> then KP issues.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


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

The script then correctly changed the DefaultVolume to "macOS Test" because you were running that and the app expected you would use this disk (pkg location) where to look for Apple's boot.efi. This is also the volume where the automate-eGPU.kext will be installed (in Hybrid mode). If you choose another macOS target partition, there is a contradiction. It doesn't support multiple macOS partitions, good point. It's preferred to use an empty USB stick, single partition (FAT32 formatted). In that case also, it chooses the current disk (pkg location) and uses that for DefaultVolume.

Clover reads from the nvram and fails to choose the default volume, so pls look into the debug log. I can send you the new bootx64.efi later where this nvram logic is removed.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago
 

@goalque The script did not change DefaultVolume to "macOS Test". What I meant was I set it manually. Your reasoning about Clover may be right. To clarify, my boot process was:

Press and hold opt -> control click "macOS Test" (boot device should be set - NVRAM updated?) -> Install EFI on AUTOMATE-EG -> Check DefaultVolume -> was Macintosh HD -> Change manually to "macOS Test" -> Reboot with opt -> Select EFI Boot -> Booted into "macOS" -> When to prefs, set it again to "macOS Test" -> Reboot on EFI -> booted correct disk. In any case, a minor problem which you have resolved anyway.

KP is the issue.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


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

UPDATE: 01.07.2018 automate-eGPU EFI v1.0.1 released:  https://cdn.egpu.io/wp-content/uploads/2018/07/automate-eGPU-EFI-v1.0.1.pkg_.zip

What's new in 1.0.1

- added support for GeForce GTX 780 3GB, GeForce GTX Titan, GeForce GTX 780 6GB, GeForce GTX 750 Ti, GeForce GTX 1060 3GB, Quadro P2000 5GB
- ValidateNvidiaKexts() and ValidateOtherKexts() in the preinstall stage (modified kexts not allowed)
- config.plist ForceIntegrated changed to MuxSetting [0 (do nothing), 1 (integrated), 2 (dedicated)]
- AMD dGPU equipped MBPs have MuxSetting 1 automatically
- DefaultVolume EFI logic refactored
The installer asks to disconnect the eGPU enclosure to avoid kernel panics during cache rebuilding
- config.plist CsrActiveConfig value is now 0x67 (disabled)

@riss now you can test both GTX 780 and P2000
@ghettocivic now you can test GTX 750 Ti
@magistr_avsh, @jack_dorsey now you can test GTX 1060 3GB and report how it goes

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


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

@goalque The script did not change DefaultVolume to "macOS Test". What I meant was I set it manually. Your reasoning about Clover may be right. 

Thanks for testing. The 750M model is now confirmed to work, the default MuxSetting should now be 0 (do nothing). So ForceIntegrated=true was the reason for kernel panic. DefaultVolume also fixed.

A few words for everyone: don't expect that everything is automated yet. Please report behaviour with different config.plist configurations and boot methods (such as hot plugging, log out/log in, hot plugging the eGPU display). It doesn't help if you just say "it doesn't work". Recommendation: choose "Hybrid" and use an external USB stick. Warning: after installed, do not plug in the eGPU when you boot normally through "Macintosh HD" disk image, uninstall the automate-eGPU.kext first.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


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

EDIT: v.1.0.3 released 🙂
- fixed "Invalid Nvidia kext found" error message if web drivers are not installed (1.0.2 didn't check the kext existence)
https://cdn.egpu.io/wp-content/uploads/2018/07/automate-eGPU-EFI-v1.0.3.pkg_.zip

automate-eGPU EFI v1.0.2 released

- added support for Geforce GTX 780 Ti
- SkipSetupDataForOSX=false setting now works (primarily meant to be used with "Pure EFI" if you want eGPU screen output)
- deletes unnecessary automate-eGPU.kext from the install location

 

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


protogon liked
ReplyQuote
pengus77
(@pengus77)
Active Member
Joined: 1 year ago
 
Posted by: goalque

EDIT: v.1.0.3 released 🙂
- fixed "Invalid Nvidia kext found" error message if web drivers are not installed (1.0.2 didn't check the kext existence)
https://cdn.egpu.io/wp-content/uploads/2018/07/automate-eGPU-EFI-v1.0.3.pkg_.zip

@goalque I installed the nvidia drivers via webdriver.sh  to force the old 378.x ones and the 1.0.3 package says the nvidia kexts are invalid... trying now to uninstall via webdriver.sh and then reinstall after.

MacBook Pro Mid-2014 - GT750M - Sonnet eGFX Breakaway Box TB3 with TB2 adapter - NVidia GTX 1080


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

EDIT: v.1.0.3 released 🙂
- fixed "Invalid Nvidia kext found" error message if web drivers are not installed (1.0.2 didn't check the kext existence)
https://cdn.egpu.io/wp-content/uploads/2018/07/automate-eGPU-EFI-v1.0.3.pkg_.zip

@goalque I installed the nvidia drivers via webdriver.sh  to force the old 378.x ones and the 1.0.3 package says the nvidia kexts are invalid... trying now to uninstall via webdriver.sh and then reinstall after.

Because they are invalid: "Modifies the installed driver's NVDARequiredOS Info.plist property."

https://github.com/vulgo/webdriver.sh

The EFI app allows only official web drivers matching macOS build number.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
pengus77
(@pengus77)
Active Member
Joined: 1 year ago
 
Posted by: goalque
Posted by: pengus77
Posted by: goalque

EDIT: v.1.0.3 released 🙂
- fixed "Invalid Nvidia kext found" error message if web drivers are not installed (1.0.2 didn't check the kext existence)
https://cdn.egpu.io/wp-content/uploads/2018/07/automate-eGPU-EFI-v1.0.3.pkg_.zip

@goalque I installed the nvidia drivers via webdriver.sh  to force the old 378.x ones and the 1.0.3 package says the nvidia kexts are invalid... trying now to uninstall via webdriver.sh and then reinstall after.

Because they are invalid: "Modifies the installed driver's NVDARequiredOS Info.plist property."

https://github.com/vulgo/webdriver.sh

The EFI app allows only official web drivers matching macOS build number.

No worries, removed nvidia drivers, installed 1.0.3, reinstalled nvidia drivers, rebooted, profit 🙂

MacBook Pro Mid-2014 - GT750M - Sonnet eGFX Breakaway Box TB3 with TB2 adapter - NVidia GTX 1080


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

You installed the old web drivers afterwards? Drivers can be installed before (the matching one only), during the installation (the matching one only) or after (anything you like).

Why not even Info.plist modifications? Due to design pattern to keep system 100% clean.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
Gnim
 Gnim
(@gnim)
Active Member
Joined: 1 year ago
 

You are just wonderful goalque
With the 1.3 patch, my gtx 970 now can peacefully go sleep and wake up. Also, I don't have to wait unreasonably long back to the desktop after quitting a game.
Just wonder if it possible to enable the clamshell?

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
 

@Gnim thanks! Basic things first. There is a lot to do in terms of AMD dGPU and Nvidia eGPU. Any app utilizing the dGPU might still turn the internal screen black (with MuxSetting=1).

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
pengus77
(@pengus77)
Active Member
Joined: 1 year ago
 
Posted by: goalque

You installed the old web drivers afterwards? Drivers can be installed before (the matching one only), during the installation (the matching one only) or after (anything you like).

Why not even Info.plist modifications? Due to design pattern to keep system 100% clean.

Yeah, installed the 378.x driver after the installation completed (asked if I wanted to download and install the latest nvidia webdriver and I said no). As I said earlier the process has been:

  1. Uninstall nvidia driver via webdriver.sh
  2. Install your 1.0.3 package
  3. Select Hybrid mode
  4. Said "no thanks" to nvidia drivers installation
  5. Disconnected eGPU when suggested
  6. Installed 378.x drivers via webdriver.sh when the installer finished
  7. Reboot via EFI
  8. All good

Would be awesome if the installer detected the plist modification in the nvidia drivers (just the target os thing) and let it be, but hey, it's a 3 minutes manual process so I don't really need it 🙂

MacBook Pro Mid-2014 - GT750M - Sonnet eGFX Breakaway Box TB3 with TB2 adapter - NVidia GTX 1080


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

automate-eGPU.kext should override NVDARequiredOS if you manage to install the old web driver in a way that it doesn't modify Info.plist. In theory, there shouldn't be real need for old web drivers. @mac_editor is trying different combinations for isolating default native driver (750M) from web drivers (for eGPU only). If it works, I can update the automate-eGPU.kext.

Hybrid still recommended, the "Pure EFI" doesn't require automate-eGPU.kext at all. Those who are adventurous enough, try it out.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
ghettocivic
(@ghettocivic)
Active Member
Joined: 1 year ago
 

Thanks goalque...installed on my system and seems to be running well.  It did fail to work properly the first time I installed (although the install said it completed successfully). I forgot that, after restoring from a Time Machine backup, that SIP may be re-enabled.  I un-installed automate-eGPU, disabled SIP, then re-installed and it works great now!  Does the installer check for SIP being disabled?  Should it even matter? I'll keep you posted if anything unusual happens  :mrgreen:

MacBook Pro 13" Late 2013 + Akitio Thunder2 + Sapphire RX570 ITX


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

@ghettocivic Thanks! Which mode? Hybrid or Pure EFI? System restart is required. The installer checks SIP in Hybrid. In Pure EFI, SIP can be enabled during the installation.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


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

Good news! I just tested the hybrid mode on 2011 Mac mini and GTX 980, and it worked on the first run. Gray screen TB1 Macs will get support soon.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ozzy, pengus77, mac_editor and 1 people liked
ReplyQuote
pengus77
(@pengus77)
Active Member
Joined: 1 year ago
 

@goalque great job with the last update! I can confirm that rebooting on my mid 2014 doesn't lead anymore to a kernel panic and performs the reboot correctly!
Now, I have to be superfast and unplug the eGPU as soon as the reboot begins, otherwise the system doesn't boot, but hey, works 🙂

MacBook Pro Mid-2014 - GT750M - Sonnet eGFX Breakaway Box TB3 with TB2 adapter - NVidia GTX 1080


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

I am wondering why hot plugging doesn't work with the 750M. What does the console log say? And "kextstat | grep NVDA"? There must be some way. I would try web driver/native driver separation. Any news regarding this @mac_editor?

I was surprised that my 2011 Mac mini was hot pluggable, GTX 980 blinking the green light immediately. Logout/login produced the eGPU screen output.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago

goalque liked
ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 2 years ago
 

Had previously posted a question about the steps I outlined a few days ago, when things didn't work as expected. I deleted that. Hopefully no one is responding but in case anyone had the same confusion I did...

I didn't realize that when you run the installer, the intent is to install things on the FAT 32 drive and the local drive also, and that the EFI / Hybrid option is only seen during installation, NOT when you subsequently option-boot. There it will only show the EFI icon when you boot.

Basically you need to have the thumb drive attached and boot from that EFI setup but it works in conjunction with all the rest of your drivers and apps on the local drive. Some type of bypass I'm assuming, to keep things running stable. Pretty ingenious!

Currently testing MBP14,3 on 10.13.5 with version 1.0.3 of the NVIDIA installer and so far seems to have worked. I see the GeForce 1070 card in the System report, reported as an eGPU. So now to test actual software.

Thunderbolt 3 Macs, Sonnet and OWC eGPUs, 4K Displays, etc


goalque and itsage liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago
 

@goalque Booting with NVIDIA eGPU (web driver PCI match eGPU-only) + mux=1 + dGPU 750m = Kernel Panic. I will try some other tricks soon.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


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

@chippy-mcchipset Obviously, I misunderstood and read your steps too quickly, sorry. If you didn't get the following message:

"Your Mac model has known issues with Nvidia cards on startup/shut down, and can't use the pure EFI mode. Please hot plug during the boot process or at login screen.",

the installer should provide both the "Hybrid" and "Pure EFI" options in the beginning of installation. The installation shows up as one "EFI Boot" selection when you boot through Apple's startup manager. By selecting it, you will be booted into macOS volume where the automate-eGPU.kext was installed (or, in the case of Pure EFI, where the installation occurred). At this stage, prior to "EFI Boot" selection, everything is already installed on the USB stick or internal drive - the "EFI Boot" just works as a sort of filter and uses Apple's native boot.efi to go into macOS. The default volume where to boot, is saved to config.plist file in EFI/Clover/ as "DefaultVolume" key.


In "Hybrid" mode, the codeless automate-eGPU.kext will be always installed on the currently booted disk, regardless of the chosen disk in the installer. In "Pure EFI" mode, only the EFI folder will be generated to the target disk, no other changes. If the target disk in the installer matches currently booted disk, EFI content will be generated to its EFI partition (not visible).

If you choose "Uninstall," the installer deletes automate-eGPU.kext from the currently booted disk and all the generated EFI content from the target disk (including invisible EFI partition, and of course, only EFI app related files).

The installer is made using Apple's pkgbuild and productbuild terminal commands which have restrictions as to multiple pkgs, and therefore this logic may not be the best.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 2 years ago
 

After getting the 1070 to show up in system report (per earlier post), plugging that GPU into main display via DP cable resulted in blank screen. Verified source was set correctly, etc. Not sure if it's my particular brand of 1070 (EVGA) or the driver version defaulted to (106) but something wasn't working there with the standard external display setup. Will try again next build.

I assume recommended process is run the installer, do an Uninstall, then run it again after restart?

Thunderbolt 3 Macs, Sonnet and OWC eGPUs, 4K Displays, etc


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

After getting the 1070 to show up in system report (per earlier post), plugging that GPU into main display via DP cable resulted in blank screen. Verified source was set correctly, etc. Not sure if it's my particular brand of 1070 (EVGA) or the driver version defaulted to (106) but something wasn't working there with the standard external display setup. Will try again next build.

I assume recommended process is run the installer, do an Uninstall, then run it again after restart?

Hybrid or Pure? With hybrid & hot plugged, you need to logout/login or hot plug the monitor at login screen to get eGPU screen output. Automation of this process is under investigation.

The Pure (no hot plugging support) doesn't produce eGPU display output as default due to "safety" reasons (this part of Clover does something with SMC). In order to have eGPU display output in pure EFI mode (not sure about hybrid), you must modify the config.plist key: 

<key>SkipSetupDataForOSX</key>
<true/>

to <false/> as mentioned on the installer's welcome text screen. At your own risk.

Yep, when the new version is released, choose uninstall, reboot, and reinstall.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
ghettocivic
(@ghettocivic)
Active Member
Joined: 1 year ago
 
Posted by: goalque

@ghettocivic Thanks! Which mode? Hybrid or Pure EFI? System restart is required. The installer checks SIP in Hybrid. In Pure EFI, SIP can be enabled during the installation.

I used Hybrid mode and restarted before trying to hot plug but I got kernel panic no matter when I plugged in.  That's when I thought SIP may have not been disabled so I uninstalled (automate-eGPU and nvidia drivers)/disabled SIP/reinstalled and now it works...so now i'm not sure what changed  :mrgreen:

MacBook Pro 13" Late 2013 + Akitio Thunder2 + Sapphire RX570 ITX


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

@ghettocivic Thanks! Which mode? Hybrid or Pure EFI? System restart is required. The installer checks SIP in Hybrid. In Pure EFI, SIP can be enabled during the installation.

I used Hybrid mode and restarted before trying to hot plug but I got kernel panic no matter when I plugged in.  That's when I thought SIP may have not been disabled so I uninstalled (automate-eGPU and nvidia drivers)/disabled SIP/reinstalled and now it works...so now i'm not sure what changed  :mrgreen:

Ok, glad to hear it now works. Best to uninstall before trying the new version. Booting through the normal "Macintosh HD" will cause KP always in Hybrid mode if the Nvidia eGPU is plugged in (due to automate-eGPU.kext). However, you can normally boot through "Macintosh HD" disk without the eGPU.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
ozzy
 ozzy
(@ozzy)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque

Good news! I just tested the hybrid mode on 2011 Mac mini and GTX 980, and it worked on the first run. Gray screen TB1 Macs will get support soon.

Best news all day 🙂

2012 15" Macbook Pro Retina GT650M + [email protected] (AKiTiO Node via TB3->TB2 adapter) + macOS10.13 & Win10


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 3 years ago
 

Was able to get 750M Mac + GTX 1070 + Latest Webdrivers + OpenCL/GL + Metal after some tinkering and following some of @goalque's suggestions. Fortunately, EFI solution can be updated easily to make use of this.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


pengus77 and goalque liked
ReplyQuote
 of  19