Setup & Software Discussions
automate-eGPU EFI - eGPU boot manager for macOS and Windows
 

automate-eGPU EFI - eGPU boot manager for macOS and Windows  

 of  23
  RSS

jamesgrean
(@jamesgrean)
Active Member
Joined: 2 years ago
 

Possibly silly question, scanned a couple of pages here but not all 15...

I sometimes run into issues booting the Mac Pro (trashcan) if I have certain USB devices connected. I have a couple of external USBs, one main culprit is a backup dock.

Anyway, does the EFI USB have to be the only USB drive plugged in at boot? I have another USB drive with a library of files on it, is there a USB boot order preference (device 1, then 2... if so which is which?)

Am I looking to remove the current method (Rastafabi's, no disrespect, but I like the idea of the USB activating and then unplugging to be a normal mac) and switching to this EFI loader.

I take it we have to install the Nvidia drivers separately then? I've been trying to update using Dobell's script but I can't get it to work. What is the preferred method of getting the correct drivers on?

Currently 378.05.05.05f02 but trying to get to 378.05.05.25f12 as per instructions from Octane render staff for 10.12.4-10.12.6. I guess I could update the OS but don't want to touch what isn't broken, or do too many steps at once (makes troubleshooting harder if I update OS, drivers, and boot method all together!).

Cheers

JG

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


ReplyQuote
montenegroexperte
(@montenegroexperte)
Eminent Member
Joined: 8 months ago
 

For me it not worked. I removed usb, reboot, update, usb in again. Start. Egpu detected but screen black.

now i dont know what to do. Sonnet puck 570 for sale now

MacMini Late 2012, Sonnet Puck 570


ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@montenegroexperte  Once booted with eGPU detected and you end up with black screen, how long did you wait before giving up or powering off ?  I had cases where it would take some time, i.e. > 45 seconds before the screen would show up.  When it did not, I would unplug and plug back my Cinema Display cable on the nMP and it would work then.  FYI, my eGPU is connected to a headless adapter rather than external display.

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
montenegroexperte
(@montenegroexperte)
Eminent Member
Joined: 8 months ago
 

Not working, i can wait 10 minutes and nothing happes. Before the update everything was fine

MacMini Late 2012, Sonnet Puck 570


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 

@montenegroexperte Reboot twice clean into macOS without the USB stick. Then use the installer link my signature to re-create your EFI stick. Then use that to boot.

@jamesgrean this solution is for macOS 10.13.4+.

This post was modified 7 months ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + Vega 64 [Sonnet Breakaway 350 -> 600W]


slhdsnet liked
ReplyQuote
montenegroexperte
(@montenegroexperte)
Eminent Member
Joined: 8 months ago
 

no itvstarted. Egoubdetecred but black screen like after the update

MacMini Late 2012, Sonnet Puck 570


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 

@montenegroexperte try the purge-wrangler next I guess.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + Vega 64 [Sonnet Breakaway 350 -> 600W]


ReplyQuote
montenegroexperte
(@montenegroexperte)
Eminent Member
Joined: 8 months ago
 

I not understand why befor update everything was ok abd now not

MacMini Late 2012, Sonnet Puck 570


ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@montenegroexperte  I guess all is fine (before & after the update) when you boot into macOS without the eGPU connected ?  Can you confirm ?

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
montenegroexperte
(@montenegroexperte)
Eminent Member
Joined: 8 months ago
 

Yes. Without usb an without egpu all ok

MacMini Late 2012, Sonnet Puck 570


slhdsnet liked
ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@montenegroexperte  What is your screen layout configuration, i.e. what type screen and how is it connected to the nMP without the eGPU to begin with ?  Which TB port are you connected to on the nMP ?  Is the screen connected from the eGPU via the HDMI port for your screen output ?

This post was modified 7 months ago

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
montenegroexperte
(@montenegroexperte)
Eminent Member
Joined: 8 months ago
 

MacMini 2012. one screen to hdmi, other thunderbolt to sinnet puck. As i told until the os update all perfect

MacMini Late 2012, Sonnet Puck 570


slhdsnet liked
ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@montenegroexperte OK, MacMini 2012 configuration.  I understand your screen is thus connected to the HDMI port on the mini and you get the black screen via eGPU connected.  Do you have a second screen you can connect directly to the puck, preferably via one of the three display port, not the HDMI ?

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
montenegroexperte
(@montenegroexperte)
Eminent Member
Joined: 8 months ago
 

One screen hdmi at the mini. Second screen at rhe puck

MacMini Late 2012, Sonnet Puck 570


slhdsnet liked
ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@montenegroexperte  Black on both screens when eGPU connected ???

This post was modified 7 months ago

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
montenegroexperte
(@montenegroexperte)
Eminent Member
Joined: 8 months ago
 

No hdmi at mini works

MacMini Late 2012, Sonnet Puck 570


slhdsnet liked
ReplyQuote
Xabazios
(@xabazios)
New Member
Joined: 7 months ago
 

Dear Specialists,
its the first time ever, i join a forum to talk about my technical problems 😀 - I've one you maybe can help me out to solve it.

My Build:

  • MacBook Pro 13 (i7, Intel Iris 655) is connected via TB3-Cable (USB-C) to the Razer Core X
  • External Monitor (LG 43UD79) is connected via DisplayPort-Cable to the AMD RX Vega 64 (inside the Razer Core)
  • OS: MacOS Mojave / Windows 10 (bootcamp)

My Problem:

  • When I boot Windows-Bootcamp ( eGPU is plugged in via USB-C-Cable), the internal Monitor of my MacBook begins to flicker while displaying the blue windows icon on loading screen. After a few seconds, my external monitor displays the original windows-login-screen and i can use windows with my eGPU. The performance is very good while playing games via steam e.g. but my internal monitor of my macbook ist still hanging in the loading screen of windows, while displaying the flickering blue icon.

Additional Information:

  • In my device-manager, the internal intel GPU doesn't appear, only the Vega 64 is displayed
  • when I try to boot without the external Monitor, i have the same flickering at the boot-screen on my macBook and nothing happens

It would be very very nice if you could help me out. I am thankful for every idea or hint.
Best regards from germany
xabazios

This post was modified 7 months ago

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


ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@montenegroexperte  OK good.  Hence, you can see your displays arrangement in the Displays preferences tab.

1.  Are you seeing the "Mirror Displays" and "Gather Windows" as available options or not ?
2.  What GPU is being listed in the Graphics of the About This Mac Overview panel ?
3.  What exact Sonnet GPU model are you running, i.e. RX 560, 570 or 580 ?

This post was modified 7 months ago

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
(@chris_moran)
Active Member
Joined: 12 months ago
 

@xabazios when you boot to mojave, do the internal laptop monitor and the eGPU work as expected?

2018 15” MacBook Pro i9 32GB 1TB + AMD Radeon Pro 560x + 550w Sonnet breakaway + AMD Radeon RX 580 + macOS 10.14.2 & Win 10 (1803)


ReplyQuote
Xabazios
(@xabazios)
New Member
Joined: 7 months ago
 

yes, for mojave it boots normally with the egpu plugged in. Exept the bootcamp boot - there, my external monitor starts windows by using the razer core, but the internal monitor still displays the windows boot icon while its flickering a little bit - like mini graphic-errors.

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


ReplyQuote
montenegroexperte
(@montenegroexperte)
Eminent Member
Joined: 8 months ago
 

Now its working. Dont now why. I also can see the small icon for the egpu. Really strange.

Only one problem still - after restart it still needs much time aftet the bell to come the apple logo. Is there a way that it boots automatic without pushing q and enter? My mac starts alonr every morning....

MacMini Late 2012, Sonnet Puck 570


slhdsnet liked
ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@montenegroexperte  Really strange indeed.  Given we use automate-eGPU EFI Loader to begin with and this prior the macOS kernel loading, I do not believe an automatic boot is possible...

FYI - Might be of help to you and/or others but I did notice something quite different after I updated to 10.14.3 altogether.  With the 10.14.2 version, my nMP would boot and show being connected to the internal D300 GPU's by default, i.e. primary display.  On the About This Mac Hardware tab, I would then see all the 3 GPU's (2 x D300 and 1 x RX 580) listed.  But then, after the update to 10.14.3 was done, rebooted and since then its always the RX 580 showing up by default as well as being first in the list when I run the Activity Monitor GPU History process.  In 10.14.2 it was always the two D300 showing first and second respectively with the RX 580 showing third.  Now its RX 580 listed first every time.  Not really sure what that entails but my eGPU works as expected.

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 
Posted by: montenegroexperte

Now its working. Dont now why. I also can see the small icon for the egpu. Really strange.

Only one problem still - after restart it still needs much time aftet the bell to come the apple logo. Is there a way that it boots automatic without pushing q and enter? My mac starts alonr every morning....

If you used the installer link in my signature to create the EFI stick, the installer adjusts the patch for AMD eGPUs (eGPU icon shows up). Normally the EFI stick patch is for NVIDIA by default (which happens to let AMD work on TB1/2 as well, but without the icon).

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + Vega 64 [Sonnet Breakaway 350 -> 600W]


slhdsnet liked
ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@mac_editor  Do not think I did yet but wanted to sincerely THANK YOU many times for the automate-eGPU EFI Installer which got me hooked into trying eGPU on my nMP to begin with.  Thanks again.   😉 

This post was modified 7 months ago

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 

@slhdsnet You're most welcome. @goalque's implementation actually has tremendous possibilities. For example, it could easily be customized for enabling Ti82 support as well as disabling discrete GPUs. I feel he has left it as homework for other users, as people sometimes should take the effort to dive into the nitty gritty details - which I think is great, but then I went and made a little script to automate the automation (for AMD-NVIDIA differences at least) lol.

This post was modified 7 months ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + Vega 64 [Sonnet Breakaway 350 -> 600W]


goalque and slhdsnet liked
ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@mac_editor  Two words come to mind...  "Awesome Work"  you did.  Keep doing !!!  Cheers.   🙂 

This post was modified 7 months ago

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: mac_editor

@slhdsnet You're most welcome. @goalque's implementation actually has tremendous possibilities. For example, it could easily be customized for enabling Ti82 support as well as disabling discrete GPUs. I feel he has left it as homework for other users, as people sometimes should take the effort to dive into the nitty gritty details - which I think is great, but then I went and made a little script to automate the automation (for AMD-NVIDIA differences at least) lol.

The key section is KernelAndKextPatches in config.plist which does the dirty job:

https://clover-wiki.zetam.org/Configuration/KernelAndKextPatches

You can add your own, no necessity to run scripts because this EFI approach is supposed to be scriptless.

On top of Clover, I have added the following new keys:

DropThunderbolt (default=false)
MuxSetting (default=0)
SkipSetupDataForOSX (default=true)

But everything else is as described in Clover documentation.

On the other hand, thanks to you @mac_editor for providing a nice piece of automation. You can edit the starting post and add your own section with a download link if you like. It's also worth shedding some light on what the script does to KernelAndKextPatches if users prefer to edit the config.plist manually.

I encourage everyone to study the contents of config.plist, its internal workings based on Clover documentation. For example, CsrActiveConfig that determines the SIP status. Feel free to decode base64 strings to hexadecimal format and discover new, better patches as your homework, but discussion about the actual reverse engineering (regarding Apple's binary files) and using reverse engineering tools is prohibited on this forum.

Some patches are done invisibly and by copyright protection because history has shown that eGPU workarounds tend to go places where some people make stealthy hackintosh business. I had to make a decision between going open source or protecting key hacks, and I chose the latter.

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 

@goalque Yep, familiar with KernelAndKextPatches in Clover. What I meant by "your implementation" was that it does not have the extra baggage (amazing work by the Hackintosh community though) that comes with Clover for Hackintoshes so it's super easy to configure with no known significant side effects so far (not so with vanilla Clover). I noticed in your description you mentioned issues outputting to eGPU-connected monitors (slow rendering). This is also an issue at the login screen on the 2018 MBP with FileVault enabled. I have yet to check on 10.14.4 beta though.

Some patches are done invisibly and by copyright protection because history has shown that eGPU workarounds tend to go places where some people make stealthy hackintosh business.

True. The purge-wrangler repo does get hits from the Bizon website and some Chinese websites (though these seemed more news outlets and blogs than anything else).

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + Vega 64 [Sonnet Breakaway 350 -> 600W]


goalque and slhdsnet liked
ReplyQuote
slhdsnet
(@slhdsnet)
Trusted Member
Joined: 8 months ago
 

@goalque  I must admit,  "Awesome Work"  you also do and keep doing as well !!!  From my perspective and having read lots of threads on the eGPU.io forum, you and @mac_editor have been very instrumental and key in making this easier to comprehend for us all.  I for one would not have had the expertise to code and implement fixes and/or scripts such as you did.  Without these, things would have been much harder, maybe impossible to tackle.

On behalf of many I am sure in the eGPU.io community, thanks again for your hard work and dedication to the cause.

With kind regards,
@slhdsnet

nMP-Mac Pro (Late 2013) with AMD FirePro D300's (x2)
✧ macOS Mojave 10.14.5 (18F132) ✧
automate-eGPU EFI (v1.0.5) USB ✧
OWC Mercury Helios FX eGPU / AMD Radeon RX Vega 56 8GB / Apple TB3-TB2 Cable Adapter ✧
✧ NewerTech HDMI Headless Video Adapter ✧


ReplyQuote
(@chris_moran)
Active Member
Joined: 12 months ago
 

@xabazios just for kicks let's give this a try:

1. Boot into windows WITHOUT the eGPU connected.
2. Run DDU and clean your system of all remnants of any drivers.
3. Once you reboot after DDU, try installing Adrenalin drivers from here (start with v18.8.2)
4. Reboot after installation ( DO NOT CONNECT eGPU)
5. Once windows loads shut down.
6. Boot into windows but this time plug in your eGPU.

Let me know what happens.

 

This post was modified 7 months ago

2018 15” MacBook Pro i9 32GB 1TB + AMD Radeon Pro 560x + 550w Sonnet breakaway + AMD Radeon RX 580 + macOS 10.14.2 & Win 10 (1803)


ReplyQuote
igor10k
(@igor10k)
New Member
Joined: 10 months ago
 

Successfully using this EFI to boot into Windows using Razer Core X with 1070 on 2016" MBPr (Pro 460) for a few weeks already and it's pretty stable. A couple of issue were encountered but none of them critical:
1. When switching from macOS to Windows I always have to boot into Windows twice in a row. First time Windows boots using the integrated graphics card even though the eGPU is connected. I have to boot into Windows once again to have the 1070 detected and working.
2. No way to change display brightness in Windows. I wish there was some terminal command to do that. Or maybe even forcing some fixed brightness level to always be used in Windows. Because right now looks like the only way to change it is to boot into macOS and then boot back into Windows twice because of the issue above.
3. In some rare cases Windows throws some kind of BSOD when loading but that's very rare and third reboot always helped so far.

But even with all of that the EFI is a very usable solution so once again thanks for all the hard work @goalque !

2016 15" MacBook Pro with Radeon Pro 460 + Razer Core X + nvidia GTX 1070 + automate-eGPU EFI + Win10


goalque liked
ReplyQuote
steve500
(@steve500)
Eminent Member
Joined: 11 months ago
 

Working beautifully with an Aorus Gaming box with Vega 56 Nano in Windows 1803 on a 2018 i7 13" Macbook Pro. Thank you very much for this. 

To avoid use of a USB stick, what is the possibility of adding these efi boot files to my internal SSD's EFI partition?

I was previously successful at this by adding a separate tiny partition to my internal drive and copying the automate-efi folder to it and would allow me to choose it on startup separate of my main EFI boot partition but now that I have redone my bootcamp installation, I forgot to leave a bit of empty drive space to make a separate efi boot partition and as fragile APFS is, I don't want to boot to windows to resize my NTFS volume smaller, lol. Any tips?

This post was modified 7 months ago

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


ReplyQuote
alphatoad
(@alphatoad)
New Member
Joined: 7 months ago
 

Thank you. I have a question: is this EFI open sourced? I can only find binary files.
thanks!

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
 

@alphatoad This is not open sourced. The app is based on Clover, which is open source.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + Vega 64 [Sonnet Breakaway 350 -> 600W]


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
 

The main post has been updated to include the automate-eGPU EFI Installer and some insight into what the installer does.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + Vega 64 [Sonnet Breakaway 350 -> 600W]


ReplyQuote
its_dy1an
(@its_dy1an)
New Member
Joined: 7 months ago
 
Posted by: dalroi

Here's an attempt to a step-by-step for my 2012 Mini with AMD eGPU.

Initial setup:

  1. Open a Terminal.
  2. If your shell is bash, the default Terminal shell, go to the next step - otherwise type bash. Apparently, mac_editors command line is not valid in (at least) tcsh, which happens to be my favourite shell.
  3. Plug in an USB stick that you don't mind getting overwritten. Note its name on the desktop. Make sure it's name does not contain EFI.
    Note: I had to repartition the stick with exFAT (it's a 16GB stick and DOS/FAT is ancient enough to have trouble with that size) because information on it got damaged somehow in an earlier attempt.
  4. Optional: Eject and unplug all other writable USB media to prevent accidentally overwriting the wrong device (your backups, for example).
  5. Copy-paste mac_editors command in Terminal and follow the steps there (that's where the name of your USB stick comes in): 
    bash <(curl -s   https://egpu.io/wp-content/uploads/2018/11/automate-eGPU-EFI-install.txt) 
  6. Remove the file apple_set_os.efi from EFI/CLOVER/drivers64UEFI/ on your USB stick. The 2012 Mini is one of those Mac's that don't need it. My eGPU hasn't activated once with this file  in the EFI stick, so it matters.
  7. Eject the USB stick.
  8. Shut down the Mac.
  9. Unplug the thunderbolt cable; I also powered off the eGPU and let everything settle for a few minutes.
  10. Plug in the USB stick.  The stick doesn't need to be plugged directly in an USB port on your Mac, BTW, an USB hub should work just fine.

Steps for every boot of your Mac:

  1. Turn on the eGPU enclosure (if you turned it off), but don't connect the Thunderbolt cable to the Mac yet.
  2. Turn on the Mac with the Option-key (Alt on a PC keyboard) pressed until you see a list of disks to choose from. If you see the Apple logo instead, something went wrong; perhaps the keyboard didn't get detected, or Option is the wrong key after all (I don't use Apple keyboards).
  3. Choose your USB stick to boot from.
  4. Press q
  5. Start Mac OS from the menu.
  6. Log in.
  7. Plug in the Thunderbolt cable.
  8. Log out (Cmd-Shft-Q).
  9. At this point, the eGPU should activate.

If you noticed that there are no pmset commands in those steps, that's correct. I don't seem to need them on my Mini.

At step 7, I usually see the eGPU symbol in the menu bar for a moment. Is it normal that it disappears?
At step 8, it seems that if I let MacOS churn through the entire session starting back up, that too much time passes before logging out and the eGPU doesn't come up. Does that make sense in any way?

For the record, my 2012 Mini detects as having Thunderbolt 2. Throughput in System Information shows the expected 10 Gb/s though.

Need help...
I just followed these steps to test my Aorus gaming box 1080 enclosure with Msi rx560 aero itx and I'm in 10.14.2 Mojave currently, but nothing worked... LED didn't turn on and the fan of the card did not run, but the small fan of the power worked, is that normal? Cause the LED and the fan worked great with the original gtx1080 even I did't login with EFI boot.

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


ReplyQuote
 of  23