Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

kushwavez
kushwavez
Posted
Posted
On 2/2/2022 at 6:05 PM, Slice said:

The information collected by @Gradou. Big thanks! 

MacBookPro 15,1 (J680AP) 15,2 (J132AP) 15,3 (J780AP) & 15,4 (J213AP)
MacBookPro16,1 (J152FAP) 16,3 (J223AP) & 16,4 (J215AP
MacBookPro16,2 (J214kAP)  //small k
MacBookAir8,1 (J140KAP) & 8,2 (J140AAP)
MacBookAir9,1 (J230KAP)
Macmini8,1 (J174AP)
iMac20,1 (J185AP) & 20,2 (J185FAP)
iMacPro1,1 (J137AP)
MacPro7,1 (J160AP)

I am not sure about "small k" and same in other cases, for example J185fAP.


@phi777

 

Just use J160AP

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

FIXED - with latest commit d6dce385777ec3fa9cb7700fc7b0f4131072142c

 

----- 

Update - i see what is happening
the last CloverBootloader commit is linked to the subproject -1 commit back so is missing the fix for HeaderX...

 

tluck@Toms-MBP16 /opt/Source/Clover

$ git --git-dir=${CLOVERDIR}/.git -C ${CLOVERDIR} pull --force --recurse-submodules

Fetching submodule OpenCorePkg

Already up to date.

Submodule path 'OpenCorePkg': checked out 'c5925d54c5eb7057c3d4f4cd015e95a37091ff91'

 

================

hmm getting this build error...

[SLINK] OcSerializeLib

In file included from /opt/Source/Clover/OpenCorePkg/Library/OcMachoLib/Macho32.c:21:

 

 

exit due to issues; /opt/Source/Clover/OpenCorePkg/Library/OcMachoLib/HeaderX.h:714:3: error: expected identifier or '('

/opt/Source/Clover/OpenCorePkg/Library/OcMachoLib/HeaderX.h:737:3: error: expected identifier or '('

/opt/Source/Clover/OpenCorePkg/Library/OcMachoLib/HeaderX.h:744:3: error: expected identifier or '('

/opt/Source/Clover/OpenCorePkg/Library/OcMachoLib/HeaderX.h:745:1: error: extraneous closing brace ('}')

6 errors generated.

make: *** [/opt/Source/Clover/Build/Clover/RELEASE_XCODE8/X64/OpenCorePkg/Library/OcMachoLib/OcMachoLib/OUTPUT/Macho32.obj] Error 1

: error 7000: Failed to execute command

: error F002: Failed to build module

- Failed -

Edited by tluck
  • Sad 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

But I see no error. 

[DLINK] CLOVERX64
[OBJCOPY] CLOVERX64
[GENFW] CLOVERX64

Generating DUETEFIMAINFVX64 FV
###
GUID cross reference file can be found at /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/FV/Guid.xref

FV Space Information
DUETEFIMAINFVX64 [29%Full] 2752512 (0x2a0000) total, 822056 (0xc8b28) used, 1930456 (0x1d74d8) free

- Done -
Build end time: 22:21:07, Mar.15 2022
Build total time: 00:04:02

 

  • Like 1
Link to comment
Share on other sites
phi777
phi777
Posted
Posted

@Slice
I do not know if this is a bad idea, but it could make live simpler for people if after line 92 of rEFIt_UEFI/Platform/platformdata.cpp there would be this code:

 

case iMac191:
return "J160AP"_XS8;    // TODO: not real value for imac19.1, but works for now
case iMac192:

return "J160AP"_XS8;   // TODO: not real value for imac 19.2, but works for now

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
10 minutes ago, phi777 said:

@Slice
I do not know if this is a bad idea, but it could make live simpler for people if after line 92 of rEFIt_UEFI/Platform/platformdata.cpp there would be this code:

 

case iMac191:
return "J160AP"_XS8;    // TODO: not real value for imac19.1, but works for now
case iMac192:

return "J160AP"_XS8;   // TODO: not real value for imac 19.2, but works for now

 

It's a good idea. 🙂

For my part, I use the SMBIOS Imac19,1 for my z390 (Coffee-Lake R), without HWTarget. This key and its value would be reserved for the Apple mac with T2 chips. Which is not the case for Imac19,1

Link to comment
Share on other sites
phi777
phi777
Posted
Posted (edited)
27 minutes ago, Matgen84 said:

Which is not the case for Imac19,1

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 ?

Edited by phi777
  • Like 2
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)

Hi @Slice

I build and make pkg the latest commit d6dce38. I don't understand why there are MD5 file from previous version, in SYM folder. How to avoid this !

 

Spoiler

2048321716_Capturedcran2022-03-1608_54_35.png.bdff5312b1602284e7912b0645c749a4.png

 

Edited by Matgen84
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
3 minutes ago, Matgen84 said:

Hi @Slice

I build and make pkg the latest commit d6dce38. I don't understand why there are MD5 file from previous version, in SYM folder. How to avoid this !

 

  Hide contents

2048321716_Capturedcran2022-03-1608_54_35.png.bdff5312b1602284e7912b0645c749a4.png

 

I will look at evening.

What script did you use?

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
1 hour ago, Slice said:

I will look at evening.

What script did you use?

 

Thanks if you can take a look. I don't use Buildme, but a personal script. No problem so far.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
6 hours ago, Matgen84 said:

 

Thanks if you can take a look. I don't use Buildme, but a personal script. No problem so far.

I think the problem is in the script.

git pull --recurse-submodule

delete Build folder

start buildme script

Снимок экрана 2022-03-16 в 19.10.32.png

  • Thanks 1
Link to comment
Share on other sites
LAbyOne
LAbyOne
Posted
Posted (edited)
9 hours ago, Matgen84 said:

Hi @Slice

I build and make pkg the latest commit d6dce38. I don't understand why there are MD5 file from previous version, in SYM folder. How to avoid this !

 

  Reveal hidden contents

2048321716_Capturedcran2022-03-1608_54_35.png.bdff5312b1602284e7912b0645c749a4.png

 

This is something can never happen.

buildpkg as it is, before building dependencies, clean-up sym, so having files from previous build can never happen.

 

Don't know what kind of script you made, but for sure, as @Slice already pointed out, the problem reside there.

Edited by LAbyOne
  • Like 2
Link to comment
Share on other sites
MifJpnAlphaPlus
MifJpnAlphaPlus
Posted
Posted (edited)
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
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
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
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted (edited)
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
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted (edited)
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

Spoiler

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

 

1722071666_ScreenShot2022-03-18at12_15_28PM.png.1304de469a30ba84387a8d1d18f4d856.png

scree463.png.7f6ae1f74a93a426dc063019a3744345.png

Edited by chris1111
see spoiler
Link to comment
Share on other sites
Guest 5T33Z0
Guest 5T33Z0
Posted
Posted

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?

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

Link to comment
Share on other sites
Guest 5T33Z0
Guest 5T33Z0
Posted
Posted (edited)
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
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted

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

Link to comment
Share on other sites
Guest 5T33Z0
Guest 5T33Z0
Posted
Posted

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

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

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...