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
The kext is included but is disabled by default. Find the dictionary entry for the kext and below <key>Enabled</key> replace <false/> by <true/>.
Hello All,
During all the excitement with OC 7.4 and the Sur Patch etc, I managed to delete my boot config file for a WINDOWS GPT SSD Hard Disk, installed via BOOTCAMP this was working fine prior. The result, OC 7.5 doesn't see the Windows Hard Drive, even when I hold down the option key at boot. Interestingly, Monterey show the HD in the startup menu, but returns an error if I try to select it.
"An error occurred while setting “BOOTCAMP” as the startup disk: The operation couldn’t be completed. (SDErrorDomain error 104.)"
Is there a way to have OPENCORE re-locate the boot partition for the WIN HD?
TIA
During all the excitement with OC 7.4 and the Sur Patch etc, I managed to delete my boot config file for a WINDOWS GPT SSD Hard Disk, installed via BOOTCAMP this was working fine prior. The result, OC 7.5 doesn't see the Windows Hard Drive, even when I hold down the option key at boot. Interestingly, Monterey show the HD in the startup menu, but returns an error if I try to select it.
"An error occurred while setting “BOOTCAMP” as the startup disk: The operation couldn’t be completed. (SDErrorDomain error 104.)"
Is there a way to have OPENCORE re-locate the boot partition for the WIN HD?
TIA
If I'm not mistaken, Windows 10 can be either Legacy (Boot Camp) or UEFI. A Legacy Windows 10 can be 32-bit or 64-bit. A UEFI version of Windows 10 can only be 64-bit, if I'm not mistaken. Windows 11 can only be UEFI (and 64-bit). You can boot a Legacy version of Windows using Apple's native Startup Disk Manager (for instance, selecting your Boot Camp volume when you press Alt at startup). OpenCore, on the other hand, can't boot a Legacy version of Windows; only a UEFI one.
If your Windows installation was somehow damaged and you don't have a backup, you'll need to reinstall Windows. A Legacy install of Windows requires a pure MBR partition or a hybrid GPT+MBR partition, not a pure GPT (GUID) partition. A UEFI install of Windows requires a pure GPT partition. If your partition table hasn't been altered, you can simply use a Windows installer (for instance, a bootable USB pen drive with your operating system) and simply install on top of whatever you have. It will probably repair any inconsistencies and you'll have a functional Windows.
Unless you are trying to migrate from 32 bits to 64 bits, which is next to impossible, you should even be able to convert a moderately faulty Legacy Windows to its UEFI counterpart.
One word of advice on Windows backups. I use Winclone, which is very efficient. On a Mac Pro 5,1 fully updated to Monterey and UEFI Windows 11, however, restores may pose a big problem, because the last part of the restore process tries to make sure the restored disk can boot as Apple developers thought Windows should behave ten years ago on this particular machine. In other words, unless I'm mistaken, it will always try to leave Windows in a "nice" Legacy condition, thereby destroying its bootability, both natively and through OpenCore. So, my advice for a successful restore is NOT to let Winclone carry out its last Legacy step, unless you have a Legacy Windows 10.
If your Windows installation was somehow damaged and you don't have a backup, you'll need to reinstall Windows. A Legacy install of Windows requires a pure MBR partition or a hybrid GPT+MBR partition, not a pure GPT (GUID) partition. A UEFI install of Windows requires a pure GPT partition. If your partition table hasn't been altered, you can simply use a Windows installer (for instance, a bootable USB pen drive with your operating system) and simply install on top of whatever you have. It will probably repair any inconsistencies and you'll have a functional Windows.
Unless you are trying to migrate from 32 bits to 64 bits, which is next to impossible, you should even be able to convert a moderately faulty Legacy Windows to its UEFI counterpart.
One word of advice on Windows backups. I use Winclone, which is very efficient. On a Mac Pro 5,1 fully updated to Monterey and UEFI Windows 11, however, restores may pose a big problem, because the last part of the restore process tries to make sure the restored disk can boot as Apple developers thought Windows should behave ten years ago on this particular machine. In other words, unless I'm mistaken, it will always try to leave Windows in a "nice" Legacy condition, thereby destroying its bootability, both natively and through OpenCore. So, my advice for a successful restore is NOT to let Winclone carry out its last Legacy step, unless you have a Legacy Windows 10.
Last edited:
you can chainload rEFInd from OpenCore what can load legacy Bios
or vice versa you can try Dayo's Bootloader variant what can load Legacy Windows and chainload OpenCore.
MyBootMgr: RefindPlus|OpenCore
section and follow the steps one after the otherThis is a guide to using OpenCore and RefindPlus, to multiboot Classic MacPros (3,1 to 5,1) as well as equivalent Xserve (2,1 and 3,1). It involves booting Mac OS from one or more OpenCore instances chain-loaded from RefindPlus and booting other OS...
forums.macrumors.com
Guys I have a problem (that hopefully can be fixed). I have a 5,1 I manage to install Opencore .62 back sometime this year and was able to install Big Sur was able to update to 11.1 but that was it. When new updates came out they never showed up on my Software Update panel. BUT today I updated Opencore (per the video instructions on how to use Clover Configurator) I restarted and at a blank screen. If I hit certain keys I can hear clicking but nothing else. System has a RX580 (Sapphire) and its hooked up to 27" LED Apple monitor. I removed the NVME drives (Sonnet card) and was able to temporarily boot up to my old Mojave.
I am at a loss how to fix this, the data is there on the drive, however there is a new "partition" titled UPDATE, which I never saw before.
Also, my EFI folder does not contain an Apple folder as I see most videos showing how to install/update Opencore have it in addition to the BOOT and OC (sorry dont remember the files on there)
Any ideas where to start?
I am at a loss how to fix this, the data is there on the drive, however there is a new "partition" titled UPDATE, which I never saw before.
Also, my EFI folder does not contain an Apple folder as I see most videos showing how to install/update Opencore have it in addition to the BOOT and OC (sorry dont remember the files on there)
Any ideas where to start?
Fiddling around with partitions etc. can easily and often make the Windows partition 'disappear', in fact it is just because the hybrid MBR setting which it needs has got changed.
Follow the gdisk instructions from here https://macriot.com/mcrt/2014/12/08...-selected-disk-is-of-the-gpt-partition-style/ . Just the sequence of commands within gdisk is fine, none of the rest of it, no other unplugging disks etc. is needed. After exiting gdisk, reboot.
Last edited:
Peter how can I prevent Winclone from carrying out its last Legacy step? I have repeatedly tried a test of restoring a winclone image of Windows 10 on my OpenCore Mac Pro 5,1 and it is not bootable, even after I try converting it to UEFI. You may have provided the reason why I have not been successful since converting the Windows 10 to UEFI and running it under OpenCore.
Last edited:
What I did, after much trial and error, is, besides keeping it from ever altering the boot configuration data (BCD) on restore, is to stop the restore process as soon as the "Updating Legacy" message is displayed after copying the image data to the disk (when the Windows disk is mounted again). Admittedly, this forces you to be close to your Mac before the BCD becomes a mess, but it has worked for me two times. If I were to let it finish normally ("successfully" in theory), I would end up with a non-booting Windows. Again, Winclone does this because that's precisely what it is supposed to do... for Legacy Windows, which, in theory, is the only flavor that is supposed to run on a Mac Pro 5,1. That could always be a possibility with a 32- or 64-bit Legacy (Boot Camp) Windows 10, but it's a nonstarter for (UEFI 64-bit) Windows 11.
A possible alternative may be to let the process finish normally and then undo the hybrid MBR conversion using gdisk as proposed in post #9,725.
Thank you so much. I'm using Mac and Windows with OpenCore in Mac Pro Mid 2010.
Hi there.
I've experienced the same exact issue with both my Mac Pro 4.1 -> 5.1 and my Mac mini 2012 running Big Sur 11.6.1.
I'm not using HandBrake and only could trace the problem back to Safari 15.1 and/or WhatsApp Desktop. Are you using WhatsApp Desktop or any other messaging app?
Not "strictly" an OpenCore query I guess, but any ideas welcome. Successfully updated my 2010 5,1 to Catalina in order to run the latest Adobe apps. All good, they updated fine. Hardware acceleration enabled on the Radeon RX 580 8 GB.
Photoshop (previous and latest version) is now complaining that OpenCL is unavailable and I need a driver update (not possible on Mac?).
Adobe lists supported cards as Metal compatible with 2GB of RAM, so the card itself should be fine.
I'm going to try turning off hardware acceleration, but wondered if anyone else had come across this?
UPDATE: Adobe recommends updating to Big Sur, oh well, may as well give it a go!
"OpenCL data on macOS 10.15.7 can become corrupted causing errors in applications that depend on OpenCL to enhance features. This issue is fixed in macOS 11.3."
I think Adobe have disabled it themselves in Photoshop running on Catalina as the option is greyed out in preferences.
Photoshop (previous and latest version) is now complaining that OpenCL is unavailable and I need a driver update (not possible on Mac?).
Adobe lists supported cards as Metal compatible with 2GB of RAM, so the card itself should be fine.
I'm going to try turning off hardware acceleration, but wondered if anyone else had come across this?
UPDATE: Adobe recommends updating to Big Sur, oh well, may as well give it a go!
"OpenCL data on macOS 10.15.7 can become corrupted causing errors in applications that depend on OpenCL to enhance features. This issue is fixed in macOS 11.3."
I think Adobe have disabled it themselves in Photoshop running on Catalina as the option is greyed out in preferences.
Another query, sorry! I am following the instructions to create a rescue CD and getting the following error in Terminal.
hdiutil create -size 200MiB -srcfolder OC-CD -format UDTO -fs FAT32 OC-CD.iso
.....could not access /Volumes/OC-CD/EFI/OC/config.plist - Invalid argument
The OC-CD folder is in my home folder, and an ISO/DMG icon temporarily appears while running the command before disappearing and the above error showing in Terminal.
hdiutil create -size 200MiB -srcfolder OC-CD -format UDTO -fs FAT32 OC-CD.iso
.....could not access /Volumes/OC-CD/EFI/OC/config.plist - Invalid argument
The OC-CD folder is in my home folder, and an ISO/DMG icon temporarily appears while running the command before disappearing and the above error showing in Terminal.
Make sure you COPY your config.plist to the desktop for editing and then COPY it back. I had a similar issue from editing it in the OC-CD folder. Follow the instructions in the first post to the letter and it should work.
All sorted this time, copying with cmd-c rather than alt-dragging did the trick, although maybe I just edited the plist in the wrong place last time. Thanks for the tip.
I had the exact same problem and @cdf clued me into copy and paste to the desktop and updated the instructions in Post #1 because of it.
Hello all, I have used the opencore / plist of martin 'lo and until this version 0.7.5, it could no longer boot, I am using a highpoint 7101 without RAID, I repeated the installation from scratch using an SSD and it works perfectly, any idea why detects the highpoint as external ?, while in version 11.2.3 it works correctly.
Has anyone seen this error before? This occurred yesterday while trying to bless OC 7.5 after doing a little editing on the config.plist file for my legacy wifi card. Changed two values, saved... and this came up. Machine wouldn't boot - had to roll back to a previous SSD. As a curious aside, the drive wouldn't bless in ANOTHER Mac Pro 5,1 - similar config, even AFTER rolling back to previous Config.plist file. Going to end up reformatting that drive, cloning a known good startup - but wow what a lost afternoon! <bleh>.
OC 7.5 Titan Ridge Yes SSDT version - Mac 5,1 - Big Sur - 12 cores, 96 gigs, all drive sleds removed but startup, all external drives shut down.
OC 7.5 Titan Ridge Yes SSDT version - Mac 5,1 - Big Sur - 12 cores, 96 gigs, all drive sleds removed but startup, all external drives shut down.
Greetings, recently I used Martin Lo's OC package to upgrade my cMP 4,1-->5,1 to Monterey successfully. I also wanted to add a Windows 10 install to the mix. I partitioned (GUID) a 4TB drive into 2 parts--a partition for Windows 10 (ExFat/GUID partition) and a Mac partition. Following directions on the thread "OpenCore on the Mac Pro", I formatted a USB installer, formatted the Window's partition, installed the ExFat driver, booted the installer with ProtectSecure Boot=true and VMM flag disabled. I then reformatted the Windows partition and proceeded with the installation. Then prepared the Windows EFI all successfully. Ejected the drive and rebooted, then selected the Window's boot option via the OC picker.
And then .... screen turns black with a slight background lighting--i.e the monitor is on but there is nothing being displayed.....leave for 30 mins with no change...
Eventually get dismayed and rebooted the cheesegrater again, picking the Monterey option--and that boots successful. I have also reset NVRAM a few times, again with no change in circumstances.
I've spent most of the day looking for anything that sounds even remotely like this on the web but to no avail. I have read post after post of this working. So I know it works, although it sounds like it may be a bit unstable.
Can anyone offer any thoughts/recommendations to get Windows 10 up and running and overcome this "slightly" black screen of death I am facing? Or has someone recently faced the same issue and was able to overcome?
thanks everyone in advance!
And then .... screen turns black with a slight background lighting--i.e the monitor is on but there is nothing being displayed.....leave for 30 mins with no change...
Eventually get dismayed and rebooted the cheesegrater again, picking the Monterey option--and that boots successful. I have also reset NVRAM a few times, again with no change in circumstances.
I've spent most of the day looking for anything that sounds even remotely like this on the web but to no avail. I have read post after post of this working. So I know it works, although it sounds like it may be a bit unstable.
Can anyone offer any thoughts/recommendations to get Windows 10 up and running and overcome this "slightly" black screen of death I am facing? Or has someone recently faced the same issue and was able to overcome?
thanks everyone in advance!