Off topic I know but I have decided for the time being that Catalina is a waste of time, offering little or no advantage and I dont like the way it partitions the hard drive so i think i'll give it a miss.
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.
MP 1,1-5,1 Obsolete, Use OpenCore instead | What you need to do to make Catalina work with MacPro5,1
- Thread starter tsialex
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
- Status
Well thanks for confirming that Target Disk mode is not an option.
But if you want your ios 13 reminders to show up on your Mac Pro work station . . .
Just a quick question so I understand correctly:
I have to have nvram boot-args="-no_compat_check" set in NVRAM for Catalina to boot? If I reset the NVRAM I have to enter this again (in my case, start up from the recovery partition on a drive with High Sierra and out in the AMD GPU that came with the computer)?
I have to have nvram boot-args="-no_compat_check" set in NVRAM for Catalina to boot? If I reset the NVRAM I have to enter this again (in my case, start up from the recovery partition on a drive with High Sierra and out in the AMD GPU that came with the computer)?
Any GPU that is supported from Recovery will work fine, you will only need to change your GPU to an older one if you have a Catalina exclusive GPU, like Radeon 5700XT.
High Sierra and Mojave Recovery supports all recent AMD GPUs, 10.13.6 only don't support Radeon VII if I remember correctly.
Happy to report that it worked exactly as I'd hoped...
- removed the drive from the mp5,1 and connected to mbp with a SATA-USB cable
- booted mbp using option key
- update to 10.15.2 using system update
- shutdown mbp
- moved the drive back to the mp5,1
- booted and all up and running on 10.15.2
Catalina 10.15.2 runs well overall for me too on my 5,1 with a new RX 5700 XT GPU, but I did experience a Kernel Panic when waking the computer from sleep:
discussions.apple.com
Maybe 10.15.3 will fix it, but after having disabled letting the computer sleep automatically and sleeping it manually I've had no problems waking it up. Also great having the computer wake much faster compared to High Sierra, which was really slow unless waking via a quick press on the power button of the computer.
In Windows 10 on the same machine I've had two glitches which seems related to the drivers from AMD, so hopefully (probably) that gets solved with driver updates down the road.
Since installing Catalina yesterday, mult… - Apple Community
Maybe 10.15.3 will fix it, but after having disabled letting the computer sleep automatically and sleeping it manually I've had no problems waking it up. Also great having the computer wake much faster compared to High Sierra, which was really slow unless waking via a quick press on the power button of the computer.
In Windows 10 on the same machine I've had two glitches which seems related to the drivers from AMD, so hopefully (probably) that gets solved with driver updates down the road.
It's a question answered on the first post, Apple removed the kexts needed for MacPro 2009 and 2010/2012 AirPort Extremes. Or you install the kexts yourself, or you upgrade to a AirPort Extreme AC (BCM94360CD) that is supported.
Ok, ordered the new AirPort Extreme AC hardware and will proceed to install Catalina after that
Mainly doing it so I can get the RX 5700 to work on Mac OS.
Thanks!
Installing Catalina from a VMWare Fusion 11.1 Catalina VM to a real disk attached to the VM (using vmware-rawdiskCreator to create/attach the disk):
View attachment 841466
View attachment 841469
View attachment 841473
View attachment 841474
View attachment 841475
Works beautifully and people that don't have a supported Mac to install Catalina have a way to install it to a MP5,1 without the need to do it by hand.
It's a lot more practical and faster than installing it using an USB adaptor + a supported Mac.
As explained on the first post, you just need to add -no_compat_check to the boot-args to boot your MP5,1 from the Catalina disk installed by the Catalina VM.
View attachment 841476
tsialex,
I'd like to try this and have carefully read through all the posts relating to this and every other one. (yes I read each and every post on this feed - all 30 pages).
I acquired VM Fusion Pro 11.5 and tried to install it on my cMP4.1 ->5.1 to find it will not run with my W3540 CPU. It prevents it from running. It gives me an error on install
In one of your early posts of this feed you say you too have a cMP4.1 ->5.1. How did you get to use VM Fusion 11.1 to do this?
I have a real cMP5,1 as well so I could install on that cMP and swap the SSD but in both macs the SSDs are installed on OWC Mercury Accelsior S PCI cards. Swapping between machines once would not be a hardship but for each upgrade 10.15.2 to 3, to 4 etc would become a hassle.
Advice?
You need a Westmere Xeon, any W36xx or X56xx will work. Nehalem Xeons won't work correctly after 10.14.3 and never supported Apple Hypervisor. That's why you can't run Fusion/Docker/Anka/OpenCore VMM flag spoofing.
I'd buy a X5677, cheap and very fast.
Single tray MP5,1 works fine speed wise after Catalina was released, but people with dual CPU trays have some problems since Apple are not testing it anymore since no 10.15 supported Mac have dual CPUs.
People are having KPs with AppleIntelMCEReporter.kext, removing/blocking it resolve the problems. More info here https://github.com/khronokernel/What-s-new-in-macOS-Catalina
@startergo had problems with AppleIntelMCEReporter.kext and OpenCore, look at his posts.
Since most people don't know how to check if your current CPU supports Apple Hypervisor, this is how to check if your current CPU supports it and can run VMware Fusion 11.5, Docker, Anka and more importantly, spoof the VMM flag with OpenCore for having native Catalina installs and software updates.
Open Terminal:
Apple Hypervisor supported the answer will be kern.hv_support: 1, it's a mid-2010 Mac Pro upgraded to X5680:
This is the same mid-2010 Mac Pro but back with the original W3565 Xeon Nehalem installed. Apple Hypervisor unsupported, kern.hv_support: 0,
This is a early-2008 Mac Pro, Apple Hypervisor unsupported, kern.hv_support: 0:
Open Terminal:
Code:
sysctl machdep.cpu.brand_string; sysctl kern.hv_supportApple Hypervisor supported the answer will be kern.hv_support: 1, it's a mid-2010 Mac Pro upgraded to X5680:
This is the same mid-2010 Mac Pro but back with the original W3565 Xeon Nehalem installed. Apple Hypervisor unsupported, kern.hv_support: 0,
This is a early-2008 Mac Pro, Apple Hypervisor unsupported, kern.hv_support: 0:
That was very useful - wish I'd known about it prior to starting down this road with = VMWare Fusion and Catalina VM attached to a real disk...Since most people don't know how to check if your current CPU supports Apple Hypervisor, this is how to check if your current CPU supports it and can run VMware Fusion 11.5, Docker, Anka and more importantly, spoof the VMM flag with OpenCore for having native Catalina installs and software updates.
Open Terminal:
Code:sysctl machdep.cpu.brand_string; sysctl kern.hv_support
Apple Hypervisor supported the answer will be kern.hv_support: 1, it's a mid-2010 Mac Pro upgraded to X5680:
View attachment 885112
This is the same mid-2010 Mac Pro but back with the original W3565 Xeon Nehalem installed. Apple Hypervisor unsupported, kern.hv_support: 0,
View attachment 885111
This is a early-2008 Mac Pro, Apple Hypervisor unsupported, kern.hv_support: 0:
My output for my cMP 4,1-> cMP 5,1 was:
but following your advice my replacement processor (X5677) is on it's way and should arrive between Jan 6 and 13. Plenty of time to get hardware for de-lidding and hex wrench long enough to reach the 3mm screws.
Thanks again for your advice with this.
Since you have a W3540, you have a single CPU tray MP4,1>5,1. Only dual CPU trays for 2009 Mac Pros use de-lided Xeons.
No need to de-lid at all for replacing your
Last edited:
What’s the advantage of this method over dosdude1‘s patcher on MP 5,1? Apologies if this has been discussed already.
- Status