Jump to content
30960 posts in this topic

Recommended Posts

5 hours ago, jlrycm said:

All good here, similar to you except that I declared 12 slots and four slots occupied. No errors.

 

I was just hoping the diagram above would look like a real MacPro in Clover which is what OpenCore accomplishes through the custom memory entries.

Here you can also increase the number of slots to 12.

2 hours ago, Matgen84 said:

Hi everybody

 

When I use make V2 (Option 7 of Buildme), the previous existing files aren't erased before to put CLOVER V2 zip file into Sim directory. Or make a mistake somewhere, sorry.

The better way is to remove sym folder at the start of buildme. 

  • Like 3
3 hours ago, Matgen84 said:

Hi everybody

 

When I use make V2 (Option 7 of Buildme), the previous existing files aren't erased before to put CLOVER V2 zip file into Sim directory. Or make a mistake somewhere, sorry.

When I have time, I'll take a look.
But @Slice already wrote that it is better to delete the entire sym folder. 🙂

  • Like 2
5 hours ago, Matgen84 said:

Hi everybody

 

When I use make V2 (Option 7 of Buildme), the previous existing files aren't erased before to put CLOVER V2 zip file into Sim directory. Or make a mistake somewhere, sorry.

You are right! ok done

Edited by chris1111
  • Thanks 2

@Slice & @MakAsrock

I think i found a bug regarding Clover > Startup sound in GUI.

Last working commit is 8fc629cdf (Artifacts)

 

ISSUE:

Setting output level is somewhat ok,but does not allow you to choose source output. 

It will just hang until you press ESC.

With this issue, no sound settings are saved in nvram

Edited by LockDown
  • Confused 1
4 hours ago, LockDown said:

@Slice & @MakAsrock

I think i found a bug regarding Clover > Startup sound in GUI.

Last working commit is 8fc629cdf (Artifacts)

 

ISSUE:

Setting output level is somewhat ok,but does not allow you to choose source output. 

It will just hang until you press ESC.

With this issue, no sound settings are saved in nvram

Bug found. Working on a fix. Try the newly compiled CLOVERX64.efi.

  • Thanks 1
18 hours ago, MakAsrock said:

When I have time, I'll take a look.
But @Slice already wrote that it is better to delete the entire sym folder. 🙂

 

18 hours ago, MakAsrock said:

When I have time, I'll take a look.
But @Slice already wrote that it is better to delete the entire sym folder. 🙂

 

I'm agree: delete sym folder is better than delete previous files 😊  Thanks @chris1111 for fix delete zip file inside sym folder for makeV2 option, but not working on my system.

 Hi @MakAsrock  If you have time, have a look to another detail about buildme script.

 

At launch, Buildme update cloverbootloader: for example 0e10cb1a9..e410c710e  master     -> origin/master (see info in the spoiler). But the header of the menu show up previous commit : in this case, Clover r5168 (SHA: 0e10cb1a9)

To have good info, we must quit buildme and relaunch it. Is possible that the header of the menu show up directly the update SHA commit !

Sorry for my poor English.

 

Spoiler

mathieu@Mac-Pro-de-mathieu ~ % /Users/mathieu/src/CloverBootloader/buildme ; exit;

Updating OpenCorePkg....

remote: Enumerating objects: 80, done.

remote: Counting objects: 100% (25/25), done.

remote: Compressing objects: 100% (16/16), done.

remote: Total 80 (delta 15), reused 10 (delta 9), pack-reused 55 (from 1)

Dépaquetage des objets: 100% (80/80), 3.39 Mio | 12.04 Mio/s, fait.

Depuis https://github.com/CloverHackyColor/CloverBootloader

   0e10cb1a9..e410c710e  master     -> origin/master

 

---------------------------------------------------------------------------------

                           🍀 Clover r5168 (SHA: 0e10cb1a9)

                              Default TOOLCHAIN: GCC152

                     Switch to XCODE select: build (with XCode)

     Depending on your XCODE version the Toolset will be automatically chosen

---------------------- Current Python version: Python 3.14.2 --------------------

 

 

1) build Clover (Default Toolchain)        😎 build Clover (with XCode)

2) build all (Default Toolchain)               9) build all (with XCode)

3) make Release (Default Toolchain)   10) make Release (with XCode)

4) update Clover                                    11) build Clover with HFSPlus

5) make pkg                                           12) Extra Options

6) make iso                                            13) Exit

7) make Clover_V2

 

Please enter your choice:

 

  • Like 1
Quote

 

@Matgen84 At launch, Buildme update cloverbootloader: for example 0e10cb1a9..e410c710e  master     -> origin/master (see info in the spoiler). But the header of the menu show up previous commit : in this case, Clover r5168 (SHA: 0e10cb1a9)

To have good info, we must quit buildme and relaunch it. Is possible that the header of the menu show up directly the update SHA commit !

 

@chris1111 I use your Clover Buildme app and have the same problem as @Matgen84

  • Like 2
2 hours ago, MakAsrock said:

I also found another bug that you didn't mention (some menu items were duplicated). Try this fix too.

CLOVERX64.efi.zip 729.35 kB · 2 downloads

Hi. I didn't notice the duplicated items, sorry about that. All good here as i have now checked all the menu items

  • Like 2
On 2/15/2026 at 5:25 AM, Slice said:

Hi Brazil!

Can anybody fix the warning?

 

Hi @Slice! 👋

I saw your post regarding the pt-BR translation warning.

I have just fixed it! I updated the 
pt-BR.po
 file adding the missing translations for Drivers, File Systems, and Themes. The translation coverage is now well above the required 74%, so the build warning should be gone and the language included again.

Here is the PR for the fix: https://github.com/CloverHackyColor/CloverBootloader/pull/801

Cheers! 🇧🇷

 

For those who like to compile in their own environment, I recommend using this compiler from my brother, @Max.1974https://github.com/maxpicelli/Clover-Compiler-Builder

Edited by Hnanoto
  • Like 3
  • Thanks 2
×
×
  • Create New...