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.
Radeon HD 7950 is fully supported by Monterey.
My bad in that case. Don't know how/why I came to the conclusion all the HD 7xxx units were dropped after HiSierra.
Must be the FireWire fixes then.
 
My bad in that case. Don't know how/why I came to the conclusion all the HD 7xxx units were dropped after HiSierra.
Must be the FireWire fixes then.
Mojave dropped all the non-METAL Radeons, HD 4000 to 6000. Radeon HD 77xx, 78xx, 79xx are METAL supported GPUs.

One thing to be aware, HD 77xx and HD 78xx GPUs flashed with the Mac EFI extracted from Sapphire HD 7950 Mac Edition stopped to work after High Sierra, but it's a frame buffer related issue and flashing back the factory ROM makes Mojave to work with the GPU again. HD 7870 is a very common GPU to be flashed that stopped to work with Mojave, if still flashed with the incorrect Mac EFI.
 
"Must be the FireWire fixes then."
I think the same, any idea how to solve it, there has been one time that it worked correctly, but I don't remember what I did.
Greetings.
 
"Must be the FireWire fixes then."
I think the same, any idea how to solve it, there has been one time that it worked correctly, but I don't remember what I did.
Greetings.
One place to check is the OCLP Discord - it is apparently very active with many of the developers participating. That might be your best place to get assistance.
 
Hello, sorry for the error, it is Monterrey 12.5.1 that I have installed, the graphics card is fully compatible, it is Mac edition that works perfectly in Mojave and in Big Sur as well. The only problem I have with this installation is with the RME fireface 800 FireWire card, which although the system recognizes it perfectly when using it, I have feedback on all the output channels. For the rest, everything works correctly (I think that sharing the screen with the iPad does not work) but the universal control, bluetooth, wifi, etc...
hello, I just have the very same problem with my fireface 800 under Monterey on my Mac Pro. did you solved the problem with the feedback on all the output channels? I tried to reset totalmix and update the firmware but to no avail. your help is very much appreciated. thanks
 
Hi, I have a Mac Pro 2012 with SSD & AMD Vega 56 gpu flashed. I have Ventura installed. I have had no issues with Opencore Legacy Patcher up until recent. Ever since Opencore Legacy Patcher 0.6.2 I cannot properly patch my Vega 56 and so in turn runs extremely slowly. Everything works fine up to and including 0.6.1 but ever since then not. Has anyone else has this issue? I had to resort back to 0.6.1 for things to work properly again but cannot even upgrade passed Ventura 13.2. Please any input would be greatly appreciated
 
Likely this is the wrong place to put this, but the thread that is about OCLP captures a lot of discussion about Ventura but tends to be very sparse with respect to Mac Pro.

Currently I'm using OpenCore with MacOS 12.6.6 on a Mac Pro 2010 with a flashed RX 580 and an upgraded WiFi/Bluetooth with USB hub inline. Other stuff as well such as Thunderbolt, maxed out Xeons, etc.

My reading over time with respect to Ventura on MacPro 2010/2012 ranges from don't bother to works great. Which leaves me confused.

What issues remain with Ventura on this hardware? Is it worth the investment to move to Ventura?
 
Ventura runs on the cMP with:
- Full graphics acceleration
- Full hardware acceleration
- Handoff/Continuity with upgraded hardware
- Full USB support
- USB 3 PCIE support
- Unupgraded WiFi card support
Make of it what you will.
 
Ventura runs on the cMP with:
- Full graphics acceleration
- Full hardware acceleration
- Handoff/Continuity with upgraded hardware
- Full USB support
- USB 3 PCIE support
- Unupgraded WiFi card support
Make of it what you will.

Good summary.
Full USB support is not quite correct.
"Full" is only after Root Patching (i.e. after installation). During clean installs, internal USB 1.1 peripherals (e.g. bluetooth) do not work. For installs and Recovery, users need an external USB 2.0 hub into which wired keyboard and mouse must be attached.

Also, there are other issues too. See here regarding AVX support on older CPU's (e.g. Mac Pro's and Mac pre-Haswell).
 
  • Like
Reactions: h9826790 and Bmju
Pressed for time, but I believe the OCLP cited (links) represent things that can be worked around, including using an inline mini USB hub between an upgraded WiFi/BlueTooth card to mitigate he USB1.1 issue with respect to installs and recovery, as well as using an external hub for say keyboard and potentially mouse.

The AVX support is worrying. Though I really don't use voice assist as discussed in the other thread. Are there other applications that lean on AVX instructions?

I thought that Titan Ridge was supported. Thoughts?
 
Pressed for time, but I believe the OCLP cited (links) represent things that can be worked around, including using an inline mini USB hub between an upgraded WiFi/BlueTooth card to mitigate he USB1.1 issue with respect to installs and recovery, as well as using an external hub for say keyboard and potentially mouse.
Yes internal inline USB Hub solves the issues of allowing bluetooth to work during installs. I documented how I did my USB Hub project here for Mac Pro. That not so easy, for example, for MacBook's.

The AVX support is worrying. Though I really don't use voice assist as discussed in the other thread. Are there other applications that lean on AVX instructions?

Really Application dependent. Can't remember off-hand plist of Apps that crash.

I thought that Titan Ridge was supported. Thoughts?
🤷‍♂️ sorry I don't know
 
  • Like
Reactions: Bmju
For installs and Recovery, users need an external USB 2.0 hub into which wired keyboard and mouse must be attached.
For the cMP, do you need a hub or just a wired keyboard/mouse? Aren't the external USB ports all 2.0?

Nevermind: In addition to these devices being hard routed internally, like on MacBooks, Apple also wired up every USB port to switch between USB 1.1 and USB 2.0 controllers depending on the peripheral. So if a user plugs a mouse into a MacPro5,1, this will engage the legacy USB 1.1 controller. However if you plug a USB 2.0 hub into said MacPro5,1, this will start up the USB 2.0 controller allowing for native support in macOS.

 
Hi, I have a Mac Pro 2012 with SSD & AMD Vega 56 gpu flashed. I have Ventura installed. I have had no issues with Opencore Legacy Patcher up until recent. Ever since Opencore Legacy Patcher 0.6.2 I cannot properly patch my Vega 56 and so in turn runs extremely slowly. Everything works fine up to and including 0.6.1 but ever since then not. Has anyone else has this issue? I had to resort back to 0.6.1 for things to work properly again but cannot even upgrade passed Ventura 13.2. Please any input would be greatly appreciated
Any help on the above?
 
Your problem is that most of the people that know something about OCLP follow the Ventura thread and very few this. I understand it can be confusing since you got advice to go here, but I would follow @jgleigh ‘s advice. It might help to know that you got the advice from people that do not use OCLP and Ventura.
 
  • Like
Reactions: jgleigh
Hi, I have a Mac Pro 2012 with SSD & AMD Vega 56 gpu flashed. I have Ventura installed. I have had no issues with Opencore Legacy Patcher up until recent. Ever since Opencore Legacy Patcher 0.6.2 I cannot properly patch my Vega 56 and so in turn runs extremely slowly. Everything works fine up to and including 0.6.1 but ever since then not. Has anyone else has this issue? I had to resort back to 0.6.1 for things to work properly again but cannot even upgrade passed Ventura 13.2. Please any input would be greatly appreciated

AFAIK, OCLP do not support VEGA GPUs with Ventura, just Polaris.
 
The AVX support is worrying. Though I really don't use voice assist as discussed in the other thread. Are there other applications that lean on AVX instructions?

Really Application dependent. Can't remember off-hand plist of Apps that crash.
This could help: https://forums.macrumors.com/threads/looking-for-avx-avx2-software-failures.2283830/ - but I guess those programs are not filtered by 'crashes even with the OCLP cryptex patch applied' [search for 'Rosetta' or 'AVX' here]. Somewhere in OCLP blogs, issues, etc. I'm sure there is a list of what still doesn't work even with the patch...
 
  • Like
Reactions: MacNB2
@Sergey-Galan created a script for making a never booted legacy Windows installation from macOS itself. We need testers. If someone is willing to test it please see here:
Post in thread 'Installing Windows 10 in Legacy/BIOS mode in cMP with Boot Camp Assistant'
https://forums.macrumors.com/thread...ith-boot-camp-assistant.2386309/post-33174543

 
  • Like
Reactions: Macschrauber
hello, I just have the very same problem with my fireface 800 under Monterey on my Mac Pro. did you solved the problem with the feedback on all the output channels? I tried to reset totalmix and update the firmware but to no avail. your help is very much appreciated. thanks
Same as you and Salfuman but I'm running Big Sur via OCLP. Some times it works but mostly not. Thought it had to do with letting the kexts fulling loading so waited until activity monitor showed everything had loaded but worked for two days then stopped. Have tried multiple other options but can't get a stable system. It looks like everything has loaded in terms of the extensions and the FF800 is recognised (red host light ones out). But still get the digital feedback, sometimes the audio is there but jittery. Any suggestions would be appreciated.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.