I had previously set up several dual-boot Fedora Linux/Win7 systems, but now had the challenge of doing the same for MacOS as well..

This is absolutely not the place for any discussion on the ramifications of the ‘Hackintosh’ movement, but it will suffice to use that terrible phrase ‘Google is your friend..’..

The Clover/MacOS instance was on its own disk, and this meant that (hopefully) this would not interfere with Grub/Linux.   I tested that install by booting to the POST/BIOS UEFI boot menu (typically F9) and selecting the Clover/MacOS disk.

I found some existing dual-boot examples, but these seemed to be quite out-of-date, and so used my existing GRUB2 Win7 chainloader as a starting point.

The simplest solution I found is to use grub-customizer to create and edit the necessary entry, and this takes care of formatting and inclusion in grub.cfg etc..

In the main grub-customizer window, select Edit/New, and then select Type Chainloader and give it a suitable name (I used ‘Boot Clover’) and then ignore the ‘error’ message, and then under Partition select the efi partition where Clover resides. This should present as ‘EFI/vfat‘.

In my example, the efi partition is on the fifth physical disk, partition 1..

You should then see, under Boot sequence:

set root='(hd4,1)'
search --no-floppy --fs-uuid --set < UUID >
drivemap -s (hd0) ${root}
chainloader +1

Edit this to remove the line starting with drivemap, and edit the chainloader +1 line to
chainloader /EFI/CLOVER/CLOVERX64.efi

Then hit OK, and the new entry should show up as ‘menuentry / script:custom‘
Then in the main window hit Save, and test by rebooting..

Robert Gadsdon.  June 1, 2019.