Thank you for the reply and the development work on the patcher. I will wait patiently for future releases with full automation. Have a great day.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.15 Catalina on Unsupported Macs
- Thread starter 0403979
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Thank you for the reply and the development work on the patcher. I will wait patiently for future releases with full automation. Have a great day.
That's because you card has a Kepler GPU which uses Apple's own Nvidia Drivers which enables Metal. And your ROM was swapped by MVC and he runs his own proprietary patches on it. So have the boot screen.
For anyone under a budget on a Mac Pro and wants just Metal to work but doesn't care about speed those tiny Signature EVGA 650 video cards will work. You just can't flash those, but you will get Metal and it will consume very little power. They are half length cards.
The most popular card for the Mac Pro is the GTX 680. And My favorite out of that group is the Galaxy 2GB card which runs 2x faster. It comes factory overclocked and flashes just like all the other GTX 680 cards but it keeps its overclock, but you can overclock any 680 card yourself, I just tend not to do it because for most stuff the Mac runs fine. And you can flash the GTX 680 yourself. There is a 2GB ROM that's standard from EVGA and a German 4GB ROM that was patched. It sometimes get complaints when using two DVI displays with it. So I tend to only use 2GB GTX 680s. There is really not a huge User Experience different because the 2GB and 4GB. The 4GB does run faster but for normal use it's not noticeable.
I run 3 displays on the Galaxy 680 and it works just as well as my Titan, just 1x slower but that is only noticeable when running speed tests or if you were to render video.
Another card I have is the Kepler Titan and this is a great card even when not flashed. It's my fastest card. 3x faster than an EVGA 680 card. It's currently running Windows 10 for Fortnite and it gets up to 100 FPS.
There are several other Kepler cards, but there is one Titan that you need to stay clear from and that is the Kepler Black. It doesn't work with Apple's Nvidia drivers. So avoid that one.
And last time I checked, Apple is not alllowing Nvidia to release any new Mac drivers for Mojave and Catalina which is a shame. Hopefully Apple never removes the Kepler drivers. If Nvidia wanted to, they could probably sue Apple for anti-trust violations by not allowing Nvidia to release the drivers. I know there is more to it with the tension between Apple and Nvidia, but Apple is giving AMD no competition under the most practical situations. Plus Nvidia is not making any money from used 680 video card sales.
Last edited:
Many thnx once again for the clear explanation.
Please forgive me. I was ill and was gone for a week. I did not read ahead. I'm going to refrain from commenting until I feel better. Thank you for letting me know, as I do not wish to rekindle old feelings, ever.
This solution makes the most sense to me but the question now is, doesn't the firmware always needs to be updated when a new MacOS version is released and installed on a MacPro5,1? So far from High Sierra and Mojave I had to have my non metal original native GFX card inserted so it will successfully install the new firmware, CD tray opens then closes and updates the firmware. Then I can shutdown and place the Metal GFX card in but obviously the screen will be black until it gets to the desktop and allow me to continue with the installation. With this method I understand you install Catalina onto a SSD or equivalent drive on a supported mac but once you boot this onto MacPro5,1 after you update the nvram what about the Logic Board firmware update how will that take place? I have no idea what this firmware update is all about each time is has to be done anyhow.
For "non-integrated LCD-display-mac" (MacPro and MacMini) as stated here at bottom: https://support.apple.com/en-us/HT207513
Ignoring the machines models (that are all whitelisted in my patched CoreBrightness), do you have exactly one of the 4 external displays indicated from apple ?
From your pictures seems no, because from your system report, I don't notice "LG UltraFine".
@thicla01 , for two simple reasons, apple "LG Display" for Night Shift supported:
1) Both the "apple LG" (4k and 5k) have different inches (rather than your LG 34" inch), example: https://support.apple.com/en-us/HT210105
2) Apple don't use typically as their displays standards the " ultrawidescreen 21:9 " aspect ratio, but 16:10 in past and from 2010 (and currently) 16:9 widescreen .
So I guess, your issue is not the Metal GPU or the patched CoreBrightness , but incompatible external Display with Night Shift.
1) Both the "apple LG" (4k and 5k) have different inches (rather than your LG 34" inch), example: https://support.apple.com/en-us/HT210105
2) Apple don't use typically as their displays standards the " ultrawidescreen 21:9 " aspect ratio, but 16:10 in past and from 2010 (and currently) 16:9 widescreen .
So I guess, your issue is not the Metal GPU or the patched CoreBrightness , but incompatible external Display with Night Shift.
Attachments
Last edited:
I am having a weird problem with my Catalina install. App Store apps simply will not install. Apps get stuck here and do not progress any further. Any ideas?
I don't think this is an accurate statement. Apple does not support NVIDIA, but certainly not preventing them from developing drivers. They did not revoke the certificates, otherwise, NVIDIA would not be able to develop updates for 10.13.6 because they would not be signed. Plus the old drivers would be revoked.
"Actually, the most recent macOS driver Nvidia released was a few weeks ago, January 24th. Here it is:
https://www.nvidia.com/download/driverResults.aspx/142147/
It's signed with Nvidia's developer certificate, meaning Apple has granted Nvidia's developer account the permission to sign kexts. Apple doesn't sign individual kexts/drivers, they simply enable the ability for a developer's certificate to sign kexts.
And just in case there is still any doubt, I actually checked how the kexts in that link were signed:
Code:
$ codesign -d -vv /Library/Extensions/NVDAResmanWeb.kext
Executable=/Library/Extensions/NVDAResmanWeb.kext/Contents/MacOS/NVDAResmanWeb
Identifier=com.nvidia.web.NVDAResmanWeb
Format=bundle with Mach-O thin (x86_64)
CodeDirectory v=20200 size=53564 flags=0x0(none) hashes=1668+3 location=embedded
Signature size=4746
Authority=Developer ID Application: NVIDIA Corporation (6KR3T733EC)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Signed Time=Jan 24, 2019 at 12:25:18 PM
Info.plist entries=14
TeamIdentifier=6KR3T733EC
Sealed Resources version=2 rules=13 files=0
Internal requirements count=1 size=188In other words, we can say with absolute certainty that no, Apple is not blocking anything. Cryptographic signatures aren't backed by human power. They are not backed by a higher power. They are backed by the highest power - mathematics. If God himself were to declare this signature to be invalid, then that wouldn't make it so - it would simply mean God was wrong.
Now, it is still possible that Apple might be withholding access to certain closed-source parts of macOS that NVIDIA needs to finish drivers for newer cards. That seems extremely unlikely, given that they aren't withholding anything for every macOS prior to 10.14, and that it would go against their own best interests as a company.
Regardless, even if that is the case, that is very different from 'blocking' a finished driver."
https://devtalk.nvidia.com/default/...rivers-be-released-for-macos-mojave-10-14-/56
Ahead of a modular Mac Pro, Apple said to ready a dedicated API for writing device drivers
Last edited:
Nvidia has stated it will not release its third party Mojave drivers unless Apple approves them which Apple has not. These are the ones from their website not was is approved to be on the OS itself.
To be extra clear: I am talking about Metal Third Party Nvidia drivers here. This includes Maxwell chipsets and above, not the Kepler only ones that Apple has included in its OS.
The only reason they are there any Nvidia drivers on Mojave is for the Mac Pro 5,1. This was when Apple said Mojave would be compatible with the 2012 Mac Pro. Apple only approved two of Nvidia's video cards for the Mac Pro 5,1 and Mojave which is the EVGA GTX 680 Mac Edition and one other card more expensive card by Nvidia.
Here is Forbes take on it:
https://www.forbes.com/sites/marcoc...rs-and-nvidia-with-macos-mojave/#976eb1637e9f
Mac Pro 5,1 and Mojave:
https://www.macrumors.com/2018/09/24/mojave-2010-2012-mac-pro-metal-graphics-cards/
The last time I checked, there are no official third party Nvidia drivers from Nvidia on Nvidia's website for Mojave that user's can download like they can for High Sierra and older.
This means without some hacking / patching you cannot use a newer Nvidia video card that would support Metal.
All of MacVidCards cards for Mojave are Kepler based. And users can use non-flashed Kepler cards except for the Titan Black. Or they can used flashed GTX 680 cards or one of the new Mac Edition cards from Nvidia that are also Kepler based.
And those drivers that you mentioned that were just released are for High Sierra not Mojave or Catalina.
Last edited:
I installed DP2 using DosDudes 1.0B4 to a 2011 MBP8,2. After installing the only thing I did was rerun the patcher tool and install the Video patch. Here are the screenshots and the requested kextstat outputs. 
All I am saying is that there is no proof apart from this statement that Apple is blocking NVIDIA. There is no other approval :
I am sure @pastrychef will confirm
.Hi @0403979 !
I have almost your hardware on my Macmini 2010 (Macmini 4,1, Core 2 duo Penryn P8600, NVIDIA 320M, 8 GB RAM) and I'd like to use your patch. Since it doesn't support APFS and I'm a newbie, could you explain me easily how to install it? I will provide an accurate feedback for all other users. Until now I Have used only @dosdude1 graphical interface (perfect on my obsolete macmini until macOS 10.4.5). Now I cannot patch installer using his preliminary tool (I get an error patching the official Catalina beta 2 installer on a usb 2.0 16 GB pendrive, probably due to APFS not natively supported) Thank you and congratulations to the whole RMC Team, @dosdude1 & @ASentientBot !
I have almost your hardware on my Macmini 2010 (Macmini 4,1, Core 2 duo Penryn P8600, NVIDIA 320M, 8 GB RAM) and I'd like to use your patch. Since it doesn't support APFS and I'm a newbie, could you explain me easily how to install it? I will provide an accurate feedback for all other users. Until now I Have used only @dosdude1 graphical interface (perfect on my obsolete macmini until macOS 10.4.5). Now I cannot patch installer using his preliminary tool (I get an error patching the official Catalina beta 2 installer on a usb 2.0 16 GB pendrive, probably due to APFS not natively supported) Thank you and congratulations to the whole RMC Team, @dosdude1 & @ASentientBot !
Last edited:
Dynamic switching does not work, checking the boot and rebooting has no effect. Similarly GFXStatus changing to integrated only has no effect. Brightness controls work via function keys. Facetime says no camera connected.
I have installed Catalina beta 2 in a iMac 8,1 with dosdude1 patcher, when trying to install it, in a external HDD usb, is impossible...someone has happened?
Thanks!
Thanks!
Ok, then @dosdude1 was right, there is no non-metal acceleration under AMD 6xxx, but for those dualGPU machine the acceleration is "shared" by the IntelHD3000, you can notice it because from "OpenGL Extension viewer.app" you don't have any panel related to AMD 6xxx GPU (where in HighSierra was present).
The picture with "whiter" Dock transparency indicates that AMD 6xxx is selected but its acceleration is clearly broken, so it's an hybrid acceleration gained from the IntelHD3000, and previously also the other user was able to run and use FCPX from Catalina thanks to the IntelHD3000 on a dualGPU machine.
I also achieved an hybrid broken acceleration during Mojave 10.14.5 beta: broken hybrid acceleration
But that's not a full non-metal-openGL video acceleration, just a broken one, instead after applied the @ASentientBot "CoreDisplay fix" the full acceleration was achieved.
So I guess AMD 5xxx and 6xxx series still need a true fix, not only swapping kext, but binary patching them.
But that's not a full non-metal-openGL video acceleration, just a broken one, instead after applied the @ASentientBot "CoreDisplay fix" the full acceleration was achieved.
So I guess AMD 5xxx and 6xxx series still need a true fix, not only swapping kext, but binary patching them.
Hi everybody
I follow "your achievements" with 10.15 from the beginning even though I have not yet had the time to install it to help you test.
At first we all were a little afraid that "the adventure" stops.
I wanted to once again say a big thank you to all those who make things happen from near and far @dosdude1 @ASentientBot @pkouame @jackluke @0403979... sorry for those I forgot
Now I'm going to be a bit off topic but I have a question:
Does the dynamic wallpaper work under 10.15?
I tried to put "Catalina.heic" in Mojave's Library/Desktop Pictures/?
After having realized it, it appears in System Preferences ▸ Desktop & Screensaver ▸ Desktop but with the preview of "Mojave.heic" and in spite of the dynamic mode selected the wallpaper stays on Catalina night whatever the time of the day (although Catalina.heic contains only 2 wallpapers unlike Mojave which contains 16... in dynamic mode it should change for a few hours of the day, isn't it?)
Is this a "Catalina.heic" file bug? the hours may not have been filled in for both wallpapers when creating the .heic file?
Yet when you switch from Dynamic mode to Light (still) or Dark (still) operation is consistent.
I follow "your achievements" with 10.15 from the beginning even though I have not yet had the time to install it to help you test.
At first we all were a little afraid that "the adventure" stops.
I wanted to once again say a big thank you to all those who make things happen from near and far @dosdude1 @ASentientBot @pkouame @jackluke @0403979... sorry for those I forgot
Now I'm going to be a bit off topic but I have a question:
Does the dynamic wallpaper work under 10.15?
I tried to put "Catalina.heic" in Mojave's Library/Desktop Pictures/?
After having realized it, it appears in System Preferences ▸ Desktop & Screensaver ▸ Desktop but with the preview of "Mojave.heic" and in spite of the dynamic mode selected the wallpaper stays on Catalina night whatever the time of the day
(although Catalina.heic contains only 2 wallpapers unlike Mojave which contains 16... in dynamic mode it should change for a few hours of the day, isn't it?)Is this a "Catalina.heic" file bug? the hours may not have been filled in for both wallpapers when creating the .heic file?
Yet when you switch from Dynamic mode to Light (still) or Dark (still) operation is consistent.
Last edited:
Most likely because it requires the legacy wifi patches used by Mojave Patcher. Currently the Catalina Patcher only patches to the stock Mojave wifi kexts.