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  68
  RSS

goalque
(@goalque)
Noble Member Admin
Joined: 4 years ago
 
Posted by: Riss
Posted by: goalque

@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?

Great thanks! I'll test both Quadro and GTX 780 with my MBP 15" 2014 laptop & Mac mini 2012

You're welcome Smile By the way, @shrapnl's Titan X (Pascal) did work fine with a 13" MBP but for some reason nMP's pci enumeration didn't see the card.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
ghettocivic
(@ghettocivic)
Active Member
Joined: 3 years ago
 
Posted by: goalque
Posted by: Riss
Posted by: goalque

@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?

Great thanks! I'll test both Quadro and GTX 780 with my MBP 15" 2014 laptop & Mac mini 2012

You're welcome Smile By the way, @shrapnl's Titan X (Pascal) did work fine with a 13" MBP but for some reason nMP's pci enumeration didn't see the card.

I would be interested in testing my setup as well with the 750 Ti when this is available

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


ReplyQuote
psonice
(@psonice)
Estimable Member
Joined: 3 years ago
 

@goalque Great to see you got it released Smile Has anyone tried an iMac yet? If not, what's the status there - likely issues, probably ok, or unknown? (I'll try either way, but if it's "likely issues" I'll hold until I have a bit more time to deal with any fallout).

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

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

Unknown. Possible known issues at present (concerns all machines):

-the final stage kext cache rebuilding may yield a kernel panic -> solution: unplug the eGPU during the installation, as soon as it is detected by the installer

- "Default boot entry not found" in the debug log -> solution: do nvram reset and select the macOS as the primary boot disk if Boot Camp installed, and install the EFI on the external USB stick always.

- "Critical software component missing" error message, user error -> solution: do not boot through the normal macOS disk image when the eGPU is plugged in. Always hold down the Option key, and select "EFI boot".

The next version will skip Clover's unreliable DefaultVolume setting, and uses my own method, looping through all volumes and checks the existence of boot.efi.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 

@goalque Maybe for third issue can patch on the fly, some of kext’s Info.plist settings when booted from EFI stick. In default boot it would not be invoked even with eGPU plugged in. Also there might be a way to change string EFI Boot to something else for clarity in one of the links you shared with me privately.

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
Shrapnl
(@shrapnl)
Eminent Member
Joined: 4 years ago
 

Yep, and this same card and enclosure (Sonnet 550) work fine with an Alienware 17" laptop I have.  So the differences are Alienware/nMP and TB3/TB2-3 adaptor and TB2 cable.  Weirdly though the nMP does show the Sonnet 550 enclosure in System Report.  But no card...

2018 MacBook Pro 15" - Sonnet 550 - NVidia Titan X (Pascal)


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

Looks like it's been an eventful few days. Thank you @goalque for all your efforts.

We intend to test the new solutions in the coming days, but it's been a while since I've run any of the scripts here (was waiting for this type of setup / something that might be reasonably stable for recommendation to third parties). Here's my understanding of this new process:

0. No requirements to install any other scripts from this site prior.
1. Launch the installer and install the contents to a Fat 32 USB thumb drive.
2. Make sure the system is cleared of prior NVIDIA script files (i.e. this process doesn't automatically remove anything at any stage).
3. Mount the thumb drive and then option-boot.
4. Choose the EFI or Hybrid installer (Hybrid recommended)
5. When that process is finished, reboot and at the login screen, plug in the eGPU with the NVIDIA card installed.
6. See what happens.

Is that close / am I misunderstanding anything?

Bring peace to your computing life: stop trying to understand Apple.


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

@n9yty, when you say "kernel panic during install", at what stage exactly? In rebuilding kext caches? The system notification pop-up shows the stage. If so, the installer needs to prompt user to unplug the eGPU at the later stage, since the installed kext alone will always cause a kernel panic, if the eGPU is plugged in (didn't happen to me during installation, but very possible). And by the way, I noticed my SD card becomes easily write protected when I slide it in. When you finally succeeded, please turn on the debug log to see where it halts. For example, @lexine reported "Default boot entry not found". Clover's default boot volume logic is fixable.

I believe it was when rebuilding the kernel caches, but I honestly can’t say 100% because I looked away, but that was the last thing I saw.

Pretty sure write protect isn’t an issue, but I will watch it, try again with debug log, and let you know.

Thanks for sharing your great work and time helping us to get it working.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

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

I've uninstalled. 

When I plugged my eGPU in without booting from EFI/USB it caused a system shutdown black screen - ok, not something I would do that regular but the instal has obviously effected something at a system level, however slight, which causes these types of crashes from happening. I also have limited use for an eGPU in MacOS due to running an Ultrafine (headless HDMI is a clumsy faff of a work around IMO).

Will keep an eye on the thread to see how it develops, best of luck guys and thanks again @goalque for your cracking work.

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

 
2017 13" MacBook Pro [7th,2C,U] + RX 5700 XT @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.15.4 & Win10 2004 [build link]  


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

@chippy-mcchipset Exactly.

@n9yty I thought so. You should always unplug the eGPU, just after detected by the installer, during the installation. Otherwise, rebuilding caches may cause a kernel panic, the next version will notify the user.

@eightarmedpet This is normal if the automate-eGPU.kext is still in the kernel cache. Uninstalling (SIP disabled) isn't enough, the system must be rebooted at least once or twice also, without keeping the eGPU plugged in. After that, it should not happen again anymore. If it does, please check that you don't have other solution's kexts in /Library/Extensions/ folder.

EDIT: the "Uninstall" option doesn't uninstall Nvidia web drivers, you have to do it by yourself. With TB3 and Nvidia eGPU (without booting from EFI), it's possible that system will crash anyway if some Nvidia drivers get loaded.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
 of  68