You can always do a quick binary compare using the terminal app and this command
diff file1.rom file2.rom assuming the files are named this way.
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 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
You are true, ROM are not exactly the same (even there are not much differences, all at beginning).
And even less, my bios is the same I downloaded from techpowerup.com and ati-atiflash utility said to be the same:
Here there are much more differences, even in the middle from the files.
I have a Mid 2010 Mac Pro (MacPro5,1) running Mojave 10.14.6. It has a Metal-capable AMD Radeon 7950 Sapphire Mac Edition video card, an internal OWC 500 GB SATA SSD (not NVMe), an Apple RAID Card with 4x2 TB drives, an iSight FireWire camera and I also have a 1 TB HGST Travelstar 2.5" SATA drive (an HGST HTS541010A9E680) in a Fantom external USB 3.0 enclosure I can use in a pinch. (SIP is currently disabled if it matters.)
I had just about become convinced I could try dosdude1's Catalina Patcher or, if feeling ambitious, the latest OCLP version with some version (11.2.3? 11.5?) of Big Sur.
But I just found another post thread on here from April of last year by eksu saying that while he could see/read/write to the RAID disks through the Apple RAID Card if he grafted the AppleRAIDCard.kext in from Mojave, he couldn't get either Apple's RAID Utility or the raidutil command line app to work. 😞 So he had to keep a bootable Mojave copy around if they wanted to be able to manage an array. Arggh!
15 months later, is this still the case? It's sounding like more trouble than it's worth (I pray every day that September will bring a > 16 GB capable M1X or M2 Mac mini to replace this old warhorse with).
I had just about become convinced I could try dosdude1's Catalina Patcher or, if feeling ambitious, the latest OCLP version with some version (11.2.3? 11.5?) of Big Sur.
But I just found another post thread on here from April of last year by eksu saying that while he could see/read/write to the RAID disks through the Apple RAID Card if he grafted the AppleRAIDCard.kext in from Mojave, he couldn't get either Apple's RAID Utility or the raidutil command line app to work. 😞 So he had to keep a bootable Mojave copy around if they wanted to be able to manage an array. Arggh!
15 months later, is this still the case? It's sounding like more trouble than it's worth (I pray every day that September will bring a > 16 GB capable M1X or M2 Mac mini to replace this old warhorse with).
Not sure. Probably not an OpenCore thing because I know that your config is correct. I installed 11.4 and shortly thereafter 11.5, both from a bootable installer. In 11.5, I received the 11.5.1 notification and proceeded with the update.
I was offered 11.5.1 as soon as I finished installing 11.5! I didn't install 11.5.1 immediately, but a couple of days afterwards. It went fine (using latebloom).
OK, at last a found the switch and turned the card to "the other mode" (is there a way to know which mode I get?). But nothing changed for boot picker... I can't see any.
And looking the GPU-Z information, the ROM seems exactly the same with 1340/2000MHz default clock (I don't insert both screenshots, because they have exactly the same data):
.View attachment 1812331
But the firmware that ati-atiflash utility said it's the same as the one loaded on card before any modify, was the one compiled on 2018-07-19 01:39:00, with 1411/2000 clock frequencies. And the one that ati-atiflash utility accepted to load on card (an with which card seemed to be broken), was the one compiled on 2017-10-19 06:35:00, always with 1411/2000, instead ati-atiflash utility won't install the firmware with 1340/2000MHz.
Sapphire RX580 Pulse with Dual BIOS?
Here’s the only other mention of the BiOS switch in the box Only way to find out is taking the cooler apart and look at the chip but that would void my warranty and return priviledge with Newegg so probably won’t do that...
forums.macrumors.com
I can run a slightly patched version of Catalina (updated BLE/WiFI card, RX580 flashed) nicely without OC just with the boot-args="-no_compat_check" in NVRAM. This is without HVEC acceleration. But any time I boot with OC, this gets wiped out.
Is there any way to prevent it? May by adding the extra elements needed for OC and in Recovery and deleting the line in config.plist?
Is there any way to prevent it? May by adding the extra elements needed for OC and in Recovery and deleting the line in config.plist?
Yes. See "Clean up the NVRAM" in part 2 of the guide. Then use recovery to manage your boot args including
-no_compat_check. Note that you can minimize the use of boot args in OC by using device properties.Does upgrading past 11.2.3 break anything on a 5,1 with OC boot? I thought it messes things up like with nvme drives and power issues? I'm hoping those are a thing of the past but I haven't heard of a definite answer on updating further safely.
Several forum members, myself included, have benefited from the experimental latebloom kext, developed by @Syncretic. In my personal experience, it's fantastic, particularly as far as installing BS 11.3+ goes, but others may prefer to stick to the more stable BS 11.2.3. See https://forums.macrumors.com/thread...rkaround-for-the-11-3-race-condition.2303986/. Right now, I'm running BS 11.5.1 with no issues.
Welllll, I am a dolt. I did not realize that the OpenCore legacy patcher was specific to Big Sur, and had assumed I could use it with Catalina as well, explaining all the issues I had here: https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-30131399
Currently installing 11.2.3 on an SSD partition and I'll see how that goes.
Currently installing 11.2.3 on an SSD partition and I'll see how that goes.
Great I'll take a look and post there if there are any questions. I was asking because my cMP is working perfectly with nothing "broken" but my software update is reminding me to update and I'm not sure I should or even need to. So I thought I'd see what experiences are out there to gauge the risk.
Thanks 4 that input. I had BS 11.2.4 running very well on my Mac Pro 4,1 - 5,1. I had Auto update ON and I got 11.4 on 3 of 4 of my Mac 4,1's BEFORE I read the issues or the suggestions to NOT upgrade past 11.2.4 - TOO LATE AND all of My Mac 5,1's have PCIe - NVME. .. I did see some boot issues. last time I booted I dod not shut down My Mac has been running well with out reboot for 60 days. I read about Late Bloom, Garbage collection, corrupt chip on the MoBo etc.
That Backing up the Chip seems a bit of work & not easy.
You have given me the confidence to try 11.5.1 AND unless someone Warns me, I will try to install it on Sat 07312021.
Please someone in the Group warn me if it is not a good idea... Thank You
Based on the info I have "googled" it is not clear, how I can convert the device boot-args parameters to device properties.
My current properties are:
nvram boot-args="-no_compat_check -lilubetaall -wegbeta agdpmod=pikera shikigva=80 unfairgva=1 mbasd=1 -wegtree no32exec=0 latebloom=200 lb_range=20 lb_debug=1"
The most obvious place to search for it might be the online OpenCore docs…
To add device properties for
agdpmod=pikera shikigva=80 unfairgva=1 -wegtree, see "Add the device properties" in part 2 of the guide. (Note that you'll need the canonical path of your graphics card. This simple process is described in the first spoiler of the section "Enabling Hardware Acceleration" in part 2.)As for
-lilubetaall -wegbeta mbasd=1 no32exec=0, you should confirm that you actually need these:-lilubetaall enables Lilu and all it's plugins on unsupported macOS versions (Monterey is currently supported).
-wegbeta is redundant because of -lilubetaall.
mbasd=1 allows to use an external Apple SuperDrive in unsupported configurations.
no32exec=0 is for 32 bit apps.I hope this helps!
It is not a good idea if it is your production mac. It is a good idea if you want to help finding the root cause of the problems and are ready to have major problems.Read the first post here This is still the status of the problem.
I've just updated a BS 11.4 Parallels Desktop virtual machine to the latest developer beta of Monterey. The only thing about this that might be laterally relevant to this thread is that the first booting attempt hung. I had to reset the virtual machine to get to the Desktop. All later reboots of the VM were successful. I'm saying this because I think this confirms we should expect failed booting processes on our cMP 5,1s when attempting to boot Monterey through OpenCore and latebloom. What I don't understand is why on earth the virtual hardware of Parallels (16.5) should be, in a way, so similar to a Big Sur/Monterey unsupported Mac, such as the cMP.
One observation:
FirmwareFeatures and FirmwareFeaturesMask don't need to be specified anymore; the values from the original SMBIOS are automatically applied now.Hi
I've installed Martin's config OC 0.7.0 on both cMP5,1(Mid2012) and Big 11.2.3 w/ Radeon RX580 and a cMP4,1(Early 2009) flashed to 5,1 w/ Radeon HD 7950. Both running gr8.
However, on each Mac I'd like to re-enable SIP. I checked csrutil status and csrutil authenticated-root status and both are disabled.
I booted into Recovery and csrutil enable and csrutil authenticated-root enable...when I boot back it returns
csrutil status
System Integrity Protection status: disabled.
csrutil authenticated-root status
Authenticated Root status: disabled
In Recovery I also tried csrutil clear; then did enable. On normal boot both are still disabled
any ideas, cheers Claudio
I've installed Martin's config OC 0.7.0 on both cMP5,1(Mid2012) and Big 11.2.3 w/ Radeon RX580 and a cMP4,1(Early 2009) flashed to 5,1 w/ Radeon HD 7950. Both running gr8.
However, on each Mac I'd like to re-enable SIP. I checked csrutil status and csrutil authenticated-root status and both are disabled.
I booted into Recovery and csrutil enable and csrutil authenticated-root enable...when I boot back it returns
csrutil status
System Integrity Protection status: disabled.
csrutil authenticated-root status
Authenticated Root status: disabled
In Recovery I also tried csrutil clear; then did enable. On normal boot both are still disabled
any ideas, cheers Claudio