Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

On 5/20/2024 at 2:17 PM, Matgen84 said:

Hi @Slice @LAbyOne

Can you update buildme script with that: curl -sLq https://github.com/jief666/BootloaderChooser/releases/latest > "${CLOVERROOT}"/CloverPackage/BootLoaderChooser/BootX64.efi instead of older bootloaderchooser version 0.5 ! Please

 

well into buildme

the actual link to get the download is

curl -sLq https://github.com/jief666/BootloaderChooser/releases/download/0.5/BootX64.efi > "${CLOVERROOT}"/CloverPackage/BootLoaderChooser/BootX64.efi

so the updated one would normally look like this

curl -sLq https://github.com/jief666/BootloaderChooser/releases/download/1.4/BootX64.efi > "${CLOVERROOT}"/CloverPackage/BootLoaderChooser/BootX64.efi

 

 

On 5/20/2024 at 2:17 PM, Matgen84 said:

Hi @Slice @LAbyOne
I test to build Clover with GCC132 and GCC14, without success: not define toolchain error 😪
Have a nice day

 

the actual defined default toolchain in clover source is GCC131 (so since GCC132 and GCC14 are defined nowhere, its only natural you get such an error)

that said (tested from 10.13.6 to Monterey, as ventura or sonoma will be the same),

build works perfectly either using gcc 13.0.3 or gcc 14.0.1

gcc 14.0.1 and binutils 2.42 need to be patched for backward OS compatibility (pre BS) otherwise build fail

but i guess you'r not concerned by that.

Have a nice day

  • Like 2
Link to comment
Share on other sites

On 5/21/2024 at 8:27 AM, Slice said:

OK, but I tried "latest" and it is not working. The working solution is "1.4". Can you verify your line?

 

Hi @Slice

It's working for me. "latest" is redirected to : https://github.com/jief666/BootloaderChooser/releases/tag/1.4. So if I don't mistaken, it took the latest tag !

  • Like 1
Link to comment
Share on other sites

Posted (edited)
On 5/23/2024 at 3:16 PM, LAbyOne said:

 

well into buildme

the actual link to get the download is

curl -sLq https://github.com/jief666/BootloaderChooser/releases/download/0.5/BootX64.efi > "${CLOVERROOT}"/CloverPackage/BootLoaderChooser/BootX64.efi

so the updated one would normally look like this

curl -sLq https://github.com/jief666/BootloaderChooser/releases/download/1.4/BootX64.efi > "${CLOVERROOT}"/CloverPackage/BootLoaderChooser/BootX64.efi

 

 

 

the actual defined default toolchain in clover source is GCC131 (so since GCC132 and GCC14 are defined nowhere, its only natural you get such an error)

that said (tested from 10.13.6 to Monterey, as ventura or sonoma will be the same),

build works perfectly either using gcc 13.0.3 or gcc 14.0.1

gcc 14.0.1 and binutils 2.42 need to be patched for backward OS compatibility (pre BS) otherwise build fail

but i guess you'r not concerned by that.

Have a nice day

 

How to use gcc 14.1.0 for building. This version is marked in build_gcc14.sh.
 

Thanks

Edited by Matgen84
Link to comment
Share on other sites

2 minutes ago, Matgen84 said:

 

How to use gcc 14.1.0 for building. This version is marked in build_gcc14.sh.
 

Thanks

Same GCC131.

  • Like 2
Link to comment
Share on other sites

1 hour ago, Slice said:

Same GCC131.

 

I don't understand what you means. Can you explain (I'm a newbie, sorry)?

Link to comment
Share on other sites

12 hours ago, Matgen84 said:

 

I don't understand what you means. Can you explain (I'm a newbie, sorry)?

You should think nothing. Just use buildme. The default toolchain is GCC131.

If you have no gcc then buildme will create new one from sources 14.1. Without asking you "do you want version 13 or 14?".

With what version of xcode do you really use XCODE5 toolset? Did you ask Acidanthera about Xcode version?

Toolset is toolset and it has own enumeration.

  • Thanks 1
Link to comment
Share on other sites

Posted (edited)
On 5/25/2024 at 9:48 PM, Slice said:

You should think nothing. Just use buildme. The default toolchain is GCC131.

If you have no gcc then buildme will create new one from sources 14.1. Without asking you "do you want version 13 or 14?".

With what version of xcode do you really use XCODE5 toolset? Did you ask Acidanthera about Xcode version?

Toolset is toolset and it has own enumeration.

 

Actually, I use XCODE 14.3 to build Clover. I sent you a MP before reading your comment !

 

Now I try to reproduce GCC building with your explanation. But if GCC exist, what is the correct procedure.

 

EDIT: I launch buildme without args on my Monterey system: 

1) build Clover (Default Toolchain)	 	 8) 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: 1
[CHECK XCODE]
- Building GCC 13.2.0 toolchain for x64
- to /Users/mathieu/src/Cloverbootloader/toolchain/cross/bin/x86_64-clover-linux-gnu
  Running on Mac OS X 12.7, with x86_64 architecture.
  Using Xcode SDK: /Applications/Xcode-14.3.0.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
Status: gmp-6.3.0 not found.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2045k  100 2045k    0     0  1655k      0  0:00:01  0:00:01 --:--:-- 1657k
Warning: Got more output options than URLs
Status: mpfr-4.2.1 not found.

 

Edited by Matgen84
Link to comment
Share on other sites

Quote
Status: gmp-6.3.0 not found.

The message mean it is not found in your computer so it will be downloaded from outer server. An next I see the success.

  • Confused 1
Link to comment
Share on other sites

On 5/27/2024 at 4:03 AM, Matgen84 said:

 

Actually, I use XCODE 14.3 to build Clover. I sent you a MP before reading your comment !

 

Now I try to reproduce GCC building with your explanation. But if GCC exist, what is the correct procedure.

 

EDIT: I launch buildme without args on my Monterey system: 

1) build Clover (Default Toolchain)	 	 8) 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: 1
[CHECK XCODE]
- Building GCC 13.2.0 toolchain for x64
- to /Users/mathieu/src/Cloverbootloader/toolchain/cross/bin/x86_64-clover-linux-gnu
  Running on Mac OS X 12.7, with x86_64 architecture.
  Using Xcode SDK: /Applications/Xcode-14.3.0.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
Status: gmp-6.3.0 not found.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2045k  100 2045k    0     0  1655k      0  0:00:01  0:00:01 --:--:-- 1657k
Warning: Got more output options than URLs
Status: mpfr-4.2.1 not found.

 

 

Hi @Matgen84 

You can try first build all  - is number 2) 

You can use Command Line Tools with xcode 15.2 if you not can finish compilation with Xcode 15.3, but I recommend you use Ventura or Sonoma. With Monterey the boot is very lower and lazy more than 30 seconds. 

With Ventura or Sonoma you can compile and get better boot faster, until 9 or 10 seconds. 

You can use available beta files to download from GitHub that is compile same away like in your machine, here:

 

 

https://github.com/CloverHackyColor/CloverBootloader/actions/runs/9054001371 

 

Need login account 

 

CloverV2-5158.zip 

 

Or use this file above dowloaded from Git 

 

 

Link to comment
Share on other sites

  • 2 weeks later...

Here everything works fine, Sequoia and Sonoma, using a new Clover 5159 (commit 30b3ac544), and compiled with Xcode 15.1 and command line tools 15.1 too. 

 

 

 

 

 

image.png.4dcb3fcf1bda0eca0ca8488569b35c83.png

 

 

  • Like 8
Link to comment
Share on other sites

11 hours ago, Matgen84 said:

Hi @Slice

Thanks for release 5159 😊 Could you add os_sequoia to the list of os icons supported, please.

Already done.

  • Like 7
  • Thanks 1
Link to comment
Share on other sites

15 minutes ago, jackacc said:

opencore  have    ocat 

 

opencore (config.plist)   Configuration file template

 

 

clover (config.plist)?

It is config-sample.plist. It is one for all because Clover is able to configure hardware automatically.

  • Like 4
Link to comment
Share on other sites

Try use Clover Configurator, and he fix automatic errors from your plist. 

 

Need put Devices and boot args, and I recommend  you try EFI basic from Olarila.com and if you need, ask for @MaLd0n help you!! He is Olarila owner 

 

 

https://www.olarila.com/topic/5676-hackintosh-efi-folder-with-clover-and-opencore/ 

 

 

https://mackie100projects.altervista.org/download-clover-configurator/ 

 

 

image.thumb.png.81af9c6cdba423e637a6462fa55b0f90.png

 

 

 

 

 

 

 

 

 

 

2 hours ago, cankiulascmnfye said:

Got Clover r5159 working on my Lenovo T490 with Sequoia. Intel BT is not working, but that's a kext issue.

 

Maybe you should try use @Shaneee kexts but its important use Opencore ResetNvram, I have no idea why Clover not clean totally Nvram. 

 

 

 

And need put parameters on boot or in Nvram 

 

First: 

 

sudo nvram bluetoothHostControllerSwitchBehavior=always

 

sudo rm -f /Library/Preferences/com.apple.Bluetooth

 

Them: 

 

Or use Opencore to boot and Clean Nvram and reboot to Clover. 

 

Or just put on Nvram this args 

 

sudo nvram bluetoothInternalControllerInfo=0

sudo nvram bluetoothExternalDongleFailed=0

 

 

 

Edited by Max.1974
  • Like 2
Link to comment
Share on other sites

HI, id like to use clover with Catalina on an amd laptop. I added the kernel patches and the same kexts from the working config in opencore but it stucks early on boot. Is there a guide to config clover properly?

Link to comment
Share on other sites

×
×
  • Create New...