Jump to content

[Release] macOS Big Sur 11.2-11.2.1-11.2.2-11.2.3

gengik84

By gengik84,
in New Releases and Updates

 Share
110 posts in this topic

Recommended Posts

XanthraX
XanthraX
Posted
Posted

Opencore > NVRAM > Add > 7C436110... csr-active-config.... 00000000 - SIP completely enabled (0x0);

30000000 - Allow unsigned kexts and writing to protected system file locations;

67000000 - SIP completely disabled

 

Software update is offered only with SIP completely enabled.

  • Like 1
Avery B
Avery B
Posted
Posted

@ellaosx likely a panic of some sorts. When you open up everything again, there should be another prompt that says "Your computer shut down because of a problem" which the option to view a log. It may be that you have some sort of panic which occurs only at shutdown.

Riley Freeman
Riley Freeman
Posted
Posted (edited)
On 3/2/2021 at 6:00 AM, ellaosx said:

Does anyone having issue like this everytime i start/restart big sur?

Pressing Open doesnt show anything.

20210223_083317.thumb.jpg.d77eae9df934656e97f6890461a88f29.jpg

 

It's FakeSMC. Or to be more specific one of the keys it injects (MSSD, which stores the shutdown state). The value FakeSMC injects works ok with Clover but not OpenCore.

 

Edit the info.plist and delete that key.

Edited by Riley Freeman
iCanaro
iCanaro
Posted
Posted
6 hours ago, Riley Freeman said:

 

It's FakeSMC. Or to be more specific one of the keys it injects (MSSD, which stores the shutdown state). The value FakeSMC injects works ok with Clover but not OpenCore.

 

Edit the info.plist and delete that key.

does the same thing with Clover

18 minutes ago, ellaosx said:

I am using latest clover & fakesmc of slice. All the kext are latest too. I only even installed fakesmc, lilu & whatevergreen for a test, but same issue.

you'll have to use VirtualSMC for a while or resist and wait for this little bug to be fixed

i'd reported this bug to @Slice

https://www.insanelymac.com/forum/topic/299861-hwsensors3/?do=findComment&comment=2751416

 

LockDown
LockDown
Posted
Posted (edited)
8 hours ago, Riley Freeman said:

 

It's FakeSMC. Or to be more specific one of the keys it injects (MSSD, which stores the shutdown state). The value FakeSMC injects works ok with Clover but not OpenCore.

 

Edit the info.plist and delete that key.

 

2 hours ago, iCanaro said:

you'll have to use VirtualSMC

 

Both suggestions worked :thumbsup_anim:

Thank You @Riley Freeman and @iCanaro

Edited by ellaosx
  • Like 1
  • Thanks 2
Riley Freeman
Riley Freeman
Posted
Posted
18 hours ago, ellaosx said:

@Riley Freeman

I am using latest clover & fakesmc of slice.

 

18 hours ago, iCanaro said:

does the same thing with Clover

 

Thanks for the corrections. I thought I read somewhere that the issue didn't affect Clover but I might have picked it up wrong. Using OC and VirtualSMC here.

iCanaro
iCanaro
Posted
Posted

Question: Does anyone have the ASM1042 USB controller working with big sur on their hack??? If you how did you do it?

 

 

@Riley Freeman the advice to remove from the fakesmc plist the MSSD entry looks like it solves 

 

:thanks_speechbubble:

  • Like 1
iCanaro
iCanaro
Posted
Posted
18 hours ago, iCanaro said:

Question: Does anyone have the ASM1042 USB controller working with big sur on their hack??? If you how did you do it?

 

fixed the problem at the root, inserted into the Z68 PCI card to have additional USB 3.0, OOB operation

https://www.amazon.it/gp/product/B00JEVLEFQ/

now 2 usb 3.0 rear ports and the 2 front of the case fully functional with all OS :thumbsup_anim:

HenryV
HenryV
Posted
Posted (edited)

Since these posts show updates, I am looking for some pointers as to why updates are not showing in Big Sur system preferences.

 

Csrutil enable and csrutil authenticated-root enable in recovery console modifies NVRAM csr-active-config in config.plist to 10000000 and booting is enabled but no updates.

 

Cannot boot Big Sur with SIP completely enabled 00000000 in config.plist due to kernel panic.

 

Any specific pointers as to where and what to look for with boot args set to:

no_compat_check  keepsyms=1 -lilubetaall -v debug=0x100 lapic_dont_panic=1

 

What specific log files to look at?

What specific boot files to look at?

 

 

 

 

Edited by HenryV
typo
  • Like 1
Vyzantion
Vyzantion
Posted
Posted (edited)

You know, I was ready a few hours ago to make a joke about Apple releasing the 11.2.3 update tonight, but I thought it would have been a little mean... But here we are, it seems I was right.

Unlike 11.2.1 and 11.2.2, at least the published the full installer at once, I can download it from Apple via Gibmacos tonight. After I re-create the installation usb drive with 11.2.3 , since I would probably not be able to update it properly, would you advice me to make an in-place upgrade using the Big Sur install app from Applications, in order to avoid a clean install? Or the latter seems safer?

Edited by Vyzantion
XanthraX
XanthraX
Posted
Posted
11 hours ago, XanthraX said:

Everything seemed to work OK in installation, but now I have sound interruptions at every about 30 seconds. Is anyone else experiencing this? I replaced the kexts in EFI, i rebooted. The problem persists.

Sorry, it was my only fault. After the update, a VST plugin lost its license data and ran in demo mode. Can be ignored or deleted.

jsl2000
jsl2000
Posted
Posted (edited)
16 hours ago, Cyberdevs said:

macOS Big Sur 11.2.3 direct download link if anyone is interested.

Thanks for your help and now I can boot Big Sur 11.2.3 in my three old hackintoshs including P6TSE (Sandy Bridge, i7-920 CPU), P5Q PRO (LGA775, Intel Core 2 Extreme X9650) and GA-965P-DS4 (LGA775, Intel Core Duo 2 E8400).

Edited by jsl2000
  • Like 2
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...