I assume you should be able to use the terminal command to bless the EFI boot partition you want to boot to. The Dortania guide has instructions for unflashed GPUs that should work.
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.
macOS 12 Monterey on Unsupported Macs Thread
- Thread starter khronokernel
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I didn't check that earlier since it was related to iMac/MacPro.
I did however give it a try, but couldn't mount the EFI in terminal diskutil, nor could I bless it:
No mount point for /Volumes/EFI
Can't determine mount point of '/Volumes/EFI'
Could not extract mount point
In the Monterey thread, page 217, post #5,415, there is mention of a free efi mount app, and there is the mount efi script available on the OCLP page. I am not sure that either will solve your problem, but you should be able to mount the efi partition.
Thinking of upgrading my MacBookPro 8.2 from a dosdude patched install to OCLP Monterey.
Can I just upgrade (no formatting etc.)?
One little typical Mac-like feature that doesn’t work for me on MacBookPro4,1 after applying the root patch is the drag-and-drop of volume or folder icons from the deskop in an app’s open/save file dialog window. Normally it would change the file path in the dialog to the item, that has been dragged into it.
I’ve tested this with a newly installed Monterey 12.6.1, without root patches applied it did work as expected. After applying root patches (oclp 0.5.1 release version) that drag-and-drop feature isn’t working any longer.
This is by no means a show-stopper, but would still be nice if could brought back somehow with the root patch.
I’ve tested this with a newly installed Monterey 12.6.1, without root patches applied it did work as expected. After applying root patches (oclp 0.5.1 release version) that drag-and-drop feature isn’t working any longer.
This is by no means a show-stopper, but would still be nice if could brought back somehow with the root patch.
Last edited:
The feature still works for me, 12.6.1 on MacPro3,1. Sometimes it actually moves or copies the dragged item instead of just changing the path (the option key can be used to copy the dragged item except when you drag it to the path popup menu which probably makes that the safest place to drag to).
Is there a way to check what OCLP patches are installed or what version? Or which OCLP was booted - the location of the injected kexts?
I booted from an older patched EFI from a internal SSD (still running Monterey 12.3.1), but will now also try to boot fully from the external flash drive where the 12.6.1 system is on.
EDIT:
Now fully booted from the external flash drive, with freshly patched EFI (oclp 0.5.1) on it, but no dice. Same es before, drag-and-drop into file open/save dialog has no effect.
Observation: After drag-and-drop let go of the mouse button quickly the semi-transparent icon is moving back in a straight animation to the icons location on the desktop, which seems to visualize that the drag-and-drop operation to this area is not permitted, or said differently: the app doesn’t support that operation, while it normally should.
Last edited:
i'm afraid not, and will result in a KP.
dosdude1 patches are in the way, and seems they cannot be removed..
Make a backup before hand, if you try and and get succes let me know thanks
Hello all,
I have a strange problem with OCLP on an iMac11,3 (new GPU W6170M): when I start OCLP it tells me that I have the wrong settings. Apparently OCLP thinks my iMac is a 11,1 but it definitely is a 11,3.
It is not a big problem because everything works fine (as far as I can tell) but I would like to know why this happens.
Thanks
I have a strange problem with OCLP on an iMac11,3 (new GPU W6170M): when I start OCLP it tells me that I have the wrong settings. Apparently OCLP thinks my iMac is a 11,1 but it definitely is a 11,3.
It is not a big problem because everything works fine (as far as I can tell) but I would like to know why this happens.
Thanks
I did not run a "scratch install". I just used the Open Core Patcher OCLP 0.5.1 to install patcher and MacOS... it was very similar to an "OS version upgrade" over the air. All my settings and user files are still there and I am working with the same environment (including my Anaconda programming environment for Python). I made a full backup but it was not needed to restore any files or settings.
Excluding minor well known issues related to "non metal"machine (I have a 8.1) everything is running fine ... I would say with the same speed I had with Dosdude1-Catalina patcher.
Thanks for your message.
I will try an iclp monterey upgrade again over an dosdude1 patched mojave install.
If that does not work, i will upgrade it first to dosdude1 catalina, and then upgrade to oclp monterey..
Hope that that perhaps might work
EDIT: I'm leaving this post below for historical purposes, but after re-running OCLP 0.5.2 to create a MBP6,2 EFI, the kernel patches referenced below now appear in the OCLP-generated config.plist. I do not understand why these did not appear the first time I ran OCLP 0.5.2.
=======================================
I'm testing OCLP 0.5.2 on my HackBookPro6,2 and discovered something that I think might be an OCLP 0.5.2 bug. I just want to check here before diving too far into a rat hole to debug this. The MBP6,2 EFI generated by OCLP 0.5.2 omits the following kernel patches that were present in the EFI generated by OCLP 0.5.1:
EDIT: I'm aware that the third patch (Reroute kern.hv_vmm_present patch (2) Ventura) had a MinKernel = 22.0.0, so only the first two kernel patches are applicable to Monterey.
Thank you.
=======================================
I'm testing OCLP 0.5.2 on my HackBookPro6,2 and discovered something that I think might be an OCLP 0.5.2 bug. I just want to check here before diving too far into a rat hole to debug this. The MBP6,2 EFI generated by OCLP 0.5.2 omits the following kernel patches that were present in the EFI generated by OCLP 0.5.1:
- Remove kernel patch Reroute kern.hv_vmm_present patch (1)
- Remove kernel patch Reroute kern.hv_vmm_present patch (2)
- Remove kernel patch Reroute kern.hv_vmm_present patch (2) Ventura
EDIT: I'm aware that the third patch (Reroute kern.hv_vmm_present patch (2) Ventura) had a MinKernel = 22.0.0, so only the first two kernel patches are applicable to Monterey.
Thank you.
Last edited:
I've only discovered a little problem with my OCLP Monterey 12.6.1 install on my iMac12,2. Oddly, I have NO sound coming from the internal speakers. The only sound I get comes from external speakers/headset. Didn't OCLP 0.5.1 resolve this bug? I know of the Windows 10 UEFI sound being resolved but this is strange indeed. Anyone know of a fix to restore sound to the internal speakers?
Cheers
Cheers
Last edited:
I have an iMac 12.1 with M5100 GPU, presently in Monterey 12.6.1 using opencore 0.50.
Can I update OC to 0.52? Will I have any problems? Fyi I want to remain to Monterey, I will not update to Ventura.
Can I update OC to 0.52? Will I have any problems? Fyi I want to remain to Monterey, I will not update to Ventura.
I just finished a scratch (internet recovery install of High Sierra, then OC patched Monterey). The only glitch I had was that Bluetooth would not operate when I booted to the patched USB Drive ( I was successful using a USB Keyboard and mouse)
Upon installation Bluetooth returned. Hmmm
iMac mid2010 12.5 base model
Original GPU Original 500GB 7200RPM spinner, 16GB RAM
0.5.2 patcher level
Upon installation Bluetooth returned. Hmmm
iMac mid2010 12.5 base model
Original GPU Original 500GB 7200RPM spinner, 16GB RAM
0.5.2 patcher level
Hello, I have just ordered a BCM94360CD module with an adapter for my 2008 CMP 3.1 to finally recover bluetooth. A charitable soul who has already made this modification can tell me which are the correct locations for connecting the wires because this card contains the wifi and bluetooth module in a single card. Thanks
Does my post assist you at all?
Your adapter card may or may not have extra wires connected to it for bluetooth USB. You should not need them with the MacPro3,1 as it will connect to bluetooth USB through the mini-PCIe connector. You will want to remove the existing bluetooth module next to the wireless slot. I would connect the antenna wires before inserting the BCM94360CD into the adapter because the card will be flipped and the antenna connectors will not be accessible. The bluetooth antenna should go on J3.
Last edited:
Further to my unresolved audio problem problem with the OCLP (0.5.1) install of Monterey (12.6.1) on the iMac12,2 I thought I'd add this additional screenshot in the hope that someone may be able to help me debug this problem.
I'm not experienced in macOS and really confused why there is no audio with the internal speakers after a clean install of OCLP and Monterey. However, what I've discovered under System Preferences->Sound->Output is that the only device found is (Name) Digital Out -> (Type) Optical digital-out port. So this tells me the internal speakers have not been detected?
I'm not experienced in macOS and really confused why there is no audio with the internal speakers after a clean install of OCLP and Monterey. However, what I've discovered under System Preferences->Sound->Output is that the only device found is (Name) Digital Out -> (Type) Optical digital-out port. So this tells me the internal speakers have not been detected?
Last edited:
I had the same problem in my iMac 12.1 (Monterey 12.6.1). I reverted back to OCLP 0.50 and it was fixed.
I think OCLP 0.51 and/or 0.52 probably include an updated version of appleALC.kext that does not work correctly with our 2011 iMacs.
Last edited:
I noticed my audio bug as well, starting with the beta version of 0.5.2.
I would have internal speakers, but no audio jack for external speakers, it would have a 🚫 for up or down control. Leaving it plugged in, put mac to sleep, unplug, awake mac, it would start using internal again. Reversing the process leads to the same symbol.
Quitting coreaudiod in Activity Monitor didn't work to reboot the driver either. Only real fix i have found was reverting to 0.5.1.
I have read the docs about my mac being unsupported for the time being, HOWEVER, I'm still on Monterey, not Ventura, so this bug makes no sense to me as this is the only time it has happened through all of my use of OCLP.
Looking through the release notes, it appears the new version of AppleALC 1.7.6 could be the issue?
Last edited:
Hey! A have a problem with Safari on Monterey 12.6.1 (iMac27 mid2011). I updated Safari to ver. 16.1 (official release) and it stopped working properly - when trying to open any page using cookies, Safari starts to immediate reload (two times) and come up with "a problem repeatedly occurred"... I've tried lots of "100 percent working" fixies but nothing really worked. I figured out that it was connected with cookies - when I disable cookies pages are loading normally. But with denied cookies some of pages are not working - e.g. gmail login etc. Anybody who had same problem and fixed that? Thx
I was getting a headset icon instead of the speaker icon on the top menu bar and had no sound.
Reverting back to 0.50 fixed it. The new appleALC.kext should be the culprit.
Thanks to you both… I have to make the modification in a big week because there is no time. I will keep you informed of developments.
thanks again