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

[Solved] automate-eGPU EFI - eGPU boot manager for macOS and Windows  

 of  26
  RSS

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

does it work with catalina beta(5) ?

This post was modified 3 months ago

MBP17 late 2011 TB1 Radeon Pro WX 4100


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

@mac_editor

Back in business ;.)
Cleaning the Kernel Cache solved the problem!
Thanks!

MacMini Late 2012, Sonnet Puck 570


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

ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 3 months ago
 
Posted by: @mac_editor
Posted by: @civa

I used whatever the instructions said to download and create a FAT 32 boot disk from 

Sorry, I’m not too versed in scripts.

@civa read main post again.

Pardon?

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


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

@civa

Sorry for being unclear. Check out the main page of this thread: https://egpu.io/forums/mac-setup/automate-egpu-efi-egpu-boot-manager-for-macos-and-windows/

In the first post, there is another section titled automate-eGPU EFI Installer. Check that out.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


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

@espionage724

Thank you for the heads-up. It was my oversight to not consider SD cards. I do not have one to experiment with though so I cannot add/test this functionality. If you are a software developer (you're running Fedora - so you are ;p) please consider looking at the script (see Pastebin link on main page) and adding this functionality.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 3 months ago
 
Posted by: @mac_editor

@civa

Sorry for being unclear. Check out the main page of this thread: https://egpu.io/forums/mac-setup/automate-egpu-efi-egpu-boot-manager-for-macos-and-windows/

In the first post, there is another section titled automate-eGPU EFI Installer. Check that out.

Those are the instructions on followed. That is how I add the boot usb. 
Is there an update to the boot usb? 

not meaning to be obtuse, but if I’m on this thread and gotten this far, I think it should be assumed those are the instructions I followed. 

Has something changed?

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


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

@civa No nothing has changed. The reason I brought this up is because there are two ways to set up the USB stick - one is to download the EFI files manually, unzip them, and copy them to a USB drive formatted as FAT-32. The other is to run the script in the installer section. While running the script, it gives you the option of choosing GPU vendor (AMD or NVIDIA). If you choose AMD, the patch applied in the EFI configuration changes so when you connect an eGPU, the eGPU icon would show up. Hence my goal for asking was which way you used to set up the USB. Earlier you mentioned you were not familiar with running scripts, and you mentioned that the GPU shows up in Graphics/Displays but no icon in the menu. Both point to manual setup rather than the script one (from the install section).

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 3 months ago
 
Posted by: @mac_editor

@civa No nothing has changed. The reason I brought this up is because there are two ways to set up the USB stick - one is to download the EFI files manually, unzip them, and copy them to a USB drive formatted as FAT-32. The other is to run the script in the installer section. While running the script, it gives you the option of choosing GPU vendor (AMD or NVIDIA). If you choose AMD, the patch applied in the EFI configuration changes so when you connect an eGPU, the eGPU icon would show up. Hence my goal for asking was which way you used to set up the USB. Earlier you mentioned you were not familiar with running scripts, and you mentioned that the GPU shows up in Graphics/Displays but no icon in the menu. Both point to manual setup rather than the script one (from the install section).

Oh, okay. I guess I did the simple method, which was downloading and creating the boot usb. I know I didn’t get to choose the manufacture.

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


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

Hi,

I'm trying to boot into Windows 10 (confirmed that it's UEFI in msinfo) with an USB stick created using the installer, but I get the following error:

FileOpen:2707 Status 8000000000000007

Any idea how I could fix it? I'm using an MBP2017 15" with latest Catalina beta (trying to boot into MacOS gives the same error). I tried resetting SMC and NVRAM without luck.

Thanks

MBP 2017 15", MacOS 10.15 19A526h, GTX1070 EGPU


ReplyQuote
dalroi
(@dalroi)
Active Member
Joined: 1 year ago
 

@Civa: Did you try without the file that I removed in step 6 of my Mac Mini 2012 setup guide on page 7 of this thread?

Mac Mini 2012 + Sonnet Breakaway Box (up to 300W) + Asus Arez Radeon RX560 2GB


ReplyQuote
PoundOfFlesh
(@poundofflesh)
New Member
Joined: 3 months ago
 

Hello,

Thanks for all of this. The main purpose of this post is really just to say thanks for all the info and the work that was done to help others. I will post some details of my past 2 days of testing for any other's reference and for feedback.

My setup:

  • 2018 Mac Mini
  • Razer Core X Chroma (only device currently plugged into TB3 port)
  • PNY GeForce 1060 GTX
  • Sabrent USB 3.1 Enclosure for M.2 NVMe SSD (plugged into USB port)
  • Samsung 970 EVO (inside Sabrent enclosure)
  • Dell U2715H (main monitor plugged into HDMI, only monitor used in MacOS, secondary monitor in Windows 10 Bootcamp)
  • ASUS VG248QE (main monitor in Windows 10 Bootcamp, not used in MacOS)

I will just list out some notes in bullet format as I think it's easier to scan through.

Installation:

  • Used mac_editor's (not sure how to use @ references here, is it just a link to the profile?) script to install to USB stick
  • Bootcamp installed Windows 10 Home (1903) on main disk of Mac Mini
  • Using Samsung 1 TB drive as external space to install programs to for Windows
  • I'm sorry, can't remember this exactly but first Windows 10 boot:
    • Use automate-eGPU boot option (using this every time to load into Windows) 
    • eGPU was disconnected
    • Only using HDMI monitor
    • Installed all Bootcamp drivers
    • Restart back into Windows
    • Plug eGPU in while after Windows has booted
    • Install Nvidia driver for 1060
    • Restart back into Windows
    • Plug in VG248QE
    • Set VG248QE to main monitor
    • Install ToastyX strobelight settings
    • Install misc stuff like Windows updates, Steam, a couple games

Misc. Notes:

  • Since I have an Nvidia card and I'm not doing heavy GPU tasks in MacOS, I'm not running eGPU while in MacOS
  • USB stick containing automate-eGPU EFI is plugged into Core X Chroma
  • I haven't solved this but I will randomly load into Windows and the entire Core X Chroma seems like it isn't found
    • Shutting everything off and swapping TB3 ports seems to help reconnect
  • I have an old 120hz monitor and I loaded ToastyX's ( https://www.blurbusters.com/easy-lightboost-toastyx-strobelight/) strobelight successfully, and am getting high refresh on the main Windows monitor
  • Using builtin Ethernet port for connectiviy
  • Some games seem incompatible when loading high anti-aliasing (sample size: 2, 1 failure) and just close
  • I had issues with getting a wireless DualShock 4 controller to work. Seems like I was getting very bad latency.
    • Ended up disabling the Bluetooth Network Adapter (which wasn't being used). I believe this was the main culprit.
    • I also disabled all other network adapters that I wasn't using.
  • Using DS4Windows driver for DualShock 4 seemed to cause a bad driver incompatibility crash when loading a game that knocked out the entire Core X Chroma
    • I had to reboot and just use native Steam/Windows Bluetooth for the controller
  • I was having trouble with the Samsung external drive failing to load when booting into Windows sometimes, issuing a USB error in Windows.
    • Part of this was a conflict due to the automate-eGPU USB stick getting letter drive D on load.
    • I went into Computer Management and changed the drive letter for the external drive to Y
  • The external drive is where I'm installing all games and large programs (main OS disk is only 40GB)
  • Sometimes, when I can't get things working, it seems like shutting everything off and swapping ports helps.
  • When going between OSes, I generally shut off the Mac Mini
    • If I'm going to MacOS, then I turn off the Core X Chroma while shut off
    • If I'm going to Windows, then I turn it on while shut off and use automate-eGPU EFI to load Windows every time

Again, thanks to those that made the scripts. I really appreciate it. If you have any questions about what I did, let me know and I'll try to provide as much feedback as possible. I apologize for not remember or writing down everything but I went through a lot of iterations of trying to figure out what I was supposed to be doing and the quirks of my devices.

This post was modified 3 months ago

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


ReplyQuote
John Keates
(@oneplane)
Active Member
Joined: 1 year ago
 

I'm running into an issue where the EFI application just hangs after selecting either boot option (boot macOS or boot Windows). This is with version 1.5 on an Early 2015 13" MBP. Currently working fine with purge-wrangler (and an Apple TB2-TB3 adapter, Akitio Thunder 3 and RX570). Windows is not on the internal drive but on an external USB3 SSD, I suspect this is why automage-eGPU EFI can't boot, because it only supports the direct boot to Apple's EFI boot loader or the one from Windows. SIP is on, internal SSD is APFS (standard macOS install). 

Does the EFI application have specific ordering or places to look when searching for the correct OS to start? Because if I just put the bootmgrfw.efi on the Apple ESP it could still load the external Windows install just fine. Still doesn't explain the boot-to-macOS issue (I did remove the purge-wrangler kext mods when I tried this).

Windows 10 pre 1903 worked fine, but on 1903 it no longer assigned the resources correctly and now the eGPU won't start natively like it used to, so I wanted to try the EFI method hoping it would enable large memory and solve it.

rMBP 2015 13", AkiTiO Node, RX 570 4GB, 10.14 + Win10, Apple TB2-TB3


ReplyQuote
nu_ninja
(@nu_ninja)
Estimable Member
Joined: 2 years ago
 
Posted by: @r3don

I'm running Windows 10 from external Samsung T5. First attempts were failing - after selecting “Windows” menu item the system kept freezing. So I've just copied "Microsoft" folder from external ssd EFI partition to my Macbook internal EFI partition and now it works just fine. 

^^ From about 8 pages back in this thread. You might be facing larger issues though if macOS is also failing to boot

This post was modified 3 months ago

Mid-2012 13" Macbook Pro (MacBookPro9,2) TB1 -> RX 460/560 (AKiTiO Node/Thunder2)
+ macOS 10.15+Win10 + Linux Mint 19.1


ReplyQuote
John Keates
(@oneplane)
Active Member
Joined: 1 year ago
 
Posted by: @nu_ninja
Posted by: @r3don

I'm running Windows 10 from external Samsung T5. First attempts were failing - after selecting “Windows” menu item the system kept freezing. So I've just copied "Microsoft" folder from external ssd EFI partition to my Macbook internal EFI partition and now it works just fine. 

^^ From about 8 pages back in this thread. You might be facing larger issues though if macOS is also failing to boot

Ah, I was looking for someone else who was doing the same, I guess my search terms weren't as well-targeted as I thought 😉


Edit:
as it turns out, it's not as much about the EFI boot loader for Windows not being on the internal ESP on Apple's SSD, but about it being available on an external drive as well. Booting works instantly as long as there is no Windows ESP connected via USB, including booting to macOS. It also immediately fixes error 12. So for others using Windows from an external disk: you have to rename (you could remove it but that makes restoring harder) the Windows EFI directory with the ESP to something that is not EFI (i.e. i named mine disabled-EFI), and copy the Microsoft directory inside the Microsoft ESP to Apple's ESP. Inside Apple's ESP you have an EFI directory with an Apple directory inside that one. You can copy the Microsoft directory next to the Apple one, which will then be available to boot from. The Microsoft EFI boot loader and BCD will live there and will be able to boot Windows (Windows 10 in my case) from the external drive. This works both with the automate-eGPU EFI loader as well as without (but then the eGPU doesn't work).

Ideally the automate-eGPU EFI loader would add support for either chain loading to rEFIt/rEFInd or Clover because those can actually boot off of fully external drives without the EFI mess, but I suspect that might be more work with more moving parts making it more fragile.

This post was modified 2 months ago

rMBP 2015 13", AkiTiO Node, RX 570 4GB, 10.14 + Win10, Apple TB2-TB3


ReplyQuote
yfain
(@yfain)
Active Member
Joined: 2 months ago
 

Got the error message that no egpu is detected.

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


ReplyQuote
Espionage724
(@espionage724)
Active Member
Joined: 3 months ago
 
Posted by: @laimis17

does it work with catalina beta(5) ?

I don't know what beta 5 is, but automate-eGPU EFI doesn't work with Catalina beta build 19A546d (boot halts after selecting macOS on the boot manager).

purge-wrangler works though

MacBook Pro (Retina, 13-inch, Mid 2014)
AKiTiO Thunder2
XFX Radeon RX 580
macOS Catalina 10.15
Fedora Workstation 31 Beta


ReplyQuote
zooli
(@zooli)
Eminent Member
Joined: 3 years ago
 

I'm having issues with automate-eGPU EFI on my 2012 Mac mini with Boot Camp (Windows 10 LTSC 1809). I used the installer by mac_editor. The bootloader loads up fine, but doesn't detect eGPU and when I try to boot to Windows with iGPU (from the menu), the screen freezes and I have to turn the computer off. MacOS boots up fine. Does anyone know what the problem could be (and how to solve it:) ? Can it be due to that I have Windows legacy install (through Boot Camp Assistant)? Details here.

Never mind, it's solved. The problem was using the mini-display port for the monitor, which is the only TB 1 port on the 2012 Mac mini.

This post was modified 2 months ago

2012 Mac mini i7 2.6Ghz . 16GB RAM . 500GB SSD . 1TB HDD . Razer Core X . Sapphire RX 580 Nitro+ SE . DVI 60Hz monitor . MacOS 10.14.6 . Windows 10 LTSC 1809


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

A question about automate-eGPU EFI and using it in MacOS High Sierra 10.13.6 (17G8030).
It has always worked for me as a standard setup as described in this thread. Since recent updates though (about 1-2 weeks ago) I can't get the eGPU running anymore under MacOS.

Here's the procedure.

1. I boot with eGPU disconnected, from the stick. In MacOS i then only have the internal GPU running, which looks good.

Screen Shot 2019 09 13 at 11.45.13

2. The i connect the eGPU (same as above still) and re-login. After the re-login I'm usually running on the GTX 1080ti and the external screen. But now everything stays internal with dGPU activated even.

Screen Shot 2019 09 13 at 11.46.44

What's running wrong here? Any tips how I can fix this quickly?
In Windows it still works fine, btw; even without eGPU EFI stick boot up.

PS: also just ran this and it says the latest nVidia drivers are installed.

This post was modified 2 months ago

Late 2016 15" MBP w/ Radeon Pro 460, 2m CalDigit TB3 cable, Mantiz Venus eGPU case, NVidia GTX 1080ti.


ReplyQuote
ucs308
(@ucs308)
Active Member
Joined: 2 months ago
 

I used the installer described in the first post, to create a USB stick. When I hold the "option" key down I get three options. Windows/Mac/EFIBOOT. I select the EFIBOOT with the eGPU disconnected and I see the main screen for automate-eGPU. I select 'q' for the quick start and am presented with options to start MacOS or Windows etc. But I cannot select any of them. The keyboard does not seem to work (though it must because I could hit Q). 

I am using 2018 Mac mini with Catalina Beta 8 ( the latest ).

The machine has never had automate-eGPU EFI installed before. 

I have not - yet - read all the posts in this thread.

This post was modified 2 months ago

System 1: Mac Mini 2018 / i7 16GB / iGPU Intel 630 / eGPU Radeon RX 580 (XFX varient) + Sonnet Breakaway Box 650W / Windows 10 via Bootcamp / Mac OS Catalina ( beta 8)


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

I used the installer described in the first post, to create a USB stick. When I hold the "option" key down I get three options. Windows/Mac/EFIBOOT. I select the EFIBOOT with the eGPU disconnected and I see the main screen for automate-eGPU. I select 'q' for the quick start and am presented with options to start MacOS or Windows etc. But I cannot select any of them. The keyboard does not seem to work (though it must because I could hit Q). 

I am using 2018 Mac mini with Catalina Beta 8 ( the latest ).

The machine has never had automate-eGPU EFI installed before. 

I have not - yet - read all the posts in this thread.

I noticed the problem is that the Mac does not boot. pressing "Load Mac OS" never does anything. 

Has anyone had this work on a Mac running Catalina?

System 1: Mac Mini 2018 / i7 16GB / iGPU Intel 630 / eGPU Radeon RX 580 (XFX varient) + Sonnet Breakaway Box 650W / Windows 10 via Bootcamp / Mac OS Catalina ( beta 8)


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

ReplyQuote
ucs308
(@ucs308)
Active Member
Joined: 2 months ago
 

@mac_editor

I did. But I might not have checked the option that allowed booting from external drives. Now however I have other (new) issue. When I boot with Command+R pressed I get the recovery screen. I select security options from the menu and get a message saying the current RecoveryOS has no access to the security settings. And that I need to restart with Command+R pressed. 

 

OK. I got back into the Security Options by clearing the nvram and restarting with command+r. My settings were no firmware password, no security options and allow booting from external drives. 

This post was modified 2 months ago

System 1: Mac Mini 2018 / i7 16GB / iGPU Intel 630 / eGPU Radeon RX 580 (XFX varient) + Sonnet Breakaway Box 650W / Windows 10 via Bootcamp / Mac OS Catalina ( beta 8)


ReplyQuote
ucs308
(@ucs308)
Active Member
Joined: 2 months ago
 

automate-eGPU is broken on Catalina Beta 8.

System 1: Mac Mini 2018 / i7 16GB / iGPU Intel 630 / eGPU Radeon RX 580 (XFX varient) + Sonnet Breakaway Box 650W / Windows 10 via Bootcamp / Mac OS Catalina ( beta 8)


ReplyQuote
(@ron_johnson)
New Member
Joined: 2 months ago
 

Is it feasible to get both iGPU and dGPU available? Windows can only see the dGPU.

- Macbook 11,5 (2015 15" w/ AMD R9 M370x)
- macOS 10.14.6
- Windows 10 (10.0.17763 Build 17763)

The battery life while traveling is dramatically less solely on the dGPU :/

This post was modified 2 months ago

Macbook 2015 15", R9 M370X


ReplyQuote
emanuelediba
(@emanuelediba)
Eminent Member
Joined: 11 months ago
 

On my setup, it has been working for months, but now, when I select “Boot Windows” it get’s stuck on the bot loader screen and nothing will happen. I did the USB key again but no luck... 

What could be the issue causing this? Should I try reset NVRAM?

Mid-2012 15" Retina MacBook Pro + Akitio Node + AMD RX 580


ReplyQuote
(@ty_irvine)
New Member
Joined: 2 months ago
 

@goalque

Thank you for making this!! It worked so well for me!

I made a MS-DOS(FAT) partition off my internal drive and popped it in there. So easy!

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


ReplyQuote
emanuelediba
(@emanuelediba)
Eminent Member
Joined: 11 months ago
 

I can't boot Windows anymore with automate-eGPU EFI, I can't understand why. It hangs when I select "Load Windows".  I've tried to format the entire Bootcamp partition, re-create the USB drive with the script, but no luck.  Do you have any ideas? It seems like it can't find the Windows partition...

Mid-2012 15" Retina MacBook Pro + Akitio Node + AMD RX 580


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 3 months ago
 
Posted by: @mac_editor
Posted by: @civa

That’s not very clear to me (I’m also using a late 2012 Mac mini , though not one person has answered the questions I have asked) 

@civa I answered specifically to Sebastian who is using a GT 750M MacBook Pro 15".

Posted by: @civa

the entire reason to use automate eGPU is to avoid disabling system integrity

Booting with automate-eGPU EFI automatically disables System Integrity Protection IIRC.

If you created your USB stick with the installer script, you will see the eGPU icon, otherwise not. If the issue started occurring after an update, rebuild kernel cache.

I took  your advice and reloaded the the installer using the script. It worked. I get the icon in the top bar, and I see that my card is being read as Radeon HD Hawaii XT Prototype
Basically, thank you, and I think I need to get a Vega.

Also, Are you updating this for Catalina? 

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 3 months ago
 
Posted by: @civa
Posted by: @mac_editor
Posted by: @civa

That’s not very clear to me (I’m also using a late 2012 Mac mini , though not one person has answered the questions I have asked) 

@civa I answered specifically to Sebastian who is using a GT 750M MacBook Pro 15".

Posted by: @civa

the entire reason to use automate eGPU is to avoid disabling system integrity

Booting with automate-eGPU EFI automatically disables System Integrity Protection IIRC.

If you created your USB stick with the installer script, you will see the eGPU icon, otherwise not. If the issue started occurring after an update, rebuild kernel cache.

I took  your advice and reloaded the the installer using the script. It worked. I get the icon in the top bar, and I see that my card is being read as Radeon HD Hawaii XT Prototype
Basically, thank you, and I think I need to get a Vega.

Also, Are you updating this for Catalina? 

Damn it. Now I have rebooted my machine, and the icon dropped from the top bar. Why is this happening?

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


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

@civa

You must boot via the automate-eGPU EFI menu every time you need eGPU support. If this stops working for some reason, rebuild kernel cache via Terminal (look it up).

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 3 months ago
 
Posted by: @mac_editor

@civa

You must boot via the automate-eGPU EFI menu every time you need eGPU support. If this stops working for some reason, rebuild kernel cache via Terminal (look it up).

So I basically have to leave the thumb drive in, at least until I get a new Mac where I don’t need the script, is what you’re saying?

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


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

@civa

As written in the original post:

The whole idea of automate-eGPU EFI is to keep your system clean, no modified kexts. When the USB is unplugged, and you reboot, your Mac is in factory state.

Once you boot, you can eject the thumb drive. But the next time you boot, you need to go via the thumb drive/EFI menu.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
joevt
(@joevt)
Prominent Member
Joined: 2 years ago
 

@civa

Create a small FAT partition and copy the EFI partition of the thumb to it. You can give the partition a name and icon.
Some instructions are listed at:  https://apple.stackexchange.com/questions/338574/bless-error-when-installing-refind
To summarize, create a FAT partition (the example has name BOOTMGR).
Copy the EFI folder from the thumb drive to the new FAT partition.
Use the bless command to create a label which will appear in the Startup Manager (doesn't work on older Macs):

bless --folder /Volumes/BOOTMGR/EFI/BOOT --label automate-eGPU

You can also paste an icon into the Finder Info window of the BOOTMGR partition.
Maybe use a better name than BOOTMGR for the partition.
Actually, the above is basically the same instructions used to create the USB thumb drive. Which means you did not have to create the partition on a USB thumb drive in the first place. The point of the bless command is to give the partition a more meaningful label than just the default "EFI Boot".

If you have an older Mac, the bless label might not work. In that case, create an HFS+ partition, copy the EFI files to it and use bless to bless the EFI boot loader and give a label. For example, I have a MacPro3,1 (2008) with Mojave on an APFS partition, and I haven't added an APFS driver to my firmware yet, so I need to use an EFI boot loader to load the APFS EFI driver. I created a small 100 MB partition (it only needs to be 10 MB) called "Mojave Boot". Added a folder called "macOSMojaveBooter" containing the EFI app (ShellX64.efi), which runs a script (startup.nsh) which loads the apfs driver (apfs.efi), mounts apfs volumes in EFI, and starts the macOS boot file at System\Library\CoreServices\boot.efi on my Mojave APFS partition. The bless command is the following:

sudo bless --folder /Volumes/Mojave\ Boot/macOSMojaveBooter --file /Volumes/Mojave\ Boot/macOSMojaveBooter/ShellX64.efi --label Mojave --setBoot

--label is what will appear in the Startup Manager (when you hold option key during boot).
--setBoot changes the startup preference in nvram - it's optional.
--folder and --file affect parameters on an HFS+ partition. --file is the efi app that you want to be executed for boot. --file allows efi apps to be located in a different place than the default (which is EFI/BOOT/BOOTX64.EFI  on an EFI partition).

Does automate-eGPU require write access to its partition? I think EFI only has write access to FAT partitions, not HFS+ partitions.

This post was modified 2 months ago

Mac mini (2018), Mac Pro (Early 2008), MacBook Pro (Retina, 15-inch, Mid 2015), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 3 months ago
 
Posted by: @mac_editor

@civa

As written in the original post:

The whole idea of automate-eGPU EFI is to keep your system clean, no modified kexts. When the USB is unplugged, and you reboot, your Mac is in factory state.

Once you boot, you can eject the thumb drive. But the next time you boot, you need to go via the thumb drive/EFI menu.

So this will work with Catalina? 
I honestly didn’t understand that from the initial post. 
Essentially, I’m always booting from the thumb drive, in order to support both my monitors, via the eGPU, until I upgrade my Mac to a newer version, that does not require the EFI to run an external GPU. 

I understand, though does this impact system performance, at all? 

I have an MSI RX Vega 56 OC on the way, btw, now that I realize High Sierra needs a Vega or higher to function correctly.

@joevt

That’s a lot for me to go over. Do you mind if I get back to you tomorrow? 

This post was modified 2 months ago

Mac Mini (Late 2012) , quad core i7 2.6 GHz, 16 GB DDR3, and Dual internal SSDs, 1 TB and 4 TB

AKiTiO Node Pro AMD Radeon R9 290X


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

So this will work with Catalina? 

The patches work - don't know about the tool itself as I haven't tried.

Posted by: @civa

I understand, though does this impact system performance, at all? 

No.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
 of  26