Clover General discussion

[morfy]

10 hours ago, Slice said:

Show your config.plist

It starts up regularly but does not see the latest update.

config.plist

[Slice]

Change

		<key>FirmwareFeatures</key>
		<string>0xFD8FF576</string>
		<key>FirmwareFeaturesMask</key>
		<string>0xFFDFFF7F</string>

to

		<key>ExtendedFirmwareFeatures</key>
		<string>0x8FD8FF576</string>
		<key>ExtendedFirmwareFeaturesMask</key>
		<string>0x8FFDFFF7F</string>

See carefully all changes

[Jief_Machak]

8 hours ago, chris1111 said:

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

Clover config Validator ➤ Validate nothing

More details, please.

Your config.plist, and what would you expect to be reported and that it's not.

[chris1111]

2 hours ago, Jief_Machak said:

More details, please.

Your config.plist, and what would you expect to be reported and that it's not.

Before the commit 

 

After

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

Clover config Validator ➤ Validate nothing

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

 

 

Edited October 20, 2021 by chris1111

[Matgen84]

1 hour ago, chris1111 said:

Before the commit 

 

After

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

Clover config Validator ➤ Validate nothing

 

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

 

 

 

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

 

[morfy]

3 hours ago, Slice said:

Change

		<key>FirmwareFeatures</key>
		<string>0xFD8FF576</string>
		<key>FirmwareFeaturesMask</key>
		<string>0xFFDFFF7F</string>

to

		<key>ExtendedFirmwareFeatures</key>
		<string>0x8FD8FF576</string>
		<key>ExtendedFirmwareFeaturesMask</key>
		<string>0x8FFDFFF7F</string>

See carefully all changes

 

File modified, starts regularly but update does not see it.

[Slice]

56 minutes ago, morfy said:

 

File modified, starts regularly but update does not see it.

If you have no RestrictEvents.kext then install it.

Otherwise remove it.

[morfy]

13 minutes ago, Slice said:

If you have no RestrictEvents.kext then install it.

Otherwise remove it.

I removed from the kext folder on the EFI I deleted RestrictEvents.kext and here's the update!

[morfy]

@Slice update installed. Usual 2 restarts. thank you so much for your support  

[Gradou]

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

 

[Slice]

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

[Gradou]

25 minutes ago, Slice said:

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

"And no back !" I don't understand !!!??

[kushwavez]

I still don't understand why is it working for me with the old Clover v5138 without any modifications. Maybe the older SMBIOS? I'm using MBP11,4

 

[Jief_Machak]

7 hours ago, chris1111 said:

Before the commit 

 

After

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

Clover config Validator ➤ Validate nothing

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.

[chris1111]

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

d

Edited October 20, 2021 by chris1111

[LAbyOne]

@chris1111

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

 

becose tested with old version here

and got this

So

just build the latest and got this

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

[chris1111]

1 hour ago, LAbyOne said:

@chris1111

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

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

Yes thanks thats make sens

[LAbyOne]

@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

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

[LockDown]

@Slice

boot7 is gone?

 

BTW, legacy needs openruntime in BIOS folder, else it wont boot to desktop.

Edited October 21, 2021 by LockDown

[chris1111]

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

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 October 21, 2021 by chris1111

[rramon]

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 October 21, 2021 by rramon

[Gradou]

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

[rramon]

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

 

 

 

 

 

[SavageAUS]

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

[Gradou]

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