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

Page 5 / 20 Prev Next
  RSS

ed_co
(@ed_co)
Reputable Member
Joined: 2 years  ago
Posts: 349
May 6, 2018 12:43 pm  
Posted by: fr34k

@ed_co
2. Yes it does not change 10.13.3 at all. The new procedure is only required due to the update to 10.13.4
6. Yes the script will not run with an eGPU connected. It will simply refuse action to prevent panics during execution. This measure is for newbies that might think that would be a great idea, which it definitely is not.

@fr34k @goalque
Oh, it is a pity. I thought that the new approach was for everything, not just 10.13.4.
Which by the way, could you please, tell us how this new stuff works? I think that was goalque's idea, right? Could you please explain, how it works? What exactly is it going under the hood? I liked the previous approach of yifanlu, and I am curious how it works now 😉
Today, if nothing comes up, I will install 10.13.4
Cheers guys

mid-2017 Macbook Pro RP560 + MSI GTX1080Ti GAMING [email protected] (Mantiz Venus) + macOS10.13.5 & Win10


fr34k liked
ReplyQuote
Username
(@username)
Estimable Member
Joined: 2 years  ago
Posts: 180
May 6, 2018 12:52 pm  

When I stepped up to 10.13.3 I often suffered from long boot times which came from Nvidia drivers crashing during boot. That was the cause of the black screen.
Downgrading the Nvidia drivers sovled everything.

I usually have two 27" Eizo monitors but I can't fit them both on the desk right now.
But I have connected my Mac mini HDMI out to the Eizos HDMI in and the DisplayPort from the eGPU to the same Eizo.
That way I have boot screen on Inpu1 and eGPU screen on input 2 🙂

That means I get full acceleration on my 27" over DisplayPort yet EFI boot screen if I wish.

The extra HDMI screen I've placed far right in the monitor setup in macOS.

2012 Mac Mini + [email protected] (AKiTiO Thunder3 via TB3->TB2 adapter) + macOS


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1184
May 6, 2018 12:53 pm  

@fr34k
Oh, it is a pity. I thought that the new approach was for everything, not just 10.13.4.
Which by the way, could you please, tell us how this new stuff works? I think that was goalque's idea, right? Could you please explain, how it works? What exactly is it going under the hood? I liked the previous approach of yifanlu, and I am curious how it works now 😉
Today, if nothing comes up, I will install 10.13.4
Cheers guys

Yes, 10.13.4 workaround was my idea and yifanlu's workaround is still necessary - the script just automates the process. If you are curious, look at the GitHub source code 🙂 We want to avoid lower-level technical discussion regarding binary patches.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


fr34k liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 10 months  ago
Posts: 386
May 6, 2018 1:37 pm  

@leoleal
Nah, you just found a bug... Nothing to worry about: I haven't tested if something even exists before I do an action on it. 

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 1 year  ago
Posts: 31
May 6, 2018 1:45 pm  

Thank you for helping us all, @fr34k !

Do you believe it is what's bugging my OS? not even standalone internal screen works for me. I' m restoring 13.3 time machine backup.

If I can help you with further tests, lemme know, cause I'm keeping the clean 13.4 backup ready to go.

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 10 months  ago
Posts: 386
May 6, 2018 1:51 pm  

@leoleal
No, I don't think so.
I've just committed the fix.
What this was about:
I deactivate automatic driver updates for NVIDIA drivers and there the "autoCheck" value must be set to 0. I don't know why it didn't exist but it should not have any 
effect on that.


@leoleal
can you boot with an eM attached directly to your
Mac?

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
mardarethedog
(@mardarethedog)
New Member
Joined: 6 months  ago
Posts: 3
May 6, 2018 2:00 pm  
Posted by: Donald Martin

@mardarethedog What monitor do you use for the 1080TI? Also, try running GPUsniffer before using Premiere Pro. Right click Premiere Pro - "Show Package Contents".

@donald_martin Only using the internal iMac monitor which is accelerated by the internal gpu.

davinci resolve and premiere pro are accelerated by the 1080TI. Both apps see the card. Also GPU activity monitor reports that the 1080TI is used both for timeline playback and export.

What's the benefit of using GPUsniffer before using Premiere Pro?

Best,
Rob


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 7 months  ago
Posts: 36
May 6, 2018 2:39 pm  
Posted by: goalque
Posted by: rhenriques11

In my case I have a MacPro TrashCan with two internal AMD Fire Pro 500 and two external eGPU's, both Nvidia GTX 1080 Ti. All it's working now. If you have one of these models please take notice that it's important to choose the right thunderbolt ports used. MacPro has 6 TB2 ports and I was successful in connecting the screen to N2, one of the eGPU to the N1 and the second one to N5.

Photos, screenshots? Let see if we can enable all 6 TB2 ports for eGPU use, my automate-eGPU.sh script's -a mode did that earlier. @fr34k could implement the same functionality.

Hi goalque. I'm using a diferente setup now. I've conected one of the NVidias directly to the screen and started up with it connected to the machine. It's using Port N4. The other one is connected after the log in. Working perfectly. Nvidia is now the main GPU of the machine.
See attached screenshots.


ReplyQuote
lars18th
(@lars18th)
New Member
Joined: 6 months  ago
Posts: 3
May 6, 2018 2:55 pm  

Hi,
My results with the script in case it helps.
macOS 10.13.4 freshly installed on an external SSD. Applied security patch so that version is 17E202. fr34k's script worked like a charm. Acceleration for games working. I don't use CUDA, and it is not installed by default on the script, so I cannot tell about it.
On first reboot, the eGPU icon on the task bar didn't appear. Once rebooted again, it was there with the name of the GPU.
Specs:
rMBP 13" mid 2014. No dGPU, just intel Iris 5100.
Akitio Thunder2. Zotac GeForce 1050Ti OC.

As mentioned before, if I hotplug the eGPU once the system has booted, I get a black screen on the external display. If I try to 'hot-unplug' it, the system crashes and reboots itself.

I think everything that happens on my system is working as expected.

Many many many thanks for this amazing work.

Regards.

13" rMBP mid 2014. macOS 10.13.4 (thanks @fr34k !).
Akitio Thunder2 with Zotac nVidia 1050Ti OC (fits without modding).
eGPU working in macOS and Win10 2018 Spring Update


fr34k liked
ReplyQuote
Charly4
(@charly4)
Eminent Member
Joined: 1 year  ago
Posts: 37
May 6, 2018 3:06 pm  

@mac_editor
Any idea which is the problem with dEGPU´s?
On the other hand, Are you experimenting minor issues with some transparencies like me?

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


mellowwood liked
ReplyQuote
LeoLeal
(@leoleal)
Eminent Member
Joined: 1 year  ago
Posts: 31
May 6, 2018 3:24 pm  
Posted by: fr34k

@leoleal
can you boot with an eM attached directly to your 
Mac?

@fr34k, no I can't. I tried that too. Attached monitor directly on Mac with HDMI Cable, No Luck. Internal and External Monitor showed black screen (internal shows the apple logo with progress bar stuck. Cursor works.

As soon as I delete the KEXT, Internal and External monitor come back to life, but then I have no eGPU again.

I Tried using Integrated Graphics Only from the app @goalque linked to deactivate the 750m dgpu. No Luck either.

Restored the 13.3 Image and everything is working.

As last resort I tried even deleting the KEXT, installing the V8 PKG, booted, no luck, then copied the kext from your script over It (maybe something in that PKG's script would work), also no luck.

I turned On verbose Boot-arg, and filmed my screen with my cellphone (LOL) to read the boot messages before Apple logo Appear. I Could pause the video and read... didnt find anything special that could sign to a problem with the drivers.

But It really seems that It's something very specific with the EGPUSUPPORT kext. Im sorry I dont have deep knowledge to give you more info... unless U orient me to do so. My system is Safe... I have a working state (10.13.3) and a Freshly Updated state (10.13.4 w/ security update) saved in Time Machine.

Thank you again!

EDIT: Editted my signature to include my setup.

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


ReplyQuote
Mize
 Mize
(@mize)
Eminent Member
Joined: 8 months  ago
Posts: 46
May 6, 2018 3:27 pm  

Tried the very latest just now and still no go on iMacPro 🙁

iMac Pro (2017), 3.2 GHz Xeon W, 32 GB, 1TB SSD, RX Vega 56 + AKiTiO Node Pro w/ Zotac 1080 Ti, working with login hack on 10.13.3 but BROKEN by Apple blocking Nvidia in 10.13.4. Boo-hiss you Apple!


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1184

ReplyQuote
(@omer_ben-amram)
New Member
Joined: 12 months  ago
Posts: 1
May 6, 2018 4:13 pm  

MBP 2017, GTX 1070 10.13.4 latest here.
Working as expected - except getting black screen (with mouse) on hot plug. It's resolved after log off/logon.

The nice improvement from 10.13.3 that chrome is finally as responsive as with the internal GPU!
It used to lag when scrolling, unless started with --disable-gpu flag.

Also getting the disconnect "null" on taskbar.

Thanks a lot for your effort folks. It's really impressive!


fr34k and goalque liked
ReplyQuote
Baris Oktem
(@baris-oktem)
Active Member
Joined: 11 months  ago
Posts: 17
May 6, 2018 4:25 pm  

I assume if i make this eGPU script in my iMac Pro FinalCut Pro X will not work with eGPU (with NVidia 1080ti card) box in it?
I have to plug it out eGPU box or what is my another options?


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years  ago
Posts: 1335
May 6, 2018 4:29 pm  
Posted by: Charly4

@mac_editor
Any idea which is the problem with dEGPU´s?
On the other hand, Are you experimenting minor issues with some transparencies like me?

I’m busy with other stuff. Research will continue later this month on my end.

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


fr34k and Charly4 liked
ReplyQuote
Charly4
(@charly4)
Eminent Member
Joined: 1 year  ago
Posts: 37
May 6, 2018 4:47 pm  
Posted by: mac_editor
Posted by: Charly4

@mac_editor
Any idea which is the problem with dEGPU´s?
On the other hand, Are you experimenting minor issues with some transparencies like me?

I’m busy with other stuff. Research will continue later this month on my end.

Great!!

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


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 10 months  ago
Posts: 386
May 6, 2018 5:51 pm  

The help (explanation of the parameters) can now be reached with the --help | -h | -? | ? | help command.
When a parameter is not recognised, a more helpful error is now displayed.
A few changes under the hood have been made since some logic was just inflexible.

A few more updates are still to come. However, it may take a while for some to arrive.
My time is getting more and more limited. I think there will always be time for fixes, so keep 'em coming. 😁

EDIT: of course --checkSystem and --checkSystemFull have been added...

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


LeoLeal and Charly4 liked
ReplyQuote
Ningauble77
(@ningauble77)
Trusted Member
Joined: 9 months  ago
Posts: 65
May 6, 2018 6:26 pm  

Tempted to pull the trigger and install the new 10.13.4 workaround on my 15" 2016 MBPro+Core2+GTX1080, I have two questions first.

1.  I see that Nvidia egpu+ AMD dgpu is problematic (automatic switching has to remain on etc), I am fine with limited functionality of the dGPU when docked to the egpu, I usually run it in clamshell anyway, but I need the dGPU to work normally once I am undocked and mobile, will the patched wrangler function prevent the normal operation of my Radeon 460 Pro when not attached to the egpu?

2.  The recommendation is to fully disable SIP for installation, has anyone tried switching to --without kext after the fact in my configuration?  I'm guessing it might not like the hex patched gpuwrangler and cause issues?  I'm not crazy about the idea of running fully SIP disabled day in day out (--without kext worked fine for me in 10.13.3).


verichip liked
ReplyQuote
Artemus80 J.
(@artemus80_j_)
Active Member
Joined: 7 months  ago
Posts: 12
May 6, 2018 6:43 pm  

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 🙂

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


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1184
May 6, 2018 6:51 pm  
Posted by: Ningauble77

Tempted to pull the trigger and install the new 10.13.4 workaround on my 15" 2016 MBPro+Core2+GTX1080, I have two questions first.

1.  I see that Nvidia egpu+ AMD dgpu is problematic (automatic switching has to remain on etc), I am fine with limited functionality of the dGPU when docked to the egpu, I usually run it in clamshell anyway, but I need the dGPU to work normally once I am undocked and mobile, will the patched wrangler function prevent the normal operation of my Radeon 460 Pro when not attached to the egpu?

2.  The recommendation is to fully disable SIP for installation, has anyone tried switching to --without kext after the fact in my configuration?  I'm guessing it might not like the hex patched gpuwrangler and cause issues?  I'm not crazy about the idea of running fully SIP disabled day in day out (--without kext worked fine for me in 10.13.3).

1) M370X operates normally when undocked (automatic graphics switching can be checked and unchecked), don't know about Radeon 460.
2) You can be the first to try. If --without kext prevents access to /S*/L*/E*, you must keep SIP fully disabled during the installation. After that, --without kext should work.

EDIT: see the post below.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


fr34k liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 10 months  ago
Posts: 386
May 6, 2018 6:51 pm  

@ningauble77
--w/o kext won't work for you... NVIDIA + 10.13.4 -> guaranteed!

EDIT: (haven't seen @goalque's post, installation + w/o/k -> won't work), after that, maybe: but please don't test without backup

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


goalque liked
ReplyQuote
Baris Oktem
(@baris-oktem)
Active Member
Joined: 11 months  ago
Posts: 17
May 6, 2018 7:47 pm  

Ok i finally managed to work with iMac Pro 10.13.4 17E202
It's working flawlessly with some applications like Redshift in Cinema 4D and After Effects working better now.
Thank you very very much for this script. I'm really appreciated for everyone who contributed this great work.
I have some issues
- Log out and Log in not working when i try that screen getting green Apple logos and grey noise 🙂
- When eGpu attached i couldn't restart black screen coming and when i turning of eGPU it restart and going normal boot.
- When eGPU open and connected machine doesn't start it should be closed. 
- Startup process; i turned on machine wait 10-15 sec and than open eGPU that's the way open eGPU for me.
- And lastly in Cinema 4D Octane Cuda drivers not working properly. I thing thats nothing about eGPU it has to be update with NVidia i'm not sure. 

Thank you again.


fr34k and goalque liked
ReplyQuote
Mize
 Mize
(@mize)
Eminent Member
Joined: 8 months  ago
Posts: 46
May 6, 2018 7:48 pm  
Posted by: goalque
Posted by: Mize

Tried the very latest just now and still no go on iMacPro 🙁

@DANgerous25 got it working earlier

https://egpu.io/forums/builds/2017-imac-pro-gtx1080ti32gbps-tb3-akitio-node-macos-10-13-2/
https://egpu.io/forums/mac-setup/imac-pro-high-sierra-10-13-2-buildc2120-nvidia-web-drivers-incompatible/#post-27054

Yeah, I had it working on 10.13.3 also. Tried many drivers and many scripts but cannot get it working on 10.13.4.

Thanks for all the efforts folks.

iMac Pro (2017), 3.2 GHz Xeon W, 32 GB, 1TB SSD, RX Vega 56 + AKiTiO Node Pro w/ Zotac 1080 Ti, working with login hack on 10.13.3 but BROKEN by Apple blocking Nvidia in 10.13.4. Boo-hiss you Apple!


fr34k and goalque liked
ReplyQuote
verichip
(@verichip)
Active Member
Joined: 8 months  ago
Posts: 9
May 6, 2018 9:26 pm  

I have a Radeon dGPU in my 2017 MacBook, and since automatic gpu switching is turned on, when macOS tries to use the dGPU the whole system gets sluggish until it goes back to using the Intel iris graphics. Is there any way of disabling the Radeon dGPU while my eGPU is connected?

2017 15" Macbook Pro Touchbar (Radeon Pro 555), Gigabyte AORUS Gaming Box (GTX 1070)


ReplyQuote
BonzTM
(@bonztm)
New Member
Joined: 6 months  ago
Posts: 1
May 7, 2018 12:02 am  
Posted by: BonzTM
Posted by: verichip

I have a Radeon dGPU in my 2017 MacBook, and since automatic gpu switching is turned on, when macOS tries to use the dGPU the whole system gets sluggish until it goes back to using the Intel iris graphics. Is there any way of disabling the Radeon dGPU while my eGPU is connected?

Exactly the same MBP and issue on my end.  dGPU kicks on and makes internal screen black and everything sluggish.  Tried booting without eGPU plugged in and forcing iGPU with gfxstatus, then hotplugging eGPU.  External monitors come on, but can only see the mouse while the rest is black.  

Been following this thread and the prior thread since pg41.  I knew I should've just kept Goalque's original script and 10.12 🙂 .  Here's to hoping the great minds figure out a workaround before I get beat. (gf's MBP)

Scratch that.  I just downloaded gfxStatus 2.2.1 and swapped to iGPU.  Wham, perfect.  No lag, all screens work.
https://github.com/codykrieger/gfx.io/blob/gh-pages/downloads/gfxCardStatus-2.2.1.zip


goalque and fr34k liked
ReplyQuote
rmara
(@rmara)
New Member
Joined: 5 months  ago
Posts: 2
May 7, 2018 12:50 am  

So I followed all the steps on my macbookpro 2011 with 10.13.4 17E202 installed
 and I got this answer when trying to run the script : 

marazano-odysseus:~ Richard$ bash <(curl -s https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh)
You use the old wrangler patch. Please follow instructions on eGPU.io/GitHub.
Interrupt...
   cleaning system                                                        [done] The script has failed.
Nothing has been changed.

Anyone having any idea what to do?


ReplyQuote
Artemus80 J.
(@artemus80_j_)
Active Member
Joined: 7 months  ago
Posts: 12
May 7, 2018 2:35 am  

Thank you so much the script was a smooth sail and just like everyone else yes I got the blackscreen if started with eGPU plugged in as well as the "Null " thing.  Those things actually don't bother me and I actually got Premiere and After effects to recognized CUDA, but... unfortunately the performance remain the same.  Could this be because I am using my internal iMac monitor and not external?


ReplyQuote
verichip
(@verichip)
Active Member
Joined: 8 months  ago
Posts: 9
May 7, 2018 5:17 am  

Cool finding! What's your procedure for booting up? Do you boot with the eGPU connected or do you hot-plug it later?

2017 15" Macbook Pro Touchbar (Radeon Pro 555), Gigabyte AORUS Gaming Box (GTX 1070)


ReplyQuote
mzo
 mzo
(@mzo)
New Member
Joined: 2 years  ago
Posts: 3
May 7, 2018 6:49 am  
 
Regarding deleting the KEXT backup before running the new script. I for sure uninstalled the temporary script, and I believe I did it before upgrading to 17E202. Is there a way to double check this before running the new script in case I’m mistaken and actually did run the uninstaller after upgrading to 17E202? Thanks 

ReplyQuote
lexine
(@lexine)
Eminent Member
Joined: 1 year  ago
Posts: 43
May 7, 2018 8:01 am  
Posted by: goalque

@lexine, thanks for the system log. It says the same what @Username reported earlier regarding black screens:

https://egpu.io/forums/mac-setup/wip-nvidia-egpu-support-for-high-sierra/paged/8/#post-22991

WindowServer [ERROR] - Fallback GPU Display Pipe transaction submission failed

Framebuffer issues I guess. I recall there was some driver developer discussions that Apple is going to deprecate IOFramebuffer and said that it is not officially supported.

http://www.displaylink.com/downloads/macos

"We have become aware that installing macOS release Version 10.13.4 will cause DisplayLink connected displays to go blank after the OS upgrade"

Can you try other monitors/display interfaces?

Thanks for the hint, but I am not really sure whether it is the DisplayLink issue. I only have the samsung 4k TV available at the moment, but when I tested I just had the black screen when connected to the egpu via HDMI ... Also when I connect my dell monitor normally via the TB3-- > HDMI connector it is working well ... I will try to dig around a bit, probably I will perform the clean install as soon as I have some time to do it...

2017 13" MacBook Pro TouchBar + [email protected] (Aorus Gaming Box) + macOS10.13 & Win10


ReplyQuote
Baris Oktem
(@baris-oktem)
Active Member
Joined: 11 months  ago
Posts: 17
May 7, 2018 8:46 am  

Is there any possibility to safe eject or disconnect card future updates? Is it possible to make it or is it really hard?


ReplyQuote
ohsoweird
(@ohsoweird)
Active Member
Joined: 1 year  ago
Posts: 11
May 7, 2018 8:46 am  

Hi all, seem to have issues installing the new script.
I have run the previous uninstaller as instructed but still seem to block to continue (on 10.3.4 17E199):

DESKTOP-5GT9TK4:~ michael$ bash <(curl -s https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh)

You use the old wrangler patch. Please follow instructions on eGPU.io/GitHub.

Interrupt...

   cleaning system                                                                                                                                                                  [done]

The script has failed.

Nothing has been changed.


ReplyQuote
ikir
 ikir
(@ikir)
Prominent Member
Joined: 2 years  ago
Posts: 751
May 7, 2018 10:09 am  

Tried with a MacBook Pro 15" 2013 with GT650M and the external screen remain black but it is detected along with eGPU by systems, internal screen is sluggish and lag when eGPU is connected. GPU is Radeon RX Vega 64

eGPU.it | LG 34" 4K 34UC88 curved ultrawide display
MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD --> my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64


ReplyQuote
(@omegajani)
New Member
Joined: 5 months  ago
Posts: 1
May 7, 2018 12:04 pm  
Posted by: rmara

So I followed all the steps on my macbookpro 2011 with 10.13.4 17E202 installed
 and I got this answer when trying to run the script : 

marazano-odysseus:~ Richard$ bash <(curl -s https://raw.githubusercontent.com/learex/macOS-eGPU/master/macOS-eGPU.sh)
You use the old wrangler patch. Please follow instructions on eGPU.io/GitHub.
Interrupt...
   cleaning system                                                        [done] The script has failed.
Nothing has been changed.

Anyone having any idea what to do?

After I made sure, that I have deinstalled every Script I have used before I just reinstalled 10.13.14. 
No clean install - just load the Installer and reinstall Mac OS. Worked for me. Thanks @fr34k for your work btw.


fr34k liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 10 months  ago
Posts: 386
May 7, 2018 12:46 pm  

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


@baris-oktem
I wish we knew.
In theory: signal the driver to perform an eject and your done.
In practice: kextutil unload should do this but a panic occurs. When do we need to call which function. A ton of research will be needed.
-> To answer your question we don't know, yet. It might be easy to fix and only hard to find or hard for both.

macOS-eGPU.sh on GitHub (fr34k's macOS-eGPU.sh on eGPU.io)
----
2016 15'' MacBook Pro + [email protected] (Sonnet Breakaway 550) + macOS 10.13.6 (17G65 driver: 378.10.10.10.30.107 + CUDA: 396.148)


ReplyQuote
Page 5 / 20 Prev Next