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
Updating now. Tell you later.
Attachments
People with NVIDIA Kepler GPUs SHOULD NOT INSTALL 12.5. Apple did changes with Monterey 12.5 that made the Kepler drivers completely un-accelerated, only the frame buffer still works.
It's probably a good* time to replace the GPU for a modern AMD one or stick to 12.4 for the time being, or even downgrade to 11.6.8 (just did that with my MacPro5,1 with GTX 680) since the issue with Kepler drivers is a very complex one.
*good as less horrible than before, since used GPU market is now at a more or less sane levels again.
It's probably a good* time to replace the GPU for a modern AMD one or stick to 12.4 for the time being, or even downgrade to 11.6.8 (just did that with my MacPro5,1 with GTX 680) since the issue with Kepler drivers is a very complex one.
*good as less horrible than before, since used GPU market is now at a more or less sane levels again.
Last edited:
No luck updating. When reboots, boot from “macOs Installer” volume, as usual, but hangs and reboot again.
Tried to boot fron the usual volume, but an empty progression bar appears.
Tried to boot fron the usual volume, but an empty progression bar appears.
Attachments
Last edited:
Sorry. Mac Pro 4,1->5,1. Anyway, it has failed updating with this method many times before.
When released the full installer, I´ll try as usual: clean install and then Migration Assistant.
Last edited:
You can get the full installer from Apple Store, like I did.
why not? And I was asking @trifero that question because his system is crashing. if your system crashes then I will ask you the same thing. what hacks do you have in place to run 12.4 and are you doing any new ones for 12.5? Is your setup the same as CDF's guide in post #1 or are you running some other variation of your own. These are important points...you can say it works for you, but if so then we need to know exactly what you did for it to run fine.
I did not installed the patch because I had no kernel issues with my configuration and EFI, which I generate with Plistlib Generator. The tool is linked into first post, I'm pretty sure none of the tool users have the patch applied also, they usually follow the example setup I provide. I'm currently still on 12.4:
Last edited:
I upgraded to 12.5 without any issues, using the latest release of Plistlib Generator. The difference between my tool and other solutions out there is that the generator allows you to have full control how you build your EFI and configuration. By default, it uses the failsafe suggested OC settings, as intended. You can define in your setup file whatever settings you like to have customized. In the example I applied the settings provided by @cdf, minus the AVXpel patch which I don't use but can be applied easy.
Last edited:
alright, you are not being clear. I am following CDF's guide, which is the purpose of this thread, I don't use your tool and don't plan to. Perhaps you are unwittingly doing the AVXpel patch using that tool and you don't even realize it. In any case, I have backed up my system and attempting update on the backup I will report back shortly. My system is very vanilla following CDF's guide to the letter.
That's an illogical statement, do you understand how OC works?
That's perfect, you use a good approach but your previous comment makes me doubt that. If you remove the AVXpel patch, you will have the same configuration as the one present in my Mac, so should be able to upgrade without issues. I personally avoid any patches, if they are not needed, it might be different for you.
Is up to you what you plan to do, I'm simply sharing that I upgraded without any issues for last 2 versions, without AVXpel patch aplied.
Last edited:
Yes. Do you understand how AVXpel works?
AVXpel is part of cdf’s guide. It is purely plist hack.
Many people had problems without AVXpel that is why cdf added it to the guide. It will depend on your usage pattern of macos.
I am booting 12.5 now should have news in a few mins
AVXpel is part of cdf’s guide. It is purely plist hack.
Many people had problems without AVXpel that is why cdf added it to the guide. It will depend on your usage pattern of macos.
I am booting 12.5 now should have news in a few mins
I updated easily
using martin's config 0.8.0.1 with the syncretic patch,
but after login - the first symptom was a corrupted image on the screen, and then there were reboots and panic
I rewrote my EFI using my macbookpro and replaced opencore with 0.8.2 with my own config from cdf with a syncretic patch.
the system crashed due to kernel panics in a couple of minutes after login.
I didn't even have time to read the kernel panic report.
but what I managed to see was that the panic was due to the avast antivirus,
and also because of the wrong addresses.
then I deleted patch and enabled noAVX kext, and I removed the AVAST antivirus.
Now I'm working fine on 12.5.
there is no panic.
what was the reason: a syncretic patch or an antivirus or both together,
I can’t say.
but with kext and without antivirus 12.5 it works fine
My current OC 0.8.2 with edited cdf config +TBOLT3+radeonsensor+noAVX
My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.2, mac os 12.5
using martin's config 0.8.0.1 with the syncretic patch,
but after login - the first symptom was a corrupted image on the screen, and then there were reboots and panic
I rewrote my EFI using my macbookpro and replaced opencore with 0.8.2 with my own config from cdf with a syncretic patch.
the system crashed due to kernel panics in a couple of minutes after login.
I didn't even have time to read the kernel panic report.
but what I managed to see was that the panic was due to the avast antivirus,
and also because of the wrong addresses.
then I deleted patch and enabled noAVX kext, and I removed the AVAST antivirus.
Now I'm working fine on 12.5.
there is no panic.
what was the reason: a syncretic patch or an antivirus or both together,
I can’t say.
but with kext and without antivirus 12.5 it works fine
My current OC 0.8.2 with edited cdf config +TBOLT3+radeonsensor+noAVX
My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.2, mac os 12.5
Last edited:
IMO, you do not. Otherwise you would not state that people apply configuration changes without their knowledge. Also, the AVXpel patch was created by @Syncretic and is an alternative to the NoAVXFSCompressionTypeZlib.kext created by @khronokernel, which downgrades the Zlib library in order to avoid kernel panics. In macOS 12.4 and 12.5 Beta 1, AVX1.0 was added in AppleFSCompressionTypeZlib. Since our processors do not support AVX1.0, @khronokernel used the AppleFSCompressionTypeZlib from macOS 12.3.1.
Last edited:
Ok thanks for your analysis of what you think I know.
AVXpel is part of cdf’s guide. I consider it essential for 12.4, or some other hack needs to be used that is not in cdf’s guide such as noAVX or perhaps the other one you mentioned. However as I sit here waiting for 12.5 to complete the upgrade I realize that AVXpel is setup with minKernel and max kernel values for only 12.4 and syncretic stated a few months ago it would be necessary with every OS release to verify the patch is still correct and bump up the maxkernel value. So it’s not clear to me right now that 12.5 upgrade should be done until we have clarity about needed AVX hacks.
AVXpel is part of cdf’s guide. I consider it essential for 12.4, or some other hack needs to be used that is not in cdf’s guide such as noAVX or perhaps the other one you mentioned. However as I sit here waiting for 12.5 to complete the upgrade I realize that AVXpel is setup with minKernel and max kernel values for only 12.4 and syncretic stated a few months ago it would be necessary with every OS release to verify the patch is still correct and bump up the maxkernel value. So it’s not clear to me right now that 12.5 upgrade should be done until we have clarity about needed AVX hacks.
That does not mean you need to apply it. Did you had issues, which made you apply the patch or you applied the patch because you saw it into guide? Also, for MaxKernel, you can remove that line or use 21.6.0 value. Have you tried to upgrade without the patch applied? You an always apply the patch after.
I have booted into 12.5 and seems to be working without bumping up the MaxKernel value of AVXpel. So that is good news, but I do know that there are certain usage patterns that have to be encountered in order for the missing AVX functionality to cause a panic.. I'm not sure what those test scenarios would be, in order to find out if 12.5 has somehow been fixed by Apple to not need AVXpel any longer.
However, I read from Syncretic that with each OS update, it would be necessary to verify that any kind of patch like that would need to be verified to be correct and should be verified before bumping up the MaxKernel value, because the binary code being patched may have changed since 12.4. So I will wait to hear from CDF or syncretic on this point before doing that. Anyway, so far....no panic.....
However, I read from Syncretic that with each OS update, it would be necessary to verify that any kind of patch like that would need to be verified to be correct and should be verified before bumping up the MaxKernel value, because the binary code being patched may have changed since 12.4. So I will wait to hear from CDF or syncretic on this point before doing that. Anyway, so far....no panic.....