Clover General discussion

[MaLd0n]

1 hour ago, MacKonsti said:

a)

try this folder, @MacKonsti

Reset nvram first time with F11 key in boot screen

EFI MacKonsti 01.zip

 

 

[Jief_Machak]

1 hour ago, Alpha22 said:

Hello Jief_Machak

i tried your app and this is the result

 

fabio@iMac-di-Fabio ~ % /Users/fabio/Desktop/CloverConfigPlistValidator0.6 /Users/fabio/Desktop/Clover/config.plist 

Warning: Unknown key '/ACPI/DSDT/DropOEM_DSM:13'. Skipped.

Warning: Unknown key '/GUI/Custom/Entries[0]/Ignore:420'. Skipped.

Warning: Unknown key '/GUI/Custom/Entries[1]/Ignore:436'. Skipped.

Warning: Unknown key '/GUI/Custom/Entries[2]/Ignore:450'. Skipped.

Warning: Unknown key '/GUI/Mouse/DoubleClick:478'. Skipped.

Warning: Unknown key '/KernelAndKextPatches/KernelCpu:559'. Skipped.

Warning: Unknown key '/Quirks/DisableRtcChecksum:627'. Skipped.

Yep, useless keys, if I'm not mistaken.

[Guest]

@Jief_Machak

Can I ask where they are taken from or how are these parameters found? I ask because in my case starting with either High Sierra or Big Sur, only High Sierra is always detected in debugging And this has negative effects on boot of Big Sur

 

 

thank you

Edited October 25, 2020 by Guest

[LockDown]

@Jief_Machak

Also this under ACPI.

smartUPS
<key>smartUPS</key>
<string>No</string>

CCPV0.6complains that it should be an integer instead of a string.

[MacKonsti]

1 hour ago, ellaosx said:

@Jief_Machak

Also this under ACPI.

smartUPS
<key>smartUPS</key>
<string>No</string>

CCPV0.6complains that it should be an integer instead of a string.

 

I put <false/> and it works for smartUPS key, mate, please try that. Not sure if all keys accept "No" or "Yes" in such way as <string>

Edited October 26, 2020 by MacKonsti

[Slice]

6 hours ago, ellaosx said:

@Jief_Machak

Also this under ACPI.

smartUPS
<key>smartUPS</key>
<string>No</string>

CCPV0.6complains that it should be an integer instead of a string.

 

5 hours ago, MacKonsti said:

 

I put <false/> and it works for smartUPS key, mate, please try that. Not sure if all keys accept "No" or "Yes" in such way as <string>

It can be <string> or boolean <true/> or <false/>. Not <integer>.

[Andres ZeroCross]

In HP notebook, only there "OS Boot Manager" as UEFI Entry boot, And i have single Disk with Windows and macOS.

I have copy CloverX64.efi to EFI/Microsoft/Boot and rename the original "bootmgfw.efi" to "bootmgfw-orig.efi" then rename "CLOVERX64.efi" to "bootmgfw.efi"

But, in 5125 (I don't test it in 5124, 5122 is still normal) it doesn't work anymore. 

The config.plist is not recognized,, and i got default theme loaded by this method. 

I revert back to 5122,, please @Jief_Machak give solution

[Common_Sense]

@Jief_Machak .VolumeLabel.txt appends the text inside the file to the already existing label of macOS Preboot volume. This must be a bug?

[kushwavez]

29 minutes ago, Andres ZeroCross said:

In HP notebook, only there "OS Boot Manager" as UEFI Entry boot, And i have single Disk with Windows and macOS.

I have copy CloverX64.efi to EFI/Microsoft/Boot and rename the original "bootmgfw.efi" to "bootmgfw-orig.efi" then rename "CLOVERX64.efi" to "bootmgfw.efi"

No need for renaming, that can cause serious problems. Leave the Windows boot files alone. Copy & Paste the CLOVER and BOOT folder to the EFI, in Windows cmd (admin mode) use this command to set Clover to default: 

bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi

Then restart. 

[Slice]

27 minutes ago, kushwavez said:

No need for renaming, that can cause serious problems. Leave the Windows boot files alone. Copy & Paste the CLOVER and BOOT folder to the EFI, in Windows cmd (admin mode) use this command to set Clover to default: 

bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi

Then restart. 

No serious problem. It is working method.

1 hour ago, Andres ZeroCross said:

In HP notebook, only there "OS Boot Manager" as UEFI Entry boot, And i have single Disk with Windows and macOS.

I have copy CloverX64.efi to EFI/Microsoft/Boot and rename the original "bootmgfw.efi" to "bootmgfw-orig.efi" then rename "CLOVERX64.efi" to "bootmgfw.efi"

But, in 5125 (I don't test it in 5124, 5122 is still normal) it doesn't work anymore. 

The config.plist is not recognized,, and i got default theme loaded by this method. 

I revert back to 5122,, please @Jief_Machak give solution

Can you give us preboot.log to see what is the problem this way?

[Guest]

@Slice

could you check also here if you have time?

GetOS seems to fail and for kernel patches in AMD system is a mess (if you use a single config.plist using MatchOS to apply right Kernel patches for each Os to boot dfferent systems)

thank you

Edited October 26, 2020 by Guest

[Jief_Machak]

8 hours ago, ellaosx said:

@Jief_Machak

Also this under ACPI.

smartUPS
<key>smartUPS</key>
<string>No</string>

CCPV0.6complains that it should be an integer instead of a string.

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.

[Jief_Machak]

1 hour ago, Andres ZeroCross said:

I have copy CloverX64.efi to EFI/Microsoft/Boot and rename the original "bootmgfw.efi" to "bootmgfw-orig.efi" then rename "CLOVERX64.efi" to "bootmgfw.efi"

Clover is now getting all its files from where the efi is in. So if you put Clover in "EFI/Microsoft/Boot", you have to put config.plist, kexts dir etc. in that dir.

 

1 hour ago, kushwavez said:

 

bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi

 

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.

[Andres ZeroCross]

3 hours ago, Slice said:

No serious problem. It is working method.

Can you give us preboot.log to see what is the problem this way?

Sorry, i have pressed F2 in GUI CLOVER, but when i checked to EFI/CLOVER/misc,, there is no Preboot.log.

And i try to use this method to my PC (Copy CLOVERX64.efi to Microsoft/Boot folder and rename it to bootmgfw.efi and change original bootmgfw.efi to bootmgfw-orig.efi) and got some problem.

Btw, F2 didn't give any output to EFI/CLOVEr/Misc

[MaLd0n]

25 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.

enable debug in boot tab

[Slice]

3 hours ago, Jief_Machak said:

Clover is now getting all its files from where the efi is in. So if you put Clover in "EFI/Microsoft/Boot", you have to put config.plist, kexts dir etc. in that dir.

 

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.

The feature is follow:

Some bioses don't want to start bootx64.efi. They want to start only EFI/Microsoft/bootmgrw.efi. So the trick is replace this file to Clover and Clover already knows the file name "bootmgfw-orig.efi" to start Windows. 

[Jief_Machak]

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

[kushwavez]

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.

[Jief_Machak]

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.

[kushwavez]

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.

[JorgeMax]

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

Spoiler

Thank you

[Slice]

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.

[Jief_Machak]

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 ?

[iCanaro]

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

[JorgeMax]

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