Search the Community

For those interested, currently the new Clover manages to start mojave, catalina and big sur beta 9 correctly of course it is all "work in progress" and in my opinion the situation can only improve for the AMD user. Having over OC also Clover on platforms like my X570, which until recently could not even start, is very positive. Two boot loaders are better than one 😉 Clover 5134 5124 config-BS.plist.zip config-moj_cata.plist.zip config-CATA_MOJ_26.plist.zip config-CATA_BS_29.plist.zip config-CATA_BS_38.plist.zip 20-10-2020 -> CloverV2-5125-e80852a82 -> https://www.macos86.it/files/file/89-clover-release-beta/ Clover_Patch_29-moj_cat_bs.plist.zipClover_Patch_38-moj_cat_bs.plist.zip boot mojave, catalina big sur Clover_Patch_35plus-moj_cat_bs.plist.zip small evolution of the previous 3 plists Clover_Patch_38-hs_moj_cat_bs.plist.zipClover_Patch_35plus-hs-moj_cat_bs.plist.zipClover_Patches_30-moj_cata_bs.plist.zip correct config 35plus as there was a kext to patch aquantia, it did nothing but it was useless and superfluous Clover_Patch_35+-hs-moj_cat_bs.plist.zip 23-10-2020 Clover_17H_Patches38_MatchOS_Empty_X_All.plist.zip This is the KernelToPatch that I have decided to adopt for the time being is that of OC converted for Clover. The MatchOS field where they were invoked 10.13.x,10.14.x,10.15.x,11.x were left empty while I defined those where one or two macOS is invoked Limit has been commented on and not converted to RangeFind