hiphopboy Posted November 4, 2021 Share Posted November 4, 2021 anybody have this error on quicktime, this speaker icon just have a haft 1 1 Link to comment Share on other sites More sharing options...
Gradou Posted November 4, 2021 Share Posted November 4, 2021 (edited) 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 (J215APMacBookPro16,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 November 4, 2021 by Gradou 4 1 Link to comment Share on other sites More sharing options...
Naki Posted November 4, 2021 Share Posted November 4, 2021 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! 2 Link to comment Share on other sites More sharing options...
ndungu6678 Posted November 5, 2021 Share Posted November 5, 2021 (edited) On 11/4/2021 at 8:02 AM, hiphopboy said: anybody have this error on quicktime, this speaker icon just have a haft My QuickTime player volume icon shows up ok!- Mac OS Monterey 12.1 BETA Edited November 6, 2021 by ndungu6678 3 Link to comment Share on other sites More sharing options...
hiphopboy Posted November 5, 2021 Share Posted November 5, 2021 Maybe it's the SMBIOS configuration 2 Link to comment Share on other sites More sharing options...
PG7 Posted November 5, 2021 Share Posted November 5, 2021 Monterey 12.1 b1 intel i5 M430 bootloader OpenCore 0.7.6 "Clover (r.5142 version) NO Work patch ! ! !" my config.plist Clover r5142 = No boot ! ! ! (Patch ?) my config.plist OpenCore 0.7.6 = OK config-OC 0.7.6 patcher.plisconfig-Clover r5142 patcher ?.plist Spoiler 1 Link to comment Share on other sites More sharing options...
MorenoAv Posted November 5, 2021 Share Posted November 5, 2021 (edited) 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 November 5, 2021 by MorenoAv 1 Link to comment Share on other sites More sharing options...
chris1111 Posted November 5, 2021 Share Posted November 5, 2021 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 2 Link to comment Share on other sites More sharing options...
MorenoAv Posted November 5, 2021 Share Posted November 5, 2021 2 minutes ago, chris1111 said: send config here please I will fix Thanks @chris1111 , Here it is the config.plist config.plist 1 Link to comment Share on other sites More sharing options...
Anto65 Posted November 5, 2021 Share Posted November 5, 2021 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 3 1 Link to comment Share on other sites More sharing options...
chris1111 Posted November 5, 2021 Share Posted November 5, 2021 7 minutes ago, MorenoAv said: Thanks @chris1111 , Here it is the config.plist config.plist 17.83 kB · 2 downloads Here fix config.plist.zip No isue 2 1 1 Link to comment Share on other sites More sharing options...
MorenoAv Posted November 5, 2021 Share Posted November 5, 2021 (edited) 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 November 5, 2021 by MorenoAv 1 Link to comment Share on other sites More sharing options...
Anto65 Posted November 5, 2021 Share Posted November 5, 2021 (edited) It might depend on the ScanPolicy how is set, what value do you have? With 0 It should detect it, You haven't installed in mbr right?No with Win 11 I don't think so Edited November 5, 2021 by antuneddu 1 Link to comment Share on other sites More sharing options...
MorenoAv Posted November 5, 2021 Share Posted November 5, 2021 Hi @antuneddu, My Scan policy is 17760515, and no I installed Windows 11 in GPT I think... Link to comment Share on other sites More sharing options...
eSaF Posted November 5, 2021 Share Posted November 5, 2021 (edited) 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. 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 November 5, 2021 by eSaF 4 1 Link to comment Share on other sites More sharing options...
MorenoAv Posted November 5, 2021 Share Posted November 5, 2021 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... Link to comment Share on other sites More sharing options...
Anto65 Posted November 5, 2021 Share Posted November 5, 2021 (edited) 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 November 5, 2021 by antuneddu Link to comment Share on other sites More sharing options...
MorenoAv Posted November 5, 2021 Share Posted November 5, 2021 4 minutes ago, antuneddu said: I wrote it to you ......... With 0 It should detect it I changed it to 0, and now I have again Windows 11 at boot... Thanks 1 Link to comment Share on other sites More sharing options...
eSaF Posted November 5, 2021 Share Posted November 5, 2021 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. 2 Link to comment Share on other sites More sharing options...
MorenoAv Posted November 5, 2021 Share Posted November 5, 2021 (edited) 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 Edited November 5, 2021 by MorenoAv 1 Link to comment Share on other sites More sharing options...
Anto65 Posted November 5, 2021 Share Posted November 5, 2021 3 minutes ago, MorenoAv said: 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... try scanpolicy 19860739 or https://oc-scanpolicy.vercel.app/ to find the right value for you ,default is 17760515 1 1 Link to comment Share on other sites More sharing options...
MorenoAv Posted November 5, 2021 Share Posted November 5, 2021 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... 5 Link to comment Share on other sites More sharing options...
Anto65 Posted November 5, 2021 Share Posted November 5, 2021 (edited) Sorry but I don't understand, you have only updated oc to 0.7.6 but you haven't already configured everything in the previous versions or not? How was it all high now 😊 ? Edited November 6, 2021 by antuneddu 1 2 Link to comment Share on other sites More sharing options...
MorenoAv Posted November 6, 2021 Share Posted November 6, 2021 Yeah @antuneddu, I updated to OC 0.7.6 and all hell broke loose, as sometimes happens, and you are right I had all configured but with errors that showed itself in this update... With your help al is ok now... 1 Link to comment Share on other sites More sharing options...
chris1111 Posted November 6, 2021 Share Posted November 6, 2021 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. Try 0 (zero) that is my setting. @eSaF Same here 0 = 0 issue 7 1 2 Link to comment Share on other sites More sharing options...
Recommended Posts