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 know this is a Mac Pro forum, right?
You can try installing through Hackintool (it is inside it). Dosdude's USB installer patcher works for sure.
Thanks, But I prefer to stick with Mojave for now. It can provide all functions and features which I needed from all apps. Even hardware HEVC decode acceleration on FCPX is possible thru Lilu and WEG on Mojave. And no 5% CPU performance penalty too. I've no point to jump into Catalina and got no major benefit at this moment.
I hope someday there's a one step utility created such as a patch installer developed which can simplify all these steps. Right now, there're too many micro-steps have to be implemented to get it worked out. One small mistake could kill the Opencore-Catalina system. In my past few days of attempt. I killed 3 boot drives already by wrong steps. So I can tell. I demand stability in my work. Mojave solves all my problems at once, recovery is simple. And dual boot can be done easily. But I look forward to that on OpenCore Catalina.
Last edited:
Expert cdf
macrumors 6502-Said:
My recommendation is what has worked well for me, but other setups are certainly possible. I believe that @w1z has had success with just NVMe drives on a 7101A (see post #6).
Expert @w1z
I have a 7101A with Samsung NVME 1tb drives, one with current mojaveA and another I can use for CatalinaB and a separate SSD in sled 1 with Windows 10 on it- Do I need to worry about mojave drive being before catalina drive in the 7101A since my windows 10 is on the separate SSD sled not on a shared mojave drive?? I am a real NEWBIE!!
macrumors 6502-Said:
My recommendation is what has worked well for me, but other setups are certainly possible. I believe that @w1z has had success with just NVMe drives on a 7101A (see post #6).
Expert @w1z
I have a 7101A with Samsung NVME 1tb drives, one with current mojaveA and another I can use for CatalinaB and a separate SSD in sled 1 with Windows 10 on it- Do I need to worry about mojave drive being before catalina drive in the 7101A since my windows 10 is on the separate SSD sled not on a shared mojave drive?? I am a real NEWBIE!!
Has anyone figured out how to boot into a Windows 10 UEFI install while using OpenCore with Catalina and no boot screens? I used to use the following command:
This worked great in Mojave, but in Catalina with OpenCore it simply reboots back into macOS.
Code:
sudo bless --mount /Volumes/Windows --setBoot
sudo rebootThis worked great in Mojave, but in Catalina with OpenCore it simply reboots back into macOS.
You need to sudo mount the ESP (EFI) partition of your Windows installation then execute:
Code:
sudo bless --folder /Volumes/NO\ NAME --file /Volumes/NO\ NAME/EFI/Microsoft/Boot/bootmgfw.efi --setBoot --nextonly --verbosethen
Code:
sudo rebootIn my case, my Windows ESP partition is named "NO NAME"
If you want your mac pro to boot into Catalina by default after performing NVRAM reset or blessing OC, place the Catalina drive in Slot 3 and Mojave drive in Slot 2 on your 7101A as drives are scanned in the order 4 3 2 1 instead of 1 2 3 4 (and placed in that order on the boot screen) - not sure if this is a Catalina specific thing or not as I did not attempt to use OC with Mojave.
Internal SATA installations/ESP partitions are presented after or in between NVMe drives on the boot screen but never before the first NVMe drive.
Code:
EFI found at IODeviceTree:/efi
Mount point for /Volumes/EFI is /Volumes/EFI
Common mount point of '/Volumes/EFI' and '' is /Volumes/EFI
No BootX creation requested
No boot.efi creation requested
found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xFF1FFF3F
found ioreg "FirmwareFeatures"; featureFlagsValue=0xC00C5403
isPreBootEnvironmentUEFIWindowsBootCapable=0
preboot environment is not UEFI boot capable
isDVDWithElToritoWithUEFIBootableOS=0
Checking if disk is complex (if it is associated with booter partitions)
GPT detected
Booter partition required at index 2
System partition found
Preferred system partition found: disk1s1
Preferred system partition found: disk2s1
Preferred system partition found: disk3s1
Returning booter information dictionary:
{
"Auxiliary Partitions" = (
);
"Data Partitions" = (
disk2s1
);
"System Partitions" = (
disk2s1,
disk3s1,
disk1s1
);
}
Path to mountpoint given: /Volumes/EFI
IOMedia disk2s1 has UUID 194F7002-E9C3-4A2E-AF97-50375CE5883C
Setting EFI NVRAM:
efi-boot-next='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>194F7002-E9C3-4A2E-AF97-50375CE5883C</string></dict></dict><key>BLLastBSDName</key><string>disk2s1</string></dict></array>'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-file'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-mkext'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-kernelcache'
Old boot-args: -no_compat_check -wegtree shikigva=144
Got token: -no_compat_check
Preserving: -no_compat_check
Got token: -wegtree
Preserving: -wegtree
Got token: shikigva=144
Preserving: shikigva=144
New boot-args unchanged, skipping update.
Code:
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *2.0 TB disk0
1: Windows_NTFS Storage 2 2.0 TB disk0s1
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI EFI 209.7 MB disk1s1
2: Microsoft Basic Data Storage 999.9 GB disk1s2
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *512.1 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_APFS Container disk4 359.9 GB disk2s2
3: Microsoft Reserved 16.8 MB disk2s3
4: Microsoft Basic Data Windows 151.4 GB disk2s4
5: Windows Recovery 617.6 MB disk2s5
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_HFS Backup 500.1 GB disk3s2
3: Microsoft Basic Data Storage 3 1.5 TB disk3s3
/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +359.9 GB disk4
Physical Store disk2s2
1: APFS Volume macOS - Data 96.3 GB disk4s1
2: APFS Volume Preboot 25.4 MB disk4s2
3: APFS Volume Recovery 525.4 MB disk4s3
4: APFS Volume VM 1.1 MB disk4s4
5: APFS Volume macOS 11.0 GB disk4s5Your bless command is blessing the wrong partition disk2s1 rather than disk1s1. Which one of them is mounted? Actually from what I can see disk2s4 is a Bootcamp windows right? It is not UEFI Windows. Is there BootX64.efi there?
disk2s1 should be the right partition. disk1 is just additional storage and does not contain a Windows installation. disk2s4 is my actual Windows system partition.
Code:
% ls /Volumes/EFI/EFI/Microsoft
Boot RecoveryAnd inside of Boot...
Code:
% ls /Volumes/EFI/EFI/Microsoft/Boot
BCD da-DK hu-HU kd_07_1415.dll qps-ploc
BCD.LOG de-DE it-IT kd_0C_8086.dll ro-RO
BCD.LOG1 el-GR ja-JP kdstub.dll ru-RU
BCD.LOG2 en-GB kd_02_10df.dll ko-KR sk-SK
BOOTSTAT.DAT en-US kd_02_10ec.dll lt-LT sl-SI
Fonts es-ES kd_02_1137.dll lv-LV sr-Latn-RS
Resources es-MX kd_02_14e4.dll memtest.efi sv-SE
bg-BG et-EE kd_02_15b3.dll nb-NO tr-TR
boot.stl fi-FI kd_02_1969.dll nl-NL uk-UA
bootmgfw.efi fr-CA kd_02_19a2.dll pl-PL winsipolicy.p7b
bootmgr.efi fr-FR kd_02_1af4.dll pt-BR zh-CN
cs-CZ hr-HR kd_02_8086.dll pt-PT zh-TWIs there bootx64.efi under EFI/Boot?
[automerge]1577378741[/automerge]
Try this script
Code:
display dialog "Select a startup disk" buttons ¬
{"Windows", "macOS", "Recovery"}
set bootVol to the button returned of the result as text
do shell script ¬
"bless -mount \"/Volumes/" & bootVol & ¬
"\" -setBoot -nextonly" with administrator privileges
#do shell script "shutdown -r now" with administrator privilegesYes, the one that came with OpenCore. I also have a backup of my original located at /Volumes/EFI/EFI/backup_bootx64.efi.
I tried the script to no avail. I then put my old bootx64.efi file in place and used the old command I had. That worked, but of course OpenCore no longer works. Any ideas on how to use both OpenCore and enable booting into Windows?