webg3
macrumors 6502a
Do not do this. Big Sur does not have acceleration on old-macs to depend on api metal (GPU); The minimum is a GPU with Metal 1
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
Ausdauersportler
macrumors 603
You missed the famous @ASentientBot added back graphics acceleration support for a list of pre metal systems and there is a public beta phase using OCLP. Just changed the first post to reflect this recent changes...
Of course this does not bring metal support to non metal GPU systems. So some apps may not work or only within some limits as before.
webg3
macrumors 6502a
True, I missed that point. But going back a few pages, I noticed that it is still being tested, so I don't recommend it for daily use. I have a MacBook Pro 2010 13 "NVIDIA GeForce 320m too. however since we achieved acceleration in macOS Catalina, still, the best system for these older ones is macOS Mojave, due to a number of factors.
Not that it can't be tested, that's for sure, but for daily use I don't recommend it.
Thanks for the info, I really want to install it for testing only.
Just updated my MBP 2012 15" to 11.3 with Ben's Patched Sur v0.2.1. Came from manually installing micropatcher and gave Patched Sur a try. No more USB Stick creation, very easy updating. Everything works as expected. Thank you for that!
Hello everyone,
today I installed macOS 11.3 from full USB stick installer on my iMac11,2 21.5" Mid-2010 with i7-860S, flashed K1100M and upgraded BCM94360CD (see photo attached), using OCLP 0.1.1 on internal SSD EFI.
Everything works perfectly fine, except for one thing: brightness control. No way to get it working.
In "Patcher Settings" I disabled point 12 "Set Acceleration Patches" and even set point 4 "force iMac Metal Patch" to "NVIDIA GPU", as I have a K1110M.
When I build OpenCore it detects my card and says that it installed the relative patches, but when I reboot (with or without SMC/PRAM resets), I always have brightness at full tilt.
Previously I had macOS 11.2.3 installed with OCLP 0.0.22 over a pre-existent 11.2.3 partition installed with barrykin's big-sur-micropatcher.
Everything there worked absolutely fine AND I had brightness control perfectly working too.
I've tried 0.0.23, 0.1.0 and 0.1.1, none of them gave me brightness control so I reverted back to 0.0.22 and now everything works fine, even in macOS 11.3.
I assume for some reason OCLP after 0.0.22 doesn't create config.plist correctly for my machine for some reason, or I'm doing something wrong.
I've got no problem staying on 0.0.22, but I reported my case hoping it can be helpful for future developments 🙂
You all are doing an amazing job with this patcher, thanks a lot for your immense efforts to keep old machines like mine in touch with 2021 ^^
today I installed macOS 11.3 from full USB stick installer on my iMac11,2 21.5" Mid-2010 with i7-860S, flashed K1100M and upgraded BCM94360CD (see photo attached), using OCLP 0.1.1 on internal SSD EFI.
Everything works perfectly fine, except for one thing: brightness control. No way to get it working.
In "Patcher Settings" I disabled point 12 "Set Acceleration Patches" and even set point 4 "force iMac Metal Patch" to "NVIDIA GPU", as I have a K1110M.
When I build OpenCore it detects my card and says that it installed the relative patches, but when I reboot (with or without SMC/PRAM resets), I always have brightness at full tilt.
Previously I had macOS 11.2.3 installed with OCLP 0.0.22 over a pre-existent 11.2.3 partition installed with barrykin's big-sur-micropatcher.
Everything there worked absolutely fine AND I had brightness control perfectly working too.
I've tried 0.0.23, 0.1.0 and 0.1.1, none of them gave me brightness control so I reverted back to 0.0.22 and now everything works fine, even in macOS 11.3.
I assume for some reason OCLP after 0.0.22 doesn't create config.plist correctly for my machine for some reason, or I'm doing something wrong.
I've got no problem staying on 0.0.22, but I reported my case hoping it can be helpful for future developments 🙂
You all are doing an amazing job with this patcher, thanks a lot for your immense efforts to keep old machines like mine in touch with 2021 ^^
Attachments
khronokernel
macrumors 6502
Hi, could you open an issue on Github regarding this? Forums are an absolute pain to keep track of issues from our end, so having a consolidated area is much appreciated. When you open the issue on Github, please upload an IOReg of your machine (file -> SaveAs):
Thanks in advance,
- Mykola
OpenCore-Patcher is awesome, just updated my late 2012 iMac to macOS 11.3 while having Filevault turned on, so dar I always had to make a reinstall and did a Time Machine backup before, so nice being able to just update 😀
One question, macOS now always asks me to update to 11.4 Beta 1 which I don't want to do and I didn't use Beta versions before. I tried to leave the Beta program in the update dialogue under settings but that didn't help. How can I make sure the OS only looks for updates of the stable version?
One question, macOS now always asks me to update to 11.4 Beta 1 which I don't want to do and I didn't use Beta versions before. I tried to leave the Beta program in the update dialogue under settings but that didn't help. How can I make sure the OS only looks for updates of the stable version?
amaze1499
macrumors 68000
Mac_tech
macrumors 6502
Done, same issue. timestamp was 10:39 - 10:40am. Looks like a lot happened in the background and hope it's not too much information. I copied the log from that minute but let me know if you need something specific. Hope this helps.
AlexSakha67
macrumors member
Hello, it's very nice, thanks to your knowledge, I almost fully use the old unsupported computer technology apple. I updated the installed MacBook and MacPro system on top. Everything is ingenious, aerobatics is like a new real computer technology apple. Super Opencore Legacy Patcher👍💫🏆
Thanks to khronokernel, SentientBot, dosdude1, Ausdauersportler and the developers🙌😊
Thanks to khronokernel, SentientBot, dosdude1, Ausdauersportler and the developers🙌😊
Attachments
hvds
macrumors 6502a
It is wonderful to have OpenGL back. I'm very grateful to ASentientBot and the OCLP team for providing it!Hello everyone! So with 11.3's official release today, we're proud to announce that we've released OpenCore Legacy Patcher v0.1.1! And with it, beta support for GPU Acceleration Patches!
Release 0.1.1 · dortania/OpenCore-Legacy-Patcher
Fix iMac11,3 GFX0 pathing Add MouSSE support to iMac10,1 with Metal AMD GPU Fix iMac11,1 and iMac11,3 Nvidia boot issues after PRAM reset Fix DRM support on Nvidia-only configurations Support opti...github.com
Overall we're insanely impressed with the progress made regarding acceleration support and have to give a huge round of applause to our very own @ASentientBot. While not perfect, these acceleration patches are very much usable and even daily drivable for those willing to tolerate the odd visual glitches here and there. And building off the foundation ASentientBot had laid with their Nvidia Acceleration Patches, we were able to get AMD's TeraScale 1 series, Intel's IronLake and Sandy Bridge series all working fantastically! However please keep expectations low, as these patches are still in beta and are under heavy development.
For the first 2 notes, I've uploaded an 11.2.3 Installer on Archive.org for users to easily download when Apple removes the app from their servers:
- Note 1: with macOS 11.3 Beta 2 and newer, there is heavy display artifacting on AMD GPUs during sleep wake, display resolution changing and connecting external displays. We highly advise users to stay on 11.2.3 or older until we've resolved the issue.
- Nvidia and Intel GPUs are not affected
- Note 2: Mac Pro users with NVMe drives should be wary of installing 11.3 as well due to the device being present resulting in boot issues
- Note 3: For current known issues with acceleration patches, check out the associated Github issue
And our final announcement for today is that we've started our very own discord server, OpenCore Patcher Paradise! The goal of this server is to help consolidate information, testing, issues and such into one server. With the influx of users trying the acceleration patches, we highly recommend popping in our server if you have any concerns or want to share success posts.
Server Link: OpenCore Patcher Paradise Discord Server
Just did a clean install of 11.3 on an external SSD using OCLP 0.1.1, on my MBP5,2.
- needed a manual reboot once at start of stage2, then it proceeded right to the setup screens
- setup executes a bit slow as graphics acceleration comes in later - but works
- used migration from Catalina 10.15.7 (on the internal SSD). (A posteriori migration to my previous installation of BS didn't work, hence I reinstalled, and also to go from 11.4beta to released 11.3)
- then applied the Post Install Volume Patch of OCLP 0.1.1, reboot and boom - acceleration!
- update to 11.4beta is still offered despite patched system volume, as khronokernel has indicated earlier (but I cancelled the download).
One more small remark: don't select "reduce transparency" as otherwise the left part of the menu bar isn't updated correctly. Plus small other graphics glitches which don't hurt.
That all looks so good that I'll soon swap this BigSur SSD with the Catalina SSD and use it on SATA for more testing.
Attachments
Last edited:
pietruszkim
macrumors newbie
Thank you for patient answers 🙂 I read the docs but some things were for me not clear...
1. So OCLP makes only changes on pendrive or on disk containing OCLP, no changes in NVRAM?
2. I read on OCLP website: Hibernation Support-Patched Sur-Only supports stock drives! My is 3rd party-Samsung.
3. Now clear.
4. Now clear.
Ausdauersportler
macrumors 603
1. I did not wrote that! (You were asking and) I was writing about the firmware, not NVRAM. Use the big search machine to get definitions of both.
2. This is not the OCLP website you found and linked there - it is Patched Sur, please do not confuse this. If you need to know something about Patched Sur ask the author on his discord server channel - link on the site you already found.
Last edited:
Thank you for developers
Test BigSur11.3 with error more details
frame buffer lagging and USBmouse
Test BigSur11.3 with error more details
frame buffer lagging and USBmouse
Last edited:
Fernando Nakashoji
macrumors newbie
I switched from Barry K.'s excellent micropatcher to OCLP on my Macmini. After a few reboots, Big Sur 11.3 seems to be even smoother than 11.2.3. Congratulations to everyone involved in the development!
However, as I need to use windows applications at work, can anyone help with a detailed roadmap on how to set up a new bootcamp with OCLP?
However, as I need to use windows applications at work, can anyone help with a detailed roadmap on how to set up a new bootcamp with OCLP?
Fernando Nakashoji
macrumors newbie
Well, according to the discussion on discord, the bootcamp works normally ... I'll try ...
contacos
macrumors 604
Used PatchedSur again to install 11.3 and worked like a charm (laptop specs in my signature). I am too dumb for the other methods, this one offers a nice UI for dummies like me
Ausdauersportler
macrumors 603
Fine that you got there! But you need no new and additional GUI and new process to replace the standard apple software update.
The only thing I do (right now) and did in the last 4 month with OpenCore and OCLP is this:
A few (automatic) reboots later I am on the next (most recent version). What can be more easy?
Ausdauersportler
macrumors 603
We have three or four threads here on the forum just about OpenCore on the Mac Pro series to get Apple Software Update and other things working, again. OCLP is the latest kid on that party.
It would be really a complete nuisance to start with an old fashioned patcher tool using your system.
The current problems with version 11.3 and NVME connected drives on Mac Pro system will not just go away when using a different patcher.
So, I have a late 2012 13" rMBP, with micropatched 11.2 installed. I tried downloading 11.2 from apple and reinstall the OS with OCLP as suggested from github page(?) but realized Apple had taken 11.2 down. So I downloaded 11.3 and went with OCLP installation to see how it goes. Everything went fine but it just couldn't boot from my internal drive even after installing the OC to my internal drive, I have to plug in the USB installer and select my internal drive. I have file vault and SIP turned off. So my question is that what else can I do apart from a clean OS install then a time machine restore? Thank you very much.
Ausdauersportler
macrumors 603
The 2012 MBP is fully supported by OCLP.
I think it is worthwhile switching over to OCLP because of simplicity of OTA afterwards. You might think OCLP is complicated but it is straight forward in operations especially for models fully supported.
When I switched to OCLP, it was not that hard:
- get OCLP app, install app
- create USB installer for your current version ie 11.3
Create a bootable installer for macOS – Apple Support (AU)
You can use a USB flash drive or other secondary volume as a startup disk from which to install the Mac operating system. These steps are primarily for system administrators and other experienced users.
- run OCLP app
- build patch (default settings), install patch to USB stick earlier with installer 11.3
- reboot with option key on start up, select OCLP EFI Boot
- Use 11.3 installer, install over your internal disk, preserving your data
That's it.
If you want to remove USB from boot up process, just run OCLP again, install patch to internal disk, reboot with option key and select internal EFI.