Just to confirm, you're using rEFInd to boot W10 EFI so it can successfully do upgrade as using OC to boot W10 EFI will make the W10 update failed?Tinkered on with this over the weekend and I'm now using the chainloading technique described by @startergo earlier in this thread to fire up Windows in CSM / Legacy mode. I've got a basic-as-possible rEFInd installed on my Catalina EFI partition alongside OC using BlessOverride and HideSelf as false.
I couldn't get the described .contentDetails and .disk_label.contentDetails to adjust the name on the picker for the EFI partition, so I just renamed it to WINDOWS. Ends up looking like this:
It's worked perfectly through upgrades to Windows 10 v2004 and the adjusted parameters from OC are all carried through properly. I need to figure out how to work the Entries portion of my config.plist so I can point OC explicitly to rEFInd, but BlessOverride is more than good enough for now.
I'm really impressed at how well OpenCore works, full kudos to the developers. I couldn't have imagined it would be this seamless.
No, using rEFInd to boot Windows 10 in Legacy mode, not EFI mode. I trashed the UEFI installation.Just to confirm, you're using rEFInd to boot W10 EFI so it can successfully do upgrade as using OC to boot W10 EFI will make the W10 update failed?
No, using rEFInd to boot Windows 10 in Legacy mode, not EFI mode. I trashed the UEFI installation.
Yes if you can see the bootpicker you can use FileVault.With all this wonderful progress, can FileVault be turned on and used again with the new boot picker?
Big thanks to all who contributed @cdf, @h9826790, @startergo, @w1z and especially to @vit9696
I just booted into my cMP with Radeon VII, I have bootselector via OC, bootscreen, full HW acceleration and internal disc icons on Catalina 10.15.3
My EFI is attached below.
No more need for a Mac Pro 2019
View attachment 894152
That's intentional.Indeed thanks for everyone who contributed to this project!
One question to @rroumen:
I'm using your EFI and it works great as you described, but one thing I noticed in your config file is that the VMM flag is not enabled to allow Catalina updates ("Cpuid1Mask" is different than "Cpuid1Data").
Is that on purpose? will Catalina native updates work or do I need to change those values based on the first post (step 4)?
Thanks!
What’s the best way to test this under macOS? Because leaving the VMM flag present and booting into Windows it appears to ramp up and down as intended.Only turn on the VMM flag when you need to update Catalina. Otherwise, CPU power manager won't function correctly. e.g. Turbo Boost will be disabled, and CPU can't reduce clock speed (and power consumption) during idle.
IMO, the easiest way, open terminal and enterWhat’s the best way to test this under macOS? Because leaving the VMM flag present and booting into Windows it appears to ramp up and down as intended.
pmset -g thermlog
. This should only works when CPU power management is working properly.Using OC with APFSLoader driver did not work to display any apfs formatted partitions.I Can confirm that OC works on the Xserve3,1 using a HP AMD WX4150 in the MXM slot (replaced GT120) via the mDP.
Without OC there is zero display from the card at boot or in the OS (which doesn't support this GPU 10.11).
With OC 0.5.5 with the GOP setup there is display from the card for the boot picker, verbose boot, and in the OS in VESA mode.
So this is proof that a modern PC GPU can be used (unaccelerated) in older versions of macOS as I believe @h9826790 had theorized.
Working to update to a modern OS and see what does / doesn't work but figured I'd mention a bit of success publicly.
What is your firmware revision.Hi everyone, could I have a hand?
We've installed our Titan Ridge card with modified firmware. Added OpenCore and the Boot Drivers to the EFI folder however sometimes this Apple folder/file appear and it stops it working.
Mac Pro 5,1 / Mojave
Does anyone know why it does and how to prevent it?
Thank you!
What is your firmware revision.
In post #1, does Disk B have to be Mojave or can I use High Sierra?
Wireless keyboard?OK, I follow the instructions from post #1. I see the open core menu when reboot but I cannot select anything. When I press arrow keys on the keyboard, the selection arrow does not move at all. Then after 10 seconds, it automatically boots into Mojave. Anyone has any ideas ?
Path
Type: plist string
Failsafe: Empty string
Description: Entry location depending on entry type.
Entries specify external boot options, and therefore take device paths in Path key.
These values are not checked, thus be extremely careful.
Example: PciRoot(0x0)/Pci(0x1,0x1)/.../\EFI\COOL.EFI
HackintoolHi all,
I will like to add the path to an efi file on another volume in the "Entries" section of my config file and notice this part in the configuration docs that says:
Code:Path Type: plist string Failsafe: Empty string Description: Entry location depending on entry type. Entries specify external boot options, and therefore take device paths in Path key. These values are not checked, thus be extremely careful. Example: PciRoot(0x0)/Pci(0x1,0x1)/.../\EFI\COOL.EFI
I presume the device path to a volume is different from the usual "/Volumes/DriveName". Any hints on how to determine this?
Thanks. I had thought that tab only dealt with PCI slots ... How do I ID a specific volume?Hackintool