macOS High Sierra Supplemental Update!!!
 
Notifications
Clear all

macOS High Sierra Supplemental Update!!!  

 of  2
  RSS

Tim Irvin
(@ziggy029)
Active Member
Joined: 4 years ago
 
Posted by: Eightarmedpet

Just bought a 1070... first boot I experienced error 12 (as I did with my 1050 and 1060) but was prompted to restart to finish setting up new hardware, after that it's all good... not getting much of a performance increase over my 160 though so may swap back (1060 6GB the sweet spot for U class CPU's?).

Yes, it will depend some on the speed of your interface but there are clearly diminishing returns above some point regardless.  I have a TB1 interface on my late 2012 Mini, so I am using a 1050Ti under 10.12.6.  I'm set to borrow an RX580 in the next few days and I'll try that under High Sierra (I have two bootable partitions on this machine, one still on Sierra for the GPU compatibility and one sandbox running HS).  

If I see considerably better performance I may actually go out and get one, but I suspect the 10 GB limitation of the TB1 interface might lead to diminishing returns and the 1050 Ti will be "enough" for now, even as the RX580 might do much better under TB3, for example.  

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

.

ReplyQuote
NvidiusMaximus
(@nvidiusmaximus)
New Member
Joined: 4 years ago
 
Posted by: Naragato

Before people start speculating,  I'm fairly sure that this update did nothing to improve eGPU compatibility either in bootcamp or in MacOS.

 

I agree. Nothing in Apple's documentation that suggests improvements made to the eGPU setup. Maybe because eGPU is considered beta software for now,  it's possible they could update things without listing them in the official support documents. The only way to be sure would be to check the package contents. There was a fix for InDesign but it's not related to eGPU stuff.

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

.

ReplyQuote
eth
 eth
(@eth)
New Member
Joined: 4 years ago
 

I can confirm that something had changed after one of the high sierra updates (10.13.1?).

I don't see a large memory entry like in the brand new 2017 macbooks, but the left-closest port now definitely works without disabling any controllers.

And what's indeed surprising is that it's actually plug'n'play like on my dell xps 9550: i can plug the card in with windows booted up or disconnect it; when i was using right tb ports such operations (other tb/usb devices count too) almost 100% resulted in instant black-screen reboot.

Though using right-sided ports still results in error 12 and left-farthest port doesn't work at all, windows gets frozen on the bootscreen if the enclosure is already connected or requires a reboot when it is hot-plugged. But maybe i'm simply not lucky enough...

Had discovered this after the latest high sierra update, before this i was using right ports with disable x8 controller method, no dsdt/clover & no rEFInd since i use an external display.

My config is MBPr 2016 Radeon Pro 455 + Aorus 1070 gaming box w/external display, latest non-insider preview windows 10.

Feel free to ask for any detailed info you need.

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

.

ReplyQuote
mgarito
(@mgarito)
New Member
Joined: 4 years ago
 
Posted by: NvidiusMaximus
Posted by: Naragato

Before people start speculating,  I'm fairly sure that this update did nothing to improve eGPU compatibility either in bootcamp or in MacOS.

 

I agree. Nothing in Apple's documentation that suggests improvements made to the eGPU setup. Maybe because eGPU is considered beta software for now,  it's possible they could update things without listing them in the official support documents. The only way to be sure would be to check the package contents. There was a fix for InDesign but it's not related to eGPU stuff.

As of 10.13.2 Beta (17C60c) the AMD Radeon Pro WX7100 (inside a sonnet breakaway box) is at least being flagged by the OS whereas in 10.13.1 this card wasn't even being recognized last week on 10.13.1.  More specifically, now I get a "to use this eGPU you must logout and log back in" notification, however doing so locks up the OS. Baby steps I guess...

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

.

ReplyQuote
Sereosh
(@sereosh)
Active Member
Joined: 4 years ago
 

I updated and checked on Boot Camp since some people have seen changes with their setup. 

Well it's still the same for my 15" 2016 MBP w/Radeon Pro 460 and AORUS Gaming Box 1070. I still need to do integrated.bat/apple_set.efi/disabling PCIe lanes to get the eGPU to work properly. 

On the left ports, Windows freezes on boot if eGPU is connected. On the right ports, the eGPU is detected and Windows boots (and no error 12). Some applications seem to use it but I I get terrible performance. I figured I could try to update the display driver, no dice. So I restored Windows back and I guess I'll keep using the good old (working) procedure.

It's interesting that @mklegend has seen improvements. Maybe it's because he's using a Mantiz Venus

Also, the updates removes rEFInd.

2016 MBP 15"
Radeon Pro 460 dGPU
AORUS Gaming Box 1070 eGPU
macOS 13.16.6


ReplyQuote
mklegend
(@mklegend)
Eminent Member
Joined: 4 years ago
 
Posted by: Sereosh

I updated and checked on Boot Camp since some people have seen changes with their setup. 

Well it's still the same for my 15" 2016 MBP w/Radeon Pro 460 and AORUS Gaming Box 1070. I still need to do integrated.bat/apple_set.efi/disabling PCIe lanes to get the eGPU to work properly. 

On the left ports, Windows freezes on boot if eGPU is connected. On the right ports, the eGPU is detected and Windows boots (and no error 12). Some applications seem to use it but I I get terrible performance. I figured I could try to update the display driver, no dice. So I restored Windows back and I guess I'll keep using the good old (working) procedure.

It's interesting that @mklegend has seen improvements. Maybe it's because he's using a Mantiz Venus

Also, the updates removes rEFInd.

I've updated to High Sierra v10.13.1 (17B48) and checked bootcamp for any changes, thankfully everything is running as originally mentioned in my first post here.

No errors, all PCIe controllers are enabled and I'm using the right side TB3.

Please note that windows device manager still shows the eGPU and the non-detected dGPU, and doesn't show the iGPU, may be it'll work for you if you followed the same workflow I referred to in this comment:  https://egpu.io/forums/mac-setup/macos-high-sierra-supplemental-update/#post-21420

Best Regards,

Mohammad Katayen (mklegend)


ReplyQuote
Sereosh
(@sereosh)
Active Member
Joined: 4 years ago
 

I did everything you wrote. The eGPU is definitely detected when I plug it in the top right port (the only one that works), but I think Windows still uses the dGPU (which has no drivers) to run applications, resulting in poor performance. Are you running an external monitor? I don't have one, maybe this is why I still have trouble.

2016 MBP 15"
Radeon Pro 460 dGPU
AORUS Gaming Box 1070 eGPU
macOS 13.16.6


ReplyQuote
 of  2