[APP] NVIDIA eGPU support for High Sierra (NVIDIAEGPUSupport)
 
Notifications
Clear all

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

 of  199
  RSS

vn1minh
(@vn1minh)
New Member
Joined: 3 years ago
 

First of all, I just want to say my thanks to @yifanlu for the great work that you are doing. I was using eGPU on Sierra 10.2.x for a while until today. I would like to share my experience to this thread that hopefully can help others. Below is my spec:

MacBook Pro 15 Mid-2017 TouchBar Radeon Pro 560

Aorus Gaming Box with Nvidia GTX 1070

I have an Acer XB241H plugged into the DisplayPort and a LG LED screen plugged into the HDMI of the eGPU. Both are 1080p display.

I simply followed the instruction on first post to install.

I have SIP disabled completely

My start-up process is: first, not have eGPU plugged in. Starts up Mac until log in screen. Plugs in the eGPU and type my password to login. All of my screens display perfectly fine without any issue.

Additional info that might help others: I previously came from Sierra 10.12.x with just automated-eGPU.sh from @Goalque applied.

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

.

ReplyQuote
biasuz
(@biasuz)
Active Member
Joined: 4 years ago
 
Posted by: goalque
Posted by: biasuz

 

One question.

Is the side effect of this is that it makes the eGPU work in windows without any scripts whatsoever?

I had never used the windows eGPU because I thought it was too gimmicky. As soon as I made it work in High Sierra, since the performance increase was not on par with what I was expecting, I decided to give my win 10 install a try. I booted into windows with the eGPU conected and automatically it did some updates during bootup. But it's working ever since.

I didn't perform any of the tutorials or executed any scripts whatsoever. Anyone else with this experiencing this?

It has, however, the limitations of this install. The external monitor is what makes it work.

macOS and Windows are two disctinct operating systems. Something changed on the macOS user space, has no influence on the Windows boot process. Firmware updates along with macOS 10.13 can change Windows boot behaviour.

Ok. That seems quite inside expectations. 
But if the macOS install has no impact in the windows install I have 2 questions.

1. Why is there a tutorial with scripts and whatever to make it work in windows if it works without any modification?

2. I've read some posts where some users were getting error 12 in windows after implements this kext. Why did they want to uninstall it?

MBP mid-17 R560 + Aorus Gaming Box


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined: 4 years ago
 
Posted by: yifanlu
Posted by: Rycco

Ok, on the file /Library/Extensions/NVDAEGPUSupport.kext/Contents/Info.plist, I found the first one and changed to the second one. Restarting now:

 

<key>DTSDKBuild</key> <key>DTSDKBuild</key> <string>17A360</string> <key>DTSDKName</key> <string>macosx10.13</string> <key>DTXcode</key> <string>0901</string> <key>DTXcodeBuild</key> <string>9A1004</string>

 

 

<key>DTSDKBuild</key><key>DTSDKBuild</key> <string>17B45a</string> <key>DTSDKName</key> <string>macosx10.13.1</string> <key>DTXcode</key> <string>0901</string> <key>DTXcodeBuild</key> <string>9A1004</string>

That's not it. You have to change NVDARequiredOS in each nvidia driver. Like ones that start with NVDA or GeForce.

Thanks yifanlu! I changed the right files and now I don;t get that message anymore, but no eGPU success yet. I tried the sign in without it, plugging in, it does recognize the Thunderbolt profile etc, but when I sign out and sign in again no success 🙁

2017 15" MacBook Pro (RP555) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

ReplyQuote
yifanlu
(@yifanlu)
Eminent Member
Joined: 3 years ago
 
Posted by: Rycco
Posted by: yifanlu
Posted by: Rycco

Ok, on the file /Library/Extensions/NVDAEGPUSupport.kext/Contents/Info.plist, I found the first one and changed to the second one. Restarting now:

 

<key>DTSDKBuild</key> <key>DTSDKBuild</key> <string>17A360</string> <key>DTSDKName</key> <string>macosx10.13</string> <key>DTXcode</key> <string>0901</string> <key>DTXcodeBuild</key> <string>9A1004</string>

 

 

<key>DTSDKBuild</key><key>DTSDKBuild</key> <string>17B45a</string> <key>DTSDKName</key> <string>macosx10.13.1</string> <key>DTXcode</key> <string>0901</string> <key>DTXcodeBuild</key> <string>9A1004</string>

That's not it. You have to change NVDARequiredOS in each nvidia driver. Like ones that start with NVDA or GeForce.

Thanks yifanlu! I changed the right files and now I don;t get that message anymore, but no eGPU success yet. I tried the sign in without it, plugging in, it does recognize the Thunderbolt profile etc, but when I sign out and sign in again no success 🙁

Do you see it in system profiler? Does OSX think there's a new monitor? Do you get the same black screen problem?

NVIDIAEGPUSupport - Nvidia eGPU support for macOS High Sierra
Clover-DSDT+apple_set_os.efi - Macbook Pro Windows error 12 & iGPU fixed Bootloader
---
late-2016 13" MacBook Pro Touchbar + [email protected] (HP OMEN Accelerator) + macOS10.13 & Win10

 
2016 13" MacBook Pro [6th,2C,U] + GTX 1060 @ 16Gbps-TB3 (HP OMEN Accelerator) + macOS 10.13 & Win10 [build link]  


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined: 4 years ago
 

I see this in system profiler:  https://imgur.com/a/RDlFG
But no, the MacOS does not think there's a new monitor. The external monitor is not activated at all.

2017 15" MacBook Pro (RP555) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined: 4 years ago
 

Oh ok maybe you;re looking for this:  https://imgur.com/a/MDDM9

2017 15" MacBook Pro (RP555) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 4 years ago
 
Posted by: biasuz

Ok. That seems quite inside expectations. 
But if the macOS install has no impact in the windows install I have 2 questions.

1. Why is there a tutorial with scripts and whatever to make it work in windows if it works without any modification?

2. I've read some posts where some users were getting error 12 in windows after implements this kext. Why did they want to uninstall it?

My primary OS is macOS. I've not much experimented with Windows recently (unless I have to use Visual Studio). Every MBP has a different firmware, and it's been reported that at least new 2017 MBPs are becoming more plug-and-play on Windows due to Apple's firmware changes. Maybe some users accidentally associated it with this kext. There are so many factors on Windows boot.

automate-eGPU EFIapple_set_os.efi

Mid 2015 15-inch MacBook Pro eGPU Master Thread

 
2018 13" MacBook Pro [8th,4C,U] + Radeon VII @ 32Gbps-TB3 (ASUS XG Station Pro) + Win10 1809 [build link]  


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 
Posted by: yifanlu
 
Is the first problem that using your purge script, the internal display doesn't work anymore? Have you tried the boot option "nv_disable=1"?The second problem is more tricky. Can you hot plug the AMD eGPU and run "sudo sysdiagnose" and send me the result?

Ok, I see that NVIDIA eGPUs work fine on these Mac models - as reported in the Successes list. Anyway, these are my findings:

  • Setting nv_disable=1 results in boot failure on macOS High Sierra, irrespective of script involvement. Prior versions of macOS boot successfully - but do not scale properly on the native display and do not enable acceleration. My script essentially fixes the "acceleration" part if used in conjunction on these older OSes - but not High Sierra.
  • The current state of the script (1.2.1) moves only GeForce kexts, not the core drivers. This means that I allow the GPU to initialize, but prevent it from being used in High Sierra. However, this disables video output via any port - including the Thunderbolt ports. This probably hampers eGPU support. Booting in this state with the eGPU connected never works. The boot process never completes. Essentially, on High Sierra, all my script can do is to stop the dGPU from working but not supporting eGPUs.

 

You requested a sysdiagnose? When exactly do you want it, as soon as I hot-plug it and get the connection notification? Because there is no other working state where I may take the sysdiagnose with the eGPU connected.

 

Also, for clarification, I am using an RX 580 4GB as my eGPU.

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined: 4 years ago
 

Ok, to sum up my experience (failure). Setup:

Macbook Pro 2017 15` Touch Bar Radeon Pro 555
Mantiz Venus

1080ti evga FTW3
Monitor  Asus MG278Q connected thru DP

MacOs 10.13.1 Beta (17B45a)

Steps I went thru:

  1. Enabled SIP
  2. Modified Nvidia Driver Package install to accept my version of MacOS
  3. Installed Nvidia Driver and rebooted
  4. Was getting "Nvidia driver isn't compatible with your MacOS", ignored it and ran the yifanlu package without the eGPU connected
  5. Rebooted with eGPU, nothing
  6. Fixed the "Nvidia driver isn't compatible with your MacOS" message by changing NVDARequiredOS on two files at /Library/Extensions
  7. Tried all combinations of booting, including:
    1. Rebooting without eGPU, logging out, connecting eGPU and logging in.
    2. Hotplug the eGPU on Macos loading
    3. Boot with eGPU connected
    4. Praying and booting

I got those on my system information app: https://imgur.com/a/RDlFG and https://imgur.com/a/MDDM9 . Nothing on the external monitor at anytime. Just to clarify, this setup worked really well on Sierra.

2017 15" MacBook Pro (RP555) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

ReplyQuote
biasuz
(@biasuz)
Active Member
Joined: 4 years ago
 
Posted by: goalque
Posted by: biasuz

Ok. That seems quite inside expectations. 
But if the macOS install has no impact in the windows install I have 2 questions.

1. Why is there a tutorial with scripts and whatever to make it work in windows if it works without any modification?

2. I've read some posts where some users were getting error 12 in windows after implements this kext. Why did they want to uninstall it?

My primary OS is macOS. I've not much experimented with Windows recently (unless I have to use Visual Studio). Every MBP has a different firmware, and it's been reported that at least new 2017 MBPs are becoming more plug-and-play on Windows due to Apple's firmware changes. Maybe some users accidentally associated it with this kext. There are so many factors on Windows boot.

Thanks for the info.

Let it be reported that at least in my MBP 2017 it works in windows right outside of the box... no fiddling around required. no scripts, no EFI, no nothing required.

 

Although it works is macOS right now, in most games I've tested I would not recommend to anyone the upgrade. Bioshock remastered works waaay slower in my aorus gaming box than it does on the embedded RP560.  Maybe the drivers are to blame for this and it will improve overall with a formal release. But, for now, performance on the Mac environment is not commendable.

The only benefit in games on macOS I can see right now is that the fans on the MBP stay around 2000 RPM, so they are nearly silent with gaming use. Other than that maybe we need better drivers before any real evaluation. 

MBP mid-17 R560 + Aorus Gaming Box


ReplyQuote
 of  199