2017 13" MacBook Pro TouchBar + GTX1070@32Gbps-TB3 (Aorus Gaming Box) + macOS10.13 & Win10 [lexine]^  

 

lexine
(@lexine)
Eminent Member
Joined:5 months  ago
Posts: 22
October 6, 2017 2:25 pm  

Hi all,

this is my first experience with implementation of the egpu. During the implementation I encounter some of the small issues which I eventually resolved by  “trail & error”. Once I completed the implementation I decided to perform a new installation of Windows to have the clean install, the 2nd attempt went very smoothly :). In this guide I would like to share my experience & issues I encounter during the configuration of egpu (as best to my knowledge, as I did not take the notes ;-).

Lets start:

1. Attempt

  • Installation of Windows 10 via BootCamp
    – during the first steps I already encounter the 2 issues:
       1.BootCamp was not able to create my windows partition due to local time machine snapshots (I had to remove them)
            To list local snapshots: “tmutil listlocalsnapshots / ” & remove “tmutil thinlocalsnapshots / 10000000000 “
       2. My MSDN Windows ISO was 1703 version which is no-go for BootCamp installation, therefore I downloaded Win10_1607 version.
    – Once I fixed above the installation was done properly.
  • I done some studies before so I decided immediately to update the Aorus firmware to fix H2D issue
    – Followed the @theitsage guide
    – Update went very smoothly I did not encountered any serious issues as far as I remember
    – I think at this point I still did not installed the GTX drivers yet
  • Installed the drivers for GTX from NVIDIA website, GPU was recognised and working properly
  • I had some issues with the unknown devices in device manager, probably during my play with thunderbolt drivers update, so at this point I decided to reinstall completely windows

2. Attempt:

  • Installed Windows via BootCamp (no isses, I already knew:))
  • Boot the Windows, perform the Intel Driver installation from web, and done the recovery safe point
  • Connected the Aorus Box, was recognised I installed the drivers from Nvidia website
  • Checked the H2D with cuda-z, as I was confused from last time whether it was patched properly, but it looks OK
  • Done

Basically my 2nd attempt was a plug & play experience (no error 12). However I encounter the issue that macbook is disabling my iGPU when the egpu is connected during the startup, so basically I had to perform the hotplug when Windows boot logo appeared.

To fix the above issue I simply follow again the general guide – Boot Camp eGPU Setup Guide for Thunderbolt 3 MacBook Pro and installed refind+apple_set_os.efi

I did encounter the issue with refind as it was not able to detect my MacOS partition, I guess it is related the APF + macOS HighSierra, basically I had to manually create the macOS stanza as per the refind&apfs . My final stanza :

menuentry “My macOS” {

    icon \EFI\refind\themes\rEFInd-minimal\icons\os_mac.png

    volume “Preboot”

    loader \AF1E80A3-A625-387F-A278-E680E2CB3D2D\System\Library\CoreServices\boot.efi

    graphics on

    enabled

}

I used the “graphic on” in addition to the reddit guide, as otherwise there was some nasty kernel text on screen during the booting:).

 Some benchmarking :  

Edited: 3 months  ago

2017 13" MacBook Pro TouchBar + GTX1070@32Gbps-TB3 (Aorus Gaming Box) + macOS10.13 & Win10


nando4 liked
ReplyQuote
lexine
(@lexine)
Eminent Member
Joined:5 months  ago
Posts: 22
October 6, 2017 4:12 pm  

It seems that I am getting some H2D bandwidth degradation when I am using the apple_set_os.eif instead of hot-plugging at Windows boot logo.

 

Host to Device – apple_set_os.efi: Host to Device – hot-plug at Windows boot:
Edited: 5 months  ago

2017 13" MacBook Pro TouchBar + GTX1070@32Gbps-TB3 (Aorus Gaming Box) + macOS10.13 & Win10


nando4 liked
ReplyQuote
lexine
(@lexine)
Eminent Member
Joined:5 months  ago
Posts: 22
October 6, 2017 5:48 pm  

I am investigating and testing the above H2D performance, and I am not sure whether it is really related to rEFInd+apple_set_os.efi.
When I change method and boot the windows with hotplug during the windows logo after first boot I get error 12 and Windows ask to reboot to resolve, I will do the reboot again with hotplug and the GTX1070 is working normally with proper H2D performance … I can do multiple reboots with same method and it is ok. 

As soon as I boot with apple_set_os.efi Windows will encounter again after first boot error 12 and ask to reboot. After rebooting again with same method it is working flawlessly without the problem.

So every time I switch the method how I bot the Windows I need to perform one more reset to resolve the error 12 …
So I assume that H2D performance might be related how windows automatically resolve the error 12 ?
But it is just an idea. Not sure how to confirm… 

2017 13" MacBook Pro TouchBar + GTX1070@32Gbps-TB3 (Aorus Gaming Box) + macOS10.13 & Win10


ReplyQuote
atomsapple
(@atomsapple)
New Member
Joined:5 months  ago
Posts: 2
October 6, 2017 6:28 pm  

I’m using a 2017 13″ MacBook Pro nTB, and have had a ton of issues since receiving my AORUS GTX 1070 Gaming Box last Sunday. My goal here was to utilize my work 13″ MBP as my home gaming solution. I come home, plug in a single TB3, and I’m good to game using the internal monitor.

I could never get rEFInd to work with my APFS Encrypted volume. Being locked out, I was able to get into Recovery, kill rEFInd and implement apple_set_os.efi as a direct replacement for bootx64.efi. Eventually I got the thing setup. I could only ever get it to work with the MBP turned all the way off, and then manually plugging in the TB3 cable and having it boot to Windows. Any attempt to hot plug at the Windows logo would result with either a boot and the eGPU not being seen, or a freeze on the Windows boot logo, with graphical glitches.

I thought I had the process all figured out, but 3DMark Time Spy would would fail after a few seconds. UNIGINE Heaven would run without issue at Extreme setting. UNIGINE Valley at Extreme HD when benchmarking would fail 3/4 of the way through, crashing the app. I tried to play Mortal Kombat XL and find crazy horizontal screen distortion on the bottom half of the screen. Attempting to launch Planet Coaster, the thing would crash to desktop after a few minutes of play. DOOM and Rocket League on the other hand, worked fine!

Eventually, I threw in the towel and killed my Bootcamp partition. I restarted the computer to macOS to find severe screen flashing. No number of PRAM resets or booting from Internet Recovery would fix the issue. It also seemed my Mac installation was now borked as I couldn’t access any files. After a few hours, I turned the computer on again to find my Mac installation working properly, but with a bit less screen flashing. Eventually it subsidized and the computer has been working fine. I’m of the notion now that I have a bad logic board and need to get the computer fixed.

Can you do me a favor and try these benchmarks with your internal MBP monitor only, no external monitor plugged in? Maybe try some of your games on your internal MBP monitor, and let me know if you’re seeing anything buggy or glitchy? If you’re not, then that pretty much confirms after I get my logic board replaced that I’ll be fine to continue down this path, or will require a replacement AORUS Gaming Box, if that’s at fault. I just want to know I’m not wasting my time going down this path. I reaaaaaaaaally want this to work. It’s the most cost and space effective way for me to PC game and with all of the success you and others are having, why can’t I have success?


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined:1 year  ago
Posts: 1578
October 7, 2017 12:55 am  

@lexine, apple_set_os.efi is a good workaround solution particularly for 15″ MBPs where it activates the iGPU such that the dGPU can be disabled to free up resources. Consider that it’s mechanism of operation is to fake a macOS boot. There may be other unintended side effects when doing that which you’ve identified two of already:

1. a lowered H2D TB3 eGPU performance. We have noted that CUDA-Z runs under macOS do give these same lower H2D results.

2. Different pre-allocation of PCIe devices when booting a Windows versus fake macOS boot. Hence the requirement to do a reboot to resolve error 12 when switching to either bootup mode.

As your 13″ MBP allows hotplugging at the Windows logo, I would advise using this method to do your Windows boot. Consider adding a boot menu delay to allow easier timing of that hotplug:

bcdedit /set {bootmgr} displaybootmenu yes
bcdedit /set {current} bootmenupolicy Legacy

REF: tenforums

 

Edited: 5 months  ago

eGPU Port Bandwidth Reference TableeGPU Setup 1.35


theitsage liked
ReplyQuote
lexine
(@lexine)
Eminent Member
Joined:5 months  ago
Posts: 22
October 7, 2017 9:32 am  

@atomsapple: Sorry to hear about your problems.

1. rEFIND : I don’t think direct replacement of boot.efi with apples_set_os.ef was a good solution (anyway I am still new to macOS booting process), if your APFS was not recognized by rEFInd you can always boot a macOS standard way – holt the “option key” during the startup of PC, it should automatically bring you standard macOS boot loader (manager?) and you can start the macOS normally (I done it this way till I got my rEFInd to detect macOS partition). 

2.macOS: Does it work properly now ? Do you still have the screen glitchy / buggy problems ?  Before any replacement I would suggest you to backup the important data, and try to reinstall completely your macOS via recovery and afterwards install the windows. For some of the first testing you don’t need the rEFInd or something. Just boot into Windows connect graphic card and install drivers. Do the shutdown disconnect the cable, turn of the PC with option key pressed, select Windows to boot and plug the eGPU. 

3. games: I did tested the Mass Effect Andromeda & Witcher on internal screen it seems ok.

Here is the UNIGINE Valley benchmark (only internal screen) : 

@nando4: Thanks for your input. Well all the reason behind the apple_set_os.efi was my comfort, that I don’t have to do hotplug everytime when I boot Windows … It would be nice to solve this issue somehow, but it is not critical : -) .

2017 13" MacBook Pro TouchBar + GTX1070@32Gbps-TB3 (Aorus Gaming Box) + macOS10.13 & Win10


ReplyQuote
(@a_thibault)
Active Member
Joined:5 months  ago
Posts: 8
October 11, 2017 11:37 am  

Installed Windows via BootCamp (no isses, I already knew:))

Boot the Windows, perform the Intel Driver installation from web, and done the recovery safe point

Connected the Aorus Box, was recognised I installed the drivers from Nvidia website

I’m stuck here. Posting everywhere, looking at every forum or reddit post but still can’t find any solution. My Aorus Box is still undetected. I have TB3 drivers installed but still 0 reactions on ports. I have uninstalled Windows and tried again and again i just cant make it work 🙁


ReplyQuote
lexine
(@lexine)
Eminent Member
Joined:5 months  ago
Posts: 22
October 11, 2017 3:36 pm  

Did you used Apple out-of box thunderbolts drivers which installed directly with Windows? Or you tried to installed latest ones ? 
As I remember I used the original out-of-box, so after Windows installation, I just plug Aorus installed NVIDIA drivers, rebooted with option key to select Windows, once the Windows boot logo showed I hot-plug the Aorus, and it was detected in the Windows properly.

2017 13" MacBook Pro TouchBar + GTX1070@32Gbps-TB3 (Aorus Gaming Box) + macOS10.13 & Win10


ReplyQuote
moe7946
(@moe7946)
New Member
Joined:4 months  ago
Posts: 2
October 15, 2017 9:26 pm  

I have the exact same problem. On both Mac and Windows(with apple_set_os.efi) I get around 1600 MiB/s H2D which is way lower than the average we see here.

It is annoying but for windows you can kind of fix it by hotplugging as @lexine said, but the problem is the MacOs.

What I’m guessing is that MacOS somehow restricts the bandwidth on TB3 on boot and because apple_set_os.efi is a fake MacOS boot, it is also restricted after it is booted to windows. 

Really hope someone can come up with a solution.


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined:1 year  ago
Posts: 1578
November 28, 2017 9:12 am  

Upgraded to macOS10.13

From [APP] NVIDIA eGPU support for High Sierra (NVIDIAEGPUSupport)

Posted by: lexine

Got it working MBP 13 2017 TouchBar & Aorus Gaming Box… I downloaded the NVIDIAEGPUSupport-f233ad3ccf11b8752425a8e4974c0606f5552db4 commit, builded the kext copy over to /Library/Extensions, updated the owner and rebuild the cache … external screen is working, cuda-z as well .. but I am not sure on display tab I still have :

1

2

However rest seems ok :

3
4

 

Edited: 3 months  ago

eGPU Port Bandwidth Reference TableeGPU Setup 1.35


ReplyQuote
  
Working

Please Login or Register