Jief_Machak Posted October 26, 2020 Share Posted October 26, 2020 37 minutes ago, Andres ZeroCross said: Sorry, i have pressed F2 in GUI CLOVER, but when i checked to EFI/CLOVER/misc,, there is no Preboot.log. The path is now {whatever folder clover efi is in}/misc Link to comment Share on other sites More sharing options...
kushwavez Posted October 26, 2020 Share Posted October 26, 2020 4 hours ago, Jief_Machak said: I didn't know that, but it's interesting. That said, you have a much simpler solution that will also bring you new possibilities : BootLoaderChooser (https://github.com/jief666/BootloaderChooser/releases) You put that BootX64.efi in EFI/Microsoft/Boot, rename it "bootmgfw.efi" if you need to. Next reboot, you'll have a text menu. Choose your Clover wherever is it. Next reboot you won't see that text menu unless you boot when a key kept pressed down. This allows you to have multiple Clover folder AND multiple Clover efi file inside each Clover folder. That's awesome for debugging and (or) testing! Also this cmd is very simple. Basically it's just modifying the original Windows bootloader config to not point to bootmgfw.efi, but to CLOVERX64.efi and it'll just load that. So the Windows bootloader will start first, then it'll load the Clover. Good thing that you can mess up the Clover or even delete that, Windows loader then will ignore the location and will load Windows instead automatically. Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 26, 2020 Share Posted October 26, 2020 3 minutes ago, kushwavez said: Basically it's just modifying the original Windows bootloader config to not point to bootmgfw.efi, but to CLOVERX64.efi and it'll just load that. It looks like that, but you still have to modify "bootmgfw.efi". The content of "bootmgfw.efi" will be the BootloaderChooser efi. 5 minutes ago, kushwavez said: So the Windows bootloader will start first The Windows bootloader starts first, but it's not Windows bootloader anymore. It's BootloaderChooser. 6 minutes ago, kushwavez said: Good thing that you can mess up the Clover or even delete that, Windows loader then will ignore the location and will load Windows instead automatically. Sorry, not too sure of the meaning. 1 Link to comment Share on other sites More sharing options...
kushwavez Posted October 26, 2020 Share Posted October 26, 2020 3 minutes ago, Jief_Machak said: It looks like that, but you still have to modify "bootmgfw.efi". The content of "bootmgfw.efi" will be the BootloaderChooser efi. The Windows bootloader starts first, but it's not Windows bootloader anymore. It's BootloaderChooser. Sorry, not too sure of the meaning. Oh sorry, it's not for that, it's for "bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi" in Windows. Link to comment Share on other sites More sharing options...
JorgeMax Posted October 26, 2020 Share Posted October 26, 2020 @Jief_Machakcould you check why these keys don't work when checked? Spoiler Thank you Link to comment Share on other sites More sharing options...
Slice Posted October 26, 2020 Share Posted October 26, 2020 Clean NVRAM where OpenCore tends to write "boot-args=...". This is wrong because this variable is not a business for a bootloader. In my case Verbose is this menu works fine. 1 Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 26, 2020 Share Posted October 26, 2020 2 hours ago, JorgeMax said: @Jief_Machakcould you check why these keys don't work when checked? Reveal hidden contents Thank you I didn't see Slice answer and I tried too. Works fine. @Slice Could we implement a warning ? Like "Your boot options will be ignored ?" Or "Would you like to delete OpenCore NVRAM boot options NVRAM ?" or else ? 1 Link to comment Share on other sites More sharing options...
iCanaro Posted October 26, 2020 Share Posted October 26, 2020 (edited) i wanted to point out these oddities that you see in the GUI on BigSur with Clover last commit https://github.com/CloverHackyColor/CloverBootloader/commit/c458db4acd9eabeafbf2a8c40fd152e076d6d894 Spoiler PS: but maybe it was the previous commit, I see new build if I compile Clover now i finish compiling and text Edited October 26, 2020 by iCanaro 1 Link to comment Share on other sites More sharing options...
JorgeMax Posted October 26, 2020 Share Posted October 26, 2020 1 hour ago, Slice said: Clean NVRAM where OpenCore tends to write "boot-args=...". This is wrong because this variable is not a business for a bootloader. In my case Verbose is this menu works fine. This "boot arguments" is defined in my Clover config.plist, not OpenCore If I mark the field for verbose mode, it does not work, and this is repeated in the other fields Link to comment Share on other sites More sharing options...
D-an-W Posted October 26, 2020 Share Posted October 26, 2020 @JorgeMax assuming you can boot into Big Sur using the Preboot option could I possibly see your EFI folder please (Minus serials of course)? Link to comment Share on other sites More sharing options...
JorgeMax Posted October 26, 2020 Share Posted October 26, 2020 9 minutes ago, D-an-W said: @JorgeMax assuming you can boot into Big Sur using the Preboot option could I possibly see your EFI folder please (Minus serials of course)? EFI.zip 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted October 26, 2020 Share Posted October 26, 2020 @iCanaro latest build c458db4acd9eabeafbf2a8c40fd152e076d6d894 is fine for me on AMD and Intel Spoiler 3 Link to comment Share on other sites More sharing options...
PG7 Posted October 26, 2020 Share Posted October 26, 2020 2 hours ago, SavageAUS said: @iCanaro latest build c458db4acd9eabeafbf2a8c40fd152e076d6d894 is fine for me on AMD and Intel how to compile commits? tanks Link to comment Share on other sites More sharing options...
iCanaro Posted October 26, 2020 Share Posted October 26, 2020 2 minutes ago, PG7 said: how to compile commits? tanks here CLOVERX64--5125--c458db4ac.efi.zip 1 Link to comment Share on other sites More sharing options...
iCanaro Posted October 26, 2020 Share Posted October 26, 2020 @PG7 they churned out another one here's the commit https://github.com/CloverHackyColor/CloverBootloader/commit/fafc50e3d07be49b55256c0efdbb4c2e424d93b4 CLOVERX64--5125--fafc50e3d.efi.zip 1 Link to comment Share on other sites More sharing options...
naiclub Posted October 26, 2020 Share Posted October 26, 2020 Good news for me now opencore no longer causes the bios to be locked. Many thanks to developers. Sorry, that's not a clover forum. 1 Link to comment Share on other sites More sharing options...
PG7 Posted October 26, 2020 Share Posted October 26, 2020 36 minutes ago, iCanaro said: here CLOVERX64--5125--c458db4ac.efi.zip this commit CLOVERX64--5125 - c458db4ac.efi has a probleme! repeat the same on my two BigSur systems where one is for testing and the other I use for everything! like these prints Jieff already made a correction to me that was working correctly! I will test the next one that posted here too! if you want to test what Jieff sent me with correction it will always be one more test! follow here and thanks for sending me the commit Spoiler CloverX64-2020-10-25-20-53-58-d540f76-dirty-jief.efi.zip Link to comment Share on other sites More sharing options...
naiclub Posted October 26, 2020 Share Posted October 26, 2020 2 minutes ago, PG7 said: this commit CLOVERX64--5125 - c458db4ac.efi has a probleme! repeat the same on my two BigSur systems where one is for testing and the other I use for everything! like these prints Jieff already made a correction to me that was working correctly! I will test the next one that posted here too! if you want to test what Jieff sent me with correction it will always be one more test! follow here and thanks for sending me the commit Reveal hidden contents CloverX64-2020-10-25-20-53-58-d540f76-dirty-jief.efi.zip Is it good news? Can you try the full installation with beta 10? Link to comment Share on other sites More sharing options...
PG7 Posted October 26, 2020 Share Posted October 26, 2020 19 minutes ago, iCanaro said: @PG7 they churned out another one here's the commit https://github.com/CloverHackyColor/CloverBootloader/commit/fafc50e3d07be49b55256c0efdbb4c2e424d93b4 CLOVERX64--5125--fafc50e3d.efi.zip with this latest commit CLOVERX64--5125 - fafc50e3d.efi is already with the correct correction for the Preboot BigSur repeat case and I already have both well named, such as Jieff had noticed me! Spoiler Thank you follow the prints in the difference! debug.log 11 minutes ago, naiclub said: Is it good news? Can you try the full installation with beta 10? I haven’t tested the installation yet, but I’ll even test it today and answer later! 1 1 Link to comment Share on other sites More sharing options...
PG7 Posted October 26, 2020 Share Posted October 26, 2020 1 hour ago, naiclub said: Is it good news? Can you try the full installation with beta 10? still unable to install BigSur from the USB installer! here I used the last Commit that iCanario posted continues with the same error and I'll make it clear: Neither Opencore in any version (I haven't tested the 0.6.3 dev) nor Clover I can install BigSur no version the error is the same in both Bootloaders (Catalina installs without a problem) step 1 follow the prints! *this first installation step goes well Spoiler Google translate ! step 2 where everything happens is that it arrives at the screen with the mouse pointer and sends to pass the discount of 29 minutes it simply restarts and always stays on it without going any further Google translate ! Spoiler 2 Link to comment Share on other sites More sharing options...
PG7 Posted October 26, 2020 Share Posted October 26, 2020 however checking on the partition where I tried to install it everything is correct! Spoiler Link to comment Share on other sites More sharing options...
naiclub Posted October 26, 2020 Share Posted October 26, 2020 (edited) 25 minutes ago, PG7 said: still unable to install BigSur from the USB installer! here I used the last Commit that iCanario posted continues with the same error and I'll make it clear: Neither Opencore in any version (I haven't tested the 0.6.3 dev) nor Clover I can install BigSur no version the error is the same in both Bootloaders (Catalina installs without a problem) step 1 follow the prints! *this first installation step goes well Hide contents Google translate ! step 2 where everything happens is that it arrives at the screen with the mouse pointer and sends to pass the discount of 29 minutes it simply restarts and always stays on it without going any further Google translate ! Hide contents The symptoms are the same as me. Now I have a lot of peace of mind as the opencore no longer harms my motherboard. Edited October 26, 2020 by naiclub Link to comment Share on other sites More sharing options...
naiclub Posted October 26, 2020 Share Posted October 26, 2020 1 hour ago, PG7 said: still unable to install BigSur from the USB installer! here I used the last Commit that iCanario posted continues with the same error and I'll make it clear: Neither Opencore in any version (I haven't tested the 0.6.3 dev) nor Clover I can install BigSur no version the error is the same in both Bootloaders (Catalina installs without a problem) step 1 follow the prints! *this first installation step goes well Reveal hidden contents Google translate ! step 2 where everything happens is that it arrives at the screen with the mouse pointer and sends to pass the discount of 29 minutes it simply restarts and always stays on it without going any further Google translate ! Reveal hidden contents Opencore, I use it well (0.6.3 dev). Link to comment Share on other sites More sharing options...
cyrhex Posted October 27, 2020 Share Posted October 27, 2020 works in my celeron g1620 in first attemp,,i dont know why it doesnt work on my ivybridge laptop Link to comment Share on other sites More sharing options...
LockDown Posted October 27, 2020 Share Posted October 27, 2020 (edited) 18 hours ago, Jief_Machak said: I really dont see how is that possible. The message, in case of a boolean is expected is "Expecting <true/> <false/> or <string> tag containing true, false, yes or no" I copied/pasted this key and it works : no complain when it's "<string>No</string>". Send me back your config.plist AND the version of the validator you're using, please, and I'll have a look. All good now. It was actually my fault by following the old wiki. BTW: iMac:~ ella$ /Users/ella/Desktop/CloverConfigPlistValidator0.6 /Users/ella/Desktop/config.plist Warning: Unknown key '/SystemParameters/ExposeSysVariables:1226'. Skipped. Edited October 27, 2020 by ellaosx Link to comment Share on other sites More sharing options...
Recommended Posts