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 set up (with tsialex!) a MP 5.1 with a RX 5700xt and Monterey, under OCLP. In Videoproc software hardware acceleration and encoding are available for the 5700xt. There are all the greenlights. However in Videoproc, Handbrake, QuickTime and Compressor only CPU is used for HEVC encoding.
Final Cut rendering is GPU accelerated. But encoding isn't.
Hi Zazaki,

I have the same config as yours, I have been trying to enable RX5700xt in the past 2 days, but no luck, do you mind sharing your config with me?

Thank you
 
Change that Board ID should not disable the boot picker, unless you accidentally made an syntax error. Please double check that.
I checked the string, it is OK. Unfortunately, I still got the same error - a black screen when trying to install Big Sur.
I tried installing Monterey and here it went a little better: the installer only threw an error at the end: "A required firmware update could not be installed"....
 
I checked the string, it is OK. Unfortunately, I still got the same error - a black screen when trying to install Big Sur.
I tried installing Monterey and here it went a little better: the installer only threw an error at the end: "A required firmware update could not be installed"....
I had had same issue as you had, what I did, was get a good install at Mojave, then ensure my ROM version was 144.0.0.0.0, then I create an install USB from OLCP, then I boot up from the USB, delete the HDD that I was installed, be sure the new HDD that you create do not have the EFI, all system HDD do not have the old EFI fodder, then you should be fine!
 
I checked the string, it is OK. Unfortunately, I still got the same error - a black screen when trying to install Big Sur.
I tried installing Monterey and here it went a little better: the installer only threw an error at the end: "A required firmware update could not be installed"....
For Monterey installation, you have to do this.

That Board-ID change is solely for enabling all the ports on the graphic card. Monterey installation is another issue.
 
  • Like
Reactions: 0134168
I had had same issue as you had, what I did, was get a good install at Mojave, then ensure my ROM version was 144.0.0.0.0, then I create an install USB from OLCP, then I boot up from the USB, delete the HDD that I was installed, be sure the new HDD that you create do not have the EFI, all system HDD do not have the old EFI fodder, then you should be fine!
@ John, the problem is: – i cannot boot from USB disk created via OCLP, because USB disk created such way is not bootable (not blessed). I bless it in recovery mode, but, even after that, after USB boot, Big Sur installer hang my system.
Probably the cause is my NVIDIA Quatro NVS510 Card (4 mini Display Ports). I like it, because I have a pair old Apple Vision monitors with mini DP connectors, the quality of image is still outstanding, and they work seamlessly in Mojave (camera and sound) without mess with interface adapters. But the software I use (VS Code, for example) will lose support any day now in Mojave. Or they have already lost it. So I'm trying to pick up the system.
@ h9826790 – thank you for another advice, I will try and give report.
 
@ John, the problem is: – i cannot boot from USB disk created via OCLP, because USB disk created such way is not bootable (not blessed). I bless it in recovery mode, but, even after that, after USB boot, Big Sur installer hang my system.
Probably the cause is my NVIDIA Quatro NVS510 Card (4 mini Display Ports). I like it, because I have a pair old Apple Vision monitors with mini DP connectors, the quality of image is still outstanding, and they work seamlessly in Mojave (camera and sound) without mess with interface adapters. But the software I use (VS Code, for example) will lose support any day now in Mojave. Or they have already lost it. So I'm trying to pick up the system.
@ h9826790 – thank you for another advice, I will try and give report.
Hi,

Have you tried Apple's way to create the bootable macOS USB? here is the link


I did, I moved back to Mojave first after I was done with Mojave, and then I upgraded to Monetery, you can ensure your system won't freeze in Mojave.
 
Hello All,

I am hoping someone can help me to let my RX5700 work, I was trying to get it done, but after I tried both @ h9826790 and OCLP, the system was installed successfully, but the HW acceleration still failed, Any idea?

Please see the photo in detail!

Thank you
Screen Shot 2023-11-29 at 1.14.29 PM.png
Screen Shot 2023-11-29 at 1.15.24 PM.png


 
Last edited:
Hello All,

I am hoping someone can help me to let my RX5700 work, I was trying to get it done, but after I tried both @ h9826790 and OCLP, the system was installed successfully, but the HW acceleration still failed, Any idea?

Please see the photo in detail!

Thank you
View attachment 2318604View attachment 2318602View attachment 2318603View attachment 2318601

Please replace the whole EFI folder by my latest package (assuming your system files are NOT patched by OCLP), your screen capture suggest you haven't done the steps correctly.

Of course, you have to turn on the 32GB DIMM support for your memory config.

If you did everything right, both System Info and Hackintool should show 9144.x.x.x.x in the BootROM version, but not 144.0.0.0.0 (assuming you are using my package).
Screenshot 2023-11-29 at 15.09.09.png

Screenshot 2023-11-29 at 15.09.29.png
 
  • Like
Reactions: 0134168 and John Fu
Please replace the whole EFI folder by my latest package (assuming your system files are NOT patched by OCLP), your screen capture suggest you haven't done the steps correctly.

Of course, you have to turn on the 32GB DIMM support for your memory config.

If you did everything right, both System Info and Hackintool should show 9144.x.x.x.x in the BootROM version, but not 144.0.0.0.0 (assuming you are using my package).
View attachment 2318615
View attachment 2318616
I will do it and report back to you, Thank you
 
  • Like
Reactions: h9826790
Hello All,

I am hoping someone can help me to let my RX5700 work, I was trying to get it done, but after I tried both @ h9826790 and OCLP, the system was installed successfully, but the HW acceleration still failed, Any idea?

Please see the photo in detail!

Thank you


Remove/Mask your serial number in the hardware overview image. Someone may use it to spoof your machine for apple services.
 
@h9826790 Thanks to your advice, finally managed to install Monterey, but Mac Pro does not see NVidia NVS510 card. Mac Pro detects a noname card with only 22 MB RAM and runs very slowly. That is, without any acceleration.
I tried to apply ROOT PATCH with OCLP installer (it recognized NVidia GPU Keppler correctly), but after this operation at startup the image in the monitor disappears. There is no video signal on any of the card's four mini DP slots. Unfortunately, this card only has miniDP connectors, no others, so I guess the situation is difficult.
 
@h9826790 Thanks to your advice, finally managed to install Monterey, but Mac Pro does not see NVidia NVS510 card. Mac Pro detects a noname card with only 22 MB RAM and runs very slowly. That is, without any acceleration.
I tried to apply ROOT PATCH with OCLP installer (it recognized NVidia GPU Keppler correctly), but after this operation at startup the image in the monitor disappears. There is no video signal on any of the card's four mini DP slots. Unfortunately, this card only has miniDP connectors, no others, so I guess the situation is difficult.
I reviewed your last few posts.

You initially asked for Big Sur issue, which has Kepler support.

But then you changed to Monterey, which has no Kepler support, that's why your GPU become a no name card.

If you want to use OCLP, please use full set of OCLP, including let it to install OC for you.

You can't mix my OC EFI folder with OCLP root patching. It won't work.
 
  • Like
Reactions: Macschrauber
Hello!

I have updated to OS 12.7.1 and that turned out fine. I change the config.plist file back on the EFI disk. Both CupidlMask and the SMBIOS, but sytem upgrade still shows in systempreference. Whow do I turn this off?

/Doc
 
Hello!

I have updated to OS 12.7.1 and that turned out fine. I change the config.plist file back on the EFI disk. Both CupidlMask and the SMBIOS, but sytem upgrade still shows in systempreference. Whow do I turn this off?

/Doc
That's normal. The Sonoma update prompt is always there. You better just ignore it.
 
  • Like
Reactions: expede
Let me explain in turn: Trying to install BigSur, even after replacing the text strings in config.plist still ends up with a black screen.
So I tried installing Monterey, which was successful, but without acceleration. That's why I tried ROOT PATCH with OCLP. Which also ended in failure.
So the question is: Is it possible to get acceleration of the Nvidia NVS card (GPU Keppler) in Monterey within the Martin Lo package?
As for OCLP: I tried to use it before I installed the Martin Lo package. OCLP was unable to create a proper EFI partition - it was missing the BOOT folder and some others files also are missing, so there was no way to boot.
 
Let me explain in turn: Trying to install BigSur, even after replacing the text strings in config.plist still ends up with a black screen.
So I tried installing Monterey, which was successful, but without acceleration. That's why I tried ROOT PATCH with OCLP. Which also ended in failure.
So the question is: Is it possible to get acceleration of the Nvidia NVS card (GPU Keppler) in Monterey within the Martin Lo package?
As for OCLP: I tried to use it before I installed the Martin Lo package. OCLP was unable to create a proper EFI partition - it was missing the BOOT folder and some others files also are missing, so there was no way to boot.
OCLP has no BOOT folder, that's normal.

For most GeForce Kepler GPU, this should work, but I am not sure if it works for your NVS card. You may have to add the Device ID manually by yourself.
 
Please replace the whole EFI folder by my latest package (assuming your system files are NOT patched by OCLP), your screen capture suggest you haven't done the steps correctly.

Of course, you have to turn on the 32GB DIMM support for your memory config.

If you did everything right, both System Info and Hackintool should show 9144.x.x.x.x in the BootROM version, but not 144.0.0.0.0 (assuming you are using my package).
View attachment 2318615
View attachment 2318616
@h9826790

I am using your open-core package, and everything is good, but it seems when I plug in the 2nd display, it can not detect it, any idea why? Thank you!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.