macOS 11 Big Sur on Unsupported Macs Thread

[thatsmeonlyme]

THANKS !!!!, YouTube is working fine now. Still stuck with the booting time. I think its something to do with snapshots or mounting volumes.

The long booting time is a known old problem depending on TRIM. Have a look whether Trim is enabled. If not you should enable it. During restart pess option key. when in the boot option go to your boot drive pressing ctrl and click the mouse on it. booting time should be faster then.

 

[Ausdauersportler]

I guess your issues are instead due to a reset of "AMFI or SIP enabled" (especially if you use Opencore those variables reset often) and your patched AppleGraphicsControl kext with its plugins incompatible with kernelcollections (I'd exclude CoreBrightness), anyway if patched CoreBrightness caused issues don't use it, my post was just to point that frameworks exec patching is still feasible also without extracting the BigSur dyld shared cache. Because essentially when are required patched frameworks, the previous macOS exec are used, as with kext, they are almost all from HighSierra (and Mojave).

To remove a patched framework on BigSur, is suffice to remove its exec on /Versions/A/ folder (so the dyld shared cache one is used), if you have working sudo mount -uw / simply replacing it (from another macOS or recovery because frameworks exec are constantly in use by macOS) at next reboot will work, with snapshot booting instead you have to create a new snapshot with replaced framework and possibly rebuild at least BootKernelExtensions.kc to tag the new snapshot for UUID matching with Preboot.

The first thing I checked were the NVRAM settings, both with and without OpenCore. And yes, of course your patched CoreBrightness framework works really great with my other machines. I will give it another try later on.

The High Sierra AppleGVA.framework including all the AppleIntelHD3000* and AppleIntelSNB* I had checked from Beta 3 on until Beta 10 completely, but I missed the recent change in the Micro Patcher.

 

[Mark Meretz]

No Bundle in S/L/E and Big Sur boot fine.....

 

[Ausdauersportler]

No Bundle in S/L/E and Big Sur boot fine.....

Have all the files installed as I did it several times before (these are unchanged from the Catalina patching of this 2011 iMac with a Metal GPU), system boots fine, but still no H.264.

I will change the iMac patch part to provide all these files. We need (probably) all of them to have the system sleeping. Before I assumed the complete set will be installed just by the selection of the 2011 model....

 

[Barry K. Nathan]

The Safari error can be solved:
Go to Safari preferences, enable developer in the menu bar. under experimental features disable V9 decoder. Restart Safari and youtube should be working again.

Yes, this is the correct workaround for the YouTube problems in Safari. It's a Big Sur beta 10 bug that also affects supported Macs.

 

[MacHacJac]

I guess I patched the HighSierra AppleGVA.framework to use it on BigSur, maybe @Ausdauersportler could try it, since currently I cannot test it on an IntelHD3000 GPU .

The attached for beta10 should be replaced here: /System/Library/PrivateFrameworks/

To replace this framework follow the conditions I wrote on previous post, but mainly requirements are: AMFI disabled, csrutil disable, with sudo mount -uw / replacing the framework is much easier, but also with snapshot booting can replace it from a BigSur macOS Installer then make a new snapshot with framework replaced (as when replace kext).

I can test it if you'd like on my 2011 13" MBP if you still need it tested.

 

[akki_nd]

The long booting time is a known old problem depending on TRIM. Have a look whether Trim is enabled. If not you should enable it. During restart pess option key. when in the boot option go to your boot drive pressing ctrl and click the mouse on it. booting time should be faster then.

Trim is already enabled, and when I checked in verbose mode
"apfs_vfsop_mount:2197:disk2s1:0 mounted volume: APPLE SSD-Data" is taking maximum time..
Thanks.

 

[Alex-Microsmeta]

Yes, this is the correct workaround for the YouTube problems in Safari. It's a Big Sur beta 10 bug that also affects supported Macs.

On iMac 2013 works without the need of a workaround

 

[eminemmm]

First, make sure you've done a Time Machine backup, as I've mentioned in a few previous posts.

Next, try doing the following:

Boot from the patched installer USB. Open Terminal. Then run the following commands:

cd /Volumes
mount -uw "Volume Name" (such as "MY KINGSTON SSD" or "Macintosh HD" or whatever your Big Sur volume is)
cd "Volume Name"
cd System/Library
mv Extensions Extensions.old

Then quit Terminal, start the Installer, and reinstall Big Sur. See if you're able to make WiFi and Ethernet work afterward.

tried but nothing worked

 

[hvds]

CoreBrightness.framework (and nightshift with it) also working on MBP5,2 with BS beta10. *

Many things in good shape on this legacy USB machine.

I had the problem of Photos.app crashing with all BS betas, but I had always used migration assistant to populate it with all my photos from Catalina. There seem to be one or more with problematic data among them. Without migration (just importing quite a few photos from iPhone) no problems.

* patch-kexts.sh is so well structured that I didn't replace CoreBrightness manually, but found it easier to make a small temporary change/addition to micropatcher 0.4.3 instead.

Thanks Barry K. Nathan and jackluke!

Two small scratches to this picture of BS beta10 on MBP5,2:

1 - while system information shows that USB mouse or keyboard are connected, system settings don't, and the devices don't react. OK in BS public beta 1. The same for on-board USB or USB3 of nanotech expresscard.

EDIT: USB mouse and keyboard work in beta10 after booting with CMDS+S/exit as seen earlier by alex-microsmeta.

2 - patched CoreBrightness.framework needs amfi_get_out_of_my_way=1 in boot-args, otherwise booting hangs. Reverted to unpatched one without problem (again via patching-over with patch-kexts.sh), to verify that booting is normal again.
Then went again to patched one for convenience of night shift.

Ausdauersportler had reported this already, I didn't notice it earlier as amfi setting was in place.

For me these are minor points which may still be cured. Thanks again to all!

 

[jackluke]

1 - while system information shows that USB mouse or keyboard are connected, system settings don't, and the devices don't react. OK in BS public beta 1. The same for on-board USB or USB3 of nanotech expresscard.

EDIT: USB mouse and keyboard work in beta10 after booting with CMDS+S/exit as seen earlier by alex-microsmeta.

2 - patched CoreBrightness.framework needs amfi_get_out_of_my_way=1 in boot-args, otherwise booting hangs. Reverted to unpatched one without problem (again via patching-over with patch-kexts.sh), booting normal again (no night shift of course).

About the issue of USB mouse and keyboard non responsive, it's not due to my patched CoreBrightness, rather to LegacyUSBInjector.kext that on BigSur for Nvidia MCP79 and MCP89 Chipset for more working reliability requires CMD+S and exit.

About using patched frameworks and amfi, through this ASentientBot plist (a kind of amfi partially enabled to keep TCC.db stock and works also directly from snapshot booting desktop):

sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true

then you can clear the nvram boot arg for amfi (but SIP disabled is still required for patched frameworks), meanwhile I updated to 10.15.7 the patched CoreBrightness (pikeralpha method) aligning with BigSur beta10 Info plist, so maybe use this attached if you need night shift displays on BigSur non Metal GPU.

 

[hvds]

About the issue of USB mouse and keyboard non responsive, it's not due to my patched CoreBrightness, rather to LegacyUSBInjector.kext that on BigSur for Nvidia MCP79 and MCP89 Chipset for more working reliability requires CMD+S and exit.

About using patched frameworks and amfi, through this ASentientBot plist (a kind of amfi partially enabled to keep TCC.db stock and works also directly from snapshot booting desktop):

sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true

then you can clear the nvram boot arg for amfi (but SIP disabled is still required for patched frameworks), meanwhile I updated to 10.15.7 the patched CoreBrightness (pikeralpha method) aligning with BigSur beta10 Info plist, so maybe use this attached if you need night shift displays on BigSur non Metal GPU.

Thanks @jackluke , I had forgotten about the com.apple.security.libraryvalidation.plist which is routinely used in patched Catalina. Sorry, my fault. I'll try it right away, and also your new patched CoreBrightness.framework.


EDIT: that worked well, booting OK without amfi in nvram.
Your new patched framework and the libraryvalidation.plist are in place on my BS beta10 (USB SSD).
I've left this again to the patch-kexts.sh machinery, very convenient!
(for info to @Barry K. Nathan and @Ausdauersportler , appended is the minimally modified script I'm using temporarily (two places labeled hvds), together with the files used from micropatcher, with extra folders PrivateFrameworks and Preferences)

The existing libraryvalidation.plist (I took it from 10.15.7) and one freshly made in BS beta10 (defaults write...) are identical.

Just as a reminder, my BS USB installer is a hybrid based on createinstallmedia of beta10, patched with jackluke's BigSur BaseSystem legacy usb fix b9, and the patch-kexts part of Barry's micropatcher 0.4.3 for post-install patching.

 

[jackluke]

First, make sure you've done a Time Machine backup, as I've mentioned in a few previous posts.

Next, try doing the following:

Boot from the patched installer USB. Open Terminal. Then run the following commands:

cd /Volumes
mount -uw "Volume Name" (such as "MY KINGSTON SSD" or "Macintosh HD" or whatever your Big Sur volume is)
cd "Volume Name"
cd System/Library
mv Extensions Extensions.old

Then quit Terminal, start the Installer, and reinstall Big Sur. See if you're able to make WiFi and Ethernet work afterward.

As you know from BigSur many core kext (example Wifi and Sound) to load after a new snapshot requires not only BKE but also SKE updated, so they are included on both kernelcollections, but apart this, from the user output seems that is using a dual GPU Mac with AMD GPU and IntelHD3000 , SKE can't complete to update because needs this AMDRadeonX3000.kext (stock on HighSierra but not on Mojave).

When the Sandy Bridge Mac has only IntelHD3000 GPU your BKE and SKE worked without issues, instead probably with a dual non Metal GPUs, the kmutil tries to rebuild the kernelcollection using the main hardware GPU in that case AMD Video card, so I guess is triggered when some IntelHD3000 kext are added to kernelcollections.

Hence to let rebuild SKE.kc for install patched "Wifi and Sound", I'd try to don't install IntelHD3000 kext on a dual GPU non Metal with an AMD video card, or maybe installing but also with HighSierra AMDRadeonX3000.kext (and its related dependencies kext bundles).

 

[akki_nd]

If someone can look at the screenshots and suggest something, I think I am missing something.

 

[jackluke]

Trim is already enabled, and when I checked in verbose mode
"apfs_vfsop_mount:2197:disk2s1:0 mounted volume: APPLE SSD-Data" is taking maximum time..
Thanks.

I guess it's the SSD vendor controller (or its NAND flash chip) a bit incompatible with APFS dual filesystem (snapshot booting), BigSur drivers or machine internal AHCI.

 

[Enthuser]

Hi, Sorry, I've been trying to get Audio over HDMI on a GTX680 in a cMP 5,1 2010 on Catalina 10.15.7 without success. I am using A DisplayPort to HDMI cable (Also tried HDMI direct) Having tried to get HDMIAUDIO 1.1 installed via kext as per this site. Should I persevere or will the patcher (I've used Dosdude 1's all this time) for Big Sur deal with this as well?? any help would be greatly appreciated and you have helped in so many other ways before.

 

[MacHacJac]

I've been talking to someone on discord about patching basesystem.dmg with a post-install app on Big Sur. They mentioned duplicating the base system, patching the duplicate, and deleting the original. Has anyone tried this yet in Big Sur, or am I just behind? If not, I'm gonna try this out and see if I can get an app into the basesystem.dmg

 

[jackluke]

I've been talking to someone on discord about patching basesystem.dmg with a post-install app on Big Sur. They mentioned duplicating the base system, patching the duplicate, and deleting the original. Has anyone tried this yet in Big Sur, or am I just behind? If not, I'm gonna try this out and see if I can get an app into the basesystem.dmg

I also attempted to add apps there and if you read my earlier posts, editing Utilities.plist you can point any app exec, but AppleScript converted app won't work, because osascript doesn't work from BigSur Recovery, so you should check that your builded apps are independent and also that launch from BigSur normal booting, because since frameworks are in dyld shared cache you can't add easily frameworks to a BaseSystem to support a third party app, otherwise you should use script apps that are essentially bash script with chmod 755.

Moreover I noticed that is even possible to boot a patched BaseSystem with its stock BootKernelExtensions.kc (but for legacy USB Mac only prelinkedkernel), the main condition is SIP with value 0xFFF or ASentientBot patched 0xfff boot.efi that allows any patched BaseSystem booting without kp verification.

 

[thatsmeonlyme]

I've been talking to someone on discord about patching basesystem.dmg with a post-install app on Big Sur. They mentioned duplicating the base system, patching the duplicate, and deleting the original. Has anyone tried this yet in Big Sur, or am I just behind? If not, I'm gonna try this out and see if I can get an app into the basesystem.dmg

[automerge]1603563055[/automerge]

Hi, Sorry, I've been trying to get Audio over HDMI on a GTX680 in a cMP 5,1 2010 on Catalina 10.15.7 without success. I am using A DisplayPort to HDMI cable (Also tried HDMI direct) Having tried to get HDMIAUDIO 1.1 installed via kext as per this site. Should I persevere or will the patcher (I've used Dosdude 1's all this time) for Big Sur deal with this as well?? any help would be greatly appreciated and you have helped in so many other ways before.

As far as I know it is only working not this way. I myself got Audio working using the original line out. I´m not sure but I think mini display port does not support audio output.

 

[Ausdauersportler]

About the issue of USB mouse and keyboard non responsive, it's not due to my patched CoreBrightness, rather to LegacyUSBInjector.kext that on BigSur for Nvidia MCP79 and MCP89 Chipset for more working reliability requires CMD+S and exit.

About using patched frameworks and amfi, through this ASentientBot plist (a kind of amfi partially enabled to keep TCC.db stock and works also directly from snapshot booting desktop):

sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true

then you can clear the nvram boot arg for amfi (but SIP disabled is still required for patched frameworks), meanwhile I updated to 10.15.7 the patched CoreBrightness (pikeralpha method) aligning with BigSur beta10 Info plist, so maybe use this attached if you need night shift displays on BigSur non Metal GPU.

What can I say, you were right, as always.

After polishing the config.plist to set boot-args and the csr-active-config correctly the CoreBrightness.framework is running fine on my AMD Polaris based iMac 2011, too.

 

[Barry K. Nathan]

I've just released Big Sur Micropatcher v0.4.4. Release notes:

This release is basically a grab bag of bug fixes and under-the-hood improvements. There will be at least one more release in the next few days, so most existing users do not need to update to this release. (If you use remount-sysvol.sh or you are experimenting with kext patches beyond what patch-kexts.sh normally does, I would suggest updating, however.)

[automerge]1603601259[/automerge]

About the issue of USB mouse and keyboard non responsive, it's not due to my patched CoreBrightness, rather to LegacyUSBInjector.kext that on BigSur for Nvidia MCP79 and MCP89 Chipset for more working reliability requires CMD+S and exit.

I believe it's a problem with IOHIDFamily.kext not LegacyUSBInjector.kext. In the next day or two I should have a v0.4.5pre ready for testing with a patch, and I'll post again when that's ready. (cc @Alex-Microsmeta @hvds)

 

[Barry K. Nathan]

As you know from BigSur many core kext (example Wifi and Sound) to load after a new snapshot requires not only BKE but also SKE updated, so they are included on both kernelcollections, but apart this, from the user output seems that is using a dual GPU Mac with AMD GPU and IntelHD3000 , SKE can't complete to update because needs this AMDRadeonX3000.kext (stock on HighSierra but not on Mojave).

Look at @eminemmm's previous posts. It's a 13" 2011 MacBook Pro. It's HD 3000 only. It's not a dual GPU machine.

Somehow it's having trouble removing the kexts that are left over from the dosdude Catalina patcher's Legacy GPU Patch, and that's why kmutil is failing.

@eminemmm I have another set of instructions to try. I'm having trouble figuring out how my previous instructions would not have worked, but try this before I suggest anything more drastic.

First, make sure you've done a Time Machine backup, as I've mentioned in a few previous posts.

Next, try doing the following:

Boot from the patched installer USB. Open Terminal. Then run the following commands:

cd /Volumes
mount -uw "Volume Name" (such as "MY KINGSTON SSD" or "Macintosh HD" or whatever your Big Sur volume is)
cd "Volume Name"
cd System/Library
rm -rf Extensions
rm -rf Extensions.old

Then quit Terminal, start the Installer, and reinstall Big Sur. See if you're able to make WiFi and Ethernet work afterward.

 

[jackluke]

I believe it's a problem with IOHIDFamily.kext not LegacyUSBInjector.kext. In the next day or two I should have a v0.4.5pre ready for testing with a patch, and I'll post again when that's ready. (cc @Alex-Microsmeta @hvds)

During early Catalina beta ASentientBot patched IOHIDFamily.kext to make a kind of automatic exited single user mode, then on next Catalina beta apple weirdly fixed it to work without that patch.

When you install the LegacyUSBInjector.kext as --bundle-path on BKE, does iSight webcam work ?

Because I get kp on later booting when use bundle path for Legacy USB Injector and Video Support .

I guess that kp is due to LegacyUSBVideoSupport.kext (so I removed) while non working iSight to video framebuffer kext loaded, because seems without those kext (using basic graphics kext as safe mode) on BKE (and SKE) the internal webcam worked for Legacy USB Mac .

 

[Mark Meretz]

cool, thank you for your update and you have included the HD3000 bundle, had to add 2 lines in the kext-patch.sh now are as there and still do not put an H264

 

[Comicbooklovers]

Hi!!!
I installed Big Sur on my Unsupported Imac 2013, and would like to know if there is anyway I can Update it.

THANKS!!!