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

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

 of  56
  RSS

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

@fr34k

I used this command in Terminal to turn off autoboot when the lid is open

sudo nvram AutoBoot=%00

To restore the original behaviour you can use

sudo nvram AutoBoot=%03

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


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

@imcalledandy
That works as well...

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
imcalledandy
(@imcalledandy)
Estimable Member
Joined: 3 years ago
 

So reinstalling macOS from Recovery means I can now boot again!

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


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

I've been having an absolute bear of a time getting my egpu to work.  Finally given up on the windows side, as I've made more progress on the mac side.  My setup:

15" MBP (Late 2013) w/GT750m
AORUS 1070
Official Apple TB2 cable
Official Apple TB2 <-> TB3 adapter

I've been totally unable to get windows to recognize my egpu, and I've followed multiple guides.  It just never shows up in the device manager.  Lights never come on, etc.

However on the mac side, even before any tweaks, the AORUS lit up and showed up in the system report as a thunderbolt device.

Now using @fr34k 's script, I am getting close.  the default way did not work.  I had to do the first suggestion under the 'tweaks' section ('execute in new order').  I cannot boot with the egpu connected, or the internal screen just stays black (backlight on, and fan steadily increasing in intensity... seems like it's stuck in some sort of loop).  However if I hotplug the egpu right after I type in my password and log in, the box lights up and my external monitor wakes up from sleep.  If I try hot plugging any sooner, the laptop becomes unresponsive.

The main issue now is that my external monitor is just black, and no windows show up on it.  Oddly, my mouse shows up on it, but dragging anything from my internal screen over to the external just looks like I'm moving my mouse over... nothing changes from the black.  In my system report, it's showing that my internal screen is powered by the 750, and the external is powered by the 1070.

Has anyone experienced anything like this?  Any ideas?

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


ReplyQuote
comfycat
(@comfycat)
Trusted Member
Joined: 2 years ago
 

@dubax Just a quick note: you need to spoof a macOS boot to get Windows 10 bootcamp to recognize the eGPU. Look for tutorials on using Refind and apple_set_os.efi. After you spoof and boot Win, you'll be able to see the device in device manager and install drivers. You'll need AORUS Gaming Engine (free app from Gigabyte) to force the fans to work at 100% to keep your GPU temp down (the TB2 adapter seems to interfere with the fans and LED lights). I've been playing AAA games at 4k with my AORUS 1080 since I got this figured out (my specs in signature); good luck!

I have a similar setup to @dubax, and I saw all sorts of wierd things when I was trying to get macOS to recognize my eGPU, including what they described. I'll share what worked for me with macOS and @fr34k's updated script; this may not work for different Macbooks or anyone else at all! You've been warned.

Keep your eGPU unplugged until the end. The first step is to disable or partially disable csrutil. Boot in recovery, then "csrutil disable" or "csrutil enable --without kext" (I prefer the former). Reboot, and run the script via the link in fr34k's earlier posts; The script failed at first, telling me that my OS was not supported (10.13), so I was out of luck until fr34k could come to my rescue. Since then the script has been updated, and also allows SIP (csrutil) to be completely disabled and still run. So when I ran the script the second time (really the fourteenth time) it worked marvelously! BUT if you've had problems running the script previously, run the script first with the modifier "--uninstall" and get it back to basics first! Then reboot, then run the script. Finally, do a complete shutdown, plug in the eGPU to the Mac, boot into macOS, and you should see the 1070 or 1080 in your system report under Graphics/Displays. Then you're golden! I've heard that you'll only get the eGPU boost with an external display on macOS, but you can use the eGPU with the internal display on Windows 10 bootcamp, hence my earlier instructions. With macOS and Windows 10 working with the AORUS 1080 eGPU currently, I've got the best of both worlds. I hope you can too!

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


fr34k and itsage liked
ReplyQuote
dubax
(@dubax)
New Member
Joined: 2 years ago
 

@comfycat

On the windows side, I've followed all the guides. I'm spoofing the OS and using refind, GPU switch, etc... and it still does not show up in the device manager.

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


comfycat liked
ReplyQuote
protogon
(@protogon)
Active Member
Joined: 2 years ago
 

Thank you @fr34k and everybody else for all your hard work.
Sorry to hijack this thread but while my problem is a little bit different just want to ask a quick question.

My system is Latest Macbook pro 2017, Sonnet 550 with a TitanXP.
Everything else works (C4d, redshift, octane, cuda, external displays etc), however, Houdini uses OpenCl for accelerating simulations and for some reason it doesn't want to 'see' opencl within nvidia even though I know it is supported by the card.
I assume it is something that has to do with the kexts that doesn't allow opencl to be visible on the system.

If I run in houdini's terminal:

HOUDINI_OCL_VENDOR="NVIDIA Corporation" hgpuinfo
as to force the vendor, I get:
hgpuinfo[3532:234831] +[MTLIOAccelDevice registerService:]: Failed to find bundle for accelerator bundle named: GeForceMTLDriverWeb errno: 0
 
So the problem seems to be that houdini doesn't recognise the "GeForceMTLDriverWeb" as on OCL accelerator.

Also tried with the following env vars:
HOUDINI_OCL_DEVICENUMBER = 0
HOUDINI_OCL_DEVICETYPE = “GPU”
HOUDINI_OCL_VENDOR = “NVIDIA Corporation”

Did anybody had success with OpenCL?
Any suggestions/recommendations would be very helpful.

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
 

@dubax
I've also tried it and did not need any tricks or other workarounds. It worked right out of the box (only needed to disable the AMD GPU in the device manager) BUT only with 1703, I then upgraded to 1709 and it all fell apart and so I deleted everything.
I'm currently thinking about trying it again but I think the windows experience is in my opinion still 
incomparable to macOS. Though apple could do a great deal of making AMD AND NVIDIA eGPUs a piece of cake in macOS AND windows. But they are apple, they never asked the customer what they wanted.
I'm still praying each night for native NVIDIA support for macOS arriving at WWDC 2018. Windows support would be the cherry on the huge pile of ice cream topped with chocolate sprinkles and bathed in strawberry sauce.

Oh apple. Just once listen what would make customers happy...

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)


comfycat and itsage liked
ReplyQuote
(@valquev)
New Member
Joined: 2 years ago
 

So here is my benchmark results and my setup : https://imgur.com/a/KfuEy

Would you know why my unigine heaven benchmark score is so low ? I opened and runned it on my external screen who is my default screen, plugged directly on the GTX1060.
I just feel that my mantiz venus and GTX1060 are used as TB2 to HDMI adapter and unigine heaven / valley results are exactly the same without EGPU.

Thanks in advance.

2013 15'' MacBook Pro retina (GT750M) + GTX1060 with TB2 TB3 adaptor (Mantiz Venus) + macOS 10.13.3 (17D102)


ReplyQuote
fireheadman
(@fireheadman)
Trusted Member
Joined: 3 years ago
 

Sure wishing the 1st post of this thread would have mentioned 
NOT COMPATIBLE with 10.13.4.
I'm on this version now and lost my 3 monitor setup....  fingers crossed the developers on this thread have some magic to make it work on this version.

Have to boot back into bootcamp/windows to use all my monitors.

If you guys need a tester, hit me up.. I'm willing to help out however


DAILY DRIVER: ⚡cMP 2010 (ⓄⓈ:DualBoot macOS 10.13.6/Windows 2016 (1803)) | ⒸⓅⓊ:3.47GHz Xeon X5690 (x12 core)
ⓇⒶⓂ:64GB 1333MHz DDR3 | ⓈⓈⒹ:1TB SSD (LiteON 512 -x4 - RAID1) w/Marvell Raid Controller | ⒼⓅⓊ:
Nvidia GTX 1080 TI 11GB Founders Edition
⚡ Previous was MacMini 2011 w/AKiTiO Thunder2 | ⒼⓅⓊ:EVGA GTX 1060 3GB SC Gaming


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

Sure wishing the 1st post of this thread would have mentioned 
NOT COMPATIBLE with 10.13.4.
I on this version now and lost my 3 monitor setup....  fingers crossed the developers on this thread have some magic to make it work on this version.

Have to boot back into bootcamp/windows to use all my monitors.

Was going to ask if anyone tried Freak's script with official 10.13.4 release. Sounds like not workable for now.

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


ReplyQuote
fireheadman
(@fireheadman)
Trusted Member
Joined: 3 years ago
 

very bummed... as I use my desktop every single day and not I gotta hack it out with a single monitor . (feeling like the stone age days again) .  🙁


DAILY DRIVER: ⚡cMP 2010 (ⓄⓈ:DualBoot macOS 10.13.6/Windows 2016 (1803)) | ⒸⓅⓊ:3.47GHz Xeon X5690 (x12 core)
ⓇⒶⓂ:64GB 1333MHz DDR3 | ⓈⓈⒹ:1TB SSD (LiteON 512 -x4 - RAID1) w/Marvell Raid Controller | ⒼⓅⓊ:
Nvidia GTX 1080 TI 11GB Founders Edition
⚡ Previous was MacMini 2011 w/AKiTiO Thunder2 | ⒼⓅⓊ:EVGA GTX 1060 3GB SC Gaming


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

@fireheadman looks like you're on a thunderbolt 1/2 mac, which 10.3.4 doesn't support for eGPU (at this point at least), so you might want to roll back to 10.3.3 if you have backups.

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
 

@fireheadman
@chippy-mcchipset
You are right. My script does not work for .4, yet. I cannot tell when it's going to work.
I recommend staying at .3 for now and to those who already upgraded follow @psonice's advice and downgrade via Time Machine Backup ASAP. On the red side, older Macs with TB2 or lower aren't supported by 10.13.4 so this may even reach the green side, it's unknown yet. (Link)

If you haven't any backups you might try waiting or a clean install with manual backup aka copy files to external drive.

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)


comfycat and itsage liked
ReplyQuote
ozzy
 ozzy
(@ozzy)
Trusted Member
Joined: 3 years ago
 
Posted by: natemac00

Whenever I update my OS to the next version, I can never boot my computer after... I just get stuck at the Black Apple boot screen and NEVER get any further.

I've tried booting into 'Safe Mode' & PRAM Reset and doesn't fix it. This has happened the past few updates.

The only way I've been able to fix it, is by using a High Sierra USB boot drive and "Upgrading(reinstalling)" the original High Sierra on top of the current one...
then installing the latest updates from the App Store...
finally, installing the NVIDIA Drivers & nvidia-epu file.

Is there something I need to be uninstalling or doing first before I do a MacOS update?
This is only on my MacBook Pro 2014, I do not have this issue on my 2013 MacPro.

I have the same problem. For me it's related to the eGPU extension. I have to boot into recovery mode, open the terminal, navigate to the Extensions directory, do the command to delete that, then I can boot fine again. Then I can install the new version (which is correct for the OS), and all is well again. Kind of annoying, but once I figured it out it only adds 5-10 minutes.

2012 15" Macbook Pro Retina GT650M + [email protected] (AKiTiO Node via TB3->TB2 adapter) + macOS10.13 & Win10


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

@ozzy
@natemac00
I think an uninstall before the update is still less time, although you still need to enable SIP for the installation of the NVIDIA drivers (except of course you use the special SIP setting)

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

@ozzy
@natemac00
I think an uninstall before the update is still less time, although you still need to enable SIP for the installation of the NVIDIA drivers (except of course you use the special SIP setting)

Well 13.4 just came out so I’ll have a chance to find out. Thanks for the help

3D Cinema 4D/Octane Artist
Gigabyte Aorus GTX 1080 Gaming Box w/ TB2to3 Adapter
2013 Mac Pro
2014 MacBook Pro


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

@natemac00
Don't upgrade yet! See

EDIT: Added warnings into the script, the original post and the GitHub repo.

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

New Drivers are here. Anyone tested?
https://images.nvidia.com/mac/pkg/387/WebDriver-387.10.10.10.30.103.pkg   --> build 17E199  New!

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


ReplyQuote
9935c101ab17a66
(@9935c101ab17a66)
Active Member
Joined: 2 years ago
 
Posted by: fireheadman

Sure wishing the 1st post of this thread would have mentioned 
NOT COMPATIBLE with 10.13.4.
I'm on this version now and lost my 3 monitor setup....  fingers crossed the developers on this thread have some magic to make it work on this version.

Have to boot back into bootcamp/windows to use all my monitors.

If you guys need a tester, hit me up.. I'm willing to help out however

If you're running an unsupported eGPU and running third-party scripts to gain functionality you should:

a) NOT do software updates without thoroughly investigating whether or not it is safe
b) Have a backup/clone of your boot drive so that you can restore if there are issues.

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


fr34k and comfycat liked
ReplyQuote
(@kedzip)
New Member
Joined: 2 years ago
 

First time here, I have a 2017 MBA 13 on 10.13.3 and a Sonnet Breakaway eGPU with a GTX 980 ti through TB2 to TB3
I installed everything with fr34k's automated eGPU script. I can only get it to boot and be recognized with boot, log in, plug in, log out and back in. The external screen doesn't working. I can see the backlight is on but the screen's black and I can't even see the cursor. I've tried other boot methods and having SIP on and off. When I go to About this Mac, in display, I see that both displays are recognized but both are still under the iGPU. System Information sees the card correctly and nVidia driver manager in System Preferences sees it just fine. I don't know what to do anymore.

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
 

@kedzip
did you try all the 
tweaks linked in my signature? (Here I think 6 might work)

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
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 

@protogon
wow, this is 
somewhat odd:
The 387.10.10.10.30.103 web drivers are for build 17E199
Apple lists the build number as 17E198 here

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

Installed 10.13.4 and Nvidia driver 387.10.10.10.30.103.

And built NvidiaEGPUSupport from source code with corresponding version strings modified. 

Doesn't work, crashes every time trying to plugin my Akitio node

Any ideas?

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


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

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
 

@protogon
does it 
work? If so what exactly did you do?

I'm still facing the problem of Kernel Panics everywhere:
Kernel Extensions in backtrace:
com.apple.AppleGPUWrangler(3.18.48)[639340A6-458F-376A-93C5-30FB44E58EAE]@0xffffff7f847d5000->0xffffff7f847defff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1850E7DA-E707-3027-A3AA-637C80B57219]@0xffffff7f83c94000
dependency: com.apple.iokit.IOGraphicsFamily(519.15)[D5F2A20D-CAB0-33B2-91B9-E8755DFC34CB]@0xffffff7f8448c000
dependency: com.apple.AppleGraphicsDeviceControl(3.18.48)[89491182-0B41-3BC3-B16F-D5043425D66F]@0xffffff7f84792000
com.nvidia.web.GeForceWeb(10.3.1)[F9DB65B6-77E6-301B-90F3-707D89858428]@0xffffff7f88426000->0xffffff7f88510fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1850E7DA-E707-3027-A3AA-637C80B57219]@0xffffff7f83c94000
dependency: com.apple.iokit.IONDRVSupport(519.15)[B419F958-11B8-3F7D-A31B-A72166B6E234]@0xffffff7f847b8000
dependency: com.nvidia.web.NVDAResmanWeb(10.3.1)[732647D4-EFC4-3E75-9618-B96D61BE214C]@0xffffff7f879a4000
dependency: com.apple.iokit.IOGraphicsFamily(519.15)[D5F2A20D-CAB0-33B2-91B9-E8755DFC34CB]@0xffffff7f8448c000
dependency: com.apple.iokit.IOAcceleratorFamily2(378.18.1)[BAA0383C-9650-3934-B04A-69008F757A2C]@0xffffff7f855ff000

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

Sorry @Fr34k if my post wasn't clear.

I haven't installed 10.13.4 on my main machine (2017 late MBP, Sonnet 550) that has the eGPU but on a Mid2012 with Nvidia Chipset. Just replied about the version number.

I'm in the the mid of a project and don't have time to install and debug the eGPU on latest High Sierra.
Will do though within the week. Hope you find a solution sooner 😉
Maybe give this a try:
https://github.com/pedroresende/NVIDIAEGPUSupport
edit: and this that was mentioned here:
https://github.com/Benjamin-Dobell/nvidia-update

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
 

@protogon
ATM I've got a little time on my hand and I'm currently tinkering with my system (including changing the KEXT) and can't get it to work.
I would definitely hold off for now. On Tuesday I need my Mac up and running again so I think I will revert back on Monday (if not sooner).
Either I'll find a clue until then or someone else fixes the problem...

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
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@fr34k: You're on the right track. The place where the kext crashes is a good starting point.

As I pointed out earlier in the beta stage, AMD drivers do load fine via TB2 and the eGPU briefly shows up under system report, also under the PCI information (Driver Installed: YES), but the stop method gets called immediately. Why to load the drivers in the first place if the purpose is to completely block?

macOS 10.13.4 brought an unnamed validation method that checks the existence of IOThunderboltSwitchType3 class on the host Mac. If you google it, you will find nothing except this unblocker where it is referenced:

https://github.com/rgov/Thunderbolt3Unblocker/blob/master/Thunderbolt3Unblocker/Thunderbolt3Unblocker.c

Our forum does not encourage doing binary hacks. If you can do in-memory override, much better. There are plenty of hackers who do this in their day-to-day work to find out system security holes and get paid by services like HackerOne. That's where reverse engineering is very acceptable. I recall yifanlu. One of them surely will stop by on this thread sooner or later. Of course, Apple can block it again. Must be Intel's pressure or the fact that some configurations are not 100% stable via TB2. End users want something reliable, and Apple cannot guarantee TB2 stability.

Apple could at least announce that "may work" is not true anymore if this is done on purpose. Customers do not like to guess.

Release Notes v1.0: "The kit may work with Thunderbolt 2-enabled Mac computers via a Thunderbolt 2 to Thunderbolt 3 adapter".

https://developer.apple.com/development-kit/media/external-graphics/Release-Notes-ECDK_v1.pdf

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread


itsage and protogon liked
ReplyQuote
(@kedzip)
New Member
Joined: 2 years ago
 
Posted by: fr34k

@kedzip
did you try all the 
tweaks linked in my signature? (Here I think 6 might work)

I did #6 and now the cursor shows up on the second screen but still black.

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


ReplyQuote
fireheadman
(@fireheadman)
Trusted Member
Joined: 3 years ago
 

good thing = have time machine backups to revert to
bad thing = found out my backups are possibly corrupted, working with Apple support to get them verified/working

....then will hopefully restore

UPDATE: I have my backups back online, performing restore of OS back to 10.13.3.     Will stay tuned in hopes something breaks through on 10.13.4 for TB2 support on eGPUs.


DAILY DRIVER: ⚡cMP 2010 (ⓄⓈ:DualBoot macOS 10.13.6/Windows 2016 (1803)) | ⒸⓅⓊ:3.47GHz Xeon X5690 (x12 core)
ⓇⒶⓂ:64GB 1333MHz DDR3 | ⓈⓈⒹ:1TB SSD (LiteON 512 -x4 - RAID1) w/Marvell Raid Controller | ⒼⓅⓊ:
Nvidia GTX 1080 TI 11GB Founders Edition
⚡ Previous was MacMini 2011 w/AKiTiO Thunder2 | ⒼⓅⓊ:EVGA GTX 1060 3GB SC Gaming


ReplyQuote
i0ntempest
(@i0ntempest)
Trusted Member
Joined: 3 years ago
 

So what's the current status on 10.13.4 for TB3 Macs?

Setup 1: Apple iMac 2017 21.5” 4K + eGPU
dGPU: AMD Radeon Pro 560
eGPU: ASUS Strix AMD Radeon Vega 56 via Thunderbolt 3 (AKiTiO Node)
OS: macOS Catalina 10.15.3, Windows 10 1809, Kali Linux 2020.1
Setup 2: Apple Mac mini 2018 + eGPU
iGPU: Intel UHD Graphics 630
eGPU: AMD Radeon RX 570 MXM via Thunderbolt 3 (Sonnet Breakaway Puck)
OS: macOS Catalina 10.15.4 Beta, Windows 10 1909


ReplyQuote
9935c101ab17a66
(@9935c101ab17a66)
Active Member
Joined: 2 years ago
 

I had a pretty stable / solid 10.13.3 install running and decided to try upgrading to 10.13.4 to see if it would get clamshell mode working. Spent 3-4 hours tonight messing with stuff, and could not get 10.13.4 going, at least with existing tools/scripts. Tried basically all of the EGPU activation scripts and tools I could find and none of them worked. Either the external GPU was not recognized at all or plugging in my eGPU would immediately cause a kernel panic. I think we'll have to wait for updates.

(FYI, 2016 MBP 15" TB, TB3, HP Omen, GTX 970)

Going to reinstall 10.13.3 tomorrow unless anything major changes.

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
 

@9935c101ab17a66
@i0ntempest
and all others as well
The tree of kernel panics is different for each driver and each situation.
It will take quite some time to figure something out. You first may want to find the problems causing the panics then you can even start about thinking of solution.
It won't bring you any joy updating to 10.13.4 unless:
a) you don't need your eGPU for an unforeseeable span of time
b) you're into KEXTs and want to tinker and actively find a solution

I don't have much time so I may only find clues. If you want to take a look what the current enabler does with the system visit my GitHub repo.
DO NOT EVEN THINK ABOUT USING THE EXPERIMENTAL BRANCH AND THEN REPORTING THE PANICS. This does not help at all, atm. (Unless of course you've got a lead, then go ahead)
You may use it for your own testing and research. Until I update the master stay away from the script in the experimental branch.

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
fireheadman
(@fireheadman)
Trusted Member
Joined: 3 years ago
 

curious of this behavior...
Just completed my restore back to 10.13.3, noticed some artifacts from eGPU, so started by rebooting with PROM reset (CMD+OPT+r+p).... waited for the 2 apple chimes and logged back in.

However I am back to 1 screen (hdmi output from macmini).
I will re-run the script "bash <(curl -s  https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh)  -r"  to see if this resets the eGPU configuration...

..Just curious if anyone else has reset the PROM and reverted to no eGPU? 


DAILY DRIVER: ⚡cMP 2010 (ⓄⓈ:DualBoot macOS 10.13.6/Windows 2016 (1803)) | ⒸⓅⓊ:3.47GHz Xeon X5690 (x12 core)
ⓇⒶⓂ:64GB 1333MHz DDR3 | ⓈⓈⒹ:1TB SSD (LiteON 512 -x4 - RAID1) w/Marvell Raid Controller | ⒼⓅⓊ:
Nvidia GTX 1080 TI 11GB Founders Edition
⚡ Previous was MacMini 2011 w/AKiTiO Thunder2 | ⒼⓅⓊ:EVGA GTX 1060 3GB SC Gaming


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

@fireheadman
reseting the NVRAM will reset csrutil also

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


ReplyQuote
 of  56