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 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I have both bluetooth keyboard and mouse, and at the boot picker i have to click the mouse or button on the keyboard ( i usually do caps lock since it doesn't start any actions) a few times for them to connect before the timeout.
yes, previous normal no problem, but I try for Activate AMD hardware acceleration
my mouse and keyboard I see on bootpicker not working, but I try to move and push return working, but on screen cursor not seen move and mouse not show.
but previous my mouse and keyboard normally and I can see on bootpicker
From being burned in the past, my keyboard is hard wired. My mouse is BT. I think having a hard wired device helps with initial boot up. It may have worked before but your are stretching the limits of your cMP with OC.
Does anyone tested the "BigSur beta 5" incremental update 7,15 GB ?
Because seems even spoofing with OpenCore a supported BigSur mac, the software update tells that a full installer is required and invites to download a full 12 GB installer rather than using a correctly detected incremental 7,15 GB update.
Because seems even spoofing with OpenCore a supported BigSur mac, the software update tells that a full installer is required and invites to download a full 12 GB installer rather than using a correctly detected incremental 7,15 GB update.
I just did it and everything went well with the incremental update. I had been prompted with the correct installer. The system never asked for the full installer.
macOS Big Sur vers 11.0 Beta (20A5354i)
Same to me. I tried re-enroll but it didn't fix anything. It always inviting to a full installer. I don't get it why! @jackluke if you find any solution for this please let me know. Thanks.
I spoofed an iMacPro1.1 using OpenCore 0.6.0 on my cMacPro 5,1 (spec in the signature file) It went directly to the 7.15Gb file - updated. but the whole process was over 1 hour ( I have a fast enough internet connection - the download was only about 10 - 15 minutes for the update. The installation took forever - well over 1 hour. ... but it worked well and after rebooting I switched the EFI folder back to my regular unspoofed cMP 5,1 EFI
I did have to edit the hidden file in
/System/Volumes/Preboot/'MYUUID'/System/Library/CoreServices/.disk_label.contentDetails
to change the label in the bootpicker from Preboot to 'BigSur'
BigSur is working well now
I did have to edit the hidden file in
/System/Volumes/Preboot/'MYUUID'/System/Library/CoreServices/.disk_label.contentDetails
to change the label in the bootpicker from Preboot to 'BigSur'
BigSur is working well now
Last edited:
What do you mean by "successfully install". You seem to have an issue, so not so successful. Did you follow the first post wiki? I suggest you start from scratch and follow the wiki in post #1. I had 0.5.9 working well and just set up 0.6.0 by following the wiki from scratch.
Help please.
I just installed OpenCore 0.6 on my 2010 cMP 5,1 with a Radeon RX580 and NVMe blade that boots to Catalina (10.15.6). While configuring the config.plist, I noticed that there is an argument for Opencanopy.efi, but when I downloaded the OcBinaryData zip file, I did not see the .efi file. My cMP boots ok, but I am not seeing the boot picker screen.
Suggestions?
Thank you in advance!
I just installed OpenCore 0.6 on my 2010 cMP 5,1 with a Radeon RX580 and NVMe blade that boots to Catalina (10.15.6). While configuring the config.plist, I noticed that there is an argument for Opencanopy.efi, but when I downloaded the OcBinaryData zip file, I did not see the .efi file. My cMP boots ok, but I am not seeing the boot picker screen.
Suggestions?
Thank you in advance!
Thank you, nobullone1964, I do not see the GUI. I did not see the open canopy.efi. I thought the GUI components were present with the downloaded files. I wonder if I overlooked a config argument. I double-checked and did not notice anything missing.
Last edited:
Hi folks,
I really did not plan to mess around with Open Core on my 5.1, however, I did purchase a flashed Gigabyte Titan Ridge card for Thunderbolt support. - What I really did not know about this, - it only runs with an Open Core installation. ughh..
So, who can help me with this? I am really good with hardware mods, Pixlas was easy for me, however when I think about Open Core software and the risk to brick my system I am sweatn bullets here. To go through all 146 pages of this post seems tough, can someone point me in the right direction? Where should I start? Or could I circumvent this with a simple Canopy boot picker product? I guess not..
I really did not plan to mess around with Open Core on my 5.1, however, I did purchase a flashed Gigabyte Titan Ridge card for Thunderbolt support. - What I really did not know about this, - it only runs with an Open Core installation. ughh..
So, who can help me with this? I am really good with hardware mods, Pixlas was easy for me, however when I think about Open Core software and the risk to brick my system I am sweatn bullets here. To go through all 146 pages of this post seems tough, can someone point me in the right direction? Where should I start? Or could I circumvent this with a simple Canopy boot picker product? I guess not..
Hi! I am a simple user. I didn't read all 147 pages here (in fact I don't understand 90% of the contents). I just followed word by word the thread #1. The wiki is very detailed, information is verified by a lot o people here. They have done a great job. I think you can trust without sweating any bullet! Just follow the post #1... point by point...
Last edited:
I had OpenCore 0.5.9 installed on my secondary cMP (dual X5680 and a Pulse RX580) and was able to upgrade OC to 0.6.0 and also make mods including putting OC on a USB stick, make PCI drives appear internal, and also install the graphical boot picker. I carefully followed the fantastic instruction in wiki post #1 and all has gone well.
Thank you to those of you clever people who created these options to extend the life and functionality of our blessed cMPs, and to all the community who contribute to helping others out. There’s a huge amount of patience and good will alive here on MR.
For those of you just arriving here and wanting to give OC a go, I can’t say it strongly enough - go to post #1, read through the full post and work out what you want to achieve (including the options) before you start taking your first steps.
Thank you to those of you clever people who created these options to extend the life and functionality of our blessed cMPs, and to all the community who contribute to helping others out. There’s a huge amount of patience and good will alive here on MR.
For those of you just arriving here and wanting to give OC a go, I can’t say it strongly enough - go to post #1, read through the full post and work out what you want to achieve (including the options) before you start taking your first steps.
OpenCore is a great project. It works. @tsialex tells us that OpenCore can run Catalina with the no_compat_check added to boot without it. DosDude1 has a patched version. My 5,1 machine doesn't need any of his patches except those requiring booting to the OS. My question is can we do a vanilla install that can be applied without patches? Can we edit the installer to delete any blocks that mention this said Mac Pro? And...will they stick post install?
Catalina runs without any patches or OpenCore, if you have a fully compatible MP5,1 - just need a compatible Mac or a VM to install and -no_compat_check at the boot-args.
With OpenCore, you can install and update on your MP5,1 directly, that’s why OC supplanted every other way to run Catalina.
I am using OC 0.6.0. updated from 0.5.9 following the post #1 wiki. Works like a charm without needed to mess with any system files.
I agree totally. My point is an installation from the start that will stick. My main concern was booting without a patch. We all know that those exist, but can it be done without opencore? I've done the opencore installation with only a Catalina drive. It worked. Can it be done without utilizing opencore. I use all my kexts directly installed. Some say it's safer with opencore utilizing the kexts installed directly. I say bull. Before this project started everyone installed their kexts directly. Now, because of this project, they say use opencore. Nix opencore, forget about the patches and opencore for the boot. Is it possible to create an installation that utilizes part of DosDude's creation (boot) with the opencore setup within that works beyond Apple stating this computer can not be supported that will stick? Yes, I realize that a pram can throw it off. That is what I am looking to see. If I had half the ability to do the work these guys have done I may find a resolution. So my question exists...
OpenCanopy.efi is in EFI/OC/Drivers. It comes with the OpenCore download and is copied over in the first step where you copy the OC EFI folder. It doesn't come with the OpenBinaryData. Check that it is there. Your settings for opencanopy in your config look correct.
I notice you have <key>ShowPicker</key><false/>. If you want it to come up without holding down opt or esc set this to true and reboot.
Last edited:
Well I guess it depends on what you are trying to achieve. I run Catalina on my MacPro5,1 with just -no_compat_check in the boot args and without OC. I boot OC from a USB stick with the VMM flag when I want to run software update on my Catalina install otherwise I don't use OC. I'll probably change at some point but for now I don't have an OC EFI partition on one of my internal drives.
Thank you, 6DecadesLater, I edited ShowPicker to keep it off the grid until I develop a solution. I did check to see if I can locate OpenCanopy.efi in EFI/OC/Drivers and it is there. I rebooted and not GUI or picker screen. Still troubleshooting.
Last edited:
When the bootpicker is set to off it should default to EFI if you haven't set a startup disk in system preferences. Start with the basic config linked in post #1. You should show the list when booting. When you get to that point hit me up and we'll go from there.