You need to have the correct path to config.plist
One way of doing it:
https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-29158723
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
One way of doing it:
https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-29158723
I have a question I have been using OpenCore with macOS Big Sur for some time now. So far everything works fine but I noticed that my Mac doesn't make any boot chime when starting. Does anybody have an idea what this is due to? In system preferences is the boot chime activated.
If there's nothing wrong with your machine,
the volume of the output device "Internal Speaker" of the last operating system you used
sets the volume of the next boot chime.
I have to try if booting OC with Cat or BS still set the volume of the boot chime...
/edit: indeed, still works while booting OC, no matter wich OS.
Last edited:
About the step of:
Bless the volume for booting by entering: bless --mount /Volumes/EFI --setBoot,
this command, in terminal, has never worked for me while I always had to use the following command:
bless —mount /Volumes/EFI setBoot —file /Volumes/EFI/EFI/BOOT/BOOTx64.efi —verbose
Any suggestion?
So to convert the hybrid MBR created by the Bootcamp assistant to a protective MBR (GPT in UEFI mode Apple style)
This is needed:
Code:
sudo gpt show /dev/disk10
gpt show: /dev/disk10: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 4 Pri GPT table
6 76800 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
76806 60058593 2 GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
60135399 25
60135424 57077248 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
117212672 209
117212881 4 Sec GPT table
117212885 1 Sec GPT header
g5@G5s-iMac-Pro ~ % sudo gdisk /dev/disk0
GPT fdisk (gdisk) version 1.0.5
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present
Found valid GPT with hybrid MBR; using GPT.
Command (? for help): p
Disk /dev/disk0: 117212886 sectors, 447.1 GiB
Sector size (logical): 4096 bytes
Disk identifier (GUID): 392E642E-FDC7-437F-A958-CBF575B16E7D
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 5
First usable sector is 6, last usable sector is 117212880
Partitions will be aligned on 2-sector boundaries
Total free space is 234 sectors (936.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 6 76805 300.0 MiB EF00 EFI system partition
2 76806 60135398 229.1 GiB AF0A Apple APFS
3 60135424 117212671 217.7 GiB 0700 Microsoft basic data
Command (? for help): x
Expert command (? for help): z
About to wipe out GPT on /dev/disk0. Proceed? (Y/N): y
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Warning: The kernel may continue to use old or deleted partitions.
You should reboot or remove the drive.
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.
Blank out MBR? (Y/N): y
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Command (? for help): x
Expert command (? for help): l
Enter the sector alignment value (1-65536, default = 2048): 1
Expert command (? for help): m
Command (? for help): n
Partition number (1-128, default 1): 1
First sector (6-117212880, default = 6) or {+-}size{KMGTP}: 6
Last sector (6-117212880, default = 117212880) or {+-}size{KMGTP}: 76805
Current type is AF00 (Apple HFS/HFS+)
Hex code or GUID (L to show codes, Enter = AF00): EF00
Changed type of partition to 'EFI system partition'
Command (? for help): n
Partition number (2-128, default 2): 2
First sector (76806-117212880, default = 76806) or {+-}size{KMGTP}: 76806
Last sector (76806-117212880, default = 117212880) or {+-}size{KMGTP}: 60135398
Current type is AF00 (Apple HFS/HFS+)
Hex code or GUID (L to show codes, Enter = AF00): AF0A
Changed type of partition to 'Apple APFS'
Command (? for help): n
Partition number (3-128, default 3): 3
First sector (60135399-117212880, default = 60135399) or {+-}size{KMGTP}: 60135424
Last sector (60135424-117212880, default = 117212880) or {+-}size{KMGTP}: 117212671
Current type is AF00 (Apple HFS/HFS+)
Hex code or GUID (L to show codes, Enter = AF00): 0700
Changed type of partition to 'Microsoft basic data'
Command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/disk0.
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Warning: The kernel may continue to use old or deleted partitions.
You should reboot or remove the drive.
The operation has completed successfully.
g5@G5s-iMac-Pro ~ % sudo gpt -r show /dev/disk0
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 76800 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
76806 60058593 2 GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
60135399 25
60135424 57077248 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
117212672 209
117212881 4 Sec GPT table
117212885 1 Sec GPT headerThank you so much that worked perfectly. I'm curious, someone told me that installing windows using a a USB could lead to some issues, and possibly bricking the system. Is there a way to complete the installer using DL DVD's ?
Currently running Catalina via OpenCore on my Mac5,1. I'm wondering what the easiest way to move to Big Sur safely would be?
Reinstall my original Mojave disk in Slot B, a new disk in Slot A, make the required changes to install Big Sur and then use the migration assistant?
Or clone my Catalina install to a new disk and use the software update option that currently shows an update to Big Sur? This would probably save me a lot of work replicating what I have currently setup. If this is the best option. how would I go about cloning my Catalina install making sure the EFI partition is properly copied?
Reinstall my original Mojave disk in Slot B, a new disk in Slot A, make the required changes to install Big Sur and then use the migration assistant?
Or clone my Catalina install to a new disk and use the software update option that currently shows an update to Big Sur? This would probably save me a lot of work replicating what I have currently setup. If this is the best option. how would I go about cloning my Catalina install making sure the EFI partition is properly copied?
PART II
Advanced Configuration ✅
Everything has worked exactly as indicated in the WikiPos, in case it could help someone I attached the part of my config.plist to show as internal the Lycom DT-130 pcie two NVMe SSD (first one running this Catalina OC)
Using System Information and gfxutil as described in post 1 the code for "DeviceProperties" in my case was :
Next step BigSur update .....
!!!! Thanks to @cdf and everyone involved in this excellent "tutorial" and +
Advanced Configuration ✅
Everything has worked exactly as indicated in the WikiPos, in case it could help someone I attached the part of my config.plist to show as internal the Lycom DT-130 pcie two NVMe SSD (first one running this Catalina OC)
Using System Information and gfxutil as described in post 1 the code for "DeviceProperties" in my case was :
Code:
</dict>
<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>built-in</key>
<data>
AA==
</data>
</dict>
<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>built-in</key>
<data>
AA==
</data>
</dict>!!!! Thanks to @cdf and everyone involved in this excellent "tutorial" and +
I have done it both ways (6-core & 12-core), but you are right about the second method being the easiest to fix, to be the same as your Catalina volume. Also, neither CCC or SuperDuper! will clone the EFI without further steps.
To do it automatically, you need EFIClone and CCC, as it doesn't work with SD. However, you can do it easily, post cloning; just copy and paste it onto the EFI partition of the clone.
One note on Big Sur cloning, it isn't possible yet with either CCC or SD. I have been reinstalling it and using Migration Assistant to update it, but there's still a lot of stuff to redo.
Good luck.
To do it automatically, you need EFIClone and CCC, as it doesn't work with SD. However, you can do it easily, post cloning; just copy and paste it onto the EFI partition of the clone.
One note on Big Sur cloning, it isn't possible yet with either CCC or SD. I have been reinstalling it and using Migration Assistant to update it, but there's still a lot of stuff to redo.
Good luck.
@Steve_Jones
The way in which I usually copy my Catalina OC to a new hard drive is probably not the best because here are people who really know a lot more, but if it helps you it is:
Format the new disk in APFS, clone with Carbon Copy Cloner as usual and when finished mount the EFI partition of that new disk (which will be empty) and copy into it the EFI folder that works with my Catalina OC
Hope it helps
The way in which I usually copy my Catalina OC to a new hard drive is probably not the best because here are people who really know a lot more, but if it helps you it is:
Format the new disk in APFS, clone with Carbon Copy Cloner as usual and when finished mount the EFI partition of that new disk (which will be empty) and copy into it the EFI folder that works with my Catalina OC
Hope it helps
Yes it works. I got some questions
1. How can we convert an existing config file to a setup.py file without manual editing? I guess there is no way and it has to be edited manually from what I can see.
2. This script only supports the RELEASE OC version correct? Is there a way to download latest commit?
First of all thank you very much for your help! Thank you for your availability, for your timeliness and for your competence that every time you can solve problems!For quick diagnosis, please read this post, and try the pre-configured OC 0.6.3 package.
This package built from my cMP that is running a Radeon VII.
Activate AMD hardware acceleration
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 1.0.0] For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in...forums.macrumors.com
I have uploaded your OpenCore 0.6.3 Package and everything now works perfectly!
The last step now I would like to clone the two SATA SSD disks, Mojave and Catalina, into two NVMe disks and for this I ask you if I can then load the EFI folder containing OC into the new NVMe Catalina disk or, in case it is not possible, into which SATA disk I can load it.
Thanks again in advance!
Translated with www.DeepL.com/Translator (free version)
I recommend you just keep OC at the SATA driver, there is virtually no performance difference anyway.
You only need to worry about the major important changes in
setup.py, as everything else will be generated automatically. If you're worried there are settings you missed in setup.py, you can do a config.plist compare with either diff or your favourite editor. I recommend VSCode.Yes, release or debug versions only. Advanced users can easily build the latest master, I created the documentation. Building the binaries from master is time consuming, it should take 5-10min.
@cdf I merged PR #42 allowing local binaries, so advanced users can use the latest master into generator.
Last edited:
So you mean I have to keep Catalina on the SATA SSD?
But if so then does that mean I have to give up NVMe disk speed for Catalina?
OK thanks!
Also because Windows is already installed in a SATA SSD that I will then reconnect on the second port of the optical drive after reactivating OC.
My NVMe's are a lot faster than my Sata SSD (Mojave), that is why I run Big Sur and Windows on them.
Well, I understand! But then what do you suggest me to do?
Keep Mojave on SATA SSD and install Catalina (then I will upgrade to Big Sur) and Windows on the two NVMe disks respectively?
But then OC on which disk should I install it? On any other SATA disk?
To complete it I ask you an additional suggestion!
As you can see from the photo, the two NVMe disks are installed in the IOCREST PCIe 16x controller in slot #2 just above Radeon VII.
I noticed that after installing this controller, the noise is slightly increased and also the heat inside the cMP.
Of course I understand that two of the three fans on the Radeo VII now have less space to dissipate the heat.
Do you think this is not a problem (the heat) or is it better to move the controller in slot #3?
Thanks again in advance!
Translated with www.DeepL.com/Translator (free version)
Attachments
Cant you move the nvme controller to 1, and GPU to 2 ?
as it looks like 3 is empty.
3 and 4 share bandwith so giving up 3 for less heat is not too much pain.
as it looks like 3 is empty.
3 and 4 share bandwith so giving up 3 for less heat is not too much pain.
The Radeon VII sure can run like that without issue. At worst, just more noise.
But since your slot 3 is empty, you can seriously consider move the IO crest to slot 1, and put the Radeon VII in slot 2.
Anyway, if you need further discussion in this matter, you better open a new thread. This is not OpenCore related anymore.
Last edited:
I'm struggling with the icon boot picker. Whatever I try, there is only the text based picker.
OpenCore 0.6.3
Opencanopy.efi is in the drivers folder and "activated" in the config.plist
PickerAttributes is set to 1
PickerMode is set to External
different .icns files are in EFI/OC/Resources/Image
Any idea how I can obtain the icon boot picker???
EDIT: I got the standard hard disk icons now, but how can I assign a specific icon to each drive?
OpenCore 0.6.3
Opencanopy.efi is in the drivers folder and "activated" in the config.plist
PickerAttributes is set to 1
PickerMode is set to External
different .icns files are in EFI/OC/Resources/Image
Any idea how I can obtain the icon boot picker???
EDIT: I got the standard hard disk icons now, but how can I assign a specific icon to each drive?
Last edited:
Hello, I made an external BigSur patched Recovery uploaded here: Dropbox link
If someone want to test it on MacPro , you don't need to apply these fixes, just try boot its graphical environment with a customised menu, it should work from apple boot picker, OpenCore, Refind or any other bootloader.
If you use your internal or external OpenCore setup or an UEFI Windows 10 with its BOOTX64.efi , just don't install any of those opencore contained in this external recovery environment, while BigSurFixes are safe to install and don't involve any opencore config change.
For example, those interested in getting Night Shift, they could try to apply from Utilities menu "BigSurFixes Frameworks patch" (that is a patched CoreBrightness framework) or "BigSurFixes Continuity fix" (that is a patched IOBluetooth framework) that should whitelist any Broadcom Wifi with Bluetooth 4.0 for continuity features or even "BigSurFixes disable snapshot" to use "sudo mount -uw /" directly from BigSur normal booting.
But consider that if you apply any of those fixes the OTA update aren't detected more (even with board id spoofing), unless you reinstall BigSur from a stock "Install macOS Big Sur.app", because on BigSur kext patches imply making a new bootable unsealed snapshot, while OTA updates require a stock BigSur sealed snapshot, anyway reinstalling BigSur Data are kept and OTA update with snapshot sealing is fixed.
If someone want to test it on MacPro , you don't need to apply these fixes, just try boot its graphical environment with a customised menu, it should work from apple boot picker, OpenCore, Refind or any other bootloader.
If you use your internal or external OpenCore setup or an UEFI Windows 10 with its BOOTX64.efi , just don't install any of those opencore contained in this external recovery environment, while BigSurFixes are safe to install and don't involve any opencore config change.
For example, those interested in getting Night Shift, they could try to apply from Utilities menu "BigSurFixes Frameworks patch" (that is a patched CoreBrightness framework) or "BigSurFixes Continuity fix" (that is a patched IOBluetooth framework) that should whitelist any Broadcom Wifi with Bluetooth 4.0 for continuity features or even "BigSurFixes disable snapshot" to use "sudo mount -uw /" directly from BigSur normal booting.
But consider that if you apply any of those fixes the OTA update aren't detected more (even with board id spoofing), unless you reinstall BigSur from a stock "Install macOS Big Sur.app", because on BigSur kext patches imply making a new bootable unsealed snapshot, while OTA updates require a stock BigSur sealed snapshot, anyway reinstalling BigSur Data are kept and OTA update with snapshot sealing is fixed.