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.
I have to say that I've been absurdly pleased with how well Monterey is running on my 2010 Mac Pro under OpenCore. So pleased, in fact, that I wrote up a description of my experience and submitted it to Allison Sheridan's podcast, "The Nosillacast." You can hear the podcast here, if you're interested:


My sincere thanks to @cdf, @Syncretic, @tsialex, @startergo, and the countless others who contribute to this little corner of the Mac computing world.
 
Is anyone using FileVault in Monterey? Any risks / downsides? Can it just be turned on, or are there any other considerations?

I'm using FileVault with Apple Secure Boot (j160) + ApECID enabled in OpenCore for maximum security and it works great! The only downside is a slight but not noticeable read/write performance penalty due to the encryption/decryption.

5.1 seems very sluggish on Monterey. 12c with 5700XT and 96GB of ram. Hmm... maybe a good idea to jump back to an earlier version?

Same setup but I have the opposite experience. I feel Monterey is faster and more responsive than Big Sur, especially when booting, loading applications (not sure - could be due to the apps being further optimized), running Parallels 17 with multiple VMs especially Windows 11, copying/deleting large number of files, network transfers especially with bonded (lacp) connections, faster iCloud syncs / AirDrop etc.
 
I'm using FileVault with Apple Secure Boot (j160) + ApECID enabled in OpenCore for maximum security and it works great! The only downside is a slight but not noticeable read/write performance penalty due to the encryption/decryption.



Same setup but I have the opposite experience. I feel Monterey is faster and more responsive than Big Sur, especially when booting, loading applications (not sure - could be due to the apps being further optimized), running Parallels 17 with multiple VMs especially Windows 11, copying/deleting large number of files, network transfers especially with bonded (lacp) connections, faster iCloud syncs / AirDrop etc.
Monterey is snappy for me as well in general but audio plugins in FCPX cause major issues, spinning beach ball etc usually having to force quit. FCPX runs ok but even the basic Apple AU channel EQ is very sluggish compaired to using the same version of FCPX in Big Sur.
 
I recently bought a new 27 inch monitor for my Mac Pro 5,1 but there seems to be an error where MacOS identifies it as a 32” monitor and stretches the boot screen and drive picker as seen in the 1st attached photo. When MacOS loads in then it fixes the resolution as seen in the 2nd attached photo. Is there any way to manually set open core’s resolution to resolve this?

The misidentified monitor :
8B7AD225-63BC-4409-8300-C46912D53F4A.jpeg


Before MacOS loads in :
10BABAE2-373E-40C6-BBE5-FB303CBD96D1.jpeg


After the resolution changes :

0F38DE9F-523A-4FB5-8552-E7FD41D646CF.jpeg
 
Hello All,

I have a MacPro mid 2010 with a flashed Titan Ridge 2.0. I’m looking to attach supplementary power to the card, My RX580 uses the 2 main power sources, but I’m thinking of using the optical drive power. Has anyone tried this? What kind of cable would be required?

Thanks
 
I recently bought a new 27 inch monitor for my Mac Pro 5,1 but there seems to be an error where MacOS identifies it as a 32” monitor and stretches the boot screen and drive picker as seen in the 1st attached photo. When MacOS loads in then it fixes the resolution as seen in the 2nd attached photo. Is there any way to manually set open core’s resolution to resolve this?

The misidentified monitor :
View attachment 1964714


Before MacOS loads in :
View attachment 1964712


After the resolution changes :

View attachment 1964713

This is normal Open Core behavior and nothing to worry about. Even if you set your resolution for Hi-DPI within your config, the same thing would still happen -- again, normal Open Core behavior.

FWIW, I have dual 27" LG 4K's (27UP850) and get the same thing in "Displays" showing it as a 31.5" I suspect it is because LG uses the same drivers for their 32" and 27" monitors, so this is also nothing to worry about.

Here is what my 'Displays' looks like:
Screen Shot 2022-02-25 at 10.41.24 PM.png


Hope that helps.
 
Last edited:
  • Like
Reactions: NC12 and 0134168
I successfully installed OpenCore and upgraded to Catalina but my hardware acceleration does not work. Where should I start to fix that. If there is a better thread to ask this question let me know. I'm brand new to all this. Thanks.
 

Attachments

  • Screen Shot 2022-02-26 at 11.19.52 AM.png
    Screen Shot 2022-02-26 at 11.19.52 AM.png
    190.3 KB · Views: 61
I successfully installed OpenCore and upgraded to Catalina but my hardware acceleration does not work. Where should I start to fix that. If there is a better thread to ask this question let me know. I'm brand new to all this. Thanks.
That card may be too new to be supported under Catalina (just a guess). You probably need Big Sur or Monterey.
 
  • Like
Reactions: TimothyR734
I successfully installed OpenCore and upgraded to Catalina but my hardware acceleration does not work. Where should I start to fix that. If there is a better thread to ask this question let me know. I'm brand new to all this. Thanks.
How do you know hardware acceleration is not working?
 
The VideoProc Converter app shows it's not enabled or available.
The only validation of VideoToolbox hardware assisted acceleration that VideoProc does is to check if the GPU model have a name starting with AMD. From the screenshot you posted earlier, yours don’t have. Rename it in the properties, see previous posts about this issue to know how to do it.
 
The VideoProc Converter app shows it's not enabled or available.
Without hardware acceleration, it is extremely obvious in just using the UI, everything is insanely slow.
The only validation of VideoToolbox hardware assisted acceleration that VideoProc does is to check if the GPU model have a name starting with AMD. From the screenshot you posted earlier, yours don’t have. Rename it in the properties, see previous posts about this issue to know how to do it.
That makes far more sense than there being no actual acceleration in the OS/no support. Thanks.
 
  • Like
Reactions: TimothyR734
So, by hardware acceleration you mean hardware acceleration of screendraws or GPU-assisted h264/5 encoding?
in my case, screendraws, the whole UI. I of course had zero hardware acceleration when I installed Monterey because there are no NVidia drivers included by default. It was pretty bad. Once I ran the OCLP patcher and got HW acceleration back, it was back to what we expect it to be like.
 
  • Like
Reactions: TimothyR734
I'm looking for some advice. Using OCLP 0.4.2 I installed Big Sur on a 2012 Mac Pro 5,1 with metal GPU. The install went okay and I was in Big Sur. But when I shut it down and then restarted, my Mac would not recognize my hard drive.....I got the big "circle with a slash". I re-ran the installer and it left me booted in Big Sur. But when I restarted, it again would not recognize the HD. Any suggestions I might try? Thanks in advance for your help.
 
I'm looking for some advice. Using OCLP 0.4.2 I installed Big Sur on a 2012 Mac Pro 5,1 with metal GPU. The install went okay and I was in Big Sur. But when I shut it down and then restarted, my Mac would not recognize my hard drive.....I got the big "circle with a slash". I re-ran the installer and it left me booted in Big Sur. But when I restarted, it again would not recognize the HD. Any suggestions I might try? Thanks in advance for your help.
did you apply the root patches?
 
did you try and reinstall open core
Okay, I reinstalled OCLP to the Big Sur HD. To restart, I had to go thru the "option" key at startup.....meaning, I couldn't just hit "restart" (when I did, I got a black screen). I had to select the EFI boot (that wasn't present before) to get back to Big Sur.

I have another HD installed that has High Sierra on it. I have one 32 bit app (Quicken 2007) that I have used as my checkbook for over a decade now and I will boot into when I need to. But getting back to Big Sur was a chore (I had to use my " Big Sur Install USB thumb drive" and go thru the "reinstall" procedure. But what I've got now, I can work around. I tried using the "Start Up" tab in System Pref, but when in High Sierra, it wouldn't recognize the Big Sur HD as an option.....now I have a work around.

Thanks for the suggestion......if you have any other ideas or suggestions, I would appreciate your feedback.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.