Setup & Software Discussions
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (Razer Core V2) + mac...
 

2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (Razer Core V2) + macOS 10.14.5 & Win10 1809 [Ningauble77]  

  RSS

Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

System Specs:
2018 13" MBPro 16GB/i7/1TB
Sapphire Radeon VII 16GB
MacOS 10.14.5 Public Beta 2
Windows 10 Build 1809

egpu Hardware:
Razer Core v2
HP Spectre 32 32" UHD Display via Displayport
Cable Matters 6' TB3 Cable

Installation Steps:

macOS:
Installed Radeon VII into enclosure, installed MacOS 10.14.5 beta.  On hotplug or  at boot time Radeon VII is detected automatically.  The eject widget is present as normal.  The external display is not currently automatically detected at either boot time or upon initial hotplug.  I have to disconnect/reconnect displayport cable, turn off/on monitor, eject and re-hotplug the egpu, or close the MacBook lid to get the external display detected and working.  I've experienced occasional issues with DisplayPort audio where the sound starts coming from the MacBook speakers instead of my display's headphone jack, and the HP Spectre 32 is missing from the sound control panel, ejecting the egpu and reconnecting it usually fixes this.

Win10:
Used DDU to uninstall existing nvidia drivers from my previous rtx 2080 egpu.  Booted into windows again with no peripherals attached.  Hotplugged the egpu.  Installed latest AMD Adrenalin software (19.4.1).  Radeon VII is yellow banged with event 12.  Radeon Installer asks for reboot, I click ok. 

Next boot, internal display is stuck at windows logo, but external display comes live with login screen.  There is a message about a new system profile asking to reboot again.  Before I can say yes the display goes dark.  I wait a few minutes and force shutdown with the power button.  Subsequent boots into bootcamp with egpu attached at boot works with the internal display disabled on the windows logo, and sleep missing from the windows menu power options.  Otherwise seems fully functional.

Benchmarks:
I've been unable to run Unigine benchmarks in MacOS for mysterious reasons possibly related to the beta OS.  I have run a fair number of benchmarks in Win10.  All benchmarks were run on external display.

AIDA64:

AIDA64

Unigine Valley:

unigine valley R7

3DMark Fire Strike:
https://www.3dmark.com/fs/19027727
3DMark Time Spy:
https://www.3dmark.com/spy/6881572
3DMark Time Spy Extreme:
https://www.3dmark.com/spy/6885390

Comments:  I had been hoping to have an egpu setup that would let me use my MacBook pro as my universal computing device, for MacOS and Windows work and play.  I had been waiting for official nvidia support since Dec 2017 when I had first bought the core v2 and moved over one of my GTX 1080 cards from my desktop.  After 1.5 years of waiting I have given up hope of there being proper nvidia support in Mojave.

The Radeon VII in windows is noticeably slower than the RTX 2080 card I was previously using, but is still acceptable for most of the games I play.  World of Warcraft and Elder Scrolls online are a few fps slower than the RTX, but generally stay above 60fps in non-cpu bottlenecked portions of the game.  Hellblade Senua's Sacrifice is noticeably less smooth than the RTX card but still playable at 4k Ultra settings.  No Man's Sky is borderline playable at 4k with alot of stuttering issues and texture filtering strangeness I did not experience with the 2080.  Forza Horizon Demo gets about 50fps at 4k vs 59fps with the RTX Card.  I've seen lower than normal performance at times due to clocks being stuck at 1350mhz, which is possibly a holdover from a reboot from MacOS, but I have been unable to consistently reproduce this issue.  Loading up hwinfo and confirming that the card is clocking up to 1770mhz or so makes sure I am getting normal performance.

Performance in MacOS games (World of Warcraft/Elder Scrolls Online/Diablo3)  is currently a mixed bag, I am hoping it will improve as the drivers mature and reach an official release.  Power consumption is noticeably lower running the same game in MacOS vs Windows, which makes me think that the beta drivers are running at lower than usual clocks for now.

Sleep behavior in MacOS has been a pleasant surprise.  When I select sleep from the apple menu, after about a minute the egpu powers down and all usb peripherals power off as well.  Then after a short wait they come back on, run for about 30s, then go back to sleep, usually for good. I have seen the enclosure and connected peripherals come back on during sleep once or twice randomly, but this happens on the order of once or twice over a span of several hours for only about 30s or so.

Before my Air conditioner was turned on in the room I have the egpu in, the core V2 has gone into the highest fan-speed state I've seen before while gaming in windows.  The noise was pretty awful.  After setting the room to 72 degrees F, the noise is still loud but no longer sounds like a vacuum cleaner.  The Radeon VII itself is louder than the 2080, but the fans don't have the horrible whine that the Core V2 PSU fans make.

This topic was modified 4 months ago

2018 13 Macbook Pro + Core v2 + Radeon VII Win10 1903/MacOS 10.14.6
ASUS X99 Deluxe+Core v2 + Radeon VII Win10 1809


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

@ningauble77 Nice build! If you use @goalque's automate-eGPU EFI, you will be able to keep the iGPU activated booting into Windows. That will prevent the stuck Windows logo on the internal display as well as allow internal display acceleration by eGPU loopback.

Best ultrabooks for eGPU use

eGPU enclosure buying guide


goalque liked
ReplyQuote
OliverB
(@oliverb)
Noble Member
Joined: 10 months ago
 
Posted by: itsage

@ningauble77 Nice build! If you use @goalque's automate-eGPU EFI, you will be able to keep the iGPU activated booting into Windows. That will prevent the stuck Windows logo on the internal display as well as allow internal display acceleration by eGPU loopback.

I don't have this macbook model anymore to test, but could it be possible that the "uninstall trick" prevents the internal display to go blick. It prevents it with well the 15-inch 2018 model.

@ningauble77
after hotplugging the eGPU and getting Error 12 you could try to uninstall the eGPU in Device Manager and immediately reboot. Those steps are described in this bootcamp guide under Section C)
You don't have to follow the complete guide. Just boot without eGPU plugged in, hot-plug it and then follow C7 and C8.

This post was modified 4 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
 

@oliverb For me it didn't change anything. I've the same setup, except Asus XG Station Pro. I wonder why it would be beneficial because the operating system is not aware of the EFI side. Inactivated iGPU results in blinking eGPU monitor (DP-DP connection) too, on login screen. And you've the stuck Windows logo on the internal display.

Works perfectly with automate-eGPU EFI and Multiple displays setting "show only on 2".

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


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

@goalque
thank you for this information. Of course, it was only an attempt.

For reasons unknown the internal display gets blacked/stuck on Windows logo on the 15-inch models, too when booting with eGPU plugged in (AMD and nVidia eGPU alike). The "uninstall gpu"-trick solves the issue with those models.
Another important information is that Error 12 is prevented by booting with eGPU plugged in. This works for 2015, 2017 and 2018 MacBooks and 2018 Mac Mini. It would be interesting to know about 2016 and 2014 and earlier models.

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


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

PCIe enumeration is not trivial for eGPUs that have large BARs. Apple has its own algorithm for macOS, and it is much better than what we see in Windows. I found a patent filed by Intel. May be related to their Thunderbolt software for PC laptops and recent Windows 10 versions.

https://patentimages.storage.googleapis.com/9e/5c/d8/4dee1666567b59/US20170185525A1.pdf

"The scalability limitations of resource allocations by the traditional PCI enumeration algorithm is clearly evident in usage scenarios for PCI based SSDs devices (for example, based on NVMe) and in Thunderbolt hierarchies, where these limitations do not allow large/deep hierarchies to be configured. This creates errors where the user is unable to use devices in such configurations. For example, there could be situations where more than 256 PCI based solid state drives need to be connected to a single system or there could be hot-plugged devices such as that for Thunderbolt where the resources reserved for a given portion of the tree are insufficient to configure the hot-plugged Thunderbolt devices. In these scenarios, the traditional PCI enumeration algorithm depletes the scares BDF resource very quickly due to allocation mechanisms such as equally dividing and allocating the available bus numbers among all hot plug capable ports. The traditional approach of using rebalancing to redistribute resources, as discussed earlier, is not suitable for many use cases. The new algorithm proposed in this disclosure addresses these limitations in conjunction with the MPB to significantly improve resource configuration and scalability in such scenarios."

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


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

I have been guessing since long ago, that recent Versions of Windows 10 allocate the PCIe resources much better for eGPUs then they did before. (Yet not as good as MacOSX though). Something must have changed as I found several builds where users had issues I could not reproduce with the exact same hardware.

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
 
Posted by: OliverB

I have been guessing since long ago, that recent Versions of Windows 10 allocate the PCIe resources much better for eGPUs then they did before. (Yet not as good as MacOSX though). Something must have changed as I found several builds where users had issues I could not reproduce with the exact same hardware.

Windows respects ACPI tables in the firmware during the boot. This hasn't changed recently but what is changed is the firmware. Apple saw our workarounds and now the "Large Memory" in the Device Manager comes by default with new Macs. That helps a lot in most cases but it is still a workaround.

Intel's Thunderbolt software doesn't help with Mac firmwares. AFAIK, it is the key element in PCIe resource allocation on Windows PCs, when you hot plug the device. The D3 is the lowest power state of the device, for example when you put a computer to sleep or a surprise removal occurs.

https://downloadmirror.intel.com/26486/eng/Thunderbolt%20Release%20Notes.pdf

Added support for Windows* 10 RS3 Native PCIe Enumeration ("Native Express" mode) and Selective Suspend (RTD3) state.

This post was modified 4 months ago

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


itsage and OliverB liked
ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

Ok, thanks to @Colonel Blimp, I have Heaven and Valley working in MacOS.  Here are some benchmark results for the extreme HD preset, and also 4k with 4x MSAA:

unigine valley r7Macos
unigine valley R7macos 4k

unigine valley R7 4k
unigine heaven r7macos
unigine heaven r7macos 4k

2018 13 Macbook Pro + Core v2 + Radeon VII Win10 1903/MacOS 10.14.6
ASUS X99 Deluxe+Core v2 + Radeon VII Win10 1809


itsage liked
ReplyQuote
Beta
 Beta
(@beta)
New Member
Joined: 3 months ago
 

Thanks for taking the time to post this.  I am very seriously considering doing this exact build.  I have never used MacOS but have an iPhone, AppleTV, Apple Watch, Apple Music etc, so would like to be able to put the rest of the ecosystem together while still having the option to do some gaming in Windows and be mobile in a laptop form factor.

I also play WoW, and currently I have a desktop windows PC with a GTX 1080 hooked up to 3 matching 4k monitors.  I would like to keep the monitors the way they are and hook up the 2018 MBP 13 to a Razer Core X Chroma with a Radeon VII and hopefully be able to run everything ok in both environments.  Do you think there will be any issues with this based on your experience?  Ideally, I can run WoW in 4k (I can do so now on my current rig) at about 60-65 FPS.

Thanks in advance!

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


ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

I haven't used multiple monitors attached to my Radeon VII but I don't see any reason it shouldn't work.  WoW runs better in Windows than MacOS with my setup, but both run smoothly enough I am happy running it at 4k ultra in either OS (Elder Scrolls Online on the other hand, the MacOS client is choppy and stuttery with unpredictable multiple-second hangs even when the fps is near 60, and it often dips into the 30's regardless of settings).  The only major concern I would have is the Radeon VII running the fans at full during sleep or shutdown.  I haven't experienced this issue but my experience is extremely uncommon, and noone has determined why most are having this issue and I have not.

2018 13 Macbook Pro + Core v2 + Radeon VII Win10 1903/MacOS 10.14.6
ASUS X99 Deluxe+Core v2 + Radeon VII Win10 1809


ReplyQuote
Technomad
(@technomad)
Eminent Member
Joined: 1 year ago
 

I'm trying the same build, except for using my 2017 MBP 15" under 10.14.6. MBP sees the Razer v2, the card spins up and lights up, but the system refuses point blank to see the Radeon VII, under either MacOS or Windows. Just one very basic check here: the Core v2 comes with a 6+2 pin and a 6-pin power connectors - how are these plugged in to the 2 * 8-pin connectors on the Radeon VII? The RVII Quickstart guide seems to imply that connecting the 6 & the 2 to the inboard 8-pin socket and the other 6-pin to the outboard 8-pin socket should work. Am I missing something?

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


ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 2 years ago
 

Quick update on the build.  I've replaced my HP Spectre 32 with a Samsung CRG9 32:9 ultrawide monitor, and a couple of interesting things have happened:

1) The Samsung is detected at hotplug/boot time by MacOS Mojave, where I would need to power cycle the HP Display, or go to the display control panel, hit Alt/Option and click on "Detect Displays" in order for it to work.

2) If I leave the MacBook display open I now get True Tone on the Samsung, this was not available/functional on the HP.  Not a big deal, to be honest the Samsung looks better with the default colors.

3) Similarly, Night Shift is available and functional with the Samsung and was not in the control panel for the HP.

4)  In order to run at the native resolution of [email protected], I had to hold alt/option while clicking on scaled resolutions.  Additionally, the resolution scaling options in MacOS are poor with the Samsung.  5120x1440 works fine, but due to the lack of subsample AA in Mojave, text does not look very good.  3840x1080 is available, but this is not scaled by the OS, it just puts the monitor into 3840x1080 mode and lets the monitor do the scaling, which looks blurry.  Several other scaled resolutions are available, nearly all of them actually put the monitor into 3840x1080 mode and do not scale to the native resolution.  The only scaled resolution which maps directly to 5120x1440 is 2560x720, which actually looks great but everything is way too big.  At some point I may play with SwitchresX to see if I can get something equivalent to 125% scaling in windows.

My understanding is that the drivers for the built in gpu's offer a completely different list of resolutions on these 32:9 displays, with better scaled resolution options.  I have not tested this due to not having a usb-c to displayport cable.

5)  Windows 10 by and large looks fantastic, The drop in PPI is much less noticeable, and text rendering is readable and reasonably sharp.

6) On occasion, DisplayPort Audio does not initialize when booting into Windows, and the XConnect Notification blares out on my MacBook's speakers.  This can be remedied by turning the display off then on.

7) HDR games and video look quite good in windows, although the 32:9 aspect ratio leaves a lot of unused space when watching most video content.

Also, I recently replaced the PSU fans on the Core v2 with 40mm Noctuas, but any improvement to noise levels is very subtle, and the annoying high pitched whining under heavy load isn't really mitigated.  Although the fans were inexpensive, and the procedure was not too complicated, I would say its not worth the effort.

This post was modified 4 days ago

2018 13 Macbook Pro + Core v2 + Radeon VII Win10 1903/MacOS 10.14.6
ASUS X99 Deluxe+Core v2 + Radeon VII Win10 1809


itsage liked
ReplyQuote
joevt
(@joevt)
Reputable Member
Joined: 2 years ago
 

@ningauble77

If you want a HiDPI (retina) mode for 3840x1080 (133% scaling), then you need to create a scaled mode in SwitchResX of 7680x2160. Make sure the "Scaled resolutions base" is set to 5120x1440. Saves change and restart.

125% scaling means using a 4096x1152 resolution, so you should create a 8192x2304 scaled resolution to get a 4096x1152 HiDPI mode.

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


ReplyQuote