[SCRIPT] fr34k's macOS-eGPU.sh - one script, all solutions, fully automated
 
Notifications
Clear all

[SCRIPT] fr34k's macOS-eGPU.sh - one script, all solutions, fully automated  

 of  21
  RSS

ohsoweird
(@ohsoweird)
Active Member
Joined: 3 years ago
 
Posted by: fr34k

@ohsoweird
Uhm, did you run my script or @goalque's instructions (on install). It might be that no backup exists and therefore you must upgrade to 17E202 to get the new wangler.

I used your script only. So upgrading to 17E202 would be the way to go? I have avoided this due to earlier issues with updates, but should be fine now yes?
Many thanks!

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
 

@rmara
OK, I can therefore conclude that you used my temporary script. You will have to call the install script. If it does not work, you must reinstall macOS. (Again: there is no need to delete all files, just reinstall macOS)


@ikir
ah one problem might be your dGPU...
I haven't implemented yet all possible options for NVIDIA dGPUs or thunderbolt issues.


@artemus80_j_
PP should see a boost in export. Yes for live rendering an eM is required. Even then ti might not work. I don't know how PP handles footage internally.


@mzo
just run the script. It will automatically exit with a message if the patch has not been removed.


@ohsoweird et al
if you execute my script with the --checkSystem parameter it will output you the current wrangler version, this must obviously match with your current os build number:
e.g. -> AGW version [10.13.4:17E202]

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)


ikir liked
ReplyQuote
ikir
 ikir
(@ikir)
Prominent Member
Joined: 3 years ago
 

@freak
if you need some testing just tell me while I have this machine (I need to sell it, it is not mine)


MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD
my awesome Radeon VII eGPU
my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64


ReplyQuote
ohsoweird
(@ohsoweird)
Active Member
Joined: 3 years ago
 

@fr34k
Updated to 17E202 and ran script, works almost perfect on iMac 2017 27" with Akitio Node Pro and GTX1080ti.
eGPU can only be powered on when at login window or already logged in. When powered at login window the identifier also shows correct GPU model, otherwise reports "null".

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


goalque and fr34k liked
ReplyQuote
(@livesoak)
New Member
Joined: 2 years ago
 

Hey. I just installed the script and when I try and use my eGPU my laptop screen stops displaying (still backlit though) and my main monitor displays picture but it completely unusable. It is ridiculously slow. The entire OS is lagging like crazy. I had this same problem with the temporary fix script (well not when i first installed it, it worked perfectly, but then I accidentally installed the security patch and I had this exact same problem)

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
 

@livesoak
try 
hot plug instead of booting with eGPU

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
Technomad
(@technomad)
Eminent Member
Joined: 2 years ago
 

Installed using the script: the script downgraded the Nvidia drivers to 103 (from 107), otherwise everything went fine. GTX1080ti shows up properly and benchmarks ran OK for CUDA, but very slowly for OpenCL & Metal. 

However, the OS X UI slowed down to the point of unusability: lots of of SBOD and 30-40seconds between clickable actions. I upgraded the Nvidia driver back to 107 and that brought the OpenCL & Metal benchmarks back to what they should be, but made no difference to the UI.

So I've disconnected the Core v2 pending being able to resolve that - any ideas here?

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


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

@technomad
see above

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
Technomad
(@technomad)
Eminent Member
Joined: 2 years ago
 

Interesting: hot plugging activates the built-in screen, not the external monitor. System preferences show that the GTX is being used by both monitors, but the external one won't fire up.

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


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

@fr34k @Technomad exact same thing happening to me. I have my external set as default so it won't even let me login if I try booting up w/out it then plugging it in cause my login details display to the main monitor. haven't tried changing it around yet

also hot-unplugging (is that even a thing) it restarts my comp. is that normal?

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
 

@technomad
and after hot-plug a log out?
Try the steps under known issues...


@livesoak
hot
unplug -> kernel panic -> don't do that!

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
mellowwood
(@mellowwood)
Active Member
Joined: 2 years ago
 

Hi All,

I just want to thank fr34k and everybody else involved. I installed 10.13.4 on an external USB to test eGPU script and everything went buttery smooth. Im using a late 2013 MBP with the 750m 2GB chipset and an Akitio Thunderbolt 2 with nVidia GTX 1060 3GB.

Everything works with very few screen glitches. I have attached screenshots below of my setup with the screen arifacts  in some icons. 

Cant wait for new Nvidia drivers to have OpenGL support for gaming. 

Again THANK YOU SO MUCH FOR ALL THE EFFORT! 

Kind regards,
Mellowwood

Screen Shot 2018 05 07 at 18.26.07
Screen Shot 2018 05 07 at 17.57.39
Screen Shot 2018 05 07 at 17.57.26
Screen Shot 2018 05 07 at 17.55.28
Screen Shot 2018 05 07 at 17.55.04
Screen Shot 2018 05 07 at 17.54.42

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


fr34k liked
ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 3 years ago
 

Anyone with 2014 or earlier Macbook with NVidia dGPU + Akitio Thunder 2 + NVidia EGPU reported success with the new script?

If yes, care to share if you faced any difficulty and how you dealt with it?

@fr34k,  When I get time I'll restore the 13.4 Timemachine backup and use the checkSystem option (after removing the EGPUSupport kext)... Do you think that might be helpful to diagnose?

Cheers!

Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970


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

@fr34k Suggestion: Put a change log on that first post for any major changes (i.e. fixes for major issues). This thread will probably end up 30+ pages, trying to find out if a problem has been solved can become a nightmare Smile

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


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

@mellowwood I thought 2013 15" 750M was doomed to failure due to overlapping Nvidia drivers (native + web). Does OpenGL/OpenCL work?

Are there any differences between Iris Pro vs 750M driving your internal display?

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


LeoLeal liked
ReplyQuote
(@andreas_deleuran_nielsen)
Active Member
Joined: 2 years ago
 

Okay, so I tried running the script on a fresh macOS install.
To start out with it looked like it worked. I tried plugging in the eGPU after the script forced the reboot.
I got the "Disconnect "Null"" message and there was no output to my external monitor.
(didn't check if it was only a visual bug and that it might've still accelerated some apps)
Tried doing the same thing again (reboot and then plugging eGPU) - Same thing.

But now it doesn't do anything, if I try plugging in the eGPU (before or after booting/hotplugging) it just gives me kernel panic.
What could cause this, is anyone else experiencing this?

mid-2014 MacBook Pro 15" retina with Iris Pro Graphics - MacOS 10.13.4 High Sierra (17E202) - AKiTio Thunder2 PCIe Box - Zotac Geforce GTX 1050ti 4GB mini


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

@goalque 

I don't think OpenGL/OpenCL is working, I'm not sure how to test it, but I tried a Heavan benchmark but it seems to be using either the Iris Pro or the 2GB 750m as I get very low FPS.    I will be happy to run any tests and send feedback if you can guide me how to go about doing it.

Regarding the 750m and Iris Pro, I disabled the automatic gpu switching in Energy Saver under preferences, and there was no issues, but it reactivates every time I reboot, so assuming the switching is working fine as well.   

Screen Shot 2018 05 07 at 19.06.08
Screen Shot 2018 05 07 at 19.05.59
Screen Shot 2018 05 07 at 19.05.52

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
 
Posted by: Artemus80 J.

Anyone here is using eGPU strictly for creative purposes not gaming nor external display.  If so, how has it been working for you?
I will be using it for premiere, After effects (element 3D and cinema 4D if my installation is a successful one.  Wish me luck Smile

iMac (Retina 5K, 27-inch, Late 2015)
4.0GHz quad-core Intel Core i7

None of Adobe's applications have built-in support for eGPU yet. You may see some evidence that the app "Sees" the eGPU but so far all reports I've read and all tests I've attempted indicate we'll have to wait for Adobe to update the suite before we'll see the real benefits of eGPU. Not sure about Element 3D. In general I'm not aware of any plugins which have advertised eGPU support. Possibly the recent updates from Red Giant include eGPU support?

You should visit the Applications forum on this board for more specific (app by app) info but very few creative apps are currently set up on Mac to use eGPU. DaVinci Resolve is the best option right now for anything video-related.

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


goalque and itsage liked
ReplyQuote
Charly4
(@charly4)
Eminent Member
Joined: 3 years ago
 
Posted by: mellowwood

@goalque 

I don't think OpenGL/OpenCL is working, I'm not sure how to test it, but I tried a Heavan benchmark but it seems to be using either the Iris Pro or the 2GB 750m as I get very low FPS.    I will be happy to run any tests and send feedback if you can guide me how to go about doing it.

Regarding the 750m and Iris Pro, I disabled the automatic gpu switching in Energy Saver under preferences, and there was no issues, but it reactivates every time I reboot, so assuming the switching is working fine as well.   

Screen Shot 2018 05 07 at 19.06.08
Screen Shot 2018 05 07 at 19.05.59
Screen Shot 2018 05 07 at 19.05.52

You are having exactly the same issues than me, including the problems with some transparencies... Probably all of us with nvidia dGPU are having the same problems.

To know if your eGPU is working or not goto Applications -> Utilities -> Activity Monitor and then in window select GPU History, then when execute Heaven you'll see that dEPU is at 100% and the eGPU is more and less at 10% so is not rendering the bechmarck.

 And also you can try to execute any game, sure that a mesage appear saying that the card is not compatible or something similar

Captura de pantalla 2018 04 14 a las 20.37.22

Macbook PRO Retina 2012 15" (Intel HD 4000 + Nvidia Geforce GT 650M)
Akitio Thunder 2 + Nvidia 970 GTX


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

None of Adobe's applications have built-in support for eGPU yet. You may see some evidence that the app "Sees" the eGPU but so far all reports I've read and all tests I've attempted indicate we'll have to wait for Adobe to update the suite before we'll see the real benefits of eGPU. Not sure about Element 3D. In general I'm not aware of any plugins which have advertised eGPU support. Possibly the recent updates from Red Giant include eGPU support?

You should visit the Applications forum on this board for more specific (app by app) info but very few creative apps are currently set up on Mac to use eGPU. DaVinci Resolve is the best option right now for anything video-related.

Impatient people can fool apps to think that eGPU is the only GPU in your system. If developers do nothing, we need more workarounds 😀

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


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

Today's release of 10.13.5 b4 got me thinking about this script. Once it's in a non-alpha form, will it be the case each new Apple update requires a script update?

Secondarily, through four betas now I haven't seen anything that suggests additional eGPU support / fixes in this OS version... have you guys seen anything different? Apple may be waiting till WWDC to fill us in on what they intend to do next, if anything.

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


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

None of Adobe's applications have built-in support for eGPU yet. You may see some evidence that the app "Sees" the eGPU but so far all reports I've read and all tests I've attempted indicate we'll have to wait for Adobe to update the suite before we'll see the real benefits of eGPU. Not sure about Element 3D. In general I'm not aware of any plugins which have advertised eGPU support. Possibly the recent updates from Red Giant include eGPU support?

You should visit the Applications forum on this board for more specific (app by app) info but very few creative apps are currently set up on Mac to use eGPU. DaVinci Resolve is the best option right now for anything video-related.

Impatient people can fool apps to think that eGPU is the only GPU in your system. If developers do nothing, we need more workarounds Grin

That's true but you'd have to be pretty impatient to use headless adapter tricks to accelerate a true production workflow. Smile

In your experience are those workarounds stable enough across a range of adapter brands (on 10.13.4) that you could recommend them for someone in a real-world production workflow?  To me it would depend on the person and project.  From what I've seen, I don't think I'd recommend it for anyone other than freelance artists who are not involved in big budget projects / have some leeway to experiment a bit.

But your point about developers doing nothing is key; we all need to pressure all of our favorite developers (by writing them directly and asking on their social feeds to get onboard ASAP). They should be able to add support in many cases without a major update. Think 1.1 vs. 2.0. If they don't get a lot of people asking, they'll do nothing. And native support is going to be far better for everyone than applying hacks.

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


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

@psonice
done and done! Currently there was only the --checkSystem update so I made this one v0.1 alpha ...
bugfixes won't get a new version (maybe 0.11 alpha)
major updates get the .1 up
and once 10.14 arrives we've reached 1.0

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
LeoLeal
(@leoleal)
Eminent Member
Joined: 3 years ago
 
Posted by: goalque

@mellowwood I thought 2013 15" 750M was doomed to failure due to overlapping Nvidia drivers (native + web). Does OpenGL/OpenCL work?

Are there any differences between Iris Pro vs 750M driving your internal display?

@goalque Oddly enough, I am also running a Late 2013 with NVidia dGPU + Nvidia eGPU and It's working well on 13.3. I'd like to hear more from you, that have close to infinite more knowledge on this, about how 13.4 drivers work that makes this setup a doomed one. Wouldn't the NVidia Driver take over control of both cards just like in Windows and work just as normal?

@mellowwood did you try using the disable nvidia dgpu option of the script? Can you share your full experience installing your eGPU. I have a very close configuration. Late 2013 + Akitio Thunder 2 + Zotac 970GTX and I am experiencing Black internal screen (nothing plugged in) right after script reboots. I just didnt try this option and when i get time Ill restore 13.4 backup to read the checkSystem output and see if any clues arise.

Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970


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

@LeoLeal

No, i just used the terminal commands posted, from a new MacOs installation on an external USB drive, i use  for testing purposes. Im hesitant to upgrade to 10.13.4 as my 10.13.3 is still working perfect with openGL support for gaming.    I do have a "disable laptop monitor app" running which i activate when i game and i did install that on the new 10.13.4 to test.               

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


ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 3 years ago
 

My Setup is plugged since power on and It's working fine in 13.3. It is running beautifully. But 13.4 gets a black screen even without the eGPU plugged.

Macbook Pro Late 2013 (dGPU GT 750m) + Akitio Thunder 2 + GTX 970


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

That's true but you'd have to be pretty impatient to use headless adapter tricks to accelerate a true production workflow. Smile

In your experience are those workarounds stable enough across a range of adapter brands (on 10.13.4) that you could recommend them for someone in a real-world production workflow?  To me it would depend on the person and project.  From what I've seen, I don't think I'd recommend it for anyone other than freelance artists who are not involved in big budget projects / have some leeway to experiment a bit.

But your point about developers doing nothing is key; we all need to pressure all of our favorite developers (by writing them directly and asking on their social feeds to get onboard ASAP). They should be able to add support in many cases without a major update. Think 1.1 vs. 2.0. If they don't get a lot of people asking, they'll do nothing. And native support is going to be far better for everyone than applying hacks.

Headless adapters or isHeadless booleans Smile As said, these are workarounds. By definition, not recommended for any serious production use. Another key is that Apple promised Metal support across all GPUs (from AMD, Intel, Nvidia) in WWDC 2016. Metal 2 brought external GPU support and a new property that determines whether or not a GPU is external GPU, removable. This property is defined also in Nvidia's drivers but I am afraid it is just a plain struct, without any implementation.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


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

That's true but you'd have to be pretty impatient to use headless adapter tricks to accelerate a true production workflow. Smile

In your experience are those workarounds stable enough across a range of adapter brands (on 10.13.4) that you could recommend them for someone in a real-world production workflow?  To me it would depend on the person and project.  From what I've seen, I don't think I'd recommend it for anyone other than freelance artists who are not involved in big budget projects / have some leeway to experiment a bit.

But your point about developers doing nothing is key; we all need to pressure all of our favorite developers (by writing them directly and asking on their social feeds to get onboard ASAP). They should be able to add support in many cases without a major update. Think 1.1 vs. 2.0. If they don't get a lot of people asking, they'll do nothing. And native support is going to be far better for everyone than applying hacks.

Headless adapters or isHeadless booleans Smile As said, these are workarounds. By definition, not recommended for any serious production use. Another key is that Apple promised Metal support across all GPUs (from AMD, Intel, Nvidia) in WWDC 2016. Metal 2 brought external GPU support and a new property that determines whether or not a GPU is external GPU, removable. This property is defined also in Nvidia's drivers but I am afraid it is just a plain struct, without any implementation.

Good point regarding the Metal angle and Apple's part in continuing to build this part of the platform. Unfortunately Apple will probably do whatever it's going to do without respect to customer feedback for the first couple years. For example it took a lot of bashing and gnashing of teeth by industry pros (not just every day consumer-level users) to get them to admit to a failure and recommit to redesign with 2013 Mac Pro design (roughly 4 years worth). So whatever pressure and visibility we put on third party app developers it will have to be double that for Apple, and more frustrating along the way because they'll never comment on whether they've "heard us" or plan to implement anything or not.

Maybe we'll get some insight at WWDC and they'll tell us what they intend with... Metal 2.x / 3?

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


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

@goalque Oddly enough, I am also running a Late 2013 with NVidia dGPU + Nvidia eGPU and It's working well on 13.3. I'd like to hear more from you, that have close to infinite more knowledge on this, about how 13.4 drivers work that makes this setup a doomed one. Wouldn't the NVidia Driver take over control of both cards just like in Windows and work just as normal?

 The problem is that Nvidia's web drivers are not designed with eGPUs in mind. The release notes say:

"Includes BETA support for iMac and MacBook Pro systems with NVIDIA graphics".

Unfortunately.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


LeoLeal liked
ReplyQuote
phenotype
(@phenotype)
New Member
Joined: 2 years ago
 

Many thanks to @goalque and @fr34k and everyone else that has helped.

I'm up and running on a 2017 Macbook Pro 13" Non-Touch Bar + Mantiz Venus and EVGA 1080Ti FTW3.  

Some tips.

  • Run the scripts ONLY with Terminal.app.   If you happen to be in love with iTerm.   Temporarily suspend your affection, because the script will quit it as part of the "closing all open applications" portion.   This is hella confusing until you try it under Terminal.app.   Smile
  • If you've tinkered with some timid installs, but nothing full blown - then this sequence worked for me on the 13" Macbook Pro without a dGPU.. 
    1. Disconnect EGPU and don't touch it until asked.  Smile
    2. Disable SIP fully via Recovery. 
    3. Reboot into Mac OS.
    4. Run the 3.0.0 script with the --uninstall option first.
    5. Reboot.
    6. Run the 3.0.0 script with the --install option. 
    7. Plug in EGPU when asked by the script.   Disconnect EGPU when asked by the script. 
    8. Reboot.
    9. After OS has loaded, plug in EGPU.    EGPU will show a single option, Disconnect "null".   Don't touch it or do anything, just observe it.
    10. Reboot.
    11. The laptop will get 1/2 way through the boot progress bar, then move itself to the first of N number of attached monitors.
    12. You are now golden. 
    13. You can safely update to the latest Nvidia drivers - it will prompt you.
  • For Bootcamp on Windows 10 Pro
    1. Ok - this is crazy - just leave everything attached and reboot holding option into Windows.  
    2. Everything will work and display on the attached monitors
    3. Install Nvidia Experience and game ready drivers.   It will remove something called an Nvidia Container Driver(?), will flicker and freak out for a bit.   But all will be well afterwards.
    4. Reboot Windows 10 and lose your mind when Steam and Origin both work.
  • If you happen to have a TB3 audio interface such as the Lynx Aurora 16 with LSLOT.   Do not unplug it from your dock setup while running the EGPU.   You will crash hard - black screen with internationalized bad-things-just-happened notification.   Doesn't appear lasting damage will occur to anything though.
  • So moral of story is just boot and shutdown with everything attached after the above config.   Hot plugging and unplugging just seem to be bad news.   Given how fast everything boots, this isn't any inconvenience.
  • Can't figure out how to upload my screenshots, but will update soon as soon as I figure out how.  Smile   Thanks again guys!

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


fr34k and lars18th liked
ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 2 years ago
 

1. Hot plug + logout works fine. I now have the internal display on the Intel HD 630 iGPU and the external screen on the GTX1080ti.
2. Sleep/wake ah, doesn't, and hot unplug causes kernel panic. Any fixes for these?
3. under Nvidia driver .103, OpenCL doesn't appear to accelerate (GB4 benchmarks at around 34000). If I update to .107, it benchmarks around 186500, which is more like it).

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


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

OpenCL and CUDA are working fine on my machine. Blender and Agisoft Photoscan can use both Cuda and OpenCL and in both cases the speed increase it's outstanding. you can test OpenCL performance in your machine using Luxmark (A small benchmark application).

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


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

So I just wanted to add my experience with this script if anyone has a setup like mine. My setup is:

Mid 2011 Mac Mini i5
Intel HD Graphics 3000 512MB
AMD Radeon HD 6630M 256MB
macOS 10.3.4

Aorus Gaming Enclosure
w/ NVIDIA GeForce GTX 1060 6GB SC

Naturally, I've been following the eGPU thing for a while and even tried it with some of the scripts that had been out for a while. In all instances, attempting to run this setup with an eGPU failed, kernel panic when booted. I read up on the issue being the Radeon 6630M and that a 2011 Mac Mini without that dGPU was the way to go. Then, this script came along and I decided to give it a shot again. Wouldn't you know, it worked! Well, black screen at first but a restart resolved it. 

First thing I noticed was that when booted to the desktop, my computer was slow and activity monitor showed a lot of activity. This caused the internal fan to be high for a good long while. Once it settled, everything ran great. I have a Samsung TV connected to the HDMI port of the eGPU. The computer uses the Apple Thunder 3 -> 2 adapter to plug to the eGPU. 

The second thing I noticed was my Intel HD Graphics 3000 was no longer "seen" in System Report under Graphics/Displays. It only showed the AMD Radeon 6630M and the NVIDIA GeForce GTX 1060. I ran into an issue when I attempted to Disconnect the eGPU using the menubar icon and it crashed. I restarted and the Aorus Enclosure was not seen anymore, no matter how many time I disconnected it and reconnected or restarted the Mac Mini. After a few installs and reinstalls (there were several), I was able to get it back to work. But in that time, even after installing the script, the integrated card never appeared again (still hasn't).

For all intent and purposes, the script works great and I've ran a few things and haven't really ran into any other issues. The computer starts up with the eGPU when restarted, and it also starts up with the Radeon when the eGPU is disconnected. Not really looking forward to a reinstall to try to get the integrated Intel Graphics back as it currently works, but maybe some of these issues will be resolved down the line.

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


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

hi 
What I do,'t understand is that i used the script you suggested for 10.13.4 17E202 with the link provided on this thread, not from the previous thread. is there another newer script than the one on first page of th of this thread : "SCRIPT] fr34k's macOS-eGPU.sh - one script, all solutions, fully automated"  ?

I'm using a macbook pro early 2011, an akitio node, and a nvidia 1080ti...

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


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

Quick summary: Current script got me CUDA working (what I mainly need), but external displays not working as well as the 10.13.3 NVDAEGPUSupport. 

Semi-new user here, I had no problem with the 10.13.3 nVidia EGPU enabler. Trying out the 0.1 alpha script on 10.13.4  this evening with this hardware:
- 2017 Retina 27" iMac with AMD Radeon Pro 580 8GB onboard
- Gigabyte Aorus GTX 1080 Gaming Box 8GB
Under 10.13.3 the GTX 1080 was driving two external monitors:
- Cinema HD 30" display (10 year old dual-link DVI beast)
- Dell U2414H HD monitor (via HDMI)
Previously these monitors had been connected thru Apple TB3 HDMI adapter, and a Apple Dual-Link DVI to mini DisplayPort adapter via:
- OWC Thunderbolt3 Dock (disconnected during install)

With the 10.13.3 kext workaround, I had no problem driving the two outboard monitors from the gaming box. Usual startup sequence of start with eGPU disconnected, connect at login screen or log out/in. 

Starting from a pretty stock 10.13.4 plus security patch (17E202): 
Ran the script after recovery-mode csrutil disable, on the reboot I went back to csrutil enable --without kext. I don't expect that's significant, though from reading the script and forum traffic I'm assuming this is a binary patch of AppleGPUWrangler kext, plus another one for NVDAEGPUSupport maybe (or maybe just a new version). 

- Connecting the gaming box at login prompt, I get the expected properly labeled Disconnect menu item after login.
- CUDA works (which all  I technically need) according to CUDA-Z, but driving external displays is inconsistent at best. 
- For the initial test I thought I had everything working, with Cinema running off the eGPU, but that was short-lived once I oops'ed and connected the Dell via both the Dock (mDP) and the eGPU (HDMI) and  confused the poor thing into thinking there were four screens. 
- Primary symptom appears to be that I either have a black external monitor/s with working hardware cursor in the expected screen arrangement, or I get black main display and working external/s. I can still log in (blindly on the main screen, but I get my wallpapers on the externals) and shut the system down to start over. Occasionally the black screen will instead be classical video buffer garbage (smeared text in interesting colors, for instance). 

I tried a few alternatives (only the Dell monitor on eGPU, only the Cinema on eGPU, both on eGPU, Cinema on eGPU with Dell on OWC Dock) and haven't come up a with a repeat of the "fully working" state. For now I'll park the Cinema and drive the Dell from the OWC mini DisplayPort (i.e. thru the onboard Radeon). I'm wondering if returning to the latest nVidia drivers might help at all - the script downgraded to the .103 video driver and the .178 CUDA. 

Basically partial success and for me, sufficient function to be useful. If there's insight or alternatives to try, I may be able to give it a try - most likely on a weekend.

I really appreciate all the effort that you've put into assembling these workarounds!

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
 

@technomad et al

I've updated the default drivers.
Please re-run the script to update NVIDIA drivers. @technomad found a possible issue with OpenCL with previous ones.
You can also update manually.
(This only concerns already running systems.
An update for NVIDIA dGPU will follow soon.)

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)


Charly4 liked
ReplyQuote
 of  21