I vaguely recollect not being able to boot into the subject disk once but I only have my default disk loaded as a option in Refind and not 100% sure. Will add that disk to be scanned for booting by Refind and confirm later.
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 want to stick to OC only solution for now if possible (= and I have an exception which is: before I knew to beware of MacVidCards, I got my Vega56 reference from them.
(BTW I got lucky with no issues back then with the card or the individual(s), except I did ask to be able to see the boot picker on both BIOS, and he only sent it with one of them set, which i don't think was much to ask if possible given the price and time he takes.)
So I have 2 BIOS options with a physical switch on the card and one of them is flashed that allows me to see the cMP OG BootPicker, which is all I have to remember for now so I don't have to do 50 VRAM resets a week hehe, until we figure this out.
It's also being recommended to me that we use nVME drives as "project drives" instead of OS, since some issues are popping up on cMPs it seems, like this one here and we're not sure if this is just an OC thing, or if it's a symptom of something else. I do love being able to run everything in one nVME place and how snappy it all is, especially for those of us moving a lot of big'n'chunky files around.
Wasn't suggesting anything to you ... only quoted your post along with others in the context of realising that the issue was widespread and not just affecting my setup.
I have stock EFI. Would be nice to get to the bottom of the issue.
True ... just wasn't in this case.
Seems you followed the wiki on Page 1 which is the default way to go.
Hehe ok just making sure, because I didn't mean to imply I don't want suggestions. They're always welcome (= this is also why I employ the use of modern hieroglyphs extensively.
@startergo I've been trying some variations here and there, and so far my nVME drive is good to go and shows up in OC BPicker when I have the physical BIOS switch on my GPU set to low power (it's the mode that has no mac flash, - it is also the mode that results in better performance for me). I'll report back if this acts funny too.
@Dayo I followed the main Wiki kind of, because I have no interest in Catalina for the time being, and the way 0.5.8 comes packaged I barely had to do anything to the config except look at it, with documentation, and learn why it is the way it is - which has also been great.
They should make a mini documentary one day about the cMP community, it really is amazing that 10 years later, the same tower I started with is still under my desk, all thanks to a number of main dedicated geniuses and the community behind them to back it up!
This is all slowwwly starting to make sense - after poring over the original post, a couple of questions remain:
1) Does Disk A have to be blank except for OC and the install disk?
2) Must Disk B be a Mojave installation, or can a patched Catalina install work? I did the DosDude1 thing and would like to overwrite it if possible...
1) Does Disk A have to be blank except for OC and the install disk?
2) Must Disk B be a Mojave installation, or can a patched Catalina install work? I did the DosDude1 thing and would like to overwrite it if possible...
The Page 1 Wiki has an issue in that it gives the impression you must install Catalina to use OpenCore or perhaps more accurately, that installing Catalina is an integral part of installing OpenCore.
At least that's what I thought when I first came across this thread and I can see the same from a lot of questions on this. The actual case is that OpenCore allows you to install Catalina natively if you so wish but it is not a requirement.
It is a wiki and anyone and edit it but the Catalina angle is so deeply ingrained in the wiki that one would really have to tear it up in a manner that could mess things up to remove that impression it gives.
Some of us are on the even older 3,1 units. Mine is in its 13th year. Simply amazing.
All the more so as of the stuff posted is targeted at the 5,1 units but we find our way.
1) The disk doesn't have to be blank. You're really just using it for its EFI partition.
2) A patched Catalina install might work (if you can get into recovery), but I recommend Mojave.
I guess the reason is historical. Originally, the motivation for OpenCore was simply to install Catalina and have native updates. Because there was no boot-screen support for standard graphics cards, most users were in the dark, and it was important to have a very rigid set of instructions.
Now, with boot-screen support and all the other benefits OpenCore provides for the classic Mac Pro, things are certainly different. Perhaps the guide should be revised to allow for more freedom...
While I agree with the fork you're proposing, this guide serves its purpose and should stay this way because the Catalina subject is also in demand, and a necessity eventually some would say. I do think this one could be renamed to reflect the focus on Catalina though.
Building on that thought, what we're getting at collectively here, is that a guide that is more neutral and focused on OC itself without protagonizing the OS, would be helpful at some point moving forward (like the current title reflects basically).
I agree with @cdf sentiment the reason is historical hehe. Makes sense. Given the relatively early stages of OC as a deployable mostly pre-set package, I understand why we are here though. This is all still unfolding!
The amount of questions argument is relative IMO, and seems inevitable either way
one could say the current title and nature of OC right now leads to more mixed threads to dig through.The new proposed guide could:
- have a base layer covering the OC stuff like this very guide does, without the catalina focus.
- Within the guide we can maybe have it get to a section that is outlines OS specific forks or links to guides like this one.
I think that the current guide here is actually evolving this way. I'm currently working on a section for third-party-OS installation (which, incidentally, reveals a feature of OpenCore that has not yet been used for the Mac Pro...). The existing section on installing Catalina could be treated similarly. As a result, Part I of the guide would become this base layer.
Thinking loud here, one thing that probably should be done is a fork focused exclusively on MP5,1 + Catalina install and updates (VMM), a "for newbies" release of this thread that would make easier for newbies to understand what OC brings and can do.
A FAQ with the most common questions that newbies do on the first post would be very welcome too.
[automerge]1590540014[/automerge]
Btw, the newbies guide to OC should be a sticky - newbies don't know how to search
A FAQ with the most common questions that newbies do on the first post would be very welcome too.
[automerge]1590540014[/automerge]
Btw, the newbies guide to OC should be a sticky - newbies don't know how to search
Last edited:
Yes, I only had 2 unknown objects into Device Manager, one was the Bluetooth and the second was the Wifi. I right-clicked on each to install the drivers. For RX580 video or any other drivers, I used the Windows update and did not downloaded anything off the web. On first install, I did downloaded the AMD drivers but they did not help with HWAccel.
If anyone manages to get HWAccel in Windows, please share the info.
Wouldn't it be easier to have a community based 4,1/5,1 cMP Open Core EFI folder on github?
Has anyone tried applying the 10.15.5 update natively? I've setup 2 config.plist files, both identical, except one has the VMM flag enabled, the other not. Booted with the VMM flag on, and got the prompt for the update. After selecting to download and reboot, it initially goes to the applying the update Apple logo with progress bar screen, it advances something like 5-10% and then reboots, which gets back to the OC picker, and choosing Catalina (vs. Mojave or Win10) back to the desktop and Software Update noting 10.15.5 is available. This just continues to repeat the same cycle. Changing back to my normal config (VMM off) and the update prompt is there, but when selected it just immediately reboots without the Apple logo/progress bar screen. Did they build some logic in this update to bork OC/cMP implementations of Catalina?
Sure, but what I'm proposing is to simplify/facilitate for newbies, not for the advanced users.
Newbies don't even know how to download from GitHub.
Distribution file has the exact same VMM test as before, nothing changed:
10.15.5 Combo (061-78580):
10.15.4 Combo (061-72538):
Yes one of my drives is running the latest update. I lost Bluetooth though
Edit:
10.15.5. beta I lost the bluetooth. 10.15.5 release- bluetooth is back.
Last edited:
I turned on the VMM flag and successfully updated to 10.15.5.
It turns out that this is expected. When your Mac reboots during the update, you should leave the boot picker timeout to the default selection staged by the update. Otherwise the update will not proceed.
It turns out that this is expected. When your Mac reboots during the update, you should leave the boot picker timeout to the default selection staged by the update. Otherwise the update will not proceed.