Setup & Software Discussions
[APP] NVIDIA eGPU support for High Sierra (NVIDIAEGPUSupport)
 

[APP] NVIDIA eGPU support for High Sierra (NVIDIAEGPUSupport)  

 of  55
  RSS

jtob
 jtob
(@jtob)
Eminent Member
Joined: 2 years ago
 

@fr34k  I have (mostly) successfully used you're script to upgrade to the newest OS.  Thanks for making things so easy!

Here are the issues I'm facing currently:
Mac Pro (trashcan), 2 eGPU's connected via thunderbolt.  

Startup:
1. if both eGPU's connected, computer will not start
2. if 1 eGPU connected, computer makes it to login screen but sends video out through graphics card video out.  However login screen is black with only a cursor.
3. with no eGPU's connected, startup and login screen are good.  Both eGPU's can be connected at this point and are recognized by the system.

FYI: Using automate-egpu and the -a option I used to be able to boot with one eGPU attached, but not both. 
Ideally the computer should boot with any combination of attached GPU's and there would be an option in the script that allows me to chose which card to send the video out of.  ATM rebooting is a bit of a chore because it requires this whole choreographed ballet of waiting and plugging and waiting more before i can login.

Hopefully this feedback is of some use.

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


fr34k liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@jtob
phew, you haven't encountered any bugs.

It definitely is! Feedback of all sorts (although I hope for success stories) is welcome!
You said "mostly". What exactly did you tweak additionally? Maybe I can incorporate this into the script as well, if it helps.

Did you use any additional parameters (-cudaT ...)?

To be sure: It all works now (though maybe not during boot but after the login, connect, log out and in procedure)?

BTW: I need to do perform this procedure as well.

P.S: I'm currently working on it to add:
-silent mode
-suppress reboot
-more stable uninstall
-new type of error (you may still continue afterwards)
-reshaping paths for easier changes
-prewrite code for next macOS update to get the changes pushed faster...
-suppress licensing question
-rephrasing code for more careful execution

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


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

@iculikemac Ah okay, I understand. Do you know whether it's the GPU or the MOBO firmware that is actually updated?

MacOS: 15" Retina Macbook Pro 2015 Iris Pro only
Windows 10: Tornado F5 laptop with discrete GTX 1060
eGPU: GIGABYTE RX 580


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

@fr34k By "mostly" I was referring to the inability to boot without reconnecting the GPU's.  Also the script didn't seem to load the latest nvidia driver, but its not a big deal since the nvidia control panel took care of that. 

I didn't try any of the script parameters-- I'm not even sure what the different cuda options mean. 

In all its working well.

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@jtob

ah ok...
I'm currently explaining all parameters in the readme on the second branch....
Not installing the latest drivers is in fact intentional. Many seem to have problems with newer ones (including myself).

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


itsage liked
ReplyQuote
imcalledandy
(@imcalledandy)
Estimable Member
Joined: 3 years ago
 

@jtob - I use a Mac Pro (trashcan) with two eGPUs. In Sierra with automate-eGPU -a mode I could leave them both connected and it would work. High Sierra changes things a lot.

My process now is to switch both eGPUs on but do not connect them to the Mac Pro.
Boot. Log in. Log out.
I then move the mouse away from the top left corner - you'll see why in a minute.
Plug both TB cables in AT THE SAME TIME to Bus 2 (the top and and middle right ports). I line them up and push them in at the same time.
Then wait... two eGPUs will take a bit longer to be recognised than one. During this time the mouse may disappear and it may seem like macOS has frozen.
Once both are recognised the screen may flash but you'll get back to the mouse in the top left corner of the screen indicating you can now move it around and log in.
Once logged in, the CUDA warning from System Prefs should not pop up (because you have NVIDIA card(s) present)
Verify the connected cards by going into System Information.
I'm running the latest High Sierra and following this process I have 2 x 980Tis recognised each time.

2013 MacPro 2xD700 [email protected] (AKiTiO Thunder2) + macOS 10.13.3
2017 TB MBP 2xGTX1080Ti-TB3 (Akitio Node) + macOS 10.13.4


itsage liked
ReplyQuote
jtob
 jtob
(@jtob)
Eminent Member
Joined: 2 years ago
 

@imcalledandy -- You have a very similar setup!  What you are describing is my boot procedure also.  It's kind of ridiculous isn't it?  Gone are the days when i could just turn my computer on.
Automate-egpu with the "-a" option comes the closest to solving this issue but it still fails for me when I had two cards attached.  automate must be doing something with the P-Ram to allow the mac to recognize the graphics card, but what, @goalque?

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


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 1 year ago
 

I have a MacPro octacore (trashcan) with two internal AMD Fire Pro 500. I have two external boxes, both with Nvidea GeForce GTX 1080TI. One is a TB2 Bizon Box and another a Sonnet with TB3 (I use a TB3 to TB2 adaptor). I use mostly imcalledandy method. I switch on the computer and let it complete the login. After, I connect both boxes (I do not need to connect both at the same time). One is connected to TB port 4 and another to TB port 5. The TB port 1 is used to connect to a monitor. After I logout and login and everything works just fine. most apps recognize the eGPUs, at least the ones I need. In Agisoft Photoscan, for instance, the processing gain is impressive. Both 1080Ti are used for 86% of the processing calculation while both internal AMD's Fire Pro are only used for the remaining  14%. It seems that apple is having troubles in supporting TB2 in the latest 10.13.4 betas. If so, I will not upgrade anytime soon.

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


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

Hello everybody, just posting here my experience for those who share my same issues.

I have MBP late 2016 (High Sierra 10.13.3) with a Mantiz Venus and a GTX 1080. I followed the guide in the initial post (installing NVIDIASupport) and got my eGPU working attached to an external display (I need to boot with the Mantiz unplugged, login, plugin the Mantiz, logout and login again).
Unfortunately performance with the latest drivers (up to 387.10.10.10.25.161) has been very poor, laggy and slow, with videos from facebook and youtube stuttering, and Chrome tabs switching feeling like running on a Core Duo... I searched a bit the forum here but couldn't find other people mentioning the issue.

Finally I found the same problems described on tonymacx86 in this post, where it is provided the solution of downgrading drivers to 387.10.10.10.25.106 in order to solve performance issue.
The post points to the script by Benjamin Dobell nvidia-update, which automatically install and patches the drivers. I run the terminal command provided on its github:

bash <(curl -s https://raw.githubusercontent.com/Benjamin-Dobell/nvidia-update/master/nvidia-update.sh) <revision>

and the script automatically did everything. After rebooting doing the usual login-plug-logout-login trick, everything run fine and the performance of Chrome and display improved significantly, solving my issues.

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


ReplyQuote
(@william_mcinnis)
New Member
Joined: 1 year ago
 

so i went for broke on this build tell me if anyone has this working: 

Razer Core V2

Macbook pro 13in 2017 (with touch) 

Titan XP

I got it to see the razer core but it does not see the card. This was after i tried automate-egpu. Well I saw this post and the app on this one, Running this gave me power on the external monitor and i could move my mouse over to the screen kinda worked could not move any windows over it was like there was a black overlay. Found a nasty bug when i unplugged the USB-C the mac would kernel panic on me and have to be reset. I am in the process right now of reloading the mac and going to try only the script on this post and see if my results are different. I will post back with my findings if anyone has any insight into how to get the core v2, titan xp, and MBP working i will be your friend for life!

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


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

Thanks for this, it's very helpful. I attached a 1080 Aorus to my MBP Touch Bar that I'm trying to use for rendering. Everything works in Windows, Houdini, Maya, V-Ray, Redshift. All good. I've gone through the steps here to get it working on the Mac, but I'm not sure if I've missed something because the same software is complaining about not finding a suitable device. The GPU seems to show up in OS X, though in System Information it doesn't explicitly identify the GPU:

  Chipset Model: NVIDIA Chip Model
  Type: GPU
  Bus: PCIe
  PCIe Lane Width: x4
  Vendor: NVIDIA (0x10de)
  Device ID: 0x1b80
  Revision ID: 0x00a1
  ROM Revision: preset 1.0.0
  Automatic Graphics Switching: Supported
  gMux Version: 4.0.29 [3.2.8]
  Metal: Supported, feature set macOS GPUFamily1 v3

So I wonder if that's the problem. The CUDA control panels don't complain (as they do on Macs with no GPU, so I feel like it's close. Any thoughts?

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


ReplyQuote
Anchoricex
(@anchoricex)
Trusted Member
Joined: 3 years ago
 

did I shit the bed updating to the 10.13.4 beta as far as nVidia card usage?

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


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

By all accounts, yes. NVIDIA eGPUs are not supported in 10.13.4 currently.

2013 MacPro 2xD700 [email protected] (AKiTiO Thunder2) + macOS 10.13.3
2017 TB MBP 2xGTX1080Ti-TB3 (Akitio Node) + macOS 10.13.4


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

Dear eGPU community,

my goal of the script is to make it as easy as possible for the beginner to get started but also allow pros to customize it to their needs.
To achieve that goal I've, yet again, rewritten the script to incorporate a lot of tweaks.
The parameters that can be given to the script are the following: (Link to post of script) [There is more text at the bottom...]


Parameters

Standard

--install | -i

Default.

Installs software. If not specified otherwise, the script will determine itself what to install. If some software is already installed, it will be updated.

--uninstall | -u

Uninstalls software. If not specified otherwise, the script will try to uninstall the nvidia drivers, the eGPU support and all CUDA installations.

--update | -r

This will try update your drivers, eGPU support and CUDA installations. It will not install new software.


Packages

The parameters in this section will override the deductions on what to install/update/uninstall of the script.

--driver | -d

Nvidia GPU drivers for Mac

--enabler | -e


Tweak to enable eGPU support on the Mac

--cuda | -c


CUDA drivers, will use the standard driver files

--cudaDriver | -v


CUDA drivers, will use the developer driver files (from the toolkit)

Should be identical to --cuda | -c 

--cudaToolkit | -t


CUDA developer toolkit

--cudaSamples | -a


CUDA developer samples

Dependencies:

The dependency graph of the CUDA options is:
Samples -> Toolkit -> Driver
Therefore, installing the toolkit will also install the drivers and uninstalling the drivers will also remove the toolkit. 


Advanced

The parameters in this section will change the behavior of the script.

--forceNewest | -f


Force the newest nvidia drivers and CUDA drivers to be used. This is not recommended. The script will automatically determine the most stable drivers.

Cannot be used with --uninstall | -u.

--minimal | -m


Only tweak the system as little as possible. This may not work in all cases.

--noReboot | -n


Omit the otherwise obligatory reboot at the end of the script.

--silent | -s


Automatically answer every question with yes.

Can only be used in conjunction with --acceptLicenseTerms.

--acceptLicenseTerms


Answer the question of whether to accept the license terms with yes.

--errorContinue


Can only be used in silent mode. If a non fatal error occurs, try to continue by omitting some arguments. Might result in failure.

--errorBreakSilence


Can only be used in silent mode. If a non fatal error occurs, ask user whether to continue. Continuation might result in failure.

--errorStop


Can only be used in silent mode. If a non fatal error occurs, stop the script.


That is quite a lot and I will not be able to test every scenario by myself, so should a parameter combination not work to your liking, please inform me via PM.

Furthermore, I'm trying to compile a list (.plist to be exact) containing apps that require some form of CUDA installation.
If you use one of these, please PM them to me with the exact (case sensitive!) name and the required level of CUDA (driver/developerDriver/toolkit/samples). I will try to incorporate them into the list to make new installations or updates as easy as 1 terminal command and a few minutes worth of time.

And as always: look out for bugs. I've tried the script numerous times but there are parts that I can't reach...

I hope you'll be enjoying eGPU on a Mac even more now...


The parameterless command:

 bash <(curl -s  https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh) 

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


Username, ricc, goalque and 1 people liked
ReplyQuote
(@alphabet73)
Active Member
Joined: 1 year ago
 

@fr34k Unfortunately I'm getting precisely the same behaviours with this new version as I outlined here, with new iMac Pro build 17D2104 and Akitio runningTitan X --

"Boot with eGPU connected: stops boot process at around 60% then stalls permanently

Login then connect eGPU: graphics info gives the builtin Raedon chip plus a generic 'NVidia Chip Model', with apparently default values for all categories. 
The Akitio Node enclosure shows up in the Thunderbolt info, operating at Thunderbolt 3 speed

Login, connect, log out then in again: after logging out frozen on a black screen. When disconnecting there's an instant reboot.

Crash after login, connect, then disconnect: yes, instant reboot."

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@alphabet73
I guess that’s the driver. *4 is still not supplied with NVIDIA drivers...
If I just knew how to code a driver...

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


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

@fr34k Yeah I figured as much. Oh well, looks like I'll just have to be patient, thanks for the help.

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


fr34k liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@alphabet73
First, thank you for thanking me for not fixing the problem 😀
I don’t know when you got your iMac Pro, but have you considered a downgrade to .2 or .3 using Time Machine or a clean install of macOS 10.13.2/.3 without the SU

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


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

For what it's worth, I got mine working. Actually it probably was always working, I just had to do the boot, hot plug, log out, log back in dance. I'm not interested in gaming, but I'm able to use the 1080 GPU for Redshift rendering now which is great. So thanks for that scripts. Very helpful.

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


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

For anyone looking to run TensorFlow 1.6 on an eGPU, this gist might be helpful. Thanks to @ronchigram for pointing out nvidia-update - definitely a reasonable choice until things get stable. 

I should also mention that I managed render my computer unusable twice after installing NVIDIA drivers and then switching back to macOS default graphics because the new NVIDIA drivers were buggy. I don't dare to test it with the older/stable driver version I have installed now, but fortunately there haven't been any noticeable glitches so I don't need to.

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


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

Wow the new script looks impressive. Assuming you have enabled unsigned files and disabled SIP in advance do I understand correctly that it will either:

1) install the support scripts clean and the recommended drivers for the first time? 
or
2) remove any old versions of support scripts and drivers, then install the new ones?

And that at the end you just let it restart and you can start attempting to use the eGPU without further actions?

2016-2018 Macs, Sonnet eGPUs, RX, WX, Vega AMD cards, GTX 1070 and RTX 2080, various 4K displays


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@chippy-mcchipset
1. Thank you!
2. To answer your question: (in short: answer 2)
The script will automatically exit if you haven't configured SIP correctly leaving you with instructions on how to configure SIP in order to work. (completely disabling SIP is treated as incorrect, only --without kext is considered correct)
Installing eGPU Support will always purge your system of other Support techniques first (yes, even after upgrading from or downgrading to macOS Sierra (@goalque's automate-eGPU...), everything is done automatically, to be exact: I didn't code @rastafabi's package into it, this might come if I have a little time on my hand and no-one sends me bugs or a cool new idea to expand the script...).
Installing NVIDIA drivers is handled partially by this script and 
partially by @benjamin-dobell's script. They too are purged before install.
CUDA drivers are a bit special. The script will scan your installed apps and determine what level of CUDA installation is needed and install them accordingly. (I still need help to compile that list so please PM me with the exact case sensitive name of the app and the required CUDA installation (driver/developerDriver/toolkit/samples), thanks!). They too are fully purged before install. ("fully" is ATM incorrect, since I've found plenty of residue after executing the uninstall script which BTW is only installed with the developer drivers which come with the toolkit, but this will change soon since I've already opened a new branch and coded this as well (check that out at the repo); I think it can be merged quite soon).
Back to topic: It is coded that the user can simply copy and paste this bash <(curl -s https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh)  command into the terminal and everything is handled by the script. Most of us can paste it into the terminal right now and it will exit in a few seconds determining that nothing has to be done (yes, it just skips a step if the best solution is already in place). BTW: since I can't determine from the beginning what needs to be done, the warning about the reboot is always present (not with --noReboot | -n obviously) but it will not reboot if nothing that needs a reboot has been done.

My goal was (as I already said) to make it ridiculously easy but also give people that know what they want a tool that can be tailored to their needs. You just need to update your CUDA toolkit ? just slap a -r -t to it, execute and you're good to go. You don't care about CUDA? -m is for you. You work with your Mac and want it to silently execute in the background not disturbing your workflow with a reboot? -s --acceptLicenseTerms -n is for you. You only need the right enabler? -i -e is for you. Lastly, don’t forget that little -u.

To make one point clear. This is NOT a new hack of some sort. It uses the enabler mentioned at the beginning of this thread, other scripts (you can look at the external content used here) it just automates the process involved to get everything up and running.

Closing this answer with a shoutout to everyone making eGPU on a Mac possible. I love the community here because we're all in the same boat until Apple takes things into their own hands but even than this will be great for all sorts of questions and I still think my script will then still make sense.

THANK YOU ALL WHO HAVE MADE THIS POSSIBLE.
fr34k aka learex on GitHub

EDIT:
1. I will merge the second branch tomorrow so then CUDA can be purged from the system. (Unless I find bugs...)
2. With that merging comes support for @rastafabi's package to be uninstalled before any other method is installed. I guess I won't make an install branch so you can choose between automate-eGPU.sh or the enabler. Most of us have upgraded already. I will rather try to keep it up to date so it can be used for as long as possible.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


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

I just can't get this thing to work.  I'm still getting kernel panics.  One thing I noticed this time though was that the NVDAEGPUSupport kext is listed as "not loadable" in my System Information.  I've tried installing it with the computer in both 'csrutil disable' and 'csrutil enable --without kext' modes and neither one works. This is even after I reinstalled macOS.

Screen Shot 2018 03 24 at 7.14.33 PM

edit: It shows as loaded after I ran 'sudo kextutil /Library/Extensions/NVDAEGPUSupport.kext' but I still got the same crash as usual.  Maybe the combination of 2017 MBP + Node + Maxwell (980ti) just doesn't work at all? I don't see anyone in the implementations list who is using both macOS 10.13 *and* a 900 series GPU.

2017 MBP 15, Radeon 560 | Akitio Node + EVGA 980ti FTW


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

Success! 2017 iMac 27 4.2ghz Radeon Pro 580 Akito Node TB3 and Nvidia Geforce GTX 1080TI

Please note, I have not set up the EGPU to drive an external monitor, only for 3d rendering.

Thanks for the help on this site, you guys and gals are amazing!
MTM

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


ReplyQuote
comfycat
(@comfycat)
Trusted Member
Joined: 1 year ago
 

Hey! I'm new here; signed up because Fr34k's script got me really excited to get my Gigabyte Aorus Gaming box working finally on my Macbook 2013 w/ High Sierra (10.13). Unfortunately I get the following error when the script tries to install the enabler:

"No eGPU Support was found for your version of macOS.
This may change in the future, so try again in a few hours."

I'm totally confused. I have High Sierra, and it's exactly 10.13. Am I doing something wrong?
Thank you! Anyone!

You've been warned.
late-2013 13" MBP Retina + [email protected] (Aorus Gaming Box via TB3>TB2 adapter) + macOS10.13.3 & Win10


fr34k and Cikgu Lee liked
ReplyQuote
Oskar Joelsson
(@orrpan)
New Member
Joined: 2 years ago
 

MacBook Air 2011 13" + Akitio Thunder 2 + GTX 560, macos 10.13.3 works with dvi and hdmi displays not vga. Used @fr34k script

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


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

Hi folks, 
I'm having trouble with the egpu support on a 27" 2011 iMac with Akitio Thunder2 with a Nividia 1060 6gb. I'm on 10.13.3 and with the latest NVidia drivers. Disabled SIP and did the installer. Now High Sierra won't boot. It just hangs at the grey loading screen with the apple logo and loading bar. The bar is almost full but at one point just stops.

Tried resetting PRAM, unplugging all cables, reset SMC, booting in safe mode (also hangs on startup)... Now reinstalling High Sierra trough recovery mode.

Any ideas what went wrong? Any solutions?

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


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

Same here!

Like comfycat, I am new here as well.
I too got the same message although it still downloaded the package and installed it.
But did not work.

I am using a 2016 13inch MBP w/ TB with a Aorus gaming box 1080.

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


fr34k liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@comfycat
@cikgu_lee
That is unfortunate to hear, so you may have encountered a bug.

So that I can search for it, may you please send me the full command you executed to run the script.
Additionally, execute the following commands and send me the results you get back:
sw_vers -productVersion

sw_vers -buildVersion
It should definitely not download anything displaying that message...

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


itsage liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@anonomatos
did you disable SIP entirely or only enabled unsigned KEXTs

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


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

Success?  Partially...

This morning I managed to get my setup working with 10.13.3, with just one change that I thought shouldn't make a difference:

I didn't use the VGA (DVI-I->VGA) output on my eGPU.  
That's it! That one change averted the kernel panics I was getting.  I still get them when I shut down the computer, but at least I can use the eGPU now.

There's just one problem though - my main "gaming" monitor is my old widescreen Sony 24" CRT, and I specifically bought the 980ti rather than a newer Pascal GPU because it is the most powerful GPU that I know of that still supports native VGA output.    I even tried a crappy HDMI->VGA converter with the monitor and that worked, but the resolution/refresh rate support on the adapter is terrible.  I also tried my VGA->RGB BNC cable but that also gave me kernel panics just like VGA.

Has anyone else tried outputting video via VGA?  Is this a bug with the NVDAEGPUSupport.kext, the nvidia driver, or macOS itself?

2017 MBP 15, Radeon 560 | Akitio Node + EVGA 980ti FTW


fr34k liked
ReplyQuote
anonomatos
(@anonomatos)
Active Member
Joined: 1 year ago
 

@fr34k: I disabled it entirely. Should I only have enabled unsigned kexts?

On a sidenote... I didn't use your script, fr34k. I used the devild v7 one. I am reverting from a time machine backup and will try your script. Is it best to uninstall first? Or is an overwrite just as good?

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@anonomatos

My script will not work if you disabled SIP entirely only with csrutil enable --without kext.

From most people I spoke with, they reported that the custom SIP setting works more often (for me e.g. it does, with SIP disabled it does not).
This does not mean though, that it will work!

My script is written so that normally a separate uninstall is unnecessary. Every time new or updated software will be installed the old software is going to get removed first.
In your case, I would however, since you already installed it with different SIP setting (and I guess you installed everything correctly and so the script basically would not change anything) first execute:
bash <(curl -s https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh) -u
which will uninstall the enabler, the drivers and CUDA, if installed respectively.
Then after the automatic reboot has been performed run the script without any additional parameters:
bash <(curl -s https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh)

I hope this will work.
P.S: I did say first uninstall, reboot then install, because this seems to have less trap doors which might cost you unnecessary time...

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
comfycat
(@comfycat)
Trusted Member
Joined: 1 year ago
 

Thanks for the reply @fr34k! I disabled the SIP partially, the way you're suggesting, --without kext. Your script won't run in the state produced by "csrutil disable", but this is required for the package from the OP, so I've tried it both ways by accident. Been switching back and forth a lot today!

The command I used to launch your script was:

bash <(curl -s  https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh) 

I also tried some of the modifiers you listed, particularly "--enabler" and "--uninstall". I know I tried a few others. Like @cikgu_lee was saying, it ran without any modifiers, downloaded drivers and installed them, maybe did some other stuff but in the end it says the drivers installed, and the eGPU enabler failed. Trying to install just the enabler (after a full install fails, but before any uninstall process) produces the error message I posted earlier, about incorrect macOS.

And my product version is: 10.13.3 (I updated since my earlier post to see if this made a difference), and my build version is 17D47.

Any ideas? It was looking so easy...

You've been warned.
late-2013 13" MBP Retina + [email protected] (Aorus Gaming Box via TB3>TB2 adapter) + macOS10.13.3 & Win10


ReplyQuote
(@hamaad_shah)
New Member
Joined: 1 year ago
 

Hi All,

The NVIDIA eGPU support here

 https://egpu.io/wp-content/uploads/wpforo/attachments/71/4587-NVDAEGPUSupport-v7.zip 

is superb!

Everything is working well using a GTX 1070 eGPU on a MacBook Pro on High Sierra. I've collected all the steps I did here in this GitHub gist of mine: 

https://gist.github.com/hamaadshah/43b2a050112b8a3633f9db4616075c11

May I ask if the 4587-NVDAEGPUSupport-v7.zip is open source, i.e., free for commercial use. Or is it just available for personal use.

Many thanks,

Hamaad.

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@comfycat

please give me about 6h.
I will try to fix this bug.
I will notify you once I've updated the script.

The package in the opening post can also be run in the custom SIP state. It does need to be disabled entirely!

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + GTX1080Ti@32Gbps-TB3 (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
 of  55