-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
issues running turbomac on opencore-patched 2012 macbook pro #19
Comments
Try to :
I had similar issue installing with open core patched imac i think it is due to the afps snapshot being already mounted (busy) by the open core patcher last operation (i installed turbomac after the post install patch before rebooting and this probably created the problems) |
Have you tried putting the kext directly in the OpenCore EFI folder? |
OK.. So I know what your problem really is.. It has nothing to do with OpenCore at all whatsoever.. It is actually the problem from #18 Which is to say, the kext version in the release section so far only supports 6th-gen CPUs or higher (!) while your computer has a 3rd gen CPU. You would have to rebuild the kext from the above pull request so that it could work on your CPU. |
2012 13" macbook pro (9,2)
2.5 GHz Dual-Core Intel Core i5
Intel HD Graphics 4000 1536 MB
16 GB 1600 MHz DDR3
macOS ventura 13.6.1
battery completely removed
SIP and authenticated root both confirmed disabled via csrutil status, after granting execution privileges to the installer and then running it, it makes its way through the majority of the script and then at the end it returns:
however no prompt to approve an extension appears. when running "kextstat | grep TurboMac" the terminal returns
running "sudo powermetrics" returns
which shows that the cpu is still throttled to 1.2 ghz. any idea what's going wrong here? are there any special instructions for a system that's already been patched by opencore legacy patcher? this model macbook pro only natively supports up to catalina so ive used opencore legacy patcher to be able to run ventura. i know that this applies some patches to the GPU so im unsure if this somehow interferes with changes applied by TurboMac. if you need any more info from me please let me know
The text was updated successfully, but these errors were encountered: