MacOS 10.13.6 Working Nvidia TB3-TB2 Sonnet Breakaway box  

  RSS

(@allie_b)
Active Member
Joined: 6 months ago
Posts: 7
July 10, 2018 9:07 am  

Just want to confirm that I have successfully gotten my Nvidia setup to work with MacOS HS 10.13.6

1. Installed Update -> 10.13.6
2. Installed Nvidia driver update -> 387.10.10.10.40.105
3. Went to Github and ran purge wrangler Step 2 in terminal and Reran Nvidia patch.
4. Rebooted and everything worked.

Noticed improvements:

- When starting to watch a youtube video, video does not reload a first time before starting to play
- Performance overall feels smoother when navigating MacOS

Problems still Remain:

- Netflix and similar streaming sites still don't work and end up with an error when trying to watch something.

Comment on how you guys are experiencing .6 below!

Macbook Pro Mid 2014 (Iris Pro only) + Sonnet TB3 Breakaway-box 350w + Apple TB3 -> TB2 Converter + MSI 1070ti + Samsung U28E590D 4K


theitsage liked
ReplyQuote
swithdrawn
(@swithdrawn)
Active Member
Joined: 6 months ago
Posts: 5
July 10, 2018 11:42 pm  

I updated my nMP + Nvidia 1080 Ti as well. 

About halfway through the update I lost signal... I was using a miniDP -> HDMI cable running out of the Mac Pro. This update broke my ability to use the HDMI input on my monitor when using the internal D300's... there's signal, just black. Weird. miniDP -> DP cable works fine. 

I was able to Remote Desktop in and install purge-wrangler + Nvidia drivers after the update. 

I'm noticing a slight FPS performance improvement in Premier Pro with the UI/video playback.

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


ReplyQuote
CRMackintosh
(@crmackintosh)
Active Member
Joined: 9 months ago
Posts: 10
July 10, 2018 11:58 pm  

Hey Albert, thanks for posting your success.  I have a similar setup - Late 2013 nMP, Sonnet Breakaway Box with a 1080Ti card.

I've been successfully working under 10.13.3 and have been nervous to upgrade the OS.  Today I thought I might try going to 10.13.6, but I haven't yet had experience with step 3 that you described: Github purge, etc.  
Can you point me to a walkthrough that explains that process?  I'd greatly appreciate the guidance before I get started!

Thanks - 

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


ReplyQuote
CRMackintosh
(@crmackintosh)
Active Member
Joined: 9 months ago
Posts: 10
July 11, 2018 12:10 am  

more specifically, in your described Step 3, what version of the Nvidia patch did you re-run? 
NVDAEGPUSupport-v9.zip
That seems to be the latest version I can find, but it says it's for 10.13.4 (not .6 for instance - maybe it doesn't matter?)

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


ReplyQuote
devild
(@devild)
Trusted Member
Joined: 2 years ago
Posts: 66
July 11, 2018 7:50 am  

@crmackintosh, NVDAEGPUSupport.kext is not required anymore for 10.13.4+ with purge-wrangler script from @mac_editor.

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


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1808
July 11, 2018 7:56 am  

@albert_johannes , pls submit a build using the following template so we have your success on file:

https://egpu.io/forums/builds/build-template/

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2015 15" Dell Precision 7510 M1000M + macOS 10.14 & Win10


ReplyQuote
runcoach
(@runcoach)
New Member
Joined: 6 months ago
Posts: 3
July 11, 2018 7:07 pm  

For what it is worth, I just got a Sonnet eGFX Breakaway Box Model 350 with a AMD Radeon RX 580 8Gb connected to my Late 2013 Mac Pro Quad Core running Mac OS X 10.13.5 and it appears fine so far.  Issue now is to get applications taking advantage of it.  How can I benchmark it properly?  Cinebench R15 only tests one of the internal FirePro D300 and not both and I cannot find out how to test the RX 580.  I purchased from Bizon and used their eGPU patch to get it all going.  I am using an AMD card whereas you are using an Nvidia card.  Good luck!

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


ReplyQuote
devild
(@devild)
Trusted Member
Joined: 2 years ago
Posts: 66
July 11, 2018 7:37 pm  

@runcoach, connect your monitor to the RX580 and Cinebench will use the card.
p.s.: Bizon, most probably, uses the @mac_editor script because there are no other options.

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


ReplyQuote
runcoach
(@runcoach)
New Member
Joined: 6 months ago
Posts: 3
July 11, 2018 7:57 pm  

Thanks, it worked on the benchmark.  Now to test some more...

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


ReplyQuote
CRMackintosh
(@crmackintosh)
Active Member
Joined: 9 months ago
Posts: 10
July 11, 2018 11:55 pm  

@devild okay, I just did the purge-wrangler thing and now my eGPU isn't working.

When it was working in 10.13.3 I had to leave the eGPU unplugged during startup, then login in, plug it in, logout, and then login again and things would work.
However, now if I go through the same process, when I logout after plugging in the eGPU, I get a black screen and can't do anything.

So... must need to do something more than the steps outlined above.

Again, the steps I took were:
1. Installed Update -> 10.13.6
2. Installed Nvidia driver update -> 387.10.10.10.40.105
3. Went to Github and ran purge wrangler Step 2 in terminal
4. Rebooted and nothing worked.

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


ReplyQuote
devild
(@devild)
Trusted Member
Joined: 2 years ago
Posts: 66
July 12, 2018 7:34 am  

@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: 1 year ago
Posts: 296
July 12, 2018 4:36 pm  

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?

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1497
July 12, 2018 5:17 pm  

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

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
CRMackintosh
(@crmackintosh)
Active Member
Joined: 9 months ago
Posts: 10
July 12, 2018 5:35 pm  

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

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1497
July 12, 2018 5:39 pm  

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

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
CRMackintosh
(@crmackintosh)
Active Member
Joined: 9 months ago
Posts: 10
July 12, 2018 5:48 pm  

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

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


mac_editor liked
ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 1 year ago
Posts: 296
July 12, 2018 6:04 pm  
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?

I have yet to list my system & eGPU hardware or link a build guide in my signature. I will do so soon to give context to my posts.


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1497
July 12, 2018 6:12 pm  

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

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote