Jief_Machak Posted October 2, 2020 Share Posted October 2, 2020 @Matgen84 When I sent an EFI for test, it's not built with "buildme", but yes, you can. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739033 Share on other sites More sharing options...
Matgen84 Posted October 2, 2020 Share Posted October 2, 2020 (edited) 9 minutes ago, Jief_Machak said: @Matgen84 When I sent an EFI for test, it's not built with "buildme", but yes, you can. @Jief_Machak Its just a question. I try the latest two files posted here. They are same as previous in my EFI test or there are different ! Edited October 2, 2020 by Matgen84 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739036 Share on other sites More sharing options...
Jief_Machak Posted October 2, 2020 Share Posted October 2, 2020 @Matgen84 Just some problems in some cases. If it's working for you, you can stay like this for now. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739037 Share on other sites More sharing options...
SavageAUS Posted October 2, 2020 Share Posted October 2, 2020 25 minutes ago, Jief_Machak said: Yes, @Slice found and fix the problem. It's committed. Care to share the newest files please? Ive also created a new repo for AMD int and invited you. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739039 Share on other sites More sharing options...
Matgen84 Posted October 2, 2020 Share Posted October 2, 2020 4 minutes ago, Jief_Machak said: @Matgen84 Just some problems in some cases. If it's working for you, you can stay like this for now. @Jief_Machak The efi files in my EFI test repo works fine with Big Sur. Yesterday, I try to boot Catalina 10.15.7 from USB installer: can boot but KP instant reboot at the last stage. I follow your advice: stay like this for now. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739040 Share on other sites More sharing options...
Jief_Machak Posted October 2, 2020 Share Posted October 2, 2020 @SavageAUS I said to iCanaro that I'll help with AMD in few days. You can compile from source to get the latest. But no new features for you if it's already working. 3 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739041 Share on other sites More sharing options...
Jief_Machak Posted October 2, 2020 Share Posted October 2, 2020 @Matgen84 Yes, give me few days and then we'll find these problems. 2 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739043 Share on other sites More sharing options...
SavageAUS Posted October 2, 2020 Share Posted October 2, 2020 3 minutes ago, Jief_Machak said: @SavageAUS I said to iCanaro that I'll help with AMD in few days. You can compile from source to get the latest. But no new features for you if it's already working. Ah no worries. On AMD I get stuck at EXITBS:START and if slice fixed that I should be good to go. One last thing.....for now. How to build clover from source? And where will the required files be located? 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739044 Share on other sites More sharing options...
Matgen84 Posted October 2, 2020 Share Posted October 2, 2020 Just now, SavageAUS said: Ah no worries. On AMD I get stuck at EXITBS:START and if slice fixed that I should be good to go. One last thing.....for now. How to build clover from source? And where will the required files be located? Voila latest committed files ! CLOVERX64.debug CLOVERX64.efi 2 3 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739045 Share on other sites More sharing options...
iCanaro Posted October 2, 2020 Share Posted October 2, 2020 2 hours ago, SavageAUS said: Ah no worries. On AMD I get stuck at EXITBS:START and if slice fixed that I should be good to go. I'd be grateful if you post your config, so I check if I'm using kernel patches properly Clover 5120 on my X570 msi unify was the first ever that managed to start, now with 5122 ocint I can't and I'm trying to figure out if it's me who makes some gross mistake or if it's Clover 1 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739050 Share on other sites More sharing options...
SavageAUS Posted October 2, 2020 Share Posted October 2, 2020 23 minutes ago, iCanaro said: I'd be grateful if you post your config, so I check if I'm using kernel patches properly Clover 5120 on my X570 msi unify was the first ever that managed to start, now with 5122 ocint I can't and I'm trying to figure out if it's me who makes some gross mistake or if it's Clover I’ll post it soon to this reply. I don’t even know if mine is correct yet but I get clover boot screen then stuck. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739051 Share on other sites More sharing options...
iCanaro Posted October 2, 2020 Share Posted October 2, 2020 (edited) even with last Clover attached by Matgen84 I'm getting stuck here PS: on the AMD hack https://mega.nz/file/KuYQ2ZzY#WlIljeQTwac-31NU7XYgvXf--jcWx9cjze-dqMl9Pg8 Edited October 2, 2020 by iCanaro 1 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739052 Share on other sites More sharing options...
Guest Posted October 2, 2020 Share Posted October 2, 2020 (edited) 35:550 0:021 - [00]: algrey - commpage_populate -remove rdmsr :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 35:601 0:051 - [01]: algrey - cpu_topology_sort -disable _x86_validate_topology :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 35:654 0:052 - [02]: algrey - cpuid_set_cache_info - cpuid 0x8000001D instead 0 - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 35:729 0:075 - [03]: algrey - cpuid_set_cache_info - cpuid 0x8000001D instead 0 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x | MatchBuild: no] ==> allowed by OS 35:781 0:051 - [04]: algrey - cpuid_set_cache_info - cpuid 0x8000001D instead 4 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 35:834 0:052 - [05]: algrey - cpuid_set_cache_info - don't set cpuid_cores_per_package :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 35:912 0:078 - [06]: algrey - - skip cpuid_cores_per_package test -10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 35:962 0:049 - [07]: algrey - - skip cpuid_cores_per_package test :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x | MatchBuild: no] ==> allowed by OS 36:013 0:051 - [08]: algrey - cpuid_set_generic_info - remove wrmsr :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:088 0:074 - [09]: algrey - cpuid_set_generic_info - set microcode=186 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:140 0:052 - [10]: algrey - cpuid_set_generic_info - set flag=1 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:192 0:051 - [11]: algrey - cpuid_set_generic_info - disable check to allow leaf7 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:313 0:121 - [12]: algrey - cpuid_set_info - GenuineIntel to AuthenticAMD :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:366 0:052 - [13]: algrey - cpuid_set_cpufamily - force CPUFAMILY_INTEL_PENRYN :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:419 0:052 - [14]: algrey - cpuid_set_info - jmp to calculations and set cpuid_cores_per_package - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 36:497 0:078 - [15]: algrey - cpuid_set_info - cores and threads calculations - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 36:549 0:051 - [16]: algrey - cpuid_set_info - ryzen cores and logicals count - part 1 - 10.13 :: [OS: 10.13.6 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 36:602 0:052 - [17]: algrey - cpuid_set_info - ryzen cores and logicals count - part 1 - 10.14 :: [OS: 10.13.6 | MatchOS: 10.14.x | MatchBuild: no] ==> not allowed by OS 36:677 0:075 - [18]: algrey - cpuid_set_info - ryzen cores and logicals count - part 2 :: [OS: 10.13.6 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 36:728 0:051 - [19]: algrey - cpuid_set_info - ryzen cores and logicals count - part 2 :: [OS: 10.13.6 | MatchOS: 10.14.x | MatchBuild: no] ==> not allowed by OS 36:780 0:051 - [20]: algrey - cpuid_set_info - ryzen cores and logicals count - part 3 - 10.13 :: [OS: 10.13.6 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 36:856 0:076 - [21]: algrey - cpuid_set_info - ryzen cores and logicals count - part 3 - 10.14 :: [OS: 10.13.6 | MatchOS: 10.14.x | MatchBuild: no] ==> not allowed by OS 36:908 0:052 - [22]: algrey - cpuid_set_info - ryzen cores and logicals count - part 4 - 10.13 :: [OS: 10.13.6 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 36:961 0:052 - [23]: algrey - cpuid_set_info - ryzen cores and logicals count - part 4 - 10.14 :: [OS: 10.13.6 | MatchOS: 10.14.x | MatchBuild: no] ==> not allowed by OS 37:037 0:075 - [24]: algrey - i386_init - remove rdmsr (x3) :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 37:088 0:051 - [25]: algrey - tsc_init - remove Penryn check to execute default case 10.14.1-.3 :: [OS: 10.13.6 | MatchOS: 10.14.1, 10.14.2, 10.14.3 | MatchBuild: no] ==> not allowed by OS 37:142 0:054 - [26]: algrey - tsc_init - remove Penryn check to execute default case :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 37:218 0:075 - [27]: algrey - tsc_init - grab DID and FID from MSR :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 37:268 0:050 - [28]: algrey - tsc_init - skip msr_flex_ratio test and go grab FSBFrequency from EFI :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 37:323 0:054 - [29]: algrey - lapic_init - remove version check and panic - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 37:397 0:074 - [30]: algrey - lapic_init - remove version check and panic :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x | MatchBuild: no] ==> allowed by OS 37:448 0:051 - [31]: algrey - lapic_interrupt - skip checks and prevent panic - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 37:500 0:051 - [32]: algrey - lapic_interrupt - skip checks and prevent panic :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x | MatchBuild: no] ==> allowed by OS 37:574 0:074 - [33]: algrey - mtrr_update_action - fix PAT :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS For AMD users, check in your debug log if you see kernel patches allowed or not.. but problem in my case is different and maybe related in a not proper efi driver..patches I need to boot are allowed. System hangs in early stage..and it seems a similar problem AMD (trx40) users have had in the past with opencore Edited October 2, 2020 by Guest Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739058 Share on other sites More sharing options...
JorgeMax Posted October 2, 2020 Share Posted October 2, 2020 5 hours ago, Matgen84 said: Voila latest committed files ! CLOVERX64.debug CLOVERX64.efi The release version is no longer freezing on "EXITBS: STAR T" Normal startup in Mojave and Big Sur My processor not yet identified Thank you @Sliceand @Jief_Machak 4 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739061 Share on other sites More sharing options...
SavageAUS Posted October 2, 2020 Share Posted October 2, 2020 1 hour ago, JorgeMax said: The release version is no longer freezing on "EXITBS: STAR T" Normal startup in Mojave and Big Sur My processor not yet identified Thank you @Sliceand @Jief_Machak Can you share your system specs and EFI please. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739062 Share on other sites More sharing options...
jsl2000 Posted October 2, 2020 Share Posted October 2, 2020 2 hours ago, fabiosun said: 35:550 0:021 - [00]: algrey - commpage_populate -remove rdmsr :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 35:601 0:051 - [01]: algrey - cpu_topology_sort -disable _x86_validate_topology :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 35:654 0:052 - [02]: algrey - cpuid_set_cache_info - cpuid 0x8000001D instead 0 - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 35:729 0:075 - [03]: algrey - cpuid_set_cache_info - cpuid 0x8000001D instead 0 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x | MatchBuild: no] ==> allowed by OS 35:781 0:051 - [04]: algrey - cpuid_set_cache_info - cpuid 0x8000001D instead 4 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 35:834 0:052 - [05]: algrey - cpuid_set_cache_info - don't set cpuid_cores_per_package :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 35:912 0:078 - [06]: algrey - - skip cpuid_cores_per_package test -10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 35:962 0:049 - [07]: algrey - - skip cpuid_cores_per_package test :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x | MatchBuild: no] ==> allowed by OS 36:013 0:051 - [08]: algrey - cpuid_set_generic_info - remove wrmsr :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:088 0:074 - [09]: algrey - cpuid_set_generic_info - set microcode=186 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:140 0:052 - [10]: algrey - cpuid_set_generic_info - set flag=1 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:192 0:051 - [11]: algrey - cpuid_set_generic_info - disable check to allow leaf7 :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:313 0:121 - [12]: algrey - cpuid_set_info - GenuineIntel to AuthenticAMD :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:366 0:052 - [13]: algrey - cpuid_set_cpufamily - force CPUFAMILY_INTEL_PENRYN :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 36:419 0:052 - [14]: algrey - cpuid_set_info - jmp to calculations and set cpuid_cores_per_package - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 36:497 0:078 - [15]: algrey - cpuid_set_info - cores and threads calculations - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 36:549 0:051 - [16]: algrey - cpuid_set_info - ryzen cores and logicals count - part 1 - 10.13 :: [OS: 10.13.6 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 36:602 0:052 - [17]: algrey - cpuid_set_info - ryzen cores and logicals count - part 1 - 10.14 :: [OS: 10.13.6 | MatchOS: 10.14.x | MatchBuild: no] ==> not allowed by OS 36:677 0:075 - [18]: algrey - cpuid_set_info - ryzen cores and logicals count - part 2 :: [OS: 10.13.6 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 36:728 0:051 - [19]: algrey - cpuid_set_info - ryzen cores and logicals count - part 2 :: [OS: 10.13.6 | MatchOS: 10.14.x | MatchBuild: no] ==> not allowed by OS 36:780 0:051 - [20]: algrey - cpuid_set_info - ryzen cores and logicals count - part 3 - 10.13 :: [OS: 10.13.6 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 36:856 0:076 - [21]: algrey - cpuid_set_info - ryzen cores and logicals count - part 3 - 10.14 :: [OS: 10.13.6 | MatchOS: 10.14.x | MatchBuild: no] ==> not allowed by OS 36:908 0:052 - [22]: algrey - cpuid_set_info - ryzen cores and logicals count - part 4 - 10.13 :: [OS: 10.13.6 | MatchOS: 10.13.x | MatchBuild: no] ==> allowed by OS 36:961 0:052 - [23]: algrey - cpuid_set_info - ryzen cores and logicals count - part 4 - 10.14 :: [OS: 10.13.6 | MatchOS: 10.14.x | MatchBuild: no] ==> not allowed by OS 37:037 0:075 - [24]: algrey - i386_init - remove rdmsr (x3) :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 37:088 0:051 - [25]: algrey - tsc_init - remove Penryn check to execute default case 10.14.1-.3 :: [OS: 10.13.6 | MatchOS: 10.14.1, 10.14.2, 10.14.3 | MatchBuild: no] ==> not allowed by OS 37:142 0:054 - [26]: algrey - tsc_init - remove Penryn check to execute default case :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 37:218 0:075 - [27]: algrey - tsc_init - grab DID and FID from MSR :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 37:268 0:050 - [28]: algrey - tsc_init - skip msr_flex_ratio test and go grab FSBFrequency from EFI :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS 37:323 0:054 - [29]: algrey - lapic_init - remove version check and panic - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 37:397 0:074 - [30]: algrey - lapic_init - remove version check and panic :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x | MatchBuild: no] ==> allowed by OS 37:448 0:051 - [31]: algrey - lapic_interrupt - skip checks and prevent panic - 10.15 :: [OS: 10.13.6 | MatchOS: 10.15.x | MatchBuild: no] ==> not allowed by OS 37:500 0:051 - [32]: algrey - lapic_interrupt - skip checks and prevent panic :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x | MatchBuild: no] ==> allowed by OS 37:574 0:074 - [33]: algrey - mtrr_update_action - fix PAT :: [OS: 10.13.6 | MatchOS: 10.13.x, 10.14.x, 10.15.x | MatchBuild: no] ==> allowed by OS For AMD users, check in your debug log if you see kernel patches allowed or not.. but problem in my case is different and maybe related in a not proper efi driver..patches I need to boot are allowed. System hangs in early stage..and it seems a similar problem AMD (trx40) users have had in the past with opencore Can you show me the location of your Kernel/Patches or KernelToPatch in Clover's config.plist ? 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739067 Share on other sites More sharing options...
SavageAUS Posted October 2, 2020 Share Posted October 2, 2020 This is my config.plist for AMD. I have not checked if the patches load yet. config.plist 1 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739068 Share on other sites More sharing options...
Guest Posted October 2, 2020 Share Posted October 2, 2020 36 minutes ago, jsl2000 said: Can you show me the location of your Kernel/Patches or KernelToPatch in Clover's config.plist ? Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739070 Share on other sites More sharing options...
jsl2000 Posted October 2, 2020 Share Posted October 2, 2020 1 minute ago, fabiosun said: Thanks. Do I need modify Kernel Patches for AMD CPUs from OpenCore ? Because in previous version of Clover without modification it can not boot at all. 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739071 Share on other sites More sharing options...
MICKHAEL Posted October 2, 2020 Share Posted October 2, 2020 (edited) Quote hello all brave people. i have some issues with Big Sur beta 8 boot from USB... using same working EFI from Catalina/ Big Sur Beta 2 maybe someone have idea what could be and could give me a direction.. ACPI errors what do I miss? Edited October 2, 2020 by MICKHAEL Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739072 Share on other sites More sharing options...
jmacie Posted October 2, 2020 Share Posted October 2, 2020 x99 not working on BigSur Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739073 Share on other sites More sharing options...
chris1111 Posted October 2, 2020 Share Posted October 2, 2020 @Jief_Machak Test Boot Laptop HP ProBook 6570b Everything's work like OpenCore I see no difference 2 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739078 Share on other sites More sharing options...
Jief_Machak Posted October 2, 2020 Share Posted October 2, 2020 Hi everyone. Is there anyone here who - is not sure on which file his EFI bios is booting - is annoyed because clover and oc efi has to be named CloverX64.efi and OpenCore.efi. Hence, you can't easily see the version - is tired of renaming efi files to try different version (that's the consequences of the previous point). - finds not great the need to have a bootable Clover/OC backup on a USB stick in case something goes wrong at update or config modification. - is also tired to often rename Clover folders to use them. If you're interested by a definitive solution to these annoyance, just click the confused icon on this post !I have something for you. 1 3 10 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739082 Share on other sites More sharing options...
iCanaro Posted October 2, 2020 Share Posted October 2, 2020 I'm interested in having a version of Clover that starts any intel hack or AMD I'm not a developers or coders, I don't have capabilities with the use of github as a developer: I'm a simple enthusiast who has different hardware in his hands on which to try the versions in development 4 1 1 Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739083 Share on other sites More sharing options...
chris1111 Posted October 2, 2020 Share Posted October 2, 2020 For my part I am quite correct with this one that I have been testing for two days, I will stay like this and maybe come back to see if there is anything better. I'm trying to do my part but it doesn't seem very helpful. Good luck every one Spoiler Link to comment https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page/924/#findComment-2739088 Share on other sites More sharing options...
Recommended Posts