Apple's management doesn't want Nvidia support in macOS, and that's a bad sign for the Mac...
Apple just doesn't allow modern Nvidia GPUs on macOS Mojave, and this is a dramatic change from only six months ago. Given that a new Mac Pro is coming that could support Nvidia cards, and there are already eGPUs that should, it's time that Apple did.
Nvidia Titan Xp for a PCI-E Mac Pro, supported through High Sierra
As with anything Apple, there's a long history between the two companies. And, some bad blood.
Rather than picking one manufacturer over another, however, Apple was actually choosing to work to the industry standard OpenGL. Doing so meant that it could freely switch between hardware from ATI, Nvidia or any other company that met those same standards.
So, it wasn't that Apple ditched ATI and in fact there was a 466 MHz model of the Power Mac G4 (Digital Audio) which had a 16MB ATI RAGE 128 Pro graphics card instead.
Still, with the exception of the iMac (Summer 2001) which had an ATI RAGE 128 Ultra, for the next two years, all Macs shipped with some Nvidia GPU. For 2003's Power Macintosh G4 (FireWire 800), Apple used an ATI Radeon 9000 Pro.
Nvidia processor in a 2008 MacBook Pro
Then in October 2008, Apple had to admit that some MacBook Pros had faulty Nvidia processors. Back in July of that year, Nvidia itself had admitted problems though when AppleInsider asked, the company refused to confirm that its chips were causing the MacBook problems.
By this point Nvidia was doing more than straight graphics processing. It was also providing a way for Apple to integrate and connect these GPUs to the rest of the MacBook.
Diagram showing the difference Nvidia brought to the MacBook in 2008
This substantially improved the graphics on the MacBooks -- and got Nvidia into a legal battle with Intel. A technology lawsuit from Intel claimed that Nvidia's license did not allow it to make such competing, compatible chipsets. The case and an overlapping countersuit wouldn't be resolved until 2011.
While that legal battle may have been an issue that affected whether Apple would be able to use Nvidia processors in future, in 2009 there was also a report that the Cupertino company had dropped them anyway. Reportedly, Nvidia was accused of proposals that were "arrogance and bluster" and that negotiations with Apple were now extremely bitter.
Around the same time, the iPhone transformed the mobile computing market and meant phones now needed GPUs. Nvidia had been rumored back in 2006 to be what would power Apple's forthcoming product but that was using the Tegra processor which then didn't ship until 2009.
Instead of Nvidia or AMD -- by then the owner of ATI -- Apple went for Samsung processors and of course later developed its own.
At this time, Nvidia may have then believed that its own patents also applied to the GPUs in mobiles. The company tried to get companies to buy licenses for this technology and in 2013 then went as far as filing patent infringement suits against Qualcomm and Samsung.
If Nvidia tried getting Apple to pay its license fees then Apple seemingly said no. In 2016, it also said no to putting Nvidia processors in the 15-inch MacBook Pro. Instead, Apple went with AMD GPUs publicly because of performance per watt issues, but the real reason is anybody's guess.
That performance to power ratio is most significant for the GPUs inside laptops and Nvidia continued to make graphics cards that could be used as eGPUs for Macs. If you had a Mac Pro before the 6,1 cylindrical one, you could use the company's PCI-E graphics card internally with the Nvidia-provided web driver. Thunderbolt devices could attach one with a little bit of a fight that didn't improve when Apple supported eGPUs explicitly in the spring of 2018.
Nvidia graphics card from 2017
In 2017, Nvidia didn't deliver drivers during the High Sierra beta, which seems sensible. Instead, it waited to release updated drivers for the shipping version.
And now, in 2019, there aren't any functional drivers for Mojave at all. And, it's Apple's fault. The only two Nvidia cards that work with Mojave are the GeForce GTX 680, and the Quadro K5000 -- both several years old at this point. And, this is only a light brush over the history between the two companies.
"It's not like we have any real work to do on it, Nvidia has great engineers," said one developer in a sentiment echoed by nearly all of the Apple staff we spoke with. "It's not like Metal 2 can't be moved to Nvidia with great performance. Somebody just doesn't want it there."
One developer went so far as to call it "quiet hostility" between long-time Apple managers and Nvidia.
For sure, somebody at Apple in the upper echelons doesn't want Nvidia support going forward right now. But, even off the record, nobody seemed to have any idea who it is. The impression we got is that it was some kind of passed-down knowledge with the origin of the policy lost to the mists of time, or an unwritten rule like so many in baseball.
Two years ago, pre-eGPU support, this block may have made at least a modicum of sense. Any Macs with PCI-E slots were aging, and the user base was dwindling through attrition alone. But, the drivers are available for High Sierra and are getting updated to this day -- and we can testify that they still work great in a 5,1 Mac Pro, including the 1000-series cards.
The Nvidia driver can be shoe-horned onto High Sierra machines who want a Nvidia card in an eGPU. We're not going to delve into it here, but there is a wealth of information over at eGPU.io, if you're so inclined. And, don't upgrade to Mojave if you do so.
This decision makes absolutely no sense with eGPUs now being explicitly supported in macOS. They work fine in Windows, so it's not a technical limitation. Some tasks perform better on AMD, and some on Nvidia, it is a fact of silicon. There is no reason beyond marketing and user-funneling to prohibit use of the cards on a software level.
No, there aren't a ton of eGPU installs. Yes, a good portion of those users are fine with AMD cards. But, it is absolutely overly user-hostile to not allow Nvidia to release the drivers not just for future eGPU use, but for the non-zero percent of those users who are keeping the old Mac Pro alive. And if this is some kind of ancient Apple secret or preserved grudges that are preventing it, that's even worse.
And, it makes us worry what "modular" means for the forthcoming Mac Pro.
Nvidia Titan Xp for a PCI-E Mac Pro, supported through High Sierra
As with anything Apple, there's a long history between the two companies. And, some bad blood.
First collaboration
The first Mac to include a graphics processing unit by Nvidia was the Power Macintosh G4 (Digital Audio), which was released in January 2001 and continued an Nvidia GeForce2 MX. Up to then, Apple had been using graphics cards made by ATI and this change was significant for more than just switching to Nvidia.Rather than picking one manufacturer over another, however, Apple was actually choosing to work to the industry standard OpenGL. Doing so meant that it could freely switch between hardware from ATI, Nvidia or any other company that met those same standards.
So, it wasn't that Apple ditched ATI and in fact there was a 466 MHz model of the Power Mac G4 (Digital Audio) which had a 16MB ATI RAGE 128 Pro graphics card instead.
Still, with the exception of the iMac (Summer 2001) which had an ATI RAGE 128 Ultra, for the next two years, all Macs shipped with some Nvidia GPU. For 2003's Power Macintosh G4 (FireWire 800), Apple used an ATI Radeon 9000 Pro.
Problems
In 2004, the Apple Cinema Display was delayed and reportedly because of Nvidia's inability to produce the required graphics card, a GeForce 6800 Ultra DDL.Nvidia processor in a 2008 MacBook Pro
Then in October 2008, Apple had to admit that some MacBook Pros had faulty Nvidia processors. Back in July of that year, Nvidia itself had admitted problems though when AppleInsider asked, the company refused to confirm that its chips were causing the MacBook problems.
By this point Nvidia was doing more than straight graphics processing. It was also providing a way for Apple to integrate and connect these GPUs to the rest of the MacBook.
Diagram showing the difference Nvidia brought to the MacBook in 2008
This substantially improved the graphics on the MacBooks -- and got Nvidia into a legal battle with Intel. A technology lawsuit from Intel claimed that Nvidia's license did not allow it to make such competing, compatible chipsets. The case and an overlapping countersuit wouldn't be resolved until 2011.
While that legal battle may have been an issue that affected whether Apple would be able to use Nvidia processors in future, in 2009 there was also a report that the Cupertino company had dropped them anyway. Reportedly, Nvidia was accused of proposals that were "arrogance and bluster" and that negotiations with Apple were now extremely bitter.
Around the same time, the iPhone transformed the mobile computing market and meant phones now needed GPUs. Nvidia had been rumored back in 2006 to be what would power Apple's forthcoming product but that was using the Tegra processor which then didn't ship until 2009.
Instead of Nvidia or AMD -- by then the owner of ATI -- Apple went for Samsung processors and of course later developed its own.
At this time, Nvidia may have then believed that its own patents also applied to the GPUs in mobiles. The company tried to get companies to buy licenses for this technology and in 2013 then went as far as filing patent infringement suits against Qualcomm and Samsung.
If Nvidia tried getting Apple to pay its license fees then Apple seemingly said no. In 2016, it also said no to putting Nvidia processors in the 15-inch MacBook Pro. Instead, Apple went with AMD GPUs publicly because of performance per watt issues, but the real reason is anybody's guess.
That performance to power ratio is most significant for the GPUs inside laptops and Nvidia continued to make graphics cards that could be used as eGPUs for Macs. If you had a Mac Pro before the 6,1 cylindrical one, you could use the company's PCI-E graphics card internally with the Nvidia-provided web driver. Thunderbolt devices could attach one with a little bit of a fight that didn't improve when Apple supported eGPUs explicitly in the spring of 2018.
Nvidia graphics card from 2017
In 2017, Nvidia didn't deliver drivers during the High Sierra beta, which seems sensible. Instead, it waited to release updated drivers for the shipping version.
And now, in 2019, there aren't any functional drivers for Mojave at all. And, it's Apple's fault. The only two Nvidia cards that work with Mojave are the GeForce GTX 680, and the Quadro K5000 -- both several years old at this point. And, this is only a light brush over the history between the two companies.
Nvidia cries foul
In October 2018, Nvidia issued as public a statement as it ever does. In a FAQ on Nvidia's developer site, the company said that Apple was to blame for the lack of web drivers for Mojave.We saw this note in October, and started asking questions. The "rendering regressions" and "slow performance" are because there is no real acceleration going on, and even performance in the "supported" cards is iffy at best -- and took a hit in Mojave.Developers using Macs with NVIDIA graphics cards are reporting that after upgrading from 10.13 to 10.14 (Mojave) they are experiencing rendering regressions and slow performance.
Apple fully controls drivers for Mac OS. Unfortunately, NVIDIA currently cannot release a driver unless it is approved by Apple.
Our hardware works on OS 10.13 which supports up to (and including) Pascal.
Inside Apple
What we found was support inside the Spaceship for the idea, but a lack of will to allow Nvidia GPUs. We've spoken with several dozen developers inside Apple, obviously not authorized to speak on behalf of the company, who feel that support for Nvidia's higher-end cards would be welcome, but disallowed quietly at higher levels of the company."It's not like we have any real work to do on it, Nvidia has great engineers," said one developer in a sentiment echoed by nearly all of the Apple staff we spoke with. "It's not like Metal 2 can't be moved to Nvidia with great performance. Somebody just doesn't want it there."
One developer went so far as to call it "quiet hostility" between long-time Apple managers and Nvidia.
For sure, somebody at Apple in the upper echelons doesn't want Nvidia support going forward right now. But, even off the record, nobody seemed to have any idea who it is. The impression we got is that it was some kind of passed-down knowledge with the origin of the policy lost to the mists of time, or an unwritten rule like so many in baseball.
Two years ago, pre-eGPU support, this block may have made at least a modicum of sense. Any Macs with PCI-E slots were aging, and the user base was dwindling through attrition alone. But, the drivers are available for High Sierra and are getting updated to this day -- and we can testify that they still work great in a 5,1 Mac Pro, including the 1000-series cards.
The Nvidia driver can be shoe-horned onto High Sierra machines who want a Nvidia card in an eGPU. We're not going to delve into it here, but there is a wealth of information over at eGPU.io, if you're so inclined. And, don't upgrade to Mojave if you do so.
This decision makes absolutely no sense with eGPUs now being explicitly supported in macOS. They work fine in Windows, so it's not a technical limitation. Some tasks perform better on AMD, and some on Nvidia, it is a fact of silicon. There is no reason beyond marketing and user-funneling to prohibit use of the cards on a software level.
No, there aren't a ton of eGPU installs. Yes, a good portion of those users are fine with AMD cards. But, it is absolutely overly user-hostile to not allow Nvidia to release the drivers not just for future eGPU use, but for the non-zero percent of those users who are keeping the old Mac Pro alive. And if this is some kind of ancient Apple secret or preserved grudges that are preventing it, that's even worse.
And, it makes us worry what "modular" means for the forthcoming Mac Pro.
Comments
After they report earnings on the 29th, they will have to have a clearer roadmap of what is going to happen this year in regards to products and services.
I always thought it was a mistake to only focus on iPhone since you don’t put all your eggs in one basket. The Mac market may not be as lucrative as iPhone, but I’m surprised they never had a contingency plan if the whole smartphone market plateaued.
Sure they talk about services making up the difference, but I read a good article showing that services won’t be as profitable as the lost sales of iPhones.
This is the first time I have seen a little panic in Apple’s behavior. They didn’t predict that the Xs and XR would not sell as well as they thought, and they surely didn’t predict that they would be replacing 11 million iPhone batteries in 2018. That was something that they should have factored correctly. They predicted only 1-2 million batteries would have been replaced.
So if there ever is a time that you have Apple’s attention, it’s now. Let Apple know that the Mac is still very much a viable market and they can make up for years of neglect if they work fast. I know there are a lot of people who have been waiting for a Mac good enough to upgrade to and taking care of them can boost the bottom line.
Paraphrased and could be mildly-inaccurate:
He worked for Disney, did a computer video of some kind, and got fired.
Started Pixar, (help from Steve), eventual raging success.
Disney approached to buy/control Pixar, with JL as the Pixar boss.
Instead of saying F-you, he agreed to be bought out, due to Disney's mega marketing/distro business.
I recall being impressed that he could set pride/revenge aside.
Good weekend all.
PS: Not saying I'm an angel in this regard, but the story came to mind.
Is the number smaller than iPhone user base? Absolutely.
Is the number smaller than the MacBook Pro user base? Absolutely.
IF Apple continues down this road and the MacPro7,1 is an immediate "failure" that is so locked up without PCIe port access, soldered memory or SSDs, and lack of ports and expansion (as many think may be the case), there will be a larger exodus from the Apple macOS platform.
MANY people stuck with Apple or moved to Apple during the Intel shift that allowed Boot Camp. These same users are now using Apple hardware and moving back to Windows because their work requires it. NVIDIA and CUDA is a large part of the video, 3D, animation, and scientific communities. These were target audiences for Apple at one point. Shifting these users to Windows is the wrong direction for Apple to be heading.
The Hackintosh community is a different story. Some of them did this out of necessity, others just don't want to pay the Apple tax. Apple could (and maybe should) do more to lock down their macOS software to prevent moving onto non-Apple originating hardware. The T2/T3/Tx chips seem to be part of that long term plan.
All this being said - there is absolutely no reason Apple should not straight up allow NVIDIA to release drivers on their own. Force NVIDIA to have a non-Apple support disclaimer during install if it's a support issue. Regardless, Apple at minimum owes the professional community an explanation or acknowledgment of the "issue" or to defend their position. Telling pros that the 7,1 will have PCIe slots (in some fashion) and support GPUs from AMD only would be an answer. Not the answer many want, but an answer that almost all potential 7,1 purchasers are looking for.
CUDA will never open to other GPU manufacturer, it is Nvidia's crown jewellery. Opening up CUDA is like the absolute last option Nvidia will do. And I don't see these CUDA workflow changes in the next 3 - 4 years. Intel will of course tries to compete, but I don't think they could come up with something that is as refined as CUDA in short space of time.
I mean, if I designed an app using a proprietary Microsoft SDK, I'm certainly not going to lobby Apple to support that SDK. Or conversely, if I design an app using Metal and then complain it doesn't work on Windows. These are the results of my software design choices.
One of the issues with the new mini – which will also be evident in a new Pro, is that because of the timespan between hardware updates combined with the fact that it can only run the very latest version of macOS makes the machine less flexible in that you cannot necessarily move workloads from old systems to the new hardware. This can be because the required drivers, libraries or software version does not support the most recent version of macOS.
A good example is macOS Server which is both stable and reasonably useful on Sierra, but is completely useless on Mojave, and force the user to run something completely different if they want to upgrade (most likely Linux).
You will experience the same for applications that needs certain versions of OpenGL possibly in combination with GPUs as another example.
Be sensible and methodical about what you say.
It does work. That is one of the many resources that got Apple to rethink abandoning the display market and retool the Mac Pro which is currently being re-created.
The Mac Pro presents an interesting dilemma for them because it creates conflicting goals for the company. On one hand they want it to be modular/configurable, but on the other hand they don't want to tie themselves down in supporting the multitude of 3rd party devices (many poorly designed) which people will configure it to use. Which is why they generally make it incumbent on 3rd party manufacturers to ensure their hardware is compatible.
I design my software to have an abstraction layer for rendering SDKs. Under which I can use OpenGL, Metal, Vulkan, or anything else. I don't whine about support.