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.
I don't see any specific references to Hackintosh. I scrolled back and looked at the post in question, and don't see any specific references to Hackintosh, or non apple hardware.
 
I don't see any specific references to Hackintosh. I scrolled back and looked at the post in question, and don't see any specific references to Hackintosh, or non apple hardware.
I was not talking about any specific post, but in general. I have nothing against hackintoshs, myself was in that stuff time ago for so many years. I´m just saying this is not the right place for that at all.

Why? It´s so easy. When we talk about a problem in mac, we know we are sharing the same basic hardware, besides the adds like pci cards, Usb´s , etc, we can add.

In hackingtosh two persons that say they have the same "mac model", can be talking of totally different hardware and BIOS.


Simply , this is not the right forum for that . And it can be a completely waste of time for most users.
 
Last edited:
As far as I know, OCLP settings always go back to defaults. That doesn't mean to say that this setting wasn't written to the EFI. Do you still have the problem after you set it to Partial? Helped me when I had that issue quite a while ago.
Exactly. The settings in the OCLP app do not read the settings written to the EFI, but rather show the recommended settings, which can be confusing if you are not aware of that intended functionality. AFAIK.
 
You mean me?
I did but I fixed it, using Opencore Configuratior, disabling some kexts and bingo bluetooth works and the correct card BMC_20703A1 is reported in the Apple System profiler. What's odd is I re enabled all of them and bluetooth stilll works, and card still shows BMC_20703A1. Pretty strange.
 
I did but I fixed it, using Opencore Configuratior, disabling some kexts and bingo bluetooth works and the correct card BMC_20703A1 is reported in the Apple System profiler. What's odd is I re enabled all of them and bluetooth stilll works, and card still shows BMC_20703A1. Pretty strange.
That´s so great. Probably, what you disabled was avoiding the card to be recognized by the system. Once recognized, created a plist or kext that persists, even if you reenabled them. Anyway if you would like my config.plist just let me know.
 
  • Like
Reactions: Larsvonhier
I've been running 14.5, and Open Core Patcher 1.5.0 for several days now. Everything is working as expected now that I've changed software I use. Has anyone been able to come up with a fix for the occasional red menu bar tint that comes and goes? Beyond that the only other things are just things Apple has changed in the OS itself. The red menu bar tint isn't even that big of a deal, just wondered if anyone has figured out how to stop it from happening. In my observations, it seems to only happen in certain apps, and once clicked, it goes back to normal.
 
  • Like
Reactions: F1Mac
I've been running 14.5, and Open Core Patcher 1.5.0 for several days now. Everything is working as expected now that I've changed software I use. Has anyone been able to come up with a fix for the occasional red menu bar tint that comes and goes? Beyond that the only other things are just things Apple has changed in the OS itself. The red menu bar tint isn't even that big of a deal, just wondered if anyone has figured out how to stop it from happening. In my observations, it seems to only happen in certain apps, and once clicked, it goes back to normal.
Model? Any picture you can send with that red menu bar tint? I have never seen that.
 
macOS 14.6b2 installed atop b1 OTA, OCLP 1.6n runs as expected.
14.6b2.jpg
 
Last edited:
It's an iMac 17,1, and I don't think the the tint would come out in a screenshot so would have to take a physical picture of the screen itself.
I have an iMac 18,3 (same installation as Macinman, on a thunderbolt 3 external drive) and I occasionally see the same artefact. Not sure it correlates with OCLP though.
 
I know it´s something that can be very annoying for perfectionist (like me), but not a high price for running last macOS in a almost ten years old mac. Don´t you think? Just a simple click. ;)
 
I know it´s something that can be very annoying for perfectionist (like me), but not a high price for running last macOS in a almost ten years old mac. Don´t you think? Just a simple click. ;)
No, as I mentioned not a big deal and it only happens once and a while. I just hadn't used open core in a while so things get fixed in the meantime, so was just checking. I have Linux as an option when macOS doesn't do what I need, and that's one thing I was hoping the Open Core Devs would find a way to do, is bring 32 bit support to the latest macos for that legacy support on the latest OS. However like I said, a dual boot system fixes that problem easy enough.
 
Last edited:
  • Like
Reactions: 0134168
After reverting patches 962mb download on my mid 2014 MacBook Pro installed without issue using OCLP 1.5 .
Did the full install without reverting patches. Worked oob with OCLP 1.5.0.
Login was somewhat difficult, because I had too many windows of different apps open, so window server crashed in a loop. Remedy: Login with held down shift key (immediately after pwd entry) -> this disables the "re-open all windows" function. That let me root-patch the system again. Reboot, viola.
 

Attachments

  • Ohne Titel.jpeg
    Ohne Titel.jpeg
    34.4 KB · Views: 30
  • Like
Reactions: 0134168 and TOM1211
Hey @*******, I just looked up the issue, from two sources and this doesn't seem to OCLP related, it's more a GPU issue in the iMacs it seems as both these sources report it happening on supported macs:

 
  • Like
Reactions: 0134168
Hey @*******, I just looked up the issue, from two sources and this doesn't seem to OCLP related, it's more a GPU issue in the iMacs it seems as both these sources report it happening on supported macs:

Thats why my first question was about your mac model, because of the GPU. I answered "R9"
 
Thats why my first question was about your mac model, because of the GPU. I answered "R9"
Right, I just wanted to clarify for anyone else reading who may have the issue that it's not Open Core specific and that it's a Sonoma issue with iMacs with an AMD GPU. I'm also glad that it's another issue I can put in the Sonoma pile and not open core.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.