macOS 11 Big Sur on Unsupported Macs Thread

[hvds]

MacBook Pro 5,2 (17-inch, Mid 2009)
3.06 GHz Intel Core 2 Duo
8 GB 1067 MHz DDR3
NVIDIA GeForce 9600M GT 512 MB
Samsung SSD EVO 860 1 TB — two partitions: 1st has Catalina and Mojave OSs installed, 2nd has Big Sur.

Installation of Big Sur 11.3 Beta 6 via OCLP 0.0.21

I erased partition containing Big Sur beta6, previously installed via jackluke’s BigSurFixes method (it was fully functional)

Followed “how to” instructions on Dortina forums.
Big Sur Beta 6 installed in manner described by other posters, including the “1 minute left” notice, which actually took about 10 min to finish.

I was able to boot into the installation, though the process of setting up an account was painfully slow; a swipe gesture on track-pad would take 10 or more seconds to move the cursor or highlight a button.

Nonetheless, I was able to create an account and boot onto the desktop.

Following items were nonfunctional: sound (internal speakers), internal microphone, iSight camera, display-resolution choices.
However, Wifi was active, and 11.3.beta7 was listed as an available download in the Software Update Panel.

After disabling finder animation system was usable, if (subjectively) much slower than installation via jackluke’s method.

I tried to initiate a frame-buffer fix using jacklukes’s fixes, but it rendered the system un-bootable; this was not a great surprise, however, not being able to boot Catalina or Mojave (located on separate partition) was disconcerting. It was not possible to boot into Big Sur, Catalina or Mojave.

To restore boot capability I had to boot from the USB Catalina flash drive, erase BigSur Partition (using Disk Utility), reinstall Catalina 10.15.7 (no data overwrite), boot into the latter, then use disk utility to merge (now) empty BigSur partition with one hosting Catalina and Mojave.

Once above was accomplished I was able to boot Catalina and Mojave. Subsequently, I initiated a new Big Sur Partition using disk utility, and was able to successfully install 11.3.beta7 via jackluke’s Big Sur Fixes method. One fallout from this process was a loss of separate containers for Catalina and Mojave; both OSes are now in one container.

Not sure of precise steps to regain sound, microphone or camera functions once Big Sur is installed via OCLP. Based on information in this thread, perhaps BarryN’s micropatcher ’s patch-kexts.sh script, might have been more successful in supplementing OCLP install(?)

Hope this post may be of help.

Thank you to all developers and posters for making this project such a successful endeavor.

I had similar observations on my MBP5,2.

Internal audio will work when booting via OCLP 0.0.22 (no new installation needed, if I remember correctly).

Slow reaction speed, esp. during setup: jackluke's method installs ASentientBot's framebuffer patch which helps a lot, esp. for quick mouse movement; while OCLP doesn't yet I think (maybe with the next 0.0.23).

I'm presently using an OCLP 0.0.22 installation with 11.3b8, and a BigSurBaseSystemfix installation with 11.2.3, and I think I'll continue this for future versions.

 

[Larsvonhier]

Acceleration patches are not public, and likely won't be for another few months. We highly recommend users with non-Metal GPUs to run older OSes such as Catalina or Mojave

Even once acceleration patches do release to the public, we do want to ensure everyone's expectations are low. It will be worse than Catalina, there will be a lot of visual bugs and stability is still unknown.

For example, this is what happens when you sleep wake with an ATI/AMD GPU with our current private acceleration patches:View attachment 1758524

Already looks good (despite the wake-up flaws), I´m not shocked at all but pleasantly surprised instead. Keep going! ;-)

 

[air.man]

I had similar observations on my MBP5,2.

Internal audio will work when booting via OCLP 0.0.22 (no new installation needed, if I remember correctly).

Slow reaction speed, esp. during setup: jackluke's method installs ASentientBot's framebuffer patch which helps a lot, esp. for quick mouse movement; while OCLP doesn't yet I think (maybe with the next 0.0.23).

I'm presently using an OCLP 0.0.22 installation with 11.3b8, and a BigSurBaseSystemfix installation with 11.2.3, and I think I'll continue this for future versions.

Same comments here with a MB5,1. OCLP is currently slower and a bit more laggy then the JakeLuke's BigSurBaseSystemFix. The last version (0.0.23) introduces the framework support for brightness control, night shift and sleep, so the two approaches provides the same functionalities. No GPU acceleration yet, even if the Nvidia cards are reported as working.
The plus of OCLP are the availability of OTA updates and the continue activity of developing and finally the GPU accelleration when available. In addition new versions require to update the EFI only, without reinstalling the whole system.

 

[OKonnel]

...(...omissis...)... You have really installed on a clean empty partition? (no update of a micropatched version)
You have a single OCLP (OpenCore) version installed on your internal EFI?
You have generated this for the right system (it should print the 14,2 when using OCLP on the top four lines)?
Photo Booth on 11.2.3 iMac 12,2 AMD WX4170 is working smoothly. And this is a machine/ssd never had a micropatched installation seen.

Hello @Ausdauersportler! I have already answered you, but now I can add more useful information and this new post on the same issue.

So! Today I followed your suggestion and installed Big Sur 11.2.3 on another SSD, using Micropatcher instead of OpenCore LP. Photo Booth still doesn't display all Effects and even if it takes photos, it doesn't record video but only audio. So! I then reinitialised the disk and tried to install Big Sur 11.3 Beta 8, but without success.

I just found out, however, that Photo Booth works perfectly if I restart my Mac in Safe Mode and with Micropatcher or with OpenCore LP and both Big Sure, 11.2.3 or 11.3, it always works!

At this point do you think can also spoofing the Video Card, perhaps to make macOS believe that the Graphics Card is NVIDIA GTX 775M or some other similar, compatible with Big Sur, instead that GTX 780M?
Or it's possible to do some other kind of patch? For example by adding the GTX 780M's KEXT taken from Catalina and that perhaps Apple has no longer included in Big Sur, since the 27'' iMacs of late 2013 are not supported?
Succeeding in this small adventure would be a big win for all of us . Thank you

 

[strof]

Acceleration patches are not public, and likely won't be for another few months. We highly recommend users with non-Metal GPUs to run older OSes such as Catalina or Mojave

Even once acceleration patches do release to the public, we do want to ensure everyone's expectations are low. It will be worse than Catalina, there will be a lot of visual bugs and stability is still unknown.

For example, this is what happens when you sleep wake with an ATI/AMD GPU with our current private acceleration patches:View attachment 1758524

Why did you not release these patches to the public? Because of the troubles or anything else?

 

[Ausdauersportler]

Hello @Ausdauersportler! I have already answered you, but now I can add more useful information and this new post on the same issue.

So! Today I followed your suggestion and installed Big Sur 11.2.3 on another SSD, using Micropatcher instead of OpenCore LP. Photo Booth still doesn't display all Effects and even if it takes photos, it doesn't record video but only audio. So! I then reinitialised the disk and tried to install Big Sur 11.3 Beta 8, but without success.

I just found out, however, that Photo Booth works perfectly if I restart my Mac in Safe Mode and with Micropatcher or with OpenCore LP and both Big Sure, 11.2.3 or 11.3, it always works!

At this point do you think can also spoofing the Video Card, perhaps to make macOS believe that the Graphics Card is NVIDIA GTX 775M or some other similar, compatible with Big Sur, instead that GTX 780M?
Or it's possible to do some other kind of patch? For example by adding the GTX 780M's KEXT taken from Catalina and that perhaps Apple has no longer included in Big Sur, since the 27'' iMacs of late 2013 are not supported?
Succeeding in this small adventure would be a big win for all of us . Thank you

Hello!

I would not go the patch way, because it would break the OTA update again. Photo Booth is simply not a major problem. Compared to former macOS versions the number of available filters and effects dropped dramatically.

There is no single 780M.kext, there is NVIDIA Kepler support in macOS hidden in a number or kernel extensions and frameworks, the GPU 780M is one of about 20 different Kepler mobile models. Of course Apple very often uses keys to enable or disable features, like a set of board-ids to enable Night Shift.

Your Mac edition 780 has the device-id 119E.

You can modify your config.plist and add to the DeviceProperties section your graphics device path and add there a single entry called device-id using the 775M number 119D. You will have to add a key 9D110000 if I am not mistaken. Sometimes changing this value enable some features, again. Or you can try the 780M (non Mac) device-id 119F using key 9F110000.

Honestly I do not know if this changes something on your iMac.

Good luck!

 

[hadnet]

Hello!

I have a problem while installing Big Sur using micropatcher on my iMac Mid 2011 21,5. No, I am not talking about metal related issues because I have upgraded it's video card, with custom vBios, the thing worked with Catalina no problem. The issue I'm having is...weird. While installing macOS BigSur with patched bootable USB, after some time there is that part of installation in which iMac reboots couple of times to finish doing it's stuff. But, after iMac reboots, the screen is dead black but iMac is still running, doing it's thing. At one point reboots stop, the fans are still spining (i have SSD so no thermal sensor for me) but iMac is cool to the touch but no image whatsoever. Nothing changes after turning iMac off and on, only blackness.

B U T

If I hold option key and boot to boot menu and then choose Macintosh HD drive (the one with BigSur) eveything works fine. Screen is bright, colors are vibrant it's just perfect. But after rebooting again (without option key) - blackness again. Pulling out Bootable USB? Doesn't work. Installing kexts form modified BigSur USB? Nothing. Reseting Nvram, SNC, praying to late Steve Jobs, dancing?
N O T H I N G

What the heck is going on?

Hi, I'm having the same problem. I need to press Option in order to boot up, after that I get all working good (Wi-fi, sound). How did you solve this press Option issue? Can you help me, please?

Note: I used the BenSova patcher v0.1.2 beta

 

[khronokernel]

Hello everyone, with OCLP v0.0.23 right around the corner we decided to hold a poll regarding how defaults should be handled for non-Metal GPUs.

Currently, OCLP defaults to SIP and OTA Delta update support for all models and requires users to manually disable these options in patcher settings if they desired root patching (ie. brightness control)

With 0.0.23, we've added the framebuffers for legacy GPUs allowing brightness control support for the majority of machines however this comes at the cost of SIP and Delta update support. The biggest benefit for adding these framebuffers of legacy GPUs is providing better overall cursor and OS usage. Note that this is still unaccelerated, and will still be unbearable compared to Catalina and Mojave's current acceleration state.

So we ask:

Would users prefer brightness control and slightly smoother OS usage or delta updates with all the bells and whistles of SIP, AMFI, etc?

Please respond to the straw poll below:

What is more important: Brightness Control and smoother OS experience or Delta Updates, SIP and AMFI

Vote Now! [Brightness Control and smoother OS experience is more important] [Security and Delta updates are top priority]

www.strawpoll.me

 

[khronokernel]

To clarify, the above settings are merely defaults. They can be override by the end user. We're mainly trying to decide what the default logic of OCLP should be

 

[joevt]

To clarify, the above settings are merely defaults. They can be override by the end user. We're mainly trying to decide what the default logic of OCLP should be

When installing a new OS, probably want SIP and OTA updates enabled, then when the updating is done, switch to better Framebuffer, and repeat occasionally.

SIP and OTA updates remains the default for metal GPUs? So maybe should be the default of other GPUs too.

Maybe I would have an OpenCore partition for each. Does OpenCore work well from an HFS+ partition (HFS+ is read-only in EFI so logs and screenshots would need to go to a FAT or EFI partition)? I prefer HFS+ because Startup Manager will show a disk label + icon instead of "EFI Boot" + icon.

 

[Ausdauersportler]

Hi, I'm having the same problem. I need to press Option in order to boot up, after that I get all working good (Wi-fi, sound). How did you solve this press Option issue? Can you help me, please?

Note: I used the BenSova patcher v0.1.2 beta

Just answered one the github page. You should use the either my iMac micropatcher (because these patches are included there) or better OCLP (which makes your iMac a supported system needing no patches at all).

Assuming you own an 2011 imac modded with an NVIDIA GPU. You should add this to every post you make here (a signature is helpful). I am not really goof at guessing this

BTW:
Can please users of iMac Late 2009 to Mid 2011 with NVIDIA GPU report back if they have this black screen issue with OCLP?

 

[AlexSakha67]

Post-Install Volume Patch! Big Sur MacBook7.1.
Hi, the question is when I restore all the Opencore-Patcher.Command and Point 3.Post-Instate Patch, then the point 1. The volume of the patch system is all loaded and installed in S / L / E GeForcega.Bundle, NVDANV50Haltesla.kext and T . d. But iOSURFACE .KEXT is not installed iOSurface.kext not set to S / L / E
The system has become more responsive, but when I open the folders, it slows down for 6-8 seconds.
Thanks again thanks to the developers in accordance with my data, that the volume of the patch system will gradually go to OCLP😊✌️/Google translator/

 

[khronokernel]

But iOSURFACE .KEXT is not installed iOSurface.kext not set to S / L / E

That's correct, the patched IOSurface is only to be installed when graphics acceleration patches are added in main. Otherwise, there's no benefit to downgrading the kext when we're simply adding the frame buffer for brightness control

 

[khronokernel]

Hello everyone, we've just released OpenCore Legacy Patcher 0.1.0!

Release 0.1.0 · dortania/OpenCore-Legacy-Patcher

0.1.0 Fix crash on iMacs with Metal GPUs 0.0.23 Fix MacBookPro4,1 15" and 17" audio support Fix iMac7,1 24" and iMac9,1 24" audio support Fix Macmini4,1 audio support Increment binaries AppleAL...

github.com

Overall the changes are more quality of life with config building such as much better hardware detection, however this also includes the long awaited brightness control and framebuffer patches for legacy GPUs. As we polled earlier in the thread, OCLP will now build configurations that make it easier to patch the root volume by default however users who wish to have Delta updates and SIP can change the default in patcher settings. Note this only applies for models with legacy GPUs, Metal GPU models still have full SIP and delta update support

Additionally, with 0.0.23 we've added a new command line binary allowing easy building and patching with OCLP. This means that any other patcher, such as Patched Sur or MicropatcherAutomator, can easily hook onto the OCLP-CLI binary and call it to provide an OpenCore configuration. We hope these changes will get more users in the community to experiment and contribute back to legacy Mac community!

Edit: Due to an unfortunate bug in 0.0.23, we did a quick fix and released 0.1.0 to resolve issues for iMac users with Metal GPUs running OCLP

Example command for OCLP-CLI:

./OCLP-CLI --build --verbose --debug_oc --debug_kext --model iMac11,2

 

[panwato]

I updated OCLP to 0.0.23 and all is working perfectly, including backlight control.
I do some changes in patcher settings, (force Nvidia, set both SIP and SBM to true, and disabled boot picker)

So, thanks to all the people behind this incredible tool.

 

[kral84]

0.1.0 is working fine with imac 12,2 and K1100m on Big Sur (force Nvidia and Sip both disable) !! Thank youfor the fast fix

 

[jacob_pro]

We can wait until fix graphics lagging maybe in OCLP 0.023

 

[sergiodadi]

Hello everyone, I have a request from OpenCore Legacy Patcher users. Specifically we're looking to document more success cases within the patcher, this allows us to check if a specific model's been tested in the wild as well as what version of OCLP is used.

This should aid greatly for both us (the developers) as well as the users when troubleshooting since they're able to more easily find what version is known good in the event the latest release of the patcher has regressions.

To help out, we're mainly asking for the following:
- Machine model (ie. iMac14,2)
- Patcher version (ie. 0.0.21)
- Any extra mods done to the machine (ie. Wifi or GPU upgrade)

- Machine Model: iMac12,2 (iMac 27 " mi 2011)
- Patcher version: 0.0.22
- Upgraded WX4130 GPU (WX4130 Dell model)


thank for your work on OCLP

 

[lumos]

Hello everyone, we've just released OpenCore Legacy Patcher 0.1.0!

Release 0.0.23 · dortania/OpenCore-Legacy-Patcher

Fix MacBookPro4,1 15" and 17" audio support Fix iMac7,1 24" and iMac9,1 24" audio support Fix Macmini4,1 audio support Increment binaries AppleALC 1a3e5cb (1.6.0 rolling - 04-14-2021) Enhance Wi...

github.com

Overall the changes are more quality of life with config building such as much better hardware detection, however this also includes the long awaited brightness control and framebuffer patches for legacy GPUs. As we polled earlier in the thread, OCLP will now build configurations that make it easier to patch the root volume by default however users who wish to have Delta updates and SIP can change the default in patcher settings. Note this only applies for models with legacy GPUs, Metal GPU models still have full SIP and delta update support

Additionally, with 0.0.23 we've added a new command line binary allowing easy building and patching with OCLP. This means that any other patcher, such as Patched Sur or MicropatcherAutomator, can easily hook onto the OCLP-CLI binary and call it to provide an OpenCore configuration. We hope these changes will get more users in the community to experiment and contribute back to legacy Mac community!

Edit: Due to an unfortunate bug in 0.0.23, we did a quick fix and released 0.1.0 to resolve issues for iMac users with Metal GPUs running OCLP

Example command for OCLP-CLI:

./OCLP-CLI --build --verbose --debug_oc --debug_kext --model iMac11,2

Thank you for the great work!!!

 

[danslecarton]

Every time I close my 2012 Air and open it up again, I get this message. Is there a way to fix it?
I installed Big Sur through OCLP and also patched the EFI to boot without an USB drive.
I believe @A4orce84 had a similar issue?

 

[RogueB]

Hello everyone, we've just released OpenCore Legacy Patcher 0.1.0!

Release 0.1.0 · dortania/OpenCore-Legacy-Patcher

0.1.0 Fix crash on iMacs with Metal GPUs 0.0.23 Fix MacBookPro4,1 15" and 17" audio support Fix iMac7,1 24" and iMac9,1 24" audio support Fix Macmini4,1 audio support Increment binaries AppleAL...

github.com

Overall the changes are more quality of life with config building such as much better hardware detection, however this also includes the long awaited brightness control and framebuffer patches for legacy GPUs. As we polled earlier in the thread, OCLP will now build configurations that make it easier to patch the root volume by default however users who wish to have Delta updates and SIP can change the default in patcher settings. Note this only applies for models with legacy GPUs, Metal GPU models still have full SIP and delta update support

Additionally, with 0.0.23 we've added a new command line binary allowing easy building and patching with OCLP. This means that any other patcher, such as Patched Sur or MicropatcherAutomator, can easily hook onto the OCLP-CLI binary and call it to provide an OpenCore configuration. We hope these changes will get more users in the community to experiment and contribute back to legacy Mac community!

Edit: Due to an unfortunate bug in 0.0.23, we did a quick fix and released 0.1.0 to resolve issues for iMac users with Metal GPUs running OCLP

Example command for OCLP-CLI:

./OCLP-CLI --build --verbose --debug_oc --debug_kext --model iMac11,2

MacBook Pro 5,2 (17-inch, Mid 2009)
3.06 GHz Intel Core 2 Duo
8 GB 1067 MHz DDR3
NVIDIA GeForce 9600M GT 512 MB
Samsung SSD EVO 860 1 TB — two partitions: 1st has Catalina and Mojave OSs installed, 2nd has Big Sur.

Hello,

In spirit of feedback and testing ...

Installed 11.3 beta8 with OCLP 0.1.0:

Installation of the OS was similar to experience described in post #9678 above.

There was an improvement in rate of account set up, due to (now) active framebuffer(?)

Currently functional are sound control, key brightness and iSight camera.
Still Unavailable are screen brightness control and choice of screen resolutions.

Overall, after OS finishes the usual post-install housekeeping, and system animation is disabled, the response and usability almost rivals that of OS installation via BigSur BaseSystemFixes.

Hope this may be of help.

An addendum:

Just booted into Catalina and found that Big Sur partition does not show up on the desktop, nor is it visible via disk utility menu. Booting back into Big Sur requires OCLP EFI boot process; selecting Big Sur in Apple Picker leads to prohibitory sign. The degree of lag also varies while moving through Big Sur. Unless something unusual occurred during installation, it would seem that OCLP 0.1.0 still needs some "tweaking", at least for my machine(?)

Attached: screen shot of disk utility listings from Catalina OS - note: container 2, is the partition with
BigSur installation (currently missing from listing)

 

[straycat23]

Finally got Big Sur on my Mac Pro 2012 with a Radeon HD 7950. Downloaded the latest update, which was 11.2.1. Somehow with these security updates Apple is putting into their OS, I don't think you'll be able to load past 11.2.1, on anything with a USB1 or 2 or aftermarket USB3. Others may have a different experience than I did. If you did, I wish you would post it. I tried everything. I left the installer in Applications. I then downloaded the micro patcher from Github and left it in Downloads. I then created a USB. It has to be at least 16GB and left it named USB for a correct pathway. In Terminal, I put the command: sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/USB. This came from elitemacx86.com. With this command, Terminal collects the installer and the micropatcher, and your Installer USB is complete. All that is left is booting from your USB. It worked perfectly. Hopes this helps someone.

 

[startergo]

OpenCore Legacy Patcher by @khronokernel and @dhinakg is a completely different approach based on OpenCore. Detailed information is available from his announcement on this thread and their guide. This is currently the only option offering system updates via Apple software update like all supported Macs.

I don't think you'll be able to load past 11.2.1, on anything with a USB1 or 2 or aftermarket USB3.

I am not sure why you use micro patchers at all? There is a big WIKI thread for cMP5,1:

OpenCore on the Mac Pro

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

forums.macrumors.com

Up to System Version: macOS 11.2.3 (20D91)
Big Sur is very installable and usable.

 

[straycat23]

am not sure why you use micro patchers at all? There is a big WIKI thread for cMP5,1:

Basically because it took me a long time to figure this out, and I didn't know this OpenCore existed. Though I've used Macintosh a long time actually since 1984 with the Macintosh 128, I'm not that geeky. I'll try it on my High Sierra SSD. Are there any problems using it with USB PCIE cards? Thanks a lot for giving me a heads up.

 

[startergo]

Are there any problems using it with USB PCIE cards?

Not really. But you can not boot from a USB attached to a USB 3. PCIE card.