It is hard to say without a boot screen. Insert an EFI videocard so you can see what is on the screen. Try disabling the watchdog in the configuration file.
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
Thank you for your reply, rroumen (and VaporShark and startergo),
Yesterday, I had 4 drives in the Mac Pro 5.1, but this morning I pulled two HDDs out because I thought that might be the problem, but it still doesn't work after I do the SMC reset. The physical drives now in it are:
Bay 1: 2TB SATA hdd containing a working installation of the latest Mojave (and Catalina installer). I believe this HDD was formatted with the APFS scheme a week or so ago when I installed Mojave on it (it was a new drive) along with a metal-capable GPU (Sapphire Pulse Radeon RX580)...yes, I'm coming to the party late!
Bay 2: 120GB Samsung SSD, freshly erased and partitioned (one total partition) using Disk Utility (GUI version included with Mojave). I successfully mounted the EFI volume on that SSD (disk1s1 in my case), and copied into that volume the EFI directory from the latest OC download, and edited/saved config.plist and put it into EFI/EFI/OC ... and did all the steps on the first page of this thread, seemingly successfully, but after I unplug the computer to reset the SMC and restart, I get the chime, and the fans run ... but nothing beyond that. (How long does it typically take to boot at this stage? I have 32GB of error-correcting RAM, if that causes it to take longer to boot.)
One thought: I have a USB3 card in one of the slots that I added a year or two ago...could that be causing an issue?
Alternately, is there any way I could use my Macbook Air (13 inch, early 2015), hooked up to my OWC "Drive Dock" (I added the USB3 card to interface with that), to install Catalina on my SSD, then pull that SSD out of the Drive Dock and install it into my Mac Pro...possibly with some help from OC?
Thanks in advance for any help, and I apologize if these are n00b questions/problems.
ETA: One other thought: Could it be that my firmware never successfully updated? A week or so ago, during my upgrade from Sierra through HS to Mojave, I had a devil of a time trying to get through the "firmware update" process. First I couldn't get the FW update to work by holding down the power button, then it FINALLY started the FW update process but seemed to freeze up 90% of the way through – but it allowed me to proceed with the install of HS or Mojave (I forget which), which led me to believe the firmware had successfully updated – but then somewhere along the line it told me I had to update firmware AGAIN...sorry for the fuzzy details, but it's all kind of a blur since I've made so many changes, and had so much difficulty doing so, over the past few weeks. I held off on putting in the new GPU until I was ready to upgrade to Mojave, but upgrading to Mojave required me to first upgrade to HS, which in turn required the firmware update...it seems like Apple forces you to go through all these doors, each of which closes and locks behind you as soon as you go through...
Last edited:
Leave the other discs out and go back to blessing the OC drive in recovery. If you can’t get back to recovery use nvram reset, you should boot back in Mojave on disc 1 and use recovery from there out of post #1. Use the bless with —verbose to see the result. Then try again from there. The USB 3 should not be an issue, have the same as you. I have 48G ram and takes quite a while to ram test. I think should be less than a minute.
It is always possible that they did prototype with some dual socket config of the 7,1
I've read the first four or five pages of posts, but sorry don't have the time to get through 30+ pages, especially since most of what I've read relates to much newer MP's than my ancient 1,1,:
So simple question: Is there anything to gain right now for a Mac Pro 1,1 > 2,1 with OC to get it more current than El Cap? Can OC bypass the hardware limitations of the 2,1 CPU generation? Understandably most of what I've read has come from 5,1 owners, who don't have to contend with 32bit EFI and other limitations such as PCIe v1 etc and there's lots of good reasons for spending time on 4,1/5,1 MPs, whereas TBH its mostly sentiment that makes me want to do nice things to coax my 1,1 along for a while longer.
Is there a chance OC will enable 1,1 owners to get beyond 10.11? Even High Sierra would be great - or is it a case of wait and see as it's still early days for OpenCore? Unless you've got a computer science degree of course and can contribute to the process - which sadly I can't. Well I'm pretty damn sure no one would thank me for trying to help!
So simple question: Is there anything to gain right now for a Mac Pro 1,1 > 2,1 with OC to get it more current than El Cap? Can OC bypass the hardware limitations of the 2,1 CPU generation? Understandably most of what I've read has come from 5,1 owners, who don't have to contend with 32bit EFI and other limitations such as PCIe v1 etc and there's lots of good reasons for spending time on 4,1/5,1 MPs, whereas TBH its mostly sentiment that makes me want to do nice things to coax my 1,1 along for a while longer.
Is there a chance OC will enable 1,1 owners to get beyond 10.11? Even High Sierra would be great - or is it a case of wait and see as it's still early days for OpenCore? Unless you've got a computer science degree of course and can contribute to the process - which sadly I can't. Well I'm pretty damn sure no one would thank me for trying to help!
Nope. OpenCore can't do anything to overcome MP1,1/2,1 missing the SSE4.1 requirement of Sierra/High Sierra.I've read the first four or five pages of posts, but sorry don't have the time to get through 30+ pages, especially since most of what I've read relates to much newer MP's than my ancient 1,1,:
So simple question: Is there anything to gain right now for a Mac Pro 1,1 > 2,1 with OC to get it more current than El Cap? Can OC bypass the hardware limitations of the 2,1 CPU generation? Understandably most of what I've read has come from 5,1 owners, who don't have to contend with 32bit EFI and other limitations such as PCIe v1 etc and there's lots of good reasons for spending time on 4,1/5,1 MPs, whereas TBH its mostly sentiment that makes me want to do nice things to coax my 1,1 along for a while longer.
Is there a chance OC will enable 1,1 owners to get beyond 10.11? Even High Sierra would be great - or is it a case of wait and see as it's still early days for OpenCore? Unless you've got a computer science degree of course and can contribute to the process - which sadly I can't. Well I'm pretty damn sure no one would thank me for trying to help!
There is a fork of OC with few differences:
github.com
And here is the support thread
GitHub - n-d-k/OpenCorePkg: OpenCore front end
OpenCore front end. Contribute to n-d-k/OpenCorePkg development by creating an account on GitHub.
github.com
Multiple CPU package detection is fixed!
github.com
CPU package detection on configurations without MP services · Issue #663 · acidanthera/bugtracker
Code: 00:000 00:000 OC: OpenCore is now loading (Vault: 0/0, Sign 0/0)... 00:040 00:040 OC: Boot timestamp - 2020.01.14 03:57:35 00:088 00:047 OCCPU: No MP services - Not Found 00:129 00:040 OCCPU:...
github.com
Here's what I'm getting back from terminal with the --verbose:
-bash-3.2# bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/OC/OpenCore.efi --verbose
EFI found at IODeviceTree:/efi
Mount point for /Volumes/EFI is /Volumes/EFI
Mount point 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: disk0s1
Preferred system partition found: disk1s1
Returning booter information dictionary:
<CFBasicHash 0x7fb2fb500330 [0x109eb28e0]>{type = mutable dict, count = 3,
entries =>
0 : <CFString 0x1098d3be0 [0x109eb28e0]>{contents = "System Partitions"} = (
disk1s1,
disk0s1
)
1 : <CFString 0x1098d43c0 [0x109eb28e0]>{contents = "Data Partitions"} = (
disk1s1
)
2 : <CFString 0x1098d43e0 [0x109eb28e0]>{contents = "Auxiliary Partitions"} = (
)
}
Relative path of /Volumes/EFI/EFI/OC/OpenCore.efi is \EFI\OC\OpenCore.efi
IOMedia disk1s1 has UUID DA6676B2-CF2D-453B-9A7D-22ABC6ABDF15
Setting EFI NVRAM:
efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>DA6676B2-CF2D-453B-9A7D-22ABC6ABDF15</string></dict></dict><key>BLLastBSDName</key><string>disk1s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\OC\OpenCore.efi</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'
NVRAM variable "boot-args" not set.
-bash-3.2#
Does anyone see where things might be going wrong and what I might need to do to make it work?
Thank you in advance for any clues.
Is this a cosmetic thing or does it have any performance related benefits? Does it address the Geekbench scores being cut in half when disabling the VMM flag on a dual socket machine?Multiple CPU package detection is fixed!
CPU package detection on configurations without MP services · Issue #663 · acidanthera/bugtracker
Code: 00:000 00:000 OC: OpenCore is now loading (Vault: 0/0, Sign 0/0)... 00:040 00:040 OC: Boot timestamp - 2020.01.14 03:57:35 00:088 00:047 OCCPU: No MP services - Not Found 00:129 00:040 OCCPU:...
That’s not a bug for multi processor environment. Single processor setup also suffer from the same performance bug.
Thanks for your reply, Startergo.
$ csrutil status
System Integrity Protection status: enabled.
Gosh, now I feel like a dummy that I forgot about this. I guess I need to turn off SIP to do all this, don't I?
$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk3 2.0 TB disk0s2
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_APFS Container disk2 119.8 GB disk1s2
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +119.8 GB disk2
Physical Store disk1s2
1: APFS Volume F 655.4 KB disk2s1
2: APFS Volume Preboot 20.5 KB disk2s2
3: APFS Volume Recovery 20.5 KB disk2s3
4: APFS Volume VM 1.1 GB disk2s4
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.0 TB disk3
Physical Store disk0s2
1: APFS Volume G 660.2 GB disk3s1
2: APFS Volume Preboot 24.0 MB disk3s2
3: APFS Volume Recovery 507.3 MB disk3s3
4: APFS Volume VM 20.5 KB disk3s4
Hi, I have a mid-2010 MP5,1 (eight cores, 2 x 2.4 GHz E5620) with bootrom 144.0.0.0.0 and macOS 10.14.6 installed on a NVME SSD in PCIe 3. I tried several times to follow the guide in the first post of this thread, but each time at step 5e the Mac boots into grub instead of macOS on disk B (the NVME SSD in PCIe 3). I installed a triple boot with Win10 and Ubuntu (and rEFInd) on this Mac, but I removed the two SSD on which these systems are installed before trying the procedure. Can anybody help me please ? Thanks...
Last edited:
Thank you Startergo. I turned off SIP and went through the steps up to 5e again, where you shut down, unplug to reset SMC and restart...and nothing. Nothing appears on the monitor (I waited several minutes then typed in my password, hoping that I simply couldn't see the login screen, but no love...) and the fans run, but that's it.
FWIW, after doing
# bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/OC/OpenCore.efi --verbose
I saved the text output (below); does anything stick out for what I'm doing wrong? Thanks to all, again.
-bash-3.2# csrutil status
System Integrity Protection status: disabled (Apple Internal).
-bash-3.2# diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk3 2.0 TB disk0s2
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_APFS Container disk2 119.8 GB disk1s2
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +119.8 GB disk2
Physical Store disk1s2
1: APFS Volume F 716.8 KB disk2s1
2: APFS Volume Preboot 20.5 KB disk2s2
3: APFS Volume Recovery 20.5 KB disk2s3
4: APFS Volume VM 1.1 GB disk2s4
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.0 TB disk3
Physical Store disk0s2
1: APFS Volume G 660.4 GB disk3s1
2: APFS Volume Preboot 24.0 MB disk3s2
3: APFS Volume Recovery 507.3 MB disk3s3
4: APFS Volume VM 20.5 KB disk3s4
/dev/disk4 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +2.1 GB disk4
1: Apple_HFS macOS Base System 2.0 GB disk4s1
/dev/disk5 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +5.2 MB disk5
/dev/disk6 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk6
/dev/disk7 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk7
/dev/disk8 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk8
/dev/disk9 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk9
/dev/disk10 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk10
/dev/disk11 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk11
/dev/disk12 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +12.6 MB disk12
/dev/disk13 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +4.2 MB disk13
/dev/disk14 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk14
/dev/disk15 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk15
/dev/disk16 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk16
/dev/disk17 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk17
/dev/disk18 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +1.0 MB disk18
/dev/disk19 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk19
/dev/disk20 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk20
/dev/disk21 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +6.3 MB disk21
/dev/disk22 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +524.3 KB disk22
/dev/disk23 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: untitled +2.1 MB disk23
-bash-3.2# diskutil mount /dev/disk1s1
Volume EFI on /dev/disk1s1 mounted
-bash-3.2# bless --mount /Volumes/EFI --setBoot --file /Volumes/EFI/EFI/OC/OpenCore.efi --verbose
EFI found at IODeviceTree:/efi
Mount point for /Volumes/EFI is /Volumes/EFI
Mount point 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: disk0s1
Preferred system partition found: disk1s1
Returning booter information dictionary:
<CFBasicHash 0x7f8018600460 [0x10566f8e0]>{type = mutable dict, count = 3,
entries =>
0 : <CFString 0x105088be0 [0x10566f8e0]>{contents = "System Partitions"} = (
disk1s1,
disk0s1
)
1 : <CFString 0x1050893c0 [0x10566f8e0]>{contents = "Data Partitions"} = (
disk1s1
)
2 : <CFString 0x1050893e0 [0x10566f8e0]>{contents = "Auxiliary Partitions"} = (
)
}
Relative path of /Volumes/EFI/EFI/OC/OpenCore.efi is \EFI\OC\OpenCore.efi
IOMedia disk1s1 has UUID DA6676B2-CF2D-453B-9A7D-22ABC6ABDF15
Setting EFI NVRAM:
efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>DA6676B2-CF2D-453B-9A7D-22ABC6ABDF15</string></dict></dict><key>BLLastBSDName</key><string>disk1s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\OC\OpenCore.efi</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'
NVRAM variable "boot-args" not set.
-bash-3.2# csrutil status
System Integrity Protection status: disabled (Apple Internal).
-bash-3.2#
Last edited:
You shouldn't need to disable SIP because you are in recovery. Maybe try switching your drives around so that the EFI partition is disk0s1.
Are you booting Catalina or Mojave? Single or dual CPU's. What is the CPU?
Mojave, 10.14.6
From About this Mac (italics mine):
Model Name: Mac Pro (Mid 2010) A1289
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon [W3680 Westmere according to Everymac; sysctl machdep.cpu.brand_string confirms this]
Processor Speed: 3.33 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
Boot ROM Version: 144.0.0.0.0
SMC Version (system): 1.39f11
SMC Version (processor tray): 1.39f11
I've been editing/saving config.plist with textedit.
Last edited:
Experts cdf & tsialex:
Now that OC is updated to 0.5.4 do we need to redo the steps with the new 0.5.4 and config.plist?(No AppleSupport-2.1.4 incorporation step?) (OpenCore on Legacy Apple Hardware-Monday at 8:35am)
What has changed between 0.5.3 and 0.5.4? Is it advisable, important?
Now that OC is updated to 0.5.4 do we need to redo the steps with the new 0.5.4 and config.plist?(No AppleSupport-2.1.4 incorporation step?) (OpenCore on Legacy Apple Hardware-Monday at 8:35am)
What has changed between 0.5.3 and 0.5.4? Is it advisable, important?
If you want to update: Simply replace the BOOT and OC folders in your EFI folder on the EFI partition (backing up the old ones just in case). Follow steps 2 to 4 (from within Catalina) and reboot.
That's right. The support files are now included in OC.
Most notably: microcode reading has been fixed. This makes the update worthwhile. (@startergo has been doing a fine job of reporting pertinent issues to the developers!)