macOS 11 Big Sur on Unsupported Macs Thread

[disorderattempt]

Hey everyone, successful installation to iMac 12.2 (mid-2011)
machine was previously upgraded to Kepler GPU (GTX780m).

OCLP 0.5.2 + BigSur 11.7.1 = noSound issue. System did not detect any speakers. Could play sound via BT.
rebuild EFI patcher with older OCLP 0.4.11, voila, sound is back!
#no sound on big sur OCLP imac 12.1

 

[alphascorp]

Hey everyone, successful installation to iMac 12.2 (mid-2011)
machine was previously upgraded to Kepler GPU (GTX780m).

OCLP 0.5.2 + BigSur 11.7.1 = noSound issue. System did not detect any speakers. Could play sound via BT.
rebuild EFI patcher with older OCLP 0.4.11, voila, sound is back!
#no sound on big sur OCLP imac 12.1




View attachment 2125825

Hi @disorderattempt

It seems that AppleALC.kext version 1.7.6 of OCLP 0.5.2 would cause some sound problems on some Macs, either with Big Sur, Monterey or Ventura.

Have you tried replacing AppleALC.kext (v1.7.6) from OCLP 0.5.2 with AppleALC.kext (v1.6.3) from OCLP 0.5.1? (AppleALC.kext is the same version 1.6.3 in OCLP 0.5.1 and in OCLP 0.4.11)

1. Mount EFI. (diskutil list, diskutil mount /dev/diskAs1 (replace diskAs1 with your EFI volume)).
2. Replace only the AppleALC.kext file in the /EFI/OC/Kexts folder.
3. Reboot

 

[Ausdauersportler]

Hi @disorderattempt

It seems that AppleALC.kext version 1.7.6 of OCLP 0.5.2 would cause some sound problems on some Macs, either with Big Sur, Monterey or Ventura.

Have you tried replacing AppleALC.kext (v1.7.6) from OCLP 0.5.2 with AppleALC.kext (v1.6.3) from OCLP 0.5.1? (AppleALC.kext is the same version 1.6.3 in OCLP 0.5.1 and in OCLP 0.4.11)

1. Mount EFI. (diskutil list, diskutil mount /dev/diskAs1 (replace diskAs1 with your EFI volume)).
2. Replace only the AppleALC.kext file in the /EFI/OC/Kexts folder.
3. Reboot

You need to add -lilubetaall to the boot-args in the config.plist when changing the AppleALC.kext from 1.7.6 -> 1.6.3 and using the OLCP 0.5.2 release. AppleALC.kext broke in 1.6.4, but not all iMacs are affected.

 

[disorderattempt]

Hi @disorderattempt

It seems that AppleALC.kext version 1.7.6 of OCLP 0.5.2 would cause some sound problems on some Macs, either with Big Sur, Monterey or Ventura.

Have you tried replacing AppleALC.kext (v1.7.6) from OCLP 0.5.2 with AppleALC.kext (v1.6.3) from OCLP 0.5.1? (AppleALC.kext is the same version 1.6.3 in OCLP 0.5.1 and in OCLP 0.4.11)

1. Mount EFI. (diskutil list, diskutil mount /dev/diskAs1 (replace diskAs1 with your EFI volume)).
2. Replace only the AppleALC.kext file in the /EFI/OC/Kexts folder.
3. Reboot

You need to add -lilubetaall to the boot-args in the config.plist when changing the AppleALC.kext from 1.7.6 -> 1.6.3 and using the OLCP 0.5.2 release. AppleALC.kext broke in 1.6.4, but not all iMacs are affected.

i actually went with earlier OCLP 0.4.11 and it solved sound issue. will alter kext if any malfunction arises in further use.

 

[KevinClark]

Does Someone has an EFI For Macbook pro Mi 2012 i7 2,3 ghz Gt 650 m+ HD 4000 ? works for latest Big Sur

Not OCLP An EFI Like Opencore Martin Lo For Macpro 5.1 Thanks

 

[Sovaboris]

Hi @disorderattempt

It seems that AppleALC.kext version 1.7.6 of OCLP 0.5.2 would cause some sound problems on some Macs, either with Big Sur, Monterey or Ventura.

Have you tried replacing AppleALC.kext (v1.7.6) from OCLP 0.5.2 with AppleALC.kext (v1.6.3) from OCLP 0.5.1? (AppleALC.kext is the same version 1.6.3 in OCLP 0.5.1 and in OCLP 0.4.11)

1. Mount EFI. (diskutil list, diskutil mount /dev/diskAs1 (replace diskAs1 with your EFI volume)).
2. Replace only the AppleALC.kext file in the /EFI/OC/Kexts folder.
3. Reboot

Hello. I have a 2011 imac through opencore installed Big Sur sound does not work. in the settings, the output shows only headphones. Built-in output: Default Output Device: Yes Default System Output Device: Yes Manufacturer: Apple Inc. Output channels: 2 Current sampling rate: 48000 Data transmission: Built-in device Audio output source: Headphones please help


I read what is written above, but to be honest, I don’t understand much. Please help, if it's not difficult for you, write me the procedure. Thank you in advance.

 

[Ausdauersportler]

Hello. I have a 2011 imac through opencore installed Big Sur sound does not work. in the settings, the output shows only headphones. Built-in output: Default Output Device: Yes Default System Output Device: Yes Manufacturer: Apple Inc. Output channels: 2 Current sampling rate: 48000 Data transmission: Built-in device Audio output source: Headphones please help


I read what is written above, but to be honest, I don’t understand much. Please help, if it's not difficult for you, write me the procedure. Thank you in advance.

Jesus, revert to OLCP 0.4.11 - you do not need the latest version for Big Sur.

In other words: Download 0.4.11 app, start it, select build and install OpenCore, after installation reboot into Big Sur, do not touch any settings or patches and check sound. Check the OCLP docs about upgrading (it is downgrading here).

 

[Sovaboris]

Jesus, revert to OLCP 0.4.11 - you do not need the latest version for Big Sur.

In other words: Download 0.4.11 app, start it, select build and install OpenCore, after installation reboot into Big Sur, do not touch any settings or patches and check sound. Check the OCLP docs about upgrading (it is downgrading here) OCLP.

hooray thanks, everything works

 

[hvds]

Hi @disorderattempt

It seems that AppleALC.kext version 1.7.6 of OCLP 0.5.2 would cause some sound problems on some Macs, either with Big Sur, Monterey or Ventura.

Have you tried replacing AppleALC.kext (v1.7.6) from OCLP 0.5.2 with AppleALC.kext (v1.6.3) from OCLP 0.5.1? (AppleALC.kext is the same version 1.6.3 in OCLP 0.5.1 and in OCLP 0.4.11)

1. Mount EFI. (diskutil list, diskutil mount /dev/diskAs1 (replace diskAs1 with your EFI volume)).
2. Replace only the AppleALC.kext file in the /EFI/OC/Kexts folder.
3. Reboot

AppleALC is reverted to 1.6.3 in latest OCLP 0.5.3n, and includes the -lilubetaall in boot-args.
Thanks!

(didn‘t try it yet, just looking at the changelog.
build.py line 45: " -lilubetaall" may need this leading blank?)

 

[Mystere65]

I don't understand what's the point of continuing to update OCLP having Big Sur installed, I'm going with 0.2.4 and everything works fine, including the Music App

 

[KevinClark]

Have you tried to use Record Box and video and typing space bar while play video ?

Do you have bug on the video when typing space bar

 

[alphascorp]

Hi all

11.7.2 (20G1020) successfully installed on Mac Pro

EDIT: I noticed a temperature drop of 3°C on each CPU since macOS 11.7.2 update
respectively 32°C and 36°C for CPU B and CPU A instead of 35°C and 39°C (during idle periods)
The Nothbridge is still at 53°C as before.
I would like to point out that, at idle, the fans are still running at the same speed and the "system ambient" sensor has always indicated between 24°C and 26°C, for a month.

 

[Earl Urley]

I was running Big Sur 11.7.1 on a old Late 2013 rMBP 13-inch, and I had OCLP 0.5.1 installed on it.

Updated to 11.7.2, but now it locks up during the boot thermometer. Can get it to boot if I hold option at boot and pick "Macintosh HD" instead of "EFI Boot." Of course, System Profiler shows the built-in Apple firmware version if I do this.

Will downgrading to OCLP 0.4.11 fix this booting issue? Or did the /EFI partition get corrupted somehow and I have to do a TM backup, then wipe the drive and restore?

 

[mikelets456]

I apologize for asking this again. I have a 2009 Macbook pro and updated to 11.7.1 about a month ago and using the most recent Opencore legacy patcher. Today I see "software update to 11.7.2" available via settings. Can I simply update as if it were a "normal" MacOS? Or do I have to install the full package and install opencore again?

EDIT--Never mind. It appears according to this video that I can install and the Opencore legacy patcher will automatically prompt me to reinstall after the security patch has been updated.

 

[mikelets456]

I'm on 11.7.1 2009 Macbook pro---Apple maps loads but locks up on the "what's new" screen. However, Apple maps does load in the background but I can't get the "what's new" box to close. Thoughts?

EDIT--I updated to 11.7.2 and OCLP 0.5.2 and all is working fine---actually better and smoother than previously.

 

[Earl Urley]

I was running Big Sur 11.7.1 on a old Late 2013 rMBP 13-inch, and I had OCLP 0.5.1 installed on it.

Updated to 11.7.2, but now it locks up during the boot thermometer. Can get it to boot if I hold option at boot and pick "Macintosh HD" instead of "EFI Boot." Of course, System Profiler shows the built-in Apple firmware version if I do this.

Will downgrading to OCLP 0.4.11 fix this booting issue? Or did the /EFI partition get corrupted somehow and I have to do a TM backup, then wipe the drive and restore?

To answer my own question, downgrading to OCLP 0.4.11 cured the boot locking up.

They might want to mention in the docs something about the expected OS support level for each iteration of OCLP...

I'll probably keep it at 0.4.11 until Apple does its usual unannounced random abandonment of an OS level for Big Sur, if no Security Update appears within 4-6 months. So far that hasn't happened, but Big Sur appears ripe for that treatment..

 

[mrbubzie1993]

Well update fixed my own issue…after three installs did a repair disk using disk utility on the primary partition and fixed the issue….weird

 

[ericoud]

Hello,
I installed Big Sur 11.7.2 on my old iMac early 2009 (9.1) which doesn't support metal.
I installed Garageband 10.4.6, but it doesn't run: Graphics initialization impossible...
Looking at the crash log, there is an issue with: MPSImageGaussianBlur
failed assertion `[MPSImageGaussianBlur initWithDevice:] device may not be nil.'
Does someone knows is there is a fix for this issue? I didn't found any information, except that the graphic card NVIDIA GeForce 9400 doesn't support metal... I think that perhaps a workaround exist.
If there is no fix, is there a way to run an older version, the one I had on High Sierra (Garageband 6) doesn't work.

 

[mwidjaya]

is there a way to run an older version

Maybe try 10.2 version, supposedly non-metal, open GL.

Download from here.

https://archive.org/details/garage-band-10.2.0

 

[ericoud]

Maybe try 10.2 version, supposedly non-metal, open GL.

Download from here.

https://archive.org/details/garage-band-10.2.0

Thank you so much, it works on Big Sur (non metal) me after repairing the authorization:
xattr -rd com.apple.quarantine /Applications/GarageBand.app

 

[RetiredInFl]

Hey folks ... MAC newbie here. I skimmed this humonguous thread. Been a "PC GUY" since they first existed although I am a many year iPhone user. Picked up a (obviously) used Late 2012 MAC MINI 6,2, 16GB i7, 2.6GHZ, 500GB SSD, Catalina v10.15.7 for next to nothing and booted it up and liking it.

Anyway, being the bored 75 yr old retired guy that I am I wanted to do the BIG SUR update. Why? No idea but I guess because it is a challenge.

Tried multiple versions of BIG SUR and OPEN CORE both TUI and GUI and all goes fine until the final bootup after booting off the EFI option then to the INSTALL MAC OS ON BIG SUR option and get a couple weird images on the screen flipping back and forth.

Any easy hints on what I may need to change in Open Core? DO I need a specific (tried a couple) version of OPEN CORE or BIG SUR to make this work? I have lots of backups! Attached images of what I get right after I click on INSTALL BIG SUR.

 

[davidlv]

Hey folks ... MAC newbie here. I skimmed this humonguous thread. Been a "PC GUY" since they first existed although I am a many year iPhone user. Picked up a (obviously) used Late 2012 MAC MINI 6,2, 16GB i7, 2.6GHZ, 500GB SSD, Catalina v10.15.7 for next to nothing and booted it up and liking it.

Anyway, being the bored 75 yr old retired guy that I am I wanted to do the BIG SUR update. Why? No idea but I guess because it is a challenge.

Tried multiple versions of BIG SUR and OPEN CORE both TUI and GUI and all goes fine until the final bootup after booting off the EFI option then to the INSTALL MAC OS ON BIG SUR option and get a couple weird images on the screen flipping back and forth.

Any easy hints on what I may need to change in Open Core? DO I need a specific (tried a couple) version of OPEN CORE or BIG SUR to make this work? I have lots of backups! Attached images of what I get right after I click on INSTALL BIG SUR.


View attachment 2130023View attachment 2130024

Those screens are telling you to connect a wired mouse and keyboard. That can happen when the system cannot connect to a bluetooth device. Connect a wired mouse, and try to connect the bluetooth mouse later.

 

[RetiredInFl]

Those screens are telling you to connect a wired mouse and keyboard. That can happen when the system cannot connect to a bluetooth device. Connect a wired mouse, and try to connect the bluetooth mouse later.

Interesting, thanks. I did have a wired keyboard attached so I was able tab to the proper boot icon but no wired mouse. Haven't seen one of them in years! Maybe I can find one in a $1 (I mean $1.25) store here in the boondocks of FL. or of course there is always Amazon.

Edit: It was a PC keyboard if that matters.

 

[RetiredInFl]

Those screens are telling you to connect a wired mouse and keyboard. That can happen when the system cannot connect to a bluetooth device. Connect a wired mouse, and try to connect the bluetooth mouse later.

@davidlv
That was it! Thank you! Hours wasted. LOL. $4 wired mouse solved it. Now running Ventura on a Mac Mini 2012 i7 Quad 2.6Ghz w/16gig ram & 500gig SSD. OpenCorePatcher (GUI) is amazing.

 

[Earl Urley]

So I was able to convert a wheezing old unmodified iMac 11,3 (Mid-2010) from High Sierra to Big Sur 11.7.2.

Luckily it had 16 GB of RAM and a 1 TB drive, bad news is that it's an old Terascale GPU and a platter drive, and the dual core CPU instead of the quad core (uggh), so the upgrade took roughly four hours..

Still have to check to see if it does HTTP 5 streams properly but hey it boots Big Sur on a 12 year old machine!

Next project will be to swap out the platter drive for an SSD.. yeah yeah it's not going to be a huge speed jump going to a SATA SSD but the platter drive feels like it's on it's way out after a long life.