Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,059 posts in this topic

Recommended Posts

kushwavez
kushwavez
Posted
Posted
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
Jief_Machak
Jief_Machak
Posted
Posted
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.

  • Like 1
Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted
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
Slice
Slice
Posted
Posted

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.

  • Like 1
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
2 hours ago, JorgeMax said:

@Jief_Machakcould you check why these keys don't work when checked?

  Reveal hidden contents

screenshot1.thumb.png.29586a7313c45a8eb8a1439bca6c5440.png

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 ?

  • Like 1
Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted (edited)

i wanted to point out these oddities that you see in the GUI on BigSur with Clover last commit :drool:

 

https://github.com/CloverHackyColor/CloverBootloader/commit/c458db4acd9eabeafbf2a8c40fd152e076d6d894

 

Spoiler

1031397421_Schermata2020-10-26alle17_40_38.thumb.png.7343647d478b1d7dd81cf7dbbbb381c0.png1121454355_Schermata2020-10-26alle17_40_21.thumb.png.9d4c31c7a6ff104aa5724b91d671b470.png1906027406_Schermata2020-10-26alle17_40_04.thumb.png.5157f0e83777087d33945ba0f32f8503.png1728073147_Schermata2020-10-26alle17_39_29.thumb.png.6798c00f354222d8cceba51cb6f5c646.png547504185_Schermata2020-10-26alle17_39_50.thumb.png.c003c04ba9d9a5cd703ece0d0cc3282c.png

PS: but maybe it was the previous commit, I see new build if I compile Clover
now i finish compiling and text

Edited by iCanaro
  • Sad 1
Link to comment
Share on other sites
JorgeMax
JorgeMax
Posted
Posted
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
PG7
PG7
Posted
Posted
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

screenshot1.thumb.png.6407595d03d0efb9403ad306d754ae80.pngscreenshot0.thumb.png.169f5110b9d61b4ecd828f6fc7466a7f.png

Spoiler

 

 

CloverX64-2020-10-25-20-53-58-d540f76-dirty-jief.efi.zip

Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
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
PG7
PG7
Posted
Posted
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

screenshot1.thumb.png.a72a48dabf7cc113baae056fbb38f299.pngscreenshot0.thumb.png.be66cc3e1d694326fe43fd47907a224b.png

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!

  • Like 1
  • Thanks 1
Link to comment
Share on other sites
PG7
PG7
Posted
Posted
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

1927454345_Fase14.thumb.jpg.cc56308696659af627b4593a53c2f5aa.jpg1233823035_Fase13.thumb.jpg.388bce6c7f525d19cb4a14acac577803.jpg

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

912256651_Fase22.thumb.jpg.a0c57161e860fd111caaa3a42844dfac.jpg90611925_Fase23.thumb.jpg.7d4f7e5b4f788c9d250f784183858a22.jpg1388706576_Fase25.thumb.jpg.73d212c24339c4ede3499cdad2c5b55e.jpg

 

  • Like 2
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted (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 by naiclub
Link to comment
Share on other sites
naiclub
naiclub
Posted
Posted
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

1927454345_Fase14.thumb.jpg.cc56308696659af627b4593a53c2f5aa.jpg1233823035_Fase13.thumb.jpg.388bce6c7f525d19cb4a14acac577803.jpg

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

912256651_Fase22.thumb.jpg.a0c57161e860fd111caaa3a42844dfac.jpg90611925_Fase23.thumb.jpg.7d4f7e5b4f788c9d250f784183858a22.jpg1388706576_Fase25.thumb.jpg.73d212c24339c4ede3499cdad2c5b55e.jpg

 

Opencore, I use it well (0.6.3 dev).

Link to comment
Share on other sites
LockDown
LockDown
Posted
Posted (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 by ellaosx
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...