Jump to content
30970 posts in this topic

Recommended Posts

I updated the release 5172 without changing the release number. It is the same in functionality but compiled by GCC.

Also there are new icons from Chris1111. Thanks!

New books are here https://github.com/CloverHackyColor/CloverBootloader/releases/download/5172/Clover_Of_Khaki_Color_5172-en.pdf

  • Like 4
  • Thanks 3
  • 2 weeks later...

@Slice

Greetings

Tried to enable secure boot

Compiled Clover 🍀 with

./buildme "" ci -D ENABLE_SECURE_BOOT=1

Clover efi and all other efi from drivers and tools was signed.. 

sbsign --key db.key --cert db.crt --output signed_bootloader.efi original_bootloader.efi

x509 certificate endabled in bios rom

Mac partition are displayed/loaded in clover only with apfs.efi

All that without success

What should I edit in clover plist?

I'm lost

  • Like 1

@MICKHAEL

 

This is for Opencore; I'm not sure if it also applies to Clover. You can try it and let me know the result.

 

 

As you can see, the idea is that, instead of digitally signing the binaries in the EFI folder, you enroll all the .efi files in the UEFI database secure variable, which is a list of allowed signatures, so that UEFI Secure Boot accepts these .efi files as safe. You don't modify or sign the .efi files; you just tell the firmware to consider them safe to boot even if UEFI Secure Boot is enabled.

 

To do this, you have to restore the default keys in UEFI Secure Boot from the BIOS menu to remove anything you've added to them. Then, in the Enroll EFI Image menu of UEFI Secure Boot, add all the .efi files one by one. If this Enroll EFI Image menu (or something similar) doesn't exist, then this method won't work for you.

 

If you can try it, please let me know the result.

 

The worst that can happen is that this method doesn't work either, in which case you have to go back to Reset Default Keys in UEFI Secure Boot.

  • Like 4
  • 4 weeks later...
5 hours ago, Matgen84 said:

 

Hi @Max.1974 What is this Clover 5175 ? I can find it.  There is no such version at CloverHackyClover/Cloverbootloader repo. 

Sorry late, this is a beta tester version, my friend, developed by  @MaLd0n !! ;) 

 

 

 

 

  • Like 3

Clover 520x soon

A major modernization goal for Clover is full AMD platform support, from Ryzen and Threadripper to EPYC and future AMD generations. Clover should be able to handle AMD-specific macOS boot requirements more cleanly, including kernel patch handling, CPUID compatibility, SMBIOS adaptation, PCI device preparation and stable boot behavior, while still keeping every option controlled by config.plist.

Another important goal is to make Clover capable of managing the common ACPI fixes selected by the user, reducing the need for separate manual SSDTs on most chipsets. Clover should not blindly apply ACPI changes by itself. The user still enables the desired fixes in config.plist, and Clover then performs the selected work dynamically and safely according to the real firmware ACPI layout.

This means that when the user enables fixes such as EC, USBX, PLUG/plugin-type, PMCR, RTC, AWAC, HPET, IRQ fixes, NVMe injection, USB power properties or _DSM collision handling, Clover should detect the correct ACPI scope, PCI root, bridge and device path instead of relying on fixed names like PCI0, PC00 or PC02.

The objective is not to remove user control. The objective is to remove the need for hand-made SSDTs for common fixes. Clover should provide selectable ACPI fixes that work across many Intel and AMD chipsets by detecting where the patch belongs, avoiding duplicate devices, preserving valid firmware devices and renaming only target-device _DSM methods when required.

With this approach, Clover becomes more powerful and easier to maintain. Most users can rely on Clover’s built-in selectable ACPI fixes instead of manually creating SSDTs for every board, while advanced users still remain free to disable Clover fixes and use custom SSDTs when they need full manual control.

 

Quote

1. Full AMD Platform Support
   Clover should provide complete AMD support for Ryzen, Threadripper, EPYC and future AMD platforms, including kernel patch handling, CPUID handling, SMBIOS compatibility, PCI device support and clean macOS boot behavior.

2. Full Intel Platform Support
   Clover should remain compatible from legacy Intel platforms such as LGA775/Core2 up to X99, X299, Z490, Z590, Z690, Z790, Z890 and modern Core Ultra systems, with fixes scoped only to the generations that need them.

3. Clover-Managed ACPI
   Clover should reduce the need for manual SSDTs by handling common ACPI requirements internally, including EC, USBX, PLUG, PMCR, RTC, AWAC, HPET, IRQ fixes, NVMe injection and safe generated device creation.

4. No Mandatory Manual ACPI for Common Fixes
5. Safe ACPI Device Injection
   Clover should inject devices only when needed, avoid duplicates, preserve existing valid firmware devices, and rename only target-device _DSM methods when required to prevent duplicate _DSM conflicts.

6. Modern NVMe Handling
   Clover should support both existing NVMe ACPI devices and missing NVMe child devices by injecting the correct device properties or creating the required bridge/child structure when the firmware lacks it.

7. Modern Kernel Collection Boot Support
   Clover should fully support modern macOS KernelCollection boot while preserving legacy support for older macOS versions that still use mkext, prelinkedkernel or older kernel loading paths.

8. Professional Apple boot.efi Handoff
   Clover should pass boot arguments through an Apple-compatible handoff model, using verified Apple NVRAM transport for persistent boot-args and safe LoadOptions fallback only when required for installer or recovery boot.

9. Reliable Reset NVRAM
   Reset NVRAM should work cleanly from Clover without freezes, restart loops or broken firmware boot entries, while preserving essential Apple and firmware variables.

10. Clean NVRAM Management
   Clover should manage Apple, Clover, VirtualSMC, FakeSMC and Hackintosh-related NVRAM variables safely, avoiding stale variables and keeping only what is needed for stable macOS boot.

11. GCC161 Build Support
   Clover should build cleanly with the modern GCC161 toolchain, with reproducible build commands, clean output generation, no stale binary reuse and proper Release/Debug packaging.

12. Strict Kext Injection Safety
   Clover should inject only valid kext bundles, reject AppleDouble files, dotfiles and invalid metadata, avoid duplicate CFBundleIdentifier injection and preserve the correct injection order.

13. Dynamic PCI and Device Discovery
   Clover should detect PCI roots, bridges and device paths dynamically instead of assuming fixed names like PCI0, PC00 or PC02. This is essential for modern multi-root platforms such as Z890 and workstation boards.

14. Improved Power Management Foundation
   Clover should provide better platform preparation for CPU power management, including correct ARTFrequency, TSC, FSBFrequency, CPU topology, plugin-type support and compatibility with CPUFriend-style tuning.

15. Universal Stability First
   Clover must remain a universal bootloader. No improvement should be forced globally when it belongs only to one chipset, CPU family, GPU generation or macOS version. config.plist remains the final authority.

c2DpdKc.png

xQFBOkx.png

  • Thanks 1
×
×
  • Create New...