miliuco Posted October 4, 2021 Share Posted October 4, 2021 (edited) @oldman Tell me if you have 0 in UEFI >> APFS >> MinDate and MinVersion. Changed in OpenCore0.7.2 UEFI> APFS: Increased the MinDate and MinVersion defaults in the APFS driver to match Big Sur in search of greater security. These values constitute the minimum date and version of the APFS driver whose loading will be allowed at startup. Examples: MinDate and MinVersion 0 is the default setting (currently Big Sur), leave this value if you use Big Sur or Monterey MinDate = 20210508 and MinVersion = 1677120009000000 for Big Sur 11.4 (20F71) MinDate = 20200306 and MinVersion = 1412101001000000 for Catalina 10.15.4 (19E287) MinDate = 20190820 and MinVersion = 945275007000000 for Mojave 10.14.6 (18G103) MinDate and MinVersion -1 disable this check (not recommended). MinDate and MinVersion need to be tuned for macOS versions prior to Big Sur. You must type MinDate=20200306 and MinVersion=1412101001000000 for Catalina. Edited October 4, 2021 by miliuco 5 2 Link to comment Share on other sites More sharing options...
etorix Posted October 4, 2021 Share Posted October 4, 2021 17 minutes ago, oldman20 said: BUT current document guides isn't 😳, how can i config plist properly? Either stay on 0.7.2—but this is then the wrong thread—or use Configuration.pdf to understand the new options. But wait a while: The latest releases of Lilu and VirtualSMC are not out yet. 1 Link to comment Share on other sites More sharing options...
MacNB Posted October 4, 2021 Share Posted October 4, 2021 33 minutes ago, miliuco said: @oldman MinDate and MinVersion -1 disable this check (not recommended). Unfortunately, -1 is the only option if you are quadruple booting High Sierra, Mojave, Catalina & Big Sur on the same system. 3 Link to comment Share on other sites More sharing options...
oldman20 Posted October 4, 2021 Share Posted October 4, 2021 37 minutes ago, miliuco said: @oldman Tell me if you have 0 in UEFI >> APFS >> MinDate and MinVersion. Changed in OpenCore0.7.2 UEFI> APFS: Increased the MinDate and MinVersion defaults in the APFS driver to match Big Sur in search of greater security. These values constitute the minimum date and version of the APFS driver whose loading will be allowed at startup. Examples: MinDate and MinVersion 0 is the default setting (currently Big Sur), leave this value if you use Big Sur or Monterey MinDate = 20210508 and MinVersion = 1677120009000000 for Big Sur 11.4 (20F71) MinDate = 20200306 and MinVersion = 1412101001000000 for Catalina 10.15.4 (19E287) MinDate = 20190820 and MinVersion = 945275007000000 for Mojave 10.14.6 (18G103) MinDate and MinVersion -1 disable this check (not recommended). MinDate and MinVersion need to be tuned for macOS versions prior to Big Sur. You must type MinDate=20200306 and MinVersion=1412101001000000 for Catalina. Yes, MinDate and MinVersion is =0. If i change to like you said, can i still able can boot Monterrey or Big Sur? 22 minutes ago, etorix said: Either stay on 0.7.2—but this is then the wrong thread—or use Configuration.pdf to understand the new options. But wait a while: The latest releases of Lilu and VirtualSMC are not out yet. But 0.7.2 cant boot Montery, right? Link to comment Share on other sites More sharing options...
Anto65 Posted October 4, 2021 Share Posted October 4, 2021 8 minutes ago, oldman20 said: Yes, MinDate and MinVersion is =0. If i change to like you said, can i still able can boot Monterrey or Big Sur? But 0.7.2 cant boot Montery, right? Why shouldn't it boot ? I boot Mrey, BS, Catalina, Windows and Linux without problems with settings MinDate ..... in APFS ( OC-0.7.4 ) 2 Link to comment Share on other sites More sharing options...
oldman20 Posted October 4, 2021 Share Posted October 4, 2021 15 minutes ago, MacNB said: Unfortunately, -1 is the only option if you are quadruple booting High Sierra, Mojave, Catalina & Big Sur on the same system. 3 minutes ago, antuneddu said: Why shouldn't it boot ? I boot Mrey, BS, Catalina, Windows and Linux without problems with settings MinDate ..... in APFS ( OC-0.7.4 ) Thank you. But why do you have Conflict of opinion? COnfig plist guide now just at 0.7.2, so i think must start from it, than modify to 0.7.3, then 0.7.4 following changes in pdf file of they? Not jump from 0.6.9 to 0.7.4? Link to comment Share on other sites More sharing options...
miliuco Posted October 4, 2021 Share Posted October 4, 2021 @oldman APFS mindate and minversion is the same since 0.7.2. Each value is a minimum, it filters older systems. Catalina values filter Mojave and older, but you can boot newer with them. 2 1 Link to comment Share on other sites More sharing options...
pkdesign Posted October 4, 2021 Share Posted October 4, 2021 On 10/3/2021 at 2:10 PM, Slice said: Why do you seek to disable SIP? Hackintosh will work with the SIP enabled, csr-active-config=0 You want unrestricted DTRACE? You want NVRAM overflow? You want write bytes outside disk partition? I have a very specific reason and that is to continue to use TotalFinder which has to have SIP disabled in order to work. But I messaged developer and he gave me correct setting so I now have SIP enabled (mostly) with working TotalFinder. I couldn't be happier. Link to comment Share on other sites More sharing options...
Slice Posted October 5, 2021 Share Posted October 5, 2021 14 hours ago, pkdesign said: I have a very specific reason and that is to continue to use TotalFinder which has to have SIP disabled in order to work. But I messaged developer and he gave me correct setting so I now have SIP enabled (mostly) with working TotalFinder. I couldn't be happier. Finally, what is your csr-active-config now? Link to comment Share on other sites More sharing options...
pkdesign Posted October 5, 2021 Share Posted October 5, 2021 (edited) Using BitmaskDecode it gave me a value of 0x6: # CsrActiveConfig Values To Number # [ ] 1. CSR_ALLOW_UNTRUSTED_KEXTS - 0x1 (1) [#] 2. CSR_ALLOW_UNRESTRICTED_FS - 0x2 (2) [#] 3. CSR_ALLOW_TASK_FOR_PID - 0x4 (4) [ ] 4. CSR_ALLOW_KERNEL_DEBUGGER - 0x8 (8) [ ] 5. CSR_ALLOW_APPLE_INTERNAL - 0x10 (16) [ ] 6. CSR_ALLOW_UNRESTRICTED_DTRACE - 0x20 (32) [ ] 7. CSR_ALLOW_UNRESTRICTED_NVRAM - 0x40 (64) [ ] 8. CSR_ALLOW_DEVICE_CONFIGURATION - 0x80 (128) [ ] 9. CSR_ALLOW_ANY_RECOVERY_OS - 0x100 (256) [ ] 10. CSR_ALLOW_UNAPPROVED_KEXTS - 0x200 (512) [ ] 11. CSR_ALLOW_EXECUTABLE_POLICY_OVERRIDE - 0x400 (1,024) [ ] 12. CSR_ALLOW_UNAUTHENTICATED_ROOT - 0x800 (2,048) Current: 0x6 (6) This setting shows the following using csrutil status: System Integrity Protection status: enabled (Custom Configuration). Configuration: Apple Internal: disabled Kext Signing: enabled Filesystem Protections: disabled Debugging Restrictions: disabled DTrace Restrictions: enabled NVRAM Protections: enabled BaseSystem Verification: enabled Of course ocvalidate doesn't like this setting but it works. Edited October 5, 2021 by pkdesign 3 Link to comment Share on other sites More sharing options...
Moviemakergr Posted October 6, 2021 Share Posted October 6, 2021 Morning.. OC 0.7.4 broken my windows boot.. i roll back to 0.7.1 do we know anything about this? 2 1 Link to comment Share on other sites More sharing options...
deeveedee Posted October 6, 2021 Share Posted October 6, 2021 Having received his response on more than one occasion, I never thought I'd say this, but I miss Rehabman's "No problem reporting files." 5 1 Link to comment Share on other sites More sharing options...
galisrule Posted October 6, 2021 Share Posted October 6, 2021 OC 74 doesnt booth catalina either and for sure windows 11 had to revert to OC 72 Link to comment Share on other sites More sharing options...
Anto65 Posted October 6, 2021 Share Posted October 6, 2021 Some options available recommended in UEFI / APFS AUTO = 0 Currently set to allow macOS Big Sur and later (16000000000000000) ANY = -1 Allows any version to be loaded (strongly discouraged) DEFAULT MinDate = 20210101 MinVersion = 1600000000000000 HIGH SIERRA MinDate = 20180621 MinVersion = 7480770080000000 MOJAVE MinDate = 20190820 MinVersion = 9452750070000000 CATALINA MinDate = 20200306 MinVersion = 1412101001000000 BIG SUR MinDate = 20210508 MinVersion = 1677120009000000 1 1 Link to comment Share on other sites More sharing options...
galisrule Posted October 6, 2021 Share Posted October 6, 2021 19 minutes ago, antuneddu said: Some options available recommended in UEFI / APFS AUTO = 0 Currently set to allow macOS Big Sur and later (16000000000000000) ANY = -1 Allows any version to be loaded (strongly discouraged) DEFAULT MinDate = 20210101 MinVersion = 1600000000000000 HIGH SIERRA MinDate = 20180621 MinVersion = 7480770080000000 MOJAVE MinDate = 20190820 MinVersion = 9452750070000000 CATALINA MinDate = 20200306 MinVersion = 1412101001000000 BIG SUR MinDate = 20210508 MinVersion = 1677120009000000 WORKS FOR 72 NOT 74 Link to comment Share on other sites More sharing options...
Anto65 Posted October 6, 2021 Share Posted October 6, 2021 (edited) The image of the config.plist is from 0.7.4 OC and Catalina boot fine, then try with SBModel Disabled Edited October 6, 2021 by antuneddu Link to comment Share on other sites More sharing options...
galisrule Posted October 6, 2021 Share Posted October 6, 2021 I TRIED BOTH DISABLE AND DEFAULT SAME RESULT WONT BOOT CATALINA OR WINDOWS 72 and 74 is very similar accept for the array in UEFA drivers Link to comment Share on other sites More sharing options...
galisrule Posted October 6, 2021 Share Posted October 6, 2021 I think it might be something in the OpenCore efi for some hacks? Link to comment Share on other sites More sharing options...
galisrule Posted October 6, 2021 Share Posted October 6, 2021 On 9/23/2021 at 2:18 AM, SavageAUS said: Is there a setting I need to change for my smbios info to work? I have the generic section filled in correctly but shows up as pictured. Sent from my iPhone using Tapatalk UpdateSMBIOSMode change from custom to create Link to comment Share on other sites More sharing options...
Tecnicaso Rico Posted October 6, 2021 Share Posted October 6, 2021 50 minutes ago, galisrule said: OC 74 doesnt booth catalina either and for sure windows 11 had to revert to OC 72 I'm triple booting macOS Catalina 10.15.7, Windows 10 and Ubuntu Studio 20.04.3 LTS with OC 0.7.5 (which is the latest commit of 0.7.4) without problems. but there is a catch. After reading about the changes in the latest official release, comment by @miliuco at the [HOW TO] OpenCore 0.7.3 > 0.7.4 differences post he made, I followed making the "necessary changes" advised for this latest release. Specifically this is the part that made me fail in my initial attempt to boot with latest OC: "Misc >> Security >> changed Default SecureBootMode value to match SMBIOS model to fix Monterey updates. There is no need to change SecureBootModel value in the config, Default will work for everyone". I change my SecureBootModel from j185f to Default and couldn't boot. Then I switch back to j185f and then I was able to boot the latest OC. I think this Default setting only applies for Big Sur and Monterey. Also I think you should pay attention to the UEFI>>APFS section. 3 Link to comment Share on other sites More sharing options...
Anto65 Posted October 6, 2021 Share Posted October 6, 2021 44 minutes ago, galisrule said: I TRIED BOTH DISABLE AND DEFAULT SAME RESULT WONT BOOT CATALINA OR WINDOWS 72 and 74 is very similar accept for the array in UEFA drivers https://drive.google.com/file/d/1LbyKRpHMKz2k4QZDZPAk4p9-8SG2JLy0/view?usp=sharing 😇 1 Link to comment Share on other sites More sharing options...
galisrule Posted October 6, 2021 Share Posted October 6, 2021 35 minutes ago, Tecnicaso Rico said: I'm triple booting macOS Catalina 10.15.7, Windows 10 and Ubuntu Studio 20.04.3 LTS with OC 0.7.5 (which is the latest commit of 0.7.4) without problems. but there is a catch. After reading about the changes in the latest official release, comment by @miliuco at the [HOW TO] OpenCore 0.7.3 > 0.7.4 differences post he made, I followed making the "necessary changes" advised for this latest release. Specifically this is the part that made me fail in my initial attempt to boot with latest OC: "Misc >> Security >> changed Default SecureBootMode value to match SMBIOS model to fix Monterey updates. There is no need to change SecureBootModel value in the config, Default will work for everyone". I change my SecureBootModel from j185f to Default and couldn't boot. Then I switch back to j185f and then I was able to boot the latest OC. I think this Default setting only applies for Big Sur and Monterey. Also I think you should pay attention to the UEFI>>APFS section. Setting SecureBootModel to j185f really boots Catalina but not windows 11pro unlike with OC 0.72 with SecureBootMode set to default everything boot including windows Link to comment Share on other sites More sharing options...
miliuco Posted October 6, 2021 Share Posted October 6, 2021 (edited) 3 hours ago, galisrule said: OC 74 doesnt booth catalina either and for sure windows 11 had to revert to OC 72 Not true. OC 0.7.4 can boot Catalina and Windows 11. For Catalina, check @antuneddu's post, MinDate and MinVersion of UEFi >> APFS. For Windows 11, I'm booting it the same way as in 0.7.3. What's the problem or error warning? Windows icon not displayed in the picker? Selecting Windows icon fails booting Windows 11? Try 2 keys in config.plist (also for @Tecnicaso Rico) Kernel > Quirks > CustomSMBIOSGuid > True (default is False) PlatformInfo > UpdateSMBIOSMode > Custom (default is Create). Edited October 6, 2021 by miliuco 1 Link to comment Share on other sites More sharing options...
miliuco Posted October 6, 2021 Share Posted October 6, 2021 (edited) 2 hours ago, Tecnicaso Rico said: "Misc >> Security >> changed Default SecureBootMode value to match SMBIOS model to fix Monterey updates. There is no need to change SecureBootModel value in the config, Default will work for everyone". I change my SecureBootModel from j185f to Default and couldn't boot. Then I switch back to j185f and then I was able to boot the latest OC. I think this Default setting only applies for Big Sur and Monterey... Quoted text is said by OpenCore developers, setting Default as a valid value for any one since it picks for SecureBootModel the same Mac model as in current SMBIOS. But our hacks are each one a world. If you are working fine with SBM=j185f then go ahead, it's completely valid also. Do you have iMac20,2 as SMBIOS model? Edited October 6, 2021 by miliuco Link to comment Share on other sites More sharing options...
miliuco Posted October 6, 2021 Share Posted October 6, 2021 @galisrule Please complete your signature (user >> profile). Link to comment Share on other sites More sharing options...
Recommended Posts