Notifications
Clear all

MacOS 10.13.6 Working Nvidia TB3-TB2 Sonnet Breakaway box  

 of  2
  RSS

devild
(@devild)
Trusted Member
Joined: 5 years ago
 

@crmackintosh, have you deletedNVDAEGPUSupport.kext?
If yes,  try next:
boot into macOS w/o the eGPU
hot-plug the eGPU w/o monitor connected to it
hot-plug the monitor to the eGPU
if black screens, press CMD+SHIFT+Q and then Enter/Return - after that you should get a login screen

That is not dead which can eternal lie, And with strange aeons even death may die.


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

Can someone clarify why someone with a TB3 Mac would want to use this path (run, then choose option 2) vs. using goalque's 1.0.4 hybrid option for working with an AMD Mac + NVIDIA eGPU? Best I can tell the reason is, if one uses the goalque hybrid method at it doesn't work, you just have to uninstall it. Whereas with this one you may have to reinstall the entire OS from a backup?

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


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 5 years ago
Builds: 13
 

@chippy-mcchipset If you don't want to boot with an extra drive every time (as I prefer), and not modify EFI bootcamp partition (if destination is boot disk itself). Not tried the latter - is this implemented @goalque? Also, not needing to connect an eGPU to run software is a very important aspect for someone like me - patching is fast as a process. Just enter a command once - make a choice - done. Less effort (with the compromise being system modifications of course).

The rest of this explanation pertains to non-TB3 macs as well.

It is true that the uninstallation code can have bugs - there is no question about that. To counter this, the latest versions of purge-wrangler store a complete backup of all modified kexts - and they are never deleted. Only updated (say when you update the system - you have new kexts from Apple). So it has two options: to uninstall by reversing the patches, or to recover by simply replacing all patched kexts with 'clean' backed up kexts. Even if uninstall fails, recovery is an option that will return the system to the state it was in before running the script. And still won't delete the backup kexts. Backups are taken first before any modifications. Finally, if you have a 750M Mac, you can't use the NVIDIA eGPU with full potential without direct system patches at this time. There is a way to do this in EFI too - but at this time that mechanism isn't working properly (InfoPlistPatch).

In the same vein, one could argue that the backup logic can have bugs. And in that case, the uninstallation logic, which reverses patches, can come to the rescue. The failure occurs when both procedures are bugged - and if that's the case - I'd give up being a programmer haha 😉 - here the user will have to install macOS on top of their existing install.

Overall, the EFI solution is very elegant & the future - I love it, but it can be even better, and I hope to improve on it once the code is open-sourced. Goals include a versatile eGPU application to manage settings, deploy updates, ability to create APFS bootable disks (which we are not sure how to, at this time) etc. All of my gripes I mentioned are solvable in EFI - but it's just not there yet. At the end of the day - what matters is users can choose what they want.

"Desultory reading is delightful, but to be beneficial, our reading must be carefully directed." — Seneca

Author: kryptonitepurge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
Launching Apps on Specific (e)GPUs on macOS
Definitive macOS Thunderbolt eGFX Compatibility Registry

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
CRMackintosh
(@crmackintosh)
Active Member
Joined: 4 years ago
 

@devild I did not delete NVDAEGPUSupport.kext
However, when I ran the purge wrangler I noticed it said it detected a prior version of something and was removing it, but is that not the same thing?

 

How would I manually remove NVDAEGPUSupport.kext ?

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

.

ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 5 years ago
Builds: 13
 

@crmackintosh purge-wrangler does remove NVDAEGPUSupport.kext automatically if detected. To check if it's present, go to /Library/Extensions. Also see the troubleshooting guide in my signature or How-to section of the site, and give EFI solution a go after uninstalling with the script if things still don't work.

"Desultory reading is delightful, but to be beneficial, our reading must be carefully directed." — Seneca

Author: kryptonitepurge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
Launching Apps on Specific (e)GPUs on macOS
Definitive macOS Thunderbolt eGFX Compatibility Registry

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
CRMackintosh
(@crmackintosh)
Active Member
Joined: 4 years ago
 

@mac_editor thanks for that info.  I went to /Library/Extensions and didn't find that file, so I guess it was never there.

I then tried @devild suggestion of:
boot into macOS w/o the eGPU
hot-plug the eGPU w/o monitor connected to it
hot-plug the monitor to the eGPU
if black screens, press CMD+SHIFT+Q and then Enter/Return - after that you should get a login screen

That is exactly what I needed to do to get it to work.  Thank you for the suggestion @devild !

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

.

ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 4 years ago
 
Posted by: mac_editor

@chippy-mcchipset If you don't want to boot with an extra drive every time (as I prefer), and not modify EFI bootcamp partition (if destination is boot disk itself). Not tried the latter - is this implemented @goalque? Also, not needing to connect an eGPU to run software is a very important aspect for someone like me - patching is fast as a process. Just enter a command once - make a choice - done. Less effort (with the compromise being system modifications of course).

 

Thanks for the detailed explanation but re bold items...

For the first one do you mean the option-boot process?  I can understand that being a hang-up for some people. Now trying to understand if once booted, the extra drive needs to remain attached. I don't think so but maybe it must be there for the whole session.

Regarding the boot camp comment not sure what you mean. The hybrid process doesn't involve Boot Camp in any way that I can see (i.e. not required part of the process) but I may be missing something. I've successfully used it now on machines with no Boot Camp aspect to them.

On the last bold part again I may be overlooking something. If I want to use eGPU, I do the hybrid boot process and use it. If I don't need the eGPU I simply boot system normally and use whatever apps I want. Am I missing something / a limitation?

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


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 5 years ago
Builds: 13
 

@chippy-mcchipset The extra drive doesn’t need to be there once booted. But having an extra to boot with is not an optimal thing for me. 
In the installer, you can select the destination disk, right? One typically selects the external USB drive as the destination. But if you select the internal drive itself - bootcamp’s EFI partition is modified (at least goalque had implemented this while making the installer when we discussed it privately - not sure if it’s there now in the release). 
For the last bold item, I meant the installer itself - not other software in general, apologies for being unclear there. These small things really add up for me in due time and I start desiring something much simpler (updates need full uninstall - then reinstall with the EFI Installer). Of course, the easiest thing for me to do would be to create an internal partition myself and install things there, and automate the updates myself - which essentially makes the whole thing a different product entirely haha. 

"Desultory reading is delightful, but to be beneficial, our reading must be carefully directed." — Seneca

Author: kryptonitepurge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
Launching Apps on Specific (e)GPUs on macOS
Definitive macOS Thunderbolt eGFX Compatibility Registry

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
 of  2