Guten Morgen,
hat jemand von euch OpenCore und SecureBootModel richtig am laufen?
Seit einem der letzten Updates von OpenCore funktioniert bei mir das Starten von BigSur nur noch mit SecureBootModel=Disabled. Vielleicht bekommen wir zusammen hier so was wie eine Anleitung hin. Aktuell drehe ich mich damit nur im Kreis und BigSur lässt sich nicht starten wenn SecureBootModel aktiviert ist.
Hier die Beschreibung aus der Configuration.pdf von OpenCore.
SecureBootModel
Type: plist string
Failsafe: Default
Description: Apple Secure Boot hardware model.
Sets Apple Secure Boot hardware model and policy. Specifying this value defines which operating systems will be bootable. Operating systems shipped before the specified model was released will not boot. Valid values:
• Default — Recent available model, currently set to j137.
• Disabled — No model, Secure Boot will be disabled.
• j137 — iMacPro1,1 (December 2017) minimum macOS 10.13.2 (17C2111)
• j680 — MacBookPro15,1 (July 2018) minimum macOS 10.13.6 (17G2112)
• j132 — MacBookPro15,2 (July 2018) minimum macOS 10.13.6 (17G2112)
• j174 — Macmini8,1 (October 2018) minimum macOS 10.14 (18A2063)
• j140k — MacBookAir8,1 (October 2018) minimum macOS 10.14.1 (18B2084) • j780 — MacBookPro15,3 (May 2019) minimum macOS 10.14.5 (18F132)
• j213 — MacBookPro15,4 (July 2019) minimum macOS 10.14.5 (18F2058)
• j140a — MacBookAir8,2 (July 2019) minimum macOS 10.14.5 (18F2058)
• j152f — MacBookPro16,1 (November 2019) minimum macOS 10.15.1 (19B2093) • j160 — MacPro7,1 (December 2019) minimum macOS 10.15.1 (19B88)
• j230k — MacBookAir9,1 (March 2020) minimum macOS 10.15.3 (19D2064)
• j214k — MacBookPro16,2 (May 2020) minimum macOS 10.15.4 (19E2269)
• j223 — MacBookPro16,3 (May 2020) minimum macOS 10.15.4 (19E2265)
• j215 — MacBookPro16,4 (June 2020) minimum macOS 10.15.5 (19F96)
• j185 — iMac20,1 (August 2020) minimum macOS 10.15.6 (19G2005)
• j185f — iMac20,2 (August 2020) minimum macOS 10.15.6 (19G2005)
PlatformInfo and SecureBootModel are independent, allowing to enabling Apple Secure Boot with any SMBIOS. Setting SecureBootModel to any valid value but Disabled is equivalent to Medium Security of Apple Secure Boot. The ApECID value must also be specified to achieve Full Security.
Enabling Apple Secure Boot is more demanding to incorrect configurations, buggy macOS installations, and unsupported setups. Things to consider:
(a) As with T2 Macs, unsigned kernel drivers and several signed kernel drivers, including NVIDIA Web Drivers, cannot be installed.
(b) The list of cached drivers may be different, resulting in the need to change the list of Added or Forced kernel drivers. For example, IO80211Family cannot be injected in this case.
(c) System volume alterations on operating systems with sealing, such as macOS 11, may result in the operating system being unbootable. Do not try to disable system volume encryption unless Apple Secure Boot is disabled.
(d) If the platform requires certain settings, but they were not enabled, because the obvious issues did not trigger before, boot failure might occur. Be extra careful with IgnoreInvalidFlexRatio or HashServices.
(e) Operating systems released before Apple Secure Boot landed (e.g. macOS 10.12 or earlier) will still boot
until UEFI Secure Boot is enabled. This is so, because from Apple Secure Boot point they are treated as
incompatible and are assumed to be handled by the firmware as Microsoft Windows is.
(f) On older CPUs (e.g. before Sandy Bridge) enabling Apple Secure Boot might cause slightly slower loading
by up to 1 second.
(g) Since Default value will increase with time to support the latest major release operating system, it is not
recommended to use ApECID and Default value together.
Sometimes the already installed operating system may have outdated Apple Secure Boot manifests on the Preboot partition causing boot failure. If there is “OCB: Apple Secure Boot prohibits this boot entry, en- forcing!” message, it is likely the case. When this happens, either reinstall the operating system or copy the manifests (files with .im4m extension, such as boot.efi.j137.im4m) from /usr/standalone/i386 to /Volumes/Preboot/<UUID>/System/Library/CoreServices. Here <UUID> is the system volume identifier. On
46HFS+ installations the manifests should be copied to /System/Library/CoreServices on the system volume. For more details on how to configure Apple Secure Boot with UEFI Secure Boot refer to UEFI Secure Boot
section.
