Clover General discussion

[Gradou]

1 hour ago, SavageAUS said:

Well which ever is being offered is downloaded but not installing. I have tried numerous times with different settings but I get a reboot a certain spot each time and it’s too fast for a pic.
I’ll keep messing with it. Thanks for help.


Sent from my iPhone using Tapatalk

With Clover 5141, if your download did not allow the update, you must redownload the suggested update. During this re-download do not forget to remove the whole HWTarget key : <key> HWTarget </key>
<string> J137AP </string> (and save your config..pist before restarting the update otherwise the HWTarget key will cause a reboot without an update in RC2 12.0.1 (21A559)) and try to change the order of ExtendedFirmwareFeatures & ExtendedFirmwareFeaturesMask in your config.plist...

 

Edited October 22, 2021 by Gradou

[SavageAUS]

With Clover 5141, if your download did not allow the update, you must redownload the suggested update. During this re-download do not forget to remove the whole HWTarget key :  HWTarget
J137AP  (and save your config..pist before restarting the update otherwise the HWTarget key will cause a reboot without an update in RC2 12.0.1 (21A559)) and try to change the order of ExtendedFirmwareFeatures & ExtendedFirmwareFeaturesMask in your config.plist...
 

I honestly thought commenting it out would be enough. I’ll try downloading it again then removing HWTarget completely before the first reboot.
The update seems to be installing properly this time, is it safe to add back HWTarget after the update is all done?

Thank you for your help.


Sent from my iPhone using Tapatalk

[chris1111]

Latest Clover commit

Wonderfull plist Wel Done 

Boot Clover r5141 (162150e5b)

[Slice]

1 hour ago, chris1111 said:

Latest Clover commit

Wonderfull plist Wel Done 

Boot Clover r5141 (162150e5b)

@Jief_Machak

I think these Info will be good for ccpv not for release Clover as user don't know what to change to cancel such messages.

[SavageAUS]

@Slice
Clovers AudioDXE is still very sketchy / glitchy on AMD with Clover 5141.


Sent from my iPhone using Tapatalk

[Ellybz]

On 10/21/2021 at 3:16 AM, SavageAUS said:

No not angry nor do I need to explain my post.
Just simply stating the facts.


Sent from my iPhone using Tapatalk

 A little joke to light the mood, If you do not understand the saying" It's not what you said, it's the way you said it", You need to spend more time around the female species 😂. Have a good week-end everyone 🖖

Edited October 23, 2021 by Ellybz

[matxpa]

9 hours ago, Slice said:

@Jief_Machak

I think these Info will be good for ccpv not for release Clover as user don't know what to change to cancel such messages.

 

@Jief_Machak  @Slice 

 

Hi Slice

 

Look at #462 issue in (your) CloverHackyColor/CloberBootloader REPO.

 

regards

Edited October 23, 2021 by matxpa
Look instead of Lokk

[SavageAUS]

 A little joke to light the mood, If you do not understand the saying" It's not what you said, it's the way you said it", You need to spend more time around the female species . Have a good week-end everyone 

Trust me I understand the saying very well, my wife tells me all the time.


Sent from my iPhone using Tapatalk

[chris1111]

8 hours ago, Slice said:

@Jief_Machak

I think these Info will be good for ccpv not for release Clover as user don't know what to change to cancel such messages.

@Slice its not a big probleme to correct this infos in config.plist, the probleme is the validator did not recognise the error when validating

Then User make a correction to avoid this on boot

[Slice]

18 minutes ago, chris1111 said:

@Slice its not a big probleme to correct this infos in config.plist, the probleme is the validator did not recognise the error when validating

Then User make a correction to avoid this on boot

For my mind the problem is there is no error. "is the same as default" - why it is the error? What user should correct?

[chris1111]

13 minutes ago, Slice said:

For my mind the problem is there is no error. "is the same as default" - why it is the error? What user should correct?

The validator must indicate what must be corrected because presentely it indicates nothing as shown on my image but when you boot on Clover we can see that things must be modified in the config.plist
Here is the point

Edited October 23, 2021 by chris1111

[Jief_Machak]

9 hours ago, Slice said:

@Jief_Machak

I think these Info will be good for ccpv not for release Clover as user don't know what to change to cancel such messages.

I'm pretty sure the user guess what to do when the message say that it is ignored, even saying the line to remove in config.plist.

 

But also, yes, I agree, the info messages are not supposed to be displayed by Clover. Info messages is just something I've created.

Messages displayed by Clover are supposed to be the "errors" only. By error, I mean a value that is ignored and an other value is used instead, potentially leading to unexpected result.

When a value is ignored because it is the same as the one that Clover will use by default, it's not a mistake, just redondant. Therefore no message should be displayed by Clover. Ccpv will displayed them only if you ask for it with a "--info", for example. "--info" is not done yet, and ccpv currently doesn't display any info messages. Hence the difference.

There is also messages that Ccpv can't display if ProductName is not defined. In that case, they will be displayed, but the message "use ccpv" should be avoided.

 

Story short : some work to do...

26 minutes ago, Slice said:

For my mind the problem is there is no error. "is the same as default" - why it is the error? What user should correct?

There is no error. That's why the message starts with "Info:" instead of "Warning:" or "Error:" 

 

2 minutes ago, Jief_Machak said:

Messages displayed by Clover are supposed to be the "errors" only

 

[matxpa]

32 minutes ago, Jief_Machak said:

I'm pretty sure the user guess what to do when the message say that it is ignored, even saying the line to remove in config.plist.

 

But also, yes, I agree, the info messages are not supposed to be displayed by Clover. Info messages is just something I've created.

Messages displayed by Clover are supposed to be the "errors" only. By error, I mean a value that is ignored and an other value is used instead, potentially leading to unexpected result.

When a value is ignored because it is the same as the one that Clover will use by default, it's not a mistake, just redondant. Therefore no message should be displayed by Clover. Ccpv will displayed them only if you ask for it with a "--info", for example. "--info" is not done yet, and ccpv currently doesn't display any info messages. Hence the difference.

There is also messages that Ccpv can't display if ProductName is not defined. In that case, they will be displayed, but the message "use ccpv" should be avoided.

 

Story short : some work to do...

There is no error. That's why the message starts with "Info:" instead of "Warning:" or "Error:" 

 

 

@Jief_Machak 

 

Hi

 

Could you have a look at your message box and Clover issue N° 462.

 

Regards

[MacKonsti]

Hi everyone! A kind request as some of us find it hard to follow the exchanges here (yes I am one of them)

 

a) Please, is there is a fixed version of ccpv Clover Validator for r5141 can some kind soul post it here? @Jief_Machak do you have such build/binary perhaps?

 

b) Can someone update us on how to officially use r5141 for Monterey, since it's coming out tomorrow?

Eventually, what is needed extra in the config compared to Big Sur? I read @Slice having mentioned extended firmware features and dropping the HWTarget key altogether, eventually.

Perhaps a sample of a working config for me to compare the keys and understand it, if you don't have time for a mini-paragraph?

 

c) @Slice do we expect a r5142 in the next days, in your opinion, as Monterey final is released tomorrow? I mean, are there newer fixes after official r5141 release that are important for us to use?

 

Thank you all !

[Jief_Machak]

Hi, I'm not following problems about Monterey, but if an update of OpenCorePkg is needed, let me know, I can do it.

[SavageAUS]

Hi, I'm not following problems about Monterey, but if an update of OpenCorePkg is needed, let me know, I can do it.

Which version of OC is bundled with Clover now? 0.7.3 if I remember reading correctly. 0.7.4 is released.
I think it would be best to to maintain a release cycle with OC’s release version instead of just updating with major changes.


Sent from my iPhone using Tapatalk

[SavageAUS]

Hi everyone! A kind request as some of us find it hard to follow the exchanges here (yes I am one of them)
 
a) Please, is there is a fixed version of ccpv Clover Validator for r5141 can some kind soul post it here? [mention=1176907]Jief_Machak[/mention] do you have such build/binary perhaps?
 
Can someone update us on how to officially use r5141 for Monterey, since it's coming out tomorrow?
Eventually, what is needed extra in the config compared to Big Sur? I read [mention=112217]Slice[/mention] having mentioned extended firmware features and dropping the HWTarget key altogether, eventually.
Perhaps a sample of a working config for me to compare the keys and understand it, if you don't have time for a mini-paragraph?
 
c) [mention=112217]Slice[/mention] do we expect a r5142 in the next days, in your opinion, as Monterey final is released tomorrow? I mean, are there newer fixes after official r5141 release that are important for us to use?
 
Thank you all !

For me, with Clover 5141 to update the latest Beta’s (except RC2) I have needed to use OC to initiate the update then let clover take over after the first reboot. How ever with RC2 I was taught a few things.
HWTarget rtvariable was used to initiate the download process of the new update but I had to delete (not comment out) the HWTarget from rtvariables before the first reboot or else I would get stuck in a reboot loop.
I also only used the ExtendedFirmwareFeatures and it’s Mask and commented out the standard FirmwareFeatures and it’s Mask.
I also had RestrictEvents kext in place.
So I cannot say if all of the above are needed but this is what eventually worked for me.
As usual your mileage may vary but the above worked for me when nothing else would on both my hacks with MacBookPro16,4 and iMacPro1,1 smbios.


Sent from my iPhone using Tapatalk

[Slice]

1 hour ago, MacKonsti said:

Hi everyone! A kind request as some of us find it hard to follow the exchanges here (yes I am one of them)

 

a) Please, is there is a fixed version of ccpv Clover Validator for r5141 can some kind soul post it here? @Jief_Machak do you have such build/binary perhaps?

 

b) Can someone update us on how to officially use r5141 for Monterey, since it's coming out tomorrow?

Eventually, what is needed extra in the config compared to Big Sur? I read @Slice having mentioned extended firmware features and dropping the HWTarget key altogether, eventually.

Perhaps a sample of a working config for me to compare the keys and understand it, if you don't have time for a mini-paragraph?

 

c) @Slice do we expect a r5142 in the next days, in your opinion, as Monterey final is released tomorrow? I mean, are there newer fixes after official r5141 release that are important for us to use?

 

Thank you all !

Current release 5141 works fine with Monterey RC2.

5142 is not yet expected because no functional changes.

[PG7]

On 10/24/2021 at 3:56 PM, Slice said:

Current release 5141 works fine with Monterey RC2.

5142 is not yet expected because no functional changes.

 

Yes, confirmed

 

clover always as expected VERY functional

update passed without problem Clover r5141 with kext to day

4 reboots during the process and an average of 25 minutes Monterey GM

 

Thanks Team Clover

 

Spoiler

 

[Jief_Machak]

Starting OC upgrade. So, if possible, no commit please.

[Slice]

OK

[SavageAUS]

Starting OC upgrade. So, if possible, no commit please.

To which version? And when?
Will a new clover be released to reflect the OC upgrade?


Sent from my iPhone using Tapatalk

[Allan]

Thanks @Jief_Machak, waiting this new Clover release before upgrade to Monterey.

 

Hey @Slice! As you explained at the Clover Change Explanations about the ExtendedFirmwareFeatures feature, I just need to use only it to install Monterey and gets updates available right?

 

Like this 👇🏽

 

 

Thank you guys

 

[PG7]

Hello @Jief_Machak

 

there is a problem with Clover,
I explain:
I have a PC with Legacy bios versions and where clover does the entire installation process but at the end of 1 part of the 12 minutes it shows an error (une error is only produced by the installation preparation. try to run this app again)

 

if you reboot the pc hard it will show the partition with the installer on the normal disk but if you continue it will do the installation process for 29 minutes and at the end another error

(une error is the product of the application of the software update)

this same problem is happening to many members of the community but mainly on pc without UEFI (I've also seen this same error on recent pc)

 

I didn't get any logo!

when you have time so we can see together and try to solve it, let me know so we can do it.

thank you and good sequels
good job Clover always big

" there will be errors in the translation of the text as it has already happened but I use the google translator

I hope you understand or if you have any doubts let me know that I use another language in private

sorry in advance to the rest of the community if it's not understandable "

[Gradou]

Clover 5141 : update for beta 12.1 : OK, (with SMBIOS iMacPro1,1) : kext RestrictEvents (without bootarg), ExtendedFirmwares, no HWTarget key

Edited October 29, 2021 by Gradou