Recap
macOS External GPU has been possible for several years thanks to the selfless work of many in our eGPU community. Most notable is the automate-eGPU script Goalque wrote that enables eGPU in 10.9 to 10.12. Today Apple officially adds this highly-anticipated capability in macOS High Sierra 10.13.4 [17E199]. It’s now available to the general public but not without limitations. As released, only Thunderbolt 3 Macs can make use of external GPU with select AMD Radeon graphics cards.
The questions that immediately come to mind for many Mac users are whether there’s a workaround for non-supported systems, Thunderbolt 1/2 and Nvidia graphics cards. There are no easy answers, but the ball is now in Apple’s court. eGPU.io’s tremendous growth was due in part to a strong Mac user base looking for external graphics card solutions. Now that Apple has officially incorporated eGPU into their Mac platform, it’s high time for the folks in Cupertino to provide first-party support.
macOS External GPU: AORUS Gaming Box + Apple MacBook laptops
The Journey
My first attempt with external graphics was a few summers ago when I realized the Mac Pro tower’s form factor would not return in the Mac lineup. The next logical upgrade path was through an external enclosure with PCIe slot. The Mac Pro trashcan planted this seed with its six Thunderbolt 2 ports that Apple engineers cleverly attached directly to the Xeon CPU [system block diagram]. So I hopped on that train and built an eGPU out of an AKiTiO Thunder2 enclosure. The setup process wasn’t for the faint of heart. Thanks to the resources already made available on TechInferno forums moderated by Nando, I was able to piece together a Radeon RX 470 eGPU for my Macs. The software that enabled this upgrade was Goalque’s automate-eGPU script.
 |
 |
Shortly after joining and learning about eGPU in macOS on TechInferno forums, Nando, Goalque, and I were banned due to conflicts of interest with the site owners. This turned out to be a blessing in disguise. It gave us a fresh start to build a new forum, fully dedicated to external graphics card solutions. eGPU.io is now the new and hopefully permanent home for eGPU enthusiasts. Our main mission has always been to make external GPU easy and accessible to all. Intel, AMD, and Thunderbolt partners share the same vision. The complete picture came together on June 5th, 2017 when Apple announced macOS external GPU support in High Sierra at WWDC.
Frequent visits from Cupertino – Dec 25th, 2016 to May 31st, 2017
High Sierra beta was available shortly after the announcement. I tested with the Sonnet Breakaway Box + RX 580 eGPU that is the very same setup Apple used for its eGPU Development Kit. While it worked, this early build was limited to the AMD Radeon RX 580 only and hot-plugging was buggy. Goalque’s script worked more reliably in 10.12 at that point in time. macOS 10.13 was released fall 2017 with external graphics card support for developers only. We kept ourselves in the loop throughout macOS external GPU development process from 10.13 to 10.13.3. While there was marginal improvement following each update and additional support for Radeon Vega GPUs, no major change was in sight.
 |
 |
Then came 10.13.4 Beta 1, version 17E139j, and with it an initial glimpse of the public release of macOS external GPU. Beta 1 was an amazing build that refined the user experience significantly over previous versions. External GPU was now plug-and-play with almost all Thunderbolt Macs. We were beyond excited and anxious for the final release day. This excitement was short-lived. Beta 2 wreaked havoc on the hierarchy of trust. It broke compatibility with Thunderbolt 1 and Thunderbolt 2 Macs. Longtime Mac users, myself included, felt a punch to the gut when subsequent 10.13.4 Beta continued this trend, refusing to work with non-Thunderbolt 3 Macs. If you’ve been enjoying external graphics with your older Macs, stay with 10.13.3 until further notice.
Reality eventually set in; Apple is a control freak, and for them to add a software feature to support third-party hardware is unprecedented. As seen below, there are about a dozen of Thunderbolt 3 eGPU enclosures compatible with macOS. It’s likely only a handful will be macOS-certified. In the whole scheme there’s a deadline to meet and the fewer Macs to focus on, the more quality assurance Apple can provide to ensure a successful launch. I remain hopeful macOS external GPU functionality will be extended to older Thunderbolt Mac systems in due time.
April 7th 2018 Update: mac_editor found a workaround to enable external GPU functionality for TB1/2 Mac on 10.13.4.
| Compatible Enclosures macOS External GPU |
AKiTiO HOT Node |
Sonnet Breakaway 350 | 550 | 650 | 350D |
OWC Mercury |
HP Omen Accelerator | PowerColor Devil Box |
Asus XG Station Pronew |
AKiTiO Node Pro |
Mantiz Venus |
Asus ROG XG Station 2 |
Razer Core V2 |
Sonnet Breakaway Puck |
Aorus HOT Gaming Box |
| Appearance |  |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
| Included GPU1 | ✖ | ✖ | ✖ | ✖ |RX580 |
✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | RX570 | RX580 |
| Price US$ |
$260 |
$249 | $349 | $449 | $699 |
$319 | $300 |
$300 |
$330 | US$360 | $399 |
$550 |
$500 | $599 |
preview |
| Max PCIe bandwidth | 32Gbps | 32Gbps | 32Gbps | 32Gbps | 32Gbps | 32Gbps | 32Gbps | 32Gbps | 32Gbps | 32Gbps | 32Gbps | 32Gbps |
| PSU type-location2 |
SFX-int | SFX-int | SFX-int | ATX-int | fATX-int | AC-ext | SFX-int | SFX-int | fATX-int | fATX-int | AC-ext | fATX-int |
| PSU max power | 400W | 350W | 550W | 650W | 350W |
550W | 500W | 500W | 330W | 500W | 550W | 680W | 500W | 220W | 450W |
| GPU max power3 |
375W | 300W | 375W | 475W | 225W |
375W | 300W | 375W | 300W | 400W | 375W | 500W | 375W | – | 225W |
| Power delivery (PD)4 |
15W | 15W | 87W | 87W | 60W | 87W | 60W | 60W | 15W | 60W x2 | 87W | 100W | 65W | 45W | 100W |
| USB-C controller |
TI83 | TI83 | TI83 | TI83 | TI83 | TI83 | TI83 | TI83 | TI83 | TI83 | TI83 | TI83 |
| TB3 USB-C ports | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 |
| Ports max bandwidth5 | – | – | – | 5Gbps | 5Gbps | 10Gbps | 10Gbps | 5Gbps | 5Gbps | 5Gbps | – | 5Gbps |
| USB3.0 ports (+C type)5 |
✖ | ✖ | ✖ | 4+1 | 4+1 | 0 |
✖ | 5 | 4 | 4 | ✖ | 3 |
| Ethernet port5 | ✖ | ✖ | ✖ | ✔ | ✔ | ✖ | ✖ | ✔ | ✔ | ✔ | ✖ | ✖ |
| SATA port5 | ✖ | ✖ | ✖ | ✔ | ✔ | ✖ | ✖ | ✔ | ✖ | ✖ | ✖ | ✖ |
| Other ports | ✖ | ✖ | ✖ | ✖ | ✖ | USB-C 3.1 |
DP | ✖ | USB-B 3.0 | ✖ | ✖ | QC |
| Included GPU ports | ✖ | 2xDP,HDMI,DVI-D | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | ✖ | 3xDP,HDMI |
AMD: 3xDP,HDMI |
| Size (litres) [ visual ] |
14.09 |
12.71 |
12.71 | 16.00 | 16.65 | 8.23 | 12.82 | 11.56 | 20.03 | 7.65 | 5.07 | 3.30 |
| Max GPU len (in/cm) |
12.60 / 32.0 | 12.20/31.0 | 12.20/31.0 | 11.42/29.0 | 12.20 / 31.0 | 12.24/31.1 |
12.60 / 32.0 | 13.00 / 33.0 |
12.20 / 31.0 | 11.81/30.0 | – | 6.65 / 16.9 |
| Weight (kg/lb) | 4.90/10.78 | 3.20/7.10 | 3.20/7.10 | 5.50/12.10 | 3.60/7.92 | 2.95 /6.50 |
3.40/7.40 | 3.60/7.92 |
5.10/11.22 | 4.95/10.89 | 2.38/5.25 | 2.35/5.19 |
| Updated firmware6 | 25.1✔ | 25.2 | 25.2 | 25.2 | 25.1 ✔ | ?? | 25.25✔ | 25.101✔ | ✔ | ✔ | 25.1✔ | v25 ✔ | 26.1 ✔ | 25.1 ✔ | ✔ |
| TB3 cable length (cm)7 | 50 | 50 | 50 | 50 | 50 | 150 | 50 | 50 | 50 | 50 | 50 | 50 |
| Vendor page | link | link | link | link | link | link | link | link | link | link | link | link |
| Review | link | link | preview | link | user | preview | link | link | link | link | link | preview |
| User builds |
link | link | ✖ | link | link | link | link | link | link | link | link | ✖ |
The Good
The most obvious and welcome change is true hot-plug capability for macOS external GPU. In High Sierra 10.13 to 10.13.3, hot-plugging was partial in that the system would ask you to log out then log back in to initialize the eGPU. In 10.13.4, this is no longer the case. Provided you have compatible hardware, you’ll see a brand new icon in the Top Menu bar for external graphics status. For now this icon’s sole purpose is to disconnect the external graphics card safely. 10.13.4 also shows the correct identification of supported Radeon GPUs. In previous builds these cards would show up as “R9 XXX”. I foresee future enhancements to include a dedicated panel in System Preferences so that users can manually select which graphics card is engaged depending on workload and energy settings.
 |
 |
Clamshell mode is another highlight. This had been working intermittently depending on the build. Through six beta builds of 10.13.4, clamshell mode worked flawlessly on my late 2016 15″ MacBook Pro and mid 2017 13″ MacBook Pro. Sleep behavior was an improvement over previous versions too. Putting the computer to sleep while the eGPU is connected also puts the eGPU to sleep. External GPU functionality resumes working when the computer is woken up. Sleep issues may have been the deciding factor to axe Thunderbolt 1 & 2 Mac support. Using an eGPU with my Mac Pro trashcan had often caused unpredictable sleep and wake-up behaviors.
The Bad
In the current state macOS external GPU cannot provide loop-back acceleration to the internal display. This effects gaming use because the external graphics card is rendered useless without an external monitor. Professional applications that rely on OpenCL fare better because they can use all graphics cards presented in the system. In contrast AMD XConnect (Windows only) provides eGPU internal display acceleration. On the latest Adrenalin drivers, the performance difference between internal display vs. external monitor was limited to single-digit percentages.
Revision: Apple support article #HT208544 assigns the responsibility of internal display eGPU-acceleration on third-party software developers: “Pro applications and 3D games that accelerate the built-in display of an iMac or MacBook Pro. (This capability must be enabled by the application’s developer.)”
Timing for this release is rather unfortunate. Prices for graphics cards in general and AMD in specific have been inflated due to cryptomining. If you don’t currently have a compatible eGPU setup, it’s certainly not a good time to buy in. The recently announced Gigabyte RX 580 Gaming Box is one of the few reasonable options. For reference, this table shows all Radeon GPUs with native external graphics support in macOS High Sierra.
| Natively Supported macOS External GPUs | ||
| Radeon Vega | Radeon Ellesmere | Radeon Baffin |
| Pro WX 9100 | Pro WX 7100 | Pro WX 5100 |
 |
 |
 |
| Vega Frontier Edition | RX 580 | Pro WX 4100 |
 |
 |
 |
| RX Vega 64 Liquid | RX 570 | RX 560 |
 |
 |
 |
| RX Vega 64 | RX 480 | RX 560D |
 |
 |
 |
| RX Vega 56 | RX 470 | RX 460 |
|
 |
 |
The Ugly
On the developer front, third-party software needs to catch up to macOS external GPU in 10.13.4. Even though it’s been nearly a year since the release of 10.13 beta, many software have yet to take advantage of an eGPU. Apple’s own software needs improvement too. Final Cut Pro X was working very well with eGPU up until version 10.3.4. The latest version 10.4 ironically refuses to use the external graphics card for export. Then there’s the clusterfuck of software relying on Nvidia graphics cards for CUDA framework. The current Nvidia eGPU workaround may or may not survive this and ongoing macOS updates.
Last but not least is gaming in Windows. While eGPU in Bootcamp mode is neither supported nor related to this 10.13.4 release, many Mac users have been looking forward to using Thunderbolt 3 MacBook Pros as part-time gaming laptops. I wish there was better news to report. For the time being, we must continue to follow an exhaustive procedure to make use of external GPU in Bootcamp. I tried both Nvidia and AMD eGPUs with all three variations of the TB3 MacBook Pros and lived to document it. The benchmark results below demonstrate the difference between Windows vs. macOS external GPU performance.
| 2016 15" MacBook Pro | 10.13.4 RX580 | W10 RX580 | 10.13.4 RXVega56 | W10 RXVega56 |
|---|---|---|---|---|
| Unigine Valley | 36.2 FPS | 47.5 FPS | 58.8 FPS | 70.2 FPS |
| Unigine Heaven | 29.5 FPS | 46.0 FPS | 53.5 FPS | 74.1 FPS |
| Tomb Raider 2013 | 48.7 FPS | 83.0 FPS | 84.4 FPS | 124.2 FPS |
| Shadow of Mordor | 12.2 FPS | 70.9 FPS | 45.8 FPS | 96.5 FPS |
| Hitman | 27.4 FPS | 67.8 FPS | 28.6 FPS | 66.3 FPS |
| Dirt Rally | 28.6 FPS | 51.6 FPS | 72.1 FPS | 92.8 FPS |
Mac Ecosystem
Upgrading a Mac used to mean shoving hardware components inside the computer. Apple’s Thunderbolt 3 I/O only strategy on its MacBook Pro lineup is shaping the new Mac ecosystem by attaching out-of-body components. My interpretation of this add-on paradigm is similar to that of DSLR cameras. You buy the body (Mac) to get started, then invest in the lens and flash (TB3 peripheral) to get the most of your setup. A high-quality lens can last a long time and pair well to many bodies. So can a Thunderbolt eGPU enclosure with compatible Macs. Apple is seemingly positioning itself to sell Macs only as a replaceable component of a more complete computer setup.
 |
 |
Besides eGPU, other Thunderbolt 3 peripherals are gradually coming to the market. The LG Ultrafine 5K display is no longer the only Thunderbolt 3 monitor. Mantiz designed its new Thunderbolt 3 dock Titan to specifically cater to the MacBook Pro with matching esthetics and anodized space grey finish. There were a handful of Thunderbolt 3 external high-speed storage drives announced at CES 2018. AKiTiO recently introduced Thunderbolt 3 10Gbps Ethernet adapter. Sonnet has also started selling a Thunderbolt 3 memory card reader. These are just to name a few.
What’s Next
Consumer adoption is a crucial factor in determining macOS external GPU success. Thunderbolt technology has been available in a Mac since 2011. After so many years, Thunderbolt 3 has its best shot yet with a wide range of applications, eGPU being front and center. What concerns me most is the gnawing suspicion that top-level decision makers still have doubts about the costs vs benefits of TB3 technology. Thunderbolt external graphics solutions are costly for home users, much more so for business owners. In most production environments, the rule of thumb is to never run the latest OS version. Let the tech inclined suffer through bugs for a year before the production people get the stable release.
Next comes hardware investment. Most agencies I know still haven’t upgraded the majority of their equipment to Thunderbolt 3 Macs. After being neglected for many years without a proper “pro” Mac, Apple’s recent efforts excite some but leave many skeptical. Had Apple re-enabled external graphics in Thunderbolt 2 Macs, more users would be exposed to the benefits of this feature and would be more inclined to transition to the new ecosystem. Now is the time for first-party support to step up. The success of external graphics as a platform within Thunderbolt rests on the shoulders of Intel, Apple and Thunderbolt partners.
See also
- [SCRIPT] Enable eGPU for TB1/2 Macs on macOS 10.13.4
- [KEXT] Enable eGPU for unsupported AMD graphics cards
- [APP] Nvidia eGPU support for macOS 10.13 to 10.13.3
- [GUIDE ] eGPU-accelerated Internal Display for macOS
Rate this Post
Share this Post
Related Articles
Posted by: theitsage In the current state macOS external GPU cannot provide loop-back acceleration to the internal display. Actually nothing prevents us from developing apps and games that can be accelerated on the internal display. Apple puts responsibility on developers. “Pro applications and 3D games that accelerate the built-in display of an iMac or MacBook Pro. (This capability must be enabled by the application’s developer.)” https://support.apple.com/en-us/HT208544 “If an external GPU needs to send data to the built-in display, that data must first be transferred from the external GPU to the built-in GPU that drives the built-in display.” https://developer.apple.com/documentation/metal/fundamental_components/about_multi_gpu_and_multi_display_setups/ I explained… Read more »
Goalque, Thanks for all of the work toy guys have done on this page as well as taking care of the Mac faithful with GPU work in general. I do have a question. Is the performance hit going to be as drastic for internal monitor acceleration as this sounds?
https://www.youtube.com/watch?v=8k_jnoEtLTM
I’m using mid 2014 MacBook Pro and really hope that Apple will return eGPU support for TB2 as well, including Bootcamp eGPU support. Ideally for both AMD and Nvidia graphic cards. Untill then I’m going to stay at 10.13.3.
Unfortunately it seems that the RX 560 and below aren’t supported as of now. They’re not listed on the official apple support page (https://support.apple.com/en-us/HT208544), and after brief testing with my RX 560 and 10.13.4 I got the same behavior that was reported here: https://egpu.io/forums/mac-setup/akitio-node-rx-560-10-13-4-beta-black-screen/
We’re being pushed to Windows for compatibility and higher frame rates. No complaints, really.
Cmon it is a start, 10.13.4 brings a lot of fresh air. Higher frame rates depends of many things.
Higher frame rates depends on hardware and software. Hardware is the same, the app software is the same, the OS software is not.
Guess what the problem is… 🙂
Is the “RX 580 Gaming Box” enclosure seen in the picture also supported?
@daniel_bolke The Gaming Box in picture is the AORUS 1080. When the Gigabyte RX 580 Gaming Box arrives, it should be compatible with Thunderbolt 3 Macs.
Saddening to see the frame rate results in that diagram between macOS and Windows, especially for Dirt Rally in macOS 10.13.4 compared to that of Windows – that game is the only one of the software in that diagram that I know is supposed to use Metal 2 for rendering, and despite that Windows gets about 20 more frames per second on both RX580 and RXVega56. While It’s understandable that Windows is ahead I think that difference is too big. Apple (and the developers?) still has a way to go untill macOS can be areasonable alternative to Windows for gaming.… Read more »
@star-affinity I agree the results are rather disheartening. Apple talked a big game but their actions have continuously been discouraging towards Mac users. When software developers and hardware vendors don’t see an enthused user base, they will not invest heavily in the platform. To be honest with you, judging by the progress of external GPU support in High Sierra, it seems Apple did not do much until about 3 months ago.
@itsage to add to your points above, there are far too many issues with High Sierra besides just eGPU support and Metal that really need fixes. At least the Metal API works. Apple messed up in 2017 – this year should be focused only on optimization (and High Sierra was supposed to one). This is one of the worst releases of macOS I have ever experienced (in general, not eGPU related). Sierra is significantly better in day to day use. I can go on and on about non-eGPU issues in High Sierra. And I’ve barely used it for work. Wish… Read more »
macOS 10.13.4 is eGPU dynamite – it breaks 82% of our documented macOS builds
Some interesting eGPU.io build statistics. There are:
– 47 are TB3 NVidia eGPUs (30%) which have a macOS 10.13.4 unblocked TB3 eGPU interface but require an updated NvidiaEGPUSupport package
@nando4 Thank you for compiling those statistics. 4 out of 5 existing Mac eGPU setups no longer work thanks to 10.13.4.
The future is a bit pale for many of us. At least Apple do have understood that eGPUs do have a place, which is very good.
I will probably bring my rMBP up to 10.13.4 but keep my 2012 mac mini on 13.3 for the mini egpu 1070 for as long as it lasts.
My plan for the long run is to get the 580-box and a possible TB3 mac mini if Apple don’t kill that line off.
I really hate having to buy me TB3 MBP only to slap it onto a desk for 99% of its life.
I am done with Apple Desktops With Apple killing off TB2 Macs for eGPU support my annoyance with their product strategy has grown so much I just can not stand it anymore. I invested a huge amount of my hard earned money in their ecosystem (Mac Pro 6,1 2013, rMBP Mid 2015) only to find out that the system’s architecture is limited by design. Graphics performance is the biggest limitation with both of my computers. While Apple have always been slamming kind of outdated processors in their computers, I was promised expandability when they released the unconventional “thrashcan” Mac Pro… Read more »
Unfortunately, Apple does have a history of planned obsolescence so I’m not surprised by their actions with regard to this. Shame, really
I’m holding on to my Late 2012 Mini because of the quad core CPU. If they would create a new generation quad core Mini with TB3 and SSD, I’d be handing over my money. But they won’t force me into buying a MBP that doesn’t really meet my needs (I use a computer on the desktop and an iPad for portablility). So until then I will stick with 10.13.3. And if becomes obsolete before there is a *suitable* TB3 Mac for my needs and budget, maybe someone will want to buy a Mantiz Venus and an RX 580 card. Forum… Read more »
ziggy, you are my hero. I love my Late 2012 Mini 2.6GHz i7-3270QM quad core with 16GB mem and 1.2TB fusion drive. It “processes” great, but it doesn’t “fly” well (X-plane flight sim). I had to work really hard to get the 10.13.4 upgrade installed for some reason and now on the 2018-0001 security patch version, but lusting over a Sonnet Breakaway with the RX580 card. I really love Mac OS X, and especially time-machine which I don’t need very often, but when I do it has always come through for me. I want more graphics now – not in… Read more »
This is not true, Macs are the longer supported platform in industry.
@Halbertus
I agree with some of this issue are Apple fault, but as an owner of a MacBook Pro 13” 2017 I love touch bar and I love the new keyboard. I owned so many computers in my life and this one is the best yet.
Longest supported platform ? What is your definition of “supported” ? My super expensive Mac Pro 2013 (I bought for video processing) was never updated and has been obsolete for several years now. I waited for 5 years for a GPU upgrade, even at Apple’s preposterous prices, to no avail. I have my Akitio node sitting under my desk because I was convinced that Apple would have repaired to their horrible lack of attention by enabling external GPU in OS X to compensate for the inexcusable lack of upgrades, and… surprise surprise… the Mac Pro 2013 is not supported !… Read more »
Maybe I should rephrase, but they certainly had no issues with gimping iPhones after a year with the whole battery scandal, and they killed FireWire without a well-supported replacement at first as well
Posted by: nombrescreeno Maybe I should rephrase, but they certainly had no issues with gimping iPhones after a year with the whole battery scandal, and they killed FireWire without a well-supported replacement at first as well This is true, and I was quite annoyed with my phone slowing down. But looking into the problem specifics – the battery explanation makes sense. I have experienced crashes in colder weather as such (I even reported this while on iOS 10) and their fix solved the problem at the cost of performance of course. I am satisfied with their explanation. Even old MacBooks… Read more »
I think my earlier post of a NON Thunderbolt eGPU solution is getting some attention now that Apple is killing off support for TB2 eGPUs. I built this a couple years ago when my cMP was my main machine. I have since built and switched to a Windows build for my main machine and moved this eGPU setup over to the new computer, which is one of the biggest benefits – there are zero drivers needed because it’s hardware-based. Both Mac and Windows systems see this external expansion at the hardware level before POST. At any rate, here’s my original… Read more »
Complaining about technology moving forward is a bit ridiculous.
@halbertus have you had no use out of your Mac Pro over the half decade you’ve had it (assume you bought it in 2013?) because unless its been sitting gathering dust waiting for the magical day when you can expand its capabilities with an external GPU it hasn’t really been a waste of money has it?
@Eightarmedpet: I also had a lot of use for many years for another system that was not upgradable: the Commodore 64.
But it was not named “Commodore Pro 64”.
A system that cannot be quickly upgraded to allow its Pro owner to compete by using the latest technology against other Pros, cannot have “Pro” in its label.
But Apple seems to think that we are willing to buy every iteration of their underwhelming hardware because it has a “Pro” in its name.
Apple is now a home-computer company. It is not enough to put a “Pro” sticker on a home computer.
For me, the writing was on the wall as soon as Apple released the “trash can” MacPro. In hindsight I was 100% correct that if you need to do high-end 3D work at a professional level, Apple no longer makes the “Pro” machine they claim they do. From the beginning and throughout the 90s and into the mid-2000s, Apple was the better choice for media professionals and artists. Meanwhile mostly because of lower prices and compatibility, Microsoft Windows was the choice for most general-purpose computers. Now in 2018 I feel like it’s flipped around. Today, macOS is the better choice… Read more »
I have been waiting 5 years for a GPU upgrade for my Mac Pro 2013, to no avail. Now Apple could have repaired this inexcusable lack of attention to Pro customers by allowing eGPU via TB2 in the latest OS X, but they decided that we do not deserve it. I kind of feel we do not deserve it because they want more money. My Mac Pro 2013 is sitting in the closet. I had “upgraded” it with a Mac Pro 2009 properly hacked to 12 cores and a modern NV GPU. So much better. Now it is time for… Read more »
Only if the battery is under 80% of life, this is chemistry not a scandal. Otherwise you can choose your iPhone to turn off while under heavy load… like and eGPU with insufficient PSU. off topic anyway
Posted by: ikir Posted by: nombrescreeno Maybe I should rephrase, but they certainly had no issues with gimping iPhones after a year with the whole battery scandal, and they killed FireWire without a well-supported replacement at first as well Only if the battery is under 80% of life, this is chemistry not a scandal. Otherwise you can choose your iPhone to turn off while under heavy load… like and eGPU with insufficient PSU. off topic anyway Chemistry, uh ? My iPad was perfectly working before that infamous iOS upgrade and I only use it for email and web. Never had… Read more »
Posted by: Dan Streaman Longest supported platform ? What is your definition of “supported” ? My super expensive Mac Pro 2013 (I bought for video processing) was never updated and has been obsolete for several years now. I waited for 5 years for a GPU upgrade, even at Apple’s preposterous prices, to no avail. I have my Akitio node sitting under my desk because I was convinced that Apple would have repaired to their horrible lack of attention by enabling external GPU in OS X to compensate for the inexcusable lack of upgrades, and… surprise surprise… the Mac Pro 2013… Read more »
Posted by: ikir Posted by: nombrescreeno Maybe I should rephrase, but they certainly had no issues with gimping iPhones after a year with the whole battery scandal, and they killed FireWire without a well-supported replacement at first as well Only if the battery is under 80% of life, this is chemistry not a scandal. Otherwise you can choose your iPhone to turn off while under heavy load… like and eGPU with insufficient PSU. off topic anyway Respectfully disagree. Other phones don’t do this And between things like FireWire, 3.5mm headphones, and TB1/2 now, Apple has never cared about ending widely… Read more »
Posted by: ikir Posted by: Dan Streaman Longest supported platform ? What is your definition of “supported” ? My super expensive Mac Pro 2013 (I bought for video processing) was never updated and has been obsolete for several years now. I waited for 5 years for a GPU upgrade, even at Apple’s preposterous prices, to no avail. I have my Akitio node sitting under my desk because I was convinced that Apple would have repaired to their horrible lack of attention by enabling external GPU in OS X to compensate for the inexcusable lack of upgrades, and… surprise surprise… the… Read more »
So, theoretically speaking.
For those with nMP’s, couldn’t you move the SSD to the TB2 and use m2 for the GPU?
J
Posted by: hoeveler I think my earlier post of a NON Thunderbolt eGPU solution is getting some attention now that Apple is killing off support for TB2 eGPUs. I built this a couple years ago when my cMP was my main machine. I have since built and switched to a Windows build for my main machine and moved this eGPU setup over to the new computer, which is one of the biggest benefits – there are zero drivers needed because it’s hardware-based. Both Mac and Windows systems see this external expansion at the hardware level before POST. At any rate,… Read more »
Posted by: nombrescreeno Posted by: ikir Posted by: nombrescreeno Maybe I should rephrase, but they certainly had no issues with gimping iPhones after a year with the whole battery scandal, and they killed FireWire without a well-supported replacement at first as well Only if the battery is under 80% of life, this is chemistry not a scandal. Otherwise you can choose your iPhone to turn off while under heavy load… like and eGPU with insufficient PSU. off topic anyway Respectfully disagree. Other phones don’t do this And between things like FireWire, 3.5mm headphones, and TB1/2 now, Apple has never cared… Read more »
Posted by: Dan Streaman Posted by: ikir Posted by: nombrescreeno Maybe I should rephrase, but they certainly had no issues with gimping iPhones after a year with the whole battery scandal, and they killed FireWire without a well-supported replacement at first as well Only if the battery is under 80% of life, this is chemistry not a scandal. Otherwise you can choose your iPhone to turn off while under heavy load… like and eGPU with insufficient PSU. off topic anyway Chemistry, uh ? My iPad was perfectly working before that infamous iOS upgrade and I only use it for email… Read more »
This isn’t too far off-topic as we are taking about Apple’s consistent pattern of doing their own thing at the expense of their users. This just came out 5 hours ago. Have fun sticking with macOS when developers have to develop for an entirely new family of processors, completely unique to Apple! https://www.theverge.com/circuitbreaker/2018/4/2/17189372/apple-intel-chip-processors-macs-date
Sorry, your problem with that is what, precisely? Apple makes plenty of mistakes, but this is just a company looking to securing its future: whilst the Intel architecture has the advantage of near-universality in desktop and laptop devices, it’s a triumph of development over design, with a massively complex legacy architecture that is now suffering quite badly from falling off Moore’s curve. ARM, otoh, is a largely ‘clean’ architectural model that is both highly extensible and readily integrated with other elements of a close-coupled hardware ecosystem. It is also a multi-source model where you’re not tied to a single supplier.… Read more »
Only for iPhones. Will check if they have news about iPads, but I guess we need a couple more class actions 🙂
Posted by: hoeveler This isn’t too far off-topic as we are taking about Apple’s consistent pattern of doing their own thing at the expense of their users. This just came out 5 hours ago. Have fun sticking with macOS when developers have to develop for an entirely new family of processors, completely unique to Apple! https://www.theverge.com/circuitbreaker/2018/4/2/17189372/apple-intel-chip-processors-macs-date If true, this is another dumb move into Apple inconsciously and eventually becoming a software-only company. Piss off developers and your “best” hardware and “best” OS will soon be useless. You will be soon developing your own “best” apps running only on your own “best”… Read more »
@dan_streaman Apple is filtering out the demanding customers and keeping only the “best” ones.
@Technomad Note that the desktop (in terms of workloads, not form factor) is also foreign land for ARM and requires development-over-design to flourish. ARM was born with simplicity and power-friendliness in mind. This works wonderfully in mobile/portable scenarios, but *today* does not address desktop-class workloads. ARM is just starting to truly get in on multi-core (even there, things like BIG.little were more efficiency than performance-oriented). Also – there were already a couple of attempts at going after desktop/server/datacenter loads with ARM (most notably NVidia’s Denver) which failed miserably, so we know elegance in design is not enough just yet. A… Read more »
is rx 460 support in 10.13.4 with tb1/2 script?
To use RX 460/560 as eGPU in 10.13.4, you’ll need goalque’s automate-eGPU.kext.