You've actually helped me improve the documentation, thank you for your help.
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
Here's my current view on this:
Every new release of OpenCore comes with new options added and old ones removed, and the wiki in this thread is updated accordingly. While some users are happy with updating the configuration manually, others look for ways of automation. This is especially true of enthusiasts with backgrounds in scripting and programming. Such capable users can come up with many different solutions that fit their needs.
When users go through the wiki, they learn how to manually configure and install OpenCore on the Mac Pro. The aim of the wiki is to not only provide a minimal and robust approach, but also promote a configuration tailored to individual systems (for example, optimal GOP settings depend on video card model, and advanced production-style setups involve specific device paths, as boot-args should be reserved for debugging.)
A generator tool can abstract many OC settings and therefore simplify installation and updates, but for it to be consistent with the guide, it requires a configuration of its own. Of course, such a tool is very useful, and admittedly I have contemplated incorporating one in the guide. However, my current view is that the added abstraction is at odds with the aim of the wiki.
Is there any 6,1 OpenCore user here?
If possible, I wish someone can run a test.
So far, even we can achieve HEVC hardware encoding on the 5,1, we can't stream the desktop to AppleTV (or use SideCar). We can force the UI to show up, but even spoof the ident to 7,1, all we get still just black screen.
iGPU / T2 is confirmed not the key, because the above function can work on a Xeon Hackintosh.
So far, when some macOS function involve AVX, it may act abnormally on the cMP (e.g. Japanese input involve AVX, which makes no Japanese character shows up when we use such Japanese input on the 5,1). However, the system won't crash, and won't even show any warning. I suspect this "unable to use desktop streaming" may be in a similar situation.
Since we know that the 6,1 can also get HEVC hardware encoding via eGPU by using OpenCore. I wonder if any 6,1 user can try if they can use stream their desktop to the AppleTV or via SideCar.
If the 6,1 can stream out the Desktop once HEVC encoding is activated. Then more likely some key functions are missing on the 5,1's CPU.
If possible, I wish someone can run a test.
So far, even we can achieve HEVC hardware encoding on the 5,1, we can't stream the desktop to AppleTV (or use SideCar). We can force the UI to show up, but even spoof the ident to 7,1, all we get still just black screen.
iGPU / T2 is confirmed not the key, because the above function can work on a Xeon Hackintosh.
So far, when some macOS function involve AVX, it may act abnormally on the cMP (e.g. Japanese input involve AVX, which makes no Japanese character shows up when we use such Japanese input on the 5,1). However, the system won't crash, and won't even show any warning. I suspect this "unable to use desktop streaming" may be in a similar situation.
Since we know that the 6,1 can also get HEVC hardware encoding via eGPU by using OpenCore. I wonder if any 6,1 user can try if they can use stream their desktop to the AppleTV or via SideCar.
If the 6,1 can stream out the Desktop once HEVC encoding is activated. Then more likely some key functions are missing on the 5,1's CPU.
Or perhaps the issue is like DRM: Even with supported GPUs, older CPUs are blocked in the frameworks...
I definitely chose to follow cdf’s guide for setting up OC precisely because the details are explained in a step by step fashion exactly what is being done. I think any attempt to create a generalized automation will hide those details just as cdf explained. For my own part I have tried some other automatic solutions such as MyBootMgr and while they work fine, I personally prefer to have more knowledge of what I am doing. In my case I have made a script that basically just follows cdf’s instructions according to my own personal preferences. Nobody else would be able to use that script without editing it for their own choices.
But cdf’s commitment to documenting the wiki with exactly the changes needed are crucial for me. If and when things change to support Big Sur better, etc I will be able to easily read the latest wiki update and then edit my own script as needed to ensure it complies, according to my own prefs.
My script mainly helps me because I should not have to manually edit
config.plist every time a new version of OC comes out, many times without any changes to cdf’s wiki per say, but the starter config.plist which cdf provides usually always changes with each OC update. So that means in order to update OC one has to manually edit the config.plist all over again with essentially the same changes as before. The first time or two I learned some things, but now it’s just manual labor. So that is where a script comes in. But I prefer to have a custom script that is basically simple and exactly follows cdf’s guide, which I can easily change if and when the guide changes.there might be a way to make something like that generic for everyone but I think solutions like that are hard to do without getting overly complicated and as cdf noted the tendency will be for people to use the script without following the guide even once or twice and then you will have people running OC without any idea what they have done.
I also don’t like solutions where they are starting from a blank empty config.plist and building up everything because that means the script itself will have to updated far more often, literally once a month.
For me personally I prefer to take ownership of what I am installing, which Kexts, etc, but I just want to take the pain out of updating OC as often as once a month and having to manually edit the config.plist every time.
Last edited:
I am running RefindPlus/OpenCore on a MP5,1 with an unpatched copy of Mojave. I'd like to install Catalina on a separate drive for testing and just want to make sure my logic is sound:
1. Boot into OC alternate Mojave (VMM flag active)
2. Run Catalina installer and select target drive
After reboot, will RefindPlus automatically add Catalina as an OC option or will I need to do something additional? I know the boot picker will see the standard Catalina installation, but not sure how to get Catalina running as an OC instance.
1. Boot into OC alternate Mojave (VMM flag active)
2. Run Catalina installer and select target drive
After reboot, will RefindPlus automatically add Catalina as an OC option or will I need to do something additional? I know the boot picker will see the standard Catalina installation, but not sure how to get Catalina running as an OC instance.
The RefindPlus angle is a bit misleading as what it seems you are actually asking is whether OpenCore will pick up your new Catalina installation.
RefindPlus does not control anything in OpenCore and only allows you to select and boot one OpenCore instance or the other. That is the extent of the relationship between the two utilities. Think of RefindPlus as being like Finder on your Mac. It is basically a tool that allow you to select and run programs (it is a bit more than that but that is the basic function).
The OpenCore and RefindPlus thing is just a process where two totally separate and independent programs are configured to co-exist. That's all there is to the setup and each runs as if installed alone and the other is not there.
So, when you install any Mac OS version, OpenCore adds it by itself and it will be available in your OpenCore instances. It is not added by RefindPlus, which as said is just like Finder.
OpenCore will behave exactly as it would if you had installed it alone. There is no involvement by RefindPlus in what OpenCore shows as a boot option or in anything else with OpenCore for that matter.
As long as the drive on which Catalina is installed is a type of drive OpenCore is set up to scan, it will find it and show it as a boot option. For instance, it may not show up if installed on an NVMe drive and you have not set OpenCore up to scan such drives. If you used ConfigFactory, it would have sorted this out.
Last edited:
@Dayo, thanks. This is what I assumed but did not experience. As a preliminary test, I connected an external HDD that has a cloned image of Mojave on it. Upon boot, RefindPlus shows two non-OC Mojave installations; the original on my internal SSD, and the cloned image on external HDD.
The original two OC instances were also visible, default and alternate. Selecting either default or alternate would only start the internal SSD Mojave install. I did not see an option to boot the external Mojave copy in an OpenCore instance.
The original two OC instances were also visible, default and alternate. Selecting either default or alternate would only start the internal SSD Mojave install. I did not see an option to boot the external Mojave copy in an OpenCore instance.
This threw me for a loop when I first got into RefindPlus also. Basically RefindPlus will show you all bootable volumes on your system and will also show you OC configurations as bootable items. But note that an OC config is not pointing specifically to one particular OS to boot. each OC configuration is just a hardware-emulation, so to speak...and when you choose OC to boot to it..then you will see another boot menu provided by OC itself, which is where you would choose with underlying OS you want to boot through OC. RefindPlus also just shows you all the other Boot volumes, that you can potentially boot WITHOUT using OC, and it gives you the ability to have more then one OC configuration to choose from.
As I mentioned, the OS Loaders that are shown in OpenCore is an OpenCore configuration item based on where they are installed. Therefore, the OpenCore config file has to be set to enable that disk type to be scanned.
Chances are that OpenCore is not configured by ConfigFactory to scan such external drives for OS boot loaders.
You will need to look at the ScanPolicy key in your OpenCore config and set it to scan such drives or set it to "0" to scan everything. The Config used in Post 1 of this thread sets to zero as it needs to be "one size fits all" for settings that do not appear in the guide here.
The main thing is that as long as you understand that OpenCore setup using MyBootMgr is just like any other OpenCore, then you know that to configure it, you need to amend the OpenCore config file.
In this case, you need to either refer to the OpenCore manual or if asking the question here for instance, this then becomes "What do I need to set in my OpenCore Config for Mac OS installed on an external disk to appear as a boot option". That you are also running RefindPlus is not relevant and the question would be the same with or without RefindPlus.
Now someone answering might say it should appear by default as they may assume you are following Post 1 which you will need to bear in mind.
So as to that question, the ScanPolicy key needs to be set accordingly. You can go for 0 (Scan Anything/Everything) if you find the manual difficult but this has some side effects as some unwanted items may show up.
Need to be conscious of drifting further Off-Topic here though.
Last edited:
I have just noticed that after upgrading to Catalina (trought OC) my 5,1 Mac Pro the wifi is just not working.
Just me or a known issue (that I completely missed)?
Just me or a known issue (that I completely missed)?
Startergo, may be you missed my point.
I am not saying try Sidecar on the 6,1 after using SidecarEnabler.
I mean, the 6,1 CAN get HEVC hardware encoding by using eGPU and OpenCore. And Hacktintosh guy proved that iGPU is NOT a requirement, because Sidecar can work on a Xeon Hackintosh which doesn't have any iGPU.
So, that iGPU / T2 requirement is bursted. (Unless that Hackintosh guy made a false report, which we don't know at this moment)
Therefore, it may be worth to test if the 6,1 can use Sidecar after activating HEVC hardware encoding. A complete spoofing to 7,1 may be better at the beginning of the test. It can remove some unnecessary variable (e.g. the effectiveness of SidecarEnabler etc).
I am not saying try Sidecar on the 6,1 after using SidecarEnabler.
I mean, the 6,1 CAN get HEVC hardware encoding by using eGPU and OpenCore. And Hacktintosh guy proved that iGPU is NOT a requirement, because Sidecar can work on a Xeon Hackintosh which doesn't have any iGPU.
So, that iGPU / T2 requirement is bursted. (Unless that Hackintosh guy made a false report, which we don't know at this moment)
Therefore, it may be worth to test if the 6,1 can use Sidecar after activating HEVC hardware encoding. A complete spoofing to 7,1 may be better at the beginning of the test. It can remove some unnecessary variable (e.g. the effectiveness of SidecarEnabler etc).
By the way SidecarCore is no longer in
Code:
/System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/Big Sur - Sidecar file missing from SidecarCore.framework · Issue #140 · ben-z/free-sidecar
MBP 16" 2019: iPad Air2 11.1 Big Sur: iPadOS 14.4: /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore The above file doesn't exist. I guess Big Sur changed the way the a...
github.com
Last edited:
Frameworks are in the framework cache.By the way SidecarCore is no longer inCode:/System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/
Big Sur - Sidecar file missing from SidecarCore.framework · Issue #140 · ben-z/free-sidecar
MBP 16" 2019: iPad Air2 11.1 Big Sur: iPadOS 14.4: /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore The above file doesn't exist. I guess Big Sur changed the way the a...
I don't know if you can do any patching though.
OpenCore on the Mac Pro
Quick sync is not required. There’s something that we are missing in the spoofing of the imacpro setup. my hack which has a Xeon proc (with no quicksync) does airplay mirror / extended desktop streaming just fine using the rx 580 to handle the encode. I have a thread outside of this one talking...
forums.macrumors.com
I just compared AirMirror from MacBookPro11,3 and cMP5,1. On the cMP theOpenCore on the Mac Pro
Quick sync is not required. There’s something that we are missing in the spoofing of the imacpro setup. my hack which has a Xeon proc (with no quicksync) does airplay mirror / extended desktop streaming just fine using the rx 580 to handle the encode. I have a thread outside of this one talking...
VTEncoderXPCService does not even load. Attached is a sample from the service on the MBP. But I can stream AppleTV contents from the cMP to the Samsung TV screen. Apparently it loads there.
Last edited:
Yeah, clearly "streaming video" is different than "streaming desktop", but we still don't know where the difference is.
But according to Ludacrisvp's post. If his Xeon (iGPU-less) Hackintosh can do desktop streaming. That means we still have a chance. However, his Hackintosh has E5-1650v3, not Westmere. Therefore, I wonder if 6,1 (which also has the E5 Xeon) can do that once HEVC encoding is activated by OpenCore
I believe your question isn't quite precise.
Big Sur itself is 100% relevant to NVRAM / SMC reset. All these reset perform before any OS even start to load.
If you want to know if OpenCore can stay if you reset NVRAM, then the answer is "depends".
It depends on your OC config, and OC is installed on which drive, etc.