MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[Sledhead70]

Has anyone experienced an issue where the drive that has OC installed doesn't show up in the diskutil list as outlined in the first steps? I formatted the new SSD drive (i.e. Disk A) while booted into Mojave (my Disk B), mount the disk A EFI, drag in the OC and config files, and when I reboot into recovery using terminal the disk A doesn't even show in the list. Any thoughts from anyone? Thank you.

 

[Macschrauber]

Has anyone experienced an issue where the drive that has OC installed doesn't show up in the diskutil list as outlined in the first steps? I formatted the new SSD drive (i.e. Disk A) while booted into Mojave (my Disk B), mount the disk A EFI, drag in the OC and config files, and when I reboot into recovery using terminal the disk A doesn't even show in the list. Any thoughts from anyone? Thank you.

some qvo drives do not survive warm boot.

 

[Sledhead70]

some qvo drives do not survive warm boot.

Sorry, I am not sure I follow. It is a SAMSUNG 870 EVO 1TB, and when I tried installing Big Sur using OC Legacy Patcher it showed up each time, so not sure why it won't now. I am hoping to go through the manual install here since I couldn't get the 5,1 to be recognized using OCLP, but on this first attempt it fails to show up in the disk list. When I run the list it show about 12 drives (almost all are images I think), but not the target drive.

The target does show up if I use a USB adapter, so do you know if I can do the install steps using that method?

 

[Macschrauber]

Sorry, I am not sure I follow. It is a SAMSUNG 870 EVO 1TB, and when I tried installing Big Sur using OC Legacy Patcher it showed up each time, so not sure why it won't now. I am hoping to go through the manual install here since I couldn't get the 5,1 to be recognized using OCLP, but on this first attempt it fails to show up in the disk list. When I run the list it show about 12 drives (almost all are images I think), but not the target drive.

The target does show up if I use a USB adapter, so do you know if I can do the install steps using that method?

seems the 870 Evo makes also trouble like some qvo do:

Search results for query: 870 evo

forums.macrumors.com

 

[dataid]

OCAT (OpenCore Auxillary Tools) is an open source program for configuring OpenCore config.plist files through a graphical user interface. This program is available through GitHub. There is also a new mention of OCAT in the 0.7.3 OpenCore Reference Manual, "The choice of open-source implementations with transparent binary generation is encouraged (e.g. OCAT), since other tools may contain malware. Remember that a configuration made for a different hardware setup shall never be used on another hardware setup."

Link to GitHub for OCAT OpenCore Auxillary Tools

Below is the developers description from his forum thread on InsanelyMac, Open source cross-platform OpenCore auxiliary tools

OC auxiliary tools (OCAT or ocat for short) = Config.plist editor + Config.plist database + ...

Note: All platforms have the same interface style

Features include but are not limited to:
* Write plist files with spaces for indentation to fit all editors or editing environments, such as the Shell editing environment
* Powerful keyword search function, including retrieval of unseen data tables
* All tabs and checkbox text are supported for copying (right-click menu)
* Unlimited levels of undo and redo (automatically cleared when opening a new file)
* Copy and paste rows between multiple processes and single processes
* Well-built data structures to accommodate rapid iterations of OpenCore
* Built-in configuration file database
* Generate EFI folders on the desktop based on configuration files
* Each function option adopts suspension prompt and status bar prompt
* Keep up with the latest development version of OpenCore and keep pace with it completely
* Double-click to open the file, drag and drop the file to the software interface to open the file, and open the file history display
* All three platforms use OC's official macserial to generate serial numbers
* Software UI adapts to various resolutions, including winpe and linux livecd, etc.
* Built-in update check
......

Attached are a few screenshots that illustrate the user interface.

 

[Dayo]

There is also a new mention of OCAT in the 0.7.3 OpenCore Reference Manual, "The choice of open-source implementations with transparent binary generation is encouraged (e.g. OCAT), since other tools may contain malware. Remember that a configuration made for a different hardware setup shall never be used on another hardware setup."

Not to suggest there is anything wrong with OCAT but pointing out the following in the interest of accuracy:

1. The mention of OCAT in the manual is not new in v0.7.3 but appeared in v0.6.9
2. The quoted part of the manual is a bit misleading because it is incomplete.
   • To paraphrase, the manual strongly advises against using automated tools. It then says that in cases where a user has no option despite the warning given, "The choice of open-source implementations with transparent binary generation is encouraged ..."

 

[dataid]

Not to suggest there is anything wrong with OCAT but pointing out the following in the interest of accuracy:

1. The mention of OCAT in the manual is not new in v0.7.3 but appeared in v0.6.9
2. The quoted part of the manual is a bit misleading because it is incomplete.
   • To paraphrase, the manual strongly advises against using automated tools. It then says that in cases where a user has no option despite the warning given, "The choice of open-source implementations with transparent binary generation is encouraged ..."

Thank you for pointing out that OCAT was mentioned earlier than version 0.7.3. I have corrected my post. However, let us completely quote the paragraph of the reference manual. The entire paragraph is as follows:

It is strongly advised not to use any software that is aware of the internal configration (sp) structure as it constantly gets out of date and will cause incorrect configuration to be generated. If it is a must desprite (sp) the warning one should make sure to only use stable versions of OpenCore with explicit support for the particular version in the app. The choice of open-source implementations with transparent binary generation is encouraged (e.g. OCAT), since other tools may contain malware. Remember that a configuration made for a different hardware setup shall never be used on another hardware setup.

The key point is OpenCore developer's advise to not use software that uses internal configuration structure to generate the config.plist. However, if one does choose to use software to simplify the creation and/or examination of the config.plist other than by a manual editing with software unaware of internal configuration, e.g. word processor. The developers caution that when such tools are used, use tools aware of internal configuration structure only with stable versions of Opencore - officially released versions, not nightly builds or unreleased versions, by tools which have "explicit support" for the version of OpenCore being used. The developers also recommend only open-source tools with transparent binary generation in order to avoid malware. OCAT does fulfill their two cautions. OCAT is open-source with its code on GitHub and it does explicitly state which released version of OpenCore it is to be used with.

To find the OCAT version designated for use with the released, stable version of, OpenCore 0.7.3 look for the About menu which is found on the main menu of OCAT under OCAuxiliaryTools | About OCAuxiliaryTools.

 

[TECK]

To find the OCAT version designated for use with the released, stable version of, OpenCore 0.7.3

Is that what you are referring to?

 

[dataid]

Is that what you are referring to?

I hope this is clearer, I changed the original post to read: To find the OCAT version designated for use with the released, stable version of, OpenCore 0.7.3 look at the About menu which is found on the main menu of OCAT under OCAuxiliaryTools | About OCAuxiliaryTools.

 

[jfcates]

opencore 0.7.3 latebloom and nvram Confusion?

Opencore 0.7.3 instructions:
Clean up the NVRAM

• Find NVRAM and delete

XML:
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>-no_compat_check</string>
</dict>
and
XML:
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<array>
<string>boot-args</string>
</array>

latebloom instructions:
5. Edit config.plist

NVRAM | Add | 7C436110-AB2A-4BBB-A880-FE41995C9F82 | boot-args | string value

You will add to the existing string value the 3 parameters latebloom.kext uses for configuration.
The values for these parameters and their defaults are described in Syncretic's Wiki post, Post #1.
The parameters are:

latebloom
lb_range
lb_debug
etc...

So I added 7C436110-AB2A-4BBB-A880-FE41995C9F82 back into my config.plist like this:

<key>NVRAM</key>
<dict>
<key>Add</key>
<dict>
<key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
<dict>
<key>DefaultBackgroundColor</key>
<data>
v7+/AA==
</data>
<key>UIScale</key>
<data>
AQ==
</data>
</dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string> latebloom=100 lb_range=20 -v</string>
</dict>
</dict>

Mac Pro 4,1 updated to 5,1

Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.06 GHz
Number of Processors: 2
Total Number of Cores: 12
Running Big Sur on ssd, 11.2.3 downloaded 11.5 via Apple Update and have Macintosh HD listed as drive but fails to install, just reboots. Opencore is on on EFI of second ssd running Catalina.

Ant thoughts suggestions appreciated.

 

[cdf]

An[y] thoughts suggestions appreciated.

You can always add the boot-args by booting into Recovery and entering the following command in Terminal: nvram boot-args="latebloom=100 lb_range=20". This is arguably cleaner in the sense that this is how boot-args are added without OpenCore on supported Macs.

 

[eikic1]

#WTA
anyone have config for Radeon VEGA 64? CMP5,1 2012 im using OpenCore 0.7.3
On Mojave Can't Active But on Bigsur 11.2.3 Active(but Performa Not Active)

Im using dual OS

Thanks

 

[jfcates]

You can always add the boot-args by booting into Recovery and entering the following command in Terminal: nvram boot-args="latebloom=100 lb_range=20". This is arguably cleaner in the sense that this is how boot-args are added without OpenCore on supported Macs.

Thank you cdf,
I removed:

<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string> latebloom=100 lb_range=20 -v</string>
</dict>

and ran nvram boot-args in recovery terminal. I've got something screwed up somewhere, because it still rejects the update and reboots. I have no problem booting back into Big Sur 11.2.3
I'm attaching config.plist as txt file and another screen photo, but it's pretty jittery. Can anyone decipher where I've gone wrong?

 

[ashryver16]

Hello since in the #1 post it's specified that macOS 11.3+ have issues and are not recommended, does anyone have a link to download big sur 11.2.3- since the one to download it directly from apple doesn't work and a google search does not seem to yield any actual results? would be cool to include it in the #1 post too for other people who come across this thread. thank you!

 

[sfalatko]

Hello since in the #1 post it's specified that macOS 11.3+ have issues and are not recommended, does anyone have a link to download big sur 11.2.3- since the one to download it directly from apple doesn't work and a google search does not seem to yield any actual results? would be cool to include it in the #1 post too for other people who come across this thread. thank you!

To be a bit pointed - try a search of this forum yourself....I searched for "download link" in this thread and the second result in the list was - #8,603

 

[ashryver16]

To be a bit pointed - try a search of this forum yourself....I searched for "download link" in this thread and the second result in the list was - #8,603

as i said in my post the apple link doesn't work this is all i get.

 

[chrisrm9208]

Here's an oddity. I just started trying to add OC0.7.3 to a recent acquisition, a cMP Server 5,1. I put 2 cheap SSDs in, one to hold OC and one to hold macOS. Started by running OCLP2.4, which got to a quick flash of the graphic boot picker, then to a 'Prohibited' icon, white on black. Recovered, erased boot SSD, re-downloaded OCLP (it could have been corrupted...) and the same thing happens. Take SSD out and replace with known good spinner. Same result, so not the disc type of format, having tried HFS and APFS. OK, try the simple route as shown in post 1. Got to the text boot picker, OC loaded and verified, so let's try OCLP again. Back to the 'Prohibited' sign.

Any suggestions for how I might diagnose the boot picker in OCLP?

 

[PeterHolbrook]

@chrisrm9208: As indicated in the first post, Big Sur 11.3+ is not currently supported, although the latebloom workaround is known to work for a lot of users.

 

[paalb]

Here's an oddity. I just started trying to add OC0.7.3 to a recent acquisition, a cMP Server 5,1. I put 2 cheap SSDs in, one to hold OC and one to hold macOS. Started by running OCLP2.4, which got to a quick flash of the graphic boot picker, then to a 'Prohibited' icon, white on black. Recovered, erased boot SSD, re-downloaded OCLP (it could have been corrupted...) and the same thing happens. Take SSD out and replace with known good spinner. Same result, so not the disc type of format, having tried HFS and APFS. OK, try the simple route as shown in post 1. Got to the text boot picker, OC loaded and verified, so let's try OCLP again. Back to the 'Prohibited' sign.

Any suggestions for how I might diagnose the boot picker in OCLP?

Try the OCLP support on https://discord.gg/rqdPgH8xSN

 

[tsialex]

"Mom, no betas and no RCs"

 

[sfalatko]

"Mom, no betas and no RCs"

View attachment 1830460

I see the same and I'm not running any betas for Big Sur or Monterey.

So - I would hold off on the update. I can't boot into Big Sur right now - I keep getting either hangs with latebloom or hangs after the apple logo and progress bar appears. I'm in Mojave right now checking out my config.

 

[Dayo]

"Mom, no betas and no RCs"

Expect a nasty zero day exploit announcement soon

 

[sfalatko]

I see the same and I'm not running any betas for Big Sur or Monterey.

So - I would hold off on the update. I can't boot into Big Sur right now - I keep getting either hangs with latebloom or hangs after the apple logo and progress bar appears. I'm in Mojave right now checking out my config.

I finally got to the desktop however my reboots - both cold and warm - are much worse than with 11.5.2. I am getting hangs in phase 2. i am going to have to do more work on the delay.

 

[Dayo]

Expect a nasty zero day exploit announcement soon

Here it is: https://www.bbc.com/news/business-58540936

 

[TECK]

"Mom, no betas and no RCs"

View attachment 1830460

Upgraded without issues, with Latebloom 0.20. Still cannot get any notifications for new software, what is the usual fix?