euqlaog

The script doesn’t recognize 10.11 as previous OS X (maybe due to missing maintenance number). - Since you have a Nvidia dGPU MBP, never use v0.9.7. I suggest the following: 1) sudo ./automate-eGPU.sh -uninstall 2) uninstall Nvidia driver manager 3) Restart the Mac 4) Reset NVRAM https://support.apple.com/en-us/HT204063 (and disable SIP if it gets enabled) 5) curl -o ~/Desktop/automate-eGPU.sh https://raw.githubusercontent.com/goalque/automate-eGPU/7192c79bda052bff92428700b59b652b30e6ab4d/automate-eGPU.sh 6) cd ~/Desktop 7) chmod +x automate-eGPU.sh 8) sudo ./automate-eGPU.sh 9) Restart If still the same, it’s likely that a current web driver is not compatible with your dGPU/eGPU on OS X 10.11.1.

@errin: Are you aware of this bug? https://github.com/goalque/automate-eGPU/issues/8 Seems that you have already installed the correct driver. If you are using v0.9.7, uninstall it and install v0.9.6. The script should say: Driver [346.03.03f01] found from: http://us.download.nvidia.com/Mac/Quadro_Certified/346.03.03f01/WebDriver-346.03.03f01.pkg Do you want to download this driver (y/n)?

Would you provide some details? Your Mac model, script output?

OS X 10.11.1 is released, new web drivers are not available yet, but GTX 980 works after rerunning the script.

You did everything right and eGPU is detected. The only issue is that your monitor is not detected on OS X. Can you use both the internal and external screen extended on Windows? If you set the external as primary, launch the Valley benchmark windowed and move to 5K screen, is it still accelerated by the eGPU? Have you tried to hot-plug the eGPU? The -a mode is only persistent on OS X with the aid of the background process. If you once boot into Windows, it’s not anymore.

The question is, did you get better success rate than 60%? You can try also the following terminal command: sudo nvram tbt-options=\<00\> This is not persistent. You have to execute the command on OS X side before the next Windows boot.

Yes, confirmed here. Just remember to set the external screen as primary if you play games. Also in Windows.

Internal screen works, accelerated by M370X: http://forum.techinferno.com/implementation-guides-apple/10665-2015-15-mbp-r9_m370x-gtx660%4016gbps-akitio-thunder2-win10-8-1-%5Bdanielbrown941%5D.html

The concept of rendering means apps such as Octane and Indigo renderer. There are number of apps which can utilise offscreen OpenGL and computing power of OpenCL or CUDA. Adobe After Effects, Photoshop, Premiere, Final Cut Pro X etc. In this case, an external monitor is not necessary. But I don't know how well Adobe apps support external GPGPU on current release of El Capitan. CUDA drivers may not be always compatible. There was a thread about this. For OpenGL gaming, an external monitor is necessary. But that’s not the whole story. I can run some games and Valley benchmark purely on the internal retina screen accelerated by eGPU via TB port only, other display cables disconnected. The proof of concept is done, but far away from any practical for now.

Maybe you could try on OS X 10.11 if Metal is supported? http://forum.techinferno.com/apple-egpu-discussion/10289-script-automating-installation-egpu-os-x-inc-display-output-28.html#post147388 According to my testing, internal screen acceleration within application is possible without using an external monitor, but the problem is that OS X selects a GPU which outputs the main screen for the app. You can still use your eGPU for CUDA and OpenCL tasks, possibly Metal as well. Adobe apps are worth to try.

I wrote a piece of code which determines Metal support. No need for Xcode IDE yet, command line tools are enough Open Terminal and type “nano metaltest.swift” and copy paste the following code: import Metal var supportedDevices: [MTLDevice] = MTLCopyAllDevices() if (supportedDevices.count > 0) { for device in supportedDevices { var isSupported = device.supportsFeatureSet(MTLFeatureSet.OSX_GPUFamily1_v1) print("\(device.name), supported: \(isSupported)") } } else { print("No supported devices found") } Save the file and then, xcrun swiftc -o metaltest metaltest.swift ./metaltest Here’s my system output as an example: Optional("Intel Iris Pro Graphics"), supported: true Optional("NVIDIA GeForce GTX 980"), supported: true For R9 390 it gave a general name: Optional("AMD Metal"), supported: true This simply lists all the supported GPUs. Mac developer library is the best source of information.

Metal API renders smoothly through my 4K eGPU display, windowed and full screen. Reference GTX 980 and R9 390 tested. 17/10/15 14:51:41,900 MetalKitEssentials[431]: [DYMTLInitPlatform] platform initialization successful 17/10/15 14:51:41,969 MetalKitEssentials[431]: Metal GPU Frame Capture Enabled 17/10/15 14:51:41,969 MetalKitEssentials[431]: Metal API Validation Enabled The future is not about OpenGL, it’s about Metal. Mac may become finally a real gaming platform. All the Macs introduced since 2012 are supported as mentioned in WWDC 2015. Meaning that Metal works with the all GPU vendors - Intel, AMD and Nvidia on OS X El Capitan. Nvidia Maxwell architecture is only supported if Nvidia continues releasing compatible web drivers, not only for high performance apps, but also through Core Animation and Core Graphics.

4K or 5K iMacs are not confirmed to give external screen output. That’s huge amount of pixels for the eGPU to span. However, what you can still try: - sudo ./automate-eGPU.sh -a and reboot - turn on/off "Displays have separate spaces" under Mission Control - sudo ./automate-eGPU.sh -clpeak (if passes the test, the only issue is eGPU display) In order to overcome “ACPI BIOS ERROR” on Windows 10, boot into OS X, turn on script [-a] mode, select BOOTCAMP startup disk under system preferences, and reboot. When you repeat these steps, it should give approximately 9/10 successful boots into Windows.

That’s extremely low score. Quite the same have been reported here. However, I didn’t notice any UI lag with my reference GTX 980, the same 346.03.02f02 web driver. Might be possible that current driver is not Quartz compatible with the GTX 960 on OS X 10.11. Quartz layer is responsible for almost everything what you see on the screen. As said, Apple is making big changes under the hood for AMD core graphics. AMDMTLBronzeDriver.bundle includes new AMD codenames, for instance “Fiji XT” and “Fiji Unknown”. See under the system report, Graphics/Displays and press Command-R to refresh the view to see which GPU actually outputs the screen.

That's the problem. See issues at GitHub. Browse this thread back to find a link to v0.9.6.

What’s your Xbench Quartz Graphics Test score? I got ~229 for R9 390, ~224 for GTX 980, and ~84 for Iris Pro on OS X 10.11. My UI test score was pretty much the same (score 19). Tested with a single U28D590 display (3840x2160@60Hz).

First confirm that the script version is 0.9.6. ”Your system is eGPU enabled and Nvidia web driver is up to date" signifies that you have previously installed Nvidia web driver, which is the same as the script is about to download. Please don’t install web drivers manually, let the script do all the job. If message is taken from the reinstall attempt and you installed the driver by the script initially, you may have file permission issues or conflicting nvram settings. If -uninstall, Nvidia driver manager uninstall, NVRAM reset, and running the script again won’t help, the last thing you can try is reinstall of OS X. And the very last, erase + install.

I haven’t much investigated Metal at lower level, but Apple said very clearly about core graphics changes in Metal for Mac. Currently the script includes only OpenCL performance tool, but could be possible to make a tool for testing UI element rendering speed. Nvidia has done impressive job by providing those web drivers so quickly so we can expect improvements and compatibility with the 750M (which is currently beta). You can swap the card to AMD HD series - they are stable with AKiTiO, but R9s are not. NA211TB is a certain choice, but it is my understanding that R9 AMDs are stable with the Sonnet III-D and maybe other multi-slot enclosures as well. When I now recall a Sonnet SEL which was my first eGPU a long time ago, it was unstable with R9. So it might be something do with the single-slot PCIe link. No one knows the reason. The future TB3 eGPUs seems to come as mobile and desktop versions as demonstrated in videos by Intel, interesting to see how they work in OS X.

The -a mode is meant primarily for multi-slot enclosures, -m just switches back to original manual mode. The v0.9.7 is not compatible with 750M equipped MBP, but I guess you’re using v0.9.6 since Unigine benchmark works. UI sluggishness that you observed, may be due to missing Quartz Extreme acceleration. The core OS X windowing system (Core Animation & Core Graphics) - if not yet fully implemented - will be built natively on top of Metal on OS X 10.11, resulting in up to 50% faster rendering performance as mentioned in WWDC 2015. This technology is not just for game developers, it’s for all kind of OS X apps in the future. For instance, Adobe has already demonstrated After Effects and Illustrator on Metal. Amazing improvements. It’s now clear that Apple has chosen AMD as their partner. Earlier this year I saw at Khronos.org that AMD’s core software team looked for software engineers for both kernel level and OpenCL development on OS X. We don’t know how well Nvidia can support Metal on OS X if Quartz Extreme, which uses OpenGL, is going to be replaced with thin Metal layer. But I’ll continue supporting both the AMD and Nvidia the best I can, and as long as I find time. Thus far, only AMD TB3 eGPUs have been demoed on Windows platform, not officially a single word about OS X or Nvidia eGPUs from Intel.

@level5wizard: Here's the post from the previous page: http://forum.techinferno.com/apple-egpu-discussion/10289-script-automating-installation-egpu-os-x-inc-display-output-25.html#post146186 After SIP (System Integrity Protection) is disabled, installation process should go well.

The script output could be clearer. See the previous page of this thread. Your setup is almost identical to Misha's so you may have the same monitor problem.

Restoring data from a Time Machine backup would be beneficial if -uninstall didn’t help. Please use v0.9.6 since you have an Nvidia dGPU: http://forum.techinferno.com/mac-os-x-discussion/10289-script-automating-installation-egpu-os-x-inc-display-output-24.html#post145834

@Misha: I sent you PM, let me know if you can send the registry of your system. Currently the script doesn’t support HDMI/DP audio through eGPU.

That’s normal. El Capitan has SIP enabled by default. Please do as the script says: “Boot into recovery partition and type: csrutil disable”.

Seems like you hot plugged the LG TV display. The app will launch from the screen that is set as the primary, so drag the menu bar to eGPU display, disable FileVault and try again.