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.
It is much better when describing the problem to include the mac model.No, sorry. Not my first lenguaje. It is happening in a MacBook Pro 2014 13’ on OCLP 1.5 in Sonoma 14.5
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.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.
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.I tried that but it always reverts back to enabled on its own
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.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.
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.You mean me?
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.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.
14.6 beta 2 - any experiences with OCLP yet?
(I see that at least the suitable KDK 23G5061b is available and OCLP pre-downloads it).
Great.After reverting patches 962mb download on my mid 2014 MacBook Pro installed without issue using OCLP 1.5 .
Model? Any picture you can send with that red menu bar tint? I have never seen that.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.
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.Model? Any picture you can send with that red menu bar tint? I have never seen that.
Nice!macOS 14.6b2 installed atop b1 OTA, OCLP 1.6n runs as expected.
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.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.
If I remember well, it´s Radeon 9, right?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.
yes, it is and here are a couple picturesIf I remember well, it´s Radeon 9, right?
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.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.![]()
Did the full install without reverting patches. Worked oob with OCLP 1.5.0.After reverting patches 962mb download on my mid 2014 MacBook Pro installed without issue using OCLP 1.5 .
eclecticlight.co
Thats why my first question was about your mac model, because of the GPU. I answered "R9"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:
![]()
Red menu bar in Sonoma
Occasionally, switching apps in Sonoma’s Stage Manager sets the whole menu bar to red, and loses menus on its left. What’s the cause?eclecticlight.co
Menu Bar on iMac 27 turns red - Apple Community
discussions.apple.com
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.Thats why my first question was about your mac model, because of the GPU. I answered "R9"