Clover

Clover EFI is a boot loader developed to boot OS X (Hackintoshes), Windows and Linux in legacy or UEFI mode.

The main advantages of Clover are:

  • Emulate UEFI on legacy BIOS systems
  • Boot Linux kernels with EFISTUB support
  • Supports native resolution GUI on wide screens people commonly use today
  • Easy to use
  • Easily customizable

Installation

As Clover emulates a UEFI environment on BIOS systems, the steps for each type of system are similar.

UEFI Systems

Mount EFI system partition to /boot. This is the preferred method when directly booting an EFISTUB kernel from UEFI.

Generate initial ramdisk environment with mkinitcpio

Download Clover Bootable ISO from here.

Extract the archive Clover-*-X64.iso.7z and find the Clover-*-X64.iso file, mount it to a directory like /mnt/iso. It should be noted all file/folder names will be displayed in lower case in Linux, which is different from Windows and Mac OS.

Copy the whole /mnt/iso/efi folder to your EFI system partition. The tree for /boot should look likes the following

/boot/efi
/boot/efi/boot
/boot/efi/clover
/boot/initramfs-linux-fallback.img
/boot/initramfs-linux.img
/boot/vmlinuz-linux

BIOS Systems

Download the Clover Bootable ISO.

Extract the archive Clover-*-X64.iso.7z and find the Clover-*-X64.iso file, mount it to directory like /mnt/iso.

Merge Clover code with current Master and Partition Boot Records (assuming ESP is partition 1 of , change if necessary):

Mount the EFI system partition to /boot.

Copy the whole /mnt/iso/efi folder to your EFI system partition.

Copy the legacy bootloader to the EFI system partition:

Configuration

Configuration is done through an xml file config.plist under path from the UEFI partition.

A tool is now available to easily edit your config.plist in any OS: Cloud Clover Editor (CCE)

For the meaning of each key, please reference their wiki for custom entries. The key Volume should be the PARTUUID of the EFI partition and must be in upper case. The minimal initramfs in and the Linux kernel executable in are relative to the EFI partition. Backslashes should be used in accordance with EFI standards. For other arguments in , please reference EFISTUB and Kernel parameters#Parameter list.

In this example, the initramfs and kernel files are placed at the root of the EFI partition, at the same level as the efi directory. The EFI partition is mounted at /boot

chainload systemd-boot

If you need a bootloader for BIOS systems that follows The Boot Loader Specification, then systemd-boot can be pressed into service on BIOS systems. This is the configuration file needed make Clover chainload systemd-boot.

gollark: Only then can we achieve true safety.
gollark: This really vindicates my decision to write code which never allocates memory.
gollark: How useful.
gollark: Basically every classroom has a giant 4K touchscreen display with I think some sort of limited built-in computer system (I don't know how they can afford this), and they all get wired to rather outdated NUCs and used at 1080p with the touchscreen mostly ignored.
gollark: We always had smart boards and such but they generally got underutilized.

See also

This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.