Also tried OCLP in my Macbook Pro 17" 2011, both discrete and dedicate GPU working. Even native brightness control works! Not the keyboard backlight , though.
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 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
Discussed in the documentation:
TL;DR: Download LabTicks to restore partial functionality
That does not work at all and is the saem thing I tried multiple times before your comment. I was expecting more people to have the same problem but I cannot find anything about it online. It just always boots to that screen no matter what I do.
It's been a while since I visited this thread and I've left behind.
I want to update from 11.4 to 11.5.1 and I was thinking to use the latest version of OCLP to make sure that it will be fully compatible.
In the settings I can see that SIP is disabled by default for my iMac 12,1 but it was enabled before. Why is that? Should I leave it off?
What about the other options? Should I disable AMFI and SecureBootModel and keep everything else unchecked?
I want to update from 11.4 to 11.5.1 and I was thinking to use the latest version of OCLP to make sure that it will be fully compatible.
In the settings I can see that SIP is disabled by default for my iMac 12,1 but it was enabled before. Why is that? Should I leave it off?
What about the other options? Should I disable AMFI and SecureBootModel and keep everything else unchecked?
Attachments
This is a guess:
Possibly this is because your installation has been generated by migrating from micropatcher to OCLP and some residues are still visible (like an unsealed root system volume)? All the settings you posted were used with micropatcher, before.
Another explanation might be that the GUI in that stage simply checks for your system type and does no hardware detection. Since we have now TeraScale 2 (AMD HD6xxxM) support the settings are chosen to patch the root system volume.
To my knowledge you can enable SIP, AMFI, and SMB.
Monterey needs SBM disabled, though.
Check out the TUI - it is the version including the most recent software and the full and complete hardware detection (so your metal card will be recognized there).
Last edited:
Here is the fix I found that worked for me for my Canon LIDE210, perhaps useful for others who experience the same:
Last edited:
You are using OCLP? Upgrade as usual, (legacy) using software update or create a new USB with 11.5.1 on it and then migrate after installing the OS. See this guide, click "Getting Started": https://dortania.github.io/OpenCore-Legacy-Patcher/ Before you do anything, make sure you have a Time Machine backup!
Works for me and my Brother MCF-9120CN after installing the complete most recent driver package and opening the application "Brother Scanner" within the "/Library/Image Capture/Devices" folder pressing CRTL and/or right click as described above.
2012 MBA 13" 8GB. Shockingly how well Big Sur (11.5.1) + OCLP (v0.2.4) runs. Like Apple tested it and released it natively haha.
I do see CPU frequency error on About This Mac. Not that its a big deal, wondering if anyone else seen this. 12 MBA is 1.8GHz and no 2.3GHz model exist (see pic)
I do see CPU frequency error on About This Mac. Not that its a big deal, wondering if anyone else seen this. 12 MBA is 1.8GHz and no 2.3GHz model exist (see pic)
Download a full installer (link on post #1) create a new USB installer using the creatinstallmedia command (spoiler on post #1) and install the new Version using this USB installer. You can try installing version 11.5 and try an update to 11.5.1 later on using software update.
Root cause of your current problem is unknown to me. Did you do a clean installation or was it an update from micropatcher to OCLP?
Other solution:
Try updating the installed OCLP version to the most recent one and then use Apple software update to do the update.
Last edited:
probably got miss directed on the EFI bootloader. Took me awhile to understand this. Can be tricky for first timer.
bootloader is the thing that launches the OS in a partition. Normally you have 1 in your internal drive and its the thing that launches when you hold down the option key.
OCLP standard instruction suggest loading a 2nd bootloader called OpenCore onto the USB stick. OC is what launches the macOS installer (also on the USB, made when you executed the createinstallmedia command)
So if you just ran the internal drive's bootloader, you'll probably just end up in currently installed OS. I'm guessing this is what happened to you.
Need to hold down option key on restart after you make the OC and put it on the USB, run the EFI Boot icon with an external disk on it. Thats the OpenCore that got built and installed to the external USB. From there, boot the install macOS Big Sur.
When you are happy with the patched macOS, then you can installed the OC onto the internal drive and no longer need to have the USB stick with OC plugged in just to launch the patched macOS.
This 2 bootloader approach is probably safer but adds the number of things to juggle along with an extra layer of indirection. Hence the confusion and frequent novice installation failures.
Hope this helps.
Last edited:
Does it happen on supported system, too? More likely an Apple bug. OCLP does not change the macOS installed on disk.
Last edited:
Wish BS and the patch would enable bootable RAID0/RAID1 since most of us are on older machines..
I used to have RAID0 on Catalina, but its not possible on latest version, not to my knowledge anyways :/
Would love to see that 1Gbit/s read/write speeds again!
I used to have RAID0 on Catalina, but its not possible on latest version, not to my knowledge anyways :/
Would love to see that 1Gbit/s read/write speeds again!