You will get updates. They will appear below the BS "Upgrade Now" message. Just follow instructions in PART III Maintenance in the Wiki.
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
You will get updates. They will appear below the BS "Upgrade Now" message. Just follow instructions in PART III Maintenance in the Wiki.
not sure what’s happened, but I’ve removed config for lilo and weg as here, now I get a flashing power light on boot, have tried removing all drives, down to 2 ram sticks smc reset etc, still nothing
is this the feared corrupted bootrom?
When you press the DIAG Button on the backplane, EFI_DONE is off? If so, yes, your SPI flash memory is corrupted/dead.
Hello everyone. I'm running a 5,1 and successfully installed OC to move to Catalina with everything working fine. No issues. I recently upgraded to Big Sur with the typical software update and everything installed fine and appears to be running ok, except 1 thing: My USB Keyboard and USB Mouse are acting strange.
My Mouse plugged into any USB 2.0 port on my tower is recognized in the bootloader and after logging into Big Sur BUT if I unplug it after logging in, and plug it back in, the computer won't recognize it, but it is powered.
My Keyboard plugged into any USB 2.0 port on my tower is recognized in the bootloader BUT after loading into Big Sur it isn't recognized and I can't enter my password. The caps lock and function LEDs flash but then go out and no input works.
Luckily if I plug them into a USB 2.0 hub attached to my USB 3.1 card, they are both recognized and swappable.
I've tested flash drives in every 2.0 port and they are recognized and swappable, so I'm really not sure why this is an issue with my mouse and particularly my keyboard.
Any ideas what may be the issue? I've searched the site and this appears to be a unique problem. I appreciate any feedback, thanks so much.
My Mouse plugged into any USB 2.0 port on my tower is recognized in the bootloader and after logging into Big Sur BUT if I unplug it after logging in, and plug it back in, the computer won't recognize it, but it is powered.
My Keyboard plugged into any USB 2.0 port on my tower is recognized in the bootloader BUT after loading into Big Sur it isn't recognized and I can't enter my password. The caps lock and function LEDs flash but then go out and no input works.
Luckily if I plug them into a USB 2.0 hub attached to my USB 3.1 card, they are both recognized and swappable.
I've tested flash drives in every 2.0 port and they are recognized and swappable, so I'm really not sure why this is an issue with my mouse and particularly my keyboard.
Any ideas what may be the issue? I've searched the site and this appears to be a unique problem. I appreciate any feedback, thanks so much.
Yep looks like it’s that then, I do have a backup of my boot rom from a week or so ago, so I don’t pollute this thread further can I PM you about recovery options?
I wrote earlier today about what you can do in this exact situation, read here.
There is nothing else you can do besides that three options I wrote, at least you have a saved dump and won't need to spend money on a very time consume reconstruction based solely on the ESN and MLB labels and dumps from the same HWC.
If you have any doubts, please ask there, since will be helpful to others too.
Last edited:
Something similar happens to me with a USB MIDI Controller, the system only recognizes it if I connect it to the apple keyboard port, I don't know if it will be an OC or Big Sur problem.
Something similar happens to me with a USB MIDI Controller, the system only recognizes it if I connect it to the apple keyboard port, I don't know if it will be an OC or Big Sur problem.
I have same an issue. It is a bug in big sur. I think usblegacy is broken
You gave me an idea I hadn't yet tested... I plugged my usb 3 hub with my mouse and keyboard into the usb 2 ports that aren't working with them individually, and they work. So I'll probably just get another cheap hub as a workaround... thanks!
Cool thanks, good to know I'm not the only one with this issue! If I find a solution, I'll keep you updated.
Hi cdf/h9826890
Newbie here, trying to install OpenCore on my 4,1-5,1 cmp (running Mojave on nvme ssd and MSI RX580), I'll appreciate if you can clarify couple of questions:
1) Do I need to disable SIP for OpenCore install? That is the first step in the instructions from h9826890 (https://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/post-28255048) but is not mentioned in the guide (Post 1)
2) What I need is the vanilla opencore, just to be able to use Catalina/Big Sur and don't need any of the advanced features and Config file from 1st post should be enough. However I am tempted to use h9826890's method as it looks much easier in the video he provided. Can I use the Clover and Bless tool from h9826890 to be able to install and bless the vanilla config file from the first post or h9826890's bless tool is only designed to be used with his config file?
3) Will I need "boot-args="-no_compat_check" to use Catalina or Big Sur with OpenCore?
Thanks
Newbie here, trying to install OpenCore on my 4,1-5,1 cmp (running Mojave on nvme ssd and MSI RX580), I'll appreciate if you can clarify couple of questions:
1) Do I need to disable SIP for OpenCore install? That is the first step in the instructions from h9826890 (https://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/post-28255048) but is not mentioned in the guide (Post 1)
2) What I need is the vanilla opencore, just to be able to use Catalina/Big Sur and don't need any of the advanced features and Config file from 1st post should be enough. However I am tempted to use h9826890's method as it looks much easier in the video he provided. Can I use the Clover and Bless tool from h9826890 to be able to install and bless the vanilla config file from the first post or h9826890's bless tool is only designed to be used with his config file?
3) Will I need "boot-args="-no_compat_check" to use Catalina or Big Sur with OpenCore?
Thanks
Last edited:
1) the instruction in post #1 bless OpenCore in recovery partition, therefore, no need to change SIP status.
My approach is to keep it as simple as possible, but the users themselves need to know where those OC files stored. Therefore, my instructions ask the users to mount the EFI, copy the files, and run the bless tool (which required SID disabled)
2) If you want vanilla OpenCore, better go for the approach in post #1 here. Mix use different methods usually require better knowledge than average.
Of course, if you 100% sure your own config is correct, then you can download my package, remove all unnecessary kext / tool / etc, change the config.plist to your own config, then use my way to install OpenCore.
3) After you build your own config, you should know the answer. The short answer is yes, just a matter of where we put this argument in.
Just updated to the latest Mojave security patch on my 4,1 > 5,1. After the update I got a notification telling me to "learn more about my new imac pro". My system identifier is still macpro5,1 and I have never used the VMM flag. Should I be worried?
It’s the board ID injection causing it. IMO, no need to worry about that.
Ok got it. Not that it bothers me, but another I noticed that under the "about this mac" support section, the regulatory certification is also the one for the iMac pro. Just a weird thing I noticed.
Note that this does not work for Big Sur on a cMP 4,1->5,1: When I do remove the lines as suggested, I cannot boot anymore (receiving the circle with the strike-through bar after selecting the boot drive). When I add these 3 lines back to where they were, I can boot again.
I would propose to add this to the wiki-fied first entry.
Thank you @contributors for making the upgrade of cMPs to Big Sur possible in the first place!
Bootable volume renaming issue
I apologize if this has been addressed before, but I've been unable to locate the specific instruction to rename an EFI volume. As soon as it was released, I installed Big Sur on top of a secondary disk that used to have a vanilla version of Catalina, and the disk name or label was Catalina. After successfully upgrading it to Big Sur, I changed its name to "Big Sur", and that's the way the disk appears when Apple's Startup Manager kicks in. However, if I choose Boot EFI as the the startup disk (when I press Option at the chime), the Boot Picker displays that Big Sur disk as "Catalina". How can I remedy this?
I apologize if this has been addressed before, but I've been unable to locate the specific instruction to rename an EFI volume. As soon as it was released, I installed Big Sur on top of a secondary disk that used to have a vanilla version of Catalina, and the disk name or label was Catalina. After successfully upgrading it to Big Sur, I changed its name to "Big Sur", and that's the way the disk appears when Apple's Startup Manager kicks in. However, if I choose Boot EFI as the the startup disk (when I press Option at the chime), the Boot Picker displays that Big Sur disk as "Catalina". How can I remedy this?
Thanks for the reply. I am not a mac expert and will not make any changes to config file on my own without your guidance. I wish I was also knowledgeable and confident like you all.
For disk labeling OC provides its own program called disklabel:
Copy and paste that to your Bootx64.efi folder:
cd to the folder in terminal and run:
Code:
g5@G5s-Mac-Pro-2 BOOT % /Volumes/EFI/EFI/BOOT/disklabel
Usage:
disklabel -d .disk_label image.ppm!
disklabel -e "Label" .disk_label .disk_label_2x
disklabel -bgra "Label" .disk_label .disk_label_2x disklabel -e "OpenCore" .disk_label .disk_label_2x
Last edited:
in Big Sur If I disconnect my USB keyboard from the USB 2 port it will not reinitialize on a USB 2 port, only through my 3,1 Anker USB hub connected to a USB 2 port or directly to my USB 3.2 PCIE card.
yes I tried to plug usb flash drive 3.0 and it recognized. I think only issue is with usb 2.0 1.1