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 Rx 590 sapphire with boot screen
- Thread starter Merzak
- Start date
- Sort by reaction score
RX590 can work in Monterey natively, not extra driver need (in fact, no drive for you to download and install).
However, your cMP isn't support Monterey natively, you have to use OpenCore to install that.
Some users used OCLP to install Monterey with their old graphic card, then the root patch may lock the OS with the old GPU. You should avoid this.
Boot screen is not OS related, but firmware / boot loader related. Boot screen works before OS start to load.
However, your cMP isn't support Monterey natively, you have to use OpenCore to install that.
Some users used OCLP to install Monterey with their old graphic card, then the root patch may lock the OS with the old GPU. You should avoid this.
Boot screen is not OS related, but firmware / boot loader related. Boot screen works before OS start to load.
Hello h9826790
I have a similar question. I am on 5,1 with a (recently purchased) flashed Saphire rx590+ running a recent upgrade to Mojave. I have deprecated software so I am looking to upgrade via OCLP to Monterey 12.6.7. I have always updated my OS using a Nvidea K5000, however, I read or saw a comment that using an older compatible graphics card and using the OCLP root patch can create issues as you mentioned.
So do I understand from your comments that the flashed rx590 could be used because the boot screen works before OcLp, and that OCLP would not create any code that would damage the card?
thanks
I have a similar question. I am on 5,1 with a (recently purchased) flashed Saphire rx590+ running a recent upgrade to Mojave. I have deprecated software so I am looking to upgrade via OCLP to Monterey 12.6.7. I have always updated my OS using a Nvidea K5000, however, I read or saw a comment that using an older compatible graphics card and using the OCLP root patch can create issues as you mentioned.
So do I understand from your comments that the flashed rx590 could be used because the boot screen works before OcLp, and that OCLP would not create any code that would damage the card?
thanks
I currently have a NVIDIA GTX 680 flashed for Mac installed. I had Monterey up and running with OCLP with root patch for Kepler card. Monterey update 12.6.8 corrupted boot partiton so I had to revert back Mojave TM backup. Can't get OCLP to boot anymore so I want to install a Sapphire Radeon Nitro+ RX 590 and Martin Lo OC to reinstall Monterey 12.6.8.
EDIT: I reread your post. Since I will be installing Monterey on another drive it will be wiped first to accept new OS. So the OS can't be locked by root patch.
Last edited:
Can, but you have to manually turn on VMM and disable SMBIOS in the OpenCore config.plist.
It should. If no boot screen for whatever reason, 99% can be fixed by downloading a factory ROM from TechPowerUp, then flash your card back to factory state.
Thanks. I ordered an non-flashed Sapphire RX580 because it's less power hungry and is 40mm thick compared to the 590 Nitro which is 43mm thick. This way hopefully I'll still be able use PCIe slot 2 with a riser cable for my NVMe SSD. Currently I'm still using a flashed GTX680 (38mm thick) and trying to install MLOC onto a bootable thumb drive. I installed a fresh copy of Mojave onto the thumb drive, reset NVRAM and disabled SIP but can't bless OC. In recovery it shows successfully disabled SIP but when I reboot I see it's enabled with custom configuration.
Last edited:
I've tried at least 20 times over the last few weeks to disable SIP but cannot make any changes to SIP. I've even tried entering individual commands, e.g. "csrutil enable --without nvram" but I am unable to make any changes. I've followed the precedure multiple times, I reset nvram (chime 3 times), then boot into Recovery and disable SIP successfully but when I reboot normally, SIP does not save commands. Something happened when Monterey 12.6.8 security update crashed the boot partition. I was able to disable SIP and install Monterey using OCLP over a month ago but after the crash, I had to restore a TM backup of Mojave without OCLP. Now every time I try to disable SIP it does not save changes. There is very little info about this issue on the Web, I can't figure it out?
EDIT: After researching I believe my system's SIP status shows my last configuration that was implemented by OCLP before 12.6.8 security update crashed OC boot loader when I had Monterey installed with Post-Install root patches. SIP is now now locked into that configuration somehow? I can't reinstall OCLP to disable SIP as I would have to first disable SIP to install OCLP.
EDIT 2: Typed nvram -xp in Terminal.
No "csr-active-config" or "efi-boot-device" ?
Should they be listed?
Last edited:
Your GTX680 is flashed?
If yes, you can simply hold Option key to boot, and use Control + Enter to "bless" OpenCore (the EFI entry in that boot manager).
Yes it is flashed. Can you explain what you mean? Boot into what? Are you referring to my screen capture above where I'm booted into Mojave thumb drive where MLOC is loaded?
These are my options at boot screen:
Last edited:
If you are already running my package. Then you don't need to run the bless tool. It's already blessed.
And SIP is controlled by the OpenCore config.plist. That's why you can't disable it in recovery partition.
No, I have not been able to get that far. I can't bless OpenCore so I could not run your package.
But your "current boot screen" is the OpenCore boot picker, not the native Apple boot manager.
You are already running OpenCore. OpenCore is already blessed.
One can run my dumper and see what bootloader is blessed and where it lives.
Opencore legacy patcher recovery boot loop seems to be a major problem in OCLP..
´there are a lot of threads about it @ forum here, and I can´t read about a solution, threads seems to be abandoned...
I´m stucked with same problem here, have spent whole weekend trying to solve it, without sucess...
At Github, some reports about are simply closed by khronokernel, without a response from original poster...
´there are a lot of threads about it @ forum here, and I can´t read about a solution, threads seems to be abandoned...
I´m stucked with same problem here, have spent whole weekend trying to solve it, without sucess...
At Github, some reports about are simply closed by khronokernel, without a response from original poster...
OCLP have stopped issues being reported since Feb '22. He said "With the situation going on back home in Ukraine, I've temporarily disabled new Github Issues so I can focus on my family. I am currently the only active maintainer with these issues so there's no one else to delegate them to."
The only direct way to get support is to get an account on Discord and post there. Good luck there.
Sorry needed to get some sleep and clear my thoughts. I've been researching this for 2 weeks, 2 weeks of pure frustration.
Thank you for explaining what was obvious to you but not to an OC nube like myself. Everything is starting to make sense now.
I think What I have is a dysfunctional version of OCLP that installed with my TM backup. I apparently did not choose a backup that was pre OCLP installation. I have only tried to run your package from a thumb drive, I did not try to install it to my boot drive yet as I was afraid of crashing my boot partition again. So wouldn't that produce the error I posted above when I use the Bless Tool? Also when I run Monterey installer It tells me it cannot be installed to this disk. I'm almost sure that I had the OC boot picker since installing the TM backup. I'm sure you can tell me if that's the case by looking at my EFI below.
Last edited:
I'm assuming you mean ROMTool? I just dumped it but don't know how to open it. I zipped it. Deleted
Last edited:
I have a thread there, "Missing EFI Boot Option" about this issue but have not received much feedback.
That's why I said "Good luck there". It's easy to get drowned out amongst the noise there
we can see OpenCore is blessed (BootOrder0001),
OpenCore is sitting in Sata Bay 1, on the WD500 drive.
The path was disk1s1 during reading the dump file. The path varies from boot to boot.
You can use my little script: mount ESP from list. This shows Sata Bay 1 and WD500ish, too.
config.plist in the ESP also shows the OCLP version.
OCLP 0.6.8 was written in a NVRAM variable. That dont mean it was running.
The Romdump-timestamp.log shows if OpenCore runtime variable was written. Firmware spoofing is another clear sign of OC running or not. Both should be read in the log.
Those are some data points to troubleshoot with the information the Dumper gives.
Last edited: