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

[mrkapqa]

Hello friends,

have on mp5,1 the setup monterey-mojave-mavericks-win11 , and it functions quite well, thanks to m.lo 0.8.8 package!

today i installed via oclp ventura over monterey, but it would not boot via m.lo OC, only via OCLP OC setting, which at the moment, i have only installed on the USB installer for Ventura, and am wary to install it on disk, since i dont have good experience with it and it prevented me in the past to boot from older Macos.

question: what can i do on M.Lo Package 0.8.8 to enable booting the Monterey now VenturaOS from NVME properly via Opencore?

thanks!

 

[tsialex]

question: what can i do on M.Lo Package 0.8.8 to enable booting the Monterey now VenturaOS from NVME properly via Opencore?

No. Only OCLP supports Ventura via root patching and it's alpha support. Btw, this is not a OCLP support thread, you should go to the OCLP Discord server or the thread below:

https://forums.macrumors.com/threads/macos-13-ventura-on-unsupported-macs-thread.2346881/

 

[mrkapqa]

thanks, i don't need it then, that will account for an unsuccesful upgrade.

EDIT: which is the best way to install Monterey then?
i used OCLP to install it, but then booted via M.Lo package; but after some time, Monterey shows a "hash mismatch error - "
is there a another way to install Monterey on a Mp5,1?

 

[cdf]

Monterey shows a "hash mismatch error - "

This might be of interest:

https://forums.macrumors.com/threads/activate-amd-hardware-acceleration.2180095/post-31899510

 

[motiontrack]

Opencore noob here; I'm using a Mac Pro 5,1 and recently put Martin Lo's latest Opencore package in a 120 GB SSD drive to test and update to Catalina. Love it thus far.

I now want to do a clean install of Big Sur to a new 1TB SSD (as I don't have enough space on the 120GB) and don't want to mess up my OC operation and config. To do this without issues, I have a few questions I wanted to verify the workflow I'm thinking about with this group:

• Do I need to edit the config playlist in any way before I begin? e.g. VMM? and would I need to change it back after I'm done?
• Can I then clean install Big Sur from my 120 GB drive to the AFFS formatted 1TB drive?
• Once installation to new drive is successful, can I then copy and paste the OC EFI on the 120GB to the 1TB drive EFI
• then can I remove OC on 120GB SSD and remove the drive itself – will my OC carry over without issue now that it would be on the 1TB EFI folder?
• Are there any post install things I should do as it relates to OC – e.g. should I do a PRAM reset?
• Would Bluetooth/WIFI be available in Big Sur (even using a config playlist patch) - I have the original BT/WF card in my Mac Pro 5,1 and want to avoid having to buy/install a newer one.

Some additional related questions – tried reading through what's online but haven't really gotten a concise answer:

• Does having two OC's (with the same config playlist) on different drives cause issues, even if its just for a limited time (before I remove one of the drives)
• I have a non-flashed RX580 graphics card installed; would lack of bootscreen cause any issues when installing Big Sur, or at any point in this workflow?
• If a non-supported MacOS is clean-installed onto the drive that has OC on it, would it wipe OC and cause issues (e.g. the install would fail because it realizes it’s a cMP 5,1 versus a supported model) – would a workaround for this be to move the OC to a USB or another drive (similar to one of my earlier questions)

Lots of questions, I know. Thank you for any answers / advice anyone can provide in advance! Happy to read through any existing materials if someone can point me in the right direction.

 

[h9826790]

Do I need to edit the config playlist in any way before I begin? e.g. VMM? and would I need to change it back after I'm done?

Yes, if that's my pre-configured OC.

Can I then clean install Big Sur from my 120 GB drive to the AFFS formatted 1TB drive?

Can

Once installation to new drive is successful, can I then copy and paste the OC EFI on the 120GB to the 1TB drive EFI

Can, but you need to bless the new copy if you want to boot from that copy

then can I remove OC on 120GB SSD and remove the drive itself – will my OC carry over without issue now that it would be on the 1TB EFI folder?

Can. In this case, if the 1TB drive is the only boot drive, even you haven't bless it, the cMP should switch from the 120GB OC to the new 1TB OC automatically. (But I still recommend you bless the new one before you remove the old one)

Are there any post install things I should do as it relates to OC – e.g. should I do a PRAM reset?

If everything is working, do not reset NVRAM. And there is no need to do any extra reset if you just want to move to a higher capacity boot drive.

Would Bluetooth/WIFI be available in Big Sur (even using a config playlist patch) - I have the original BT/WF card in my Mac Pro 5,1 and want to avoid having to buy/install a newer one.

Users reported that BT should work if you turn on the associated kext in the config. But the report was mixed, some other seems can never get it work. I think you better try that on you 120GB drive (after you get the 1TB drive working correctly).

Does having two OC's (with the same config playlist) on different drives cause issues, even if its just for a limited time (before I remove one of the drives)

No, I have three OC copies on my cMP now, the 2nd and the 3rd are just backup. If I remove my primary boot drive, my cMP should boot from the 2nd / 3rd copy automatically.

I have a non-flashed RX580 graphics card installed; would lack of bootscreen cause any issues when installing Big Sur, or at any point in this workflow?

If that's with the factory PC ROM, OpenCore should able to make it shows boot screen via UEFI GOP. And even no boot screen, it shouldn't affect your macOS installation.

If a non-supported MacOS is clean-installed onto the drive that has OC on it, would it wipe OC and cause issues (e.g. the install would fail because it realizes it’s a cMP 5,1 versus a supported model) – would a workaround for this be to move the OC to a USB or another drive (similar to one of my earlier questions)

Not an issue for macOS.

 

[motiontrack]

Thank you for the quick reply. Sounds like I'm on the right track. Just a few things i want to clarify:

You said ' you need to bless the new copy if you want to boot from that copy'. Can i bless the 1TB Big Sur drive from the original 120gb Catalina OC drive. If so how would i do that? Or do I have to boot into and bless it from the 1TB big sur drive once ive copied over the efi to it?


You said you had three instances of OC on your cMP. Are all of them the same configs.i assume if you remove one say from bay 1, it will boot OC from bay 2 and so forth but adopt whatever config the next OC in line has?

For my last question you said not a problem for macos. So if i understand correctly, once an unsupported OS is installed via OC on the cMP, even after OC is removed from the system, the macos continues operating? Though you will lose things like hw acceleration and boot screen?

Thanks again!

 

[flaubert]

Thank you for the quick reply. Sounds like I'm on the right track. Just a few things i want to clarify:

You said ' you need to bless the new copy if you want to boot from that copy'. Can i bless the 1TB Big Sur drive from the original 120gb Catalina OC drive. If so how would i do that? Or do I have to boot into and bless it from the 1TB big sur drive once ive copied over the efi to it?


You said you had three instances of OC on your cMP. Are all of them the same configs.i assume if you remove one say from bay 1, it will boot OC from bay 2 and so forth but adopt whatever config the next OC in line has?

For my last question you said not a problem for macos. So if i understand correctly, once an unsupported OS is installed via OC on the cMP, even after OC is removed from the system, the macos continues operating? Though you will lose things like hw acceleration and boot screen?

Thanks again!

Blessing a drive is generally done via booting into a recovery partition and typing a few commands into Terminal; it doesn't really depend on what OS version the recovery partition is associated with (in other words, could be Mojave, Catalina, Big Sur, Monterey) or even what OpenCore installation got you booting into the recovery partition. Selecting the recovery partition to boot into is usually done through OpenCore, which can present you with a graphical set of disks/partitions to select from; there is a key press that I can never quite remember to get the full list (spacebar?), so I always just set OpenCore to show me all of them. See the first post of this thread for the details on how to bless a drive, and how to tweak what OpenCore shows you at boot.

Multiple instances question: Yes, if it has to progress to the next OpenCore installation on another disk it will of course use whatever the plist in that OC says to do.

For your last question the answer is NO. Once you have an unsupported OS installed you must always boot through OpenCore, lest you get the dreaded "do not enter" symbol. I believe that what @h9826790 meant by "not a problem for MacOS" is that even a clean install of MacOS will not wipe out the EFI partition holding OpenCore - the new OS install goes onto another partition of the disk. I believe you can wipe out the EFI partition if you erase the enclosing disk device (top level entity) in Disk Utility, so you want to be careful in what you select for erasing.

 

[h9826790]

Can i bless the 1TB Big Sur drive from the original 120gb Catalina OC drive. If so how would i do that?

Can

how would i do that?

Mount ONLY the EFI partition of the 1TB drive, then run the bless tool.

If multiple EFI partition already mounted, eject them all, then re-mount the 1TB's EFI partition before you run the bless tool.

 

[Gustav Holdoff]

I daily and periodically check the operation of my cMP for the correct operation of hardware and programs
after upgrading to 12.6.3, obviously something has changed in the system with my cmp
non-stop kernel task before the update was about 5%
after the update it became 12%
From my experience I can guess the following:
Apple changed something in the operation of the system, focusing on ARM processors,
I can give an example: a few months ago I installed an AI addon for blender, which for macos was written only for the arm processor - after installing this addon, macOS stopped working correctly - a kernel task appeared
I had to uninstall AI addon and reinstall the macos
the second time I got a similar problem, when I didn’t notice that I installed the blender update not for macos-intel, but for macos-arm - after starting and turning off this version of blender, I received non-stop kernel task 10%
nvram reset canceled the process, but if I turned on the blender, then the kernel task remained even after the reboot, which means the programs for arm are doing something with the macos
I uninstalled blender and installed the intel version - everything was ok

And yesterday, I checked all the processes
kernel task was 4%
updated the macos - everything seemed to be ok
but today I have a permanent kernel task 12%
resetting nvram does not change anything - the process is not deleted
what is the difference between yesterday and today: yesterday macos 12.6.2
and today 12.6.3

EDETED
multiple deep reset nvram and smc helped-

something in the work of my hardware, software, system and maybe kexts or video cards with whatevergreen affect my work

 

[h9826790]

I daily and periodically check the operation of my cMP for the correct operation of hardware and programs
after upgrading to 12.6.3, obviously something has changed in the system with my cmp
non-stop kernel task before the update was about 5%
after the update it became 12%
From my experience I can guess the following:
Apple changed something in the operation of the system, focusing on ARM processors,
I can give an example: a few months ago I installed an AI addon for blender, which for macos was written only for the arm processor - after installing this addon, macOS stopped working correctly - a kernel task appeared
I had to uninstall AI addon and reinstall the macos
the second time I got a similar problem, when I didn’t notice that I installed the blender update not for macos-intel, but for macos-arm - after starting and turning off this version of blender, I received non-stop kernel task 10%
nvram reset canceled the process, but if I turned on the blender, then the kernel task remained even after the reboot, which means the programs for arm are doing something with the macos
I uninstalled blender and installed the intel version - everything was ok

And yesterday, I checked all the processes
kernel task was 4%
updated the macos - everything seemed to be ok
but today I have a permanent kernel task 12%
resetting nvram does not change anything - the process is not deleted
what is the difference between yesterday and today: yesterday macos 12.6.2
and today 12.6.3
View attachment 2148480 View attachment 2148481

I just check my Activity Monitor, no such issue. Kernel Task stay at ~2% when I do nothing but just watching Activity Monitor in 12.6.3.

So, I guess you installed something which trigger a higher Kernel Task demand. But TBH, 10% isn't that significant, very hard to say if that means something wrong deep inside the OS.

And I don't think this is OpenCore realated at this moment.

 

[hwojtek]

From my experience I can guess the following:
Apple changed something in the operation of the system, focusing on ARM processors,

If the kernel was upgraded, perhaps it simply launches more processes.

I can give an example: a few months ago I installed an AI addon for blender, which for macos was written only for the arm processor - after installing this addon, macOS stopped working correctly - a kernel task appeared

This shouldn't install at all, but OK.

I had to uninstall AI addon and reinstall the macos

If your MacOS theory was correct, uninstalling the AI addon alone would bring things back to where they were before. No ARM code, no reason to spin more kernel tasks up.

the second time I got a similar problem, when I didn’t notice that I installed the blender update not for macos-intel, but for macos-arm - after starting and turning off this version of blender, I received non-stop kernel task 10%

How were you able to start an ARM application? Not only it has a circle/slash sign on the icon to display it will not run, but it will just not run. MacOS will display an error and the app will never start so it can not do anything to the OS.

nvram reset canceled the process, but if I turned on the blender, then the kernel task remained even after the reboot, which means the programs for arm are doing something with the macos

This means there are probably leftover bits and libraries that you didn't uninstall and MacOS tries to load them but stumbles upon some code that does not function. This said, I don't think anything is wrong with the OS itself.

And yesterday, I checked all the processes
kernel task was 4%

Solid?

but today I have a permanent kernel task 12%

Again, stuck at 12? It should be varying between 1 and anything. And this does not indicate anything is wrong.

resetting nvram does not change anything - the process is not deleted

NVRAM reset will not help with launching processes.

what is the difference between yesterday and today: yesterday macos 12.6.2
and today 12.6.3

Just don't bother.

 

[antonlinus]

so i ended up deleting the whole macOS install and did a fresh install of Win11 on a SATA SSD (which worked before i reassembled my MacPro and put in the Nvme PCIe Card and the Titan Ridge). As cdf suspected that wasn't what was causing Win11 not to boot after following the steps in post#1.
I'm sorta burnt out now and sick of wasting my time.

As you might have read i've had a small breakdown over the last few days trying to clean install my cMP with the latest OC a backup Mojave, a main macOS Monterey and a Win11 UEFI partition.
Its been a ton of (sometimes preventable) mistakes and reinstalls with plenty of dis- and reassembling parts of my cMP.

Yesterday i managed to do a completely build from scratch install of OC meticulously following cdf's post#1 tutorial step by step only including tghe kexts and drivers ect. i would need for my specific hardware. For macOS everything works perfectly everything works including Bluetooth, Hybernation, Thunderbolt ect. THANKS A BUNCH for all the sick work developping this!

As for the Windows the problem remains: If i try booting with my hardware fully assebled it will get stuck after a few seconds on the Windows bootscreen + static circular loading indicator. I can definitely say that it has something to do with my Sonnet M.2 4x4 Nvme PCIe Card that i have installed in slot 1 (bottom most) in my cMP. Windows is installed on a SATA SSD in Bay2. It does'nt matter if there are drives installed in the Sonnet card or not, Windows won'T boot with it installed. When i take it out it boots just fine...

Anyone here has this card and or tipps to get this working? I did have a fully working install of this before so i know that there is a way but i might have used a legacy install of Windows i'm not sure...

thanks a lot!

 

[tommy chen]

I daily and periodically check the operation of my cMP for the correct operation of hardware and programs
after upgrading to 12.6.3, obviously something has changed in the system with my cmp
non-stop kernel task before the update was about 5%
after the update it became 12%
From my experience I can guess the following:
Apple changed something in the operation of the system, focusing on ARM processors,
I can give an example: a few months ago I installed an AI addon for blender, which for macos was written only for the arm processor - after installing this addon, macOS stopped working correctly - a kernel task appeared
I had to uninstall AI addon and reinstall the macos
the second time I got a similar problem, when I didn’t notice that I installed the blender update not for macos-intel, but for macos-arm - after starting and turning off this version of blender, I received non-stop kernel task 10%
nvram reset canceled the process, but if I turned on the blender, then the kernel task remained even after the reboot, which means the programs for arm are doing something with the macos
I uninstalled blender and installed the intel version - everything was ok

And yesterday, I checked all the processes
kernel task was 4%
updated the macos - everything seemed to be ok
but today I have a permanent kernel task 12%
resetting nvram does not change anything - the process is not deleted
what is the difference between yesterday and today: yesterday macos 12.6.2
and today 12.6.3
View attachment 2148480 View attachment 2148481

the first thing I would do is uninstall WD discovery and WD discovery helper!

 

[Gustav Holdoff]

If the kernel was upgraded, perhaps it simply launches more processes.

This shouldn't install at all, but OK.


If your MacOS theory was correct, uninstalling the AI addon alone would bring things back to where they were before. No ARM code, no reason to spin more kernel tasks up.


How were you able to start an ARM application? Not only it has a circle/slash sign on the icon to display it will not run, but it will just not run. MacOS will display an error and the app will never start so it can not do anything to the OS.


This means there are probably leftover bits and libraries that you didn't uninstall and MacOS tries to load them but stumbles upon some code that does not function. This said, I don't think anything is wrong with the OS itself.


Solid?


Again, stuck at 12? It should be varying between 1 and anything. And this does not indicate anything is wrong.


NVRAM reset will not help with launching processes.


Just don't bother.

yes, I'll explain briefly
indeed, the AI addon is installed using python scripts, and yes, libraries are additionally installed, which are precisely the cause of the system freezing
as for the blender for arm, I successfully installed and I rendered on it until I found that it renders slower - I uninstalled the version and reinstalled the intel version

about the current situation
I once again reseted nvram and smc
turned off the computer from electricity for half a day
disconnected ram and tray
while the kernel task in activity monitor returned to normal

I don’t know - in my experience, when working in Macos and sometimes when working in Windows, something accumulates - I don’t know where, maybe in the buffers of the video card, maybe somewhere in the memory - I’m not an expert in the system
but sometimes, when a kernel task occurs on my hardware configuration, I have to monitor and periodically reset nvram
maybe everything is to blame - usb card, maybe nvme disks, I don’t know
maybe program libraries - I don't understand
maybe kexts and video card
I don't know but that's what happens to me
but if I decide to render scenes in Windows, since twinmotion in Windows renders heavy scenes for me at least 2 times faster than on Macos
then from the frequent switching of macos / windows, various failures occur - sometimes windows does not load - it just freezes, then kernel tasks appear in macos sometimes in idle mode 40-50 or even 60%

 

[hwojtek]

as for the blender for arm, I successfully installed and I rendered on it until I found that it renders slower - I uninstalled the version and reinstalled the intel version

So you installed an universal binary. No ARM code was run whatsoever.

about the current situation
I once again reseted nvram and sip
turned off the computer from electricity for half a day
disconnected ram and tray

Nothing of what you have done has anything to do with ARM code or kernel processes.
It's like you hear a noise in your car, so you tear it apart to pieces and build again, only to find out the noise was from a door that has not been fully closed.

I don’t know - in my experience, when working in Macos and sometimes when working in Windows, something accumulates - I don’t know where, maybe in the buffers of the video card, maybe somewhere in the memory

If it was like this, a reboot would get rid of it. No, it's impossible to "store" something in no buffers nor plant something into RAM so it haunts you unless you reinstall the RAM.
I assume you have some randomly installed exotic scripts/plugins, some of them taking an unusual or just less than recommended approach to the system and this leads to a more or less unstable system. You then reinstall the OS, bring back everything you needed from a backup, introduce same errors and the circle is closed.

but sometimes, when a kernel task occurs on my hardware configuration

What is with "kernel task occurs"? It has to run and consume CPU resources, otherwise it means your computer is turned off.

but if I decide to render scenes in Windows, since twinmotion in Windows renders heavy scenes for me at least 2 times faster than on Macos

This is because of driver performance in Windows.

then from the frequent switching of macos / windows, various failures occur

No, it's not like that.

just freezes, then kernel tasks appear in macos sometimes in idle mode 40-50 or even 60%

It means you keep adding something that bothers the kernel to your clean installs. Be it any hardware or software (my bet is on "almost compatible" hardware).
Anyway - disregard it. It does absolutely nothing to your computers performance.

 

[_LiveSorcerer_]

Sorry for the silly question but does Titan Ridge need power connection like Pixlas mod or not?
I installed Titan Ridge on my MacPro 5.1 2012, and I'm using OpenCore 0.8.8 on BigSur.
But when I start my Orico TB3 SSD M.2 , MacOS does not start, but when I disconnect it and start the system, MacOS starts working again.
Any idea?

 

[greenmeanie]

Anyone with a IMAC 13,1 have a solution to no sound/speakers being found when running OCLP/Ventura.

Figured it out after cleaning the headphone jack for 4 hours today. Factory sealed but somehow the cable popped off inside for the Headphone jack. Up and running again just for following this project.

 

[takobaba]

I have same log, but reboot again it not appear!

@MacHosehead @oldman32
Oh man mine is still there it's just annoying, dont know what it's telling. What is AAPL, it is a prefix for defined deviceproperties but thats all I can relate to. Anyone has any idea

00:000 00:000 AAPL: FileSetPosition:3108: FileSetPosition: attempt to set position for directory to 18446744073709551615
00:365 00:365 AAPL: FileSetPosition:3108: FileSetPosition: attempt to set position for directory to 18446744073709551615
00:391 00:026 AAPL: FileSetPosition:3108: FileSetPosition: attempt to set position for directory to 18446744073709551615

 

[joevt]

@MacHosehead @oldman32
Oh man mine is still there it's just annoying, dont know what it's telling. What is AAPL, it is a prefix for defined deviceproperties but thats all I can relate to. Anyone has any idea

00:000 00:000 AAPL: FileSetPosition:3108: FileSetPosition: attempt to set position for directory to 18446744073709551615
00:365 00:365 AAPL: FileSetPosition:3108: FileSetPosition: attempt to set position for directory to 18446744073709551615
00:391 00:026 AAPL: FileSetPosition:3108: FileSetPosition: attempt to set position for directory to 18446744073709551615

I think AAPL means the message originates from an Apple EFI driver instead of an Open Core EFI driver.

 

[antonlinus]

Sorry for the silly question but does Titan Ridge need power connection like Pixlas mod or not?
I installed Titan Ridge on my MacPro 5.1 2012, and I'm using OpenCore 0.8.8 on BigSur.
But when I start my Orico TB3 SSD M.2 , MacOS does not start, but when I disconnect it and start the system, MacOS starts working again.
Any idea?

It doesn’t need extra power it just needs to be flashed correctly, installed in slot 4 (top slot) and it needs a connection between port 3 and 5.

This guide helped a lot with this process:

thunderbolt-macpro-5-1/GC-TitanRidge.md at master · ameyrupji/thunderbolt-macpro-5-1

My story to add thunderbolt support to my Mac Pro Early 2009 (5,1) - ameyrupji/thunderbolt-macpro-5-1

github.com

Also if you boot with opencore you need to correctly install the Thunderbolt ssdt files. Check cdfs great tutorial for that in post#1

 

[tommy chen]

It doesn’t need extra power it just needs to be flashed correctly, installed in slot 4 (top slot) and it needs a connection between port 3 and 5.

as i always write, it's pin1 and 3 !

 

[g0lek]

Hello everybody.
I have a MacPro 4,1 ->5,1 with a Radeon RX5600 XT.
Opencore was installed, before 0.8, and Catalina as well as Windows 10 were running fine enough. I can't find out the exact version of oc I have but I tried running ocvalidate and it said it failed because it works only from 0.8
I started playing games on Windows recently (Detroit ...) and thought that maybe my oc install could be better for Windows 10 and the GPU.
Would Updating OpenCore give me potentially better perf from the GPU on Windows 10?
I doubt so, but if someone could confirm, or not, that would be great.

 

[prefuse07]

Hello everybody.
I have a MacPro 4,1 ->5,1 with a Radeon RX5600 XT.
Opencore was installed, before 0.8, and Catalina as well as Windows 10 were running fine enough. I can't find out the exact version of oc I have but I tried running ocvalidate and it said it failed because it works only from 0.8
I started playing games on Windows recently (Detroit ...) and thought that maybe my oc install could be better for Windows 10 and the GPU.
Would Updating OpenCore give me potentially better perf from the GPU on Windows 10?
I doubt so, but if someone could confirm, or not, that would be great.

Type this into Terminal:

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

 

[g0lek]

Type this into Terminal:

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version

REL-066-2021-02-02