Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
31000 posts in this topic

Recommended Posts

MakAsrock
MakAsrock
Posted
Posted (edited)

 

8 hours ago, Matgen84 said:

Hi all Devs

 

Try to use gcc16.1  But I can't build Clover with these settings and Default Toolchian GCC161: build error 4000 gcc161 not defined etc. 

if [[ $MYTOOLCHAIN == GCC* ]] && [[ ! -x "${GCC161_BIN}" ]]; then
    if [[ $MYTOOLCHAIN == GCC161 ]]; then
      cd "${CLOVERROOT}"
      ./build_gcc16.sh
    else
      MYTOOLCHAIN=XCODE16
    fi
  fi

 

 

 

I take a look at the repo and see : 

if [[ $MYTOOLCHAIN == GCC* ]] && [[ ! -x "${GCC152_BIN}" ]]; then
    if [[ $MYTOOLCHAIN == GCC152 ]]; then
      cd "${CLOVERROOT}"
      ./build_gcc16.sh
    else
      MYTOOLCHAIN=XCODE16
    fi
  fi

I can't build too if Default ToolChain is GCC161.

 

I don't understand why Default ToolChain must be GCC152 !!! 

  Reveal hidden contents

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

                           🍀 Clover r5172 (SHA: 9af58b239)

                              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.6 --------------------

 

 

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:

 

So Buildme use gcc152 parameters instead of gcc161 :

  Reveal hidden contents

Running edk2 build for CloverX64 using the command:

build --cmd-len=50000 -D NO_GRUB_DRIVERS_EMBEDDED -D LESS_DEBUG --conf=/Users/mathieu/src/CloverBootloader/Conf -D USE_LOW_EBDA -D ENABLE_MODERN_CPU_QUIRKS -p Clover.dsc  -a X64 -b RELEASE -t GCC152 -n 9

 

Because GCC 16.1 was not yet implemented.
After Shabbat is over, this will be published.

2026-07-0403_46_51.thumb.jpg.5b700148d008d94b060fe980b0a676d3.jpg

Edited by MakAsrock
  • Like 2
  • Thanks 2
MakAsrock
MakAsrock
Posted
Posted (edited)
On 7/4/2026 at 2:18 AM, MakAsrock said:

 

Because GCC 16.1 was not yet implemented.
After Shabbat is over, this will be published.

2026-07-0403_46_51.thumb.jpg.5b700148d008d94b060fe980b0a676d3.jpg

Release 5174 published (GCC 16.1 full implemented).

Edited by MakAsrock
  • Thanks 2
MakAsrock
MakAsrock
Posted
Posted (edited)

Release 5174 GCC 16.1 full implementation.
 

image.thumb.jpeg.1922f48e55c09937988c266be0ae9e4d.jpeg


Advanced SVG graphics, more fast more exact.
Repaired feature that SMBIOS choosing automatically according to OS version.
Using gcc-16.1.0 as main compiler.

MD5 (Clover_r5174.pkg) = 328c3aefe1ef80c724898c8f03d9cc96

What's Changed

 

🏅 Hall of Fame (Special Thanks):

  • Slice – for project general management and dedication.
  • YBronst – for menu refactoring, Quirks layout implementation, audio/GUI bug fixes and GCC 16.1 full implementation.
  • chris1111 – for the Tahoe/Christmas and other Themes assets.
  • Hnanoto – for ModernCPUquirk, completing PT-BR (Brazilian Portuguese) translations, and resolving UI build warnings. 🇧🇷
Edited by MakAsrock
  • Like 3
  • Thanks 2
LockDown
LockDown
Posted
Posted (edited)
8 hours ago, MakAsrock said:

Release 5174
Repaired feature that SMBIOS choosing automatically according to OS version.

@MakAsrock 

I was under the impression that if you leave SMBIOS empty in config.plist, Clover will detect my OS and choose a compatible smbios. But why is it clover have chosen iMac18,1 on my Tahoe which is not compatible for Tahoe?

Unless i misundertood the changelog

Edited by LockDown
  • Like 1
  • Sad 2
MakAsrock
MakAsrock
Posted
Posted (edited)
6 hours ago, LockDown said:

@MakAsrock 

I was under the impression that if you leave SMBIOS empty in config.plist, Clover will detect my OS and choose a compatible smbios. But why is it clover have chosen iMac18,1 on my Tahoe which is not compatible for Tahoe?

Unless i misundertood the changelog

The changelog is accurate, but automatic SMBIOS selection is a hardware-matching heuristic, not magic. Clover chose iMac18,1 because it detected your Intel HD 620/630. For desktop Macs, iMac18,1 is the last profile where this IGPU works as the primary display output.

Clover couldn't automatically choose iMac20,1 or 20,2 for Tahoe because Apple completely disabled the integrated Intel UHD 630 on those models at the factory level (they rely exclusively on AMD dGPUs). Forcing iMac20,x on an IGPU-only desktop would result in a black screen.

The only real Macs with a working HD 630 on Tahoe are laptops (MacBookPro16,1 / 16,4), but Clover won't automatically assign a mobile profile to a desktop configuration.

Leaving SMBIOS empty is always a gamble on newer macOS versions. If you want to boot Tahoe on this hardware, you must manually specify a compatible SMBIOS in your config.plist and inject the required device-id patches as described in Clover_Of_Khaki_Color_5172-en.pdf.

Edited by MakAsrock
  • Like 3
LockDown
LockDown
Posted
Posted (edited)

Thanks for the clarification. So would say that it's more of a hardware based detection rather than OS.

 

Im saying this due to macos not allowing you to do "fresh" install with unsupported smbios even with no_compat_check or Skip Board ID Check

Edited by LockDown
  • Like 1
MakAsrock
MakAsrock
Posted
Posted (edited)
8 hours ago, LockDown said:

Thanks for the clarification. So would say that it's more of a hardware based detection rather than OS.

 

Im saying this due to macos not allowing you to do "fresh" install with unsupported smbios even with no_compat_check or Skip Board ID Check

If you try to boot the macOS Tahoe installer without a Metal 3-supported discrete graphics card, you will completely lose display output with UHD 630 or 620 (the screen goes black). Furthermore, the -no_compat_check boot-arg no longer works in Tahoe, and even if it did, a clean install is simply not possible with it.

Edited by MakAsrock
  • Like 4
LockDown
LockDown
Posted
Posted
1 hour ago, MakAsrock said:

If you try to boot the macOS Tahoe installer without a Metal 3-supported discrete graphics card, you will completely lose display output with UHD 630 or 620 (the screen goes black). Furthermore, the -no_compat_check boot-arg no longer works in Tahoe, and even if it did, a clean install is simply not possible with it.

There is really no need to force acceleration on install. All these can be bypassed by booting with -igfxvesa + iMac20,1 then configure it after. I do it everytime i clean install.

 

Anyways...il stick to my own workaround 👍

Btw, Changes you've made in 5174 are great. Keep it up!👍

 

  • Like 2
Matgen84
Matgen84
Posted
Posted (edited)

@MakAsrock Compiling with full GCC16.1 smoothly 😊

 

EDIT: I merge your Full GCC16.1 to my local CloverBootloader. How to bump Version number on my local repo ? Please.

Edited by Matgen84
  • Like 3
deeveedee
deeveedee
Posted
Posted

@LockDown and @MakAsrock

I'm probably misunderstanding what you're saying, so could you please clarify? - thank you.  I routinely install macOS Tahoe with boot-arg -no_compat_check or with Booter Patch "Skip board ID Check" using unsupported SMBIOS MacMini8,1.  I can perform this installation on systems with only UHD630 iGPU and with systems that have both dGPU Radeon RX 560x and iGPU UHD630.

 

Under what conditions does -no_compat_check or Skip Board ID check no longer work for installing Tahoe on systems with unsupported SMBIOS?

  • Like 2
MakAsrock
MakAsrock
Posted
Posted (edited)
3 hours ago, deeveedee said:

@LockDown and @MakAsrock

I'm probably misunderstanding what you're saying, so could you please clarify? - thank you.  I routinely install macOS Tahoe with boot-arg -no_compat_check or with Booter Patch "Skip board ID Check" using unsupported SMBIOS MacMini8,1.  I can perform this installation on systems with only UHD630 iGPU and with systems that have both dGPU Radeon RX 560x and iGPU UHD630.

 

Under what conditions does -no_compat_check or Skip Board ID check no longer work for installing Tahoe on systems with unsupported SMBIOS?

You don't actually need an SMBIOS specific to your hardware. For example, I could use a MacBook Pro's SMBIOS. This wouldn't change anything except for specific hardware specific to MacBooks, such as the battery, etc.
By itself, -no_compat_check does not affect the skipping of Tahoe kernel checks and if your integrated graphics are not supported in Tahoe, you probably won't be able to install it, even with the no_compat_check boot argument.

Clover's behavior in terms of boot arguments has not changed for a very long time.

Edited by MakAsrock
  • Like 1
Slice
Slice
Posted
Posted
On 7/5/2026 at 7:27 AM, MakAsrock said:

Release 5174 GCC 16.1 full implementation.
 

image.thumb.jpeg.1922f48e55c09937988c266be0ae9e4d.jpeg


Advanced SVG graphics, more fast more exact.
Repaired feature that SMBIOS choosing automatically according to OS version.
Using gcc-16.1.0 as main compiler.

MD5 (Clover_r5174.pkg) = 328c3aefe1ef80c724898c8f03d9cc96

What's Changed

 

🏅 Hall of Fame (Special Thanks):

  • Slice – for project general management and dedication.
  • YBronst – for menu refactoring, Quirks layout implementation, audio/GUI bug fixes and GCC 16.1 full implementation.
  • chris1111 – for the Tahoe/Christmas and other Themes assets.
  • Hnanoto – for ModernCPUquirk, completing PT-BR (Brazilian Portuguese) translations, and resolving UI build warnings. 🇧🇷

I am not only "management and dedication". This is me who provided rethinking long time restriction for number of clipPathes in SVG graphics.

This is me who resolved new Clover feature with SMBIOS depending on booted OS. The bug exists since January and nobody made attempts to improve something. Except MaLdOn who at least proposed to use gcc-16.1 and made new improvements in his branch. (5200?).

  • Like 2
MakAsrock
MakAsrock
Posted
Posted (edited)
1 hour ago, Slice said:

I am not only "management and dedication". This is me who provided rethinking long time restriction for number of clipPathes in SVG graphics.

This is me who resolved new Clover feature with SMBIOS depending on booted OS. The bug exists since January and nobody made attempts to improve something. Except MaLdOn who at least proposed to use gcc-16.1 and made new improvements in his branch. (5200?).

Ok, I'll add that to the release notes.
Is this normal?

🏆 Hall of Fame

slice — for general project management, profound dedication, and single-handedly rethinking the long-standing restriction on SVG clip-path counts. Resolved a critical Clover feature for OS-dependent SMBIOS injection that had been broken since January, delivering major improvements in his branch.

ybronst — for comprehensive menu refactoring, quirks layout implementation, audio/GUI bug fixes, adapting the build scripts, and updating tools_def.template for full GCC 16.1 integration.

MaLdOn — for initiating the GCC 16.1 transition by updating the build_gcc16.sh script in his branch.

chris1111 — for creating the Tahoe, Christmas, and various other high-quality theme assets.

hnanoto — for implementing ModernCpuQuirk, completing the Brazilian Portuguese (pt-BR) translations, and resolving UI build warnings. 🇧🇷

Edited by MakAsrock
  • Like 1
deeveedee
deeveedee
Posted
Posted

@MakAsrock Ok - I still didn't understand your new explanation, but no worries, because those who needed to understand probably did.  

10 hours ago, MakAsrock said:

Furthermore, the -no_compat_check boot-arg no longer works in Tahoe, and even if it did, a clean install is simply not possible with it.

 

What confused me was your statement that "-no_compat_check" boot-arg no longer works in Tahoe....   It does.

  • Like 1
MakAsrock
MakAsrock
Posted
Posted
23 minutes ago, deeveedee said:

@MakAsrock Ok - I still didn't understand your new explanation, but no worries, because those who needed to understand probably did.  

 

What confused me was your statement that "-no_compat_check" boot-arg no longer works in Tahoe....   It does.

I'm not saying this categorically, but that's what they're saying on Reddit and it doesn't work for me as expected.

deeveedee
deeveedee
Posted
Posted

@MakAsrock There are Reddit users like this Reddit user who have problems with the boot-arg, because they type it wrong.  It's a common mistake.  If you post the config.plist with the -no_compat_check boot-arg that is not working for you, I'd be happy to review.

  • Like 1
MakAsrock
MakAsrock
Posted
Posted
8 minutes ago, deeveedee said:

@MakAsrock There are Reddit users like this Reddit user who have problems with the boot-arg, because they type it wrong.  It's a common mistake.  If you post the config.plist with the -no_compat_check boot-arg that is not working for you, I'd be happy to review.

That might be true, but it doesn't work for me for some other reason. Perhaps it's because of the physical iGPU in the i7-12700KF, although it doesn't matter if it's there or not, since there's no corresponding driver anyway.
Take a look at my config, maybe I made a typo somewhere too...

config.plist.zip

 Share
Go to topic listing
×
×
  • Create New...