Clover General discussion

[Slice]

1) +

 

I think we can no more compile Clover.prefPane. AFAIK it has no more any usage.

Also we can no compile Clover.app in the common buildme. The author disappeared and the version 1.24 remains forever. We can not copy it from release to release.

[LAbyOne]

8 hours ago, Matgen84 said:

I remember the discussion for EFI Backup, but the directory is created by the cloverpkg. Will CloverConfigPlistValidator be included in the package? or Build by the Buildme ? I don't understand.

both

 

7 hours ago, Jief_Machak said:

I thought you would fork the repo to make the pull request. That way it's easy for you to work on your contribution... I can explain if you're not familiar.

and in fact i did so, forked then opened a pull request, from dropdown menu.

something else happened? 

anyway always open to explanations... maybe i did something wrong 

 

7 hours ago, Jief_Machak said:

1) About putting things in /Applications/CloverUtilities, why don't we build in a clover subfolder (probably CloverPackage) and not put anything outside ? In a general way, I think nothing should be written outside Clover, or maybe in a clear menu item that says "Install in /Applications/CloverUtils" for example.

As I always said, It obviously would be better to have a single directory for clover, BUT, someone made me notice "We" do not have that, only the few who build clover by themselves have a "Clover destination" so become very difficult to create a single folder for it. the subfolder into $HOME/src would have been the perfect place, i agree,  and that's exactly there i keep my stuff.

Btw, into the installer resources is well clear and perfectly readable when checking the option, where the tool will be installed...

 

7 hours ago, Jief_Machak said:

2) TestNewParser is not a valid tool. It was just a transition test. It's already not working anymore. I shouldn't have committed that.

sorry about that, also my mistake, forgot to remove as example.

 

7 hours ago, Jief_Machak said:

3) I also think that the validator executable file should be renamed with the version at the end. Like CloverConfigPlistValidator-v5135, or it's a build in between release something like CloverConfigPlistValidator-{7 chars sha}

i think it can be done, in a way or another

Edited May 6, 2021 by LAbyOne

[Common_Sense]

22 hours ago, Jief_Machak said:

Almost only for the kernel patching part and the Quirks part.

The discovery of bootable volumes and what's in the menu is done like before and way before OC is initialised.

 

I never really understood why I would like to see my APFS volume but not my HFS ones (or the other way around). If a volume shows up and you don't like, there is a possibility to hide it.

 

That said, we're open to feature request discussions. What do you find interesting in ScanPolicy from OC, exactly ?

 

I would say the customisability, flexibility and ease of use, is the charm with Scanpolicy. Just look at what options that would be good to have, add up the numbers and done.

 

But you are right Clover does have good options already so maybe just try and improve what we got is a better option  

 

It would be nice with 2 kinds of options to hide boot entries:

- Hide and possible to bring up with F3

- Hide and not possible to bring up with F3

 

For instance I would like to hide the ESP/EFI partitions of Windows and macOS and don't have them come up when I press F3. 

 

What do you think?

[chris1111]

A new theme very nice add to Github Black-Blue

 

5 background included

Background1024x768.png
Background1080p.png
Background1366x768.png
Background1600x900.png
Background2560x1440.png

 

 

 

You can find my theme Clover on my signature is also linked to Google Drive

 

 

Edited May 6, 2021 by chris1111

[kushwavez]

@chris1111 could you do (or is there already available) a bootcamp like theme? 

Like this:

 

It's here on github: https://github.com/CloverHackyColor/CloverThemes/tree/master/bootcamp

But the last time I checked it didn't work (around ver v5110). Or is it? 

edit: black ver. also would be awesome

Edited May 6, 2021 by kushwavez

[Jief_Machak]

13 hours ago, LAbyOne said:

and in fact i did so, forked then opened a pull request, from dropdown menu.

something else happened? 

anyway always open to explanations... maybe i did something wrong

When I looked in the pull request, I can see "Add files via upload". So I thought there was a way to upload files to a pull request without forking and committing. Which doesn't make sense...

With a fork, we can continue to work and commit on this until we take the pull request easily.

15 hours ago, Jief_Machak said:

nothing should be written outside Clover

Not sure how much you wanna help, but if you can it'll be great.

I think Slice also agree on this (he said +1) : let's buildme build things in CloverPackage only. Could you do it ?

[cecekpawon]

On 5/5/2021 at 4:43 PM, MacKonsti said:

Hi @Jief_Machak thanks from me too for posting the CloverConfigPlistValidator officially in Clover's GitHub Releases page.

For us that don't know or don't have time to build binaries etc. now that you fixed both bugs, can we ask you to either share an updated r5134-1 or r5134.1 binary in the Releases Page or at least, kindly offer it here?

This way we know everyone is using the latest fixed one. Thank you in advance!

 

Go to https://github.com/CloverHackyColor/CloverBootloader/actions

Click 1 of latest successfully built workflow

Download the artifact

 

* Need Github account

[Slice]

Hi @Jief_Machak,

something wrong when I change one theme to another (cesium to metal)

Blue buttons are not updated to metal. It is "night" in the Clover now, may be related.

[LAbyOne]

16 hours ago, Jief_Machak said:

Not sure how much you wanna help, but if you can it'll be great.

I think Slice also agree on this (he said +1) : let's buildme build things in CloverPackage only. Could you do it ?

Well fact is, it already builds into CloverPackage, what i find awkward is to have the installer install the tool onto the same directory already containing it.

 

So to be clear as it seems to be a lot of misunderstandings:

1) it already builds into CloverPackage

2) does it still need to be added into the buildpkg (*see point 3 ) and if so where should it be pointed for installation? (since it builds before the pkg, its already  present inside CloverPackage (1) )

3) please correct me if i'm wrong. The release installer from https://github.com/CloverHackyColor/CloverBootloader/releases to be used by all those who do not build their own copy, when it will be built using the modified scheme (so as per your request including the CloverConfigPlistValidator) where it's supposed to install the tool, since /Application is not to be considered and these users do not have a $HOME/src directory ?

 

4) So i guess adding it to the pkg is not really needed.

From my perspective at this point is easier anytime you post a new release to add it to the download page and let who needs just grab it from there.

What do you think?

[Jief_Machak]

9 hours ago, LAbyOne said:

1) it already builds into CloverPackage

Ok, good.

 

9 hours ago, LAbyOne said:

modified scheme

Not sure what you mean here. The xcodebuild command can you -target and -configuration therefore not use the scheme at all.

 

9 hours ago, LAbyOne said:

it's supposed to install the tool, since /Application is not to be considered

What about /usr/local/bin of the EFI partition where Clover already install things.

What about inside the EFI/CLOVER folder.

 

I'm ok with /Applications if it's the installer that does it (and not buildme script). When you start an installer, you know it'll install, so for me it's ok.

So I may have misunderstood  when you talk about /Applications earlier.

 

9 hours ago, LAbyOne said:

does it still need to be added into the buildpkg

I think so. But what you said about user getting it manually in the github release is also possible.

 

What all the users think ?

[Matgen84]

@Jief_Machak

Just my modest opinion: validator is already provided in Github release. End users can download it along with Clover, if they need to. It seems to me the easiest solution.

Advanced users can compile it manually quite easily: with instructions in a readme.file, if they wish.

[MacKonsti]

Hi everyone, @Jief_Machak and @Slice I have a bug to report for r5134 that is not there in r5133 unless the structure of config.plist changed.

No I am getting the mouse pointer in the bootloader UI main screen in r5134 despite having it disabled (setting is respected in r5133):

	<key>GUI</key>
	<dict>
		<key>EmbeddedThemeType</key>
		<string>Dark</string>
		<key>Hide</key>
		<array>
			<string>Preboot</string>
			<string>Recovery</string>
		</array>
		<key>Mouse</key>
		<dict>
			<key>Enabled</key>
			<false/>
		</dict>
		<key>ProvideConsoleGop</key>
		<true/>
		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<false/>
			<key>Tool</key>
			<true/>
		</dict>
		<key>Theme</key>
		<string>bootcamp</string>
	</dict>

Please advise? Has the setting changed in structure? I do not get an error with CloverConfigValidator. Thank you!

[LAbyOne]

39 minutes ago, Jief_Machak said:

Not sure what you mean here. The xcodebuild command can you -target and -configuration therefore not use the scheme at all.

scheme referred to the one into buildpkg to integrate ccpv, not when building CloverConfigPlistValidator itself...   

Oh yes, forgot to mention as requested ccpv, will be named after the actual clover build. this one will generate CloverConfigPlistValidator_5134

 

45 minutes ago, Jief_Machak said:

What about /usr/local/bin of the EFI partition where Clover already install things.

/usr/local/bin?

This could be the best solution, and the easiest way to use the tool from terminal even for beginners.

Proposition: if we agree to this solution, what about renaming the tool (only the one installed in /usr/local/bin) ccpv (obviously i will also add all informations into the installer location and shortened name), otherwise writing CloverConfigPlistValidator_rXXXX any time may be annoying, would that be ok?

 

55 minutes ago, Matgen84 said:

@Jief_Machak
Advanced users can compile it manually quite easily: with instructions in a readme.file, if they wish.

Advanced users will just have to choose it from buildme menu.

 

@Jief_Machak i was wondering, if there's the intention to implement the menu "Clover Utilities", i may have an idea on how to populate it, i could eventually show you some pics of a tool I already made, to get the idea.

[Jief_Machak]

25 minutes ago, LAbyOne said:

CloverConfigPlistValidator_5134

Good.

 

26 minutes ago, LAbyOne said:

ccpv

When typing into console, you have completion. So for me a long name isn't a problem.

But I like ccpv too. I don't we'll ever confuse with "Club Canin du Périgord Vert" , so it's ok by me. Does everyone prefer ccpv ?

30 minutes ago, LAbyOne said:

the intention to implement the menu "Clover Utilities"

Sure, yes.

[Jief_Machak]

2 minutes ago, MifJpn said:

the name of r_xxxx will be piled up

Yes, that's true.

But now it's possible to keep many Clover folder with any name, and inside each folder many clover efi file with any name, that means a user might need to keep different validator versions.

 

So installing it by default in a small efi partition might not be a so good idea. Well spotted @MifJpn.

 

How do we resolve that ? Is it possible that installer ask where to put it, like a save panel ?

[LAbyOne]

56 minutes ago, MifJpn said:

Thank you for the wonderful discussion.
If it is installed in the location where the command path passes (/ usr / local / bin), the name of r_xxxx will be piled up. I think "ccpv" is a good idea. It would be great if ccpv itself displayed its release number at startup.

 

Thank you.

 

it does, in fact, if that was your question...

Edited May 8, 2021 by LAbyOne

[rramon]

Hi guys,

 

updated to r5134 and get the attached error messages which I would like to fix.

 

Read the last 15 pages of this thread so got some hints for a couple of them but still don’t know how to fix the following:

 

- /ACPI/DSDT/DropOEM_DSM:12
- /GUI/Mouse/DoubleClick:266

/KernelAndKextPatches/KernelCPU:322

Could anyone provide some information on how to fix this?
Thanks a lot for the help! 

 

 

 

Edited May 8, 2021 by rramon

[Xanny]

10 minutes ago, rramon said:

Hi guys,

 

updated to r5134 and get the attached error messages which I would like to fix.

 

Read the last 15 pages of this thread so got some hints for a couple of them but still don’t know how to fix the following:

 

- /ACPI/DSDT/DropOEM_DSM:12
- /GUI/Mouse/DoubleClick:266

/KernelAndKextPatches/KernelCPU:322

Could anyone provide some information on how to fix this?
Thanks a lot for the help! 

Open your config.plist with an editor and:

- /ACPI/DSDT/DropOEM_DSM:12                delete it
- /GUI/Mouse/DoubleClick:266                   delete it

- /KernelAndKextPatches/KernelCPU:322  delete it

 

They are ignored now, some of them are from old config.plist or probably added in a wrong way by Clover Configurator app.

[rramon]

@MifJpn

 

Already in the process of doing that.

 

I‘m down to unknown keys in custom entries - checking that right now. 
 

Edit: seemed to be the „Ignore“ key that was ignored. How ignorant^^

Edited May 8, 2021 by rramon

[Jief_Machak]

23 minutes ago, Xanny said:

Clover Configurator app

If this app is still alive, I could work with the guy so his app integrate the source code of the validator in Clover Configurator app. That'll ensure that the generated XML is 100% correct.

Do you know if the app is still alive and who make this app ?

[Matgen84]

17 minutes ago, Jief_Machak said:

If this app is still alive, I could work with the guy so his app integrate the source code of the validator in Clover Configurator app. That'll ensure that the generated XML is 100% correct.

Do you know if the app is still alive and who make this app ?

The latest release Clover Configurator app = 20/03/2021. I don't know who make it, you can sent a message on mackie100 projects web site 

 

Spoiler

 

Edited May 8, 2021 by Matgen84

[Jief_Machak]

47 minutes ago, Xanny said:

- /GUI/Mouse/DoubleClick:266                   delete it

Since 2 minutes (yes 2 minutes , see the last commit), it's now possible again to configure the DoubleClick interval. But it's called DoubleClickTime.

[Jief_Machak]

13 minutes ago, Matgen84 said:

mackie100 projects web site

done.

[Matgen84]

19 minutes ago, Jief_Machak said:

Since 2 minutes (yes 2 minutes , see the last commit), it's now possible again to configure the DoubleClick interval. But it's called DoubleClickTime.

Thanks  I see the commit with default value '500'. What do you mean by "configure" DoubleClick interval again ! I don't understand well.

[Jief_Machak]

You can set the max time between 2 clicks to be recognised as a double click. It was forced to 500. Now it's default to 500 and you can change with DoubleClickTime key in config.plist