[SCRIPT] PurgeWrangler: AMD + NVIDIA eGPUs for all Thunderbolt Macs
 

[Solved] [SCRIPT] PurgeWrangler: AMD + NVIDIA eGPUs for all Thunderbolt Macs  

 of  44
  RSS

techyowl
(@techyowl)
Eminent Member
Joined: 3 years ago
 

@jeroen-van-keulen
As far as the patch goes it doesn’t change anything. If you want to reuse the script in the future I’d recommend getting the 1.1.1 as it is safer to use.  If followed the original instructions perfectly then the backup should be fine. If it’s working you should be fine. However, like the readme states when the next MacOS update comes out it recommended to do an uninstall first and the 1.1.1 version has a much safer uninstall procedure.

early-2015 13" MBP Retina + RX580@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter)


ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 
Posted by: Blaine Miller

As far as the patch goes it doesn’t change anything. If you want to reuse the script in the future I’d recommend getting the 1.1.1 as it is safer to use.  If followed the original instructions perfectly then the backup should be fine. If it’s working you should be fine. However, like the readme states when the next MacOS update comes out it recommended to do an uninstall first and the 1.1.1 version has a much safer uninstall procedure.

@techyowl
as for the uninstall:
do you have an idea how I can use launchd to somehow auto-uninstall if an update is queued? (I want to add that into the "do it all")

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

@fr34k
One way would be to monitor the activity log for new processes that spin up during a MacOS update from the App Store and see if some of them are common for every MacOS update and monitor the activity log for that. Another options would be to monitor the MacOS equivalent of syslog which I believe they just call it console log for the update messages. However this won’t work for major version changes as you cannot guarantee the end user will actually complete the update process. Might I recommend something more along the lines of an auto patch tool? The patch is essentially a sophisticated find and replace so if it doesn’t find it no harm done and another patch will hopefully come forward for that version onwards. I believe @Goalque used something similar in the automate-eGPU.sh script.

early-2015 13" MBP Retina + RX580@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter)


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

@techyowl
The problem there is that you would have a process running constantly, draining energy

Theoretically, the kexts should be consistent throughout the systems, so:
What do you think about: (we're clean atm)
sha the .kext and store result at save place
patch
sha the new one and append
--- next execution (maybe after update)
sha kext and reference check
a) match with clean install -> use procedure above
b) match with patch -> patch (if needed, maybe update breaks something)
c) no match at all -> execute repair function for that update to restore clean install -> patch

drawback: a repair function would be needed for every possible update scenario (e.g: .3->.4, .3->.5, .4->.5 etc.)

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
punk.kaos
(@punk-kaos)
Active Member
Joined: 3 years ago
 
Posted by: goalque
Posted by: Michael Schmidt (URBN PXL)
Posted by: punk.kaos

Worked great on my 13in MBA with an RX560 after I patched my kexts for IOPCITunnelCompatible. Thanks a ton!

uhh any info about how you did that ... wanted to get a RX560 to run on my system so I can test it in FCPX

https://egpu.io/forums/mac-setup/app-automate-egpu-by-goalque/paged/2/#post-33291

Yeah, @goalque gave you better instructions than I was going to write. Follow that, its working great. 🙂

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


fr34k liked
ReplyQuote
Brian Duchesneau
(@brian_duchesneau)
Eminent Member
Joined: 2 years ago
 

2012 mac mini - Sonnet box - RX 580

Still getting no screen output even after the 1.1.1 patch.  I ran system_profiler and see the following:

AppleGPUWrangler:

Version: 3.18.48
Last Modified: 8/25/17, 1:05 AM
Bundle ID: com.apple.AppleGPUWrangler
Loaded: No
Get Info String: 3.18.48, Copyright 2016-2018 Apple Inc. All rights reserved.
Obtained from: Unknown
Location: /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGPUWrangler.kext
Kext Version: 3.18.48
Loadable: No
Validity Errors:
Validation Failures:
File access failure; can't open, or I/O error: AppleGPUWrangler
Signature Validation Errors: Kext signature validation error code -1
Dependencies: Incomplete
Signed by: Unknown

2018 macmini i7 32GB/1TB SSD - OWC 650W - RX5700XT / Sonnet Breakaway Box RX/580 - OSX Catalina10.15.1 / Bootcamp


ReplyQuote
techyowl
(@techyowl)
Eminent Member
Joined: 3 years ago
 
Posted by: fr34k

@techyowl
The problem there is that you would have a process running constantly, draining energy

Theoretically, the kexts should be consistent throughout the systems, so:
What do you think about: (we're clean atm)
sha the .kext and store result at save place
patch
sha the new one and append
--- next execution (maybe after update)
sha kext and reference check
a) match with clean install -> use procedure above
b) match with patch -> patch (if needed, maybe update breaks something)
c) no match at all -> execute repair function for that update to restore clean install -> patch

drawback: a repair function would be needed for every possible update scenario (e.g: .3->.4, .3->.5, .4->.5 etc.)

The launchD shouldn’t run on interval only on startup no need to check for patch unless it’s a new startup since every update requires a reboot anyways.

SHA would be more reliable only issue is if the data store gets wiped by something if that’s the case it could build an SHA of an already patched kext and mark it as the Clean SHA why not simply look through the binary that we are modifying and make sure it matches the users thunder bolt version we are already detecting and if it matches do nothing (patch is already applied) if it doesn’t match the version but it does find thunder bolt 3 (current known unpatched state) then assume clean install if it finds nothing (patch won’t work due to massive variation likely from an os update) assume it cannot patch this os version and remove the auto patch launchD daemon. In the last case leave the backup in place and let the user make the decision whether to run a recovery if necessary. We could also store the os version when the backup was created and remove it when the version no longer matches to avoid potential corruptions in future MacOS changes. 

This will work for currently supported patchable os versions as we know what to expect. 

It should also fail gracefully when it breaks from a new os update that changes how the limits are put in place.

It will also apply the current known patch if it hasn’t patched it yet.

early-2015 13" MBP Retina + RX580@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter)


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@techyowl How about matching kext versions (from plist)? If a newer version is detected in /S/L/E/ first update backup, then proceed. Just a thought that popped up.

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro


techyowl liked
ReplyQuote
fr34k
(@fr34k)
Reputable Member Moderator
Joined: 2 years ago
 
Posted by: Blaine Miller
Posted by: fr34k

@techyowl
The problem there is that you would have a process running constantly, draining energy

Theoretically, the kexts should be consistent throughout the systems, so:
What do you think about: (we're clean atm)
sha the .kext and store result at save place
patch
sha the new one and append
--- next execution (maybe after update)
sha kext and reference check
a) match with clean install -> use procedure above
b) match with patch -> patch (if needed, maybe update breaks something)
c) no match at all -> execute repair function for that update to restore clean install -> patch

drawback: a repair function would be needed for every possible update scenario (e.g: .3->.4, .3->.5, .4->.5 etc.)

The launchD shouldn’t run on interval only on startup no need to check for patch unless it’s a new startup since every update requires a reboot anyways.

SHA would be more reliable only issue is if the data store gets wiped by something if that’s the case it could build an SHA of an already patched kext and mark it as the Clean SHA why not simply look through the binary that we are modifying and make sure it matches the users thunder bolt version we are already detecting and if it matches do nothing (patch is already applied) if it doesn’t match the version but it does find thunder bolt 3 (current known unpatched state) then assume clean install if it finds nothing (patch won’t work due to massive variation likely from an os update) assume it cannot patch this os version and remove the auto patch launchD daemon. In the last case leave the backup in place and let the user make the decision whether to run a recovery if necessary. We could also store the os version when the backup was created and remove it when the version no longer matches to avoid potential corruptions in future MacOS changes. 

This will work for currently supported patchable os versions as we know what to expect. 

It should also fail gracefully when it breaks from a new os update that changes how the limits are put in place.

It will also apply the current known patch if it hasn’t patched it yet.

true,
AFAIK one will need a way to omit uninstall before upgrade. Since an update will circumvent launchd. (I don't think a proper logout is performed so a logout hook will also not work...)
EDIT: I don't really know... must be tested. If so: hooray, else: meh.

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

@techyowl How about matching kext versions (from plist)? If a newer version is detected in /S/L/E/ first update backup, then proceed. Just a thought that popped up.

That’s brilliant; definitely more reliable.

early-2015 13" MBP Retina + RX580@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter)


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

@techyowl
do you know if updates only do deltas on .kexts? or do the replace them completely?

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

@techyowl
do you know if updates only do deltas on .kexts? or do the replace them completely?

Complete replacement.

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro


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

@techyowl
do you know if updates only do deltas on .kexts? or do the replace them completely?

Complete replacement.

This simplifies things!

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
Brian Duchesneau
(@brian_duchesneau)
Eminent Member
Joined: 2 years ago
 

After the 1.1.1 installer I see the following when running system_profiler

AppleGPUWrangler:
Bundle ID: com.apple.AppleGPUWrangler
Location: /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGPUWrangler.kext
File access failure; can't open, or I/O error: AppleGPUWrangler
AppleMGPUPowerControl:
Bundle ID: com.apple.driver.AppleMGPUPowerControl
Location: /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleMGPUPowerControl.kext
GPUSupport:
Get Info String: GPUSupport 16.5.10.0.0
Location: /System/Library/PrivateFrameworks/GPUSupport.framework
GPUWrangler:
Location: /System/Library/PrivateFrameworks/GPUWrangler.framework
GPUCompiler:
Location: /System/Library/PrivateFrameworks/GPUCompiler.framework
SafeEjectGPU:
Location: /System/Library/PrivateFrameworks/SafeEjectGPU.framework
Type: GPU

2018 macmini i7 32GB/1TB SSD - OWC 650W - RX5700XT / Sonnet Breakaway Box RX/580 - OSX Catalina10.15.1 / Bootcamp


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

First attempt with Akitio Node and my Mac Mini late 2014 (pre 10.13.4) didn't work because of 3rd party cable and tb3/2 adapter. After I bought both Apple items, the node would turn on. Before, it was a brick. I noticed in system info that  the cable firmware versions is reported.

AKiTiO Node:

 

  Vendor Name: inXtron

  Device Name: AKiTiO Node

  Vendor ID: 0x41

  Device ID: 0x308

  Device Revision: 0x1

  UID: 0x0041537E1088B400

  Route String: 1

  Firmware Version: 25.1

  Port (Upstream):

  Status: Device connected

  Link Status: 0x2

  Speed: Up to 20 Gb/s x1

  Current Link Width: 0x2

  Cable Firmware Version: 1.0.16

  Cable Serial Number: C4M7332013UF798A3

  Link Controller Firmware Version: 0.36.0

 

Not sure if software does anything with it. My experience was total non-function (behaved like hardware). 10.13.4 broke me until Mac_editor's awesome script.

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


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

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


ReplyQuote
Brian Duchesneau
(@brian_duchesneau)
Eminent Member
Joined: 2 years ago
 

I think that is my problem with a 2012 macmini.  I ran the 1.1 script which you did not pass in tb type and it might have picked wrong.  I've tried running the the 1.0 script using tb1 and does not work. Also tried tb2 with the older script.  New script doesn't work at all. Macmini sees the GPU but doesn't load the drivers. If I unplug it complains.

2018 macmini i7 32GB/1TB SSD - OWC 650W - RX5700XT / Sonnet Breakaway Box RX/580 - OSX Catalina10.15.1 / Bootcamp


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago

ReplyQuote
Brian Duchesneau
(@brian_duchesneau)
Eminent Member
Joined: 2 years ago
 

Any help appreciated!

system_profiler | grep GPU

AppleGPUWrangler:
Bundle ID: com.apple.AppleGPUWrangler
Location: /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGPUWrangler.kext
File access failure; can't open, or I/O error: AppleGPUWrangler
AppleMGPUPowerControl:
Bundle ID: com.apple.driver.AppleMGPUPowerControl
Location: /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleMGPUPowerControl.kext
GPUSupport:
Get Info String: GPUSupport 16.5.10.0.0
Location: /System/Library/PrivateFrameworks/GPUSupport.framework
GPUWrangler:
Location: /System/Library/PrivateFrameworks/GPUWrangler.framework
GPUCompiler:
Location: /System/Library/PrivateFrameworks/GPUCompiler.framework
SafeEjectGPU:
Location: /System/Library/PrivateFrameworks/SafeEjectGPU.framework
Type: GPU
Metal: Supported, feature set macOS GPUFamily1 v3
| | | "PCITopLevel" = ("MCHC","P0P2","IGPU","XHC1","EHC2","HDEF","RP01","RP02","RP03","EHC1","LPCB","SATA","SBUS")
| | | "IOPPFDiagDict" = {"ResourceName"="Mac-031AEE4D24BFF0B1.plist","IGPUPLimitDict"={"currentLimit"=0x0,"handlerRegistered"=Yes,"pMin"=0xf,"pMax"=0x0},"DownstreamASPM"={"handlerRegistered"=Yes,"featureSupported"=Yes},"CPUPLimitDict"={"currentLimit"=0x0,"handlerRegistered"=Yes,"pMin"=0x17,"pMax"=0x0},"PLimitVersion"=0x3,"UpstreamASPM"={"handlerRegistered"=Yes,"featureSupported"=Yes},"IdlePLimitDict"={"currentLimit"=0x0,"handlerRegistered"=Yes,"pMin"=0x64,"pMax"=0x0}}
| | | "Machine" = {"Macmini6,1"={"IGPU"={"Heuristic"={"ID"=0x2,"EnableOverride"=0x0},"control-id"=0x10}}}
| | | | | "name" = "ATY_GPU"
| | +-o IGPU@2 <class IOPCIDevice, id 0x1000001fc, registered, matched, active, busy 0 (529 ms), retain 37>
| | | | "acpi-path" = "IOACPIPlane:/_SB/[email protected]/[email protected]"
| | | | "attached-gpu-control-path" = "IOService:/AppleACPIPlatformExpert/[email protected]/AppleACPIPCI/[email protected]/[email protected]/AGPM"
| | | | | "FeatureControl" = {"EnablePlaneRotation"=0x1,"GPUInterruptHandling"=0x1,"UseInterruptFilter"=0x1,"EDPDownSpreadDisable"=0x0,"FastDisplayDetectDisable"=0x0,"SpreadON"=0x1,"PowerStates"=0x1,"IgnorePanelTimings"=0x0,"GammaAdjustDisable"=0x0,"DisableDynamicFBC"=0x0,"RCxEIModeEnable"=0x1,"EnableDeepDisplay"=0x1,"MaximumSelfRefreshLevel"=0x3,"EnableConnectionState"=0x1,"DPM"=0x1,"CachedEDIDDisable"=0x0,"DeepRC6"=0x1,"ASRDisable"=0x0,"Gamma"=0x1,"FBC"=0x1,"RenderStandby"=0x1,"SetRC6Voltage"=0x0,"UseProgrammedCoefficients"=0x0,"Wate$
| | | | | | "Config4" = {"IGPU"={"unload"=Yes},"display"={"EDID"={"index"=0x0},"FeatureControl"=0xc,"unload"=No},"GFX0"={"EDID"={"index"=0x0},"FeatureControl"=0xc,"unload"=No}}
| | | | | | "Config3" = {"IGPU"={"unload"=Yes},"GFX0"={"EDID"={"index"=0x0},"FeatureControl"=0xc,"unload"=No}}
| | | | | "IOAccelTypes" = "IOService:/AppleACPIPlatformExpert/[email protected]/AppleACPIPCI/[email protected]/IntelAccelerator"
| | | | | "IOAccelTypes" = "IOService:/AppleACPIPlatformExpert/[email protected]/AppleACPIPCI/[email protected]/IntelAccelerator"
| | | | | "IOAccelTypes" = "IOService:/AppleACPIPlatformExpert/[email protected]/AppleACPIPCI/[email protected]/IntelAccelerator"
| | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/[email protected]/AppleACPIPCI/[email protected]/[email protected]/display0/AppleDisplay-5c85-1905"
| | | | "IOUserClientCreator" = "pid 578, SafeEjectGPUServ"
| | | | "IOUserClientCreator" = "pid 578, SafeEjectGPUServ"
+-o AppleGPUWrangler <class AppleGPUWrangler, id 0x100000515, registered, matched, active, busy 0 (5 ms), retain 10>
| | "IOClass" = "AppleGPUWrangler"
| | "CFBundleIdentifier" = "com.apple.AppleGPUWrangler"
| | "IOMatchCategory" = "AppleGPUWrangler"
| +-o AppleGPUWranglerClient <class AppleGPUWranglerClient, id 0x10000059b, !registered, !matched, active, busy 0, retain 5>
| +-o AppleGPUWranglerClient <class AppleGPUWranglerClient, id 0x100000604, !registered, !matched, active, busy 0, retain 5>
| +-o AppleGPUWranglerClient <class AppleGPUWranglerClient, id 0x1000006fa, !registered, !matched, active, busy 0, retain 5>
| | "IOUserClientCreator" = "pid 578, SafeEjectGPUServ"
| +-o AppleGPUWranglerClient <class AppleGPUWranglerClient, id 0x1000007c4, !registered, !matched, active, busy 0, retain 5>
| "IOUserClientCreator" = "pid 578, SafeEjectGPUServ"
| "IOUserClientCreator" = "pid 578, SafeEjectGPUServ"
2018-04-06 14:22:12.859 system_profiler[833:25875] ### System cache - version is invalid...
2018-04-06 14:22:12.859 system_profiler[833:25875] building SYSTEM cache...
2018-04-06 14:22:12.890 system_profiler[833:25875] Filtering out duplicate preference bundle "/System/Library/PreferencePanes/PrintAndFax.prefPane"
2018-04-06 14:22:12.991 AllowPasswordPref[836:25884] error == Error Domain=com.apple.LocalAuthentication Code=-6 "Biometry is not available on this device." UserInfo={BiometryType=0, NSLocalizedDescription=Biometry is not available on this device.} isSupported == 0
2018-04-06 14:22:12.992 AllowPasswordPref[836:25884] Hardware Check err == 0
2018-04-06 14:22:12.993 AllowPasswordPref[836:25884] Result -1
2018-04-06 14:22:13.104 system_profiler[789:25190] ### System cache - version is invalid...
2018-04-06 14:22:13.104 system_profiler[789:25190] building SYSTEM cache...
2018-04-06 14:22:13.113 system_profiler[789:25190] Filtering out duplicate preference bundle "/System/Library/PreferencePanes/PrintAndFax.prefPane"
2018-04-06 14:22:13.166 AllowPasswordPref[841:25920] error == Error Domain=com.apple.LocalAuthentication Code=-6 "Biometry is not available on this device." UserInfo={BiometryType=0, NSLocalizedDescription=Biometry is not available on this device.} isSupported == 0
2018-04-06 14:22:13.167 AllowPasswordPref[841:25920] Hardware Check err == 0
2018-04-06 14:22:13.167 AllowPasswordPref[841:25920] Result -1
Name: ATY_GPU
2018-04-06 14:22:16.216 system_profiler[789:25762] ### writing SYSTEM cache...
macmini:~ duchesne$

2018 macmini i7 32GB/1TB SSD - OWC 650W - RX5700XT / Sonnet Breakaway Box RX/580 - OSX Catalina10.15.1 / Bootcamp


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

Tested on Mid-2012 13" MacBook Pro TB1:

Screen Shot 2018 04 06 at 2.44.12 PM

I noticed that sometimes hot-plugging in the first time does not work. Later hot-plugs work. This was using an unreleased version of the script, but the patch remains the same.

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro


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

Also working fine on my Mid-2014 MPB 15" 🙂

Given up on all my Macs...but successfully running: Gigabyte Designare Z390, Core i9-9900K, 64GB RAM, 2x Internal GTX 1080TI, 2x GTX 1070 eGPU (Sonnet eGFX)


itsage and mac_editor liked
ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@techyowl Could you test the latest commit at your leisure? Specifically the backup part (you can simulate an old version of macOS by modifying the manifest.wglr file, then attempting re-patch).

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro


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

Nvidia eGPU's not working on my side. Kernel Panic!
Anyone had any success? Installed the latest webdriver from Nvidia, the CUDA drivers and NVDAEGPUSuppor-v8.zip. After installed purge-wrangler.sh version 1.1.1. No luck. As soon as I connect the box I get a kernel panic. 

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


ReplyQuote
Brian Duchesneau
(@brian_duchesneau)
Eminent Member
Joined: 2 years ago
 

Glad you guys have had some success.  For me me I'm outa luck.

2012 MacMini - Sonnet Breakaway Box - RX - 580

worked fine until 10.13.4

I've tried all the scripts, none work so far.

2018 macmini i7 32GB/1TB SSD - OWC 650W - RX5700XT / Sonnet Breakaway Box RX/580 - OSX Catalina10.15.1 / Bootcamp


ReplyQuote
PsyPryss
(@psypryss)
Trusted Member
Joined: 2 years ago
 

Tested Grid Autosport with 10.13.4. 3D acceleration improved tremendously from 10.12.6.

Mid 2012 15" (Non-Retina) MPB GT650M + RX580 (AKiTio Node via TB3 -> TB2/TB1 Adaptor) macOS 10.13.4/Win10


itsage and mac_editor liked
ReplyQuote
Brian Duchesneau
(@brian_duchesneau)
Eminent Member
Joined: 2 years ago
 

I appreciate your help from all of you. Unfortunately I'm unable to get this working using a macmini 2012.  See my my comments before for more detail.

I appreciate the help of the moderators up until the advice was reinstall the OS.  So long. This is why I quit Windows a while ago.

2018 macmini i7 32GB/1TB SSD - OWC 650W - RX5700XT / Sonnet Breakaway Box RX/580 - OSX Catalina10.15.1 / Bootcamp


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: rhenriques11

Nvidia eGPU's not working on my side. Kernel Panic!
Anyone had any success? Installed the latest webdriver from Nvidia, the CUDA drivers and NVDAEGPUSuppor-v8.zip. After installed purge-wrangler.sh version 1.1.1. No luck. As soon as I connect the box I get a kernel panic. 

As mentioned in the primary post, more patching is required. Replace AppleGPUWrangler from 10.13.3 and put it into your current install. It might work.

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro


ReplyQuote
(@peter_gelderbloem)
Active Member
Joined: 2 years ago
 
Posted by: mac_editor
Posted by: rhenriques11

Nvidia eGPU's not working on my side. Kernel Panic!
Anyone had any success? Installed the latest webdriver from Nvidia, the CUDA drivers and NVDAEGPUSuppor-v8.zip. After installed purge-wrangler.sh version 1.1.1. No luck. As soon as I connect the box I get a kernel panic. 

As mentioned in the primary post, more patching is required. Replace AppleGPUWrangler from 10.13.3 and put it into your current install. It might work.

Where do we get AppleGPUWrangler for 10.13.3 if I may ask?

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


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago

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

Thanks mac_editor. I'm going to try that one shortly. 
Cheers

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


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: rhenriques11

Thanks mac_editor. I'm going to try that one shortly. 
Cheers

This method is mentioned in the main post. Always check back there for updates 😉

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro


ReplyQuote
Brian Duchesneau
(@brian_duchesneau)
Eminent Member
Joined: 2 years ago
 

I tried that but TM doesn't show that directory as available for retrieve ??

2018 macmini i7 32GB/1TB SSD - OWC 650W - RX5700XT / Sonnet Breakaway Box RX/580 - OSX Catalina10.15.1 / Bootcamp


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: Brian Duchesneau

I tried that but TM doesn't show that directoty as available for retrieve ??

Don't do it through the Time Machine app (from the menu bar). Go into your disk and retrieve it via Finder please. Also save a copy of the original kext.

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro


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

mac_editor, unfortunately it didn't work. Same kernel panics. Very strange.

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


ReplyQuote
(@ziggy029)
Active Member
Joined: 2 years ago
 
Posted by: Brian Duchesneau

Glad you guys have had some success.  For me me I'm outa luck.

2012 MacMini - Sonnet Breakaway Box - RX - 580

worked fine until 10.13.4

I've tried all the scripts, none work so far.

Interesting -- same here.  I also have a 2012 Mini and an RX580, but with a Mantiz Venus enclosure.  Same thing, script does nothing and the external GPU remains unseen by the system.  Using script version 1.1.1.  

Any reports from anyone using a 2012 Mini in general or a 2012 Mini/RX 580 combo in particular who got it to work?

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


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: manuelg

It's working here with a mac mini 2012 and a Sonnet Breakaway box with a RX580, using script version 1.0.0.   However, when I first ran the script using 

sudo ./purge-wrangler.sh patch tb1

it didn't work at all, so I uninstalled it and then re-installed it using the tb2 option

sudo ./purge-wrangler.sh patch tb2

 

and then the screen came right up.  I haven't tried version 1.1.0 since everything seems to be working well at this point.

2012 Mac mini users, please try this. Use version 1.0.0 of the script and patch for TB2 and see if it works. In your console logs, when you hot-plug AMD eGPU, please check for an activity related to "AMD" - if there isn't then there is trouble detecting the GPU rather than with the patch because even without the patch, there is "AMD" activity.

purge-wranglerpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro


ReplyQuote
 of  44