Just compared your config file with the one I have that was generated with OCLP. I'm using beyond compare to compare the files.
You are missing half the stuff I have.
Im including my config if you would like to compare it.
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
Just compared your config file with the one I have that was generated with OCLP. I'm using beyond compare to compare the files.
You are missing half the stuff I have.
Im including my config if you would like to compare it.
More is not always better: @TECK has created a deliberate setup and doesn't need that other half.
@cdf - that fixed it though it took a couple of more reboots.
It seems like my update wasn't totally completed and that may have caused additional problems. I fixed the issue you pointed out with my config.plist, rebuilt the rescue CD and rebooted and had a similar problem. I added -v to the boot args and tried again and it booted. I saw a lot of "fixup" entries in the verbose boot and my "Update" Volume on my Monterey disk has been replaced by a Snapshot (com.apple.os.update-....)
I removed the -v boot arg and am back to booting into Monterey without issue.
Thanks again for the help.
Regards,
sfalatko
@NC12 Thank you. I looked in config.plist and "ShowPicker" was set to true.
But this was not the solution. I set ShowPicker to false and the time it took for the white apple symbol to appear was faster. It is only a few seconds. The time it takes for the apple symbol to appear and the progress bar to appear seems to be the same as when it is True after all.
I restored the config.plist from a backup, but that made it impossible to boot. I attach a config.plist that can only successfully boot a Mac. What is the cause?
OCLP is designed to be a broad solution for a variety of setups, so for maximum compatibility it includes a lot of stuff your Mac Pro probably won’t need but someone else’s will. A custom setup would not need as much in the config.plist since it is a lot more focused on the individual device and not a wide range. Hope this helps!
The problem is that both macOS and iPadOS are checking that your devices are supported. We can get around the macOS check, but not the iPadOS check. Perhaps more extensive spoofing could help, though we'd have to determine if it's worth it.
Post in thread 'OpenCore on the Mac Pro'
https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-30935387
This person was able to get it working. I wasn’t able to get it working while wired and I don’t have an upgraded Wifi-Bluetooth card (or any wifi card that is) to test wirelessly.
Post in thread 'OpenCore on the Mac Pro'
https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-30935387
Apparently it is possible but i’m not sure how
Hi
Thank you very much for replying. I tried that and although it got rid of the 'no entry' sign, when I set High Sierra as my startup disk from the OC boot picker, it booted into 10.13 Recovery Mode. Curiously, the StartUp disk menu command in this Recovery Mode only showed 10.13 as an available startup volume. It didn't reveal my 11.6 disk. High Sierra is on a legacy SATA HDD, Big Sur is on an SSD (Sonnet) PCI card. I could get out of this loop by plugging in a wired keyboard to reselect Big Sur as the start up volume from OC Boot Picker so all is good in terms of operation.
Do you have any thought on how to make it boot properly into 10.13, not just the Recovery Mode loop?
I don't as you are getting beyond my skill level though some questions -
Does your graphics card support the native Apple boot screen/picker (EFI flashed)? Where is your OC EFI install? Can you boot into HS with the BS disk removed?
Someone else may have some thoughts/ideas for your situation.
I have not been able to overcome the long time to boot issue, but I have been a challenger and tried updating to macOS 12.3. I updated with OpenCore 0.7.7 (OCLP 0.4.2). I felt basically fine after the update was completed. The behavior I am slightly concerned about is the occasional mild freeze state. That seems to be more likely to occur when Mission Control is activated.
So I made some modifications to OpenCore. First, I replaced it with OpenCore 0.7.9. Next I picked up the kext files from OCLP 0.4.3 and put them into OC's Kexts folder. I have a mix of OpenCore 0.7.9 and OCLP 0.4.2 and 0.4.3. (I can't boot my Mac with OCLP 0.4.3 for some reason.) After that, the behavior feels much better, but there are still some small freezes.
Is this freezing phenomenon an effect of the OS optimization work being done behind the scenes? I'm hopeful that over time this will resolve itself.
So I made some modifications to OpenCore. First, I replaced it with OpenCore 0.7.9. Next I picked up the kext files from OCLP 0.4.3 and put them into OC's Kexts folder. I have a mix of OpenCore 0.7.9 and OCLP 0.4.2 and 0.4.3. (I can't boot my Mac with OCLP 0.4.3 for some reason.) After that, the behavior feels much better, but there are still some small freezes.
Is this freezing phenomenon an effect of the OS optimization work being done behind the scenes? I'm hopeful that over time this will resolve itself.
I am running 12.3 with Martin Lo's package and have no issues whatsoever with Universal Control. Haven't used it that much, but was able to share KB/M with my M1 MBP and vice versa.
I did upgrade my WiFi/BT on Monday and had no issues besides having to relog into iCloud to get my Handoff working. Once that was working correctly, UC worked once updating to 12.3
EDIT: I did have to reboot on all my devices after updating
Last edited:
Separate question here: Hey all. I want to do a new install of Windows 10, but this time using UEFI vs the current Legacy setup. I figured it would be easier but it seems like the only way to do it is by tweaking the installer as stated in the 1st post. Is that right? I am running Martin's package on 12.3
It seems that people were doing it previously through creating a USB installer but that may not work anymore.
It seems that people were doing it previously through creating a USB installer but that may not work anymore.
That's why you should not rely on a pre-built solution and create your own, which is quite easy to learn. A clean config will make your Mac run smooth. I never had a single issue during the last 3 years I'm using OpenCore with my configuration, which is identical to OP config @cdf suggested.
I actually worked with him for a small period of time to test things and build that config and also builded the Plistlib Generator to allow other users easily upgrade their OC setup. My product is built based on Acidanthera philosophy and is considered a learning tool.
Last edited:
I would start fresh with a clean config, nothing is freezing on my Mac. What happens if OCLP or any other tool out there is not updated for a long period of time? You will be forced to do what many avoid it deliberately, learn to configure properly your OC.
This guy @cdf spent an insane amount of time testing things and building that guide, hoping that people put the effort to learn things, because OC is so easy to learn and use.
What's the card model, does it matches my signature one? I only have a iPad mini, latest model. Not sure if is compatible for universal controller.
I'm using a Python library part of Plistlib Generator tool, to extract and move the .kext zip file contents into /Kexts directory. There is a hidden directory present into dortania repo
ASPP-Override-v1.0.1.zip file and I did not wanted to have it copied into /Kexts directory:
Code:
$ unzip ASPP-Override-v1.0.1.zip
Archive: ASPP-Override-v1.0.1.zip
creating: ASPP-Override.kext/
inflating: __MACOSX/._ASPP-Override.kext
creating: ASPP-Override.kext/Contents/
inflating: ASPP-Override.kext/Contents/Info.plist
inflating: __MACOSX/ASPP-Override.kext/Contents/._Info.plistchmod 0644 the 1.0.1 Info.plist and zipped it clean. The version and release type (RELEASE or DEBUG) follow the Acidanthera naming convention, as some people like to use OC in DEBUG mode, for example. But the Info.plist contents are identical in both files.
Last edited:
Is your plan to install 10 on a separate drive? If so, the easiest way to do it is if you have a 2nd computer, put that drive in the 2nd computer, start the setup and when it goes to do the first reboot, shut it down, put the drive back in your Mac, select it from the OC boot screen (where it will now show up) and continue the installation. That will give you an EFI install of Windows 10 (assuming your temp PC is also EFI) that will work properly with OC.
As @TECK alluded to, this setup is going to cause you more headaches than any tangible benefit.
- If you want to run the latest OC, your best bet is to follow the guide and use an optimized .plist file, asking questions here when necessary.
- If you want to run OCLP, start fresh and just install it and use it how it is packaged/tested.
Thanks for the response! Yep, I have a separate SSD I that I'll be installing Windows 10 to so this should work perfectly. Thanks so much!
Updated both my cMP to 12.3 tonight. The Workstation went off without a hitch with the power management bypass kext loaded. The Media Server was another story. Went into an endless boot loop at one of the install reboots. It was my own fault, however. I shut the thing down and pulled the USB with the EFI and upon examining the config noted that the bypass kext wasn't enabled. Upon enabling and rebooting the install progressed to completion.
Testament to two conclusions: (a) double-check your work to ensure you've crossed every T, and dotted every i; and (b) put the EFI on a USB, because it makes checking for errors a lot easier and less intrusive when you're stuck in an install boot-loop time-warp.
Testament to two conclusions: (a) double-check your work to ensure you've crossed every T, and dotted every i; and (b) put the EFI on a USB, because it makes checking for errors a lot easier and less intrusive when you're stuck in an install boot-loop time-warp.
Well i hard reset my iPad mini and Universal Control works with my cMP5,1 - really nice feature though a bit strange between a 27" Apple Cinema Display and a 8" iPad mini.
Interested to see if it will work with my work MacBook Pro when it gets updated to Monterey (and I am using a VPN). That would really be nice - one mouse and keyboard for both when working at home.