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

Page 5 / 54 Prev Next
 

Chippy McChipset
(@chippy-mcchipset)
Estimable Member
Joined:8 months  ago
Posts: 187
October 25, 2017 10:21 pm  
Posted by: yifanlu

Just delete /Library/Extensions/NVDAEGPUSupport.kext to uninstall.

On second look, that's the name of the app not the web drivers, right? I guess technically to start clean I'd need to remove both but initially was asking about the web drivers themselves.

In that directory, I'm seeing:

CUDA.kext

GeForceTeslaWeb.kext (guessing this is one element of it)

GeForceWeb.kext (and the other element)

and a bunch of 

NVDA-------Web.kext files too

Presumably since there is no Nvidia hardware in this machine, would be save to remove them all but asking in case not.


ReplyQuote
mac_editor
(@mac_editor)
Prominent Member Moderator
Joined:1 year  ago
Posts: 826
October 25, 2017 10:23 pm  
Posted by: yifanlu

Just delete /Library/Extensions/NVDAEGPUSupport.kext to uninstall.

I would recommend doing this in superuser mode via a Terminal command only. In my experiments with kexts, deleting them directly via UI (even after the password prompt) has left my disks unbootable in many instances (at least for the system library extensions)  

Just to be safe, for those wanting to uninstall, I suggest this command: sudo rm -r /Library/Extensions/NVDAEGPUSupport.kext

Edited: 7 months  ago

purge-wrangler.shpurge-nvda.sh

Guides:
Mid-2014 15" MacBook Pro GT750M + RX480@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter) + macOS & Win10
Mid-2014 15" MacBook Pro GT750M + GTX980Ti@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter) + macOS


ReplyQuote
goalque
(@goalque)
Prominent Member Admin
Joined:1 year  ago
Posts: 882
October 25, 2017 10:27 pm  

By the way, Samsung U28D590D (DP-DP interface) may display black sometimes on the boot up process if it is sleeping, and then you're stuck. Press the back power joystick button, and the progress bar & Apple logo should show up, or hot-plug the monitor after you've logged in. This happened earlier too.

Edited: 7 months  ago

automate-eGPU.shapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
mbnwa
(@mbnwa)
Active Member
Joined:9 months  ago
Posts: 16
October 25, 2017 10:28 pm  
Posted by: Excubitoro

I tried switchresX , but had sip active so couldn’t install the helper. It didn’t work without it in any case, just got errors and restart when trying to log in with egpu attached.

anyone with a MacBook Pro 2016 15” and 1060/1070 that got it to work with sip disabled and changing colors to millions?

I have a 2017 Macbook Pro Touch Bar + 1080TI (SIP Disabled / Millions)

 

 


ReplyQuote
yifanlu
(@yifanlu)
Eminent Member
Joined:7 months  ago
Posts: 41
October 25, 2017 10:31 pm  
Posted by: mac_editor

Nice work @yifanlu! Things looking good for eGPUs haha. I have a question for you though.

I have been trying to get native AMD eGPU acceleration to work on macs with built in NVIDIA graphics cards (for example - 2014 15" MBP). By default, these macs don't work. After reading the thread, I noticed that you mentioned patching something associated to the NVIDIA framebuffer - which could be one of the potential issues preventing an AMD eGPU to work on these kinds of models. I have tried stuff:

https://egpu.io/forums/mac-setup/nvidia-workaround-for-high-sierra-egpu-acceleration/

But currently, there is no solution for the latest HS build to get the eGPU up and running. Perhaps what you might have done here might be applicable with modifications for this case. I would be happy if you could consider looking into this.

On the other hand, if the issue is with the clashing NVIDIA and AMD drivers/framebuffers, then your solution should accelerate NVIDIA GPUs on High Sierra on these macs without issue.

So there are two things to look at here:

  • Can using this enable NVIDIA eGPUs without bugs on Macs with built in NVIDIA chips?
  • Can using a modification of this package allow AMD GPUs to work too?

Of course, the latter seems a little less likely.

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?

Edited: 7 months  ago

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 + GTX1060@16Gbps-TB3 (HP OMEN Accelerator) + macOS10.13 & Win10


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:1 year  ago
Posts: 225
October 25, 2017 10:44 pm  

Hey guys, I'm 10.13.1 Beta (17B45a), I tried to install Nvidia drivers but it says it doesn't support this version. Is there anything I could do to install it? I wanna test on my Macbook Pro 2017 + Mantiz Venus + 1080ti.

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
theitsage
(@itsage)
Noble Member Admin
Joined:1 year  ago
Posts: 2389
October 25, 2017 10:46 pm  
Posted by: yifanlu

I've updated the first post with a list of successes, successes after hotplug fix, and failures. I'm trying to see what is common to all the people who are getting black screen errors (me included). A common thread seems to be MBP 2016/2017 + GTX1060/1070 combo.

madjazz reported that "With SIP fully disabled everything is working fine." Can anyone else with the black screen error report if they have SIP fully disabled or just "-without kext"?

EDIT: Another thing I've experienced is that during shutdown, my internal monitor turns fully cyan for a second or two before shutting down. This is regardless if eGPU is attached or just an external TB3 monitor. Has anyone else experienced this?

I had SIP disabled completely during the Nvidia web driver installation and your NVDAEGPUSupport.kext installation. CUDA works and System Information shows the right name. Backlight without output is the only issue as reported. This was with a 2016 13" Touch Bar MacBook Pro. The behavior is the same on a GTX 1070 as well as GTX 980 Ti.

Also of note is that I have Goalque's automate-eGPU.kext on this laptop too. The two workarounds do not seem to interfere with one another.

Edited: 7 months  ago

Best ultrabooks for eGPU use

eGPU enclosure buying guide

51 external GPU build guides


ReplyQuote
yifanlu
(@yifanlu)
Eminent Member
Joined:7 months  ago
Posts: 41
October 25, 2017 10:52 pm  
Posted by: Rycco

Hey guys, I'm 10.13.1 Beta (17B45a), I tried to install Nvidia drivers but it says it doesn't support this version. Is there anything I could do to install it? I wanna test on my Macbook Pro 2017 + Mantiz Venus + 1080ti.

Extract the package

pkgutil --expand orig.pkg somedir

Modify somedir/Distribution and remove the line <installation-check script="InstallationCheck();"/>

Recreate the package

pkgutil --flatten somedir new.pkg

You can now run new.pkg without checks.

After installing, if it still doesn't work you might need to go into each installed kext in /Library/Extensions and modify Info.plist and change NVDARequiredOS to your build version.

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 + GTX1060@16Gbps-TB3 (HP OMEN Accelerator) + macOS10.13 & Win10


Rycco liked
ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:1 year  ago
Posts: 225
October 25, 2017 10:59 pm  
Posted by: yifanlu
Posted by: Rycco

Hey guys, I'm 10.13.1 Beta (17B45a), I tried to install Nvidia drivers but it says it doesn't support this version. Is there anything I could do to install it? I wanna test on my Macbook Pro 2017 + Mantiz Venus + 1080ti.

Extract the package

pkgutil --expand orig.pkg somedir

Modify somedir/Distribution and remove the line <installation-check script="InstallationCheck();"/>

Recreate the package

pkgutil --flatten somedir new.pkg

You can now run new.pkg without checks.

After installing, if it still doesn't work you might need to go into each installed kext in /Library/Extensions and modify Info.plist and change NVDARequiredOS to your build version.

Thanks doing that!

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
(@biasuz)
Active Member
Joined:11 months  ago
Posts: 11
October 25, 2017 11:19 pm  

 

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.

MBP mid-17 R560 + Aorus Gaming Box


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:1 year  ago
Posts: 225
October 25, 2017 11:23 pm  

Hey, I tried installed the package without the eGPU connected. Wrong, right? But it installed succesfully. I rebooted without the eGPU, logged in, connected the eGPU, it was recognized, signed out and it frooze there, on the loading, and nothing showing up on the external monitor...

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:1 year  ago
Posts: 225
October 25, 2017 11:25 pm  

Oh ok I keep getting this message now:  https://imgur.com/a/FTbrt . Again, I;m on beta version of MacOS 10.13.1, but I edited the Nvidia installer. Is there anything I can change to get rid of this message?

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:1 year  ago
Posts: 225
October 25, 2017 11:29 pm  

Looks like I missed the instructions bellow. I'm doing that now: 

After installing, if it still doesn’t work you might need to go into each installed kext in /Library/Extensions and modify Info.plist and change NVDARequiredOS to your build version.

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:1 year  ago
Posts: 225
October 25, 2017 11:32 pm  

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>

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
goalque
(@goalque)
Prominent Member Admin
Joined:1 year  ago
Posts: 882
October 25, 2017 11:32 pm  
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.

automate-eGPU.shapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
yifanlu
(@yifanlu)
Eminent Member
Joined:7 months  ago
Posts: 41
October 25, 2017 11:36 pm  
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.

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 + GTX1060@16Gbps-TB3 (HP OMEN Accelerator) + macOS10.13 & Win10


ReplyQuote
vn1minh
(@vn1minh)
New Member
Joined:7 months  ago
Posts: 3
October 25, 2017 11:41 pm  

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.

Edited: 7 months  ago

ReplyQuote
(@biasuz)
Active Member
Joined:11 months  ago
Posts: 11
October 25, 2017 11:45 pm  
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:1 year  ago
Posts: 225
October 25, 2017 11:45 pm  
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 🙁

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
yifanlu
(@yifanlu)
Eminent Member
Joined:7 months  ago
Posts: 41
October 25, 2017 11:49 pm  
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 + GTX1060@16Gbps-TB3 (HP OMEN Accelerator) + macOS10.13 & Win10


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:1 year  ago
Posts: 225
October 25, 2017 11:52 pm  

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.

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:1 year  ago
Posts: 225

ReplyQuote
goalque
(@goalque)
Prominent Member Admin
Joined:1 year  ago
Posts: 882
October 26, 2017 12:00 am  
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.shapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + Vega64@32Gbps-TB3 (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/RX580@32Gbps-TB3 (Netstor HL23T) + macOS10.13 & Win10


ReplyQuote
mac_editor
(@mac_editor)
Prominent Member Moderator
Joined:1 year  ago
Posts: 826
October 26, 2017 12:14 am  
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-wrangler.shpurge-nvda.sh

Guides:
Mid-2014 15" MacBook Pro GT750M + RX480@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter) + macOS & Win10
Mid-2014 15" MacBook Pro GT750M + GTX980Ti@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter) + macOS


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined:1 year  ago
Posts: 225
October 26, 2017 12:30 am  

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.

Edited: 7 months  ago

mid-2017 15" Macbook Pro RP555 + GTX1080i@32Gbps-TB3 (Mantiz Venus) + macOS & Win10


ReplyQuote
(@biasuz)
Active Member
Joined:11 months  ago
Posts: 11
October 26, 2017 12:46 am  
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
yifanlu
(@yifanlu)
Eminent Member
Joined:7 months  ago
Posts: 41
October 26, 2017 1:09 am  

Okay WTF of the week. My U28E590D 4K display has support for AMD FreeSync which I naturally have turned off. When I turned it on, it works (no more black screen). This defies all logic.

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 + GTX1060@16Gbps-TB3 (HP OMEN Accelerator) + macOS10.13 & Win10


ReplyQuote
ozzy
 ozzy
(@ozzy)
Trusted Member
Joined:1 year  ago
Posts: 54
October 26, 2017 1:15 am  

Has anyone been able to get this successfully working with a MacBook Pro model with an nVidia internal discrete GPU (e.g. the mid-2012 Retina models, 2013 or 2014 models with discrete GPU)? I looked through the thread and couldn't actually see if anyone had even tested it on one of those, let alone if it worked. I saw a couple 2014 models, but it wasn't specified if they had a discrete GPU or integrated only GPU. Given the discrete nVidia GPU models won't work with an AMD eGPU in High Sierra, I want to be safe if possible before upgrading my whole system to High Sierra 🙂

2012 15" Macbook Pro Retina GT650M + GTX1070@10Gbps-TB1 (AKiTiO Node via TB3->TB2 adapter) + macOS10.13 & Win10


ReplyQuote
Tico
 Tico
(@tico)
Active Member
Joined:1 year  ago
Posts: 13
October 26, 2017 2:02 am  

Yes my  mid 2014 rMBP with discreet m750 works with a GTX 680. The 680 is a orginal  Mac version so it has boot screens.

☀️θ∆ics🌎
MacBook Pro (Retina, 15-inch, Mid 2014),2.8 GHz Intel Core i7 16 GB VIDIA GeForce GT 750M 2048 MB, Intel Iris Pro 1536 MB
Sonnet BA 650w (upgraded), Sapphire RX VEGA 8gb
Mantiz Venus GTX680


ReplyQuote
tbl777
(@tbl777)
Trusted Member
Joined:8 months  ago
Posts: 74
October 26, 2017 2:17 am  
Posted by: ozzy

Has anyone been able to get this successfully working with a MacBook Pro model with an nVidia internal discrete GPU (e.g. the mid-2012 Retina models, 2013 or 2014 models with discrete GPU)? I looked through the thread and couldn't actually see if anyone had even tested it on one of those, let alone if it worked. I saw a couple 2014 models, but it wasn't specified if they had a discrete GPU or integrated only GPU. Given the discrete nVidia GPU models won't work with an AMD eGPU in High Sierra, I want to be safe if possible before upgrading my whole system to High Sierra 🙂

At current, I do not see any iGPU-based or NVIDIA-based macbook failed, whereas the newest macbook has several failures.

Did you not see the previous part of this post?

late-2013 15" MacBook Pro GT750M + RX580@16Gbps-TB2 (AKiTiO thunder 2) + macOS 10.13


ReplyQuote
ozzy
 ozzy
(@ozzy)
Trusted Member
Joined:1 year  ago
Posts: 54
October 26, 2017 2:43 am  
Posted by: tbl777
Posted by: ozzy

Has anyone been able to get this successfully working with a MacBook Pro model with an nVidia internal discrete GPU (e.g. the mid-2012 Retina models, 2013 or 2014 models with discrete GPU)? I looked through the thread and couldn't actually see if anyone had even tested it on one of those, let alone if it worked. I saw a couple 2014 models, but it wasn't specified if they had a discrete GPU or integrated only GPU. Given the discrete nVidia GPU models won't work with an AMD eGPU in High Sierra, I want to be safe if possible before upgrading my whole system to High Sierra 🙂

At current, I do not see any iGPU-based or NVIDIA-based macbook failed, whereas the newest macbook has several failures.

Did you not see the previous part of this post?

Yes, I’ve read through the whole thing. There are two potential machines in the successes that have an Nvidia discrete Gpu. A 2013 15” and a 2014 15”. Neither specifies though so they could both be integrated gpu only. I’m hoping for confirmation of one with an Nvidia discrete gpu

2012 15" Macbook Pro Retina GT650M + GTX1070@10Gbps-TB1 (AKiTiO Node via TB3->TB2 adapter) + macOS10.13 & Win10


ReplyQuote
tbl777
(@tbl777)
Trusted Member
Joined:8 months  ago
Posts: 74
October 26, 2017 3:07 am  
Posted by: ozzy
Posted by: tbl777
Posted by: ozzy

Has anyone been able to get this successfully working with a MacBook Pro model with an nVidia internal discrete GPU (e.g. the mid-2012 Retina models, 2013 or 2014 models with discrete GPU)? I looked through the thread and couldn't actually see if anyone had even tested it on one of those, let alone if it worked. I saw a couple 2014 models, but it wasn't specified if they had a discrete GPU or integrated only GPU. Given the discrete nVidia GPU models won't work with an AMD eGPU in High Sierra, I want to be safe if possible before upgrading my whole system to High Sierra 🙂

At current, I do not see any iGPU-based or NVIDIA-based macbook failed, whereas the newest macbook has several failures.

Did you not see the previous part of this post?

Yes, I’ve read through the whole thing. There are two potential machines in the successes that have an Nvidia discrete Gpu. A 2013 15” and a 2014 15”. Neither specifies though so they could both be integrated gpu only. I’m hoping for confirmation of one with an Nvidia discrete gpu

See my previous review, macbook pro retina 15 2013-late with gt750m.

late-2013 15" MacBook Pro GT750M + RX580@16Gbps-TB2 (AKiTiO thunder 2) + macOS 10.13


ReplyQuote
mac_editor
(@mac_editor)
Prominent Member Moderator
Joined:1 year  ago
Posts: 826
October 26, 2017 3:28 am  
Posted by: yifanlu

Okay WTF of the week. My U28E590D 4K display has support for AMD FreeSync which I naturally have turned off. When I turned it on, it works (no more black screen). This defies all logic.

What lol - haven't seen that happen...

purge-wrangler.shpurge-nvda.sh

Guides:
Mid-2014 15" MacBook Pro GT750M + RX480@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter) + macOS & Win10
Mid-2014 15" MacBook Pro GT750M + GTX980Ti@16Gbps-TB2 (AKiTiO Node via TB3->TB2 adapter) + macOS


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Honorable Member
Joined:1 year  ago
Posts: 647
October 26, 2017 7:13 am  

Gave it a go on my TV... but black screen...

 

Screen Shot 2017 10 26 at 07.59.46

edit: Didn't notice at first but both displays are being powered by the 1070! Makes me think the old "headless adapter" trick may work to get my internal and LG screen working? The GPU wasn't detected on the HDMI port only the Display port. Thoughts?

Edited: 7 months  ago

2017 13" MacBook Pro Touchbar + GTX1060@32Gbps-TB3 (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + GTX1070@32Gbps-TB3 (Sonnet Breakaway Box) + Win10
---
LG 5K Ultrafine flickering issue fix


ReplyQuote
TrDA
 TrDA
(@trda)
Active Member
Joined:11 months  ago
Posts: 16
October 26, 2017 7:31 am  
Posted by: Rycco

Hey guys, I'm 10.13.1 Beta (17B45a), I tried to install Nvidia drivers but it says it doesn't support this version. Is there anything I could do to install it? I wanna test on my Macbook Pro 2017 + Mantiz Venus + 1080ti.

I had the same problem.

I installed from the App Store -> High Sierra (standard method = downgrade OS), on top of betta 4 (10.13.1).

And it all worked.

early-2015 13″ MBA + Akito Thunder 2 + GTX1050ti + external display 1080p + macOS10.13.3 & Win10
late - 2011 17″ MBP + Akito Thunder 2 + GTX1050ti + external display 1080p + macOS10.13.3 & Win10


ReplyQuote
imcalledandy
(@imcalledandy)
Estimable Member
Joined:1 year  ago
Posts: 126
October 26, 2017 8:47 am  
Posted by: mbnwa

I had the same black screen issue I had to download SwitchResX and enable the helper application and change the external screen from "Billions of Colors" to "Million of Colors" issue went away, If I revert back to "Billions of Colors" black screen come back this is on an Acer X34

Anyone looking to change the bit depth of their display should try this:

Posted by: silvioalessi

Download this app  http://resxtreme.com

and set external monitor to 8 bits/sample in Menu/ File/ Apply Selected Mode

I followed this method to get FCPX working when the eGPU is connected.

2013 MacPro 2xD700 2xGTX980Ti@16Gbps-TB2 (AKiTiO Thunder2) + macOS 10.13.3
2017 TB MBP 2xGTX180Ti-TB3 (Akitio Node) + macOS 10.13.3


ReplyQuote
Page 5 / 54 Prev Next