Clover General discussion

[LockDown]

4 hours ago, Slice said:

If you usually uses EFI/BOOT/BOOTX64.EFI then Windows may change it to own bootloader.

I am using EFI/CLOVER/CLOVERX64.EFI for daily usage and I don't afraid Windows update.

How can i do it your way?

[STLVNUB]

5 hours ago, 5T33Z0 said:

What are you talking about? I am not talking about installing Windows.

Is there anybody in here who actually can read and understand english?

I find doing a fresh install is better than stuffing around trying to get it to work

Sorry didn't read all of the thread but my input may help others that are trying to do same thing

and are not scared to try something different

 

Edited March 21, 2022 by STLVNUB

[Slice]

4 hours ago, LockDown said:

How can i do it your way?

In the Clover GUI look to second row carefully.

[makk]

7 hours ago, 5T33Z0 said:

What are you talking about? I am not talking about installing Windows.

Is there anybody in here who actually can read and understand english?

@5T33Z0

Hi there, I posted on the Opencore v Clover

try that in the post.

 

Find kushwavez's post on dual booting. He recently posted it and has vouched for many installs with this method.

 

Can you post your diskutil list over there on my posted reply on OC v Clover?

 

Thank you

[Guest 5T33Z0]

3 hours ago, STLVNUB said:

I find doing a fresh install is better than stuffing around trying to get it to work

Sorry didn't read all of the thread but my input may help others that are trying to do same thing

and are not scared to try something different

 

 

Please don't bother me with re-installing Windows 11. It was a clean install. You are totally missing the point.

[Guest 5T33Z0]

2 hours ago, Slice said:

In the Clover GUI look to second row carefully.

 

How can I change that in the config, so EFI/CLOVER/CLOVERX64.EFI is used instead of EFI/BOOT/BOOTX64.EFI?

[Slice]

1 hour ago, 5T33Z0 said:

 

How can I change that in the config, so EFI/CLOVER/CLOVERX64.EFI is used instead of EFI/BOOT/BOOTX64.EFI?

Nothing to do here because this is UEFI BIOS variables working before Clover started.

We made (namely Dmasar) an convenient method to write BOOT0000 variable to BIOS with Clover name.

There is a possibility to do the same in Shell but the command is too complex to remember.

[Guest 5T33Z0]

10 hours ago, Slice said:

In the Clover GUI look to second row carefully.

 

And what exactly do I have to took look for here?

 

[Slice]

1 hour ago, 5T33Z0 said:

 

And what exactly do I have to took look for here?

 

And then press the button and see

This action will create a boot option in BIOS

 

[PG7]

2 hours ago, 5T33Z0 said:

 

Et qu'est-ce que je dois exactement chercher ici?

 

do the following

create a new disk partition in addition to the source ESP

who already has the original Windows EFI creates a new partition with the desired size (200 Mo) Fat32 format (Windows) or MS-DOS (MacOS)

I prefer to use this way and install Bootloader Clover or another one inside that and leave the source ESP for Windows

then in the Bios boot order put this new one that I leave with the name MacOS or Boot and as Clover is great in multiboot I boot with it on MacOS or Windows and any update of other systems does not affect the mac boot

Time 8:23 = 

 

[LockDown]

9 hours ago, Slice said:

And then press the button and see

This action will create a boot option in BIOS

 

Oh Ok.I have that covered using Bootice

Edited March 22, 2022 by LockDown

[MifJpnAlphaPlus]

21 hours ago, Slice said:

And then press the button and see

This action will create a boot option in BIOS

 

 

 

Hello.

I didn't know there was such a great option. Amazing!

Windows tends to set up its own deep folders in the UEFI order.

　In contrast, creating UEFI items is quite a tedious process.
　As such, if it is not that amazing option, I work in UBUNTU's live mode, such as
　This was a nice experience to see how UEFI boot items work.

https://mifmif-mydns-jp.translate.goog/pcpc/index.php?PC3-180909&_x_tr_sl=ja&_x_tr_tl=en&_x_tr_hl=ja&_x_tr_pto=wapp

(Pardon the automatic translation.)

 

 

Yes!
This option just blew me away!

 

[tluck]

FYI....

this seems to be an Xcode 13.3 issue?  as Xcode 12.4 seems to work fine:
 

[CC] PcRtc

In file included from /opt/Source/Clover/rEFIt_UEFI/Platform/APFS.cpp:8:

In file included from /opt/Source/Clover/rEFIt_UEFI/PlatformEFI/include/Platform.h:19:

In file included from /opt/Source/Clover/rEFIt_UEFI/cpp_foundation/XString.h:13:

        size_t nb = 0;

               ^

/opt/Source/Clover/rEFIt_UEFI/Platform/APFS.cpp:52:68: note: in instantiation of function template specialization '__String<char, XString8>::isEqualIC<char, XString8>' requested here

    if ( GuidLEToXString8(*(EFI_GUID *)((UINT8 *)DevicePath+0x04)).isEqualIC(ApfsSignatureUUID) ) {

                                                                   ^

1 error generated.

make: *** [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/APFS.obj] Error 1

 

 

build.py...

: error 7000: Failed to execute command

make tbuild [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]

 

 

build.py...

: error F002: Failed to build module

/opt/Source/Clover/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

 

- Failed -

Build end time: 10:49:08, Mar.22 2022

Build total time: 00:01:08

 

exit due to issues; 1 error generated.

make: *** [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/APFS.obj] Error 1

: error 7000: Failed to execute command

: error F002: Failed to build module

- Failed -

 

[chris1111]

22 minutes ago, tluck said:

FYI....

this seems to be an Xcode 13.3 issue?  as Xcode 12.4 seems to work fine:
 

 

Yep you need to use diferant SDKs

13.3 works

https://github.com/chris1111/macOS-SDK

[Slice]

28 minutes ago, tluck said:

FYI....

this seems to be an Xcode 13.3 issue?  as Xcode 12.4 seems to work fine:
 

[CC] PcRtc

In file included from /opt/Source/Clover/rEFIt_UEFI/Platform/APFS.cpp:8:

In file included from /opt/Source/Clover/rEFIt_UEFI/PlatformEFI/include/Platform.h:19:

In file included from /opt/Source/Clover/rEFIt_UEFI/cpp_foundation/XString.h:13:

        size_t nb = 0;

               ^

/opt/Source/Clover/rEFIt_UEFI/Platform/APFS.cpp:52:68: note: in instantiation of function template specialization '__String<char, XString8>::isEqualIC<char, XString8>' requested here

    if ( GuidLEToXString8(*(EFI_GUID *)((UINT8 *)DevicePath+0x04)).isEqualIC(ApfsSignatureUUID) ) {

                                                                   ^

1 error generated.

make: *** [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/APFS.obj] Error 1

 

 

build.py...

: error 7000: Failed to execute command

make tbuild [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]

 

 

build.py...

: error F002: Failed to build module

/opt/Source/Clover/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

 

- Failed -

Build end time: 10:49:08, Mar.22 2022

Build total time: 00:01:08

 

exit due to issues; 1 error generated.

make: *** [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/APFS.obj] Error 1

: error 7000: Failed to execute command

: error F002: Failed to build module

- Failed -

 

This is one new warning "set-but-unused".

Fixed.

Test, please, more.

[tluck]

3 hours ago, Slice said:

This is one new warning "set-but-unused".

Fixed.

Test, please, more.

still the same?

CC] ConsoleWrappers

In file included from /opt/Source/Clover/rEFIt_UEFI/Platform/APFS.cpp:8:

In file included from /opt/Source/Clover/rEFIt_UEFI/PlatformEFI/include/Platform.h:19:

In file included from /opt/Source/Clover/rEFIt_UEFI/cpp_foundation/XString.h:13:

        size_t nb = 0;

               ^

/opt/Source/Clover/rEFIt_UEFI/Platform/APFS.cpp:52:68: note: in instantiation of function template specialization '__String<char, XString8>::isEqualIC<char, XString8>' requested here

    if ( GuidLEToXString8(*(EFI_GUID *)((UINT8 *)DevicePath+0x04)).isEqualIC(ApfsSignatureUUID) ) {

                                                                   ^

1 error generated.

make: *** [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/APFS.obj] Error 1

 

 

build.py...

: error 7000: Failed to execute command

make tbuild [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]

 

 

build.py...

: error F002: Failed to build module

/opt/Source/Clover/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

 

- Failed -

Build end time: 14:45:52, Mar.22 2022

Build total time: 00:00:51

 

exit due to issues; 1 error generated.

make: *** [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/APFS.obj] Error 1

: error 7000: Failed to execute command

: error F002: Failed to build module

- Failed -

 

[makk]

The other thing to look at sometimes we forget due to the many variances to the complexity to get Hacky to boot:

are and I am guilty for this and for the other ones. Because these are not in config.plist due to not putting them in.

So we forget because they are not in them. Commenting them out after having them written it is good practice instead

 of deleting from the config.plist. then this way you don't have to scramble through sample-config.plist or some page.

 

In the config.plist under Boot there is

two defaults that is overlooked or forgotten quite often due to scrambling around for a fix on something else.

 

Boot Section of config.plist

1 DefaultVolume: string [name of volume or LastedBootedVolume

1 DefaultLoader:  boot.efi [ or Cloverx64.efi ] now I had a thought which occurred to me is that you can put here some other modified 'boot.efi'; haven't tried it yet but I wonder what the outcome is? such as OpenCore.efi?  or some Grub job.efi? 

 

With these above options in boot, you can delete them, comment them out. 

 

By default the boot will be last booted volume.

By default it will be 'boot.efi.'

 

 

[makk]

could be language issue as well on the hardware.  have had this issue once or twice.

 

 

[Slice]

10 hours ago, tluck said:

still the same?

CC] ConsoleWrappers

In file included from /opt/Source/Clover/rEFIt_UEFI/Platform/APFS.cpp:8:

In file included from /opt/Source/Clover/rEFIt_UEFI/PlatformEFI/include/Platform.h:19:

In file included from /opt/Source/Clover/rEFIt_UEFI/cpp_foundation/XString.h:13:

        size_t nb = 0;

               ^

/opt/Source/Clover/rEFIt_UEFI/Platform/APFS.cpp:52:68: note: in instantiation of function template specialization '__String<char, XString8>::isEqualIC<char, XString8>' requested here

    if ( GuidLEToXString8(*(EFI_GUID *)((UINT8 *)DevicePath+0x04)).isEqualIC(ApfsSignatureUUID) ) {

                                                                   ^

1 error generated.

make: *** [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/APFS.obj] Error 1

 

 

build.py...

: error 7000: Failed to execute command

make tbuild [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]

 

 

build.py...

: error F002: Failed to build module

/opt/Source/Clover/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

 

- Failed -

Build end time: 14:45:52, Mar.22 2022

Build total time: 00:00:51

 

exit due to issues; 1 error generated.

make: *** [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/Platform/APFS.obj] Error 1

: error 7000: Failed to execute command

: error F002: Failed to build module

- Failed -

 

this line commented out in repo

-  size_t nb = 0;
+//  size_t nb = 0;

 

[Slice]

9 hours ago, makk said:

 

 

Boot Section of config.plist

1 DefaultVolume: string [name of volume or LastedBootedVolume

1 DefaultLoader:  boot.efi [ or Cloverx64.efi ] now I had a thought which occurred to me is that you can put here some other modified 'boot.efi'; haven't tried it yet but I wonder what the outcome is? such as OpenCore.efi?  or some Grub job.efi? 

 

With these above options in boot, you can delete them, comment them out. 

 

By default the boot will be last booted volume.

By default it will be 'boot.efi.'

 

 

DefaultLoader is not Clover or OpenCore. They are Boot Managers.

They choose a Boot Loader for operating system like

boot.efi for macOS

bootmgfw.efi for Windows

grubx64.efi for Linux

 

Fully agree with default values. They are not set?

[tluck]

11 hours ago, Slice said:

this line commented out in repo

-  size_t nb = 0;
+//  size_t nb = 0;

 

this is not the only issue...

/opt/Source/Clover/rEFIt_UEFI/cpp_foundation/XStringAbstract.h:553:85: note: in instantiation of function template specialization '__String<wchar_t, XStringW>::strcmp<wchar_t>' requested here

        bool operator == (const __String<O, OtherXStringClass>& s2) const { return (*this).strcmp(s2.s()) == 0; }

                                                                                           ^

/opt/Source/Clover/rEFIt_UEFI/refit/../libeg/libeg.h:132:19: note: in instantiation of function template specialization '__String<wchar_t, XStringW>::operator==<wchar_t, XStringW>' requested here

    if ( !(SValue == other.SValue ) ) return false;

                  ^

 

/opt/Source/Clover/rEFIt_UEFI/Settings/ConfigPlist/Config_GUI.h:86:131: note: in instantiation of function template specialization '__String<char, XString8>::startWithIC<char>' requested here

          XBool dgetLegacyFirst() const { return Legacy.isDefined() && Legacy.xmlString8.isDefined() && Legacy.xmlString8.value().startWithIC("F"); };

                                                                                                                                  ^

Edited March 23, 2022 by tluck

[makk]

12 hours ago, Slice said:

DefaultLoader is not Clover or OpenCore. They are Boot Managers.

They choose a Boot Loader for operating system like

boot.efi for macOS

bootmgfw.efi for Windows

grubx64.efi for Linux

 

Fully agree with default values. They are not set?

 

thanks yes I have defaults set, update with sample-config.plist 

to config.plist whenever changes are made in newer versions of clover.

 

Nice, so I can set DefaultLoader to other than boot.efi such as

1 Cloverx64.efi

2 bootmgfw.efi

 

I have set Cloverx64.efi to see what happens.

But have not tried bootmgfw.efi to boot only MS.

 

 

 

 

 

Question then,

 

what would cause Windows to autoboot ignoring Clover Menu?

 

Overriden scenario, bypass, door closed

Edited March 23, 2022 by makk

[SavageAUS]

 
thanks yes I have defaults set, update with sample-config.plist 
to config.plist whenever changes are made in newer versions of clover.
 
Nice, so I can set DefaultLoader to other than boot.efi such as
1 Cloverx64.efi
2 bootmgfw.efi
 
I have set Cloverx64.efi to see what happens.
But have not tried bootmgfw.efi to boot only MS.
 
 
 
 
 
Question then,
 
what would cause Windows to autoboot ignoring Clover Menu?
 
Overriden scenario, bypass, door closed

For the clover boot gui to get skipped you would have to have your boot order set wrong in bios.


Sent from my iPhone using Tapatalk

[makk]

3 minutes ago, SavageAUS said:

For the clover boot gui to get skipped you would have to have your boot order set wrong in bios.


Sent from my iPhone using Tapatalk

 

Thanks, I don't have that issue.

 

Someone else does.

 

So they might have BIOS set to select Bootmgfw.efi to start. MS Windows

 

[makk]

@SavageAUS

 

I have a question off topic if you could let me know in a private message.

 

I see you have Nvidia GTX 1650 on your laptop.

I just bought an used Asus Nitro 5 with Nvidia GTX 1050 Ti and wanted to know how 

and if it can be running on Monterey. What you had to do to get up if it is up.