Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

On 10/19/2021 at 6:42 AM, SavageAUS said:



 

19 hours ago, SavageAUS said:


MacBookPro16,4 and iMacPro1,1.
Both updated now just had to use OC by booting from USB to get the update to show then just let Clover do the rest.


Sent from my iPhone using Tapatalk


Sent from my iPhone using Tapatalk

With Clover 5141 and SMBIOS iMacPro1,1 for Update 12.0.1 : 2 sequences for me :

 

1) Without RestrictEvents, boot Clover with config.plist containing (in BIOS section) ExtendedFirmwareFeatures 0x8FD8FF53E and ExtendedFirmwareFeaturesMask 0x8FF9FFF3F (without "old" FirmwareFeatures & FirmwareFeaturesMask) and this key :

<key>RtVariables</key>
<dict>
<key>HWTarget</key>
<string>J137AP</string>

to see the update

2) While the update is downloading, put RestrictEvents in Kext folder, and disable the HWTarget Key, otherwise the update is not done (in my situation anyway).

It is not very simple !!😄 But this is the only way, apart from using a non-T2 SMBIOS, that I have found to achieve this update.

 

I hope Slice will find it easier

 

Link to comment
Share on other sites

7 hours ago, chris1111 said:

Before the commit 

885351885_ScreenShot2021-10-20at6_41_44AM.png.99561ff4df2891b5f7758de0cb47f36f.png

 

After

latest commit  https://github.com/CloverHackyColor/CloverBootloader/commit/710b2dcee554de0a06627b0797a16cf8adb669ce

Clover config Validator ➤ Validate nothing

1149278347_ScreenShot2021-10-20at6_39_20AM.png.76d7719de41bbfbf5ffca7da4285c377.png

Not test latest today commit https://github.com/CloverHackyColor/CloverBootloader/commit/be9b4c2d7fef57e75ceb8f12bab41202348f8ad2 if that fix 

 

 

 

6 hours ago, Matgen84 said:

 

CCPV don't work also with commit be9b4c2d7 😪 Wait and see.

 

ccpv worked. It was just that the message "Your plist looks so wonderful"  wasn't displayed.

Fixed.

  • Like 3
  • Haha 1
Link to comment
Share on other sites

2 hours ago, Jief_Machak said:

 

ccpv worked. It was just that the message "Your plist looks so wonderful"  wasn't displayed.

Fixed.

Your fixed not fixed

Validator validate nothing from config.plist

This is used to validate, then how can you say that it works if you do not see the errors or the warnings or simply display that it is good?

Please explain to me because I don't understand

d1565908726_ScreenShot2021-10-20at4_30_38PM.png.35c53020ad7bd9e91900a6b5bc84c1a5.png

Edited by chris1111
Link to comment
Share on other sites

@chris1111

maybe you'r plist is fine the way it is?

 

becose tested with old version here

512594934_Screenshot2021-10-20at23_21_28.png.b79293e7a034b17b589f2b5e2e6e3335.png

and got this

So

just build the latest and got this

516043596_Screenshot2021-10-20at23_21_41.png.50b15916174aa2f52a72c015daf37208.png

so the tool seems working

 

Then if Not working for you means No flattered plist that's another thing.

Do not forget the old saying -> no news good news :)

  • Like 4
Link to comment
Share on other sites

@chris1111

Just out of curiosity I gave a quick look at the code, and the message is there, so no way it wouldn't appear

normally when the plist is correct you should see it

infact doing a test with config-sample.plist here's what i get

2087006422_Screenshot2021-10-21at02_47_19.png.f13a759ecce5547bd96d299a739c1aa5.png

so i was wondering if something is happening with your plist...

can you try also with clover's sample.plist and see what gives?

if that gives you the same and the one you have installed still gives none

there's probably something that prevent it. just assuming...

  • Like 1
Link to comment
Share on other sites

18 minutes ago, LAbyOne said:

@chris1111

Just out of curiosity I gave a quick look at the code, and the message is there, so no way it wouldn't appear

normally when the plist is correct you should see it

infact doing a test with config-sample.plist here's what i get

2087006422_Screenshot2021-10-21at02_47_19.png.f13a759ecce5547bd96d299a739c1aa5.png

so i was wondering if something is happening with your plist...

can you try also with clover's sample.plist and see what gives?

if that gives you the same and the one you have installed still gives none

there's probably something that prevent it. just assuming...

I test the config simple.plist it say plist wonderfull but explain my why before the commit the validator validate

my plist and the sample plist both wonderfull then now it say nothing

maybe somthing new mandatary on the plist file for validate? I will check the diferance of the file

Edited by chris1111
  • Like 1
Link to comment
Share on other sites

15 hours ago, Gradou said:

With Clover 5141 and SMBIOS iMacPro1,1 for Update 12.0.1 : 2 sequences for me :

 

1) Without RestrictEvents, boot Clover with config.plist containing (in BIOS section) ExtendedFirmwareFeatures 0x8FD8FF53E and ExtendedFirmwareFeaturesMask 0x8FF9FFF3F (without "old" FirmwareFeatures & FirmwareFeaturesMask) and this key :

<key>RtVariables</key>
<dict>
<key>HWTarget</key>
<string>J137AP</string>

to see the update

2) While the update is downloading, put RestrictEvents in Kext folder, and disable the HWTarget Key, otherwise the update is not done (in my situation anyway).

It is not very simple !!😄 But this is the only way, apart from using a non-T2 SMBIOS, that I have found to achieve this update.

 

I hope Slice will find it easier

 


@Gradou @Slice
 

Does this mean that we have to remove FirmwareFeatures and FirmwareFeaturesMask alltogether from our config.plist?

 

I am confused because prior it was said to add Extended values and leave the „old“ values in place.

 

What‘s the correct way?

 

 

13 hours ago, Slice said:

I have the update just after removing HWTarget. And no back!


What do you mean exactly?

 

Thanks both for clarifying :)

Edited by rramon
Link to comment
Share on other sites

15 hours ago, Gradou said:

With Clover 5141 and SMBIOS iMacPro1,1 for Update 12.0.1 : 2 sequences for me :

 

1) Without RestrictEvents, boot Clover with config.plist containing (in BIOS section) ExtendedFirmwareFeatures 0x8FD8FF53E and ExtendedFirmwareFeaturesMask 0x8FF9FFF3F (without "old" FirmwareFeatures & FirmwareFeaturesMask) and this key :

<key>RtVariables</key>
<dict>
<key>HWTarget</key>
<string>J137AP</string>

to see the update

2) While the update is downloading, put RestrictEvents in Kext folder, and disable the HWTarget Key, otherwise the update is not done (in my situation anyway).

It is not very simple !!😄 But this is the only way, apart from using a non-T2 SMBIOS, that I have found to achieve this update.

 

I hope Slice will find it easier

 

Modifications :

1) With (and not without) RestrictEvents and its bootarg: -revsbvmm
2) Remove only the HWTarget Key, we can leave RestrictEvents and its bootarg: -revsbvmm

Link to comment
Share on other sites

@Gradou

 

This is the first time I read about a bootarg that needs to be set if one is using RestrictEvents.kext 

 

Anyway, I am talking about the settings when not using the kext.

 

And in the quoted post you stated that one has to boot without the „old“ values for FirmwareFeatures and FirmwareFeaturesMask. This is the first time I read this because - as I said - it was said to add the new values and not to remove the old ones.

 

 

 

 

 

Link to comment
Share on other sites

Clarification is definitely needed.
Do we need RestrictEvents kext?
If so does it need a bootarg?

Do we need the ExtendedFirmwareFeatures and it’s mask?

Do we also need FirmwareFeatures and it’s mask or just ExtendedFirmwareFeatures and it’s mask?

All these broken poorly informed posts are getting beyond the joke.


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

41 minutes ago, SavageAUS said:

Clarification is definitely needed.
Do we need RestrictEvents kext?
If so does it need a bootarg?
Yes
Do we need the ExtendedFirmwareFeatures and it’s mask?
Yes
Do we also need FirmwareFeatures and it’s mask or just ExtendedFirmwareFeatures and it’s mask?
Just ExtendedFirmwareFeatures and it’s mask

You need also HWTarget Key to obtain the update, but remove it to install
All these broken poorly informed posts are getting beyond the joke.

I don't untderstand, are you angry ? if Yes, why ?

you could be kind anyway, right ?


Sent from my iPhone using Tapatalk

 

Link to comment
Share on other sites

@Matgen84

all those plist issues are apparently caused by the new default "Efiversion" string.

as @MifJpnAlphaPlus reported, commenting it out, gives the expected statement,

while rolling back to the older version gives obviously the error.

So just wait until @Jief_Machak find out what's causing this

Edited by LAbyOne
  • Like 2
Link to comment
Share on other sites

9 hours ago, rramon said:


@Gradou @Slice
 

Does this mean that we have to remove FirmwareFeatures and FirmwareFeaturesMask alltogether from our config.plist?

 

I am confused because prior it was said to add Extended values and leave the „old“ values in place.

 

What‘s the correct way?

 

 


What do you mean exactly?

 

Thanks both for clarifying :)

In the new systems like Monterey bootefi asked about ExtendedFirmwareFeatures and if not found then FirmwareFeatures.

So we may keep only extended.

But I am not sure about old systems on old hardware. So my recommendation is to keep both features. There is no conflicts.

 

Next question is HWTarget. 

I implemented this feature but I don't know its influence on the system. I am watching if someone will use this feature and found some advantage. Still no.

My experience that with HWTarget I see no SoftwareUpdate while without it I got the update.

So I removed it from my config.plist forever and ever. (...no back...)

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

20 minutes ago, Slice said:

Next question is HWTarget. 

I implemented this feature but I don't know its influence on the system. I am watching if someone will use this feature and found some advantage. Still no.

My experience that with HWTarget I see no SoftwareUpdate while without it I got the update.

So I removed it from my config.plist forever and ever. (...no back...)

 

Thanks @Slice HWTarget might be useful for those using SMBIOS T2 chips like Imac20 for example. 

Link to comment
Share on other sites

On 10/20/2021 at 10:32 PM, chris1111 said:

Your fixed not fixed

Validator validate nothing from config.plist

This is used to validate, then how can you say that it works if you do not see the errors or the warnings or simply display that it is good?

Please explain to me because I don't understand

d1565908726_ScreenShot2021-10-20at4_30_38PM.png.35c53020ad7bd9e91900a6b5bc84c1a5.png

 

Chris, here everything is working normally

I use the PKG and the Clover Configurator of the Github of this same compilation

look here before and after and everything is normal

1

Spoiler

1625971019_Capturedecran2021-10-22a01_15_41.png.e01120439c9973e04bca3303fbb7a59b.png



2

Spoiler

335430090_Capturedecran2021-10-22a01_16_30.png.5e86797a9f79721bcfa31a13bfdfc0d0.png

 

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...