macOS 12 Monterey on Unsupported Macs Thread

[mwidjaya]

Thank you h9826790. The reason I ask is because my MBP has a hanging habit. It beachballs regularly for 30 seconds at a time without any CPU spiking or with just Opera browser open. Disk Activity reveals no clues as to why. CPU activity does not change when beachballing occurs. I read of other installs of Monterey using OCLP on mbp 5,1 who have a completely smooth experience. I cannot seem to track down why this is happening. Is there are a more intense disk activity scrutinising software that would flag up what's happening at the point of beachballing occuring? Could it be something involving the graphics switching being deactivated?

Suggest you redo the root patch. I suspect any time you apply software updates, you will need to reapply root patch.

Still, I continue to be impressed by the work done by OCLP devs. Massive kudos.

Finally got my 2010 MacBookPro7,1 onto Monterey and it is running quite well, despite being more than a decade old and non-metal.

 

[Staygrade]

Dying hard disks or SSDs can cause such a behaviour.
I once had a nearly new SanDisk SSD which behaved like that after a short period of using it for macOS; it had to be reset in order to work well again, so it was some firmware error of the SSD controller. Never used that SSD for macOS again.

Suggest you redo the root patch. I suspect any time you apply software updates, you will need to reapply root patch.

Still, I continue to be impressed by the work done by OCLP devs. Massive kudos.

Finally got my 2010 MacBookPro7,1 onto Monterey and it is running quite well, despite being more than a decade old and non-metal.

View attachment 2125688

I reinstalled the root patches.I have read that it might need to be done twice before rebooting, so I have done that plus I then ran First Aid in Disk Utility. Oddly, WITHOUT rebooting my machine ran smoother with fewer hangs. I have also reset the NVRAM which helped too.

Following h9826790's advice to look at Console I came across advice to First Aid the Keychain (now under Keychain Preferences as 'Reset Default Keychains...' . After doing this and restarting we do seem to be getting somewhere. The hangs are less frequent but still 30 seconds and some occurrences hang without the appearance of the Beachball jut a frozen cursor.

I'm hoping with Console I can track down the final culprit causing the now less frequent hangs. Hoping it isn't the 1 year old Crucial SSD (internetzel).

What should I be looking for in Console and under which Report?

 

[Staygrade]

Did you check console?

What should I be looking for in Console and under which Report?

 

[h9826790]

What should I be looking for in Console and under which Report?

If beachball happen every 30s, you may able to catch up some strange repeatative items' pattern in the streaming log.

 

[Staygrade]

If beachball happen every 30s, you may able to catch up some strange repeatative items' pattern in the streaming log.

Sorry if I mislead; it is not happening every 30s - the duration of the beachballing is 30s. How often it happens varies, though less often now with the help from you guys. It will do it shortly after booting - every time! And then I can be in my browser, and click on the dock Disk Utility icon to open it and BAM off it goes again, another 30s.

 

[h9826790]

Sorry if I mislead; it is not happening every 30s - the duration of the beachballing is 30s. How often it happens varies, though less often now with the help from you guys. It will do it shortly after booting - every time! And then I can be in my browser, and click on the dock Disk Utility icon to open it and BAM off it goes again, another 30s.

Then may be one of your hard drive (can be externally conencted) causing the issue.

Your discription sounds like the computer wait for the hard drive I/O return. Therefore, when you first run Disk Utility after boot, your Mac will scan through all hard drive, and tigger this issue.

 

[ChrisOSX]

First of all thank you for the reply to my post in that structured way. Would have been nice beforehand, instead of telling me how dumb I am having a problem.
All you wrote I knew already, due to my research before.
I did replace the complete OC and it didn´t work, hence my seek for help.
I managed to mount the EFI and replace the ALC, but that didn´t help either. So I think there is some deeper problem with my system ...

If I reboot my system while holding ALT, there are two options to boot into my system
1) EFI boot
2) System boot, in that case "Monterey"

Both options seem to do the same and replacing the ALC either way having no effect.

EDIT: Strange thing I just discovered is that by booting the EFI with "sudo diskutil mount EFI" now the EFI is empty.


I did reset the PRAM/NVRAM.


I did read the OLCP docs a while ago and now again and did spent hours on websites to figure it out. I surely dont look for shortcuts, but couldnt figure out the terminal commands to replace the ALC via terminal ... therefore I am here.


I understand how docs are working ! I did wrote over 100 educational books.
It is not a question of a few developers not willing or having the time to help. At a forum like this there are surely more guys having a similar problem and have the potential to help.
That´s the definition of a forum. If I can help I will happily do it and don´t call the questioner an oportunist or whatever. That´s a crazy thought in general !
Surely it would not be a problem to establish a forum full of experts, which will flatter each other at least 3 times a week.

So I absolutely appreciate that you took the time and replied ! Thank you !

I will wait for an new oclp version, i see no reason for now to do the work arround.

Thanks anyway.

New version of OpenCore Nightly fixes the audio.

0.5.3​

• Integrate FixPCIeLinkrate.efi v0.1.0
  • Fixes link rate for PCIe 3.0 devices on MacPro3,1
• Resolve AppleIntelCPUPowerManagement Panic in Safe Mode
  • Applicable for pre-Haswell Macs on Ventura
• Revert AppleALC 1.7.6 update back to 1.6.3
  • Resolves audio issues on certain Intel HDEF devices
  • Regression currently being investigated within AppleALC

 

[spacebiscuit]

I recently upgraded the GPU in my 2011 21" iMac, I followed the tutorial and flashed the vbios for the Nvidioa K1000M card and all went well. I then attempted to install Monterey via the Open Core patcher (latest available version). As instructed I created the usb installer, I then booted via the usb and proceeded to install. during the process the mac restarts and on the 3rd restart I get stuck on black screen with Apple logo at around 30-40%.

I've Googled for solutions and found a few TY videos. Have tried rebooting, installing again, clearing the PRAM but it always gets stuck in the same place. Another tip recommended booting into Safe Mode however I do not seem to be able to get to Safe Mode, holding down shift and rebooting just gets me to the boot option menu.

So I'm a little lost and don't know where to turn next, any ideas or suggestions that might help me troubleshoot this?

Thanks in advance.

 

[hwojtek]

New version of OpenCore Nightly fixes the audio.

No, this is not the "new version of OpenCore Nightly".
Nightlies are built, like, every night, so there is a "new version" every night.
And this is a nightly of Open Core Legacy Patcher. Please don't create confusion with less-than-well redacted posts.

 

[ChrisOSX]

No, this is not the "new version of OpenCore Nightly".
Nightlies are built, like, every night, so there is a "new version" every night.
And this is a nightly of Open Core Legacy Patcher. Please don't create confusion with less-than-well redacted posts.

At the time of the post is was the current nightly build. And I understand the term "Nightly". However, if you pay attention to the time stamp on the change log, you can see the last time it was updated. Weird huh.

I also did state in the post:

New version of OpenCore Nightly fixes the audio.

Notice the word Nightly? And if you cared to follow the link, it will direct you to the "Build and run from source" page. So whatever the user decides to download will be the current one. If they choose to do so.

I'm not trying to "create confusion" as you put it. I think it was simply explained. Any user in the game of unsupported modification, I would hope they would read the change log.

Simply put. I directed users to a source to fix their audio issue, not a direct download. 👍

 

[hwojtek]

However, if you pay attention

However, if you paid attention, you'd noticed the difference between "latest nightly build of Open Core" and "latest nightly build of Open Core Legacy Patcher", mainly because the Open Core versions are different between them, wouldn't you?

 

[ChrisOSX]

However, if you paid attention, you'd noticed the difference between "latest nightly build of Open Core" and "latest nightly build of Open Core Legacy Patcher", mainly because the Open Core versions are different between them, wouldn't you?

Given the 2 users I directly quoted are OCLP users as they mentioned in the posts I quoted (#8,132 for reference), and I directed them to the OCLP page, I would think I know the difference between the 2 installers. 👍

This is the point of quoting right? Now if I wasn't quoting, and putting a broad statement with a screenshot of it all working on my machine, I would have been more descriptive in my statement.

 

[hwojtek]

Given the 2 users I directly quoted are OCLP users as they mentioned in the posts I quoted (#8,132 for reference), and I directed them to the OCLP page, I would think I know the difference between the 2 installers. 👍

And yet you stated incorrectly, that the latest Open Core nightly fixes the sounds problem, contrary to the actual fact that you meant Open Core Legay Patcher nightly, thus creating a confusion. Please try to be precise next time.

 

[Staygrade]

Then may be one of your hard drive (can be externally conencted) causing the issue.

Your discription sounds like the computer wait for the hard drive I/O return. Therefore, when you first run Disk Utility after boot, your Mac will scan through all hard drive, and tigger this issue.

Hi, these two log entries in Errors and Faults in Console appear when beachballing occurs for 30s. can you help with what they mean and how to fix please?

Opera [0x10807bf2220] Bad CurrentVBLDelta for display 69673216 is zero. defaulting to 60Hz.

kernel System Policy: symptomsd(185) deny(1) system-privilege 10006

 

[Ausdauersportler]

I recently upgraded the GPU in my 2011 21" iMac, I followed the tutorial and flashed the vbios for the Nvidioa K1000M card and all went well. I then attempted to install Monterey via the Open Core patcher (latest available version). As instructed I created the usb installer, I then booted via the usb and proceeded to install. during the process the mac restarts and on the 3rd restart I get stuck on black screen with Apple logo at around 30-40%.

I've Googled for solutions and found a few TY videos. Have tried rebooting, installing again, clearing the PRAM but it always gets stuck in the same place. Another tip recommended booting into Safe Mode however I do not seem to be able to get to Safe Mode, holding down shift and rebooting just gets me to the boot option menu.

So I'm a little lost and don't know where to turn next, any ideas or suggestions that might help me troubleshoot this?

Thanks in advance.

Check the OCLP online guides about safe mode booting with OpenCore. It may need a little patience on your side and you may have to read through all pages with a little bit concentration, but on this way you will gather a lot of knowledge really valuable when using this great tool.

 

[internetzel]

Hi, these two log entries in Errors and Faults in Console appear when beachballing occurs for 30s. can you help with what they mean and how to fix please?

Opera [0x10807bf2220] Bad CurrentVBLDelta for display 69673216 is zero. defaulting to 60Hz.

kernel System Policy: symptomsd(185) deny(1) system-privilege 10006

Apparently the Opera web browser (?) tries to synchronize its frame rate to the current refresh rate of the display - but it cannot find a valid value.
Does the problem only occur when that "Opera" application is running?

 

[spacebiscuit]

Check the OCLP online guides about safe mode booting with OpenCore. It may need a little patience on your side and you may have to read through all pages with a little bit concentration, but on this way you will gather a lot of knowledge really valuable when using this great tool.

Thanks - just to add I left the installer going for 9 hours over night and the progress didn't move.

I've tried safe mode, holding shift+enter at the boot option but the mac just boots to that 30% progress as before, I can't even get into Safe Mode.

By the way, if I remove the usb stick with the installer and I try to boot I get a grey forbidden sign (ciircle with line through) and the mac powers down after about 30 seconds. Seems I don't even have a partial or broken install on my ssd.

 

[ChrisOSX]

And yet you stated incorrectly, that the latest Open Core nightly fixes the sounds problem, contrary to the actual fact that you meant Open Core Legay Patcher nightly, thus creating a confusion. Please try to be precise next time.

I stated correctly to the audience I was addressing that to.

There’s no confusion, maybe on your part, but I don't see other people complaining. You’re simply looking for a reason to say something. And now it’s turned into a pointless multi post. Cool.

If you take a glance and the very first post of this thread, everything pertains to OCLP.

Lastly, finally and end of dicussion on my part, I knew my target audience. Regardless if I abbreviated it or not, we are in a OCLP thread, so why sould I feel the need to specify otherwise? Please try to gatekeep less over silly things. 👍✌️

 

[Staygrade]

Check the OCLP online guides about safe mode booting with OpenCore. It may need a little patience on your side and you may have to read through all pages with a little bit concentration, but on this way you will gather a lot of knowledge really valuable when using this great tool.

Apparently the Opera web browser (?) tries to synchronize its frame rate to the current refresh rate of the display - but it cannot find a valid value.
Does the problem only occur when that "Opera" application is running?

I have just worked for an hour in Firefox AND with VirtualBox runing Windows and have had NO beachballing. So, so far, yes, it's only happening when Opera is open.

 

[Staygrade]

Apparently the Opera web browser (?) tries to synchronize its frame rate to the current refresh rate of the display - but it cannot find a valid value.
Does the problem only occur when that "Opera" application is running?

I have been using in Firefox for 4 hours and had only one beacballing occurance with Console providing the same Error report. The one other application I have open is VitualBox running Windows. These are the pertinent error logs:
firefox [0x1253f1a20] Bad CurrentVBLDelta for display 69673216 is zero. defaulting to 60Hz.
kernel System Policy: kernel_task(0) deny(1) system-privilege 10006

 

[wolf1734]

Hello I would like to know if I can update Monterey 12.4 to 12.6.1 on my Mac Pro 5.1 without any problem. Monterey is installed with OCLP 0.4.5 Tui. what should i do, thank you

 

[internetzel]

I have been using in Firefox for 4 hours and had only one beacballing occurance with Console providing the same Error report. The one other application I have open is VitualBox running Windows. These are the pertinent error logs:
firefox [0x1253f1a20] Bad CurrentVBLDelta for display 69673216 is zero. defaulting to 60Hz.
kernel System Policy: kernel_task(0) deny(1) system-privilege 10006

So, this seems to be a general issue on your machine and /or OS installation, since it's not limited to a single process.
Might be related to graphics patches for older GPUs possibly needed for your machine.
You might try to create a fresh new user account and see whether it happens there as well.

 

[trifero]

Hello I would like to know if I can update Monterey 12.4 to 12.6.1 on my Mac Pro 5.1 without any problem. Monterey is installed with OCLP 0.4.5 Tui. what should i do, thank you

12.6.2 is out.

 

[trifero]

All fine in a Macbook pro 17" 2011

 

[mwidjaya]

Updated to 12.6.2. Got the prompt to redo root patch, let it. Looks ok.