then again I never had the kernel panics that were prevented by adding the avxpel patches... so what do I know? =)
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 MonteRand (probably the start of an ongoing saga)
- Thread starter Syncretic
- Start date
- Sort by reaction score
you are not helping the discussion mate. You don't know that that hardware has failed. The last thing to happen was the update...and Apple has been adding problems with AVX since 12.4, which is very likely the cause in my opinion. The message in the KP (given above), allegedly implied possibly the battery needed to be changed, which I already tried.
In any KP there is always a possibility that the hardware is failing and it could be coincidence for sure that it is happening right at the same time that i updated to 12.5.1. or it might just be the update. I have very methodically been trying to narrow it down. You don't have anything useful to add here.
In any KP there is always a possibility that the hardware is failing and it could be coincidence for sure that it is happening right at the same time that i updated to 12.5.1. or it might just be the update. I have very methodically been trying to narrow it down. You don't have anything useful to add here.
then don't bother replying... honestly I feel like your non-stop posting about your problems on this thread I have been monitoring because of title aren't helping the discussion.
If you really want to blame the 12.5.1 update, and were being methodical, why wouldn't you have started with the downgrade/reinstall of 12.5 and see if the problem persisted??
Last edited:
I have been following-along with these reports, all-the-while never having a panic in near memory (maybe? sometime back in the Mojave era).
About a week after I updated to 12.5.1 I began to have regular panics (boot-able, but quickly to a panic in about a minute using my regular User Account (no problem using my Admin Account)).
Seemed obvious that something was pushing the panic button in my user account.
I had just recently started using Block-Block, so I deleted that, and the system seemed ok for a day, or so. Then, the panics returned.
I then realised that I was still using OC 0.7.8, so I updated to OC 0.8.0 . . .
. . . no panics since with:
NoAVXFSCompressionTypeZlib.kext = Enabled
MinKernel = 21.5.0
Now I'm using 12.6, with absolutely no issues. As performant as performant gets with my 5,1
{edit} During the "What the sam-hain is wrong?!" diag., I did replace my BR2032, and it did not seem to influence resolution of the panics.
Replacing the RTC battery only solves the RTC related kernel panics, when the BR2032 battery is below 3.00V and the RTC counters are stuck.
RTC crashes are most frequently the KPs that you get after waking from sleep, but also can also happen in several other situations, but the dead giveaway is if you have a crash after waking from sleep. The RTC battery is the first thing to check in this case.
Ah! Thank you.
When I relised that it was actually the original battery from 2012, it seemed even more an opportune time to replace
I hear you. you had told me before that the KP report itself was indicative of possible RTC problem... but anyway, after changing the battery...it still panic'd again.
I have since done a fresh install of 12.6 and migrated back all my apps, etc.. Well we'll see how this goes...
The fact that @splifingate mentioned his admin account didn't have a problem but his user account did for a while..is crying out as a permissions problem of some kind and its remotely possible that somehow when I updated 12.5.1 something got messed up. Maybe clean install will work. We'll see.
When it crashes here, its not a sudden crash out of nowhere...and doesn't display the kernel panic message either. what happens is that it gets to a beach ball...and hangs for a while...semi functional, the mouse responds but with beach ball, and then eventually the mouse stops responding...and eventually screen goes black. I've been able to watch it happen two times now.
I hope I'm not speaking too soon, but after doing a fresh install of 12.6 + migration...I'm 5-6 days running so far no KP.
Suggest the moderators lock this thread until/unless there are updates specifically related to the subject as I believe quite a few people monitor the thread and are getting kind of spammed at this point.
Maybe it will be useful?
There is an AVX instruction emulator and you can run unsupported applications (or games) using the emulator
Freq Rider wrote: As many here are aware, our cMPs don't support AVX CPU instructions. Intel has a work-around for developing purposes that emulates AVX on older iNtel chipsets in the form of SDE or 'Software Development Emulator.
www.facebook.com
www.intel.com
I tried to run something with the emulator, the terminal gave me an error:libdyld.dylib not found
Intel forum moderator wrote:
"This is a known issue. The pin team plans to add support for macOS Monterey in Q1. Intel SDE will support it in the next release if pin support will be ready on time."
and after a few months:
"We decided to drop macOS support because we see no business needs for providing emulation for future Intel CPUs.
The cost and the complexity of adding support for Monterey in pin was too high and was never added."
although the post on fb shows the successful results running games with this emulator
There is an AVX instruction emulator and you can run unsupported applications (or games) using the emulator
Freq Rider wrote: As many here are aware, our cMPs don't support AVX CPU instructions. Intel has a work-around for developing purposes that emulates AVX on older iNtel chipsets in the form of SDE or 'Software Development Emulator.
Log into Facebook
Log into Facebook to start sharing and connecting with your friends, family, and people you know.
www.facebook.com
Intel® Software Development Emulator
The current version of the emulator corresponds to the Intel® architecture instruction set extensions programming reference (revision 319433-055)
www.intel.com
I tried to run something with the emulator, the terminal gave me an error:libdyld.dylib not found
Intel forum moderator wrote:
"This is a known issue. The pin team plans to add support for macOS Monterey in Q1. Intel SDE will support it in the next release if pin support will be ready on time."
and after a few months:
"We decided to drop macOS support because we see no business needs for providing emulation for future Intel CPUs.
The cost and the complexity of adding support for Monterey in pin was too high and was never added."
although the post on fb shows the successful results running games with this emulator
Last edited:
Did you find a solution to run AVX depending software on Big Sur?
Edit: I probably should assume that this was a futile question.
Making this a very generic one:
Will I ever be able to install Cinema 4D 2023 (or any software asking for AVX) on my classic Mac Pro 5,1 running either Big Sur, Monterey or possible future macOSes, or even Windows?
Last edited:
Turned on voice control on a CMP and it rendered the account that turned it on impossible to login without immediate reboot. Tried the patch in hopes to fix it but no luck. It has not shown any ill sign on another acount or funtionality of OC