Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

mitch751

macrumors newbie
Jun 1, 2011
5
2
Is that possible to have two or several Opencore patched macOS on seperate hard drives on my Mac Pro 5.1 ?
 

joevt

macrumors 604
Jun 21, 2012
6,968
4,262
Is that possible to have two or several Opencore patched macOS on seperate hard drives on my Mac Pro 5.1 ?
Yes. Also, same hard drive different partitions. You'll want to use methods to tell them apart though (different icons, names, colors...)
 

sfalatko

macrumors 6502a
Sep 24, 2016
642
365
Yes, I mean GPU assisted h264/5 endoding
See @tsialex reply above - which is why I asked my question. Set your device property in your config.plist so your graphics card shows up as "AMD...." and I expect Videoproc will then report that your acceleration is working.
 

ridgwel

macrumors newbie
Dec 14, 2021
11
0
Yes. Also, same hard drive different partitions. You'll want to use methods to tell them apart though (different icons, names, colors...)
Maybe you, or anyone reading this post, can help me. I have two HD in my 2012 Mac Pro 5,1 w/metal GPU, both are NVMe ..... one is High Sierra and the other I've used OCLP 0.4.2 to install Big Sur. I have OCLP loaded on the Big Sur. After installing Big Sur, I then force booted ("option" key) the High Sierra drive, which is a native install. Everything went as expected for High Sierra. I then tried to "option" boot back into the Big Sur HD using "EFI" placed on Big Sur......I got the "circle with a slash". The mac no longer recognized Big Sur.

To get back into Big Sur I had to re-install with USB. Once install is finished, everything works as designed. Then after I restart into High Sierra then back to Big Sur......that dreaded "circle with a slash" occurs and I have to re-install to get Big Sur back.

I know I must be doing something wrong or I am lacking something when I install. I thought maybe you could help.
 

Macschrauber

macrumors 68030
Dec 27, 2015
2,983
1,489
Germany
Add -no_compat_check to the boot-args and boot HS via OpenCore.

Also set LauncherOption to Disabled if you have a bootscreen GPU, its easier to do a native HS boot with the native boot picker that way.
 
  • Like
Reactions: NC12

ridgwel

macrumors newbie
Dec 14, 2021
11
0
Add -no_compat_check to the boot-args and boot HS via OpenCore.

Also set LauncherOption to Disabled if you have a bootscreen GPU, its easier to do a native HS boot with the native boot picker that way.
Okay.....but where are the "boot-args"? And how do you boot via OpenCore? I'm sorry I'm such a newbie.....so I do require a little more education.

I do have a bootscreen GPU (Radeon HD 7950 - Mac Ed). I went thru this screen to boot the High Sierra HD.
 

paalb

macrumors 6502
Dec 17, 2019
257
180
How do I move the OpenCore from an EFI partition to another EFI partition on another hard drive?
Look at Basic Setup in first post. You can mount both with the commands shown there and move it over. Then follow the instructions to bless.
 
  • Like
Reactions: Jegriva

joevt

macrumors 604
Jun 21, 2012
6,968
4,262
Maybe you, or anyone reading this post, can help me. I have two HD in my 2012 Mac Pro 5,1 w/metal GPU, both are NVMe ..... one is High Sierra and the other I've used OCLP 0.4.2 to install Big Sur. I have OCLP loaded on the Big Sur. After installing Big Sur, I then force booted ("option" key) the High Sierra drive, which is a native install. Everything went as expected for High Sierra. I then tried to "option" boot back into the Big Sur HD using "EFI" placed on Big Sur......I got the "circle with a slash". The mac no longer recognized Big Sur.

To get back into Big Sur I had to re-install with USB. Once install is finished, everything works as designed. Then after I restart into High Sierra then back to Big Sur......that dreaded "circle with a slash" occurs and I have to re-install to get Big Sur back.

I know I must be doing something wrong or I am lacking something when I install. I thought maybe you could help.
If you only Option boot into High Sierra, then the next reboot should have gone back to OpenCore as usual (unless you did some Startup Disk or bless or other nvram stuff in High Sierra).
But in that case, option booting into EFI Boot for Open Core should have worked and booted the default option for that. But OCLP should show the menu for a couple seconds so you can see if it is going to boot Big Sur, and you can use the arrow keys to select Big Sur if it's not set to the default. Now, if not option booting doesn't get you to Open Core and Big Sur automatically, then you must option boot and hold the control key first the EFI Boot option, then use control key to boot Big Sur. Then the next boot should get to Big Sur without holding any keys.
 

ridgwel

macrumors newbie
Dec 14, 2021
11
0
If you only Option boot into High Sierra, then the next reboot should have gone back to OpenCore as usual (unless you did some Startup Disk or bless or other nvram stuff in High Sierra).
But in that case, option booting into EFI Boot for Open Core should have worked and booted the default option for that. But OCLP should show the menu for a couple seconds so you can see if it is going to boot Big Sur, and you can use the arrow keys to select Big Sur if it's not set to the default. Now, if not option booting doesn't get you to Open Core and Big Sur automatically, then you must option boot and hold the control key first the EFI Boot option, then use control key to boot Big Sur. Then the next boot should get to Big Sur without holding any keys
High Sierra HD boot up process has not been molested. I agree that option booting into EFI for OCLP should work, and it does if I have not booted into High Sierra just ahead of it. For some reason after booting into High Sierra, the only HD that gets recognized is that drive. I can get to the Option Booting of OCLP just fine, selecting the EFI Boot puts me in another screen where I can select HS or BS. Selecting BS give me the slashed circle......the only solution to get back to BS is reinstalling BS.

I was giving some advice in #10,432 above. I haven't tried that yet because after reviewing the beginning thread....I'm still lost. If you don't mind, could you look at that advice and covert it newbie language. I really don't want to take advantage of anyone's time, but you seem to be willing to help. If you don't have time......that's okay, I appreciate your effort to help. Thanks
 

aviator84

macrumors newbie
Feb 27, 2022
3
1
Hello. I was hoping someone might be able to help me. I have a 2009 mac pro 4,1 that was updated the 5,1. It has a 6core xeon processor and a msi radeon r9 280x graphics card. The graphics card was flashed so it has boot screen support. I installed opencore using the legacy patcher and have Big Sur currently installed along with my native boot mojave. Following the guide I then installed windows 10.(all operatiing systems are on seperate drives) Both Mojave and Big Sur run great without any issues. My problem is windows 10. I have it installed and can boot into it from opencore. The problem is windows is only running on the stock windows display drivers. I've tried several different ways to install drivers for my graphics card but every time I do part way through the install windows crashes. After that I can try to relaunch windows; and I get to the windows boot screen and then it will just crash again.(Won't make it to the login screen) Is there something within opencore or the config file that I need to update or modify to get my graphics card working? I've tried both stock amd drivers and radeon drivers from bootcamp drivers .com everything seems to cause windows to crash. At this point I can't even load my wifi drivers and connect to the internet because the system tries to find drivers for the graphics card(and I guess it does) because the system will crash once it tries to install them.
 

joevt

macrumors 604
Jun 21, 2012
6,968
4,262
High Sierra HD boot up process has not been molested. I agree that option booting into EFI for OCLP should work, and it does if I have not booted into High Sierra just ahead of it. For some reason after booting into High Sierra, the only HD that gets recognized is that drive. I can get to the Option Booting of OCLP just fine, selecting the EFI Boot puts me in another screen where I can select HS or BS. Selecting BS give me the slashed circle......the only solution to get back to BS is reinstalling BS.

I was giving some advice in #10,432 above. I haven't tried that yet because after reviewing the beginning thread....I'm still lost. If you don't mind, could you look at that advice and covert it newbie language. I really don't want to take advantage of anyone's time, but you seem to be willing to help. If you don't have time......that's okay, I appreciate your effort to help. Thanks
Do you have normal boot screen with your GPU so that option booting is actually happening in Apple's boot picker instead of OpenCore?
Do you have -v in the boot-args in the OpenCore config.plist so maybe it can show what the slashed circle is waiting for?
 

ridgwel

macrumors newbie
Dec 14, 2021
11
0
Do you have normal boot screen with your GPU so that option booting is actually happening in Apple's boot picker instead of OpenCore?
Do you have -v in the boot-args in the OpenCore config.plist so maybe it can show what the slashed circle is waiting for?
Yes, I do have a normal boot screen with the GPU. That's how I selected the High Sierra HD.
Now you reached a point I need clarification on to ensure that I'm doing it right. I access the config.list by mounting the EFI, then create a line with "-v"?
I'm sorry I'm not a more knowledgeable, but I do appreciate your patience....I am learning.
 

ridgwel

macrumors newbie
Dec 14, 2021
11
0
Do you have normal boot screen with your GPU so that option booting is actually happening in Apple's boot picker instead of OpenCore?
Do you have -v in the boot-args in the OpenCore config.plist so maybe it can show what the slashed circle is waiting for?
Joevt,
I have stumbled onto a solution. I reset NVRAM 3 or 4 times, I selected "allow native models" in OCLP, and "Control" selected "Big Sur" in OCLP Boot Screen. I can now select the High Sierra HD thru Mac Native Boot Screen then when I select "Restart", the Mac boots thru OCLP into Big Sur. (I figured that "allow native models" meant the same as "-no_compat_check to the boot-args".....don't know if it does or not, but it worked)

But I do want to thank you for your input, you're a good man!
 

lewnworxx

macrumors member
Mar 19, 2015
84
10
Hi all.

I'm having some challenges with the latest OC. I've done the entire process previously, hand building the config plist per the instructions on a different machine back in July of last year without incident and have been running Big Sur 11.2.3 (prior to the fix for the race conditions and I haven't updated that yet).

This go round has been very problematic. I've got a Mojave install on SSD as my base bootable, the hardware config is identical to the other machine down to the dual 3.46 6 cores, 96gb ram, Saphire Pulse Rx 580, the whole bit.

However, when I select my Mojave drive post OC boot picker, I get the circle with a slash through it and it won't boot.

My Monterey USB installer is selectable, it does boot, yet my neither my Mojave SSD nor my freshly initialized SSD for the Monterey install are selectable. The only location the installer will give me to put Monterey on is the USB installer, neither the Mojave SSD nor the empty Monterey target SSD even show up.

I've tried this both with the generic config plist linked at the end of the first post, as well as a fully built one which has the Lilu / WhateverGreen / Sir Plus / Feature unlock and all the other suggested adds from the first post (which outside of the Sur Plus addition are pretty much identical to my build on the other box).

Further I have to pull the Monterey SSD (which is where I've landed the OC install) in order to even boot back to Mojave, as booting into recovery and setting the Mojave install as the boot drive doesn't work, nor does attempting to bless the Mojave drive via terminal (and it's possible I may not be doing that bit correctly).

This is pretty puzzling as my first install last July on another machine was pretty flawless.

The only thing different from my first install I'm currently using the Mac Pro ID, as in the first post suggested that for Monterey installs, and the previous one I'd used the iMac Pro ID (I think).

Any insights? config Plist attached.

Thanks..
 

Attachments

  • config.plist.zip
    4 KB · Views: 58

lewnworxx

macrumors member
Mar 19, 2015
84
10
2019 Mac Pro is only supported after 10.15.1. OC with MP7,1 spoofing will only boot Mojave if you add -no_compat-check to the boot-args.
I think it's in there, unless I've got it in the wrong section:

<key>NVRAM</key>
<dict>
<key>Add</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<dict>
<key>boot-args</key>
<string>-no_compat_check</string>
</dict>
</dict>
<key>Delete</key>
<dict>
<key>7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
<array>
<string>boot-args</string>
</array>
</dict>
<key>LegacyEnable</key>
<false/>
<key>LegacyOverwrite</key>
<false/>
<key>LegacySchema</key>
<dict/>
<key>WriteFlash</key>
<false/>
</dict>
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.