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
You can stay with OCLP 0.3.1, it works well for installing and booting 11.6.2.
It is good to stay with 0.3.1:
- a release rather than nightly
- 0.3.2 nightlies at present may not show future OS updates.
0.3.2 does have an advantage for non-metal machines, in that graphics shows no blurs anymore. Still good to wait until the 0.3.2 release is out.
Hello,
I have recently installed macOS Big Sur 11.6 (from Catalina) on my MacMini 2012 6,2 using OpenCore Legacy Patcher and everything went well during the installation, but now i cannot use my mac.
After login to my account, i can use applications during about 1 minute, then everything crash and i can no more launch apps.
In OpenCore settings for installation, SIP is set as disabled, but when i check SIP status after installation, it's in Unknow status, even if i change it to disabled (after reboot)
In Console, i see a lot of messages like this when apps crash :
Help is welcome
I have recently installed macOS Big Sur 11.6 (from Catalina) on my MacMini 2012 6,2 using OpenCore Legacy Patcher and everything went well during the installation, but now i cannot use my mac.
After login to my account, i can use applications during about 1 minute, then everything crash and i can no more launch apps.
In OpenCore settings for installation, SIP is set as disabled, but when i check SIP status after installation, it's in Unknow status, even if i change it to disabled (after reboot)
In Console, i see a lot of messages like this when apps crash :
Help is welcome
You cannot change the SIP status with OpenCore other than editing the config.plist or rebuilding and rewriting OpenCore through OCLP. Check the docs and even GibHub issues about this ongoing discussion. SIP is controlled by OpenCore only as long as you boot and use it.Hello,
I have recently installed macOS Big Sur 11.6 (from Catalina) on my MacMini 2012 6,2 using OpenCore Legacy Patcher and everything went well during the installation, but now i cannot use my mac.
After login to my account, i can use applications during about 1 minute, then everything crash and i can no more launch apps.
In OpenCore settings for installation, SIP is set as disabled, but when i check SIP status after installation, it's in Unknow status, even if i change it to disabled (after reboot)
In Console, i see a lot of messages like this when apps crash :
Help is welcome
There is a known problem with fast crashing apps mostly coming with the famous "Hash mismatch" error message.
What i don't understand is that SIP is disabled in OpenCore settings when i install it
Again, read the docs. It is clearly stated your system would need root volume patching and SIP disabled with Monterey. Since the software cannot feel, smell or hear what macOS you are planning to install it goes the way of the least resistance.
Since you and only you can know what is to be installed next you and only you can choose SIP enabled when running OCLP.
This is a complex topic, but you are entering the world of unsupported macs. There is only one person left who will support your system now - this is you! Get prepared for this job!
@enka95 I appreciate @Ausdauersportler is already aware of this, of course, but without wanting to over-complicate the issue, it is possible to set up OpenCore so that it does not control SIP, i.e. so that it would be controlled normally in Recovery as you expect. Do do this, you need to understand how to edit the config.plist file NVRAM section correctly... This would not be the right thing to do if you are installing Monterey and using OCLP, but it might be a sensible change to make if you are sticking with Big Sur.
Yes, this is another option. Thanks for pointing this out, again.
Right now I try to find the balance between the (OLCP) one size fits all (every machine and every macOS version) approach and the complete freedom to edit the config.plist yourself. The two main developers used the idea if having a hardware detection built in and making choices for the config depending on the results. Later we got Monterey and now we have two possible macOS versions to maintain with different (necessary) settings and this causes confusion within the user base.
Using the TUI version one has the control to disable SIP before building OpenCore and installing it. I guess we need a better documentation (in case someone wants to read it) to reflect these different options when sticking with Big Sur.
BTW: I wrote before OCLP 0.2.4 was the last pure Big Sur release and it would offer the correct settings.
Last edited:
Suggestions from someone also running Big Sur on 2012 mini with OCLP 0.2.5:
- Start all over, possibility that old kexts in Catalina messing up
- Use OCLP 0.2.4 or 0.2.5 TUI
- Assuming you will not be going to Monterey anytime soon, check patcher settings to turn on SIP and Secure Boot (you only need to turn off SIP for Monterey because of post install patch of HD4000 graphics)
- Clean install 11.6, ie. delete disk before install
I'm not the person you've addressed, but with a little help of Google's image search: Hope this helps.
Last edited:
On Big Sur AFAIK not without enrolling the Mac to an MDM. The softwareupdate --ignore "macOS Monterey" switch was reinstated in Catalina, but remains unavailable in Big Sur.
Hi, so I did it. Using OCLP 025 I installed BS 11.6.1 on my MacBook Pro 2009, after installing PostInstallPatches everything moved smooth, but I found 4 issues: 1. Display and sound strips looks ugly in Control Center. 2. No icons in e.g. Accessibility contol panel 3. No NightShift tab in Display Control Panel 4. No visible possibility of update to 11.6.2 in Update control Panel. Do you have the same issues in your MacBook Pro? Firts I installed PostInstallPatches from OCLP 025, having above mentioned issues I installed Patches from 032 night build but nothing changed... BR.
Attachments
I have the same three issues 1,2,3 as you mentioned. Used the latest OCLP 0.3.2 nightly for post install patches. - There is not identical, but similar behaviour in Monterey (but night shift is there); in both cases using the same non-metal acceleration code, i.e. the latest SkyLight framework.
I did see the 11.6.2 in the update control panel when booting with OCLP 0.3.1, but not with 0.3.2 nightlies, and used it to update 11.6.1 to 11.6.2 meanwhile (didn't try 0.2.5). There might also have been a transition effect between multiple release candidates of 11.6.2, all called 11.6.2 but with different version codes (20G311 being the latest). There should be a release of 11.6.2 before long I guess, hopefully coming with a full InstallAssistant.pkg.
Last edited:
Affirmative for issues 1, 2 and 3 (MacBookPro5,2 17" Mid 2009, 3.06 GHz Penryn T9900). Interestingly, the very same "Spoken Content" icon is correctly displayed in the Accessibility Features on my machine while all others are not.
Hi, thank you for your quick reply. now I know that I am not alone with these issues
So I am wating for 11.6.2 a full InstallAssistant.pkg. Have a nice weekend. BTW BS 11.6.1 does really his job in MacBook Pro Mid 2009. Thanks once again for an inspiration to do that.
Last edited:
Hello I am wondering what you are saying about the blur fix ? is it he graphics glitch we get in dark mode mostly ?
and if yes were can I find it please ?
Re: DRM on Big Sur - most encoders stripped. Issue viewing TV channels (in this case all Swiss TV) that is using DRM on its live TV
Hi all,
Need help: since upgrading to BS (and using now 11.6.2 (20G311) with OLCP .32 with blur fix) from Catalina 15.7, I can no longer view live Swiss TV channels. I can however view other "non live" proposed Swiss programming (replays, etc.) I can also view other live TV channels in other countries as well, just not DRM-based live TV. Have tried proposed browser extensions, specific DNS setting and all with no result. I am using BS on a MBP 8,2 (2011) with dGPU disabled. Could that be the issue since I found info on Whatevergreen (https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Chart.md) stating the following:
Hi all,
Need help: since upgrading to BS (and using now 11.6.2 (20G311) with OLCP .32 with blur fix) from Catalina 15.7, I can no longer view live Swiss TV channels. I can however view other "non live" proposed Swiss programming (replays, etc.) I can also view other live TV channels in other countries as well, just not DRM-based live TV. Have tried proposed browser extensions, specific DNS setting and all with no result. I am using BS on a MBP 8,2 (2011) with dGPU disabled. Could that be the issue since I found info on Whatevergreen (https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Chart.md) stating the following:
DRM Compatibility on macOS 11+
Things to keep in mind:- All kinds of software DRM decoders were removed from macOS 11
- All kinds of legacy hardware DRM decoders (e.g. NVIDIA VP3) were removed from macOS 11
- WhateverGreen Shiki functionality is not planned for inclusion for macOS 11
- Only IGPU-free Mac models allow for full DRM content access given a compatible AMD GPU video decoder
- For old CPUs (e.g. Xeons or Quad 2 Quad) and supported AMD GPUs injecting unfairgva with <01 00 00 00> value is required for streaming DRM
- AMD GPU video decoder preference can be chosen through preferences overrides for some types of DRM content (like Apple TV and iTunes movie streaming). This preference may not always be compatible with the rest of the operating system and may cause problems with other ways of hardware media decoding and encoding. For this reason such an override is not recommended for daily use and shall only be enabled on demand.
- defaults write com.apple.AppleGVA gvaForceAMDKE -boolean yes forces AMD DRM decoder for streaming services (like Apple TV and iTunes movie streaming)
- defaults write com.apple.AppleGVA gvaForceAMDAVCDecode -boolean yes forces AMD AVC accelerated decoder
- defaults write com.apple.AppleGVA gvaForceAMDAVCEncode -boolean yes forces AMD AVC accelerated encoder
- defaults write com.apple.AppleGVA gvaForceAMDHEVCDecode -boolean yes forces AMD HEVC accelerated decoder
- defaults write com.apple.AppleGVA disableGVAEncryption -string YES forces AMD HEVC accelerated decoder
- defaults write com.apple.coremedia hardwareVideoDecoder -string force forces hardware accelerated video decoder (for any resolution)
- defaults write com.apple.coremedia hardwareVideoDecoder -string disable disables hardware accelerated video decoder (in QuickTime / Apple TV)
(As far as I know) This is a well known feature of macOS Big Sur. DRM needs a metal iGPU (HD4000 and better) or a recent AMD dGPU like the RX560 or better (PCI or MXM).
You may try another browser, but Apple TV will not work any longer. Sorry, some features are linked to hardware and cannot be patched.
Big Sur even broke AirPlay on systems using a modern AMD GPU.
Thanks Ausdauersportler. Though I liked Big Sur too many little hassles on my 8,2 that made it less productive with respect to Catalina. Will now have to reinstall Catalina with reformatted drive with Dosdude's patcher and reinstall applications and a data restore. Will never be thankful enough to all that I am able to go this far on an 11+ year MBP!
My MBP4,1 17-inch (Early 2008, specs in signature) is running superbly on Catalina, thanks to dosdude1's excellent patcher.
I successfully installed Big Sur via OCLP and the instructions from the guide on Dortania.
With only 4GB of RAM at the time it was a drag, though. Graphics lagging behind tremendously, so I decided to roll back to Catalina, now at v.10.15.7 (19H1612).
I now bumped the RAM to 6GB and am eager to shoot for Big Sur again.
Can anyone on this forum report on a successful installation of Big Sur on the MBP4,1 and report on overall performance, flaws, etc.? If successful, the fellow boardmember is kindly asked to provide a how-to upgrade from Catalina, which would be highly appreciated.
Thank you very much in advance
I successfully installed Big Sur via OCLP and the instructions from the guide on Dortania.
With only 4GB of RAM at the time it was a drag, though. Graphics lagging behind tremendously, so I decided to roll back to Catalina, now at v.10.15.7 (19H1612).
I now bumped the RAM to 6GB and am eager to shoot for Big Sur again.
Can anyone on this forum report on a successful installation of Big Sur on the MBP4,1 and report on overall performance, flaws, etc.? If successful, the fellow boardmember is kindly asked to provide a how-to upgrade from Catalina, which would be highly appreciated.
Thank you very much in advance
Last edited:
Just upgraded my Catalina 10.15.7 to 11.6.1, and am very very happy. Running solid on my 5,1.
very happy with the UI improvements, and the system seems to be much more stable than Catalina was (if that's possible).
Hope Monterey gets to be like this.
very happy with the UI improvements, and the system seems to be much more stable than Catalina was (if that's possible).
Hope Monterey gets to be like this.
About to take the plunge of upgrading and moving my operation from Mojave to the more modern world of Big Sur on my production cMP (office, design, small amounts of audio/video editing, app dev etc). Big Sur is running beautifully as a testbed with minimal apps. I just want to know if there are any strong reasons why I should not upgrade, and if my method below looks good. I'm aware of no support for 32-bit software, and I'm fairly much sure all are 64-bit on Mojave, so don't expect software will be an issue.
My plan of attack is as follows (using my primary cMP as per my sig):
1. I have two full backups of my Mojave NVMe boot drive (both on SSDs) using CCC, plus a Time Machine backup.
2. I'll boot my testbed Big Sur SSD (SATA II bay), reformat my Mojave NVMe and clean install Big Sur onto it.
3. Next, I'll use Migration Assistant to suck my apps from my Mojave backup onto my new Big Sur NVMe.
4. I'll then add my User accounts (in place) on my homebuilt Fusion Drive. Big Sur NVMe will only have two Admin accounts - Users accounts will remain on the FD.
5. I'll then backup my new Big Sur NVMe with my Time Machine (no going back?), and use one of the backup Mojave SSDs to backup my new Big Sur NVMe using CCC.
Anyone see any issues with this?
Update: I went ahead and installed Big Sur using the method above. I use MyBootMgr and booted into OC_ALT before running the Big Sur installer.
After setting up a new Admin account, I ran Migration Assistant and wow - what a breeze, and fast. Of course it was, due to the Mojave drive being on a SATA III PCIe adapter (~550MB/ps) and my NVMe drive bring on a PCI 3.0 switch Ableconn dual M.2 adapter).
It also located User accounts on my Fusion Drive, also noting that the data was remote. I wasn’t sure what that was going to mean (eg just ignore, try to copy the User data off the FD etc), but upon selecting all my FD User accounts, and after a faultless couple of reboots, voila - it added my User accounts (referenced to my FD) without any strange consequences.
All in all, the easiest and fastest clean install > Migration Assistant upgrade ever.
My plan of attack is as follows (using my primary cMP as per my sig):
1. I have two full backups of my Mojave NVMe boot drive (both on SSDs) using CCC, plus a Time Machine backup.
2. I'll boot my testbed Big Sur SSD (SATA II bay), reformat my Mojave NVMe and clean install Big Sur onto it.
3. Next, I'll use Migration Assistant to suck my apps from my Mojave backup onto my new Big Sur NVMe.
4. I'll then add my User accounts (in place) on my homebuilt Fusion Drive. Big Sur NVMe will only have two Admin accounts - Users accounts will remain on the FD.
5. I'll then backup my new Big Sur NVMe with my Time Machine (no going back?), and use one of the backup Mojave SSDs to backup my new Big Sur NVMe using CCC.
Anyone see any issues with this?
Update: I went ahead and installed Big Sur using the method above. I use MyBootMgr and booted into OC_ALT before running the Big Sur installer.
After setting up a new Admin account, I ran Migration Assistant and wow - what a breeze, and fast. Of course it was, due to the Mojave drive being on a SATA III PCIe adapter (~550MB/ps) and my NVMe drive bring on a PCI 3.0 switch Ableconn dual M.2 adapter).
It also located User accounts on my Fusion Drive, also noting that the data was remote. I wasn’t sure what that was going to mean (eg just ignore, try to copy the User data off the FD etc), but upon selecting all my FD User accounts, and after a faultless couple of reboots, voila - it added my User accounts (referenced to my FD) without any strange consequences.
All in all, the easiest and fastest clean install > Migration Assistant upgrade ever.
Last edited: