[Sticky] Two new eGPU solutions on macOS 10.13.4: pure EFI and hybrid  

Page 10 / 18 Prev Next
  RSS

goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1158
July 12, 2018 11:09 am  
Posted by: Eightarmedpet

Thanks for the explanation of the 3 different methods. Sounds like EFI does the least tinkering and as I dont care about hot plugging may be the best solution for me.

Did you mean your methods work in Mojave? Couldn't quite work out what you wrote reg that.

If you decide to use "Pure EFI", you will probably miss Apple's built-in external GPU features, including this:
https://egpu.io/forums/mac-setup/potentially-accelerate-all-applications-on-egpu-macos-10-13-4/

Only the "Hybrid" solves AMD dGPU issues, and provides a closed clamshell mode.

This was done in "Pure EFI" mode & Mojave:

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/#post-37780

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/paged/2/#post-37848

Haven't tried the latest beta builds.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 6 months  ago
Posts: 38
July 12, 2018 12:05 pm  

Just tried 1.0.4 on my system. Installed to a newly formatted flash drive using Hybrid (AMD dGPU), selected EFI boot as startup disk, then blank screen. It’s just sitting there, not showing anything - might this be an artefact of 10.13.6? I haven’t plugged in the eGPU - was waiting for the login screen for that.

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1158
July 12, 2018 12:22 pm  
Posted by: Technomad

Just tried 1.0.4 on my system. Installed to a newly formatted flash drive using Hybrid (AMD dGPU), selected EFI boot as startup disk, then blank screen. It’s just sitting there, not showing anything - might this be an artefact of 10.13.6? I haven’t plugged in the eGPU - was waiting for the login screen for that.

Thanks for the report. Interesting that @Gnim got it working and you didn't. Different hardware, different behaviour, I suppose.

What do you mean by "EFI boot as startup disk"? You can't select the "EFI Boot" as startup disk in macOS preferences - "EFI Boot" disk must be selected manually always (hold down the Option key on startup). An external USB is highly recommended.

I've not tried 10.13.6 yet, only 10.13.5. Always possible that Apple has set up roadblocks.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 6 months  ago
Posts: 38
July 12, 2018 12:29 pm  
Posted by: goalque
Posted by: Technomad

Just tried 1.0.4 on my system. Installed to a newly formatted flash drive using Hybrid (AMD dGPU), selected EFI boot as startup disk, then blank screen. It’s just sitting there, not showing anything - might this be an artefact of 10.13.6? I haven’t plugged in the eGPU - was waiting for the login screen for that.

Thanks for the report. Interesting that @Gnim got it working and you didn't. Different hardware, different behaviour, I suppose.

What do you mean by "EFI boot as startup disk"? You can't select the "EFI Boot" as startup disk in macOS preferences - "EFI Boot" disk must be selected manually always (hold down the Option key on startup). An external USB is highly recommended.

I've not tried 10.13.6 yet, only 10.13.5. Always possible that Apple has set up roadblocks.

Sorry, bad terminology: I did select the EFI boot from option key on startup, and using an external USB. It would be interesting to see if anyone else with 10.13.6 has similar issues.

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1158
July 12, 2018 12:52 pm  

@Technomad Would you provide the boot log (debug flag set to true) when the eGPU is disconnected and you boot through the "EFI Boot" selection? Preferably in PM.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
Gnim
 Gnim
(@gnim)
Active Member
Joined: 3 months  ago
Posts: 5
July 12, 2018 1:32 pm  

@Technomad,did you turn off the mirror mode before installing? I had had the mirror mode on, and i had a black screen too. I also turn off the SIP.


ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 6 months  ago
Posts: 38
July 12, 2018 1:37 pm  
Posted by: goalque

@Technomad Would you provide the boot log (debug flag set to true) when the eGPU is disconnected and you boot through the "EFI Boot" selection? Preferably in PM.

Of course - i'll do that later today. A little more information: After I've tried to boot under EFI (having installed in Hybrid AMD dGPU mode) and the screen blanks, when I then shut down and reboot, the system does not recognise the AMD dGPU in either OS X 10.13.6 or Windows 10 (Bootcamp). I have to boot into OS X, then shut down and restart, at which point the AMD dGPU is recognised again in both OS X and Windows.

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


ReplyQuote
Tdr
 Tdr
(@tdr)
New Member
Joined: 5 months  ago
Posts: 1
July 12, 2018 1:57 pm  

I formatted my USB-Stick and installed (1.0.4) Pure EFI.  I selected EFI boot as startup volume and then just the blank screen. The eGPU is plugged in during the boot process.
iMac 5k 2017 – 10.13.6 + Breakaway Box 350 + Nvidia 1080

iMac 5k 2017 – 10.13.6 + Breakaway Box 350 + Nvidia 1080


ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 6 months  ago
Posts: 38
July 12, 2018 3:00 pm  

@goalque - Now this is weird: there's nothing in system.log at all for the period. And of course I can't put it into verbose boot mode, as the screen blanks on start-up. I tried doing it blind, but no evidence of any logging. Anything else to suggest?

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


ReplyQuote
kingbri
(@kingbri)
Eminent Member
Joined: 4 months  ago
Posts: 39
July 12, 2018 3:01 pm  

@goalque, That's the thing, I forgot to select the efi boot entry because I thought that's my windows boot since it is named the same thing, I'm gonna use rEFInd to do this next time (bootmode is SSD internal)

EDIT: it works now, when I hot plug the gpu after logging in, it logs you out and then the Egpu is working, Thanks!

Also, @mac_editor, I'm using your set-egpu script, does it work without an external display or dummy plug?


goalque liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years  ago
Posts: 1266
July 12, 2018 3:40 pm  
Posted by: kingbri

@goalque, That's the thing, I forgot to select the efi boot entry because I thought that's my windows boot since it is named the same thing, I'm gonna use rEFInd to do this next time (bootmode is SSD internal)

EDIT: it works now, when I hot plug the gpu after logging in, it logs you out and then the Egpu is working, Thanks!

Also, @mac_editor, I'm using your set-egpu script, does it work without an external display or dummy plug?

Depends on the app. Try it out - that's the best advice I can give.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
Pavelusha
(@pavelusha)
Active Member
Joined: 2 months  ago
Posts: 9
July 12, 2018 4:50 pm  
Posted by: goalque

 

That's interesting because 650M model should be "Thunderbolt port (up to 10 Gbps)" according to Apple and you should get a message "Only TB2 and TB3 Macs are supported. Please disconnect all TB1 devices." with v1.0.3.

 

However, v1.0.3 didn't find any TB1 devices. Would you run the following command in Terminal, what does it say?

 

ioreg -c IORegistryEntry -d 1 | sed -n -E 's/.*IOThunderboltSwitchType1"=([0-9]+).*/\1/p'

@goalque  I didn't run any commands before install. Some time long ago I ran TB enabler script, may be that did a trick?

All I did I uninstalled EFI boot version 1.0.1  Upgraded to macOS 10.13.6. Ran installer v. 1.0.3. Installed it on a boot volume in Hybrid mode.
The only difference from v 1.0.1 is that now after you hold Option and get into boot menu  "Mackintosh HD" volume has the same icon as EFI Boot instead of looking like a HDD icon.

2012 Retina Macbook Pro 15", AKiTiO Node Pro - Asus GeForce 1080ti 11GB


ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 11 months  ago
Posts: 277
July 12, 2018 4:54 pm  

Great work on 1.0.4 version, @goalque

AMD Hybrid mode appears to work with:
MBP14,2 running 10.13.6
Sonnet 550W
GeForce 1070

Follow-up: once we've successfully booted from the EFI bypass and are in the system, using the eGPU as driver of the main screen, is it OK to unmount the USB drive with the EFI bypass, or does that dongle / hub need to stay connected for the duration of the session? Thus far I've left it intact but am curious.


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1158
July 12, 2018 7:06 pm  

@Tdr Yep, that was very expected as I said that only the Hybrid hot plugging has a capability to solve AMD dGPU + Nvidia eGPU issues. At least with the 2013 Mac Pro and AMD dGPU equipped MBPs, not sure about iMacs.

@Technomad I meant app's own debug log, not the system log. Edit the config.plist file as advised on this thread.

@pavelusha No need to run anything. @mac_editor already explained the reason:

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/paged/9/#post-39702

@chippy-mcchipset Happy to hear that! You can unmount the USB drive after logged into macOS, it's just needed for the "EFI Boot".

The created USB stick is handy especially in "Pure EFI" mode - just plug in the stick to another Mac, no need to install/uninstall anything. Of course, "Hybrid" mode has its own advantages as explained previously.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 11 months  ago
Posts: 277
July 12, 2018 8:44 pm  

@goalque would you expect after successfully running a session, that the system would crash if you do either of these things:
• disconnect the eGPU while still running the main screen
• power off the eGPU (even though still connected) while running the main screen

This seems to be the case with the testbeds I was using today, mix of model ID and OS versions. Guessing the only way is to shut down the OS from the main screen running on the eGPU (i.e. from that Apple menu instance)?


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1158
July 12, 2018 9:13 pm  
Posted by: Chippy McChipset

@goalque would you expect after successfully running a session, that the system would crash if you do either of these things:
• disconnect the eGPU while still running the main screen
• power off the eGPU (even though still connected) while running the main screen

This seems to be the case with the testbeds I was using today, mix of model ID and OS versions. Guessing the only way is to shut down the OS from the main screen running on the eGPU (i.e. from that Apple menu instance)?

Yes, in both cases. It's a normal procedure to shut down. However, crash may not happen if you put Mac to sleep, and disconnect the eGPU. Then reconnect, and wake up. Waking up without the eGPU will result in kernel panic always. @pengus77, C/C++ programmer, might have an idea for hot-unplugging support with an Nvidia card in the future. Not easy to implement, should be Nvidia engineers' duty.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
ozzy
 ozzy
(@ozzy)
Trusted Member
Joined: 1 year  ago
Posts: 71
July 12, 2018 10:08 pm  

@goalque @Pavelusha @mac_editor Thank you to you three!!! This is the first time I've been able to get my eGPU to behave as well for gaming under Mac OS 10.3.x as it did under Mac OS 10.2.x.

I have a MBP 2012 15" Retina with TB1, nVidia 650m, Akitio Node, and GTX 1070 running 10.3.5. I just took the following steps:
1) uninstall @fr34k's script
2) format USB drive to FAT and install version 1.0.3 in hybrid mode, selecting to install the latest nVidia drivers in the process (I used 1.0.3 because of @Pavelusha's reported success, and @goalque saying 1.0.4 was not good for dGPU nvidia computers; it looks like my TB1 MBP doesn't trigger the TB2/3 check in 1.0.3 either)
3) shut down the computer
4) plugged in the eGPU
5) booted holding option, selected EFI boot, and booted up

At this point everything went fine, Heaven benchmark worked and was accelerated, etc. However, the metal game I always try, Hitman, still did not work (gave me a warning about being unsupported and then ran at about 1-2 FPS). When looking at the Activity Monitor GPU History it was clearly using the 650m. I downloaded @mac_editors set-eGPU script and used it to set Hitman to prefer eGPU. Then I re-ran Hitman and it worked, used the 1070, and ran flawlessly like it did under 10.2.x. I hadn't been able to accelerate it (or any other metal games) since upgrading to 10.3.x, so this is an amazing step. Interestingly, using @fr34ks script and the "prefer removable" string when @mac_editor first discovered it a week or two ago (before releasing his script) didn't actually work or accelerate Hitman, so this clearly works in a way that never did.

Now with everything finally working, it's time for 10.4.x to break it all again 🙂

2012 15" Macbook Pro Retina GT650M + GTX1070@10Gbps-TB1 (AKiTiO Node via TB3->TB2 adapter) + macOS10.13 & Win10


ReplyQuote
Pavelusha
(@pavelusha)
Active Member
Joined: 2 months  ago
Posts: 9
July 12, 2018 10:43 pm  

@ozzy, Sorry, yes I forgot to mention that I ran set-eGPU script too 🙂

Apple just released new MacBook Pro!  It's interesting if this solutions still work on it...

P.S. Kinda funny that they don't give you a choice whether  you wanna get a dGPU or not, but at the same time push at you Black Magic eGPU box with Radeon Pro 580.  

2012 Retina Macbook Pro 15", AKiTiO Node Pro - Asus GeForce 1080ti 11GB


ReplyQuote
n9yty
(@n9yty)
Eminent Member
Joined: 11 months  ago
Posts: 20
July 13, 2018 5:28 am  

Trying again with the 1.0.4 release. MacbookPro11,5 w/AMD R9 M370X and Intel Iris Pro. Trying to use the Auros Gamebox 1070.

Installed on SD Card using Hybrid AMD mode.

Did a reboot, and logged in.
Plugged in eGPU
Waited while the system logged me out
eGPU monitor came on as second screen, internal display black
Thinking it was waiting for login, I blindly typed my username, tab, password, enter
system logged in, internal display turned on
Everything seems to be working pretty well

Will do more testing


ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 6 months  ago
Posts: 38
July 13, 2018 10:54 am  

@goalque - PM sent, with debug log.

HTH

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


ReplyQuote
kingbri
(@kingbri)
Eminent Member
Joined: 4 months  ago
Posts: 39
July 13, 2018 12:56 pm  

@goalque, when booting, is there a way to force the efi boot entry instead of holding down alt and using it? refind doesn't work, gets stuck at booting os.


ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 11 months  ago
Posts: 277
July 13, 2018 2:58 pm  
Posted by: goalque
Posted by: Chippy McChipset

@goalque would you expect after successfully running a session, that the system would crash if you do either of these things:
• disconnect the eGPU while still running the main screen
• power off the eGPU (even though still connected) while running the main screen

This seems to be the case with the testbeds I was using today, mix of model ID and OS versions. Guessing the only way is to shut down the OS from the main screen running on the eGPU (i.e. from that Apple menu instance)?

Yes, in both cases. It's a normal procedure to shut down. However, crash may not happen if you put Mac to sleep, and disconnect the eGPU. Then reconnect, and wake up. Waking up without the eGPU will result in kernel panic always. ...

Thanks for confirmation. Not sure if this is on the "roadmap" for Hybrid solutions but it would be cool if there was a mechanism that allowed for ending the eGPU session without shutting down or using sleep-wake workarounds. Sort of a "nice to have" but not a deal-breaker if we can't. Thank you again for your continued efforts. Apple owes you a debt in my opinion for doing their homework for them.

I know the history that NVIDIA has not treated Apple well over the years, but Apple's approach here (to ignore NVIDIA because of that) has the dual effect of hurting customers, which is not great. It would be possible for them to support NVIDIA via eGPU without supporting them financially by including their dGPUs in Macs or bundling their cards with eGPUs. Seems there's no middle ground with Apple.


ReplyQuote
hkoster1
(@hkoster1)
Active Member
Joined: 10 months  ago
Posts: 19
July 13, 2018 4:34 pm  

@goalque Version 1.0.4 Hybrid AMD works fine on my 2017 15-inch TB RP560 MacBook Pro/Sonnet 550/GTX 1080 Ti, great work, thanks.

What is exactly the difference between Hybrid AMD and Clamshell? I'm asking because I usually close the MBP screen. Do I have to uninstall/reinstall or is it just an entry in some .plist to be edited?


ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 11 months  ago
Posts: 277
July 13, 2018 6:34 pm  

@goalque 

When installing any given hybrid method, does it make a difference what NVIDIA GPU is installed in the box? For example, in the following scenarios, would something different end up getting installed on the USB drive and local drive?

Model ID: different but both have AMD dGPU and TB3
OS: same
box: same
gpu: same

Model ID: same
OS: different (all 10.13.4 or later)
box: same
gpu:same

Model ID: different but both have AMD dGPU
OS: same
box: same
GPU: different

My reason for asking  boils down to: if we're using the same Hybrid mode but the initial install hardware setup was different, should I expect that moving that USB drive from one similar model ID to the next or switching the GPU, that it might not work the same as it did on the original? I.E. once you install with a particular dGPU setup, that install won't work for any other dGPU setup?

[I should add to this cable type: HDMI vs DP at time of installation, vs. what's used when booting / logging into the eGPU session.]


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Prominent Member
Joined: 2 years  ago
Posts: 852
July 13, 2018 7:53 pm  

Oddly the latest build didn't work for me. No errors but black screen (both). Initial app worked. Set up in sig.

2017 13" MacBook Pro Touchbar + GTX1060@32Gbps-TB3 (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + GTX1070@32Gbps-TB3 (Sonnet Breakaway Box) + Win10
---
LG 5K Ultrafine flickering issue fix


ReplyQuote
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Joined: 11 months  ago
Posts: 277
July 13, 2018 8:19 pm  

Anyone else seeing problems with color balance / gamma when running 1.0.4 over HDMI connections, specifically that the screen takes on a very orange tint?


ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 6 months  ago
Posts: 38
July 13, 2018 9:05 pm  
Posted by: hkoster1

@goalque Version 1.0.4 Hybrid AMD works fine on my 2017 15-inch TB RP560 MacBook Pro/Sonnet 550/GTX 1080 Ti, great work, thanks.

What is exactly the difference between Hybrid AMD and Clamshell? I'm asking because I usually close the MBP screen. Do I have to uninstall/reinstall or is it just an entry in some .plist to be edited?

That's interesting - almost identical setup to me, but mine doesn't work at all!

Mid-2017 MBP 15”/3.1GHz, Razer Core v2, EVGA GTX1080Ti, LG 34UM95, HTC Vive, Samsung Odyssey, MS Hololens.


ReplyQuote
(@daniel_varnai)
Eminent Member
Joined: 8 months  ago
Posts: 20
July 14, 2018 8:24 am  
Posted by: Technomad

Just tried 1.0.4 on my system. Installed to a newly formatted flash drive using Hybrid (AMD dGPU), selected EFI boot as startup disk, then blank screen. It’s just sitting there, not showing anything - might this be an artefact of 10.13.6? I haven’t plugged in the eGPU - was waiting for the login screen for that.

same issue with 10.13.6, hybrid iGPU mode, gtx1070. I have the boot debug log if youd like to take a look. my mbp is a 2017 15" with radeon 560 and intel 630


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1158
July 15, 2018 11:26 am  
Posted by: kingbri

@goalque, when booting, is there a way to force the efi boot entry instead of holding down alt and using it? refind doesn't work, gets stuck at booting os.

No, not at the moment. Maybe in the future. The default boot volume is always the one defined in config.plist's "DefaultVolume" key and the default disk image on Apple's boot manager is always what you have defined in "Startup Disk" (nvram variable). Clover's nvram setting didn't work well.

@chippy-mcchipset if you're not using "Pure EFI", you should always reinstall on each machine. automate-eGPU.kext needs to be created anyway in "Hybrid" mode. If both machines have AMD dGPU, the same config.plist might work.

Posted by: khoster1

Version 1.0.4 Hybrid AMD works fine on my 2017 15-inch TB RP560 MacBook Pro/Sonnet 550/GTX 1080 Ti, great work, thanks. What is exactly the difference between Hybrid AMD and Clamshell? I'm asking because I usually close the MBP screen. Do I have to uninstall/reinstall or is it just an entry in some .plist to be edited?

Nice! 10.13.4, 10.13.5 or 10.13.6? With Hybrid AMD/iGPU mode you can use both the internal and eGPU screens, the clamshell mode disables your internal screen. Switching between Clamshell mode and AMD dGPU/iGPU on-the-fly isn't yet supported, you can only use one at a time, and if want to change mode, uninstall/reinstall.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
markbam
(@markbam)
Active Member
Joined: 1 year  ago
Posts: 18
July 15, 2018 3:43 pm  

Version 1.0.4 Hybrid AMD confirmed working on my 2017 15-inch MacBook Pro (TouchBar (RP560)), Aorus Gaming Box (GTX 1080), and MacOS 10.13.6.

Mid-2017 MacBook Pro 15 inch Touchbar (Radeon Pro 560)
- Akitio Node (Radeon 580)
- Aorus Gaming Box (Geforce GTX 1080)


goalque liked
ReplyQuote
tmy82336506
(@tmy82336506)
New Member
Joined: 4 months  ago
Posts: 2
July 15, 2018 6:06 pm  

Thanks. If it's 13-inch that should be Hybrid iGPU right?


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1158
July 15, 2018 6:17 pm  
Posted by: tmy82336506

Thanks. If it's 13-inch that should be Hybrid iGPU right?

Yes, 13" MBPs are iGPU only and the closed-clamshell mode is meant for AMD dGPU MBPs for now.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
kingbri
(@kingbri)
Eminent Member
Joined: 4 months  ago
Posts: 39
July 15, 2018 10:58 pm  

@goalque, I may have made a discovery with the hybrid mode. when my mac was off, the egpu was plugged in. I booted it, selected the efi boot disk and the egpu was instantly recognized since it made an animation to recognize my "second monitor" during the apple boot screen. I checked this and it said that the display was recognized, and therefore the gpu is recognized. This experience did not need the egpu hotplugged after login, the computer just recognized it all by itself


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1158
July 16, 2018 9:21 am  

@kingbri That's how it's been working before, and may still work with v1.0.4 but hot plugging is the recommended way in hybrid mode.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
(@alex_gao)
Active Member
Joined: 7 months  ago
Posts: 9
July 17, 2018 6:38 am  

Which mode to choose if I have a iMac (Retina 5K, 27-inch, Late 2014)?


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1158
July 17, 2018 7:09 am  
Posted by: alex gao

Which mode to choose if I have a iMac (Retina 5K, 27-inch, Late 2014)?

No one has tested this with the 5K iMac, I would try "Hybrid (AMD dGPU)". Hot plug after logged in.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
Page 10 / 18 Prev Next