macOS 11 Big Sur on Unsupported Macs Thread

[rokko101]

Hi there.

I've installed Big Sur 11.6.1 on my Mac mini 2012 (i7 2.6) using the latest OCLP version... Almost everything works fine ... Except some 3d rendering apps such as floorplanner.com or room arranger ... They just crash.

It seems there's a problem with some portion of the HD4000 graphics drivers.

Can any one confirm or have any idea of how to fix it?

Thanx.

 

[Ganoninc]

Hello there,

My modded iMac 27 2010 with a Quadro K610M is running Big Sur 11.6.1 thanks to OpenCore Legacy Patcher version 0.3.1.

It's almost perfect but I've got a minor issue. It can't sleep for good.

When I was running Catalina, I was able to put it to sleep before going to bed and it would stay quiet during the night.

Now, if I put it to sleep, it wakes up regularly for maybe a minute and then goes to sleep again. So during the night, I can hear the fans spinning even if the screen remains perfectly dark.

I cannot see why it does that: log show --style syslog | fgrep "Wake reason" gives me some mysterious reasons:

2021-11-03 18:36:30.079640+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 18:37:05.945240+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 18:37:05.945243+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 18:43:57.459645+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 18:44:46.639466+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 18:44:46.639468+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:00:39.539569+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 19:01:29.372810+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:01:29.372812+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:20:46.564135+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 19:21:36.662417+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:21:36.662421+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:31:27.877314+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 19:32:17.274196+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:32:17.274198+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:32:27.584504+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 19:33:16.828756+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:33:16.828757+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:33:22.569213+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 19:34:11.798742+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:34:11.798744+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:35:06.540217+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 19:35:55.770890+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:35:55.770892+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:46:32.541367+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 19:47:22.138593+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 19:47:22.138595+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 20:05:46.489347+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 20:09:06.445556+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 20:09:06.445557+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 20:09:18.820908+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 20:10:08.068836+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 20:10:08.068837+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 20:10:39.520327+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 20:11:28.768794+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 20:11:28.768796+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 20:11:33.565567+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"
2021-11-03 20:12:23.021762+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 20:12:23.021764+0100 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: ?
2021-11-03 20:12:38.523268+0100 localhost powerd[89]: [powerd:sleepWake] Wake reason: "<private>" identity: "<private>"

and pmset -g returns the following:

System-wide power settings:
Currently in use:
standby 1
Sleep On Power Button 1
womp 0
halfdim 1
hibernatefile /var/vm/sleepimage
autorestart 0
networkoversleep 0
disksleep 10
sleep 10
hibernatemode 0
ttyskeepawake 1
displaysleep 10
standbydelaylow 4200

Here are my settings on Energy saver panel :

Any idea ?

 

[internetzel]

Hello there,

My modded iMac 27 2010 with a Quadro K610M is running Big Sur 11.6.1 thanks to OpenCore Legacy Patcher version 0.3.1.

It's almost perfect but I've got a minor issue. It can't sleep for good.

When I was running Catalina, I was able to put it to sleep before going to bed and it would stay quiet during the night.

Now, if I put it to sleep, it wakes up regularly for maybe a minute and then goes to sleep again. So during the night, I can hear the fans spinning even if the screen remains perfectly dark.

I cannot see why it does that: log show --style syslog | fgrep "Wake reason" gives me some mysterious reasons:



and pmset -g returns the following:



Here are my settings on Energy saver panel :

View attachment 1901805

Any idea ?

I had the same thing happening with my iMac late 2009 in High Sierra - although I don't remember how exactly I had solved it.
In order to know the wake reason you should search the output of

pmset -g log

In my case it was a so called dark wake because of wake on WiFi being enabled.
So I think in order to solve it I had enabled "Wake for network access", sent the system to sleep, woke it up and disabled "Wake for network access". (In the log I could see that before going to sleep there was a dark wake being scheduled.)
If you're lucky you might then see that no further dark wakes get scheduled.
You might also try an NVRAM reset.
I had something similar happening when I had Screen Time enabled in Catalina, but then the system woke up with the screen turned on. That didn't happen anymore once I disabled Screen Time.

 

[Gorditcho]

Remove the HDD from CMP completely; to prevent any confusion/mix up.

Start like new with release version of OCLP.
- build OCLP, install OCLP onto Big Sur USB stick installer
- boot OCLP EFI, install BS onto your SSD (I prefer clean install i.e. erase SSD, format APFS)
- fresh install of apps, copy your files from backup (or restore from Time Machine backup)
- build OCLP again, install OCLP onto SSD, if you want to boot without the USB stick connected all the time

Hey folks, I'm getting a lot lof grief with trying to install Big Sur on my 2011 iMac. The problem centres around my GTX 780M card I believe. I have created my USB install as per Mr Macintosh's instructions but I get stuck on verbose error 'gIOScreenLockState 3' I have been advised to ad 'agdpmod=vit9696' to the boot-args. The trouble is I have no idea how to edit 'Opencore'. Any and all help would be hugely appreciated! Cheers!

 

[Ausdauersportler]

Hey folks, I'm getting a lot lof grief with trying to install Big Sur on my 2011 iMac. The problem centres around my GTX 780M card I believe. I have created my USB install as per Mr Macintosh's instructions but I get stuck on verbose error 'gIOScreenLockState 3' I have been advised to ad 'agdpmod=vit9696' to the boot-args. The trouble is I have no idea how to edit 'Opencore'. Any and all help would be hugely appreciated! Cheers!

1. Try to run native High Sierra on this system to exclude a defective graphics card. Run HW Monitor and report all temp readings. May be you face an SMC problem because your particular card model has some incompatible chips causing conflicts on the SMBUS. The other possible explanation is: A defective and dying dGPU or VRAM.

2. It is not necessary to add this agdpmod=vit9696 entry to the boot-args, OCLP always does it for these iMac12,2 with NVIDIA dGPU. So please to not alter or edit your OC configuration.

3. We have seen very often hardware problems with graphics cards becoming apparent when migrating to a more recent macOS version. These GTX cards have been used the last 9 (nine) years mostly in gaming laptops and may be already burned or played to death.

 

[Gorditcho]

1. Try to run native High Sierra on this system to exclude a defective graphics card. Run HW Monitor and report all temp readings. May be you face an SMC problem because your particular card model has some incompatible chips causing conflicts on the SMBUS. The other possible explanation is: A defective and dying dGPU or VRAM.

2. It is not necessary to add this agdpmod=vit9696 entry to the boot-args, OCLP always does it for these iMac12,2 with NVIDIA dGPU. So please to not alter or edit your OC configuration.

3. We have seen very often hardware problems with graphics cards becoming apparent when migrating to a more recent macOS version. These GTX cards have been used the last 9 (nine) years mostly in gaming laptops and may be already burned or played to death.

Thank you 'Ausdauersporter' you are a gentleman!
I have loaded High Sierra on this machine many times over the last few days while trying to get this card to let me install Big Sur through OCPL. It runs High Sierra natively no problem at all. I will run High Sierra with HW Monitor as you suggest. Should I also run all the OCLP debugging settings on as well.
I hear what you are saying and I won't alter or edit my OC configuration. Thank you for your help Sir!

 

[chevyboy60013]

I am debating if I want to attempt this on my late 2011 13 inch MacBook Pro. I successfully installed Catalina, using the patch tool for it, and am very pleased with it and how it works. It runs Catalina like it is a supported model, even though it is not, and runs Catalina much better than my mom's Mac mini which is supported, I may have to look into that for her, it is turtle slow, even just booting up to being usable, and slower than my unsupported MacBook Pro using the same internet network, although hers is plugged into the ethernet cable, which I think in theory should be faster than using the wifi of the same network.

Please let me know if Big Sur would be worth attempting to do, and if it should work reasonably well on my late MacBook Pro 13 inch 8,1 model.

 

[cey27]

I am debating if I want to attempt this on my late 2011 13 inch MacBook Pro. I successfully installed Catalina, using the patch tool for it, and am very pleased with it and how it works. It runs Catalina like it is a supported model, even though it is not, and runs Catalina much better than my mom's Mac mini which is supported, I may have to look into that for her, it is turtle slow, even just booting up to being usable, and slower than my unsupported MacBook Pro using the same internet network, although hers is plugged into the ethernet cable, which I think in theory should be faster than using the wifi of the same network.

Please let me know if Big Sur would be worth attempting to do, and if it should work reasonably well on my late MacBook Pro 13 inch 8,1 model.

I updated my early 2011 MBP 8,1 on Tuesday from Catalina to 11.6.1 and as far as I can tell it works just fine. Performance wise I would say it's about the same as Catalina, however my CPU temperature is on average a lot higher than it was before (therefore the fans go crazy more often). That might be due to some background processes after the upgrade, I really can't tell. Right now when I'm just browsing the web with few programs running in the background CPU temperature is about 65°C.

Only issue I encountered so far is that I can't do PowerPoint presentations because when presenting (mirror view) I get stuck on the current slide with no ability to move forwards or backwards.

 

[chevyboy60013]

basically I would just have to download the Big Sur patch like I did for Catalina then?

 

[cey27]

basically I would just have to download the Big Sur patch like I did for Catalina then?

There is information on that in the first post of this thread. I followed the instructions for the OCLP, and aside from the long installation time for Big Sur, it was a pleasant experience with no problems.

 

[chevyboy60013]

ok

 

[chevyboy60013]

There is information on that in the first post of this thread. I followed the instructions for the OCLP, and aside from the long installation time for Big Sur, it was a pleasant experience with no problems.

so basically I should likely get another usb stick to make the patch tool that way I don't ruin the usb stick with the Catalina patch on it in case Big Sur doesn't want to install?

 

[lbe]

I am running Big Sur on unsupported iMac 21.5 late 2013 and there are some issues related to displaypolicyd:

displaypolicyd.log:

2021-11-06 10:26:29.373035+0100: Started at Sat Nov 6 10:26:29 2021
2021-11-06 10:26:29.378675+0100: ERROR: Policy engine instance init failed
2021-11-06 10:26:29.378779+0100: ERROR: Node active count is 0

system.log:

Nov 6 10:33:40 My-iMac com.apple.xpc.launchd[1] (com.apple.displaypolicyd[804]): Service exited with abnormal code: 1
Nov 6 10:33:40 My-iMac com.apple.xpc.launchd[1] (com.apple.displaypolicyd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Do I need displaypolicyd?
What is displaypolicyd for?

 

[lbe]

I also get this error message:

2021-11-06 13:14:27.126891+0100: PolicyEngine started: 7800020000000000, Time: Sat Nov 6 13:14:27 2021
2021-11-06 13:14:27.127058+0100: NOTICE: kAGDCCallbackCapability: 0x0 []
2021-11-06 13:14:27.127432+0100: ERROR: MULTI_HPD_MST is no longer supported

 

[izfernando]

Hi.
How can I set my MacBookPro9.1 to an MBP11.3 and not eligible to upgrade to Monterey?
I don't want to upgrade to Monterey. Only to the last updates for BigSur.

 

[izfernando]

other question
what is the best version of OCLP to install BIGSUR on macbookpro9,1?
I like the 0.1.9

 

[Ed Hartouni]

Just completed using OCLP 0.3.1 and installed MacOS Big Sur 11.6.1 on my wife's MacBookPro 9,2 (13" mid 2012, A1278)...

there are modifications to the OCLP Terminal User Interface (TUI) menu layout, so if you are use to early versions just take a deep breadth and slow down... but following the general flow of the upgrade gets you to the right place.

This MBP has a metal GPU (Intel HD Graphics 4000) so no additional work had to be done.

There are also some unexpected twists after the system is installed and the machine boots up...

I also haven't figured out why the system waits about 5 seconds and then picks the boot volume, you have to be vigilant when you choose the EFI mount for the first time or you'll boot to the "default disk"...
an annoyance.

The only problem I ran into was trying to do a TimeMachine restore from her previous backup, but more on that elsewhere.

I have to say the the OCLP utility works amazingly well!

thanks to all involved.

 

[Marty56]

I have a MacBook Air 4,2 and OCLP 0.3.1
Is there a way to enable extensions in safari.
Right now clicking on the checkmark does not work.
The outdated extension tool mentioned in the documentation causes the machine to stall.

 

[johnrak]

If I open and close the Music app I can no longer open it. I get this message and I have to reboot my Mac to reopen it.

Does anyone experience anything similar?

Also I checked the SIP status and I get e message about an unsupported configuration. Is this normal? The last time I built OCLP I used the gui version and these are my settings. Are these ok? Should I change anything and or use the tui version?

 

[Ausdauersportler]

If I open and close the Music app I can no longer open it. I get this message and I have to reboot my Mac to reopen it.
View attachment 1904595
Does anyone experience anything similar?

Also I checked the SIP status and I get e message about an unsupported configuration. Is this normal? The last time I built OCLP I used the gui version and these are my settings. Are these ok? Should I change anything and or use the tui version?

View attachment 1904598 View attachment 1904599

Use the TUI to set the SIP status and rewrite OpenCore and reboot. You cannot change it from the recovery as long as you use OpenCore.

About Apple Music check this issue. Revert to 0.2.4 or follow the guide in the description.

SIP has been disabled lately (with 0.2.5 and later) because your iMac would need post install patching on Monterey and there is no way to figure out for OCLP which macOS you are planning to install.

I guess both issues will go away by reverting to an older version, this is not the official line, but 0.2.4 is the last pure Big Sur version. Later a lot of changes came in just to make Monterey working on legacy Macs.

In general there is no need to move on to more recent OCLP version as long as you do not have any problems.

P.S.:
It is always a good idea to read the OCLP release notes before moving on and to check the issues tab on Github (open and closed ones) before posting.

Edit:
Just running the latest OCLP nightly on iMac12,2 with Big Sur 11,5 and Music works pretty well. Might be another moving target.

 

[mwidjaya]

I guess both issues will go away by reverting to an older version, this is not the official line, but 0.2.4 is the last pure Big Sur version. Later a lot of changes came in just to make Monterey work on legacy Macs.

I am using 0.2.5 for Big Sur and it is stable, without Music app crash.

In general there is no need to move on to more recent OCLP version as long as you do not have any problems.

Good point. I also see no reason to move up version, as it is stable.

 

[johnrak]

I'm not planning to try Monterey at the moment so I installed OCLP 0.2.4 TUI. The Music app issue got fixed.
I'm still getting the unsupported configuration message when I run csrutil status
These are the default settings it used to build open OpenCore. Should I change them?

 

[buckrock]

I'm not planning to try Monterey at the moment so I installed OCLP 0.2.4 TUI. The Music app issue got fixed.
I'm still getting the unsupported configuration message when I run csrutil status
These are the default settings it used to build open OpenCore. Should I change them?
View attachment 1904704

Set #11 to both True -- 'csrutil status' then should return 'SIP Status Enabled'. Also you'll need to reset NVRAM with Cmd-Opt-PR at startup.

But, I'm wondering: why not leave SIP and SBM disabled? Lots of us leave the security setting set at the disabled default even if we're not planning to upgrade to Monterey.

Also, I'd recommend updating OCLP to 0.3.1; stay with the Terminal UI. Just sayin' ...
I know: Ausdauersportler just said it is OK to stay with a stable earlier version; but the newer Terminal interface is better in my opinion.

 

[Ausdauersportler]

I'm not planning to try Monterey at the moment so I installed OCLP 0.2.4 TUI. The Music app issue got fixed.
I'm still getting the unsupported configuration message when I run csrutil status
These are the default settings it used to build open OpenCore. Should I change them?
View attachment 1904704

The only change might be enabling SecureBootModel. SIP is currently enabled. You might check the config.plist manually to confirm the correct SIP value 00000000 has been set.

Since your 2011 iMac does not need latebloom or SurPlus there is currently no need to move ahead. On the other hand owners of pre 2011 system should upgrade to 0.2.5 to get around the nasty race condition solved completely by SurPlus.

Never paid too much attention to the csrutil status - but I am constantly patching and testing on the same system. Changing SIP back and forth becomes a pain ….

 

[Ausdauersportler]

Set #11 to both True -- 'csrutil status' then should return 'SIP Status Enabled'. Also you'll need to reset NVRAM with Cmd-Opt-PR at startup.

But, I'm wondering: why not leave SIP and SBM disabled? Lots of us leave the security setting set at the disabled default even if we're not planning to upgrade to Monterey.

Also, I'd recommend updating OCLP to 0.3.1; stay with the Terminal UI. Just sayin' ...
I know: Ausdauersportler just said it is OK to stay with a stable earlier version; but the newer Terminal interface is better in my opinion.

One could check this, not sure if the Apple Music problem has been solved there, too.