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

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

 of  173
  RSS

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

@rivadart,

Does diskutil apfs updatePreboot <yourvolume> fix the boot issue?

In case not, go to recovery (for macOS 11) and restore via time machine snapshot as advised in advanced handbook. That should get you back up and running. 

 

This post was modified 1 month ago

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

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

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
rivadart
(@rivadart)
Active Member
Joined: 1 month ago
 

@mac_editor, recovery was easier than I thought. Just booted from macOS 11 flash drive,Then macOS was restored through a time machine (a copy that was made an hour ago) The script did not have to be applied again. Everything loaded eGPU works. Thank you!

This post was modified 1 month ago

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

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

@rivadart, I need more information to debug why boot failed for you. Did you try the diskutil command?

 

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

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

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
rivadart
(@rivadart)
Active Member
Joined: 1 month ago
 

@mac_editor, No. So, I have to run diskutil apfs updatePreboot <yourvolume> Where <yourvolume> should be my Big Sur volume?

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

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

@rivadart, The diskutil command was an attempt to fix your boot issue, but you restored via Time Machine with eGPU working which does not make sense. What does the script system status say? Also again share full output of diskutil list.

 

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

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

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


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

@mac_editor Thank you!!  It fixed my problem!  My egpu setup is running fine on Big Sur now!

Could you elaborate on exactly what fixed the issue? Did you run both the commands I suggested?

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

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

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
rivadart
(@rivadart)
Active Member
Joined: 1 month ago
 

@mac_editor

Spoiler
System Status

>> PurgeWrangler (master)

 

 1. Setup eGPU

 2. System Status

 3. Uninstall

 

 4. More Options

 5. Donate

 6. Quit

 

>> System Status

 

Ti82 Devices      Disabled

TB1/2 AMD eGPUs   Enabled

Legacy AMD eGPUs  Disabled

NVIDIA eGPUs      Disabled

Web Drivers       Absent

 

Back to menu? [Y/N]: 

 

Spoiler
diskutil list

[email protected] ~ % diskutil list

/dev/disk0 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *1.0 TB     disk0

   1:                        EFI ⁨EFI⁩                     209.7 MB   disk0s1

   2:                 Apple_APFS ⁨Container disk1⁩         819.0 GB   disk0s2

   3:       Microsoft Basic Data ⁨BOOTCAMP⁩                180.4 GB   disk0s3

   4:           Windows Recovery ⁨⁩                        586.2 MB   disk0s4

 

/dev/disk1 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +819.0 GB   disk1

                                 Physical Store disk0s2

   1:                APFS Volume ⁨Macintosh HD — Data⁩   435.4 GB   disk1s1

   2:                APFS Volume ⁨Preboot⁩                 474.7 MB   disk1s2

   3:                APFS Volume ⁨Recovery⁩                2.3 GB     disk1s3

   4:                APFS Volume ⁨VM⁩                      1.1 GB     disk1s4

   5:                APFS Volume ⁨Macintosh HD⁩            11.5 GB    disk1s5

   6:                APFS Volume ⁨AE Projects⁩             139.2 GB   disk1s6

   7:                APFS Volume ⁨macOS11 — Data⁩        8.4 GB     disk1s7

   8:                APFS Volume ⁨macOS11⁩                 14.7 GB    disk1s8

   9:              APFS Snapshot ⁨PurgeWrangler Setup ...⁩ 14.7 GB    disk1s8s1

 

[email protected] ~ % 

Spoiler
System Log

Generating system log...

rsync: link_stat "/Volumes/macOS11 1/Library/Application Support/Purge-Wrangler/io.egpu.purge-wrangler.config.plist" failed: No such file or directory (2)

rsync error: some files could not be transferred (code 23) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-55/rsync/main.c(996) [sender=2.6.9]

rsync: link_stat "/Volumes/macOS11 1/Library/Application Support/Purge-Wrangler/Kexts/." failed: No such file or directory (2)

rsync error: some files could not be transferred (code 23) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-55/rsync/main.c(996) [sender=2.6.9]

Log generated on the Desktop.

 

Open an issue on Github and share this file

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

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

@rivadart, Hmm ok it shows that you are booted off of a patched snapshot, and that your disk is currently patched. So I'm not sure what you restored via Time Machine. Plus there seems to be a bug with system log generator in the script on macOS 11.

If you're willing to try:

  1. Execute the script and uninstall changes.
  2. On successful reboot, eGPU should stop working.
  3. If boot fails, try the diskutil command above for Big Sur volume.
  4. Does boot succeed? If yes, then try patching system again to re-enable eGPU. If not, restore via time machine snapshot.

Btw appreciate the testing. Thanks!

 

This post was modified 1 month ago

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

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

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
killercheung
(@killercheung)
Active Member
Joined: 2 months ago
 
Posted by: @mac_editor
Posted by: @killercheung

@mac_editor Thank you!!  It fixed my problem!  My egpu setup is running fine on Big Sur now!

Could you elaborate on exactly what fixed the issue? Did you run both the commands I suggested?

I run both command kcditto and diskutil apfs updatePreboot in recovery mode as you suggested, after that it boots normally and everything works

details on my case:

1.install script, system patched and no error 

2.reboot, suck on apple logo

3.use the installer usb enter recovery mode, run command you suggested

4.reboot , egpu working!

This post was modified 1 month ago

Macmini 2012 + Sonnect egfx 550 + AMD Radeon RX 570


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

ReplyQuote
 of  173