Jump to content

[pre-release] macOS Monterey 12.1


Wayang-NT
247 posts in this topic

Recommended Posts

Beta 12.1 Update :
For T2 chip SMBIOS, with Clover r5142 (thank you Slice !!) and CloverConfigurator 5.19.0.0, it is necessary and sufficient to:

SMBIOS section: choose your SMBIOS (to keep your Serial N °, SMUUID, BSN: check Update Firmware Only), ExtendedFirmwares and Firmwares are filled in automatically.
Rt Variables section: new HWTarget box to fill in according to the SMBIOS :

MacBookPro 15,1 (J680AP) 15,2 (J132AP) 15,3 (J780AP) & 15,4 (J213AP)
MacBookPro16,1 (J152FAP) 16,3 (J223AP) & 16,4 (J215AP
MacBookPro16,2 (J214KAP)
MacBookAir8,1 (J140KAP) & 8,2 (J140AAP) 
MacBookAir9,1 (J230KAP) 
Macmini8,1 (J174AP)
iMac20,1 (J185AP) & 20,2 (J185FAP) 
iMacPro1,1 (J137AP)
MacPro7,1 (J160AP) 
It is no longer necessary to remove HWTarget at any point in the process !!

No need for the RestrictEvents kext either !!

Edited by Gradou
  • Like 4
  • Thanks 1
Link to comment
Share on other sites

On 11/3/2021 at 1:25 PM, Letitbe said:

The issue have been resolved using RestrictEvents and reinstalling the 12.1 again.

Great! :) Thanks for letting us know you were able to fix your issues. Happy it works for you now! :) 

  • Like 2
Link to comment
Share on other sites

Hi guys,

Today I tried OCS to validate my config.plist OC 0.7.6 and it returned 3 errors:

OCS: Missing key Comment, context <Drivers>! 

I'm trying to solve the missing entry of  my windows 11 at beginning of OC.

Do you know how to solve this?

Thanksconfig.plist

Edited by MorenoAv
  • Like 1
Link to comment
Share on other sites

Just now, MorenoAv said:

Hi guys,

Today I tried OCS to validate my config.plist OC 0.7.6 and it returned 3 errors:

OCS: Missing key Comment, context <Drivers>! 

I'm trying to solve the missing entry of  my windows 11 at beginning of OC.

Do you know how to solve this?

Thanks

send config here please I will fix

  • Like 2
Link to comment
Share on other sites

10 minutes ago, MorenoAv said:

Hi guys,

Today I tried OCS to validate my config.plist OC 0.7.6 and it returned 3 errors:

OCS: Missing key Comment, context <Drivers>! 

I'm trying to solve the missing entry of  my windows 11 at beginning of OC.

Do you know how to solve this?

Thanksconfig.plist

 

Schermata 2021-11-05 alle 19.59.12.png

  • Like 3
  • Thanks 1
Link to comment
Share on other sites

That solved the first errors, but now I have another one: OCS: No schema for UIScale at 12 index, context <Output>!

And my SSD with Windows is still missing in action at boot...

Thanks

 

 PS: OCS No Schema is solved, removed that entry and all is well again... 

The only thing missing is my ssd with Windows 11...

Edited by MorenoAv
  • Like 1
Link to comment
Share on other sites

58 minutes ago, MorenoAv said:

OCS: No schema for UIScale at 12 index, context <Output>!

This is a new added line in the latest OC commit, if you use OC validate within that version it will come back with no errors, if you use the app OCAT it will come back with that error as it hasn't caught up with the new OC version as yet. As you deleted that line no harm done. :thumbsup_anim:

4 minutes ago, MorenoAv said:

My Scan policy is 17760515, and no I installed Windows 11 in GPT I think...

Try 0 (zero) that is my setting.

 

Edited by eSaF
  • Like 4
  • Thanks 1
Link to comment
Share on other sites

15 minutes ago, MorenoAv said:

Hi @antuneddu,

My Scan policy is 17760515, and no I installed Windows 11 in GPT I think...

I wrote it to you ......... With 0 It should detect it

7 minutes ago, MorenoAv said:

That did the trick I have my windows back, but with it comes an entry named EFI too... and that I don't mind to make disappear... 

edit:i was worng     try 19860739  or 

https://oc-scanpolicy.vercel.app/ 

to find the right value for you ,default is 17760515 

Edited by antuneddu
Link to comment
Share on other sites

4 minutes ago, MorenoAv said:

but with it comes an entry named EFI too... and that I don't mind to make disappear... 

Have you got another version of OS X running apart from Monterey on the system? If you have and that has it's own EFI Folder, that will cause the EFI volume to show at the Boot Menu. I have one EFI Folder that resides on Monterey and that boots BS as well without EFI showing at Boot Menu.

  • Like 2
Link to comment
Share on other sites

I have macOS BS but I have only one EFI that boots Monterey and BS, the EFI that appears at first I don't know what is...

 

PS: I have found the culprit... it was an EFI in the BS SSD... I deleted it and I think that I solved the problem... BRB...

Thanks

IMG_0630.jpg

Edited by MorenoAv
  • Like 1
Link to comment
Share on other sites

I have solved all my issues with your help, your guys are fenomenal, thank you all...

 

I had an EFI in my BS Ssd, and the scan policy was wrong, now I changed it for 0, and Windows 11 now appears again...

  • Like 5
Link to comment
Share on other sites

14 hours ago, eSaF said:

This is a new added line in the latest OC commit, if you use OC validate within that version it will come back with no errors, if you use the app OCAT it will come back with that error as it hasn't caught up with the new OC version as yet. As you deleted that line no harm done. :thumbsup_anim:

Try 0 (zero) that is my setting.

 

@eSaF Same here 0 = 0 issue :hysterical:

06114357.thumb.png.3482256d941cc7dd9940a4bbc22f2a83.png

  • Like 7
  • Thanks 1
  • Haha 2
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...