Clover Efi Bootloader Iso

[Auriville Cha]

HiThanks for this detailed written guide and wonderful method!

I am new to clover and I am using this method from last 1 month, it was working absolutely well, but suddenly blue screen appeared and I can no longer boot using clover. I reinstalled windows in SSD,I made new clover stick and tried. I succeeded to boot from my nvme ssd on pcie x4 adapter again using clover, but I am getting this error in clover that (PXE-E16: NO OFFER RECEIVED). I did not get this!

Please find the attached image and help me out to resolve this problem.

@Vishwa

Hello and welcome to the forums, PXE is normally a bios setting please check that is is disabled in your computers bios.

If it is already disabled then you may have an issue within your clover configuration file. you may need to disable pxe option from the boot list within the config.plist

I hope this helps and good luck.

Unfortunately I am unable to get past "*** Scan Entries " in Clover. Tried searching the thread and a few others have had this issue - but could not find the solution.

Update: I have tried an alternative imagine of Clover however I still hang at " Scan Entries ****". I have tried disabling all SATA devices but it still hangs at this.

Continuing my post directly above -

I had difficulty with http cvad-mac.narod ru / index / bootdiskutility_exe / 0-5 but finally managed to download BDU_v2.1.2020.028b.zip!

Its instructions are not entirely clear. If I run the exe, what happens? Will it give me the opportunity to install Clover onto a USB stick?

Also - I am not going to use this or Clover to boot a Mac. I intend to use Clover to make a Dell Optiplex 3010 or 7010 boot from a NVMe M.2 SSD that is inserted into an adapter which in turn is plugged into a PCIe (x4) slot.

In such case, what should be my choices when I run BDutility.exe?

BUT MAKING PROGRESS !! Thanks.

I just succeeded in creating a Clover USB key, and in installing Windows 11, Linux Mint and Kali Linux on a non bootable NVMe SSD in a legacy system.

The NVMe SSD is installed on a 2009 legacy Gigabyte motherboard with an AMD Phenom processor through a PCIe adaptor.

I used Bootdisk Utility v.023 and Clover v.4961 to create the Clover key.

Everything works great !

@glnz The BDU from cvad is an installer it will install clover to a usb for you and attempt to configure it for the system you are installing it from, so i hope that is the same machine you wish to boot.

follow my add-on post as well as the op re what to select. I have used this to boot several non uefi bios systems from an nvme. how this works is you install clover to the usb, clover runs first every time you start up the pc and clover then passes off to the nvme for normal windows.

one of mine did this also but after waiting a bit it failed over to legacy(non uefi) and worked anyway. as of the moment i have no idea how to address this issue and i would certainly be interested if someone figures it out.

@glnz The BDU from cvad is an installer it will install clover to a usb for you and attempt to configure it for the system you are installing it from, so i hope that is the same machine you wish to boot.

follow my add-on post as well as the op re what to select. I have used this to boot several non uefi bios systems from an nvme. how this works is you installer clover to the usb clover runs first every time you start up the pc and clover then passes off to the nvme for normal windows.

This is incorrect clover is a full bootloader and was designed for osx, it can see any partition format including ext4 I have dual booted with Ubuntu via clover myself. Please ensure you add the partition guid to the config.plist file. If I recall you need to add it under the boot section.

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.

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

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.

Anyway, my question is if there's anything else I can try to chainload these bootloaders together to work like Chimera, or if there's another way to boot directly into OS X from GRUB.

The last I checked, Chimera was strictly a BIOS-mode boot loader. Because GRUB can't change from EFI-mode to BIOS-mode (or vice-versa), this implies that your GRUB is (or at least was) also installed in BIOS mode. If you've switched GRUB from BIOS-mode to EFI-mode, that's a critical detail.

Clover, OTOH, is more complex. Its core is as an EFI-mode boot manager that launches OS X's EFI-mode boot loader; however, Clover includes a complete EFI implementation that runs like a BIOS-mode boot loader -- essentially, an EFI that runs as software on a BIOS-mode computer, rather than as firmware. Thus, Clover can run on either BIOS-mode computers or on EFI-based computers. If you've made no changes to GRUB, you will be able to launch Clover from GRUB only if you've also installed Clover's BIOS-mode EFI "emulator" software; and then you'll need to launch Clover much as you had been launching Chameleon. Your first couple of Clover examples (the ones that referenced bootx64.efi) would work on an EFI-based computer running an EFI-mode version of GRUB, but will not work if you're using a BIOS-mode computer. Your final example (with the chainloader +1 line) is for a BIOS-mode boot, and so might work if you've installed Clover's BIOS-mode components.

Stepping back a bit, you may want to examine your other OS components, as well as your computer's capabilities. If your computer was introduced in mid-2011 or later, it's probably EFI-based; but if it's older, it's probably a BIOS-only machine. Ubuntu is easy to switch between boot modes, providing you know how to install suitable boot loaders for each mode. Windows is a little trickier, since it ties its partition table type to its boot mode -- Windows boots in BIOS mode only from MBR disks and in EFI mode only from GPT disks. (I've heard of some exceptions to this rule, but they're pretty exotic.) Thus, switching the Windows boot mode requires changing the partition table and installing a new boot loader.

Between all these issues, there's a lot of complexity in your triple-boot setup, and you've omitted the most important details -- namely, the partition table types and boot modes of most of your OSes (although I've inferred some of that information). This makes it difficult to offer specific advice. One point, though: Clover configuration and setup is well beyond the scope of this site. If you want to use GRUB as your primary boot manager, though, you must pay attention to your boot mode and install follow-on boot loaders in the same mode (BIOS/CSM/legacy vs. EFi/UEFI) that GRUB uses.

Given your new information, there are several possible ways to proceed. One is, as you suggest, to convert both Windows and Ubuntu to boot in EFI mode. Another is a hybrid setup. One way to do this would be as follows:

You may need some more tweaking at this point, but that's the basic outline of it. In this configuration, rEFInd will enable you to boot Ubuntu (in EFI mode), Clover (in EFI mode), or Windows (in BIOS mode); and Clover should boot OS X (and may show options for Windows and/or Linux, too).

Something similar should be possible with Clover as the primary boot manager; however, with this setup, Clover will show options for OS X (in EFI mode), GRUB (in BIOS mode; or in EFI mode if you install the grub-efi package), and Windows (in BIOS mode). I don't know the exact steps you'd take to set this up. Whether you prefer Clover or rEFInd as your primary boot menu is a matter of personal preference.

Your plan to convert everything to EFI mode is also workable, but will involve more effort and slightly more risk in the short term. Once set up, you could use GRUB, Clover, or rEFInd as your primary boot manager. If you used GRUB or rEFInd as the primary boot manager, you'd still need Clover to boot OS X; and if you used Clover as the primary boot manager, you'd need to use GRUB or rEFInd to boot Ubuntu.

You could use rEFInd on a USB flash drive or CD-R to play with some of these options to see how they'd work, with negligible risk to your configuration, since you'll make no changes to your hard disk.

In sum, you've got a lot of options for how to proceed, with no clear winner in terms of ease of use or complexity -- they all should work pretty well, but you'll need two boot managers for at least one OS boot path.

How would I go about adding the hard drive to the clover boot list? Or have it autodetected? In grub2, for example, you can just tell it to reconfigure. In windows, you can use BCDEdit. But for Clover, I am lost.

This has been a slightly longer post, but I hope it is useful. The steps involved can take a while, but they are quite simple to follow. As always, if you need me to clarify anything, let me know in the comments.

Hey Hamish,

Thanks for the wonderful guide. I am currently stuck on the step of adding the .efi driver to the USB. Once I use Rufus to install the image of refind on my USB my windows 10 no longer recognizes the USB stick.

I think this can be resolved by either using the Windows Command Prompt, or using a Linux live disk. Are you comfortable with either of these options? If it comes to it, I could just upload an image of my USB stick that has the driver pre-installed.

3a8082e126