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
I tried target disk mode from MacBookPro15,1 with Catalina rev1 installed. Downloaded the Catalina rev 2 and upon attempt to install to the target disk I get:
"you may not install to this volume because it is a mac in target disk mode"
[doublepost=1561062322][/doublepost]Bootcamp installer rejects to continue until all external drives (target drives) are ejected
"you may not install to this volume because it is a mac in target disk mode"
[doublepost=1561062322][/doublepost]Bootcamp installer rejects to continue until all external drives (target drives) are ejected
I tried target disk mode from MacBookPro15,1 with Catalina rev1 installed. Downloaded the Catalina rev 2 and upon attempt to install to the target disk I get:
"you may not install to this volume because it is a mac in target disk mode"
[doublepost=1561062322][/doublepost]Bootcamp installer rejects to continue until all external drives (target drives) are ejected
Wow, looks like Apple is actively trying to prevent that workaround. I'm honestly surprised.
Okay, so what I'm going to attempt tonight is to install DR2 to a PCIe NMVe SSD mounted to a USB3.1 adapter (https://smile.amazon.com/gp/product/B07JKWHFRC/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1) using my 2017 mBP. I'll then transfer the NVMe SSD to my 5,1 cMP after applying the NVRAM boot args. We'll see how that goes and report. Anybody got advice, caveats?
I think it should work.
Actually, I did the similar steps as follows:
* I installed Catalina DP1 to SATA3 SSD on MacBook Air 2013 via USB 3.0.
* I put the SATA3 SSD on MacPro5,1, and it booted Catalina DP1 with NVRAM boot-args option.
* Recently, Catalina DP2 was released, so I connected the SATA3 SSD of Catalina DP1 to MacBook Air via USB 3.0 again, and updated it to Catalina DP2 (with Software Update, but it does not matter because DP2 is full installer anyway).
* It booted Catalina DP2 on MacPro5,1 with NVRAM boot-args option.
I don't have any issue so far.
Last edited:
Thank you everyone for doing the heavy lifting of making this work and sharing back with the community. I look forward to running Catalina on my 4,1>5,1 once it is in general release.
Well, I did the above by attaching an NVMe SSD to a USB3.1 adapter and loaded Catalina from my 2017 MPB. I applied the NVRAM boot args, transferred the NVMe to a PCIe adapter and put it in my 5,1. It booted fine. As others have reported, the drive shows up as 2 volumes. None of my NVMe drives are showing as internal, so I'll try the Innie fix to see if that works (maybe). I've got the OSXWiFi ac/BT4 adapter and it shows up fine. Music and AppleTV locked up when I tried them.
All types of PCIe drives (AHCI, SATA3, SAS, NVMe) are external to the Mac Pro firmware, it's absolutely normal. Only SATA drives connected to the southbridge SATA2 ports are internal for the Mac Pro firmware. You gain absolutely nothing performance wise hacking kexts to make PCIe drives show as internal.
I understand from a performance perspective there's nothing to be gained, but I understood that certain MacOS performance functions (e.g., swap or paging files) wouldn't be written to an external drive. I could be wrong.
No, it's exactly the same. If wasn't, a Mac Pro with SAS drives, RAID arrays or only NVMe drives wouldn't work the same as one with SATA drives connected to the southbridge SATA ports.
Just a thought but had anyone noticed that the airport code for Catalina Airport is AVX? I think we might be screwed but I really hope I’m wrong and it’s just some weird coincidence.
So only the wifi does not work? I thought there was a requirement for BT 4 (Or maybe the Airdrop only):
https://forums.macrumors.com/thread...nsupported-macs.2183772/page-77#post-27486171
Bluetooth 4 is required for AirDrop/CAT/etc, but MP5,1 Bluetooth 2.1 still works.
[doublepost=1561384400][/doublepost]
This is answered on the first post. Besides the need of an updated AirPortExtreme BCM94360CD/BCM943602CD or the install of Mojave AirPortBrcm4331.kext, everything works as with Mojave.
Sidecar needs native HEVC encoding support, all Skylake and newer Macs does HEVC encoding with QuickSync except iMac Pro which uses GPU HEVC encoding. Macs that don't have native HEVC encoding are blocked from using Sidecar.
Last edited:
Edited the previous post to "Sidecar needs native HEVC encoding support, all Skylake and newer Macs does HEVC encoding with QuickSync except iMac Pro which uses GPU HEVC encoding"
Apple released PB1, build is 19A487m, and reissued DP2 as the same build as PB1, already downloading it here.
Distribution file continue to block MP5,1:
Distribution file continue to block MP5,1:
Last edited:
It was JUST released... suggest to give it some time or else give it a shot on your machine. Unsure public beta build number or if there is any major difference from DP3.
I'm somewhat confused. Is there actually a Developer Preview 3 of Catalina that is different from DP2? DP2 was 19A487l. Is the "new" DP3 actually "19A487m", or is it called "DP3" just because a PB1 was released? The regular software update mechanism in my Catalina DP2 can't see any updates.
With the build number only changing suffix from 'l' to 'm', I'd expect there to be no significant difference between DP2 and PB1.
It doesn't mention such a thing NOW. The fact that Catalina may work on such gear was mentioned the moment this thread was created.
I made a confusion yesterday, sorry. Apple released PB1 and reissued DP2 on the Seed channel as the same build as PB1, it's not DP3. I edited my previous post.
[doublepost=1561472847][/doublepost]
original DP2 19A487l
reissued DP2 19A487m
PB1 19A487m
Reissued DP2 and PB1:
Original DP2:
Last edited:
Well, some great news. On my Mac Pro 5,1 (mid 2012) with the requisite Metal video card, I'm able to run Catalina on my Mac.
Don't know which post or thread I found this information from but it helps (BUT WITH A MINOR CHANGE).
----------
macOS Catalina runs great and very smooth on MacPro5,1. No need to patch or upgrade.
You just need to do these 3 simple steps for the MacPro5,1 to run macOS Catalina:
(1) Install masOS Catalina on a drive on a supported Mac.
(2) Boot your MacPro5,1 to recovery, and then in terminal, type:
sudo nvram boot-args="no_compat_check"
(3) transfer the drive with macOS Catalina installed to the MacPro5,1 and and boot. The MacPro5,1 will now boot up macOS Catalina.
----------
HOWEVER I got an error when doing step 2 above. Then I proceeded to enter the same command in step 2 EXCEPT not to enter the "sudo" part.
I'm happy now. My MacPro 5,1 is also happy.
Don't know which post or thread I found this information from but it helps (BUT WITH A MINOR CHANGE).
----------
macOS Catalina runs great and very smooth on MacPro5,1. No need to patch or upgrade.
You just need to do these 3 simple steps for the MacPro5,1 to run macOS Catalina:
(1) Install masOS Catalina on a drive on a supported Mac.
(2) Boot your MacPro5,1 to recovery, and then in terminal, type:
sudo nvram boot-args="no_compat_check"
(3) transfer the drive with macOS Catalina installed to the MacPro5,1 and and boot. The MacPro5,1 will now boot up macOS Catalina.
----------
HOWEVER I got an error when doing step 2 above. Then I proceeded to enter the same command in step 2 EXCEPT not to enter the "sudo" part.
I'm happy now. My MacPro 5,1 is also happy.
- Status