macOS 11 Big Sur on Unsupported Macs Thread

[khronokernel]

Hello everyone, we're proud to release OpenCore Legacy Patcher 0.1.3!

Release 0.1.3 · dortania/OpenCore-Legacy-Patcher

Fix internal PCIe devices reporting as external Opt for built-in when device path is detectable Innie 0ccd95e (1.3.0 release - 01-16-2021) Fix MacBookPro5,4 audio support Increment binaries App...

github.com

Overall note worthy changes are:
- Allow custom CPU names in About This Mac
- Fix iMac7,1, iMac8,1 and iMac9,1 audio support
- Disable the Bluetooth 2.0 controller working around Kernel Panics in iMac7,1 and MacPro3,1
- Fix external display output support on 2012+ iMacs

Hope everyone enjoys the new changes!

 

[lumos]

Hello everyone, we're proud to release OpenCore Legacy Patcher 0.1.3!

Release 0.1.3 · dortania/OpenCore-Legacy-Patcher

Fix internal PCIe devices reporting as external Opt for built-in when device path is detectable Innie 0ccd95e (1.3.0 release - 01-16-2021) Fix MacBookPro5,4 audio support Increment binaries App...

github.com

Overall note worthy changes are:
- Allow custom CPU names in About This Mac
- Fix iMac7,1, iMac8,1 and iMac9,1 audio support
- Disable the Bluetooth 2.0 controller working around Kernel Panics in iMac7,1 and MacPro3,1
- Fix external display output support on 2012+ iMacs

Hope everyone enjoys the new changes!

Thank you for your great job!!!

 

[Ausdauersportler]

With the latest OCLP on an iMac12,2 with a K4100M, do I have to do anything special for it? I'm getting some interesting banding issues going on with the transparency of windows. Everything else seems fine.. Not a big deal, was just curious. I installed 11.3.1.

These little problems are visible only with NVIDIA dGPU only but not limited to the iMac12,x. You observe it on more recent iMac models, too. So this is IMHO not a patcher issue, this is most likely an Apple bug. We had this nearly from day one with all patcher versions available. But who knows...

You may search back this thread, we had numerous such posts. If you are curious you search for answer, do you

 

[Allistah]

These little problems are visible only with NVIDIA dGPU only but not limited to the iMac12,x. You observe it on more recent iMac models, too. So this is IMHO not a patcher issue, this is most likely an Apple bug. We had this nearly from day one with all patcher versions available. But who knows...

You may search back this thread, we had numerous such posts. If you are curious you search for answer, do you

Ok, cool - thanks for the answer. Yeah, it seems pretty benign at this point so I don't care really. Everything works and videos seem to play just fine so I'm happy. Thanks again for all the hard work on this, it was a lot easier than using the Barry micropatcher. I was having to do full installs every time. Looking forward to the next OTA update so I can just do it like normal.

 

[buckrock]

Big Sur 11.4 beta 3 (build 20F5065a) 12.4GB full installer is available at:

http://swcdn.apple.com/content/down...slqm1stqe2fariwlhx2qbpv1/InstallAssistant.pkg

Specifications:
1. macOS Big Sur Beta 11.4 (20F5065a) - 071-38768 - Added 2021-05-11 18:00:03

Edited: I can verify BarryKN's 0.5.1 micropatcher still works. My rMBP mid-02012 is described in my signature.

 

[David dongfox]

i am using Mac Mini Late 2012, i try to follow OCLP guide but still can’t install . if anyone who can write a step-by-step to help me for my Mac mini. Thanks

 

[mwidjaya]

i am using Mac Mini Late 2012, i try to follow OCLP guide but still can’t install . if anyone who can write a step-by-step to help me for my Mac mini. Thanks

The official guide is already step by step. The 2012 mini is fully supported by OCLP; meaning you can use all the defaults and need not change any of the OCLP patcher settings.

There is however a bar to clear in terms of skills in executing some terminal commands.

Which step(s) are you having trouble with?

 

[Larsvonhier]

With the latest OCLP on an iMac12,2 with a K4100M, do I have to do anything special for it? I'm getting some interesting banding issues going on with the transparency of windows. Everything else seems fine.. Not a big deal, was just curious. I installed 11.3.1.

Can you post a screenshot - would like to know what it looks like...

 

[StephN999]

Bonjour,

OpenCore Legacy Patcher 0.1.4 (with some slight modifications)
+ OpenCore 0.7.0 (95bb2d7)
+ macOS 11.4 (20F5065a)

Everything is Ok.

Just a question about "Disabling unsupported iGPU" where is this patch, in a kext or the OpenCore plist?
Because either it doesn't work on my Xeon, or I failed to copy what I needed to make it work.

@khronokernel> I would like to ask you about my modification of the EFI of the iMac 2011 for Ivy Bridge support, can I send you a PM?

 

[Larsvonhier]

Question to users of MacBook 4,1 and @ASentientBot :
The basic installation with OCLP 0.6.9 / macOS 11.4 (betas 1...3) and patcher settings for MacBook4,1 works as expected, initially without framebuffer (and OpenGL, which will prob'ly never reach the x3100 GPU).
As with Mojave and Catalina on this machine, I'd like to at least see the full framebuffer (144MB).
Whenever I patch the boot volume with the OC patcher for this machine, I get the forever-spinning white wheel during boot, shortly before the user login screen. I know this behaviour might come from modified/replaced skylight and other frameworks that re-enable OpenGL on old GPUs. I'd like to skip this and just have the two/three x3100 kexts needed for the framebuffer-acceleration. How can this be done? The default skript for the MB4,1 does not take that into account (as nice as it is to have it included!).
Or are there already any success stories on the MB4,1 and I'm just getting it wrong?
Advice appreciated...!

 

[Ausdauersportler]

Question to users of MacBook 4,1 and @ASentientBot :
The basic installation with OCLP 0.6.9 / macOS 11.4 (betas 1...3) and patcher settings for MacBook4,1 works as expected, initially without framebuffer (and OpenGL, which will prob'ly never reach the x3100 GPU).
As with Mojave and Catalina on this machine, I'd like to at least see the full framebuffer (144MB).
Whenever I patch the boot volume with the OC patcher for this machine, I get the forever-spinning white wheel during boot, shortly before the user login screen. I know this behaviour might come from modified/replaced skylight and other frameworks that re-enable OpenGL on old GPUs. I'd like to skip this and just have the two/three x3100 kexts needed for the framebuffer-acceleration. How can this be done? The default skript for the MB4,1 does not take that into account (as nice as it is to have it included!).
Or are there any success stories on the MB4,1 and I'm getting it wrong?
Advice appreciated...!

Join Discord and download the complete patches manually, try the micropatcher method to change the system root volume and experiment on your system. This way you can join the dev team

 

[K two]

never mind ☺️

 

[Ausdauersportler]

What is the Update partition? Why is it there? 11.3.1 OCLP 0.1.3

This has been posted long ago on the thread...found it here.

EDIT: Added the link to the FAQ in case someone wants to read it
EDIT 2: Link was already there in this question: Q: How to prepare my installation disk before installation?

 

[K two]

i am using Mac Mini Late 2012, i try to follow OCLP guide but still can’t install . if anyone who can write a step-by-step to help me for my Mac mini. Thanks

Step by step - https://dortania.github.io/OpenCore-Legacy-Patcher/INSTALLER.html#downloading

 

[KennyW]

Hello everyone, we're proud to release OpenCore Legacy Patcher 0.1.3!

Release 0.1.3 · dortania/OpenCore-Legacy-Patcher

Fix internal PCIe devices reporting as external Opt for built-in when device path is detectable Innie 0ccd95e (1.3.0 release - 01-16-2021) Fix MacBookPro5,4 audio support Increment binaries App...

github.com

Overall note worthy changes are:
- Allow custom CPU names in About This Mac
- Fix iMac7,1, iMac8,1 and iMac9,1 audio support
- Disable the Bluetooth 2.0 controller working around Kernel Panics in iMac7,1 and MacPro3,1
- Fix external display output support on 2012+ iMacs

Hope everyone enjoys the new changes!

Error in creating the OCLP ...... both 0.1.3 and 0.1.4

 

[K two]

This has been posted long ago on the thread...found it here.

EDIT: Added the link to the FAQ in case someone reads it

Thanks for the info and the FAQ update. 😉

 

[khronokernel]

Error in creating the OCLP ...... both 0.1.3 and 0.1.4

View attachment 1773594

Please report issues on Github, not forums

 

[HonzaJaros]

Hello, is there a way how I can create OCLP on windows? My Mac seems to be out of order
I had patched sur and I delete partition and on other Mac I wanted to download and create the USB meanwhile and disk died

mbp mid 2012

so only hw is iPad Pro or fiance’s HP laptop

i have tried to recover to mountain lion but after instalation it goes straight to recovery

 

[khronokernel]

Hello, is there a way how I can create OCLP on windows? My Mac seems to be out of order
I had patched sur and I delete partition and on other Mac I wanted to download and create the USB meanwhile and disk died

so only hw is iPad Pro or fiance’s HP laptop

i have tried to recover to mountain lion but after instalation it goes straight to recovery

What Mac? Also if you know how to use the Command Line in Windows, it's actually fairly simple to get a bootable Big Sur installer

Basically the idea is as follows:

- Format a USB drive as FAT32 in Windows (needs to be 4GB~)
- Download an EFI for OCLP compatible with your model
- I can provide once you tell me the model
- Download a macOS Big Sur recovery image with /Utilities/macrecovery/macrecovery.py
- Place the EFI folder from OCLP onto root of the drive
- Create a new folder on the root of the USB drive called com.apple.recovery.boot
- Place the BaseSystem.dmg and BaseSystem.chunklist we downloaded from macrecovery.py

For more step-by-step, can follow the below guide:

Making the installer in Windows | OpenCore Install Guide

At the end, instead of placing OpenCorePkg's EFI folder you'll place then one I'd give you

 

[HonzaJaros]

What Mac? Also if you know how to use the Command Line in Windows, it's actually fairly simple to get a bootable Big Sur installer

Basically the idea is as follows:

- Format a USB drive as FAT32 in Windows (needs to be 4GB~)
- Download an EFI for OCLP compatible with your model
- I can provide once you tell me the model
- Download a macOS Big Sur recovery image with /Utilities/macrecovery/macrecovery.py
- Place the EFI folder from OCLP onto root of the drive
- Create a new folder on the root of the USB drive called com.apple.recovery.boot
- Place the BaseSystem.dmg and BaseSystem.chunklist we downloaded from macrecovery.py

For more step-by-step, can follow the below guide:

Making the installer in Windows | OpenCore Install Guide

At the end, instead of placing OpenCorePkg's EFI folder you'll place then one I'd give you

its MacBook Pro 13 mid 2012

I did the usb, I can see the efi to boot and once I hit enter it freezes

is it because the wrong efi right?

 

[K two]

Any way to toggle OFF the auto select countdown timer in the OCLP Boot Picker?

 

[Allistah]

Any way to toggle OFF the auto select countdown timer in the OCLP Boot Picker?

I was curious about this too.. ..and if there were any repercussions for lowering it? It's not too long the way it is though so it's not too much of a bother to me but I was indeed curious.

 

[Ausdauersportler]

I was curious about this too.. ..and if there were any repercussions for lowering it? It's not too long the way it is though so it's not too much of a bother to me but I was indeed curious.

OpenCore docs are the right place to look for fine tuning like this. If you do not want to see it all you can configure this using the OCLP app, too. It is most useful for graphics cards without an EFI boot picker.

OpenCore offers thousands of those settings, it is impossible to make all adjustable using the OCLP app. This would create another interface to OpenCore - like editing the config.plist on your own from the scratch

 

[kakumakaku]

Hello! Apologies in advance for my english)
I studied the forum for a long time and looked for my problem through a search in the branch, but unfortunately I did not find anything, so I ask for help. I want to thank in advance all active users of this forum, for the already completed upgrade of my iMac 12.2 27"(2011) from HD6970 to GTX 880m(already a year in use and everything works well), now I'm waiting for a WX7100 card and details for updating WIFI + BT, I hope that the card with the number "C" will be working)
Now I'm trying to update my iMac to Big Sur via Opencore, but I ran into a problem in the form of an endless restart into recovery mode during installation and I have been trying to deal with it for two days

I will describe the order of my actions:

1. Made a bootable USB with Big Sur (tried different versions 11.2.1 / 11.3 / 11.3.1), formatted the drive in a GUID, as indicated in the instructions, to create an additional EFI partition.

2. Launched the Opencore app(0.1.4), created an assembly for my model and wrote it to the EFI partition of the pre-created Big Sur boot disk.

3. Restarting in the drive selection mode and choosing to boot "EFI boot opencore" (no further black screen with text followed, as shown in many videos, but the background turned black, not white), chose the Big Sur installation.

4. Installation proceeds normally until the remainder of 12 minutes before completion, then a reboot occurs and goes into OS Sierra recovery mode.
I tried resetting PRAM every time I boot, go into disk selection mode and then go to Opencore and turn on the Big Sur installation, but either a black screen with a lock sign came out, or the Sierra recovery process loaded.

I read that this is possible due to a broken disk signature, but I don't quite understand how to fix it.

Thanks in advance!

 

[wire_]

Exactly!
Thank you for understanding. I'm not in a hurry, but gradually I will either figure out the intricacies, or ... update the hardware

To make things easier get Propertree, a lightweight plist editor, mountEFI.command script (or any other other means of mounting your OCLP EFI partition) then...

If I recall the context of your question properly

...edit config.plist by finding NVRAM entry and the sub-entry uuid for boot-args, and adding agdpmod=vit9696 to boot args

Plist keys that begin with # are comment so you can make notes to yourself in the file.

This option is a whatevergreen.kext (graphics patcher) option pertaining to board-id spoofing to work around black screen in certain SMBIOS igpu/dgpu combos. vit9696 is the handle of a whatevergreen author and the option is named for his discovery of the workaround.

Note that all the technical explanations for the patches are in the form of lore about what works, which often crosses over into detailed technical understanding but at core (haha) this is hacking not engineering, so a lot of features and explanations are circular and obtuse. It a fun hazard of the culture.

The OC config.plist structure is quite well documented at Dortania github

* * *

I think its funny that Microsoft owns github and it has become defacto central house for mac nerds struggling to keep old HW alive. 'warms my heart.