macOS 11 Big Sur on Unsupported Macs Thread

[justperry]

One thing I want to do soon is to take a closer look at the WiFi patch and see if there's anything I can do to make it less buggy. (It has had bugs to varying degrees with all of the Big Sur betas.) I have ideas but I need to implement and test before I promise anything.

I probably won't get a chance to look into it until a week from now, but we'll see...

Thanks Barry.
My Mac has a wired connection, Wifi is just for fallback, no biggie for me, your help is much appreciated, plenty of others have no wired option.

 

[Barry K. Nathan]

@Barry K. Nathan the version 17 of ur patcher may works on public beta 4? when I used the 17 one on BS3 my wifi buttons and keylight buttons works good, but now work buggy....

Is "wifi buttons" the WiFi on/off button in the WiFi menu, and "keylight buttons" the keyboard backlight brightness keys on the keyboard? If so (for "keylight buttons"), I think you may be the second person to complain about those not working (the first person filed a GitHub issue, but they had the problem under beta 3 as well).

v0.0.17 should work with beta 4, but it's missing the fix for the camera/microphone permission problem that you reported. (If you redo step 6 of the README using v0.0.19 that'll fix the camera/microphone permission problem, no need to redo anything else with v0.0.19.)

 

[Ronald Steven]

Is "wifi buttons" the WiFi on/off button in the WiFi menu, and "keylight buttons" the keyboard backlight brightness keys on the keyboard? If so (for "keylight buttons"), I think you may be the second person to complain about those not working (the first person filed a GitHub issue, but they had the problem under beta 3 as well).

v0.0.17 should work with beta 4, but it's missing the fix for the camera/microphone permission problem that you reported. (If you redo step 6 of the README using v0.0.19 that'll fix the camera/microphone permission problem, no need to redo anything else with v0.0.19.)

yes, all buttons in the menu, but in beta 3 all menu works good. and now it doesn´t turn on/off wifi networks or blacklight brightness

 

[Barry K. Nathan]

I have tried to send from BigSur beta 4 Terminal and Recovery (via OpenCoreLoader4)
nvram boot-args="-no_compat_check" (csrutil status is disabled)
everytime it returned: nvram: error setting variable -'boot-args': (iokit/common) general error.

This question may seem randon, but do any of the macOS installations on your Mac have FileVault enabled?

 

[Alex-Microsmeta]

This question may seem randon, but do any of the macOS installations on your Mac have FileVault enabled?

no... mystery continues!

 

[Barry K. Nathan]

no... mystery continues!

That is very useful information. That's actually the second report I've heard of a 2010 Mac being unable to change boot-args in nvram using Big Sur. (The first report was via Discord, and did not involve OpenCore, but there were macOS installations with FileVault enabled.)

 

[Barry K. Nathan]

yes, all buttons in the menu, but in beta 3 all menu works good. and now it doesn´t turn on/off wifi networks or blacklight brightness

Do the keys on the keyboard (I believe it's the same keys as F5 and F6) work for keyboard backlight brightness? If so, that would be a workaround for now. If not, I need to know about it.

By the way, just so I know in more detail what kind of Mac you have, would you mind running this command in Terminal and letting me know the output? sysctl -n hw.model

 

[Alex-Microsmeta]

from BigSur normal booting it's: sudo nvram boot-args="-no_compat_check"

anyway you don't need because it's already disabled from USBopencore , to skip the stage3 installer or fix the snapshot booting you need to use an USB BigSur Installer with createinstallmedia, then apply: https://github.com/barrykn/big-sur-micropatcher

or this: BigSur BaseSystem legacy USB fix

sudo tried unsuccesfully There is no "BigSur - Data" option for external drive on startup disk in Preferences Panel, only for the Beta 3 installed on internal SSD. I can only chose "BigSur" and only from "BigSur beta3", it is prohibited from Catalina, so I have setted it and I'm continuing the installation to verify if enabling nvram boot-args="-no_compat_check" from dosdude1 Catalina Patcher has changed something. If not, I will retry tomorrow with @Barry K. Nathan micropatcher.

 

[Alex-Microsmeta]

Hello Alex-Microsmeta,

Just curious how you got SIRI to work. Siri crashes on launch on my installation (MacBook Pro 5,2 C2D Penryn), while everything else you listed works (in addition, internal sound and mic work perfectly). There is no graphic acceleration available.

I'm reinstalling it from scratch, I will report to you tomorrow

 

[amaze1499]

To fix "BIerrorDomain Error 3" you need to apply the ASentientBot Hax3 HaxLib.dylib, and to apply a dylib without apple signature you need "amfi_get_out_of_my_way=1" in nvram (or on com.apple.Boot.plist) .

Maybe try this that should apply both to an USB BigSur Installer: BigSur BaseSystem legacy USB fix

For your Mac that is an Ivy Bridge, you don't need USBopencore .

Oh thank you so,much! That did it! I did apply the legacy USB fixes in the wrong order.

 

[Barry K. Nathan]

sudo tried unsuccesfully There is no "BigSur - Data" option for external drive on startup disk in Preferences Panel, only for the Beta 3 installed on internal SSD. I can only chose "BigSur" and only from "BigSur beta3", it is prohibited from Catalina, so I have setted it and I'm continuing the installation to verify if enabling nvram boot-args="-no_compat_check" from dosdude1 Catalina Patcher has changed something. If not, I will retry tomorrow with @Barry K. Nathan micropatcher.

There are inaccuracies in the micropatcher README regarding some 2010 Macs. So try the following: Try creating, patching, booting the USB as if you were using a 2011 or later Mac. After the installer USB boots, see if the keyboard and mouse are working. If they are, proceed as if you were using a 2011 Mac, with two exceptions:

1. If step 6 (with set-vars.sh) produces the same nvram error, then run nvram csr-active-config and make sure it's set to w%08%00%00 (or w%09%00%00, that's also OK). If it's anything else, boot into Mavericks or earlier (holding Shift-Option-Command-R at boot should boot Lion from Internet Recovery) and do the 2 commands listed in step 13, then boot back into the Big Sur installer, pick up with step 6 again (ignore the errors this time) and continue.
2. If you get to step 9, use --all instead of --2011.

If the keyboard and mouse do not work once you boot from the patched installer USB, then I'll have to do more work on the patcher before it'll work on your Mac Mini, but there's a good chance the keyboard and mouse will work, so if you try the micropatcher, I'd like to know how things go.

 

[ethanhodges]

Is it possible to go from Beta 3 to Public Beta without patching it?

 

[Ronald Steven]

Do the keys on the keyboard (I believe it's the same keys as F5 and F6) work for keyboard backlight brightness? If so, that would be a workaround for now. If not, I need to know about it.

By the way, just so I know in more detail what kind of Mac you have, would you mind running this command in Terminal and letting me know the output? sysctl -n hw.model

@Barry K. Nathan Keys are F5 - F6 work normally. That’s ok.

My model is MabookPro 9,2.

I installed public beta 4 with patcher 0.019 and the bug button continius ?

 

[saltyboat]

Does anyone have any guess how long it will be until DosDude releases a patcher? or if he ever will?

 

[Ronald Steven]

@Barry K. Nathan The backlight brightness keys work perfectly.

Model MacbookPro9,2

i had installed public beta 4 and the button’s bug continues and I forgot to say that in picture profile all pictures doesn’t appears I have to select it randomly and the Boot disk’s name is “Efiboot” and the name that i put before install was “BigSur” ??‍♂️

 

[maxsp97]

cMP 5,1 mid 2012 successfully installed Big Sur Beta 4 with Barry big sur micropatcher 0.0.19.
With upgraded Apple WiFi 802.11ac Bluetooth 4.2, WIFI/BT and AirDrop are working.

Thank you Barry K. Nathan, ASentienBot and jackluke

 

[Barry K. Nathan]

Is it possible to go from Beta 3 to Public Beta without patching it?

If you had to patch Beta 3 to install it in the first place, you need to patch the Public Beta to do the update. (There may be some very obscure exceptions to this, but I believe it's true in the general case.)

@Barry K. Nathan The backlight brightness keys work perfectly.

Model MacbookPro9,2

i had installed public beta 4 and the button’s bug continues and I forgot to say that in picture profile all pictures doesn’t appears I have to select it randomly and the Boot disk’s name is “Efiboot” and the name that i put before install was “BigSur” ??‍♂️

Wow, that is strange that the profile pictures aren't showing up. Eventually I'll have a supported Mac (it might not arrive until next week), then I can see if it happens there too. (For what it's worth, this isn't happening on my MacBookPro8,1.) Possible workarounds might include the tricks that improve things on non-Metal Macs (even though your Mac has Metal): Dark mode and/or Reduce Transparency (so you could try those and see if you still have the problem).

 

[Ronald Steven]

If you had to patch Beta 3 to install it in the first place, you need to patch the Public Beta to do the update. (There may be some very obscure exceptions to this, but I believe it's true in the general case.)


Wow, that is strange that the profile pictures aren't showing up. Eventually I'll have a supported Mac (it might not arrive until next week), then I can see if it happens there too. (For what it's worth, this isn't happening on my MacBookPro8,1.) Possible workarounds might include the tricks that improve things on non-Metal Macs (even though your Mac has Metal): Dark mode and/or Reduce Transparency (so you could try those and see if you still have the problem).

I’ll will try something, thanks

 

[Ronald Steven]

is there some option to install a unsealed disk Big Sur beta4 for unsopported Macs?

 

[Barry K. Nathan]

is there some option to install a unsealed disk Big Sur beta4 for unsopported Macs?

My patcher installs unsealed by default, unless you add the --seal command line option to set-vars.sh in step 6. If you previously used Hax.dylib, which did not disable sealing, then I don't think there's any way to get rid of the "sealed" attribute without deleting and recreating the APFS volume. (You can use the mount command to see if your Big Sur system volume was ever sealed.)

Keep in mind, just installing unsealed isn't enough to allow mount -uw / to work, if that's what you're after.

If you're trying to install without snapshot booting, that's possible but tricky. In about a week (maybe less, but assume a week) I'll have a couple of helper shell scripts which I think will make life with snapshot booting much easier. (They won't disable snapshot booting, and they won't allow 'mount -uw /' to work with snapshot booting, but I think they'll make it easy to modify the system volume.)

 

[Ronald Steven]

My patcher installs unsealed by default, unless you add the --seal command line option to set-vars.sh in step 6. If you previously used Hax.dylib, which did not disable sealing, then I don't think there's any way to get rid of the "sealed" attribute without deleting and recreating the APFS volume. (You can use the mount command to see if your Big Sur system volume was ever sealed.)

Keep in mind, just installing unsealed isn't enough to allow mount -uw / to work, if that's what you're after.

If you're trying to install without snapshot booting, that's possible but tricky. In about a week (maybe less, but assume a week) I'll have a couple of helper shell scripts which I think will make life with snapshot booting much easier. (They won't disable snapshot booting, and they won't allow 'mount -uw /' to work with snapshot booting, but I think they'll make it easy to modify the system volume.)

that it will be great! thanks for your effort! I think return to beta 3, and be waiting for ur scripts. Good luck with that @Barry K. Nathan !

 

[RogueB]

Are you doing fresh installs? Or did you try upgrading a Catalina? I know when I tried to upgrade a Catalina drive to Big Sur I had all kinds of weird issues.

I installed Big Sur directly on a new partition; no other operating system previously occupied that partition.

The cause of global SIRI crashes goes beyond installing Big Sur over another version of the operating system.
See jackluke's response, (to my query about SIRI) in post #2888, above this entry

 

[RogueB]

Siri.app (CoreServices and Applications) since BigSur beta 3 doesn't work more on non-metal because they changed the animation, I guess its frameworks are based on Metal (as Drift screensaver for example) .

Yes, that is my understanding as well. I do believe you postulated this basis for SIRI disfunction in previous post.

 

[kral84]

If you're using a 2011 Mac, beta 4 is going to break Ethernet again and my patcher doesn't properly handle it yet. I'll try to do a v0.0.19 release tonight to fix this. (I might not be able to get it done until tomorrow evening, but I'll try to get it done tonight.)

@Barry K. Nathan have you fix the ethernet problem my.friend if yes i would try upgrade to.beta 4 to test it...thx

 

[Barry K. Nathan]

@Barry K. Nathan have you fix the ethernet problem my.friend if yes i would try upgrade to.beta 4 to test it...thx

My initial attempt to fix it actually did the opposite and made Ethernet completely stop working. I need more time to look into it.