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

OliverB
(@oliverb)
Noble Member
Joined: 10 months ago
 

Tahiti and Fiji work quite well, but lots of of the legacy AMD cards won't work in MacOSX. R9 290 and HD 7770 wouldn't work. I really tried hard. Anything under HD 7000, e.g. HD 6950, HD 5850 wouldn't work either. Of course they cannot do Metal, but R9 290 and HD 7770 are supposed to support Metal.

This post was modified 3 months ago

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


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

The D500/D700 device ids are equivalent to HD 7870/7970. I have both cards. If the card is not on this list:

https://support.apple.com/en-us/HT208898

it may work partially or not at all. Apple says "Third-party graphics cards vary, so you should check with the vendor of your specific graphics card for compatibility details".

As a rule of thumb, if you choose the right vendor and the device id exists in all IOPCITunnelCompatible sections, it should work.

This post was modified 3 months ago

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


ReplyQuote
singermustdie
(@singermustdie)
Active Member
Joined: 5 months ago
 

Hey all. Newbie eGPU attempter here. 

I have a late 2013 iMac (TB1) with an interior NVIDIA GeForce GT 755M and a Sonnet Breakaway with Sapphire Radeon RX580. I get to the Load MacOS selection but then it gets stuck on "Saving…" I've waited as much as 20 minutes, no go.

I'm pretty sure I'm following the directions, but want to spell out what I've done to see if you think I've missed something

1) Download EFI 
2) Format USB with MS-DOS (FAT) MBR
3) Copy EFI folder on to USB drive
4) Boot into EFI (plug eGPU in here?)
5) select q and "Load MacOS"

From there things get stuck on "Saving…". I have reformatted and renamed the drive a few times to make sure that isn't the issue.

Am I missing something that any of you can see? I have tried booting into EFI with the eGPU both connected and disconnected and in both cases I end up at "Saving…" 

Also, does anyone have the same hardware and if so has it worked for you?

Thanks for all the work on this and for any responses. All the best.

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


ReplyQuote
dalroi
(@dalroi)
Active Member
Joined: 10 months ago
 

A few fairly wild guesses that you may want to check regardless...

I notice you mention your USB device as a "drive". How big is it? You may be running into the disk-size limit of MBR. Then again, you could write the EFI folder to it - but the full OS probably has more smarts available for the task than a simple boot loader...

The other possibility that comes to mind is that, if I recall correctly, the USB image makes assumptions on where MacOS is located. If your OS isn't in the default location, it's quite that "Saving..." is the last thing the EFI boot image prints. Frankly, I don't know if it prints anything when it starts its attempt to load the OS or when it fails to find it.

I'm sure more knowledgeable people will chime in, but this may get you going.

Finally, the correct moment to plug in the eGPU is after you logged in. For me it usually works when booted up with the eGPU plugged in, but that's not guaranteed. I'm on different hardware too.

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


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined: 3 years ago
 

I just tried using the script on a 2017 MBP 13 inch with a Mantiz Venus and a gtx 980. When I boot from the EFI using a usb stick and the eGPU plugged in, it says "No eGPU was detected.". Any ideas why its not being detected?

mid-2017 15" Macbook Pro RP555 + [email protected] (Mantiz Venus) + macOS & Win10


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

I just tried using the script on a 2017 MBP 13 inch with a Mantiz Venus and a gtx 980. When I boot from the EFI using a usb stick and the eGPU plugged in, it says "No eGPU was detected.". Any ideas why its not being detected?

Your question is answered here, here and here 🙂

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


ReplyQuote
singermustdie
(@singermustdie)
Active Member
Joined: 5 months ago
 
Posted by: singermustdie
Thanks @dalroiPosted by: dalroi

A few fairly wild guesses that you may want to check regardless...

I notice you mention your USB device as a "drive". How big is it? You may be running into the disk-size limit of MBR. Then again, you could write the EFI folder to it - but the full OS probably has more smarts available for the task than a simple boot loader...

The other possibility that comes to mind is that, if I recall correctly, the USB image makes assumptions on where MacOS is located. If your OS isn't in the default location, it's quite that "Saving..." is the last thing the EFI boot image prints. Frankly, I don't know if it prints anything when it starts its attempt to load the OS or when it fails to find it.

I'm sure more knowledgeable people will chime in, but this may get you going.

Finally, the correct moment to plug in the eGPU is after you logged in. For me it usually works when booted up with the eGPU plugged in, but that's not guaranteed. I'm on different hardware too.

Thanks for the reply @dalroi

My drive is a 16GB USB 2.0 Kingston Thumbdrive. Do you think more space than that is needed?

But this does have me wondering if the 2.0 might be a problem. I'll find another thumb to try.

The MacOS is definitely in the default location. I also have a Win10 bootcamp install on the same drive, but that's it. 

And thanks for the eGPU plugging confirmation. I haven't gotten that far yet, but it sounds like I was at least doing it correctly.

So, off of the comments from @dalroi I ended up trying a different USB (3.0 this time) and voila, success as it booted into Mac and also recognized my RX580 eGPU in system preferences after hotplugging.

Now the issue seems to be that my 2nd monitor (the one the eGPU is connected to) is black. I've tried different HDMI cables, reboots, reinstalls, no luck. I also tried changing the MUX setting to 1 (as detailed in @goalque's instructions for NVidia eGPUs. Not my situation but I tried it anyway) and reformatted the thumb with @mac_editor's script in case I was missing a step. Still no.

If I move my mouse over in that direction, it is clearly ON, but black. 

Is this a PurgeNVDA candidate as @Koopa mentioned in this post? 

Or is the late 2013 iMac with NVidia graphics still considered incompatible as mentioned in this post.

Any and all help much appreciated.

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
 

@singermustdie Unfortunately the internal NVIDIA GPU and the lack of muxing will prevent external monitor from functioning over the eGPU. purge-nvda would not help either (requires iGPU + muxing-capable system - which only MBPs have). I don't have this kind of Mac anymore or I would have investigated further 🙁

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


ReplyQuote
singermustdie
(@singermustdie)
Active Member
Joined: 5 months ago
 
Posted by: mac_editor

@singermustdie Unfortunately the internal NVIDIA GPU and the lack of muxing will prevent external monitor from functioning over the eGPU. purge-nvda would not help either (requires iGPU + muxing-capable system - which only MBPs have). I don't have this kind of Mac anymore or I would have investigated further 🙁

Bummer. Thanks @mac_editor

So, does that mean I can't use the eGPU at all or just not with this USB Boot method? (I know there's also the purge-wrangler option.) Or perhaps instead of using it with an external monitor I could use the script that enables eGPU on the iMac's itself. 

That's not ideal for me anyway as my iMac screen is cracked and oozing, but I'm just curious.

I feel like I know the answer (no), but I'm asking anyway.

Thanks again.

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
 

@singermustdie There is no difference in terms of capability between the patching mechanisms (they are just that - different ways to apply patches), so unfortunately the answer is no. However, and I'm not sure if this will work, but if you do not at all want to use the broken iMac display, maybe completely disabling the NVIDIA framebuffer might fix the issue (usually doing just this has prevented boot on similar Mac laptops - never tested an iMac myself - so ensure that you have a way to get into recovery or single user mode - CMD+S on boot). You can disable the framebuffer via Terminal as:

sudo nvram boot-args="nv_disable=1"

and then reboot. Most likely this will prevent boot. However, if boot succeeds, you will see an unaccelerated/slow interface (like in Safe Mode) on your iMac and external monitors connected to iMac won't work. However, plugging in an eGPU with an external monitor would result in an accelerated external monitor using the eGPU (assuming patches are installed). To undo changes if boot fails, do:

sudo nvram -d boot-args

in single user mode or recovery.

This post was modified 3 months ago

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


ReplyQuote
singermustdie
(@singermustdie)
Active Member
Joined: 5 months ago
 
Posted by: mac_editor

@singermustdie There is no difference in terms of capability between the patching mechanisms (they are just that - different ways to apply patches), so unfortunately the answer is no. However, and I'm not sure if this will work, but if you do not at all want to use the broken iMac display, maybe completely disabling the NVIDIA framebuffer might fix the issue (usually doing just this has prevented boot on similar Mac laptops - never tested an iMac myself - so ensure that you have a way to get into recovery or single user mode - CMD+S on boot). You can disable the framebuffer via Terminal as:

sudo nvram boot-args="nv_disable=1"

and then reboot. Most likely this will prevent boot. However, if boot succeeds, you will see an unaccelerated/slow interface (like in Safe Mode) on your iMac and external monitors connected to iMac won't work. However, plugging in an eGPU with an external monitor would result in an accelerated external monitor using the eGPU (assuming patches are installed). To undo changes if boot fails, do:

sudo nvram -d boot-args

in single user mode or recovery.

Thanks for that @mac_editor. I'll give it a shot when I get a moment and am feeling brave. 

Or I'll just get a new computer-)

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


ReplyQuote
tndiggs
(@tndiggs)
Active Member
Joined: 3 months ago
 

On my 2018 MacBook Pro 13 non touchbar (macbookpro14,1) i can’t boot into this. An error log flashes briefly and then a blank screen. 

Ive tried erasing and reinstalling OS X, but that didn’t help. 

I put out the usb stick into another Mac and it worked, so I know the usb stick is good. 

Any ideas?

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


ReplyQuote
nu_ninja
(@nu_ninja)
Estimable Member
Joined: 1 year ago
 

@tndiggs

Did you disable secure boot and allow booting from external drives? ( https://support.apple.com/en-us/HT208330 )

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


ReplyQuote
tndiggs
(@tndiggs)
Active Member
Joined: 3 months ago
 
Posted by: nu_ninja

@tndiggs

Did you disable secure boot and allow booting from external drives? ( https://support.apple.com/en-us/HT208330 )

The non touchbar 13” doesn’t have a t2, so that’s not affecting it :/

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


ReplyQuote
huafengchun
(@huafengchun)
Active Member
Joined: 10 months ago
 

I meet the same  question. Have you fix this?

@goalque Thank you for this awesome tools. But I met a problem. when I choose EFI boot and hit enter, I see some logs flash and then my screen show nothing forever. Did I miss something?

This post was modified 2 months ago

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


ReplyQuote
Dezmond
(@dezmond)
New Member
Joined: 2 years ago
 

No idea how to run chmod to be honest. Tried those lines of code on page 1 and I get this info back:

MacBook-Pro-van-Desmond-2:~ desmondgerritse$ sudo kextutil -t -v 0 /System/Library/Extensions/AppleGraphicsControl.kext

Password:

MacBook-Pro-van-Desmond-2:~ desmondgerritse$ sudo kextutil -t -v 0 /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGPUWrangler.kext

Kext with invalid signatured (-67061) allowed: <OSKext 0x7fddf545f3f0 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGPUWrangler.kext/", ID = "com.apple.AppleGPUWrangler" }

Kext with invalid signatured (-67061) allowed: <OSKext 0x7fddf54625f0 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

Code Signing Failure: code signature is invalid

Kext with invalid signatured (-67061) allowed: <OSKext 0x7fddf54625f0 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

Kext with invalid signatured (-67061) allowed: <OSKext 0x7fddf54625f0 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

MacBook-Pro-van-Desmond-2:~ desmondgerritse$ sudo kextutil -t -v 0 /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext

Kext with invalid signatured (-67061) allowed: <OSKext 0x7fdbb6462600 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

Kext with invalid signatured (-67061) allowed: <OSKext 0x7fdbb6462600 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

Kext with invalid signatured (-67061) allowed: <OSKext 0x7fdbb6462600 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

MacBook-Pro-van-Desmond-2:~ desmondgerritse$ sudo kextutil -t -v 0 /System/Library/Extensions/IOGraphicsFamily.kext

Kext with invalid signatured (-67061) allowed: <OSKext 0x7fb5ed6239d0 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

Code Signing Failure: code signature is invalid

Warnings:

    Personality matches on IOResources but IOMatchCategory is missing or not equal to its IOClass; driver may be blocked from matching or may block others:

        IODisplayWrangler

 

MacBook-Pro-van-Desmond-2:~ desmondgerritse$ sudo kextutil -t -v 0 /System/Library/Extensions/IONDRVSupport.kext

Kext with invalid signatured (-67030) allowed: <OSKext 0x7f97d3e49910 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IONDRVSupport.kext/", ID = "com.apple.iokit.IONDRVSupport" }

Kext with invalid signatured (-67061) allowed: <OSKext 0x7f97d3e55800 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

Code Signing Failure: code signature is invalid

Kext with invalid signatured (-67061) allowed: <OSKext 0x7f97d3e55800 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

Kext with invalid signatured (-67061) allowed: <OSKext 0x7f97d3e55800 [0x7fff8eab7af0]> { URL = "file:///System/Library/Extensions/IOGraphicsFamily.kext/", ID = "com.apple.iokit.IOGraphicsFamily" }

MacBook-Pro-van-Desmond-2:~ desmondgerritse$

This post was modified 2 months ago

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


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

@goalque
if I boot with the efi boot I get black screen any fix for that??

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


ReplyQuote
Koray Birand
(@koray_birand)
New Member
Joined: 2 years ago
 
Posted by: goalque

@gcoban would you run commands one by one:

sudo kextutil -t -v 0 /System/Library/Extensions/AppleGraphicsControl.kext
sudo kextutil -t -v 0 /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGPUWrangler.kext
sudo kextutil -t -v 0 /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext
sudo kextutil -t -v 0 /System/Library/Extensions/IOGraphicsFamily.kext
sudo kextutil -t -v 0 /System/Library/Extensions/IONDRVSupport.kext

One of those returns something else than an empty string.

I ran all the lines one by one.. The last line fails.. This is what I get:

Korays-Mac-Pro:Downloads koraybirand$ sudo kextutil -t -v 0 /System/Library/Extensions/IONDRVSupport.kext

Kext with invalid signatured (-67030) allowed: <OSKext 0x7faf53c55740 [0x7fff83e718f0]> { URL = "file:///System/Library/Extensions/IONDRVSupport.kext/", ID = "com.apple.iokit.IONDRVSupport" }

Code Signing Failure: code signature is invalid

Korays-Mac-Pro:Downloads koraybirand$ 

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


ReplyQuote
Null
 Null
(@null)
New Member
Joined: 2 months ago
 

This method was working until today,

After windows' last security update, I ran into the Black Screen Problem that other users have come across. I rebooted the computer and the black screen went away, and windows started downloading an update for the Nvidia driver. Now whenever I boot up the Boot USB or either MacOS or Win10 fails to recognize the eGPU. I'm running the Aorus Gaming box with the RTX 2070 with a 2018 13" MacBook Pro

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


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

When I try to use this on my 2016 MBP - my machine just locks up and I have to reboot.

My Bootcamp is on an external SSD - is this the cause?

Any workarounds at all?

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


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

Hi everyone! My first post!

eGPU is exciting 😀

So I got a Razer Core X and a Radeon RX 580

I connect it to a MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports, no touch bar) using TB3 provided by the Razer Core X.

MacOS no problems at all, its perfect.
Windows 10 Pro Bootcamp I got the Code 12 problem. Still solving that one. That lead me here.

I want to run automate-egpu-efi app but it doesn't boot to it. I used on my MacBook Pro 15" from mid-2014 and it boots to it. So USB Stick is ok.

So I started wondering why is not working with this one (13" with TB3)

I read some more and I Disable System Integrity Protection after Boot intro recovery mode and use the Terminal.

csrutil disable
root

It had encryption with FileVault I disabled it after deleting a profile that ensured it and turned it off.

Still not working.

Sometime it flashed something so I managed to get it on video using my iPhone.

APFSStart:1555: Mounting with apfs_efi_osx-945.260.7
efi_fusion_pairing:668: Container 8bd1ee35-64c8-4b26-8b61-7cb1e68d520f
efi_fusion_pairing:673: fusion uuid: 0000000-0000-0000-00000000000
efi_container_create:972: Volume attached is internal
nx_kernel_mount:1473 : checkpoint search: largest xid 2925171, best xid 2925171 @ 245
No ER state object for volume Preboot - rolling is not happening, nothing to recover.

My volume is APFS. I think my 15" is not. Could that be a problem?

If you have some tips for me would be greatly appreciated. Thank you.

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


ReplyQuote
Branislav Benak
(@branislav_benak)
New Member
Joined: 8 months ago
 

Hi,
I had this problem when the USB stick FAT32 was called "EFI". If it is so, you'll have to rename it. 
But, may be it is not your problem. Just a pointing to some possible error.

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


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

@branislav_benak hi! thank you for trying to help.

I tried two different USB Sticks both are called EGPUBOOT
I used the automate-eGPU EFI v1.0.5 Installer

And they are working on my other MacBook Pro 15" just this one is TB2 and I don't have eGPU connected to it.

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


ReplyQuote
dalroi
(@dalroi)
Active Member
Joined: 10 months ago
 

Seeing that you have a TB3 Mac with an Apple-supported card in your eGPU, you don't need the eGPU EFI boot method.

The Windows error must have some other cause. I doubt the eGPU EFI boot method makes any difference at all there.

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


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago
 

@joaoamaral I have . 2017 Macbook too and the EFI Bootloader works for me, as does rEFInd at times.

IIRC I did have issues with the auto create although I think Maceditor updated it since. You could try and recreate the USB manually, the instructions are in the EFI Bootloader thread and make sure you are super careful how you format the USB, I'm not going to try and guess which it is for fear of accidentally spreading misinformation but there are screenshots of Disk Utility in the thread too.

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


ReplyQuote
Dan Hartman
(@dan_hartman)
Active Member
Joined: 2 years ago
 

Did a recent windows update break this for anybody else?  EDIT:  Just saw the null user post but doesn't look like there's a solution?

My mac mini 2018/vega 56 would no longer give me the windows loging screen.  If I unplug the egpu and boot normally it works fine.  Played around for a while and figured windows maybe got corrupted, so i did a fresh install.

Seems I can get it to work after a fresh 1903 install, but after the windows updates kick in -- not sure which one offhand but I think it was some security update.

So for now I switched back to an nvidia gpu.  That works fine without using the automate-egpu efi boot, but if i do use it i get the same problem where the windwos login screen never shows up.

This is a pretty anooying solution since the nvidia gpu won't work until macos, but with the amd & stock boot I wont have functional internal video.

This post was modified 2 months ago

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


ReplyQuote
Dan Hartman
(@dan_hartman)
Active Member
Joined: 2 years ago
 

Well, turns out part of my problems wasn’t from windows at all, but because I was an idiot and installed a macOS beta.  Seems like it probably updated the firmware, and the OS X spoofing no longer works to enable the iGPU.  Trying to use some different versions with rEFInd’s spoof_osx_version, but haven’t been successfully yet.

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


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

Why i'm unable to boot into windows?
Always stuck at the os choosing screen. I can boot to mac os with no problem.

I'm using imac 4k 2017, sonnet 550, vega 56

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


ReplyQuote
Jihaiki
(@jihaiki)
New Member
Joined: 2 years ago
 

First off, thanks for all of the effort put into this. It seems like a lot people attribute their setup's success to this tool and I imagine it's not a trivial amount of effort to maintain this thing.

I'm here to echo the issues in the replies above. I can select the EFI booter from the OS selection screen on startup, but in my case I immediately gets stuck at this screen: https://imgur.com/a/BuZlHtl

I've tried disabling SIP, as well as booting directly from a FAT partition rather than a USB drive with no luck. Anyone have thoughts on how to work around this?

Hardware:
13" Macbook Pro (2017, no touchbar) | MacOS Mojave 10.14.5
Windows 10 1903 (installed via Bootcamp utility)
Razer Core X + AMD RX 580

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


ReplyQuote
Vrk3ds
(@vrk3ds)
Active Member
Joined: 1 year ago
 

Good Morning,

Has anyone been able to get automate-eGPU to work when you have bootcamp on an external SSD? When I option start and select the EGPUBOOT drive I have installed it to, it hangs when trying to launch Windows with the message at the bottom showing Saving.......

This was working just fine prior to me moving my bootcamp partition to an external SSD. I can launch windows via the bootcamp partition just fine but am losing the ability to drive both my egpu(Vega Frontier Edition in a node pro) and the igpu on my 2018 Mac mini to two external monitors.

I've also tried to use rEFIND but can't even get that to start the boot manager now or prior to moving the bootcamp partition.

Thanks,

2018 Mac Mini 32gb 512 ssd
Akitio Node Pro with Vega Frontier Edition
Dual boot OSX and Bootcamp Windows via External SSD


ReplyQuote
itsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
 

@vrk3ds How many Windows volumes available at boot? As far as I know the automate-eGPU EFI boot loader can only detect one instance of macOS and Windows volume. If there are multiple volumes, it will select the first one found. It's possible external volume is a limitation of automate-eGPU. I can't confirm whether that's the case because I don't use Boot Camp on an external drive. It's not a reliable long-term solution.

 

Best ultrabooks for eGPU use

eGPU enclosure buying guide


ReplyQuote
Vrk3ds
(@vrk3ds)
Active Member
Joined: 1 year ago
 

@itsage

only 1 osx and 1 windows partitions, but several other ssd drives 

and even stranger is that Windows is actually seeing the other monitor? It shows up as second display in display properties, its just black and won't turn on?

This post was modified 4 weeks ago

2018 Mac Mini 32gb 512 ssd
Akitio Node Pro with Vega Frontier Edition
Dual boot OSX and Bootcamp Windows via External SSD


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Noble Member
Joined: 3 years ago
 

Just gave this another bash since I have a new enclosure and it worked perfectly. 
So odd that enclosures do actually make a difference (ti82 vs ti83 chip based).

2017 13" MacBook Pro Touch Bar
GTX1060 + AKiTiO Thunder3 + Win10
GTX1070 + Sonnet Breakaway Box + Win10
GTX1070 + Razer Core V1 + Win10
Vega 56 + Razer Core V1 + macOS + Win10
Vega 56 + Mantiz Venus + macOS + W10

---

LG 5K Ultrafine flickering issue fix


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

@eightarmedpet it probably didn’t work for you previously because this doesn’t include ti82 patches. This can be added to the configuration. When I have some time, perhaps I’ll update the installer script to include this.

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


ReplyQuote
Vrk3ds
(@vrk3ds)
Active Member
Joined: 1 year ago
 

Thank You for all of your hard work on this build guide.

I have a similar build and I am running into some challenges.

My hardware is as follows:
2018 Mac mini 32 gb
OSX Mojave 10.14.5
512 gb ssd
Akitio Node Pro
Vega Frontier Edition
Viewsonic 4k monitor connected to egpu
Viewsonic 4k monitor connected via HDMI on Mac mini
Latest build of Windows on external 750 gb SSD connected via tb3 (Akitio enclosure)

I have tried to use reFIND, and it simply will not load the boot screen? Did you run into any issues with installing it? I used the install script included with the zip file?
Did you have to do anything special to get it working?

When I boot normally via option into windows, it recognizes the egpu, switches the boot process to that display and disables the igpu.

Once Windows loads, it has fully recognized the egpu, and the display properties shows the second(igpu) as a second monitor, but is black(presumably not receiving a signal)

Any thoughts or ideas on any of this would be greatly appreciated

2018 Mac Mini 32gb 512 ssd
Akitio Node Pro with Vega Frontier Edition
Dual boot OSX and Bootcamp Windows via External SSD


ReplyQuote
Civa
 Civa
(@civa)
Active Member
Joined: 2 weeks ago
 

I have an issue you may be able to help me with 
I am running a late 2012 Mac Mini, quad core i7 2.6 GHz, 16 GB DDR3, and two internal SSDs, a 1 TB and a 4 TB 

I have been attempting to set up an AMD Radeon R9 290X, in an AKiTiO Node Pro, but my bigger issue is automate eGPU. 

My monitors are capable of thunderbolt, HDMI, and mini display port 

I currently have the main one connected via thunderbolt.  

Realizing I need the thunderbolt port (this only has one) for the eGPU setup, I’ve connected via hdmi 

the problem is I can’t get a screen in EFI boot mode on hdmi 

I’ve fumbled though it in the dark, so to speak, based on key press memory, and I can finally see the eGPU in the graphics section of the system report on “about this Mac”, but it doesn’t show as main graphics in “about this Mac” (the entry screen), nor do I see it in the icons on the status bar, at the top. 

I suspect o didn’t do it correctly. 

Is there any way I can get the Mac Mini to generate a screen in EFI mode, over HDMI, so I can actually see if I’m doing the process correctly? 

Any and all assistance would be greatly appreciated.

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
 of  23