2016 15" Gigabyte Aero 15 GTX1060 + [email protected] (AKITiO Node) + Win10 [pyroxide]  

  RSS

pyroxide
(@pyroxide)
Active Member
Joined: 1 year ago
Posts: 5
August 15, 2018 1:14 pm  

System specs
Gigabyte Aero 15 (i7-7700HQ, GTX 1060, 1080p)
32GB (2x16GB) Kingston Impact DDR4-2400 (model HX424S14IBK2/32)
2x Samsung 960 Pro 1TB NVMe SSDs (model MZ-V6P1T0BW) (both with 4B6QCXP7 firmware)
GTX1060 dGPU
Windows 10 (any version from GTX 1080 Ti's release date)
Any Nvidia GeForce drivers supporting the GTX 1080 Ti (398.82 available, but using 398.36 because of MH: World performance bug)

eGPU hardware
Gigabyte GTX 1080 Ti Aorus Waterforce Xtreme Edition (model GV-N108TAORUSX W-11GD)
Akitio Node
Silverstone 600W SFX PSU (model SST-SX600-G)
Acer Predator X34 ([email protected], G-SYNC) (plugged into eGPU DisplayPort)
Oculus Rift+Touch (connected to eGPU HDMI, each sensor plugged directly into laptop)

Hardware pictures

 

 

Installation steps
While not always necessary, disabling the dGPU in BIOS it prevents games from using the wrong GPU.

Benchmarks

Firestrike 1.1 @ 2076 MHz core/6016 MHz memory = 14,853
http://www.3dmark.com/fs/16095328
Superposition 1080p Extreme @ 2062 MHz core/6014 MHz memory = 5663 (42.36 fps avg)
Valley Extreme HD @ 2088 MHz core/6016 MHz memory = 4132 (98.8 fps avg)

Comments
CUDA-Z reports incorrect "host to device" bandwidth.
All tested games at maximum settings have a sustained FPS higher than 50 at 3440x1440. 85+ FPS is more common.
VR performance is exceptional on Oculus Rift. Untested on Vive or Vive Pro.
My eGPU is currently overclocked with MSI Afterburner @ +60 MHz core and +400 MHz memory with the power limit at 130% (thanks to the 600W PSU) and temp limit to 80C.

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


nando4 and theitsage liked
ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1815
August 16, 2018 12:53 am  
Posted by: pyroxide

Comments
CUDA-Z reports incorrect "host to device" bandwidth.

CUDA-Z is reporting the correct H2D bandwidth. It seems Gigabyte has not as yet corrected the hosting PCIe port for the TB3 controller to run at x4 3.0 rather than x4 2.0. Can read about this issue here.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2015 15" Dell Precision 7510 M1000M + macOS 10.14 & Win10


ReplyQuote
pyroxide
(@pyroxide)
Active Member
Joined: 1 year ago
Posts: 5
August 19, 2018 7:01 pm  
Posted by: nando4
Posted by: pyroxide

Comments
CUDA-Z reports incorrect "host to device" bandwidth.

CUDA-Z is reporting the correct H2D bandwidth. It seems Gigabyte has not as yet corrected the hosting PCIe port for the TB3 controller to run at x4 3.0 rather than x4 2.0. Can read about this issue here.

If that's the case, then why does HWiNFO report 3.0 4x for PCIe bus root port #5 (the one containing the TB3 controller) as well as every device down that branch?
EDIT: Upon further research, the September 2017 BIOS update addressed this issue.

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
pyroxide
(@pyroxide)
Active Member
Joined: 1 year ago
Posts: 5
August 22, 2018 8:05 am  

As proof that CUDA-Z is outdated and incorrect, I would also like to point out that if this eGPU were running at 16 Gpbs, then it would show in the Firestrike benchmark.
So go ahead and update the title to say 32 Gbps.

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1815
August 22, 2018 8:30 am  

@pyroxide,  please run a AIDA64 GPGPU benchmark to see bandwidth to and from eGPU and post.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2015 15" Dell Precision 7510 M1000M + macOS 10.14 & Win10


ReplyQuote
pyroxide
(@pyroxide)
Active Member
Joined: 1 year ago
Posts: 5
August 22, 2018 9:06 am  

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


nando4 liked
ReplyQuote
pyroxide
(@pyroxide)
Active Member
Joined: 1 year ago
Posts: 5
November 12, 2018 12:58 pm  

I have had great success using this setup in Linux Mint 19 Tara with Cinnamon DE. There are some quirks and I will share them for anyone who may be interested in them.

Configuration:
dGPU still disabled in BIOS
Linux Mint 19 Tara (Cinnamon)
Linux kernel 4.15.0-38
Proprietary Nvidia driver 390 (I have had no luck with 396 or 410)

The largest caveat that I have experienced for this configuration is that the eGPU will not function from cold boot into Linux Mint. There is a workaround, however; I must first boot Windows to the login screen, then I can restart and boot to it. I believe this has to do with the Thunderbolt 3 device being trusted.

Both recent proprietary driver releases, nvidia-driver-396 and nvidia-driver-410, have given me nothing but headaches. After installing either of these drivers, I cannot even get to the DM, but instead the monitor will flash every second, trying to send signal, then quit and the monitor tells me no signal. So I am stuck with nvidia-driver-390.

For monitor overclocking, I have had to set the desired resolution and refresh rate in Nvidia X Server Settings (under Administration) and apply changes. Then under Mint menu->Preferences->Display, apply to save this on next boot. I also configured GRUB to use my monitor's native resolution and am using "quiet splash nomodeset"

What is working?
Steam; I have only tested Rise of the Tomb Raider, BioShock Infinite, and Stardew Valley (all seem to be functioning properly)
Steam Play beta; Killing Floor 2 works (minus voice chat, but that's not specific to this configuration)
VLC; "XVideo output (XCB)" must be selected. 4K H.265 seems to play fine (I only lost a few frames, probably because it was being downscaled to 3440x1440).

Soon I will add my system & eGPU details or a build link to this my signature to give context to my posts


ReplyQuote