euqlaog

@w4vz Don’t worry, the script will find the matching driver if Nvidia wants so. Usually within a day or two. There will be an alternative.

Nice to hear about your success with the RX 480. The recent macOS builds brought Metal support for Polaris, patching the white areas in Safari. You did nothing wrong. My previous posts answer these questions.

Well, the power up process is not very convenient: https://www.techinferno.com/index.php?/forums/topic/10143-2015-13-macbook-pro-gtx1070fe16gbps-tb2-akitio-thunder2-win10-creativie/ https://www.techinferno.com/index.php?/forums/topic/8212-2015-13-macbook-pro-gtx97016gbps-tb2akitio-thunder2-win81osx1010-tranj10/ https://www.techinferno.com/index.php?/forums/topic/10081-early-2015-13-macbook-pro-gtx107016gbps-tb2-akitio-thunder2-win1081-3d-printed-enclosure-nasiryahm/ I would consider HD 7970, Sapphire Nitro+ RX 480, or R9 Nano if the R9 280X did not show any sign of these boot issues. At least R9 Nano and HD 7970 should stay stable with the Akitio on Windows 10.

Yes, you have to replace your GPU with the Thunder2. Maxwell 9xx series cards are reliable choice. I can’t recommend any, please browse through the implementation section: https://www.techinferno.com/index.php?/forums/forum/113-implementation-guides-apple/ EDIT: Just noticed that your MBP is equipped with the Intel Iris 6100, it’s an early 2015 13” model which is problematic in the early boot stage with Maxwell series cards.

NA211TB doesn’t have these issues. The only difference between R9 280X and HD 7970 is the chipset. Tahiti XTL core has better power efficiency but it is prone to signal loss between power states, and Thunder2 can’t cope with it. OS X/macOS will crash eventually as well. I don’t know if this can be fixed by a new vBIOS. Your TB2 card narrows the link to PCIe 2.0 x4.

One of the cards that leads to a system crash. Get a HD 7970, that stays stable.

Yes, this did not come as a surprise. I was aware from the beginning that someone could potentially use the v0.9.8 for commercial purposes (and still can), but never thought that one could take the MIT license literally and make an unreasonable profit. The script automates the process that you can do by hand. Everyone who modifies Apple’s copyrighted kext files, should be aware of Apple Software License Agreement: http://images.apple.com/legal/sla/docs/macOS1012.pdf The existence of hackintosh communities indicates that personal hackintoshing is ok, but if someone is profiting money from a breach of the SLA, we know what happens. Publicly given quick fix (issue #31) from me is not a complete fix for macOS Sierra, it’s not version specific and never ended up to the source code of automate-eGPU.sh v0.9.8. At that time, the change was possible, but since the fix applies to v0.9.9 in the source level, you cannot merge the v0.9.8 and the proposed fix in issue #31 due to the license condition [2] of v0.9.9 at present.

I received Bizon’s “iMac 5K” version from @Dae. Thank you. Bizon uses automate-eGPU.sh v0.9.8 as the basis and it is completely invisible to the user because of the “hidden” flag. They referred it as "a special version of the activation script provided upon request to users of iMac 5K”, and it contains the same line 62 “quick fix”. Furthermore, lines 516, 725 and 754 were modified in order to support macOS Sierra which is clearly prohibited: 2. Backward modification or merging with earlier versions is prohibited, including changes to support macOS Sierra as described in issue #31. https://github.com/goalque/automate-eGPU/blob/master/SCRIPT-LICENSE.txt

@Dae Thanks for the blog post. I would be interested what kind of script did they provide? You're referring to a workaround by Netkas? His post is written on Feb 25th, 2016. After my ”quick fix” solution proposed here: https://www.techinferno.com/index.php?/forums/topic/7989-discontinued-automating-the-installation-of-egpu-on-os-x-inc-display-output/&do=findComment&comment=138038 Does the ”different version of the script” support macOS Sierra? I found a new web site which says ”macOS Sierra 10.12 or later”: https://support.bizon-tech.com/hc/en-us/articles/210708989-What-operating-systems-support-the-BizonBOX-What-are-the-minimum-operating-system-requirements- It’s against the new license of automate-eGPU.sh. By the way, according to google translation, Bizon claims to have found a way around Apple’s SLA regarding their Hackintosh business: http://bizon-pc.com/ru/faq/#faq30 They push the responsibility to the end user.

Everyone can translate the last 20 pages of his nonsense: http://www.macuser.de/threads/macpro-nmp-mit-externer-gpu.716921/ There is no any war, Bizon has kindly removed the link to my GitHub repository due to the new license. I am not concerned if someone misuses my script. @Uhlhorn does not seem to understand the sanctions in the hardware/software industry if a company does not follow the license terms of the big players. If he prefers shady business model, I wish him good luck.

You've already answers to your questions on german forum. As a software engineer I am very strict about licensing. I don't want to be in any association with a company who violates Intel's certification requirements. I have a full time job, EFI project on my free time, and other more important things in my life. No time to give endless support.

Bizon has chosen a shady, terribly risky way of making money by selling products that violate Intel’s certification requirements. Furthermore, the script modifies Apple’s kext files. AFAIK, it’s illegal to sell hacks. Soon after the release of my script, small startup companies started popping out. Bizon, Bullbox, Wolfe. Only the Bizon has somewhat survived. They took the MIT license literally, forgot the rules of Thunderbolt technology and Apple’s SLA. The new license is the last nail in the coffin. I see some light in the tunnel of EFI approach.

In that case, no problem. @dan273 is running 10.12.

Your Mac operating system version.

Looks good. They are not allowed to distribute my script for macOS Sierra. I’m curious, what’s your system version?

I appreciate your help. I like the idea of “open eGPU for all”, but I have realized that a fully working eGPU system is dependent on all components: firmware, OS version, backplane, graphics card and its driver. With the help of my friends, I have a much better chance to provide a solution that fulfills Apple’s SLA and Intel’s rules. I can’t promise any timetable. Nope. The most observant readers know who my friends are.

@anarki Sorry, no more unlocks. One user said thanks, and have not logged in since then. The test was to be conducted a month ago. @Manuel Noriega No. https://www.techinferno.com/index.php?/forums/topic/10057-automate-egpu-efi-mac-bootscreen-on-egpu/&do=findComment&comment=144965 @LukeHero Normal. The demo doesn’t automate anything in user space. It only demonstrates boot screen switching. This project is proprietary with a company that is specialized in TB2 and TB3 expansion products certified by Intel.

Technically, the MIT license made it possible, but I never wanted that the script would end up into a shady business area. They don't support macOS Sierra currently, and hopefully not in the future: https://bizon-tech.com/us/faq-egpu/#egpu10 I can't change the license of forked versions up to v0.9.8 which are under the MIT. If someone sees that bizon-tech uses macOS Sierra, please report.

You may be right if we are precise. I didn’t thought your use case, everything is linked together Well, now it’s clear

“For commercial purposes” means, for example, selling or advertising the script itself, its abilities and functions in OS X, or using the script with some product/software to make profit. That is prohibited. Your personal renderings are not direct outputs from the script. There is a rendering software in between which allows commercial use, I suppose. However, the condition [1] says “for personal use”, so as long as your renderings are not done in a corporate environment, you can still use the script for your daily work.

The script just had its funeral. The EFI app will replace it. I’m confident that Nvidia continues releasing web drivers. Boxes are boxes, they don’t automate anything. Drivers and apps do.

@MartyF81 It’s up to Nvidia. Sierra GM says: Searching for matching driver... No web driver yet available for build [16A319]. v0.9.9 remains the last one, let’s hope for an extended life cycle. If it doesn’t work, I don’t have time to provide support. Unfortunately. It has been a great adventure with you all! I am not in a hurry with the EFI app.

automate-eGPU.sh is discontinued. I found new opportunities from the EFI side. Versions up to 0.9.8 can still be modified under the MIT license as long as taking into account the new license condition of v0.9.9 [2]: Backward modification or merging with earlier versions is prohibited, including changes to support macOS Sierra as described in issue #31. The v0.9.9 cannot be developed further unless I change the conditions. Copying for personal use is only allowed. If you make changes to v0.9.9, you cannot distribute it on the web. Why such a restrictive license? Because people blindly buy the amazing BizonBox and they don’t have a clue that the box includes my script: https://www.techinferno.com/index.php?/forums/topic/6224-diy-egpu-macbook-experiences/&do=findComment&comment=125354 Without my script, it’s just a brick. I’m optimistic that a group of Harvard students have chosen the right way. However, I’ve a feeling that a part of the inner mechanism is derived from my work. There is one interesting detail in their “internal screen” demo: the eGPU doesn’t show any displays under the Graphics/Displays, or did they forget to press Command+R? Also “Metal: supported” is not in the list. Some readers might remember my posts how to run Valley benchmark and play some games on the retina screen in OS X, accelerated by the eGPU, only the TB cable plugged in. I really hope that their method is a kernel extension.

I don't know, boot into OS X, turn on the -a mode, change the default startup disk to Boot Camp, restart and try. And then repeat the steps. The -a mode is not persistent on Windows.

This may improve stability: https://www.techinferno.com/index.php?/forums/topic/5661-us189-akitio-thunder2-pcie-box-16gbps-tb2/&page=39#comment-109360