Jump to content
8755 posts in this topic

Recommended Posts

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.

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?

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 by pkdesign
  • Like 3

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

 

905530141_Schermata2021-08-21alle14_30_0 

  • Thanks 1
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

 

905530141_Schermata2021-08-21alle14_30_0 

WORKS FOR 72 NOT 74 

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. 0e0782aff9c96eb822b0a2924953ea88.jpg


Sent from my iPhone using Tapatalk

UpdateSMBIOSMode change from custom to create

Screen Shot 2021-10-06 at 4.08.01 PM.png

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.

 

  • Like 3
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 😇

  • Like 1
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

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 by miliuco
  • Like 1
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 by miliuco
46 minutes ago, miliuco said:

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?

I have 17,1

15 minutes ago, Tecnicaso Rico said:

I have 17,1

Then you have SecureBootModel j185f (iMac20,2, it filters macOS 10.15.5 and older, macOS 10.15.6 and newer are allowed ) but SMBIOS iMac17,1. Anyway, if it works fine, go ahead.

21 hours ago, Moviemakergr said:

Morning..

OC 0.7.4 broken my windows boot.. i roll back to 0.7.1

do we know anything about this?

The mystery was solved .. it was the AppleVTD That I used 0.73 and later..

Now i m on 0.74 and booting Win 11 and monterey..

 
Edited by Moviemakergr
16 hours ago, miliuco said:

Then you have SecureBootModel j185f (iMac20,2, it filters macOS 10.15.5 and older, macOS 10.15.6 and newer are allowed ) but SMBIOS iMac17,1. Anyway, if it works fine, go ahead.

I think the reason it works is because each of the different  SecureBootModel  options started to be supported during a specific macOS release and the SMBIOS reference just indicates which was the first SecureBootModel option used by that SMBIOS. So I think what matters is to pair the SecureBootModel option with the macOS version you are using.

Hi. I have two macOS drives that show up in Opencore boot picker. In macOS I have them named differently, one is "macOS Big Sur" and the other is named "Backup" but in the boot picker they both show as same name "macOS Big Sur". My question is how can I configure so thet my Backup disk shows with the name "Backup" in the boot picker? How/where do I do that? Many thanks for help

×
×
  • Create New...