macOS 11 Big Sur on Unsupported Macs Thread

[K two]

Big Sur 11.5.2 seems to break DRM playback with AppleTV, again. Although the the VDADecoderChecker reports Hardware acceleration is fully supported AppleTV gives me just a black screen using my AMD dGPU while streaming a free series pilot, sound is still fine.

On the other had this works pretty well on my iMac11,3 system still using 11.5.1 (similar hardware setup with Polaris AMD dGPU) and worked before the update on this particular iMac12,2.

EDIT and FIX:

UpdatingWhateverGreen to 1.5.2 and Lilu to 1.5.5 (both latest versions) on my stock OCLP 0.2.4 gives me back AppleTV streaming of pilots. You may also just use the latest nightly build of OCLP. I assume it contains the latest OpenCore release and kernel extensions, too.

The current 0.2.5 payload is listed, here: https://github.com/dortania/OpenCore-Legacy-Patcher/tree/main/payloads/Kexts/Acidanthera

 

[Caesar_091]

Hello,

is there an easy guide/tutorial to install BigSur on a 5,1 Mac Pro running MacOS Catalina via OC?

 

[Caesar_091]

Hello,

is there an easy guide/tutorial to install BigSur on a 5,1 Mac Pro running MacOS Catalina via OC?

...nevermind

 

[0134168]

Hello,

is there an easy guide/tutorial to install BigSur on a 5,1 Mac Pro running MacOS Catalina via OC?

I simply updated.

 

[Xavier]

I have an iMac 27" Late 2013 and I used OCLP 0.2.4 to updated to macOS 11.5.1. Everything works flawlessly except sometimes when the computer wakes from sleep, Finder will quit and not reopen. I have to restart for everything to go back to normal

Has anyone run into this issue?

 

[dghazfan]

I have an iMac 27" Late 2013 and I used OCLP 0.2.4 to updated to macOS 11.5.1. Everything works flawlessly except sometimes when the computer wakes from sleep, Finder will quit and not reopen. I have to restart for everything to go back to normal

Has anyone run into this issue?

Yes, I have
Mine especially problematic after using subler and/or if there is a heavy disk write activity into apfs-formatted hdd

 

[Macschrauber]

I maybe have a workaround for HID devices not being recognize:

MP3,1 OCLP 0.24 Big Sur 11.5.2

When I boot the system the wired Magic Trackpad 2 would not work, shows not in USB tree. I dont see a point using a trackpad with Bluetooth btw.

If I use it in OCLP boot picker it got recognized.

I bet there are other USB devices that could be initialized that way.

 

[Whynot2018]

hi Everyone

I installed 3 months ago OpenCore with a USB starter. Now I lost my USB starter drive. Is it possible to patch that version and start normally?

macOS 11 Big Sur on Unsupported Macs Thread

Great Work.I'm really impressed.It's not that slow.During Apple ID settings at the beginning was too slow but afterwards It was just like Sierra or little bit slower.

forums.macrumors.com

Thanks.

 

[rehkram]

I installed 3 months ago OpenCore with a USB starter. Now I lost my USB starter drive. Is it possible to patch that version and start normally?

Good question, I was wondering about that myself.

 

[jotzet]

I have an iMac 27" Late 2013 and I used OCLP 0.2.4 to updated to macOS 11.5.1. Everything works flawlessly except sometimes when the computer wakes from sleep, Finder will quit and not reopen. I have to restart for everything to go back to normal

Has anyone run into this issue?

Hello, are you using a FusionDrive Combo?
Thanks, Jo

 

[Brawdy14]

Hello, are you using a FusionDrive Combo?
Thanks, Jo

My suggestion is to update to Version 11.5.2 before investigating further!

 

[Lars B.]

I would still like to be able to use FileVault on non-Metal systems (and HD4000 systems with Monterey). I posted this analysis on the OpenCore bug tracker:

The first version of FileVault (Mac OS X 10.3 to 10.6) encrypted only your user data (home folder), not the system. An attacker with access to the hard drive contents would therefore not be able to read your data (it's encrypted), but would be able to modify the system. The attacker could, e.g., copy your data in encrypted form and modify the system in such a way that it would send your password to a remote server the next time you logged in. They could then use that password to decrypt their copy of your data.


On later versions of macOS (10.7 to 10.15), FileVault would therefore encrypt both, the system and the data. An attacker with access to the hard drive contents would then not be able to read the data or modify the system (because everything is encrypted).


Current versions of macOS (11 and 12) go back to the old model. Here, FileVault encrypts only the data (which is now on its own volume), the system itself stays unencrypted. However, nowadays the system volume is signed. An attacker with access to the hard drive contents would therefore still not be able to read the data (it's encrypted) or modify the system (because the modification would break the signature and be detected).


That's the reason why Apple does not allow enabling FileVault on machines where the system volume is not signed, e.g. because GPU acceleration patches have been applied. If you could enable FileVault without a signed system volume, the attack against the first version of FileVault described above would work again. The attacker could modify the system (because it's not encrypted) and because there's no signature, the modification would not be detected.


So there is no technical reason why FileVault would need a signed system volume to be able to encrypt your data, but instead, Apple does not want to lull you into a false sense of security.


However, the first version of FileVault (and the current version if it worked without a signed system volume) is not useless. They still protect your data perfectly against an attacker who simply steals your computer and does not give it back to you, which would be the vast majority of cases. Therefore, it would absolutely make sense to enable FileVault even without a signed system volume.


Because Apple has disabled FileVault on systems without signed system volumes, it would be necessary to patch FileVault and remove the check. When I find the time, I would like to try to find out what has to be changed, but I would be interested to hear what is already known about this. There seem to be at least two checks: You cannot disable the signed system volume as long as FileVault is enabled, and you cannot enable FileVault if you already disabled the signed system volume. What happens if you disable the signed system volume and then boot from another drive (with 10.15 if need be) and encrypt the data volume? Does macOS refuse to boot in that case (third check)?

khronokernel answered:

Unfortunately you cannot [disable the signed system volume] without disabling APFS snapshots and therefore the mechanism to update the OS through system preferences

I don't really understand. You have to disable the signed system volume anyway to apply the root patches for GPU acceleration (or HD4000 support on Monterey). My question is about FileVault.

 

[khronokernel]

I would still like to be able to use FileVault on non-Metal systems (and HD4000 systems with Monterey). I posted this analysis on the OpenCore bug tracker:



khronokernel answered:



I don't really understand. You have to disable the signed system volume anyway to apply the root patches for GPU acceleration (or HD4000 support on Monterey). My question is about FileVault.

The system volume is still sealed, but no longer has Apple's signature. Therefore you cannot enable FileVault on a no longer intact Apple signature. This is an OS limitation imposed by Apple, not an arbitrary one made by OCLP. Feel free to try and boot a root patched OCLP volume with FileVault in Big Sur or newer, there's a very high chance of instability, data corruption and loss of OTA.

 

[Lars B.]

Hi khronokernel, please don't view this as offensive, I really appreciate all your work and I can understand that you don't have a lot of time!

I think you are not reading my posts before you answer.

Me:

[Long explanation why Apple has chosen to disable FileVault on patched systems, followed by:]

Because Apple has disabled FileVault on systems without signed system volumes, it would be necessary to patch FileVault and remove the check. When I find the time, I would like to try to find out what has to be changed, but I would be interested to hear what is already known about this. There seem to be at least two checks: You cannot disable the signed system volume as long as FileVault is enabled, and you cannot enable FileVault if you already disabled the signed system volume. What happens if you disable the signed system volume and then boot from another drive (with 10.15 if need be) and encrypt the data volume? Does macOS refuse to boot in that case (third check)?

You:

This is an OS limitation imposed by Apple, not an arbitrary one made by OCLP.

That's what I had already written.

Feel free to try and boot a root patched OCLP volume with FileVault in Big Sur or newer, there's a very high chance of instability, data corruption and loss of OTA.

So have you (or someone you know) already tried it, and you got instability and data corruption?
Or have you not tried it yet, but you assume that the system will get unstable? If it's the latter, why do you think it might lead to data corruption? Apple did not disable FileVault because of technical problems, but because it's not really secure when the system volume can be modified (see above) and Apple does not want you to believe it's secure when it's not. That's why I don't really see an obvious reason why something should get unstable.

 

[Xavier]

Hello, are you using a FusionDrive Combo?
Thanks, Jo

No fuision drive, still an HDD.

 

[dfkinca]

Thanks for these wonderful tools to extend the lives of our Macs!

I just installed on a MacBookPro9,1. Have a dual boot configuration (Windows/Mac), not using Bootcamp (instead using the UEFI Windows guide).

Re: macOS 11.5.2, everything seems to be working as far as I have tested it (have not dug deep into DRM though).

Re: Windows 10, the sound is working natively on Windows (Yay!). And, most everything else seems to work as well. But, I cannot get the screen brightness keys (dimmer (F1) / brighter (F2)) to work; this despite having done suggested Windows driver upgrades (both BC, and SDIO).

Any thoughts/suggestions on how I might be able to get screen brightness keys working when booted in Windows?

Thanks in advance.

 

[Ulises Lopez]

Salut @quaccOS
Yes I created them,
I made them first with black SSD
View attachment 927926
but I prefer the news in gray...
View attachment 927927
I also made them with the old HDD icon
View attachment 927928
then with the new HDD icons from Big Sur
View attachment 927929

Indeed the personalized icons of the discs will not appear on the bootscreen

Where can i get your icon set, to use it on my Hackintosh?

 

[alphascorp]

Where can i get your icon set, to use it on my Hackintosh?

Hi @Ulises Lopez

Here is the link: https://drive.google.com/drive/folders/1XMj9hYOtARRvgF6AcROrdukQeUcG7zS3

 

[JedNZ]

Just to report that I was able to update from Big Sur 11.2.1 to 11.5.2 without incident today.

I was quite confused about what process I needed to follow because my setup is with the latest version of MyBootMgr (072a). I read through this forum as well as the Latebloom forum and was quite confused about whether I should use the OCLP or not, and whether I needed to remove my other boot drives to prevent drive corruption etc.

In the end I bit the bullet (I have multiple backup regimes in place). I booted into OC_ALT (VMM activated), unmounted all other drives, and then double clicked on the Install macOS Big Sur installer on the USB stick (plugged into in a port on the USB 3.0 PCIe card - great transfer speeds of up to 90MBps). It stalled halfway through on the progress bar after the first stage – but after 30 minutes of waiting I forced a shutdown, and on rebooting it continued on without incident (booted another 2 or 3 times altogether).

My system is as per my sig, and has the following bootable drives:
cMP 4,1>5,1 with Mojave (10.14.6 - NVMe PCIe), Catalina (10.15.7 - SSD in Upper OB), and Big Sur (now at 11.5.2 - SSD in SATA Bay 3).

I have to say I'm impressed that it worked and that I didn't have to jump through any more loops like having to play around with the Latebloom parameters (just the stock standard MyBootMgr settings - I assume Latebloom was activated automatically?) or any other boot-args or other workarounds that many have had to use.

I have booted only twice into Big Sur, both without incident. I'll do some more testing to see how things go.

 

[Sevenfeet]

I have 11.5.2 on all of my elderly Macs with OLCP 0.2.4 (iMac 8,1, two Mac 3,1s, MacBook 5,1) with the notable exception of my Mac Mini 4,1. This machine has never gotten through the install past 11.4 and I may return it to 11.4 pending some sort of a solution. I have not tried the 0.2.5 nightlies yet.

 

[mr__explorer]

Hi! I've just bought a 5,1 Mac Pro, 12-core, 32GB ram with a flashed GTX 680. I installed Big Sur via OpenCore and the DisplayPort does not work. Also HDMI only outputs 30Hz (at all resolutions) to my 4K60 display.

So far I have tried using the weg agdp boot-args and those didn't solve either issue.

I came across a solution here #685 and tried it, unsuccessfully, then realizing it was only a solution for Catalina.

Any ideas on what I can do to get DP working properly? I am very close to just wiping the system and using Mojave instead, but I don't want to give up that easily. I don't want to just have to do this all again when Mojave loses support. I'm also accustomed to BS on my laptop, and my memories of any quirks or issues Mojave might have for me are now 2 years old.

 

[Ganoninc]

Good afternoon OpenCore Legacy enthusiasts,

I've been running Big Sur 11.4 and 11.5.x on my MacBookPro10,2 for 3 months already.

I started this adventure with a clean install and I manually copied files from my time machine backup to my mac.

Most of the time, everything is perfect.

But, sometimes, usually after a sleep, like once or twice a week, it just crashes.

It's not a kernel panic, it's something weirder.

Usually, it happens when I try to open an app or switch to another one. If I do so at the right moment, I get a message like "this app cannot be open -10" or "this app has crashed". Then it's impossible to reopen that app and all other apps crash the same way once I put focus on them (somehow this doesn't affect PHPStorm / java).

If I'm in using Safari when the crash happens, Safari will just loop on saying the web page has crashed and try to reload it several times per second.

Oh by the way, the Finder also dies quickly.

So, when I'm running out of time and watch all the app crashing one by one, I just close what I can close and grab one of my open terminal and reboot using sudo reboot.

I've searched the web already and read some logs. I've seen answers pointing something like faulty RAM. However, I think this is not the issue because this Macbook worked great on Catalina.

Can someone help me?

I'm not afraid of going deep into MacOS if it can help, I'm a software developer and I've been using a Hackintosh (clover, then OpenCore) for several years.

Thanks!

 

[internetzel]

Good afternoon OpenCore Legacy enthusiasts,

I've been running Big Sur 11.4 and 11.5.x on my MacBookPro10,2 for 3 months already.

I started this adventure with a clean install and I manually copied files from my time machine backup to my mac.

Most of the time, everything is perfect.

But, sometimes, usually after a sleep, like once or twice a week, it just crashes.

It's not a kernel panic, it's something weirder.

Usually, it happens when I try to open an app or switch to another one. If I do so at the right moment, I get a message like "this app cannot be open -10" or "this app has crashed". Then it's impossible to reopen that app and all other apps crash the same way once I put focus on them (somehow this doesn't affect PHPStorm / java).

If I'm in using Safari when the crash happens, Safari will just loop on saying the web page has crashed and try to reload it several times per second.

Oh by the way, the Finder also dies quickly.

So, when I'm running out of time and watch all the app crashing one by one, I just close what I can close and grab one of my open terminal and reboot using sudo reboot.

I've searched the web already and read some logs. I've seen answers pointing something like faulty RAM. However, I think this is not the issue because this Macbook worked great on Catalina.

Can someone help me?

I'm not afraid of going deep into MacOS if it can help, I'm a software developer and I've been using a Hackintosh (clover, then OpenCore) for several years.

Thanks!

I have experienced the same several time and there have been other users reporting the same issue.
No one here seems to have analyzed the problem yet - I haven't done so because I'm still using Mojave and boot into Big Sur for testing purposes only.

 

[Ausdauersportler]

Good afternoon OpenCore Legacy enthusiasts,

I've been running Big Sur 11.4 and 11.5.x on my MacBookPro10,2 for 3 months already.

I started this adventure with a clean install and I manually copied files from my time machine backup to my mac.

Most of the time, everything is perfect.

But, sometimes, usually after a sleep, like once or twice a week, it just crashes.

It's not a kernel panic, it's something weirder.

Usually, it happens when I try to open an app or switch to another one. If I do so at the right moment, I get a message like "this app cannot be open -10" or "this app has crashed". Then it's impossible to reopen that app and all other apps crash the same way once I put focus on them (somehow this doesn't affect PHPStorm / java).

If I'm in using Safari when the crash happens, Safari will just loop on saying the web page has crashed and try to reload it several times per second.

Oh by the way, the Finder also dies quickly.

So, when I'm running out of time and watch all the app crashing one by one, I just close what I can close and grab one of my open terminal and reboot using sudo reboot.

I've searched the web already and read some logs. I've seen answers pointing something like faulty RAM. However, I think this is not the issue because this Macbook worked great on Catalina.

Can someone help me?

I'm not afraid of going deep into MacOS if it can help, I'm a software developer and I've been using a Hackintosh (clover, then OpenCore) for several years.

Thanks!

The first version which gave me this annoying error is Big Sur 11.5.2 on two systems (not patched with some legacy patches). So both iMacs have an unaltered stock Apple macOS Big Sur installation like a fully supported systems, but we inject a lot of kernel extensions to get Ethernet, WiFi, etc working.

Nevertheless I had it on both systems shortly after upgrading from 11.4 to 11.5.2 via OTA.

System one:
So far I tried to reinstall the latest Big Sur from the recovery partition. Everything went well, uptime approx. 48h.
After modifying the OpenCore config.plist and another reboot the same problems came back, a new reboot and a NVRAM reset gave me a new stable system. Everything is quite fresh and the latest reboot happened 21h ago.

System two:
48h uptime and no problems, than I had to reboot to install Monterey B6 and test some OpenCore changes. No problems so far.

When it happens it is even impossible to create screenshots with the error messages. Finder dies quickly and the best strategy is a quick reboot. Happened four times now, three times on system one in the last two weeks and one time on system two.

 

[Bmju]

Good afternoon OpenCore Legacy enthusiasts,

I've been running Big Sur 11.4 and 11.5.x on my MacBookPro10,2 for 3 months already.

I started this adventure with a clean install and I manually copied files from my time machine backup to my mac.

Most of the time, everything is perfect.

But, sometimes, usually after a sleep, like once or twice a week, it just crashes.

It's not a kernel panic, it's something weirder.

Usually, it happens when I try to open an app or switch to another one. If I do so at the right moment, I get a message like "this app cannot be open -10" or "this app has crashed". Then it's impossible to reopen that app and all other apps crash the same way once I put focus on them (somehow this doesn't affect PHPStorm / java).

If I'm in using Safari when the crash happens, Safari will just loop on saying the web page has crashed and try to reload it several times per second.

Oh by the way, the Finder also dies quickly.

So, when I'm running out of time and watch all the app crashing one by one, I just close what I can close and grab one of my open terminal and reboot using sudo reboot.

I've searched the web already and read some logs. I've seen answers pointing something like faulty RAM. However, I think this is not the issue because this Macbook worked great on Catalina.

Can someone help me?

I'm not afraid of going deep into MacOS if it can help, I'm a software developer and I've been using a Hackintosh (clover, then OpenCore) for several years.

Thanks!

Do you use OpenCore Legacy Patcher or just OpenCore with own config? You have a very compatible Mac, if you upgrade the internal WiFi card it can run Big Sur 100% unpatched and you just have to use OC to fake the model, to get upgrades. Which is what I'm using, on a retina MBP10,2 and have not seen any crashes. So just wondering if the problems may be caused by a patch or setting somewhere which - at least on your machine - you may not actually need.