Jump to content
30960 posts in this topic

Recommended Posts

15 hours ago, phi777 said:

OK, to be honest, I only tested it for imac 19.2, without J160AP it leaves HWTarget blank and I could not update. So do you propose, leaving it blank for imac19.1 or using x86legacy ?

Hello.

I was also using an iMac 19,2. (i7-8700,H370)
We had just scheduled an update to 12.3.
I had a large file server.Once I backed up the entire system.
And then.
I tried without HWTarget(Not Blank) and with HWTarget being x86legacy, both updates worked.

 

Spoiler

218996594_2022-03-1623_06_55.thumb.jpg.150fbaa0bec72ecaf0b3cd0eeeea6ca6.jpg

 

Spoiler

2097457417_2022-03-174_45_12.thumb.jpg.a1d1bde00ec3d115138b467af1a1db67.jpg

 

 

 

Spoiler

1514920529_2022-03-1623_10_48.jpg.cfa74191594a215a7c144982a68d2970.jpg

 

Edited by MifJpnAlphaPlus
  • Like 2
9 hours ago, chris1111 said:

Xcode Version 13.3 (13E113)  build Failled on Monterey 12.3

GCC build correct without issue

 

1081041522_ScreenShot2022-03-16at5_34_12AM.png.0d6c12c83dde42c875fdab6c00ef79d4.png

Thanks for the note. Will be corrected.

Is it the only place? I have no Xcode13 to check.

  • Like 1
3 hours ago, Slice said:

Thanks for the note. Will be corrected.

Is it the only place? I have no Xcode13 to check.

Yes only place? I believe because he stops there

Edited by chris1111
On 3/17/2022 at 1:34 AM, Slice said:

Thanks for the note. Will be corrected.

Is it the only place? I have no Xcode13 to check.

 

Hi  @Slice

I did a lot of testing and the problem comes only from Xcode Version 13.3 (13E113) 

because with Xcode Version 13.2.1 (13C100) in macOS 12.3 Clover source no problem compiling Xcode and GCC

Here build Xcode sucessfull

 

BUILDINFOS_STR "Args: -mc -D NO_GRUB_DRIVERS | --cmd-len=50000 -D NO_GRUB_DRIVERS --conf=/Users/chris/src/CloverBootloader/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 12.3"

 

 

EDIT *** 

Xcode Version 13.3 (13E113) works with MacOSX12.1.sdk

Edited by chris1111
see spoiler
10 minutes ago, 5T33Z0 said:

If i use Clover r5145 to Boot Windows 11, Windows Boot Manager Takes over the first position in the boot driver order. How can I fix this?

I am not understanding what do you want to fix. It is the matter that windows will be started when reboot from windows. It is how the update working.

LastBootVolume is that.

But there is another thing. 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.

Guest 5T33Z0
11 hours ago, Slice said:

I am not understanding what do you want to fix. It is the matter that windows will be started when reboot from windows. It is how the update working.

LastBootVolume is that.

But there is another thing. 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.

 

It skips Clover. Like I said: Windows Boot Manager takes over the first position in the Boot drive order.

This is not about Clover GUI loading and then Windows is the selected disk.

Please read more carefully!

Edited by 5T33Z0

Use Windows Install.app

Will install to any drive with its own boot loader.

Very easy to use, just download iso and the rest is super easy

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 by STLVNUB
  • Confused 1
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.

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.

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 = 

 

  • Like 1
21 hours ago, Slice said:

Снимок экрана 2022-03-21 в 19.33.08.png

And then press the button and see

Снимок экрана 2022-03-21 в 19.33.22.png

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!

 

  • Like 1

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 -

 

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

  • Like 2
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.

  • Like 2
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 -

 

×
×
  • Create New...