Setup & Software Discussions
[SCRIPT] PurgeWrangler: AMD + NVIDIA eGPUs for all Thunderbolt Ma...
 

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

Page 5 / 37
  RSS

(@dukebound85)
New Member
Joined: 1 year ago
Posts: 3
Apr 7, 2018 12:50 am  

Thank you so much for this and getting me back up and running.

However, has anyone else had their egpu performance drop dramatically from 10.13.3 to 10.13.4?

I am running a 2012 13" mbp with TB 1 and a mantiz with a RX 570

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


ReplyQuote
rmvz3
(@rmvz3)
Trusted Member
Joined: 2 years ago
Posts: 50
Apr 7, 2018 1:00 am  

Any Nvidia eGPU success case until now? I'll try it tomorrow if I can retrieve the needed file from Time Machine. Is there any way to know if it is the right version besides the date, by the way?

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


ReplyQuote
drunknbass
(@drunknbass)
Active Member
Joined: 1 year ago
Posts: 6
Apr 7, 2018 2:14 am  

I 'think' when there are updates the updates will get put into a folder then it reboots to that 'blessed' location to perform the update. Maybe you can detect this?

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


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 1 year ago
Posts: 39
Apr 7, 2018 3:00 am  

Finally succeed to mount a Aktio or a Sonnet Box (both with Nvidias GTX1080Ti) into my MBP mid 2015.
Hot plug works but to disconnect we have to shutdown the machine. Trying to eject from the widget will crash the machine. 
The method was to install new Nvidia web drivers for 10.13.4, Cuda drivers and NVDAEGPUSuppor-v8.zip. 
After exchange the AppleGPUWrangler.kext by the version from 10.14.4 beta 1. Finally use the mac_editor suggested commands to repair permissions. 

$ sudo chown -R root:wheel /System/Library/Extensions/

$ sudo chmod -R 755 /System/Library/Extensions/

$ touch /System/Library/Extensions/

the last line was only successful by using sudo, like this:

$ sudo touch /System/Library/Extensions/

After I've just restarted and things work as they used to work in 10.13.3. The only advantage now is that we can use the eGPU without the need to logout and log in again. 

I've noticed that there's some unsuitability with some apps, like the Luxmark benching app. Agisoft Photoscan also works just fine but, after quit the "send crash log to developer appears. However, despite this small issue, the app works just fine. Blender also sees the Nvidia and can use CUDA without problem. 
Waiting for the refining but, for now, seems to be fine. 

I was able to simultaneously connect 2 NV 1080Ti eGPU's to the MBP 2015 but they seem to create some instability in several apps. They are recognized by the system but the do not seem to be able to work together. This is probably more a limitation of the TB2 controller of the MBP 2015 because, even before, it was impossible to have 2 eGPU working in this machine. 
Cheers

 

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


ReplyQuote
Blaine Miller
(@techyowl)
Eminent Member
Joined: 2 years ago
Posts: 46
Apr 7, 2018 3:31 am  
Posted by: mac_editor

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

I made another pull request on the GitHub repo. it seems to function really well. I noticed you removed the auto reboot (maybe a silent option would run that but a normal patch could prompt the user Y/n defaulting to yet to reboot on user input) The sea is probably way simpler to implement and may for obvious reasons be more reliable in enforcing structure with the unknown. Changing the .wglr file to have 10.13.3 made it realize it needed to update the backup after that fix I committed. Re-running the patch seems to handle the existing backups. the new version politely ignores the previous backup methods. I also validated the backup contained the TB3 string in its hex like the current stock binary has. I didn't check this between executions but changing the macOS version line to 10.13.3 that forced it to rerun could theoretically overwrite a valid backup however uninstalling and rerunning the patch seems to keep the correct version in the backup directory (given you set remove previous backups or modify the macOS version in the .wglr file so that the patch recreates the backup from an uninstalled(or unpatched) binary).

All that to say if it is used without user modifications, it will be safe.

if you try to use it on an unsupported macOS version like 10.11 or something off like that it doesn't handle that.

Everything else it handles and seems to check reliably.

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 2093
Apr 7, 2018 3:35 am  

@techyowl already merged it 😉 nice catch that one haha. The broader checks for different os versions and hardware will be handled in a bigger ‘super script’ so to speak, courtesy of @fr34k.

Also the .wglr extension and superuser permissions are in place to ‘dissuade’ people from modifying it. Not that they can’t. Now we could check that too, but that’d be a bit much lol. 

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


ReplyQuote
Blaine Miller
(@techyowl)
Eminent Member
Joined: 2 years ago
Posts: 46
Apr 7, 2018 4:14 am  
Posted by: mac_editor

@techyowl already merged it 😉 nice catch that one haha. The broader checks for different os versions and hardware will be handled in a bigger ‘super script’ so to speak, courtesy of @fr34k.

Also the .wglr extension and superuser permissions are in place to ‘dissuade’ people from modifying it. Not that they can’t. Now we could check that too, but that’d be a bit much lol. 

I look forward to the 'Super Script' I had a feeling @fr34k was working on something along those lines.
Yeah if the end user modify's those backups lets just assume they either know what they are doing or are willing to accept fault. There is somewhat of a reason Apple puts a mask on all the magic behind the curtains and discourages everyone from touching things they shouldn't. Doesn't stop those who know there way around things.

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


fr34k and mac_editor liked
ReplyQuote
Sovereign
(@sovereign)
Active Member
Joined: 2 years ago
Posts: 19
Apr 7, 2018 10:53 am  

Got it to work too on my Mac Pro. It boots with the eGPU attached only, monitor connected to eGPU. Boots a bit slower though than normal. I used the kext from 13.3.2, didn't have one from 13.3.3 anymore.

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


theitsage liked
ReplyQuote
rmvz3
(@rmvz3)
Trusted Member
Joined: 2 years ago
Posts: 50
Apr 7, 2018 12:42 pm  
Posted by: rhenriques11

Finally succeed to mount a Aktio or a Sonnet Box

Congratulations. Then you don't need to use the PureWrangler script, are you?
The missing hot unplug feature makes this unusable for me anyway. :/ What happens when you close the lid? Will it restore correctly?

It would be nice if someone uploaded the AppleGPUWrangler.kext from 10.14.1 beta 1

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


ReplyQuote
Sovereign
(@sovereign)
Active Member
Joined: 2 years ago
Posts: 19
Apr 7, 2018 1:17 pm  
Posted by: rmvz3
Posted by: rhenriques11

Finally succeed to mount a Aktio or a Sonnet Box

Congratulations. Then you don't need to use the PureWrangler script, are you?
The missing hot unplug feature makes this unusable for me anyway. :/ What happens when you close the lid? Will it restore correctly?

It would be nice if someone uploaded the AppleGPUWrangler.kext from 10.14.1 beta 1

Correct, if you're copying over AppleGPUWrangler.kext you just need to set permissions. 

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


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 1 year ago
Posts: 39
Apr 7, 2018 1:19 pm  

Hi rmvz3. I did not need to use the script. After the installation of the needed Nvidia files (Driver, CUDA and NVDAEGPUSupport-v8, I've just used the AppleGPUWrangler.kext from 10.13.4 beta 1 and did the mac_editor suggested commands for permission repair. Closing the lid shuts the monitor light but will deactivate password protection. After reopen the lid the computer will be immediately available. Shutdown works fine but logout does not work. If we try to logout the monitor goes black and stays that way until a forced restart. 
All the rest it's working just fine. HotPlug for itself it is a great add because sometimes I have the computer on, with work ongoing and now I do not need to log out and in anymore.   

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


ReplyQuote
rmvz3
(@rmvz3)
Trusted Member
Joined: 2 years ago
Posts: 50
Apr 7, 2018 1:55 pm  
Posted by: rhenriques11 HotPlug for itself it is a great add because sometimes I have the computer on, with work ongoing and now I do not need to log out and in anymore.   

Thank you for answering rhenriques11 and Sovereign. In fact, the hot plug feature was the main reason for me to test this thing because I never boot my mac (only for booting with bootcamp), just open/close the lid. I don't want to have to remember to shut down and boot every time (and switch on/off the eGPU PSU). With hot-plug however I would plug the eGPU only when I wanted.

I'll try if I can, anyway. Always is good to have the option to use the 1070 if I need it.

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


ReplyQuote
rmvz3
(@rmvz3)
Trusted Member
Joined: 2 years ago
Posts: 50
Apr 7, 2018 2:10 pm  

Great! I can live with that! Thank you for your help, rhenriques11.

BTW, where is supposed to be the AppleGPUWrangler.kext? I can't find it anywhere. Also, I don't think I have a proper Time Machine version of it :/

EDIT: I've found GPUWrangler.framework in library/PrivateFrameworks. Is this it?

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


ReplyQuote
Sergey White
(@sergey-white)
New Member
Joined: 1 year ago
Posts: 1
Apr 7, 2018 2:31 pm  

Thanks a ton!!!!!))))

I have got a success. My devices are:

  1. Mid 2015, 15 i7 2,5 16gb + AMD Radeon R9 M370X + Intel Iris Pro
  2. Akitio tunder 2
  3. MSI Radeon RX 560 4gb

I had got nothing or black screens after I have installed then script 1.1.1.  Then I started to read posts and I found some extra. This is the link. https://egpu.io/forums/mac-setup/app-automate-egpu-by-goalque/paged/2/#post-33291

So..
1) I pasted into "/System/Library/Extensions/AMDRadeonX4000.kext/Contents/Info.plist" directory key from the link above.
2) re-install  sudo ./
purge-wrangler.sh

CHEEEERRRSSS!!!!!!!!

Mid-2015 15" MacBook Pro M370X + MSI RX560 4GB TB2 (AKiTiO Thunder2) + macOS 10.13.4


theitsage liked
ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
Posts: 4034
Apr 7, 2018 2:50 pm  
Posted by: rmvz3
Posted by: rhenriques11

Finally succeed to mount a Aktio or a Sonnet Box

Congratulations. Then you don't need to use the PureWrangler script, are you?
The missing hot unplug feature makes this unusable for me anyway. :/ What happens when you close the lid? Will it restore correctly?

It would be nice if someone uploaded the AppleGPUWrangler.kext from 10.14.1 beta 1

Distributing files from beta software is not allowed.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

94 external GPU build guides


goalque liked
ReplyQuote
André Santos Silva
(@andre_santos_silva)
Active Member
Joined: 2 years ago
Posts: 14
Apr 7, 2018 3:19 pm  

confirm it works on a 2013 13 rMBP. Thanks for your work!

late-2013 13" Macbook Pro Retina + [email protected] (Sonnet Greakaway 350 via TB3->TB2 adapter) + macOS10.13 & Win10


theitsage liked
ReplyQuote
Sovereign
(@sovereign)
Active Member
Joined: 2 years ago
Posts: 19
Apr 7, 2018 3:27 pm  
Posted by: rmvz3

Great! I can live with that! Thank you for your help, rhenriques11.

BTW, where is supposed to be the AppleGPUWrangler.kext? I can't find it anywhere. Also, I don't think I have a proper Time Machine version of it :/

EDIT: I've found GPUWrangler.framework in library/PrivateFrameworks. Is this it?

It is in /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/

I'm using the kext from 13.3.2. Works also.

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


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 1 year ago
Posts: 39
Apr 7, 2018 4:20 pm  

Just upgraded my MacPro late 2013 and things are also working just fine with 2 external NV Geforce 1080Ti. The first time the machine start and we connect the GPUs, CUDA seems not to work correctly with some apps. After reinstalling CUDA and restart things are very smooth. As theitsage says, do not distribute beta .kext from apple because is not allowed. I recommend you to first backup your machine (I've used Carbon Copy Cloner) and then upgrade. This way you can get the AppleGPUWrangler.kext from the previous system and use the purposed methodology. 

As a final Conclusion, It's hard to understand why apple did this modification into AppleGPUWrangler.kext. It is not that hard for Apple engineers to automate the modification that we are doing for ourselves. It leads us to think that TB/TB2 deliberate blockage it's a planned obsolescence for sales increase... which is a very bad way of doing business and mines costumers trust. 

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


ReplyQuote
philw
(@philw)
Trusted Member
Joined: 2 years ago
Posts: 75
Apr 7, 2018 5:13 pm  

I have a Time Machine copy of AppleGPUWrangler.kext that says in Get Info that it is Version 3.16.2 – would that be the correct one?
Thanks!

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)


ReplyQuote
Sovereign
(@sovereign)
Active Member
Joined: 2 years ago
Posts: 19
Apr 7, 2018 5:23 pm  
Posted by: philw

I have a Time Machine copy of AppleGPUWrangler.kext that says in Get Info that it is Version 3.16.2 – would that be the correct one?
Thanks!

Dunno if that came from 13.3.3, but the AppleGPUWrangler.kext from 13.3.2 is also version 3.16.2.

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


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 1 year ago
Posts: 39
Apr 7, 2018 5:30 pm  

Version in 10.13.3 is 3.16.2.

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


ReplyQuote
breakaway550
(@breakaway550)
New Member
Joined: 1 year ago
Posts: 2
Apr 7, 2018 5:39 pm  

I installed the script 1.1.1 on mid 2014 MBP 15 running 10.13.4.  the OS recognized the RX580 card in Breakaway 550 box but there's nothing on the external monitor.  Has anyone had same issues as mine?  any fix please.

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


ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
Posts: 4034
Apr 7, 2018 5:45 pm  

@rhenriques11 Another possible reason Apple blocked TB1/2 Macs from external GPU in 10.13.4 is to comply with Intel eGFX certification. In my observations, sleep and wake-up with an attached eGPU are not reliable. I wish Apple had given more explanation of non-TB3 exclusion.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

94 external GPU build guides


goalque liked
ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 1 year ago
Posts: 39
Apr 7, 2018 6:04 pm  

I hope so theitsage . If that's the case they should explain it.
Well, at least we have lots of talented people here that were able to find a solution. This is working really well in the MacPro late 2013!!

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


theitsage liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 2093
Apr 7, 2018 6:08 pm  
Posted by: breakaway550

I installed the script 1.1.1 on mid 2014 MBP 15 running 10.13.4.  the OS recognized the RX580 card in Breakaway 550 box but there's nothing on the external monitor.  Has anyone had same issues as mine?  any fix please.

If your mac has discrete NVIDIA GPU, use purge-nvda.sh (in my signature) as well.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 2093
Apr 7, 2018 6:09 pm  
Posted by: theitsage

@rhenriques11 Another possible reason Apple blocked TB1/2 Macs from external GPU in 10.13.4 is to comply with Intel eGFX certification. In my observations, sleep and wake-up with an attached eGPU are not reliable. I wish Apple had given more explanation of non-TB3 exclusion.

It might just be this - but they sure have done a lazy job of excluding TB1/2 from what I've seen.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


theitsage liked
ReplyQuote
Sovereign
(@sovereign)
Active Member
Joined: 2 years ago
Posts: 19
Apr 7, 2018 6:10 pm  
Posted by: mac_editor
Posted by: theitsage

@rhenriques11 Another possible reason Apple blocked TB1/2 Macs from external GPU in 10.13.4 is to comply with Intel eGFX certification. In my observations, sleep and wake-up with an attached eGPU are not reliable. I wish Apple had given more explanation of non-TB3 exclusion.

It might just be this - but they sure have done a lazy job of excluding TB1/2 from what I've seen.

Don't ever encourage them to do better.  :mrgreen:

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


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 1 year ago
Posts: 39
Apr 7, 2018 6:20 pm  

This is outstanding!! Check what appears in the menu bar eGPU widget if we startup with the eGPU connected to the monitor instead of the internal GPU! The name is recognized correctly. 

Screen Shot 2018 04 07 at 19.13.40

If two are connected, they appear just fine in the system profiler

Screen Shot 2018 04 07 at 19.21.14

but the name of the second one will be generic into the widget

Screen Shot 2018 04 07 at 19.21.25

It seems that the ports where we connect the eGPU's matter. Things seem only to work great if I connect to port 2 and 5. Otherwise some apps have CUDA errors.

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


charleszhao, PsyPryss, mac_editor and 3 people liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
Posts: 1418
Apr 7, 2018 7:00 pm  
Posted by: rhenriques11

This is outstanding!! Check what appears in the menu bar eGPU widget if we startup with the eGPU connected to the monitor instead of the internal GPU! The name is recognized correctly.

Dual screen output working?

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 1 year ago
Posts: 39
Apr 7, 2018 7:09 pm  
Posted by: goalque
Posted by: rhenriques11

This is outstanding!! Check what appears in the menu bar eGPU widget if we startup with the eGPU connected to the monitor instead of the internal GPU! The name is recognized correctly.

Dual screen output working?

I have a Monitor directly connected to the CPU and another connected to one of the eGPUs. Both working good. The other external eGPU is just for processing. Agisoft photoscan, for instance, can use all available GPUs for calculations.

Here's how processing power is distributed accordingly to the processing power of each GPU. Notice how the once (in 2013) top notch AMD Fire Pro 500 now pales when compared to the Nvidias. 

Screen Shot 2018 04 07 at 20.16.50

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


ReplyQuote
rmvz3
(@rmvz3)
Trusted Member
Joined: 2 years ago
Posts: 50
Apr 7, 2018 8:35 pm  
Posted by: Sovereign

It is in /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/

Thank you, Sovereign.

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


ReplyQuote
charleszhao
(@charleszhao)
Active Member
Joined: 1 year ago
Posts: 11
Apr 7, 2018 8:41 pm  

"i have the same problem after i discrete NVIDIA GPU, use purge-nvda.sh, and also enable egpu on tb2 script. reboot and plug; the interal screen freez and external screen have no output signal. 

my mac is a late 2013 mbp retina with gtx 750m with Breakaway and rx580 8g"

guess what, not work just because my rx580 is something wrong, after i fixed the card, the script works fine

WX20180423 225132@2x
Snip20180421 1

 

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


ReplyQuote
Sickntired
(@sickntired)
New Member
Joined: 1 year ago
Posts: 3
Apr 7, 2018 9:32 pm  

This thread has allowed me to use my AMD Vega 64 with my Mac Mini 2014 very easily!  Thanks!

However, I also have an Nvidia 1080 Ti that I would prefer to use because of its speed and because the card is quieter. 

What exactly do I need to do to get the 1080 Ti card working?  I haven't actually connected it yet as I wanted to be sure I did any necessary steps first. 

Thank you for any help!

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


ReplyQuote
(@rhenriques11)
Eminent Member
Joined: 1 year ago
Posts: 39
Apr 7, 2018 9:35 pm  
Posted by: rmvz3
Posted by: Sovereign

It is in /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/

Thank you, Sovereign.

From my experience, the AppleGPUWrangler.kext from 10.13.3 seems to be a lot more stable than the one from 10.13.4 Beta1. You will notice, in some cases, a slower startup, but the overall stability seems to be a lot better after. I was experiencing, in the beginning  occasional hangs during shutdown and, sometimes, the second eGPU failed to mount. Now it's solved with AppleGPUWrangler.kext 3.16.2 from MacOS 10.13.3. 

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


ReplyQuote
(@brian_duchesneau)
Eminent Member
Joined: 1 year ago
Posts: 21
Apr 7, 2018 9:41 pm  

I second this statement. I was unable to get my Mac mini 2012 with a Sonnet box and RX580 to work with any of the scripts.

I was able to copy the 10.13.3 kext from Time Machine, rebuild kext cache and now all is working fine.

2012 macmini i5 2.5Gz 16GB/1TB SSD - Sonnet Breakaway Box RX/580 - OSX Mojave 10.14.1


ReplyQuote
(@brian_duchesneau)
Eminent Member
Joined: 1 year ago
Posts: 21
Apr 7, 2018 10:09 pm  

Yes. I had the same problem. I ended up restoring the kext from 10.13.3 via Time Machine and rebuilt the kext cache manually from the command line.

i think there might be an issue with one of the scripts that I used from here that did either incorrect tb1/2 detection patching and/or incorrect kext cache regeneration. I know I used the early version that would overwrite the original backup, so maybe that was part of my problem too.

i’ve read In one of the posts of a user that used the original script prior to tb1/2 auto detect having to pass in tb2 on a tb1 Mac mini to get it working. With that switch removed and now relying on auto detect being the only option.

i hope if the above is true the guys providing us help can fix this before the next OSX update reverts these changes.

Either way, thanks to all the folks in this forum for all the help and guidance this week.

2012 macmini i5 2.5Gz 16GB/1TB SSD - Sonnet Breakaway Box RX/580 - OSX Mojave 10.14.1


ReplyQuote
Page 5 / 37