I’ve ordered an NVME to PCIE adapter…the RIITOP that is recommended in the thread elsewhere on this forum. Going to try an install of Sequoia on that and we’ll see how it goes. Yes, I know will need an NVME drive, too. 😊
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Sequoia on the 5,1
- Thread starter flyproductions
- Start date
- Sort by reaction score
I've tried to get a "clean install" of Sonoma on this Mac Pro 3,1 and very frustrated. I can get it to boot, but cannot get Safari to upgrade to 18.4. And there is some weird stuff showing up in my Login apps. Taking a break until my new SSD shows up, when I will give Sequoia another shot. In the meantime, I just installed Linux Mint on a SATA SSD...having fun with it.
Hi - I am having problems with OCLP 2.3.1 on my cMP 5,1
Why 2.3.1? If I install/update the boot to 2.3.2 my mac will no longer boot Sequoia (prohibit sign). Also OCLP did not properly recognise my mac's hardware configuration (i.e. I replaced the original wifi/BT card) and will install kexts and config stuff that in Sequoia completely screws up bluetooth (but not wifi).
The worst problem I have though is this: if the screensaver kicks in and I deactivate it - keyboard or mouse activity - I instantly lose video and the fans rev up (I think the RX580's). If I reboot I will just get the mac started with no video and then sitting on a blank no video screen. If I reboot with option key (the firmware has enableGOP patch) I get a BLACK screen with three HDs and a "boot efi" - not the light grey screen that will usually appear in this case - and the resulting screen does not respond to mouse or keyboard. Left it 48 minutes longest time. Nothing. If I reboot witout option, same no video screen after chime.
To get video I need to clear NVRAM 4xchime and then start with option jey (now I get grey screen again) and this time the boot kicker works so I can startup to efi boot and boot Sequoia with OCLP.
I have turned off the screensaver, but I still get the no video black screen on normal startup sometimes.
Any way to address this?
Why 2.3.1? If I install/update the boot to 2.3.2 my mac will no longer boot Sequoia (prohibit sign). Also OCLP did not properly recognise my mac's hardware configuration (i.e. I replaced the original wifi/BT card) and will install kexts and config stuff that in Sequoia completely screws up bluetooth (but not wifi).
The worst problem I have though is this: if the screensaver kicks in and I deactivate it - keyboard or mouse activity - I instantly lose video and the fans rev up (I think the RX580's). If I reboot I will just get the mac started with no video and then sitting on a blank no video screen. If I reboot with option key (the firmware has enableGOP patch) I get a BLACK screen with three HDs and a "boot efi" - not the light grey screen that will usually appear in this case - and the resulting screen does not respond to mouse or keyboard. Left it 48 minutes longest time. Nothing. If I reboot witout option, same no video screen after chime.
To get video I need to clear NVRAM 4xchime and then start with option jey (now I get grey screen again) and this time the boot kicker works so I can startup to efi boot and boot Sequoia with OCLP.
I have turned off the screensaver, but I still get the no video black screen on normal startup sometimes.
Any way to address this?
Last edited:
What mess!
Start over from Mojave and make sure you take out all the drives, except the main drive you are using for the OS.
I have Monterey, Sonoma and Sequoia, plus OCLP 2.3.2 all on one NVMe ( via containers ).
Then reintroduce each other drive to see what's conflicting?
Start over from Mojave and make sure you take out all the drives, except the main drive you are using for the OS.
I have Monterey, Sonoma and Sequoia, plus OCLP 2.3.2 all on one NVMe ( via containers ).
Then reintroduce each other drive to see what's conflicting?
Yup. What a mess! I think I might have found the problem.
When I updated OCLP to v232 I also updated the EFI and the patches. Then in short order I discovered my bluetooth (mouse) was screwed and also that I could no longer boot to Sequoia (prohibit sign) I went back to Mojave and replaced the EFI folder with a backup (v231) made as safety before the update. And then I was able to boot again and forgot to uninstall the corresponding patches and reinstall the v231 patches. So I have done that now, basically reinstalled OCLP patcher 231 and redid the post update patches. Mac booted properly, wifi/BT is good and screensaver was activated a couple of times with no recurrence of the video card blackout. So this mismatch of 232 OS patches on a 231 boot EFI seems to have been the cause of my grief. We will see . . .
EDIT OK, spoke too soon. A cold boot up this morning simply led to the same black screen. Eventually it will reboot and repeat. If I hold option key I get the black version of the Apple bootpicker but it does not respond to keyboard or mouse. Wireless or wired. I have to CmdOptPR 4x to clear OC and get the grey screen bootpicker and can proceed from there as expected. No idea now what cause may be but something is messing up the NVRAM I guess. After removing all drives except Sequoia and OC EFI drive no change. Restarting warm seems to work fine. I once again tried upgrading to OCLP to 232 but again, cannot boot Sequoia at all (prohibited). So I am back on 231. Going to try going back to 230 now but changelog doesn't really indicate it will be very different so I am not hopeful.
When I updated OCLP to v232 I also updated the EFI and the patches. Then in short order I discovered my bluetooth (mouse) was screwed and also that I could no longer boot to Sequoia (prohibit sign) I went back to Mojave and replaced the EFI folder with a backup (v231) made as safety before the update. And then I was able to boot again and forgot to uninstall the corresponding patches and reinstall the v231 patches. So I have done that now, basically reinstalled OCLP patcher 231 and redid the post update patches. Mac booted properly, wifi/BT is good and screensaver was activated a couple of times with no recurrence of the video card blackout. So this mismatch of 232 OS patches on a 231 boot EFI seems to have been the cause of my grief. We will see . . .
EDIT OK, spoke too soon. A cold boot up this morning simply led to the same black screen. Eventually it will reboot and repeat. If I hold option key I get the black version of the Apple bootpicker but it does not respond to keyboard or mouse. Wireless or wired. I have to CmdOptPR 4x to clear OC and get the grey screen bootpicker and can proceed from there as expected. No idea now what cause may be but something is messing up the NVRAM I guess. After removing all drives except Sequoia and OC EFI drive no change. Restarting warm seems to work fine. I once again tried upgrading to OCLP to 232 but again, cannot boot Sequoia at all (prohibited). So I am back on 231. Going to try going back to 230 now but changelog doesn't really indicate it will be very different so I am not hopeful.
Last edited:
One thing I would like to have back in the later versions of MacOS is the built-in SATA Superdrive.
I occasionally want to rip older CDs and even play DVDs.
Did anyone figure out a way to get the 5,1 Superdrive to work in Sequoia era MacOS?
I occasionally want to rip older CDs and even play DVDs.
Did anyone figure out a way to get the 5,1 Superdrive to work in Sequoia era MacOS?
Your question implies, that the original SuperDrive doesn’t work any more. I did move on 5 or 6 years ago and replaced my drive with a newer Blue Ray writer to watch Blue Rays on the MP5.1.
Use the search function of this forum to find out the best replacements. There has been numerous options. I think I did go with the recommendation from OWC. Those models are guaranteed to work on the Mac platform. Owc also has a good external enclosure for that, either empty or already filled with a suitable BlueRay. I am traveling right now, but I think I have a BR writer from Pioneer BK xyz something.
I think the built-in disc drive in the 3,1 is a PATA, and that's the problem. If I run something like High Sierra, the disc drive is there. And it seems the SATA disc drive in the 5,1 is still recognized, although it's a bit tricky to use.
Guessing Apple must have dropped the PATA drivers at some point and that makes it difficult to use the drive in the 3,1. Just a guess?
No big deal, I have multiple CD/DVD drives that are USB and they fulfill my needs.
Is there a support group / thread here for OCLP? I have spent a week trying to get answers from the Discord but nothing. So I am asking anyone with OCLP knowledge and MacPro boot and MacPro boot with OCLP knowledge. So I am not sure if I am actually asking this in the right thread or not?
Problem: I cannot boot my MacPro from a shutdown. Best I can do is hold option and get to a black screen bootpicker. Without option I just get a black screen.
If I hold option key at boot I will get a BLACK Apple bootpicker. This is not normal. It should be grey. Where does this come from? Is this stored in NVRAM? Anyway, this bootpicker contains 3 generic HD icons one for each bootable system partion - Monterey, Sequoia and Mojave plus it has the EFI Boot option. Unfortunately it does not respond to keyboard (wired) or mouse (wired to keyboard) input so I cannot select anything. It will stay like this until the Mac in forced to shut down via the power button.
Execept - now and again the screen is LIGHT GREY not black. But rarely. Still, the bootpicker is usesless as no keyboard/mouse selection is possible.
As I understand this - nothing has been loaded in terms of OS at this point. I have always thought holding the Option key took me to the APPLE boot picker (enableGOP firmware mod) - but that is ALWAYS on a light grey screen, not a black one.
So in terms of the boot process, after holding option key and getting to this screen (bootpicker) where am I?
1. Is opencore loaded active at this point?
2. Is my Mac Pro still "vanilla" - ie nothing to do with opencore anywhere - OR - has OCLP put something in NVRAM that could possibly be causing a problem.
3. Should my USB ports back/front be working normally (I understand that it is the OS that contains or doesn't contain support for USB 1.0)? Essentially why can I not use arrow/return keys on Boot-with-Opt bootpicker?
When in this situation, ie every startup from shutdown, the only way to boot my Mac is to clear NVRAM x4 (not sure if I need 4 but anyway I do that) and then holding the option key will get me to the GREY Apple bootpicker, BUT the keyboard is working (direct USB or via hub) and I must select OCLP EFI BOOT option and then I get it bootpicker with colourful drive icons and I can boot Sequoia.
I am concerned clearing the NVRAM every single time I start up my mac now is going to damage something.
I have tried many ways to uninstall/resinstall/remove patches etc etc etc. At present I have OCLP 2.3.1 installed, as 2.3.2 I can definitely NOT boot Sequoia no matter what (Prohibit). Anyway, moving past the bootpicker simply introduces more problems and variables so I would like first understand the part above, which I assume all happens BEFORE anything is actually booted.
Thanks.
Problem: I cannot boot my MacPro from a shutdown. Best I can do is hold option and get to a black screen bootpicker. Without option I just get a black screen.
If I hold option key at boot I will get a BLACK Apple bootpicker. This is not normal. It should be grey. Where does this come from? Is this stored in NVRAM? Anyway, this bootpicker contains 3 generic HD icons one for each bootable system partion - Monterey, Sequoia and Mojave plus it has the EFI Boot option. Unfortunately it does not respond to keyboard (wired) or mouse (wired to keyboard) input so I cannot select anything. It will stay like this until the Mac in forced to shut down via the power button.
Execept - now and again the screen is LIGHT GREY not black. But rarely. Still, the bootpicker is usesless as no keyboard/mouse selection is possible.
As I understand this - nothing has been loaded in terms of OS at this point. I have always thought holding the Option key took me to the APPLE boot picker (enableGOP firmware mod) - but that is ALWAYS on a light grey screen, not a black one.
So in terms of the boot process, after holding option key and getting to this screen (bootpicker) where am I?
1. Is opencore loaded active at this point?
2. Is my Mac Pro still "vanilla" - ie nothing to do with opencore anywhere - OR - has OCLP put something in NVRAM that could possibly be causing a problem.
3. Should my USB ports back/front be working normally (I understand that it is the OS that contains or doesn't contain support for USB 1.0)? Essentially why can I not use arrow/return keys on Boot-with-Opt bootpicker?
When in this situation, ie every startup from shutdown, the only way to boot my Mac is to clear NVRAM x4 (not sure if I need 4 but anyway I do that) and then holding the option key will get me to the GREY Apple bootpicker, BUT the keyboard is working (direct USB or via hub) and I must select OCLP EFI BOOT option and then I get it bootpicker with colourful drive icons and I can boot Sequoia.
I am concerned clearing the NVRAM every single time I start up my mac now is going to damage something.
I have tried many ways to uninstall/resinstall/remove patches etc etc etc. At present I have OCLP 2.3.1 installed, as 2.3.2 I can definitely NOT boot Sequoia no matter what (Prohibit). Anyway, moving past the bootpicker simply introduces more problems and variables so I would like first understand the part above, which I assume all happens BEFORE anything is actually booted.
Thanks.
Last edited:
What machine do you have?
Also important when upgrading is to stop the OS from prepackaging updates. disable silent updating.
Also OCLP will install the required KDKs for you when you do move up the OS.
I still have my original WiFi card and it installs fine.
Also important when upgrading is to stop the OS from prepackaging updates. disable silent updating.
Also OCLP will install the required KDKs for you when you do move up the OS.
I still have my original WiFi card and it installs fine.
The spoiler shows my system detail.
I have an upgraded wifi-BT card which OCLP completely ignores (it always applies the fix kext which will essentially screw up my bluetooth and after every OCLP install this must be corrected - OCLP does not actually check your hardware it makes assumptions and this is one of them - this video explains the problem and the workaround
).
Unfortunately OCLP is installing something in NVRAM that is causing a problem. Once the NVRAM is flushed I can use the EFIboot without issue. If I restart the boot will be fine. If I shutdown and start I will no longer be able to boot until I flush NVRAM again.
The "apple bootpicker on black background with no keyboard/mouse response" on opt-key startup is a definite and repeatable indicator or symptom of a key issue here - I wish I could find someone with boot knowledge who could explain why this happens or what might make it happen. It is essentially a useless screen, displaying drives and efiboot as per apple but I am unable to select or choose with keyboard/mouse and there the mac will sit forever.
Once I restart and clear NVRAM x4 and use option key I get the same apple bootpicker but now on the proper light-grey screen and I can arrow-select, return choose etc and choose efiboot boot and then my Sequoia drive and boot back into Sequoia just fine.
The problem is that now I have to do this NVRAM clearing ever single time I boot this machine from shutdown and stressing that chip which is apparentkly asking for trouble on this hardware according to @tsialex who built my rom for me.
Unfortunately I am stuck now. I tried to install Sonoma and go back one OS to use an earlier OCLP but I cannot migrate my user folder. I just get error'd and it aborts. I cannot afford to lose that as its kinda critical to me. I upgraded to be able to use the latest FCPX and now I have boxed myself into a corner. I cannot go back to Monetery, which essentially always worked flawlessly and for which I can and always did create my own OC EF config.
So I don't think there is anything wrong with hardware or OS drives as they can always boot just fine once NVRAM is cleared, but then as soon as I shutdown then whatever it is in the NVRAM causing this black apple bootpicker kicks back in and I get either it or a black screen if I dont hold option.
I have tried asking on discord but no response whatever. The bad thing about OCLP is the problems are very techncal but there is no support other than other users and it seems I am alone in this as I have had no one offer any explanation for the symptoms here.
I have an upgraded wifi-BT card which OCLP completely ignores (it always applies the fix kext which will essentially screw up my bluetooth and after every OCLP install this must be corrected - OCLP does not actually check your hardware it makes assumptions and this is one of them - this video explains the problem and the workaround
Unfortunately OCLP is installing something in NVRAM that is causing a problem. Once the NVRAM is flushed I can use the EFIboot without issue. If I restart the boot will be fine. If I shutdown and start I will no longer be able to boot until I flush NVRAM again.
The "apple bootpicker on black background with no keyboard/mouse response" on opt-key startup is a definite and repeatable indicator or symptom of a key issue here - I wish I could find someone with boot knowledge who could explain why this happens or what might make it happen. It is essentially a useless screen, displaying drives and efiboot as per apple but I am unable to select or choose with keyboard/mouse and there the mac will sit forever.
Once I restart and clear NVRAM x4 and use option key I get the same apple bootpicker but now on the proper light-grey screen and I can arrow-select, return choose etc and choose efiboot boot and then my Sequoia drive and boot back into Sequoia just fine.
The problem is that now I have to do this NVRAM clearing ever single time I boot this machine from shutdown and stressing that chip which is apparentkly asking for trouble on this hardware according to @tsialex who built my rom for me.
Unfortunately I am stuck now. I tried to install Sonoma and go back one OS to use an earlier OCLP but I cannot migrate my user folder. I just get error'd and it aborts. I cannot afford to lose that as its kinda critical to me. I upgraded to be able to use the latest FCPX and now I have boxed myself into a corner. I cannot go back to Monetery, which essentially always worked flawlessly and for which I can and always did create my own OC EF config.
So I don't think there is anything wrong with hardware or OS drives as they can always boot just fine once NVRAM is cleared, but then as soon as I shutdown then whatever it is in the NVRAM causing this black apple bootpicker kicks back in and I get either it or a black screen if I dont hold option.
I have tried asking on discord but no response whatever. The bad thing about OCLP is the problems are very techncal but there is no support other than other users and it seems I am alone in this as I have had no one offer any explanation for the symptoms here.
Since you are constrained to a difficult position, take some steps back and get your Mac Pro working again.
Boot a supported macOS release, re-flash your reconstructed BootROM image, install back your original BT card ( or even ignore BT completely for now ) and install Monterey or Sonoma, I'd forget Sequoia. If you need to save your data, install Sequoia to a spare disk to access it and then move it to another disk.
I've warned years ago that your choice of BT card was not the correct one for the Mac Pro, the iMac AirPort Extreme that works best with a MacPro5,1 is BCM94360CD, while the one that is known to make a mess with the NVRAM (constantly recreating bluetoothActiveControllerInfo and bluetoothInternalControllerInfo variables) when you boot earlier than Catalina is the updated one with BT4.2, BCM943602CDP.
I don't recommend BCM943602CDP for anyone that have to boot earlier macOS releases and should be avoided in general, even more so that OCLP ignores it completely.
Thanks Alex, that's not what I wanted to hear but at least you have addressed my problem in detail. Yes, I remember now after reading your emails again. I suppose the illusion of success while all is working well faded that advice into the background.
Unfortunately the installation of the Wifi/BT card was not done by me and I no longer have the original hardware. I will have to try and get hold of the recommended card. Since then everything has been fine until I began using OCLP due to the need to work on an FCPX file on a job. All was fine until at some point this conflict arose.
Yesterday I made a CCC backup of the HD data and erased the drive. After 4 attempts I managed to get Sequoia installed fresh on the drive with OCLP 2.3.2, only to spend 3 hours on Migration and then get stuck in a "Migration Successful - Please Restart to complete" loop.
The reason for this seems to be documented (https://dortania.github.io/OpenCore-Legacy-Patcher/TIMEMACHINE.html) so now I was planning to wipe again and install Sonoma in order to get back to Sequoia.
At present, even though I cannot boot into Sequoia due to the migration/time machine issue above, I have finally got OCLP 2.3.2 working on this Mac without prohibit signs and also I have Bluetooth/mouse function working properly. I am currently running on Monterey but need to install at minimum Sonoma for FinalCut.
In the meantime I will go searching for that card. I will probably have to buy one from USA so it will take time. I am hoping I can get back to working without completely screwing up my cMP / NVRAM.
Thanks for your help, at least I am not stumbling around banging my head in the dark anymore!
Last edited:
Yes, I am making progress there. I have managed to get a clean Sonoma 14.7.5 installed, I have not yet tried the Migration tool to get back my data but I have successfully got the BT mouse working properly again. I came upon this resource from Acidanthera - BRCM PATCH and his GitHub has a later version the kexts than OCLP 2.3.2 comes bundled with.
The standard OCLP 2.3.2 installer/patch does not provide the required recognition and support for my bluetooth card but it only has an earlier version of these kexts. I hope that in the short term this means I am OK with this card until I can find another. It's quite easy to find iMacs and MacBooks for parts here but not the trashcan Mac Pro! The only alternative is to order that BCM94360CD card from USA. The only time I am booting Mojave is when I have problems, but recently that has been a LOT.
iMacs of several years have BCM94360CD, late-2012 to late-2015 if my memory serves me right.
Anyway, BCM94360CD is easily found on AliExpress.
Immediately turn off auto updating in the system settings prior to upgrading to Sequoia.
Should have no problems with the wifi removed, and just ethernet hooked up.
When upgrading, OCLP shold have a popup saying you need install KDK package.
For me, it was easy. When I downloaded the KDK package first, then downloaded Sequoia. both updated on it's own.
That was weird, but I didn't have to do anything. Was on auto pilot or something.
Its taken me almost 4 days and lawd knows how many hangs and restarts but I think I am back to where I was this time last week.
The problem with OCLP and upgrades is that none of that applies in a clean install. You get no messages and no KDK downloads etc. And you cant install KDK's on a wiped drive that has no OS. That all only works on an "update" vis System Settings and you can't "update" a second or third or whatever time! At some point you have to do a full install.
Eventually I had to wipe it all including OCLP, install Sonoma (Sequoia just would not clean install at all ever successfully). Update Sonoma to Sequoia. Then install OCLP, but use some different KDK's and little pieces to get the bluetooth working properly. And then troubles started again with Migration Tool which also never ever worked no matter how or what I tried to migrate (system settings at least).
When I used CCC to restore it obviously overwrote something important or copied over something that was a problem cause as then OCLP refused to install root patches (can't mount root volume, system mismatch). So start again etc., creating bootable backups of every system install with CCC (which requires patches to be reverted) so that I didn't get stuck without an OS basic and bootable.
What a nightmare it all was. And it all started with a simple yes to upgrade to OCLP 2.3.2!
The problem with backups is stuff hangs around on drives that shouldn't but nevertheless, where would I be without them. In future when I do a CCC backup I will ensure it's bootable, even though I have to go through the patch revert/boot/clone/restore/boot process every time. Having a backup of only the data is just not good enough to restore your system properly (keychains, software licenses, rlm servers, app plugins etc etc).
I really sometimes wish I could just switch off all of Apple's "security" completely. I just don't operate in an environment where any of that crap is useful. A simple, bootable back up of my system, regularly updated - is that too much to ask? Time Machine and Migration Tool are no good to me anymore as a system restore strategy. Far too many "terms and conditions" and ultimately complete failure to deliver.
The problem with OCLP and upgrades is that none of that applies in a clean install. You get no messages and no KDK downloads etc. And you cant install KDK's on a wiped drive that has no OS. That all only works on an "update" vis System Settings and you can't "update" a second or third or whatever time! At some point you have to do a full install.
Eventually I had to wipe it all including OCLP, install Sonoma (Sequoia just would not clean install at all ever successfully). Update Sonoma to Sequoia. Then install OCLP, but use some different KDK's and little pieces to get the bluetooth working properly. And then troubles started again with Migration Tool which also never ever worked no matter how or what I tried to migrate (system settings at least).
When I used CCC to restore it obviously overwrote something important or copied over something that was a problem cause as then OCLP refused to install root patches (can't mount root volume, system mismatch). So start again etc., creating bootable backups of every system install with CCC (which requires patches to be reverted) so that I didn't get stuck without an OS basic and bootable.
What a nightmare it all was. And it all started with a simple yes to upgrade to OCLP 2.3.2!
The problem with backups is stuff hangs around on drives that shouldn't but nevertheless, where would I be without them. In future when I do a CCC backup I will ensure it's bootable, even though I have to go through the patch revert/boot/clone/restore/boot process every time. Having a backup of only the data is just not good enough to restore your system properly (keychains, software licenses, rlm servers, app plugins etc etc).
I really sometimes wish I could just switch off all of Apple's "security" completely. I just don't operate in an environment where any of that crap is useful. A simple, bootable back up of my system, regularly updated - is that too much to ask? Time Machine and Migration Tool are no good to me anymore as a system restore strategy. Far too many "terms and conditions" and ultimately complete failure to deliver.
Migration tool is what throwing you off.
Install Monterey, which you have OCLP installed to get Monterey.
Then turn off in system setting automatic update, because it's downloading foreseen packages that will give you problems.
Then at this point you have OCLP and Monterey.
Now create a new Container, which when you upgrade, you will upgrade to the new container ( name it SEQUIOA )
Now upgrade to Sequoia, provided you have the latest OCLP 2.3.2
When going through the process OCLP will automatically say you need to install KDK, install. While you are installing Sequoia.
When both are installed, do the upgrade and target the upgrade to the Sequoia container. The KDK will install first to prepare for Sequoia.
A new Opencore Legacy Patcher came out, 2.4.0. One of the mentioned fixes is the USB Camera support problem. Hopefully this resolves the USB camera problem. OCLP 2.4.0
@Mic-M4c
Thanks Macsonic! I'll try it this week, that would be great and help that this legendary Macs live one more extra year with current MacOS. I am very happy! 
Last edited:
Hello. @Mic-M4c Some great news. Been praying for a fix. A Youtube blogger, Jessie’s Flying tested the OCLP 2.4.0 on his 2012 Classic Mac Pro and now the webcam works fine. The camera also works on his PCIE USB3 card. Below is his video. One note, you’ll need to jump to 16:00 mins as that is the clip he shows the camera works. Thanks @Frixo Cool 🙏 👍
Video on OPCP Test
Attachments
I can confirm that the problem is resolved! OCLP 2.4.0 allows third-party USB webcams to be used normally. Our beloved Mac Pro 5.1 will live even longer!
OCLP 2.4.0 allows third-party USB webcams to be used normally. Our beloved Mac Pro 5.1 will live even longer!