To be honest, I'd advise against option B. I had the apfs.efi removed and ApfsDriverLoader-64.efi isntalled on 10.13.5, and it just worked fine. However, during the update to 10.13.6, after the second reboot Clover just simply stopped working. Apparently the ApfsDriverLoader-64.efi was unable to locate the apfs.efi on the system drive (maybe it was temporary unavailable or relocated during the update process), so the system could not boot. To add insult to injury, I was unable to boot using a Vanilla Clover on a USB drive unless i disabled the system drive (disabling the SATA drive in BIOS) completely, since it was also loading the ApfsDriverLoader from the system drive's EFI partition (even though it was not installed on the USB drive itself). As a last resort, I had to boot a Ubuntu using USB, mount the system drive EFI partition, remove the ApfsDiverLoader and reinstall the apfs.efi manually, so then I could boot and finish the installation.
So I'd say it is much safer to have the apfs.efi among the drivers instead of relying on ApfsDriverLoader to do the job.
I'm glad. Probably this was an issue with the specific Clover version I used or was caused by some other factor? Next time I'll try again. Surely though if this was a widespread problem, others would be reporting it by now.I had no problem updating with apfsdriverloader to 10.13.6
Same card here, at first the card functioned without and then after 13.5 it did not. My situation also needed to have CSM enabled in BIOS plus CSMVideoDxe-64 in Drivers64UEFIjust updated through the appstore whitout problems. but i have some questions.
Is the usb port limit patch needed if i have made a custom ssdt ?
another question: i own a gigabyte rx560 4gb oc from Gigabyte. is it possible to use this card without lilu and whatevergreen ?...
with lilu and whatevergreen it is working great. with the displayport and hdmi active.
without these kexts i got a blackscreen. thanks in advance.
Just confirming before I update that if I install latest Clover that I DO NOT need to copy over the new apfs file like I did on the .1,.2, etc., releases, correct? Thanks.