Oh right.
I'll try that.
As I said I think OC is working as I can see the option to upgrade to Big Sur. Just no OC boot picker.
Would the GPU BIOS switch (factory or Mac Flashed) make a difference to seeing the OC boot picker?
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 Activate AMD hardware acceleration
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I'll try that.
As I said I think OC is working as I can see the option to upgrade to Big Sur. Just no OC boot picker.
Would the GPU BIOS switch (factory or Mac Flashed) make a difference to seeing the OC boot picker?
Yeah the original one I can ok
But the OC one is now missing since re-installing OC.
Does the BIOS have an effect on the OC Boot picker?
hmmm... after loosing my Windows 10 boot option in the bootpicker menu I decided to just restore my winclone backup to the drive to see if that would fix any issues. It restores the image just fine but it just won't show in the bootpicker and it won't let me boot from it in the 'Startup Disk' systems preferences menu on Catalina... (when I try that I get "the bless tool was unable to select the current boot disk")
I don't quite know what my next course of action should be.
I don't quite know what my next course of action should be.
Last edited:
take care if it's an uefi installation not to boot without OpenCore protection. At least make a backup of your boot rom if you have none.
I made a tool to dump the boot rom and run the most basic checks. S.I.P. must be disabled for the needed kext.
Dropbox - File Deleted - Simplify your life
I don't know what that means? The EFI of the Windows drive (I mounted it using Clover Configurator) is empty.take care if it's an uefi installation not to boot without OpenCore protection. At least make a backup of your boot rom if you have none.
I made a tool to dump the boot rom and run the most basic checks. S.I.P. must be disabled for the needed kext.
Dropbox - File Deleted - Simplify your life
www.dropbox.com
maybe that helps:
itsfoss.com
If you boot uefi Windows without OpenCore protection you will get Windows Certificates written in your Mac's boot rom. You can't get ridd of those certificates - what can botch your boot rom if other problems are in as well.
Getting away those certificates is easy if you have a firmware backup - just flash back. If you have no backup you will need someone who can rebuilt your firmware.
So everyone should have a backup. My tool makes one plus check for certificates (and other data points what can indicate an unhealthy boot rom).
Check if Computer Uses UEFI or Legacy BIOS [Linux & Windows]
A quick tutorial to tell you if your system uses the modern UEFI or the legacy BIOS. Instructions for both Windows and Linux have been provided.
itsfoss.com
If you boot uefi Windows without OpenCore protection you will get Windows Certificates written in your Mac's boot rom. You can't get ridd of those certificates - what can botch your boot rom if other problems are in as well.
Getting away those certificates is easy if you have a firmware backup - just flash back. If you have no backup you will need someone who can rebuilt your firmware.
So everyone should have a backup. My tool makes one plus check for certificates (and other data points what can indicate an unhealthy boot rom).
I am still trying to figure out how I can get the current Windows 10 drive to boot without having to reinstall the whole thing...
I am able to access it fine through Parallels as a 'Boot Camp' VM. Everything is still there the way I left it.
Thats not correct, the Mac Pro can easily boot Uefi Windows 10 and so easily get botched with Windows certificates.
I did not know that. I have never booted into Windows 10 without OpenCore though... so just for the slight chance that what you describe might be the case: How would I go about checking for these certificates?
Yes. That's what I said originally. The apple BP works fine.
BUT the problem is the OC one has stopped working since I re-installed OC on my start-up disk. BUT I can still see the option to upgrade to Big Sur in system preferences.
SO what's going on with Open Core?
It´s a nasty problem. Look in this thread.
MP5,1: BootROM thread | 144.0.0.0.0
For MacPro5,1 BootROM upgrades, please read the first post of the thread below to know how to do the firmware upgrade: https://forums.macrumors.com/threads/mp5-1-what-you-have-to-do-to-upgrade-to-mojave-bootrom-upgrade-instructions-thread.2142418/ For MP4,1 to MP5,1 cross firmware flashing...
forums.macrumors.com
It’s really hard to tell what’s wrong, I recommend you download the latest package in post #1314, and completely re-install OC.
Thank you. I have checked that thread and I have also checked my Windows 10 install (through Parallels) and it’s in Legacy mode. So I’m not sure if a busted ROM is my problem. I will download the tools from that thread and try a ROM dump to check.It´s a nasty problem. Look in this thread.
MP5,1: BootROM thread | 144.0.0.0.0
For MacPro5,1 BootROM upgrades, please read the first post of the thread below to know how to do the firmware upgrade: https://forums.macrumors.com/threads/mp5-1-what-you-have-to-do-to-upgrade-to-mojave-bootrom-upgrade-instructions-thread.2142418/ For MP4,1 to MP5,1 cross firmware flashing...
meanwhile I am noticing I know get this message after waking the Mac from sleep (only from the Catalina drive; which is the MVMe)
EDIT: Thank you all thus far. I will move this topic now to the Boot ROM thread so this thread can stay on-topic. My apologies.
Last edited:
I can tell you that I CAN´T boot my SSD SATA Windows 10 from internal SATA port. Have to do ir through an ESATA, don´t know why.
internal SATA = Mac Pro drive bay? Aren't drive bays set to IDE when booted using Boot Camp legacy BIOS boot?
Mac Pro can't boot ESATA unless you're doing UEFI boot. UEFI boot sets internal drive bays to AHCI.
