[Sticky] [SCRIPT] Enable AMD & NVIDIA eGPUs on TB1/2/3 Macs on macOS 10.13.4+  

Page 33 / 33 Prev
  RSS

cdbell7686
(@cdbell7686)
New Member
Joined: 1 month ago
Posts: 3
January 27, 2019 11:12 pm  

I'm running a 2011 MBP High Sierra 10.13.6 with the dGPU disabled and purchased a Gigabyte RX 580 Gaming Box.  
I have run through the steps of the Purge Wrangler script.  
But when I try to boot with the gaming box, the computer won't fully boot.  When I try to hotplug the gaming box, the computer stops functioning (well, the mouse moves on the screen, but nothing will click)
Does anyone have any insight before I eat $70 on a restocking fee for this Gaming Box?

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


ReplyQuote
XPi
 XPi
(@xpi)
New Member
Joined: 4 weeks ago
Posts: 3
January 28, 2019 1:14 pm  

Maybe I'm stupid but, I followed the sparsely described process on the github repo and everythin went nice, with no result. I plug the egpu on booting, after login, re-login, but in any moment the Mac seems to detect neither the eGPU or the External Display.
I've been working with the eGPU without mayor problems with the learex/macOS-eGPU for a week (except slow UI, solved with DisableMonitor).

Edit: I've been able to make it work after some reinstallation tests. But I have the same slow UI problem, that I solved with the same method. Do you know a better way?

 

Mac configuration:
MacBook Pro (15-inch, 2017), MacOS 10.13.6 , 2,9 GHz Intel Core i7, 16 GB 2133 MHz LPDDR3, Radeon Pro 560 4096 MB
Intel HD Graphics 630 1536 MB

EGPU: Razer Core X with NVIDIA GTX 1070

This post was modified 3 weeks ago

MacBook Pro (15-inch, 2017) / macOS 10.13.6 / Razer Core X / NVIDIA GeForce GTX 1070


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
January 28, 2019 4:19 pm  

@xpi See hardware chart and more tools in the documentation (see Black Screens issue - same workarounds apply). It's a known issue. You can try steps in the automate-eGPU EFI main post for switching to iGPU, or disabling your iGPU. DisableMonitor seems like a good workaround.

This post was modified 3 weeks ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
ataylor
(@ataylor)
Active Member
Joined: 6 months ago
Posts: 16
February 5, 2019 1:27 am  

Ok. here is an odd one.. before i go sell all my GTX-9 series cards..  Using purge-wrangler script on a 2018 15 in macbook pro with touchbar - i can't seem to get the machine to like more than one egpu unless they are the same kind.  i.e 2 1080s seem to work. but 1 1080 and 1 980Ti don't
i only see the one that i plug in first.. the other one is listed as - nvidia chip model.

Do they need to be all the same family? 9series or 10 but not a mix? I would love to get both 1080's and both 980Ti's running on the 2018 MacbookPro 15 i9

i attached my AGDCD

This post was modified 2 weeks ago

2018 MacBookPro 15 in. /w Touchbar - i9 - 32gig ram - 1080 Aorus 1080 Gaming Box - Sonnet-Breakaway550 with GTX 1080 - Still need to get both of the GTX 980TI working for 4 GTX total cards


ReplyQuote
hvdtuan
(@hvdtuan)
Active Member
Joined: 2 weeks ago
Posts: 5
February 7, 2019 7:16 pm  

Hello,
I bought the Apple Adapter Thunderbolt Adapter 3 to Thunderbolt 2 and Sonnet eGFX + AMD RX 580 + and the Thunder Cable 2 for my Macbook Pro Retina 13 End 2013 under OS High-Sierra. I disabled SIP, installed Purge Wrangler and verified in system state (7) - TB1 / 2 AMD eGPUS: enabled.

After starting my Macbook Pro, it detects the AMD RX 580 graphics card.

Is it possible to choose, my Macbook Pro works with the AMD graphics card ?

How will I be able to test the AMD graphics card that it runs on my Macbook Pro ?

Thank you

Macbook Pro 15-2011, Macbook Pro Retina 13-2013, Macbook Pro Retina 15-2012, Macbook Pro Retina 15-2015, Imac 27 2013
Sonnet eGFX 550 + AMD RX 580


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 7, 2019 8:04 pm  

@hvdtuan use activity monitor - CMD+4. Rest was mentioned in the script documentation on github (basically see Apple eGPU doc or use set-eGPU). You can upgrade to Mojave. 

This post was modified 2 weeks ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
hvdtuan
(@hvdtuan)
Active Member
Joined: 2 weeks ago
Posts: 5
February 8, 2019 8:15 pm  

Thank you for your answer, but I have another questions. I've managed to make my E-Gpu work with my external monitor. The problem is want it to work with my internal monitor and i've made some research and I know I must have a ghost display. Do  I have to buy a headless HDMI adaptor or is there another way to create a ghost display ? And if I have to buy a headless adptor wich one should I choose ? 
Is this one good ?

Thank you.

Macbook Pro 15-2011, Macbook Pro Retina 13-2013, Macbook Pro Retina 15-2012, Macbook Pro Retina 15-2015, Imac 27 2013
Sonnet eGFX 550 + AMD RX 580


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 8, 2019 8:45 pm  

@hvdtuan you don’t need a ghost adapter on Mojave, and only need one on High Sierra for some OpenGL apps, alongside set-eGPU. Any adapter will do. I’ve personally never used one though.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
OliverB
(@oliverb)
Honorable Member
Joined: 4 months ago
Posts: 609
February 8, 2019 10:28 pm  
Posted by: mac_editor

@hvdtuan you don’t need a ghost adapter on Mojave, and only need one on High Sierra for some OpenGL apps, alongside set-eGPU. Any adapter will do. I’ve personally never used one though.

I don't have ghost adapter. But there are cases when you need one without monitor. E.g. in one game the use of the second gpu is only possible when a "monitor" is plugged in. (That is for windows of course)

This post was modified 2 weeks ago

2018 15" MBP & 2015 13" MBP connected to RTX2080Ti GTX1080Ti GTX1080 Vega56 RX580 R9-290 GTX680


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 8, 2019 10:31 pm  

@oliverb Which case? In Windows we have the GPU preferences option. Plus some games have in-built options to select rendering GPU (F1 2018 for instance). IIRC the adapter is only needed for High Sierra + set-eGPU + OpenGL, or older macOS eGPU configurations (Sierra, etc.).

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
OliverB
(@oliverb)
Honorable Member
Joined: 4 months ago
Posts: 609
February 8, 2019 10:55 pm  
Posted by: mac_editor

@oliverb Which case? In Windows we have the GPU preferences option. Plus some games have in-built options to select rendering GPU (F1 2018 for instance). IIRC the adapter is only needed for High Sierra + set-eGPU + OpenGL, or older macOS eGPU configurations (Sierra, etc.).

@mac_editor, this one. I couldn't get it to use a second (e)GPU without a monitor being connected to it.

I solved it by connecting my monitor with two cables (Displayport and HDMI)

This post was modified 2 weeks ago

2018 15" MBP & 2015 13" MBP connected to RTX2080Ti GTX1080Ti GTX1080 Vega56 RX580 R9-290 GTX680


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 8, 2019 11:02 pm  

@oliverb second eGPU is an edge case and is kind of irrelevant to the issue discussed here, but good to know! Also the performance boost is quite nice if one has another eGPU lying around. Pretty cool.

This post was modified 2 weeks ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
OliverB
(@oliverb)
Honorable Member
Joined: 4 months ago
Posts: 609
February 8, 2019 11:12 pm  
Posted by: mac_editor

@oliverb second eGPU is an edge case and is kind of irrelevant to the issue discussed here, but good to know! Also the performance boost is quite nice if one has another eGPU lying around. Pretty cool.

Ashes of the Singularity is not my kind of game, but from a technical point of view, it's great. It splits up sections of the screen and distributes tasks to render certain sections to the GPUs . Very interesting.

2018 15" MBP & 2015 13" MBP connected to RTX2080Ti GTX1080Ti GTX1080 Vega56 RX580 R9-290 GTX680


ReplyQuote
ataylor
(@ataylor)
Active Member
Joined: 6 months ago
Posts: 16
February 8, 2019 11:23 pm  

In doing 3d rendering connecting monitor is problematic... So for now in using 3 GTX 1080s. For real time rendering for octane and redshift!   Mostly Cuda stuff have the screen hooked up to TB via Apple dongle.. In theory I could use 4 cards if I want to hook the monitor to one... But seems to be hard to make happy.

2018 MacBookPro 15 in. /w Touchbar - i9 - 32gig ram - 1080 Aorus 1080 Gaming Box - Sonnet-Breakaway550 with GTX 1080 - Still need to get both of the GTX 980TI working for 4 GTX total cards


ReplyQuote
hvdtuan
(@hvdtuan)
Active Member
Joined: 2 weeks ago
Posts: 5
February 10, 2019 1:20 pm  
Posted by: mac_editor

@hvdtuan you don’t need a ghost adapter on Mojave, and only need one on High Sierra for some OpenGL apps, alongside set-eGPU. Any adapter will do. I’ve personally never used one though.

Hello mac_editor
I installed the set-eGPU on my Macbook Pro Retina 15-inch OS Mojave, in PCI menu says Management installed: no.

There is also no display on the external display.

set-eGPU compatible with Macbook Pro Retina with Thunderbol 1 ?

Thank you

This post was modified 1 week ago

Macbook Pro 15-2011, Macbook Pro Retina 13-2013, Macbook Pro Retina 15-2012, Macbook Pro Retina 15-2015, Imac 27 2013
Sonnet eGFX 550 + AMD RX 580


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 10, 2019 5:28 pm  

@hvdtuan Please read the entire documentation. Your 15” Mac may have an NVIDIA dGPU that would require purge-nvda as well (read its doc entirely if needed as well). You won’t need the latter if you don’t use external monitor or adapter (which Mojave doesn’t require anyway). 

This post was modified 1 week ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
hvdtuan
(@hvdtuan)
Active Member
Joined: 2 weeks ago
Posts: 5
February 12, 2019 6:59 pm  
Posted by: mac_editor

@hvdtuan Please read the entire documentation. Your 15” Mac may have an NVIDIA dGPU that would require purge-nvda as well (read its doc entirely if needed as well). You won’t need the latter if you don’t use external monitor or adapter (which Mojave doesn’t require anyway). 

I have finally managed to make my Egpu work with my computer with an external monitor and an internal monitor due to an adaptor HDMI that I've made. Thank you, by the way you've helped me a lot.

Macbook Pro 15-2011, Macbook Pro Retina 13-2013, Macbook Pro Retina 15-2012, Macbook Pro Retina 15-2015, Imac 27 2013
Sonnet eGFX 550 + AMD RX 580


ReplyQuote
kataplof
(@kataplof)
New Member
Joined: 3 days ago
Posts: 2
February 17, 2019 12:32 pm  

Hi,

I tried to perform the options indicated in the forum (purge-wrangler.sh and automate-eGPU EFI) and in both I have the following problem, when starting the computer with the eGPU connected, after advancing the load bar halfway, later I stay in a black screen

If I perform the steps of purge-wrangler.sh and connect the eGPU once I have booted the system, it detects it and shows it to me in the graphics / screens section. Note that in the step of installing the web drivers, it shows me the following warning:
Latest Available Driver: 17G5019
Your macOS Build: 18D109
Recommendation: Major OS version discrepancy detected. Patching not recommended.

If I don't install it, it does not detect the eGPU, if I install it, it detected but with the problems indicated here.

When I connect it with the system already started (the system detects it), if I open the cinema 4D with octane, the program remains frozen, if I remove the eGPU, the program works without problems (in the octane case, it loads but does not use it) for not having the eGPU.

I think the problem with the cinema 4D may come because the system is not able to start with the eGPU connected.

Summing up all this, someone could help me with:

  1. Any idea / solution for the black screen at startup?
  2. Any solution to the problem with cinema 4D and octane?

The detail of my computer and the eGPU is the following:
iMac (Retina 5K, 27 inches, 2017)
Processor 3.8 GHz i5
Graphics Radeon Pro 580 8192 MB
Mojave 10.14.3 OS

Aorus gtx 1080 gaming box

I've been looking for the forum but I did not find something to solve my problem, if there is something I have not seen, my apologies for opening a new post, if you can direct me I would appreciate it.

Many thanks in advance to anyone who can help me.

A greeting.

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 17, 2019 12:57 pm  

@kataplof read the script documentation on github (see install notes).

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
kataplof
(@kataplof)
New Member
Joined: 3 days ago
Posts: 2
February 17, 2019 5:17 pm  

Hi @mac_editor,

Thank you very much for the help. I have reviewed the documentation and followed the steps indicated in the prerequisites and then the following ones to the installation.

When you have indicated to me that you read the documentation in relation to the installation, you refer to the section 'Note About NVIDIA Setups' ?, if so, I do not know if you want to say that for versions 10.14 and major it is not possible to perform the installation, is it right? if yes, do you know if a solution is foreseen in the short term?

If you did not refer anything to this, could you specify a bit more than part of the documentation should I review?

Again, thanks for everything.

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 18, 2019 1:44 am  

@kataplof that’s the correct inference. macOS 10.14 isn’t supported only because there are no Web Drivers for it. I would say no - I would not bank on support from NVIDIA/Apple anytime soon in case eGPU is essential for your work. You may alternatively use High Sierra.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
(@nath_dee)
New Member
Joined: 2 weeks ago
Posts: 3
February 18, 2019 7:19 am  

Hi I seem to not able to get RTX 2080 to work on high sierra with this script

my setup is
- razer core x 
- AsUs Stris RTX 2080
- Macbook pro late 2014 iris graphic (thunderbolt 2)

It is because i might run the script wrong or is it because RTX is not supported yet 

thank you for your help

This post was modified 2 days ago

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 18, 2019 7:20 am  

@nath_dee RTX drivers are needed for macOS. Currently not available.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
(@nath_dee)
New Member
Joined: 2 weeks ago
Posts: 3
February 18, 2019 7:22 am  

Thank you so much for your quick reply, understood 😊🙏🏻

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


mac_editor liked
ReplyQuote
(@nath_dee)
New Member
Joined: 2 weeks ago
Posts: 3
February 18, 2019 7:28 am  

My current set up
- Razer core X
- Macbook pro late 2014 iris graphic (thunderbolt 2)

If RTX 2080 have no driver yet, if i buy Vega 64 to use in the mean while waiting for 2080 driver. Would the Vega 64 work?

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 19, 2019 7:31 am  

@nath_dee Compatibility is mentioned in the documentation. It would work.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


ReplyQuote
baggio89
(@baggio89)
New Member
Joined: 2 weeks ago
Posts: 4
February 19, 2019 10:35 pm  

Hello there 🙂 

Just wanted to let you know, that since the last update on purge-nvda and purge-wrangler my setup stopped working.

I used both (wrangler for AMD setup and nvda to disable dGPU).

Setup:

Razer Core X

AMD Radeon Vega 56

Macbook pro late 2013 15inch retina

Everything worked fine before, but now i cant boot into macOS anymore loading bar gets stuck at 50%...

Tried 10 / 15 times by reinstalling scripts, save mode etc...

But everytime i have purge-nvda AMD eGPU's installed, boot is failing 🙁 

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 19, 2019 10:37 pm  

@baggio89 Known issues section for purge-nvda. This is likely the script causing your boot issues (purge-wrangler doesn't affect boot typically).

This post was modified 8 hours ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


baggio89 liked
ReplyQuote
baggio89
(@baggio89)
New Member
Joined: 2 weeks ago
Posts: 4
February 19, 2019 11:27 pm  

Thanks! @mac_editor for the fast reply! :O 

I can confirm that purge-wrangler is working fine.

Once installed i can connect my eGPU and it recognizes it. Then because i have Intel iris pro + NVDIA GeForce GT 750M i have to install purge-nvda and choose option 1 (AMD eGPU's) to overcome the black screen on my external monitor. Before, this worked fine and sometimes i had boot problems but then i just uninstalled purge-nvda via safe mode, reinstalled and then it booted correctly and my eGPU works as expected, plug and play. 

But now... after the new purge-nvda update, when install and choose option 1 and reboot, it gets stuck.... Then i uninstall purge-nvda and i can boot again... but when i reinstall purge-nvda it gets stuck again, and again, and again... 

Am i missing something, or could this problem be in the latest update?

If you can point me in the right direction to install purge-nvda 3.0.2 i can test if the previous release solves the problem 🙂 

I know this command below installs (release/latest) but im not sure how to get release/3.0.2 installed...

curl -q -s " https://api.github.com/repos/mayankk2308/purge-nvda/releases/latest " | grep '"browser_download_url":' | sed -E 's/.*"browser_download_url":[ \t]*"([^"]+)".*/\1/' | xargs curl -L -s -0 > purge-nvda.sh && chmod +x purge-nvda.sh && ./purge-nvda.sh && rm purge-nvda.sh

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 19, 2019 11:33 pm  

@baggio89 Instead of uninstalling purge-nvda, try running the Set Mux to iGPU option. This is the mentioned workaround in the Known Issues section. I am not sure what's causing the failures (see purge-nvda thread), but basically it is beyond control. What essentially helps is running the patch in Single User Mode. I am also working on an update (3.0.4) which has some refinements and re-adds a prompt to reboot from the script itself (at the end of a patch) - though it may still face the same issue. It doesn't help that I don't have my 2014 NVIDIA MBP anymore, so I'm testing (at least the mux setting) on a 2018 MBP which seems to be working for me. Please let me know how it goes.

To install 3.0.2 or any older release, you can go the Releases page on Github, download the script for the version you need, launch terminal, and do:

cd ~/Downloads # Assuming the script was downloaded here
bash purge-nvda.sh
This post was modified 7 hours ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


baggio89 liked
ReplyQuote
baggio89
(@baggio89)
New Member
Joined: 2 weeks ago
Posts: 4
February 20, 2019 12:19 am  

Great! thanks @mac_editor 

I did the following: 
downloaded the previous version of purge-nvda (3.0.2)

cd "location of downloaded .sh file" 
chmod +x purge-nvda.sh
sudo ./purge-nvda.sh 

With 3.0.2 installed i picked option 1(AMD eGPU's), rebooted and everything works fine...  💡 

Seems there is some difference in the latest release (3.0.3) which causes the boot issue everytime. 
To look into this further i could try the workaround mentioned in the knows issues as you referred. 

To proceed i need to understand this: 

Because of the unknown impact of the mux variable in EFI, the patches are sometimes partially applied, thus resulting in an unbootable system. Booting into single user mode and running the workaround re-sets the mux correctly and completes the patch.

When rebooting into single user (cmd + r) what is the workaround or what command do i type? cause the script is not accessible via terminal... it replies "command not found" 


You also mentioned:

What essentially helps is running the patch in Single User Mode, 

How do i do that? 
Im quite new to terminal, but i grasp the concept... i guess 🙂 hehe 

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 1844
February 20, 2019 12:30 am  

@baggio89 When you run the script in the manner described above, a copy is installed in /usr/local/bin. This location is already in the default macOS PATH (hence you can subsequently type purge-nvda only). In Single User Mode (⌘ + S while booting), you need to first mount your root disk:

mount -uw /
# then
purge-nvda
# Use Set Mux to iGPU option

From 3.0.2 -> 3.0.3 I didn't change the patch, except the sleep time applied after the patch. For 3.0.4 I have reverted the time back to what it was (5s). If you would like, I can send over 3.0.4 to you before release (@psypryss as well, if you have some time for testing). It would be great if you could test that out. No point in releasing an update if there's no resolution.

The meaning of the quoted statements is essentially this:

When you set the mux preference (which is an NVRAM command in the script), the preference is written in the NVRAM (which is basically non-volatile memory useful for reading boot information). But, sometimes the firmware just does not read the mux preference -> mux does not change (stays on dGPU) -> another NVRAM command disabled dGPU -> boot stuck.

Ideally mux changes to iGPU, dGPU is disabled, and reboot succeeds on iGPU. The statement in italics sometimes does not happen (for unknown reasons).

This post was modified 6 hours ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
----
Multiple Build Guides


baggio89 liked
ReplyQuote
baggio89
(@baggio89)
New Member
Joined: 2 weeks ago
Posts: 4
February 20, 2019 1:06 am  

Great explanation @mac_editor thanks! 
Mounting the root makes sense as single user only loads command line interface.
From there i will change mux to iGPU, (try to) boot on iGPU while the dGPU is disabled.

Will test if this makes any difference in version 3.0.3 and will post the outcome.
Would be happy to test 3.0.4 also in the morning (02:00 AM in the Netherlands hehe).
Send it over and i will look into this.

Thanks for you assistance! 

:mrgreen: would be great if NVIDIA and AMD could work simultaneously, so you can use clamshell and backlight 

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


ReplyQuote
Page 33 / 33 Prev