Clover General discussion

[STLVNUB]

Just now, makk said:

I'll help out if you want?

That's where I got a few from that  I want to convert to Clover.

They should have tons of themes. Use CloverConfigurater as it willl install themes for you

2 minutes ago, STLVNUB said:

They should have tons of themes. Use CloverConfigurater as it willl install themes for you

Well it used too

[Stefanalmare]

1 hour ago, STLVNUB said:

                                                 Clover, The Famous Bootloader Documentation by STLVNUB
                                                 --------------------------------------------------------------

Clover resides in the esp of a disk, it consists of an EFI Folder, here is the structure of it
EFI/BOOT/BOOT.efi
   /Clover
          /ACPI
          /Drivers
          /Kexts
          /misc
          /themes
          /tools
          CLOVERX64.efi
          config.plist
          
You will need to place any ACPI amls into ACPI/patched
You will need to place some drivers into drivers/UEFI
You will need to put any kexts into kexts folder
There is a provision for placing kexts for different OS in it
e.g For Catalina, make a folder for 10.15
Place any kexts you need to run it
For Big Sur make an 11 folder and put into it the relevant kexts for it.
etc etc

There is also Other folder, which is for kexts that work for all macOS

misc folder is for logs, bootlog etc

themes is for themes to give you a boot screen, Clover has builtin theme
There are toins of themes you can use

tools contains the efi shell and bdmesg.efi

You will also need to edit the config.plist, you can't boot unless you have a valid config
-----------------------------------------------------------------------------------------

Compiling
=========

Some feel the need to compile the latest version of Clover

To compile you will need to clone the Clover repository to your HDD
To do so execute this command in your HOME folder
1.
git clone https://github.com/CloverHackyColor/CloverBootloader.git --recurse-submodules 
This will copy the latest Clover code to your HDD.

Issue git pull to get the latest code

 

2.

Compile Clover
Make sure you are in the Clover folder so run terminal
cd to CloverBootloader folder

 

3.

Compile GCC, there is a script file to do that
Also there are various other scripts that compile mtoc, nasm etc

 

4.

Now you should be ready to compile.
Issue this command, ./buildme

 

5.

You will be presented with a screen with a lot of optiions
e.g select 7 to build All of Clover, good time to grab a coffee or drink of your fancy

You will end up with all of Clover
e.g iso and an EFI folder you can use as the base of your 
EFI. You will need to place ACPI files, Drivers,kexts and themes you need to boot.

 

6.

Sit back and relax and boot your macOS
 

Good job:

git clone https://github.com/CloverHackyColor/CloverBootloader.git --recurse-submodules + cd to CloverBootloader folder + ./buildme = all compiled in an old core2 Monterey latest Beta.

[STLVNUB]

Well a least one person liked it

[Stefanalmare]

44 minutes ago, STLVNUB said:

Well a least one person liked it

If somebody want:

Clover.sh

[STLVNUB]

3 hours ago, Stefanalmare said:

If somebody want

Clover.sh 151 B · 2 downloads

Good Easy Script, Our People Will Like It

Just a suggestion could you get it to check for compiled GCC

 

You just need to check for a file in the compiled gcc and build if not there

with  build_gcc11.sh

You can probably get it to build the other dependancies too

good luck 

 

Edited March 12, 2022 by STLVNUB

[Stefanalmare]

16 hours ago, STLVNUB said:

Good Easy Script, Our People Will Like It

Just a suggestion could you get it to check for compiled GCC

 

You just need to check for a file in the compiled gcc and build if not there

with  build_gcc11.sh

You can probably get it to build the other dependancies too

good luck 

 

When I compiled on core2 hack I had no error. Is true, I had after that gcc error on my main z690 hack. I added MacKernelSDK to script (not sure if I did the right thing), and after that I compiled without errors.

Attached is the compile log.

 

Spoiler

 

Compile log.txt

Edited March 13, 2022 by Stefanalmare

[LAbyOne]

18 hours ago, STLVNUB said:

Good Easy Script, Our People Will Like It

Just a suggestion could you get it to check for compiled GCC

You can use the one on my signature..  Clover Setup

 

18 hours ago, STLVNUB said:

You just need to check for a file in the compiled gcc and build if not there

with  build_gcc11.sh

You can probably get it to build the other dependancies too

good luck 

 

No need for other checks. Clover does it

when build is called if no toolchain is present it will start install

and this happen for all choices.

to avoid to have installing dependencies when not present *in case you just hit build clover as first choice

just select "build all".

 

I'm going to add it also to Hackintosh Tools section..

as it only having it on sig may pass unnoticed.

 

> Edit: DONE

 

Edited March 13, 2022 by LAbyOne
added link to Hackintosh Tools

[LAbyOne]

Updated also

Clover Suite Builder

this will most likely be the last update of this tool.

 

I recently made a newer version with more options for the user to choose

the best way for him to use this tool

[phi777]

Anybody knows a HWTarget for imac19.2? Had it set to x86legacy, got 12.2 but didn't get 12.2.1 or now, 12.3? Looking at platformdata.cpp it seems to be not there. Thanks

[kushwavez]

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

[phi777]

28 minutes ago, kushwavez said:

@phi777

 

Just use J160AP

Thank you so much. I tried j160 , J185AP , but J160AP works!
Should I set it back to x86legacy after the update or leave it? 

[kushwavez]

just leave it like that

[phi777]

@kushwavez12.3 is installed, you are a hero!

[tluck]

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 March 15, 2022 by tluck

[Slice]

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

 

[MifJpnAlphaPlus]

Hello.

I was worried so I did a git clone and selected build and it worked.

git clone https://github.com/CloverHackyColor/CloverBootloader.git --recurse-submodules

Thank you

 

[phi777]

@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

[Matgen84]

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

[phi777]

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 March 16, 2022 by phi777

[Matgen84]

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

 

Edited March 16, 2022 by Matgen84

[Slice]

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

 

I will look at evening.

What script did you use?

[Matgen84]

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.

[Slice]

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

[LAbyOne]

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

 

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 March 16, 2022 by LAbyOne

[chris1111]

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

GCC build correct without issue

 

Edited March 16, 2022 by chris1111