Jief_Machak Posted October 5, 2020 Author Share Posted October 5, 2020 7 hours ago, naiclub said: I will use yours. You mean, using the BootloadeChooser ? Link to comment Share on other sites More sharing options...
naiclub Posted October 5, 2020 Share Posted October 5, 2020 51 minutes ago, Jief_Machak said: You mean, using the BootloadeChooser ? Yes, and I use it. It's better than -opencore without bios blocked. Link to comment Share on other sites More sharing options...
D-an-W Posted October 6, 2020 Share Posted October 6, 2020 @Jief_Machak can we now use the most recent Clover commits with your BOOTx64.efi? Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 6, 2020 Author Share Posted October 6, 2020 2 hours ago, D-an-W said: can we now use the most recent Clover commits with your BOOTx64.efi? Yes sure. I do. Link to comment Share on other sites More sharing options...
D-an-W Posted October 11, 2020 Share Posted October 11, 2020 @Jief_Machak its trivial but there are a couple of Typos in the menu... Link to comment Share on other sites More sharing options...
D-an-W Posted October 13, 2020 Share Posted October 13, 2020 @Jief_Machak any plans to remove the text that is seen after choosing the boot option (Sort of a verbose mode)? Link to comment Share on other sites More sharing options...
naiclub Posted October 15, 2020 Share Posted October 15, 2020 On 10/14/2020 at 3:23 AM, D-an-W said: @Jief_Machak any plans to remove the text that is seen after choosing the boot option (Sort of a verbose mode)? Just delete -V, the message is no longer showing. Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 15, 2020 Author Share Posted October 15, 2020 1 minute ago, naiclub said: @Jief_Machak any plans to remove the text that is seen after choosing the boot option (Sort of a verbose mode)? If you're speaking of BootLoaderChooser, yes, there 3 lines showing which Efi file is loading. That's DEBUG version and I may have forgotten to remove them in Release version. I'll do that soon. 2 Link to comment Share on other sites More sharing options...
D-an-W Posted October 16, 2020 Share Posted October 16, 2020 Hi @Jief_Machak just tried to use Clover r5125 but got this warning, it's in the same folder as the previous three versions I have used BLC with...... Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 17, 2020 Author Share Posted October 17, 2020 (edited) 14 hours ago, D-an-W said: Hi @Jief_Machak just tried to use Clover r5125 but got this warning, it's in the same folder as the previous three versions I have used BLC with...... EDIT : never mind, I found the problem. Edited October 17, 2020 by Jief_Machak Link to comment Share on other sites More sharing options...
D-an-W Posted October 17, 2020 Share Posted October 17, 2020 Missed what you said, is it a Clover or BLC issue? Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 17, 2020 Author Share Posted October 17, 2020 Just now, D-an-W said: Missed what you said, is it a Clover or BLC issue? I think it's a RELEASE compilation problem of Clover. Link to comment Share on other sites More sharing options...
D-an-W Posted October 17, 2020 Share Posted October 17, 2020 Ok thanks, I do compile Clover myself as I have to edit a line. Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 17, 2020 Author Share Posted October 17, 2020 3 minutes ago, D-an-W said: I have to edit a line. Which line ? Do you just remove the line needed for BLC to know if Clover is relocatable ? Link to comment Share on other sites More sharing options...
D-an-W Posted October 17, 2020 Share Posted October 17, 2020 I just uncomment out this line... ReplaceName(dsdt + BrdADR, BridgeSize, device_name[9], "ARPT"); Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 17, 2020 Author Share Posted October 17, 2020 It's now fixed in master branch. Fetch and pull Clover and it should be ok. 1 Link to comment Share on other sites More sharing options...
D-an-W Posted October 17, 2020 Share Posted October 17, 2020 Just tried again with updated Clover, still seems the same... Link to comment Share on other sites More sharing options...
Matgen84 Posted October 17, 2020 Share Posted October 17, 2020 14 minutes ago, D-an-W said: Just tried again with updated Clover, still seems the same... Just a opinion: Bootloader Chooser doesn't recognize clover folder. Maybe, it's case sensitive: try \EFI\CLOVER instead of \EFI\Clover. Rename CLOVERx64 r5125.efi to CLOVERx64_r5125.efi 1 1 1 Link to comment Share on other sites More sharing options...
D-an-W Posted October 17, 2020 Share Posted October 17, 2020 I did think of that but r5124, 23 & 22 worked just fine with the same folder name. Link to comment Share on other sites More sharing options...
D-an-W Posted October 17, 2020 Share Posted October 17, 2020 Renamed Clover to CLOVER and r5125 works now (Named CLOVERx64 r5125.efi), thanks for encouraging me to try it @Matgen84 2 Link to comment Share on other sites More sharing options...
MacKonsti Posted December 11, 2020 Share Posted December 11, 2020 (edited) On 10/3/2020 at 4:21 PM, jsl2000 said: This new BootX64.efi can go to text menu and worked perfectly now after re-edit my EFI structure as following: Thanks for the visual confirmation @jsl2000 I really needed this to understand ! Cheers mate. @Jief_Machak thank you again for your great work and contribution. Allow me to post a question about BootloaderChooser: Its main purpose is to test multiple configs of the SAME Clover and/or OpenCore configurations only? Or can we also test different RELEASES of Clover or OpenCore? If the latter is valid, can you please suggest a working method/structure of folders? Scenario: Say that I have a working Clover r5119 and that I want to test out r5123 or r5127 but because of a non-found bug yet, despite same config.plist I cannot boot from r5127. The reason for keeping r5119 is because I know it boots perfectly. Perhaps swapping between a single Clover and OpenCore build is easier, like the above image. Thanks for your brief confirmation Edited December 11, 2020 by MacKonsti Link to comment Share on other sites More sharing options...
HcNguyen111 Posted December 26, 2020 Share Posted December 26, 2020 On 12/12/2020 at 2:16 AM, MacKonsti said: Thanks for the visual confirmation @jsl2000 I really needed this to understand ! Cheers mate. @Jief_Machak thank you again for your great work and contribution. Allow me to post a question about BootloaderChooser: Its main purpose is to test multiple configs of the SAME Clover and/or OpenCore configurations only? Or can we also test different RELEASES of Clover or OpenCore? If the latter is valid, can you please suggest a working method/structure of folders? Scenario: Say that I have a working Clover r5119 and that I want to test out r5123 or r5127 but because of a non-found bug yet, despite same config.plist I cannot boot from r5127. The reason for keeping r5119 is because I know it boots perfectly. Perhaps swapping between a single Clover and OpenCore build is easier, like the above image. Thanks for your brief confirmation Just put multiple Clover.efis into the same CLOVER folder with different filenames. 2 Link to comment Share on other sites More sharing options...
MacKonsti Posted December 26, 2020 Share Posted December 26, 2020 Thanks for the tip @HcNguyen111 but remember, the few EFI drivers needed themselves won't be changed, they have to be common between versions... so better use the common denominator (lowest version tested) I guess, unless a bug was fixed in some driver. But that's a good tip, thanks mate. My only concern is that if we want to use r5123-1 without OcQuirks and r5127 with OcQuirks, the presence of some files in /drivers/UEFI/ are going to be messy... Link to comment Share on other sites More sharing options...
Jief_Machak Posted December 26, 2020 Author Share Posted December 26, 2020 New clover ignore drivers AptioMemoryFix.efi. So you can leave it there for 5123. The added Quirks section won't bother 5123, it'll just be ignored. Just remember that Clover before 5126 (not sure of the number) can only start in a folder named CLOVER (uppercase and lowercase shouldn't matter but there maybe a bug in BootloaderChooser, as I read earlier). So you can have a folder named CLOVER for 5123 and CLOVER5127 (or CLOVERfoobar or whatever) for 5127, if you need difference in drivers or kexts. 4 Link to comment Share on other sites More sharing options...
D-an-W Posted June 26, 2021 Share Posted June 26, 2021 Is anyone still using this and managed to get it to work with OpenCore, when I try I just get a prompt saying **Press any Key** and it then returns to the BLC menu? Link to comment Share on other sites More sharing options...
Recommended Posts