Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Which vBIOS version do you have installed? Does this version support brightness control on your system?
If not check back on the iMac GPU thread in case you missed the vBIOS update posted more than a year ago.
I don't know exactly which version. This version that is installed does not support native brightness control. I will revisit the topic about the iMac GPU and see how the vBios update procedure does. The current version installed on the GPU is well over 1 year old.
 

Attachments

  • WhatsApp Image 2022-08-21 at 10.05.14.jpeg
    WhatsApp Image 2022-08-21 at 10.05.14.jpeg
    281.8 KB · Views: 84
  • WhatsApp Image 2022-08-21 at 10.05.14(1).jpeg
    WhatsApp Image 2022-08-21 at 10.05.14(1).jpeg
    330.4 KB · Views: 83
Updated to 21G83 using 0.4.10. No issues.
On my iMac 15,1 Late 2014, running Monterey 12.5.1(21G83) via OCLP 0.4.10, Outlook has started to stop working and that shows in the Activity Monitor as "Microsoft Outlook is not responding" - but it uses a high % of the CPU.
Anyone else or any ideas? Will have to disable Spotlight and thus stop the indexing, just to get my work done.
Edit: The cause of this was the Windows mail I was opening. It had a HUGE message history under the top level message. Obviously it was way over the level that Office 2019 for Mac can handle. Mail from other clients, even with 2 or 3 years of messages, works fine, as does a new message.
This is the first time I have run into this Office bug.
 
Last edited:
Thanks to the latest developers efforts, with OCLP 0.4.10 I got the following Kepler cards up and running in Mac Pro with macOS 12.5. Full acceleration/metal, login problem solved:

GT630 2GB
Quadro K600 1GB
Quadro K420 1GB
(no bootscreen due to PC firmware on card)

So I add my big kudos to the community that again made this possible!
I want to get the gt630 working properly on my hack, the frame buffers are guessed at 4 HDMIs. The question I have for you is do you know if this is a patch on something like nvidia resman or something? In that case would be doable on a hack. Would even be happy staying on big sur if could get the correct FBs.

Was a MVC and tried flashing back to factory but that was not the right guess! Though expensive for what it was did not care since could now use the rx580 in the cMP haha... Plus had bought a gtx 780 thought to be regular for super cheap turned out to be MVC...
 
Last edited:
Hey all. I have 12.5.1 running under OCLP 0.4.10 on a mac pro 5,1. I just noticed that under system prefs->sharing->media sharing, nothing appears. The preference pane is missing. Also other computers on the LAN cannot load the music library. Any ideas?
 
I want to get the gt630 working properly on my hack, the frame buffers are guessed at 4 HDMIs. The question I have for you is do you know if this is a patch on something like nvidia resman or something? In that case would be doable on a hack. Would even be happy staying on big sur if could get the correct FBs.

Was a MVC and tried flashing back to factory but that was not the right guess! Though expensive for what it was did not care since could now use the rx580 in the cMP haha... Plus had bought a gtx 780 thought to be regular for super cheap turned out to be MVC...
Don´t know exactly how you want to split the outputs to 4 displays, but I found the tool ResXtreme very helpful for modifying screen rez and colour depth/pixel. The tool still runs fine on Monterey. Perhaps contacting the author for source code or implementation of new features can be a way?
 

Attachments

  • Bildschirmfoto 2022-08-22 um 09.16.04.jpg
    Bildschirmfoto 2022-08-22 um 09.16.04.jpg
    71 KB · Views: 47
Strange observation with 12.5.1 and OCLP 0.4.10 on a MacBook Pro 8,2:
This machine has a HD3000 iGPU and Radeon 6xxx dGPU (both need non-metal accel patch).

Installation of (upgrading from Catalina) 12.5.1 went without hickups, OCLP finds the correct patch set (it reports both GPUs) and patch goes without errors.

After rebooting nothing changed, no acceleration and no transparent window panes.
Tried this a second time, same result.

Only after NVRAM-disabling the dGPU, so that only HD3000 is "visible" and re-patching, everything works as expected.
Just the AMD/ATI is missing then.

Any ideas or reports that this is (un-)avoidable? I have not yet tested older OCLP versions, but would think this is not a new bug of 0.4.10 ... ?
 
Hey all. I have 12.5.1 running under OCLP 0.4.10 on a mac pro 5,1. I just noticed that under system prefs->sharing->media sharing, nothing appears. The preference pane is missing. Also other computers on the LAN cannot load the music library. Any ideas?
Hm. Just checked. Pane and entry (3rd from top) are there with my 12.5.1 on Mac Pro 5,1. Patched also with 0.4.10.
 

Attachments

  • Bildschirmfoto 2022-08-22 um 09.26.00.jpg
    Bildschirmfoto 2022-08-22 um 09.26.00.jpg
    83.1 KB · Views: 64
Strange observation with 12.5.1 and OCLP 0.4.10 on a MacBook Pro 8,2:
This machine has a HD3000 iGPU and Radeon 6xxx dGPU (both need non-metal accel patch).

Installation of (upgrading from Catalina) 12.5.1 went without hickups, OCLP finds the correct patch set (it reports both GPUs) and patch goes without errors.

After rebooting nothing changed, no acceleration and no transparent window panes.
Tried this a second time, same result.

Only after NVRAM-disabling the dGPU, so that only HD3000 is "visible" and re-patching, everything works as expected.
Just the AMD/ATI is missing then.

Any ideas or reports that this is (un-)avoidable? I have not yet tested older OCLP versions, but would think this is not a new bug of 0.4.10 ... ?
Most people disable the Radeon anyway due to its terrible history of giving up the ghost and taking the whole computer with it. Only a small percentage of this model have lasted this far. I have one too, still working as a backup mail machine, with the Radeon GPU disabled).
Running Big Sur is much easier, but I have installed Monterey now. The heat this machine generates is considerable, and Macs Fan Control works hard to keep the heat under control. I would advise you give up on the idea of getting more speed from the Radeon and just enjoy using an 11 year old Mac running the latest macOS (of course not the very latest!) Thanks to the OCLP devs!
 
12.5.1 runs just fine on my Ivy Bridge mini.

View attachment 2044204
I ended up going back to Big Sur on my MM6,1. I have the i5 one. 12.5 worked perfectly but the 12.5.1 did something weird. After the install it was continually blue screening on boot - got into safe mode to re-install the Root Volume patches and it would not accept my password to elevate to root privileges even though it works everywhere else. Downloaded the TUI version from the github but even though it said it was installing the patches it still would only boot in safe mode except for the occasional random time. Plus the Time Machine Migration Assistant (when it did boot) would go through the motions of reinstalling all apps and user data but after reboot - nothing was copied off and it wouldn't boot unless in safe mode. TBH it's no longer an important mac - I only run Logic on it!

But wondering if anyone has seen anything similar
 
Quick Q

If i wanted to recreate a 12.5.1 installer for a macmini6,1 on a macbookpro11,3 - is it as simple as - in OCLP - change device to mm6,1, build opencore and install to the usb drive and then create the installer?
Yes, this is the reason why there is a model selection at all. Do not touch any other settings available - mostly developer stuff.
 
I add that to act in original mode, I first deleted all contents of EFI OpenCore.
I used OpenCore Configurator in Catalina to activate the EFI partition on the Desktop and to delete the inside EFI folder.
So, I rebooted deleting the PRAM by holding down the CMD+Alt+PR keys on the Gong until I heard the Gong a couple of times.
So at new Gong I held down the Alt Option key until the Disc where I have Catalina appeared and so, after starting and updating Catalina:
- I started OCLP 0.4.9 and installed the EFI Boot in the EFI partition of the main SSD where I have Monterey.
- I opened System Preferences and select as Startup Disk the one I have Monterey on.
- I rebooted and at the Gong I pressed Alt until the OCLP's EFI Boot icon appeared.
So, I clicked on it while holding down the CTRL key.
Note: CTRL pressed during select and click on EFI Boot is a trick almost always useless; but it could be useful for those who do not realize that exist other EFI partitions in which is installed the OpenCore EFI Boot. By pressing the CTRL key during press Enter, therefore, you set this latest "EFI Boot" as default.
Referring to your post of 23rd July you have highlighted an issue that I have on pretty much exactly the same system as you have, including the same internal SSD. My EFI version is stuck on 432.60.3.0.0, but it looks like you've managed to get yours to where it should be as reported by SilentKnight. I can boot into Catalina but applying the July security update has not done the trick. I'm hoping you can explain the section above a bit more for me...how do I use OCLP to show the EFI folder when booted in Catalina? Cheers
 
well I unpatched to get smaller update OTA as usual and that has put me back at a log in loop with no safe mode accessible either I’m going to download full installer and give that a go looks like I’m the first one to fail . Suppose you shouldn’t unpatch first ?.
I didn't unpatch, figuring there was less chance of hitting the login loop issue. Installing the full update OTA went super well, and on first login OCLP auto-prompted me to reapply the patches because the installer removes them.

The 11 GB full installer download thing is inevitable with SIP/SSV being partially disabled; I can see why Apple does that. How can an installer do a safe incremental update unless the system is locked down and therefore a fully known and understood entity? The answer is it can't at present, and probably never will.
 
I didn't unpatch, figuring there was less chance of hitting the login loop issue. Installing the full update OTA went super well, and on first login OCLP auto-prompted me to reapply the patches because the installer removes them.

The 11 GB full installer download thing is inevitable with SIP/SSV being partially disabled; I can see why Apple does that. How can an installer do a safe incremental update unless the system is locked down and therefore a fully known and understood entity? The answer is it can't at present, and probably never will.

Still I’ve had no problem doing it this way with no errors till 12.5 and I’m going to try again to see if it’s just the graphics card throwing up the error or not.
 
  • Like
Reactions: rehkram
Hi everyone, I'm just checking if anyone else has experienced regular crashes (from 12.1 to present) It seems to be window server related where the system freezes and then either logs you out or reboots (not related to the 12.5 GPU issues. I'm currently on 12.4). I sometimes get these multiple times per day. I never had these issues with Big Sur on an iMac (21.5-inch, Late 2012)
 
Looking for advice from others who have installed Monterey using the MyBootMgr RefindPlus/OC chainloader.

I’m looking for a workflow for installing Monterey on my cMP (see my signature for my system details) when using MyBootMgr 0.8.3 installed OC chainloaded from RefindPlus. I plan to clean install Monterey on a separate blank SSD in a SATA II bay for testing before finally updating my main production BigSur system. Will the default OC_ALT config.plist (with VMM and Monterey options enabled) be enough or do I need to make further changes? Will I have to use OCLP in any way? I’ve never used that for my other macOS boot systems (Mojave or BigSur).
 
Still I’ve had no problem doing it this way with no errors till 12.5 and I’m going to try again to see if it’s just the graphics card throwing up the error or not.
I'm betting that the recent Kepler fix that appeared in OCLP 4.10 is the change that created the different behavior but I could be wrong. I'm assuming you're using OCLP 4.10, correct? Did you use it for the previous installs?
 
On my iMac 15,1 Late 2014, running Monterey 12.5.1(21G83) via OCLP 0.4.10, Outlook has started to stop working and that shows in the Activity Monitor as "Microsoft Outlook is not responding" - but it uses a high % of the CPU.
Anyone else or any ideas? Will have to disable Spotlight and thus stop the indexing, just to get my work done.
Edit: The cause of this was the Windows mail I was opening. It had a HUGE message history under the top level message. Obviously it was way over the level that Office 2019 for Mac can handle. Mail from other clients, even with 2 or 3 years of messages, works fine, as does a new message.
This is the first time I have run into this Office bug.
In my experience, even with mega WAN site databases and their supporting client apps' docs, supposedly intended to help us all figure out and manage the next incoming tide of paid-for c*** once and and forever, it remians a perrenial struggle.

For small companies such things become a major burden to the point where the owner may finally shrug and say "are you kidding me?", or in my case "see you after the pandemic but only when your account is up to date. COD terms only, no exceptions".

Folks running MacBooks as email servers is interesting, unless you're not at all concerned about the possibility of anyone reading your mail. You may have a point unless you've linked your common address to a gmail one. Of course I get that, security should be a lifelong pursuit. Strive to say say nothing on gmail (or anywhere else) that could be misinterpreted. Keep in mind that SSL is powerful but increasingly crackable given the growth in horsepower. Yikes.
 
Last edited:
I just upgraded an MBP11,3 and an MBP11,1 from macOS Big Sur 11.6.8 (supported) to Monterey 12.5.1, on the internal SSD: sofar, everything works quite well (apart from some minor glitches immediately after the upgrade)… :cool:
 
Most people disable the Radeon anyway due to its terrible history of giving up the ghost and taking the whole computer with it. Only a small percentage of this model have lasted this far. I have one too, still working as a backup mail machine, with the Radeon GPU disabled).
Running Big Sur is much easier, but I have installed Monterey now. The heat this machine generates is considerable, and Macs Fan Control works hard to keep the heat under control. I would advise you give up on the idea of getting more speed from the Radeon and just enjoy using an 11 year old Mac running the latest macOS (of course not the very latest!) Thanks to the OCLP devs!
Ok, what about "the rest of us", still using the Radeon? I asked because while I´m well aware of those microballing and heat issues my machine is not yet affected and that strange patching behaviour is new now. So thanks for the time you took to answer, but that was not the question...
 
Last edited:
I'm betting that the recent Kepler fix that appeared in OCLP 4.10 is the change that created the different behavior but I could be wrong. I'm assuming you're using OCLP 4.10, correct? Did you use it for the previous installs?

yes using OCLP 4.10 after testing again to get the smaller OTA it works fine unpatched to get in safe mode when using Iris pro I think I somehow I made a mistake and made it default to Kepler causing the loop and no safe mode because OCLP has a revert patches I’ve never seen a problem in using it for safety yes i get downloading the full installer makes sense but have never needed to .
 
  • Like
Reactions: rehkram
Installing Monterey 12.5.1 was a fairly easy process with my (MyBootMgr v083) RefindPlus|OpenCore setup on my cMP 4,1>5,1 - see my sig for my system setup. I simply booted into BigSur via my OC_ALT instance of OpenCore, downloaded the full Monterey installer via System Preferences>Software Update and installed it on a blank SSD. It had to reboot a couple of times, and the OpenCore picklist diligently defaulted to the macOS Installer, then back to the Monterey SSD at the end, and everything went fine. I don't usually have my cMP set to go to sleep, so I was pleasantly surprised to have to wake it up after I went out for a while and for it to resume without throwing a wobbly.

Hopefully this helps anyone else using the RefindPlus|OpenCore chainloader to install. When I'm ready, I assume I can upgrade over the top of my production system running BigSur via the same method.
 
I have a similar setup. Warning, I was able to update to 12.5.1 easily using system preferences update... no problem. I did use VMM. However, after a few days of running it has KP'd twice. Sometimes it gets stuck while booting up also, but someone suggested using -v boot-args which so far seems to help it boot without getting stuck. But the KP's came later while I was away from the desk both times so I have no idea what caused them. I never use sleep and have it set to never. I am suspicious that something is amiss with this update.
 
Wise and considered words to help steer me. I wonder if OCLP has a setting which can slow the boot process down, rather that my verbose mode work-around? Anyway, it may be timely for me to reflash my Matt Card with the reconstructed ROM done expertly by tsialex, as the ROM chip registers may just be getting a bit full or have conflicting drive cache settings, seeing I boot in and out of 10.6, 10.12 and 12.5 regularly. Starting with a clean slate may give me a better rate of successful Monterey boots - seeing few, if any, other 5,1 users have reported boot problems (baring the boot loop issue which I haven't experienced).
[Update] I reflashed my ROM chip but am still getting boot stalls at about the 1/3rd way point. I'll add -v to my OCLP boot string until a better solution comes along. I'm still incredibly grateful to have my 5,1 running so well on the latest OS.
Latebloom does this, guess this workaround is no longer part of the standard config generated by OCLP since SurPlus replaced it as a real solution. Even this solution had only a short life time since Apple fixed the bug later on.

But I really do not know if it is a good idea to hide problems (by using boot delays) instead of trying to figure out the root cause of your problem.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.