This is a thread dedicated to what is needed to make Catalina work with the now unsupported MP5,1 + METAL supported GPU. If you want to discuss about why Apple removed support, please go to this thread
10.15 won't support MP5,1 anymore, support starts with MP6,1.
View attachment 840579
If you install Catalina with a supported Mac then move the drive to your MP5,1 (with a METAL supported GPU) or use Target Disk Mode, or
use VMWare Fusion to install to a disk you just need -no_compat_check added to the Mac Pro NVRAM boot-args, after that 10.15 "works" with a MP5,1.
It's a little slower than Mojave, not unusual for a beta with all the debug settings activated, and have some problems, but you really just need -no_compat_check when you install the Catalina Developer Preview with a supported Mac.
You need SIP disabled to change boot-args and you need to do it before installing your Catalina drive. No need to keep SIP disabled, it's just needed to set the boot-args. Btw, you can set NVRAM boot-args directly from the Recovery partition without disabling SIP. If you do it from Recovery, no need to use sudo.
Code:
sudo nvram boot-args="-no_compat_check"
Problems found so far:
- Apple removed the drivers for BCM94322MC from Catalina, the original AirPort Extreme card from both mid-2010/mid2012 Mac Pro. If you updated to BCM94360CD and BCM943602CD, both models work with Catalina. The original Bluetooth module works, Ethernet works.
View attachment 840582
- Apple NVIDIA native drivers are buggier than the usual, with black bars on the Safari tab bar all the time - screen capture don't show it, I had to take a photo. Lots of black blocks on Finder file lists too. I'm using a
flashed eVGA GT 640 2GB with this Mac Pro:
View attachment 840585
Notes:
- Catalina Sidecar is blocked on MP5,1, read post #59.
- Before anyone asks again, Catalina is not supported (actively blocked) on a MP5,1:
View attachment 840834
The block showed above is in the distribution file, InstallESD.DMG/OSInstall.mpkg/Distribution. It's a double block, since you need to add the boardID to the list of supported ones.