2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 @ 32Gbps-TB3 (AORUS Gaming Bo...
 
Notifications
Clear all

2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 @ 32Gbps-TB3 (AORUS Gaming Box) + macOS 10.13.2 & Win10 [Markus Koepke]  

 of  3
  RSS

Markus Koepke
(@ghostronaut)
Eminent Member
Joined: 3 years ago
 

Info: Originally, this was a post i started because I had issues getting my Gaming Box to work on my machine. I have since resolved those issues and have updated the post title. In the following I describe my setup und method of getting the Gaming Box 1080 to work. The original post is quoted at the bottom of this post, for safekeeping.

## UPDATE 09.12.208 ##
For some reason, I’m now only getting an fps reading of about 115fps as opposed to 147 in Heaven, as was the case back in January. Haven’t made any major changes to the system apart from Nvidia driver updates. I tried rolling back to the January driver, but no change in performance. Hope I can figure out what’s causing this!

Aorus Gaming Box 1080 on Macbook Pro 15" 2017 (Touch Bar) with Radeon 560

I have now gotten my Gaming Box 1080 to work without much issues in macOS High Sierra as well as Windows 10 (Bootcamp).

It only works with an external screen, I have not followed the efi / integrated.bat tutorial to get it to work on the laptop screen! I might try that in the future, for now I'm happy that its working at all 😉

Initially I had all kinds of trouble getting the Box to be recognized under Windows 10. Following are some insights into my installation process and current setup for both macOS and Win10.

macOS High Sierra

Installing the Box on macOS was not much of a hassle, all I had to do was install the script by Yifanlu ( https://egpu.io/forums/mac-setup/wip-nvidia-egpu-support-for-high-sierra ) so I could install Nvidia Web Drivers. After that, it was a simple matter of plugging in the Gaming Box (I'm using the left side Thunderbolt ports, although there are reports that all of them work) and I was good to go.

Startup process macOS: Boot into macOS login screen, hot plugin Gaming Box with external screen attached. Wait until the OS recognises the Box and the external screen takes over. Login, and you are good to go. Do not plugin the Box before the login screen. macOS will not recognise it properly and you will have issues (well, I do at least). Hot plugging in the box during runtime requires at least a log out, but I would not recommend it.

Shutdown process macOS: Haven't found a good way of doing this yet. Hot-unplugging the Box crashes macOS, but even shutting down macOS and then unplugging the Box results in a "Your system had to restart because of a problem" screen. It seems the Box keeps the machine running even after shutdown. So yes, right now I am shutting down the OS, unplugging the Box and accepting the fact that the OS reboots after that. I hope this is resolved in future High Sierra updates, I have not yet tested the new Beta which is supposed to have much better eGPU support.

Benchmarking:

As I use macOS for productive purposes (video editing, color grading), I have not much interest in gaming on this OS, but I did a Heaven benchmark anyways:

a01
a03

Not bad, I'd say. For those of you who also use their mac for content creation: I set up Davinci Resolve to use CUDA with the Gaming Box and got about 300%  (!) increase in render speed on an effects heavy project (all clips with noise reduction and 5+ nodes). Which is, pretty awesome. Although I have now less time for coffee breaks. Oh well.

Windows 10 (Bootcamp)

Installing on Windows10 was ... cumbersome, at first. I had issues. Lots of them. When I finally got the Box to be recognized and kind of work, the output I got was nowhere near what it should be (~40fps Heaven Benchmark values and the like, Prey on 1920x1200 Ultra ~30fps). After some Windows update (which I hoped would improve things) nothing worked anymore. The Box wasn't even recognized anymore.

So what I did is, I used the "restore PC" function under Windows. Essentially, I decided to set up Windows 10 fresh. I guess you could also do a proper clean install, but I wanted to try this (much faster) option first. So, I reset Windows. Then, I had to go back into macOS and startup the Bootcamp Assistant, as all the Bootcamp drivers where obviously deleted in the reset process, and not much was working under Windows anymore. In Bootcamp Assist, go to the top menu item "Action" and hit "Download Windows support software". It will download all the drivers you need for your Bootcamp partition. I placed them on the root of the Bootcamp partition. You can also store them on a USB stick, but thats not necessary. 

After that, booting back into Windows, I installed all the Bootcamp drivers. Restart after (actually, restart after every driver you install, ever).

Now I dared to plugin my Gaming Box. Voila! Windows did some background setting up and suddenly my external screen came to life. Clicking around a bit I could already feel that this was much more responsive than before my reset. So I downloaded Nvidia Geforce Experience, installed the newest Geforce driver. Restart after that obviously. Everything felt good, time for some ... 

Benchmarking:
 
 

Screen Shot 2018 01 25 at 15.18.47
 
That's a nice score. In Prey I now get an almost constant 60fps on 1920x1200 Ultra with V-Sync. Occasionally it drops to about 54fps. Awesome stuff!
 
So, if you are having issues like me, all I can recommend is resetting / clean installing Windows. It wasn't much of an issue for me since my machine is fairly new and I hadn't set up much in Windows yet.
 
Startup process Win10: So this is important. Boot into Windows and at the swirling dots hot plugin the Box. It's now or never. If you plug it in before that, Windows doesn't seem to recognise it. If you plug it in after, same problem. 

Shutdown process Win10: Just shutdown and then unplug the Box. Hot unplugging doesn't seem to crash the system though.

 
 

----

Original Post:

Hi,

after quite some trouble I finally got my Gaming Box to work under Bootcamp. The H2D and D2H readout is 2260/2677 when I start without an external screen attached to the Gaming Box (I can plug it in after boot, but if I have it plugged in at boot, I get lower readouts).

An issue I'm having is, that when I plug in an external screen via HDMI from the Gaming Box, I can not set that screen to be the main screen under display settings. That is to say I *can* set it that way in the settings, but it doesn't work. My Macbook screen continuous to be the main screen. Also I have to set everything to "duplicate screen", otherwise the scaling is off on my external device (and I can not change the scaling settings). So right now the only way this works without the scaling being way off is with the screens being mirrored, wich is kind of annoying as I basically would like to close the lid of my Macbook and only use the external screen. Any advice?

Thanks!

Macbook Pro Touchbar 2017 i7 3.1Ghz Kaby Lake 16GB Ram | Aorus Gaming Box 1080 | HTC Vive

 
2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 @ 32Gbps-TB3 (AORUS Gaming Box) + macOS 10.13.2 & Win10 [build link]  


ReplyQuote
ghoulish31
(@ghoulish31)
Active Member
Joined: 2 years ago
 

I wish I had an answer for you on this but I just wanted to say I have the exact same hardware as you (2017 15" MBP with RP560 and the 1080 AGP) and after trying for 12+ hours to get it to work in Boot Camp yesterday, I had zero success. I tried disabling PCIe lanes (1901 and 1905) but that led to quirks where Windows wouldn't boot or the touch bar wouldn't turn on in macOS.

I could only get as far as running apple_set_os.efi and integrated.bat, installing the Intel drivers and forcing iGPU in Boot Camp, but then all I got was a horribly flickering internal screen and nothing at all on my external monitor.

I'm about to give up. 🙁

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Markus Koepke
(@ghostronaut)
Eminent Member
Joined: 3 years ago
 

Sorry to hear that 🙁 I had a lot of trouble as well, mainly because I crashed the machine while installing the Nvidia drivers on the first try and Windows was totally screwed after. I honestly couldn't tell you how I got it to work ...

One thing regarding "same setup": I have the Radeon 560. Not that that should make any difference.

Macbook Pro Touchbar 2017 i7 3.1Ghz Kaby Lake 16GB Ram | Aorus Gaming Box 1080 | HTC Vive

 
2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 @ 32Gbps-TB3 (AORUS Gaming Box) + macOS 10.13.2 & Win10 [build link]  


ReplyQuote
ghoulish31
(@ghoulish31)
Active Member
Joined: 2 years ago
 

Oops - typo. Mine has the 560 too. But I'm tempted to sell the thing until all these issues sort out - I thought I had a stronger stomach Smile

Maybe I'll have more luck trying to get it to work in macOS instead of Boot Camp?

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
TheOkeland
(@theokeland)
Active Member
Joined: 2 years ago
 

Hey,

just got my Aorus Gaming Box 1080 an tried to get it running in Windows (Bootcamp). Getting it to run was no Problem, just plug&play, one reboot after driver installation and I was ready to go. But looking at the H2D and D2H speeds in CUDA-Z, I am experiencing only 16XX (H2D) and 17XX (D2H). The D2D Performance is about 100GiB/s. I expected values around 22XX and 26XX.

The eGPU is connected to the top-right port of my MBP.

I just unintentionally updated to macOS 10.13.3, now Windows does not even use the eGPU anymore...

I will try a complete reinstall I suppose.

 

@ghostronaut Could you tell us which problems you had and how you solved them?

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
ghoulish31
(@ghoulish31)
Active Member
Joined: 2 years ago
 

@TheOkeland - which MBP do you own? Does it have the RP560?

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
TheOkeland
(@theokeland)
Active Member
Joined: 2 years ago
 

@ghoulish31

Yes indeed a MBP 2017 15” RP560.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Markus Koepke
(@ghostronaut)
Eminent Member
Joined: 3 years ago
 
Posted by: TheOkeland

Hey,

just got my Aorus Gaming Box 1080 an tried to get it running in Windows (Bootcamp). Getting it to run was no Problem, just plug&play, one reboot after driver installation and I was ready to go. But looking at the H2D and D2H speeds in CUDA-Z, I am experiencing only 16XX (H2D) and 17XX (D2H). The D2D Performance is about 100GiB/s. I expected values around 22XX and 26XX.

The eGPU is connected to the top-right port of my MBP.

I just unintentionally updated to macOS 10.13.3, know Windows does not even use the eGPU anymore...

I will try a complete reinstall I suppose.

 

@ghostronaut Could you tell us which problems you had and how you solved them?

I had some issues getting it to work in the beginning because I screwed up my Nvidia driver install. Other than that, it was mainly plug & play. I had the same H2D/D2H values as you at first. I'm not sure why, but now I get the expected 22xx / 26xx. I think you have to start the Macbook with the Box already attached. This post helped me a lot:  https://egpu.io/forums/builds/quick-review-on-aorus-gtx-1080-gaming-box/

Macbook Pro Touchbar 2017 i7 3.1Ghz Kaby Lake 16GB Ram | Aorus Gaming Box 1080 | HTC Vive

 
2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 @ 32Gbps-TB3 (AORUS Gaming Box) + macOS 10.13.2 & Win10 [build link]  


ReplyQuote
ghoulish31
(@ghoulish31)
Active Member
Joined: 2 years ago
 

@ghostronaut Thanks - I remember my first attempt pretty much followed that post and I did end up with the AGB being recognized by Windows, but any time I ran a game, it would run on the RP560 and not the eGPU.

That's when I started going down the path of figuring out how to disable the RP560 dGPU, but this only led to screen flickering issues and Windows boot lockups. I've also never been able to get anything to show on my external monitor connected to the eGPU via DP.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Markus Koepke
(@ghostronaut)
Eminent Member
Joined: 3 years ago
 
Posted by: ghoulish31

Oops - typo. Mine has the 560 too. But I'm tempted to sell the thing until all these issues sort out - I thought I had a stronger stomach Smile

Maybe I'll have more luck trying to get it to work in macOS instead of Boot Camp?

Funny thing: In macOS it worked without any issues. Just had to install that script that lets you install Nvidia web drivers, plug in the Box, log out and in again - boom.

Macbook Pro Touchbar 2017 i7 3.1Ghz Kaby Lake 16GB Ram | Aorus Gaming Box 1080 | HTC Vive

 
2017 15" MacBook Pro (RP560) [7th,4C,H] + GTX 1080 @ 32Gbps-TB3 (AORUS Gaming Box) + macOS 10.13.2 & Win10 [build link]  


ReplyQuote
 of  3