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

[Macschrauber]

I did run your esp tools and there're 3 active esps", the opencore, which is active, one in the vanilla Mojave disk and one in the nvme one that I use to run monterey. The culprit is the monterey one as I still had the extra efi boot option when I removed the mojave disk. However, the extra efi option only appeared when I removed windows from my mac pro. The question now is, is it safe to delete the contents of the nvme efi? - Cheers!

PS. The opencore EFI is on an ssd in sata bay 1, not on the nvme.

I can't tell you what ESPs you wrote.

Use the Label all bootloader ESPs tool to give them names and test them.

You wrote about active ESPs, I only write the word active for Windows ESP what contains Bootx64.efi. Once run outside OpenCore protection this gives you a certificate in NVRAM.

Don't ever start an Windows ESP from the Apple BootPicker. This gives you certificates. Even if there is just a lonely Windows Bootloader on a disk! I got one while testing while just copying an Windows ESP on an empty disk. But don't mind as I can delete them.

Test your nvram with the Dumper if you have Windows ESPs in your machine.

 

[eVasilis]

I can't tell you what ESPs you wrote.

Use the Label all bootloader ESPs tool to give them names and test them.

You wrote about active ESPs, I only write the word active for Windows ESP what contains Bootx64.efi. Once run outside OpenCore protection this gives you a certificate in NVRAM.

Don't ever start an Windows ESP from the Apple BootPicker. This gives you certificates. Even if there is just a lonely Windows Bootloader on a disk! I got one while testing while just copying an Windows ESP on an empty disk. But don't mind as I can delete them.

Test your nvram with the Dumper if you have Windows ESPs in your machine.

Well, I checked and there are no windows booloaders/certificates

 

[mrkapqa]

for the dvd tray: maybe some mouse hardware mimic a button press on init. I had a wireless mouse what USB dongle did this.

still having this issue with both DVD Drives ejecting (nearly) every boot ; is this standard behaviour for MacPro + later OC or do i have faulty computer/setup?

Mouse button press at startup does not seem to inhibit this behaviour most of the time.

 

[oliverc]

Getting super super slow windows 10 or 11 when using the instructions in this thread. Any clue what could cause that please? Thanks.

 

[tsialex]

Mouse button press at startup does not seem to inhibit this behaviour most of the time.

Pressing the mouse button at boot time opens the DVD tray…

 

[mrkapqa]

Pressing the mouse button at boot time opens the DVD tray…

Ok, thanks, remembered that (somehow).

Changed the mouse, problem solved (at least for 2 consecutive boots)

Now this Intellimouse Mouse Pro that was in use might have provoked this issue; could be faulty item, Or: i remember to have changed DPI settings for Intellimouse in Windows (and those changes apparently should persist on MacOS) and maybe this OC didnt like much that setting.

 

[eVasilis]

Well, I checked and there are no windows bootloaders/certificates

And the saga continues. I zipped the contents of the EFI partition on the nvme, which boots monterey, but the EFI boot option is still there. Any ideas anyone?

 

[mrkapqa]

œeVasilis i had to bless the Boot EFI partition under Mojave; if i did it under Monterey, the EFI would still be there. probably something to do with csrutil protection, i don't know; however, under Mojave, i seem to have system protection correctly disabled, and EFI symbol is gone during Boot-pickup;

 

[eVasilis]

œeVasilis i had to bless the Boot EFI partition under Mojave; if i did it under Monterey, the EFI would still be there. probably something to do with csrutil protection, i don't know; however, under Mojave, i seem to have system protection correctly disabled, and EFI symbol is gone during Boot-pickup;

Hi mrkapqa, the opencore efi partition is properly blessed from mojave and SIP disabled.

 

[mrkapqa]

i had as mentioned two EFI entries ab Pickup

one EFI Partition had a "System" Folder in it (OCLP leftover), which when scrubbed, would get me rid of the one EFI entry.
the other one persisted initially, but after replacing OC with version 1.0.0 and adjusting it for booting Monterey ( i have to change config.plist entries for "UpdateSmbios" and "Cpuid1Mask" to let Monterey again with newer MartinLO versions, don't know why though) and re-blessing from Mojave, it would somehow get rid also of second EFI entry (not at first boot, but afterwards). All a little bit confusing, but for the moment it is stable; Not that the EFI entry, causing any harm, but seems a bit out of place since it not offering any function as it seems.

 

[Gustav Holdoff]

i had as mentioned two EFI entries ab Pickup

one EFI Partition had a "System" Folder in it (OCLP leftover), which when scrubbed, would get me rid of the one EFI entry.
the other one persisted initially, but after replacing OC with version 1.0.0 and adjusting it for booting Monterey ( i have to change config.plist entries for "UpdateSmbios" and "Cpuid1Mask" to let Monterey again with newer MartinLO versions, don't know why though) and re-blessing from Mojave, it would somehow get rid also of second EFI entry (not at first boot, but afterwards). All a little bit confusing, but for the moment it is stable; Not that the EFI entry, causing any harm, but seems a bit out of place since it not offering any function as it seems.

you must to delete this System folder- there is one more boot efi - these are some artifacts from the oclp that has not yet been deleted (dated 2022).
If I were you,
I would completely delete everything inside the efi and put Martin's package again - it will be easier
inside efi structure must be the same as in post#1: only BOOT folder and OC folder (sometimes there are APPLE folder and Microsoft folder)

 

[mrkapqa]

thanks @Gustav Holdoff maybe i was unprecise, but the problem here on this MacPro has already been solved;
have OC back in place on HDD1 in SataBay1 and deleted the OCLP leftovers; no more EFI symbol, no more DVD tray ejecting at startup;;
only thing had problems with newer revisions of MartinLo Package and Windows 11 23H2 which suddenly would no longer boot (whereas 22H2 would) (incidentally also Monterey refused to boot with newer versions) but after adjusting he config.plist now it seem solved with ; So this MacHere is quite ready for task hopefully; it can now boot Mojave, or another BigSur, Monterey and Windows 11 without issue; BigSur does not go to "sleep" so will replace it with another version sometime later probably; thank you all for the constant guiding.

 

[avro707]

œeVasilis i had to bless the Boot EFI partition under Mojave; if i did it under Monterey, the EFI would still be there. probably something to do with csrutil protection, i don't know; however, under Mojave, i seem to have system protection correctly disabled, and EFI symbol is gone during Boot-pickup;

Even if it has the status of system protection reported as disabled in Monterey?

I have the Martin Lo package on two machines and although I can see it definitely loads I’m going to try getting my old Mojave disk out and blessing the EFI. Maybe I get rid of the reboot “forbidden” symbols.

I hadn’t thought of that.

 

[mrkapqa]

Even if it has the status of system protection reported as disabled in Monterey?

Well, i have sometimes changes in system protection under Monterey; at the momeent it reports as "disabled", but sometimes it reverts back to another term (not enabled) like (user defined something),
and previouisly i more or less always had done blessing from Mojave disk, and still had the 1 eFI symbol, or two;
but with proper inspection and maybe newer version of OpenCore this got sorted so for the moement this symbol is gone but i would not be surprised if it came if i attempted to to something like "NVRAM clean" or ssimilar.

 

[Kantgittrite]

In this guide, you'll learn how to use OpenCore to install, run and update macOS Catalina, Big Sur and Monterey on the 2009–2012 Mac Pro, ending up with a clean unaltered operating system just like on a supported Mac.

The approach described in this guide is for setting up and configuring OpenCore manually in a manner that aims to promote an understanding of the resulting configuration. There are other ways of setting up and configuring OpenCore on the Mac Pro that were developed after the approach described in this guide and that draw on this guide to varying extents. A popular example is OCLP (OpenCore Legacy Patcher), which sets up and configures OpenCore automatically on the Mac Pro as well as on a wide range of other legacy Macs. For support with OCLP, please use their recommended support channel.

View attachment 2057744

In this guide, you'll learn how to use OpenCore to install, run and update macOS Catalina, Big Sur and Monterey on the 2009–2012 Mac Pro, ending up with a clean unaltered operating system just like on a supported Mac.

The approach described in this guide is for setting up and configuring OpenCore manually in a manner that aims to promote an understanding of the resulting configuration. There are other ways of setting up and configuring OpenCore on the Mac Pro that were developed after the approach described in this guide and that draw on this guide to varying extents. A popular example is OCLP (OpenCore Legacy Patcher), which sets up and configures OpenCore automatically on the Mac Pro as well as on a wide range of other legacy Macs. For support with OCLP, please use their recommended support channel.

View attachment 2057744

I keep getting command not found in the terminal. I've downloaded the files that you posted. I've tried in both Recovery and Regular. I've disable SIP LoL that work.

 

[Gustav Holdoff]

Recently (this means after updating MacOS 12.7.5 and OC 1.0.0) during standard work, I discovered that sometimes increased fan speed appears;
I looked at the activity monitor and found that a process QuickLookSatellite at 200% appeared - which is supposedly responsible for the work when viewing some files (using preview or may be acrobat reader) and supposedly the process is due to the fact that the system does not like something - probably the process is designed for some commands that are not implemented on older processors.
I experimented - closed all applications - the process does not stop - I have to kill it manually.
I continue to work without rebooting, although I’m not sure that after a force quit quicklook the system remains correct. So sometimes, if the result of my work becomes critical for me and I don’t want an important program to crash while working, I force quit the process and reboot the computer.
I turn on Activity Monitor several times a day while working to make sure that I don't have any unnecessary processes. And I have never encountered this process in all my long years of work.
I discovered it only recently - I think a month ago
and I didn't install any new programs
Has anyone encountered the same process?
And is this process a problem for work?
EDITED
I have not investigated this problem deeply, but I can state that after updating MacOS to 12.7.6 this problem has not disappeared
how can I describe the occurrence of the quicklooksatellite daemon process:
I can work all day simultaneously with Archicad (70% cpu), Blender (60%), Twinmotion (200%) and using Parallels (200%) with some Windows programs.
At the same time several safari and chrome windows are open - the process is not observed
but if preview with lot of jpg open all day, or Adobe Acrobat with PDF, and if I periodically view them, switching from working with Archicad or importing these jpg files as textures into Archicad or Twinmotion, but if I pay attention to the fact that the fans are running at high speed, then opening the Activity Monitor, I find that the quicklook daemon has been running for several hours at 300% of cpu. I close all programs for an experiment - the daemon does not disappear - only Force Quit quicklooksatellite daemon normalizes the fan speed.
then I open all the programs again - the demon does not appear
At the same time, since the daemon appeared only 4 times in the last 2 months, I can compare my actions:
my standard work with programs (described earlier) does not lead to the appearance of the daemon
the daemon appears only with a large number of jpg and pdf and with active interaction - with frequent opening and closing of files for previewing

 

[flaubert]

I keep getting command not found in the terminal. I've downloaded the files that you posted. I've tried in both Recovery and Regular. I've disable SIP LoL that work.

The two quoted text sections you included in your post do not reference any commands that should be run in Terminal, so there is no way to know what it isn't working. If you want help here you're going to have to be very specific; at a minimum copy and paste the command that isn't working into a reply posting. I know that it can be frustrating when something isn't working, but take a deep breath, step back, and write out in detail what you've done up to the point where it isn't working.

 

[wyattaj25]

Hey everyone,

I sucsessfully installed this version of opencore on my mac pro 5,1 and can boot from my old install of monterey made in OCLP.

However, during the switch from OCLP to this manual install, i no longer have bluetooth and wifi connectivity in Monterey.

Is there anyway i can bring at least bluetooth back? Thanks for the help!

 

[cdf]

Is there anyway i can bring at least bluetooth back? Thanks for the help!

It’s best to use a wireless card that is natively supported in Monterey, but you can probably make your card functional by including the relevant kexts from OCLP. These kexts may also be included in Martin’s package, so you could get them from there as well if it’s more convenient.

 

[wyattaj25]

It’s best to use a wireless card that is natively supported in Monterey, but you can probably make your card functional by including the relevant kexts from OCLP. These kexts may also be included in Martin’s package, so you could get them from there as well if it’s more convenient.

Ah, understood. thanks a lot!

 

[wyattaj25]

Hey everyone, i have another problem that needs fixing. i have monterey running currently.

while trying to install windows 10, i followed all the steps of the guide above without issue. made it to the installation step, but when picking a hard drive, it gave me an error stating "we couldnt create a new partition or locste an existing one."

i saw someone said that a nvram reset would fix it, so i performed the reset.

alas, the reset did not fix the problem. i tried to boot back into monterey using opencore but everytime i tried to boot, it kernel panicked and brought me back to opencores boot picker.

i can access monterey again via opencore legacy patcher.

any idea on how to fix either of these issues? should i redo the opencore install? should i try windows 11 instead of windows 10?

 

[Macschrauber]

Hey everyone, i have another problem that needs fixing. i have monterey running currently.

while trying to install windows 10, i followed all the steps of the guide above without issue. made it to the installation step, but when picking a hard drive, it gave me an error stating "we couldnt create a new partition or locste an existing one."

i saw someone said that a nvram reset would fix it, so i performed the reset.

alas, the reset did not fix the problem. i tried to boot back into monterey using opencore but everytime i tried to boot, it kernel panicked and brought me back to opencores boot picker.

i can access monterey again via opencore legacy patcher.

any idea on how to fix either of these issues? should i redo the opencore install? should i try windows 11 instead of windows 10?

You should follow the instructions in post 1 about Windows.

Take care to don't get certificates. Backup the firmware first (see the signature for my tool).

Another (more easy) variant is here: https://forums.macrumors.com/thread...ith-boot-camp-assistant.2386309/post-32087274

 

[Gustav Holdoff]

Just updated macOS 12.7.6 with some difficulties
using OC 1.0.0 and a modified config (method 2)
during the update download the computer rebooted - and during the reboot the macOS option disappeared.
only the Windows option remained
I reset SMS and NVRAM, rewrote EFI OC to version 0.9.9 with the same config edited for the update and repeated the update download
this time the update download lasted longer than the first time and the update was correct
I rewrote EFI again to version 1.0.0
the computer is working normally
I don't understand what it was, because the configs for the update are absolutely identical for 1.0.0 and 0.9.9
if the reason was not in particular OC versions, then maybe something was written in my NVRAM that required a reset

 

[MacintoshDude24]

Hi, I have Monterey 12.6.1 installed with OC 0.8. and config version 02 of MartinLo's. I keep having a problem with a FF800 sound card connected by firewire. The only time it has worked correctly has been when installing the OS from scratch, then when shutting down and restarting if I use it as a sound device in any program, a feedback sound is produced in all the outputs, other times it plays jumpy and with glitter. However with a firewire hard drive or even a firewire connected RME UFX everything works fine. Also comment that it is not a problem with the sound card, since if I connect it to a Macbook Pro with an official installation of Monterey it works perfectly. Any help or comments on this topic?
I don't know if I should create a post just for this, if you think it's relevant I'll make a new post.
Greetings.
Thank you

Hi, I have exactly the same issue. Did you ever find a solution?
Thanks
McD

 

[Conzpiral]

Hi, I have exactly the same issue. Did you ever find a solution?
Thanks
McD

How old is your FF800, running latest firmware on it? I had to service a unit back in 2014 I used to own, and do a hardware mod to be able to run latest firmware without clicks or something... Check e.g. RME forum here.