I also updated the plist generator, see https://github.com/axivo/opencore/pull/20.
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
Guys I’m having a weird behaviour on my OpenCore instance. The wire keyboard is non responsive when I’m in the stock boot menu (text). I can’t get it to go into any of the items. This happened on the subsequent boot ups post OC installation, not the first. Very weird. I’ve tried it with Windows and Mac (vintage) wired keyboards to no avail. Kind of stuck...
Last edited:
When we turn on the VMM flag, we want to change one bit in the CPU ID and leave everything else the same. So Cpuid1Mask is the "masking tape" and Cpuid1Data is the "paint."
Hmm, the analogy makes sense, however with that info, I'm now curious as to why I was told to (on a MacPro5,1) run with the following on normal operation (and with Mask with the 8 in place for VMM):
Cpuid1Data: 00000000 00000000 00000080 00000000
Cpuid1Mask: 00000000 00000000 00000000 00000000
It seems as though both should be all 0s for normal operation, no?
I personally will treat that as
1) keep the Cpuid1Data modified, so that VMM flag is ready to be toggled.
2) Use Cpuid1Mask as the true switch to turn this function on/off.
As long as the switch is off, it doesn't matter what's behind it.
Hello On my CMP 4,1 flashed to a 5,1. When I install the 30 inch Cinema Display on the dvi port on my rx 580 the Resolutions are normal can go up to 2560x1600 when I plug in to the the disport or hdmi port using adaptor to dvi I can only go up to can go up 1280x800 resolution on my 30 inch Cinema Display and the card has been flashed by macvideo cards
I have upgraded to Beta 8 and tried to disable root-auth but the recovery terminal returned > failed setting csr-active-config. I have no idea as to why it does this. Any idea?
Yes - I did the day after it's release. I had to toggle on VMM in OpenCore 0.6.1 and as my Catalina was initially installed via dosdude1's patcher I set SecureBootModel to "Disabled".
anyone is having problems updating big sur from public beta 3 to public beta 4? I mean if I go to check for updates It tells me that I am already up to date. I have already tried to unenroll and re enroll but it’s the same.
I have also clearly Enable VMM flag.
I am on OC 0.6.1 updated by starting from the “clean” config plist on first page and re-applied the suggested various fixes section for HWA, NVME Orange icons fix.
Last thing if can help... in Catalina I have just updated to 10.15.7 with the same OC config without problems.
I’ll attach my actual config in a while.
Thank you by now for anyone who can help me.
Cheers
I have also clearly Enable VMM flag.
I am on OC 0.6.1 updated by starting from the “clean” config plist on first page and re-applied the suggested various fixes section for HWA, NVME Orange icons fix.
Last thing if can help... in Catalina I have just updated to 10.15.7 with the same OC config without problems.
I’ll attach my actual config in a while.
Thank you by now for anyone who can help me.
Cheers
For Big Sur installation / update, so far, the most reliable way is to completely spoof the cMP into an iMac Pro. The code is in post #7.
Caution: you better sign out your Apple ID before you do that. I am sure quite a few cMP users use that code to install Big Sur already without changing the serial number. Even though there is no user report any issue yet. You still better avoid your Apple ID has any relationship to that "popular serial number". Of course, you can use something like Clover configurator to generate an unique serial number for self use.
I have just followed what you said, I have modified the smbios part according to your post #7 and let cloverconfigurator create a “unique random” serial for an iMac Pro 1.1. The update appeared immediately. The only downside is that I had to connect an hdmi cable to the monitor instead of the DP connector at first boot after the config mods to correctly boot and seen the desktop.
After the update I’ll copy my previous config.plist backup.
EDIT: your posts and helps are always clear and helpful. Thank you
Last edited:
Ok, just installed beta 8 update... now... I have read on previous posts that on beta 7-8 something is changed and we have two (three?) roads for Big Sur to correctly boot:
A: set VMM always ON (like I'm doing in this moment)
B: completely spoofing iMac Pro 1,1 SMBIOS
C: set Secureboot to "Default" on unmodified installation.
now (always if I understood correctly) if I goes to route:
A: we lost something about performance and ACPM.
B: In my case I can't use DP port connections for display but only HDMI
C: i have tried to set Default entry since I don't have used any Big Sur modified installation script but it doesn't boot (maybe I don't understand what "unmodified installation" means).
At this point... what is the best thing to do? I clearly know that attempting to install Big Sur on our 5.1 machines is a risk... is this problem due to apple brick something in the latest build or is to be expected this behaviour since we are "near" to GM?
thank you
Hi there,
I install OC/Catalina on my MP 5,1 , just want the BOOT SCREEN with my GTX Titan Black.
I completed the installation with my old 5770 GPU(basic bootpicker/graphic bootpicker works fine)
after that I change to GTX Titan Black GPU, it work just like no OC installed (wont show bootpicker, just black screen -> Catalina login), but i check install again, OC installed. any idea why bootpicker dont show up?
I install OC/Catalina on my MP 5,1 , just want the BOOT SCREEN with my GTX Titan Black.
I completed the installation with my old 5770 GPU(basic bootpicker/graphic bootpicker works fine)
after that I change to GTX Titan Black GPU, it work just like no OC installed (wont show bootpicker, just black screen -> Catalina login), but i check install again, OC installed. any idea why bootpicker dont show up?
It kind of does not work for NVIDIA. Can you please use the debug version for logging?
File Swaps
To start, make sure you're using either the DEBUG or NOOPT versions of OpenCore. This will provide much more info than the RELEASE version, the specific files that need to be swapped:
- EFI/BOOT/
- BOOTx64.efi
- EFI/OC/Bootstrap/
- Bootstrap.efi
- EFI/OC/Drivers/
- OpenRuntime.efi
- OpenCanopy.efi(if you're using it)
- EFI/OC/
- OpenCore.efi
Misc
Here we'll want to enable the following:
- AppleDebug: YES
- Provides much more debugging information, specifically relating to boot.efi and will also store the log to disk.
- ApplePanic: YES
- This will allow kernel panics to be stored to disk, highly recommend keeping keepsyms=1 in boot-args to preserve as much info as possible.
- DisableWatchdog: YES
- Disables the UEFI watchdog, used for when OpenCore is stalling on something non-critical.
- Target: 65 (disregard 67 in the picture below)
- DisplayLevel: 2147483714
Last edited:
hi, thx for reply.
DEBUG version now, and config.plish edited. how can i start logging or where can i
find the log file?