Clover General discussion

[chris1111]

3 hours ago, MifJpnAlphaPlus said:

Hello.

me too.

Please use it for testing,if you can.

config.plist.zip 6.05 kB · 5 downloads

Thank you.

 

The plist  not works

Spoiler

 

Edited October 21, 2021 by chris1111
Not works

[SavageAUS]

 

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


Sent from my iPhone using Tapatalk

[chris1111]

4 minutes ago, MifJpnAlphaPlus said:

Hello.
Sorry for the lack of explanation.
If I comment out the Efiversion in the config.plist or add one, ccpv says "Good!”
I wonder why.
Thanks.

Tell im  to @Jief_Machak I dont know

[Matgen84]

Hi @Jief_Machak

I try commit 23e4b83 : ccpv display nothing if my IvyBridge config.plist and my Z390 config.plist are good 😪  Maybe I misunderstood the commit.
 

[LAbyOne]

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

[Slice]

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

[Matgen84]

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. 

[SavageAUS]

If I knew what value to set for hw.target it might be useful too. MacBookPro16,4 and iMacPro1,1.


Sent from my iPhone using Tapatalk

[PG7]

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

d

 

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

2

Spoiler

 

[LAbyOne]

New Update

nothing major fixed a few links reported not working on Docu section.

Added also a new Source for customized hardware config plists

Sorry for the trouble guys.

Edited October 22, 2021 by LAbyOne

[Slice]

On 10/21/2021 at 4:13 AM, LockDown said:

@Slice

boot7 is gone?

 

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

Why this question? boot7 is still here.

[Gradou]

10 hours ago, SavageAUS said:

If I knew what value to set for hw.target it might be useful too. MacBookPro16,4 and iMacPro1,1.


Sent from my iPhone using Tapatalk

 

Clover 5141 is needed

MacBookPro16,4 : J215AP

iMacPro1,1 : J137AP

Is this information clear enough or do you need more details ? 🤔😃

.../...

All the same I repeat, as clearly as possible, the procedure that I adopted with iMacPro1,1:

1) With RestrictEvents and its bootarg: -revsbvmm, 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 disable the HWTarget Key, otherwise the update is not done (in my situation anyway).

 

NOTA BENE : It is obvious, but I specify it, that with another SMBIOS (T2), it will be necessary to change the values of :
ExtendedFirmwareFeatures & ExtendedFirmwareFeaturesMask
and of  :
HWTarget

 

Edited October 22, 2021 by Gradou

[SavageAUS]

 
Clover 5141 is needed
MacBookPro16,4 : J215AP
iMacPro1,1 : J137AP
Is this information clear enough or do you need more details ? 
.../...
All the same I repeat, as clearly as possible, the procedure that I adopted with iMacPro1,1:
1) With RestrictEvents and its bootarg: -revsbvmm, boot Clover with config.plist containing (in BIOS section) ExtendedFirmwareFeatures 0x8FD8FF53E and ExtendedFirmwareFeaturesMask 0x8FF9FFF3F (without "old" FirmwareFeatures & FirmwareFeaturesMask) and this key:
RtVariables

HWTarget
J137AP
to see the update
2) While the update is downloading disable the HWTarget Key, otherwise the update is not done (in my situation anyway).
 
NOTA BENE : It is obvious, but I specify it, that with another SMBIOS (T2), it will be necessary to change the values of :
ExtendedFirmwareFeatures & ExtendedFirmwareFeaturesMask
and of  :
HWTarget
 

That is very helpful and the most anyone has posted about this.
Until now I have had no idea what value to set for hwtarget. I still don’t know where to get the values from or why they are needed and are they only needed for update to show them remove them upon first reboot after update.
At least now I have the values I can tinker with a usb if the rc2 update doesn’t show.
I have no clue what a T2 is……Terminator 2?
I do have to add that just because something is clear to one person doesn’t mean it is clear to everyone.


Sent from my iPhone using Tapatalk

[Jief_Machak]

19 hours ago, MifJpnAlphaPlus said:

Thank you for fixing it so many times. @Jief_Machak
I'm sorry, but the results aren't looking good.
The following is the result.

Clover first says she wants me to use CCPV, but when I use CCPV, CCPV doesn't say anything.

 

 

 

 

I'm stumped.
Please help me.
If there is a fundamental mistake, please point it out. Please do.
Thank you very much.

config.plist.zip 6.07 kB · 2 downloads

Oups, was too quick to commit 23e4b83d...

Fixed (I think ).

[Gradou]

1 hour ago, SavageAUS said:

Until now I have had no idea what value to set for hwtarget.

I still don’t know where to get the values from 

With OpenCore 0.7.4 it can be checked by command : 

% sysctl hw.target

If you don't have OC 0.7.4, use OpenCoreConfigurator ---> Misc-->Security--->SecureBootModel : l : a drop-down menu and you see several values for T2 Mac (SMBIOS). I put the values ,corresponding to the SMBIOS to use, in upper case and added at the end : AP

 

Why they are needed and are they only needed for update to show them remove them upon first reboot after update.

personal experiments (a lot of time needed ... thank you !) after readings (including Slice 👏 Clover literature)

 

I have no clue what a T2 is……Terminator 2?

Computers with Apple T2 Security Chip
 

The following Mac computers have the Apple T2 Security chip : just after each model of mac T2, between the first parentheses, the HWTarget value which I think is the correct one (from experience), the second parentheses are for the values of ExtendedFirmwareFeatures & ExtendedFirmwareFeaturesMask (which are sometimes the same for different models of Mac)

 

MacBookPro 15,1 (J680AP) 15,2 (J132AP) 15,3 (J780AP) & 15,4 (J213AP) (0x8FD8FF426 & 0x8FF9FFF3F)

MacBookPro16,1 (J152FAP) 16,3 (J223AP) & 16,4 (J215AP) (0x8FDAFF066 & 0x8FFFFFF7F)

MacBookPro16,2 (J214KAP) (0x8FFAFF06E & 0x8FFFFFF7F) 

MacBookAir8,1 (J140KAP) & 8,2 (J140AAP) (0x8FD8FF42E & 0x8FF9FFF3F)

MacBookAir9,1 (J230KAP) (0x8FFAFF06E & 0x8FFFFFF7F)

Macmini8,1 (J174AP) (0x8FD8FF466 & 0x8FFDFFF7F)

iMac20,1 (J185AP) & 20,2 (J185FAP) (0x8FD8FF576 & 0x8FFDFFF7F) 

iMacPro1,1 (J137AP) (0x8FD8FF53E & 0x8FF9FFF3F)

MacPro7,1 (J160AP) (0x8FDAFF066 & 0x8FFFFFF7F) 

 

Of course all this requires to be experienced (and confirmed or denied) by anyone curious to test (at their own risk !!) This is a forum for exchange, isn't it?

 

Edited October 22, 2021 by Gradou

[SavageAUS]

Boot with ExtendedFirmwareFeatures & Mask and FirmwareFeatures & Mask = no update shown.
Boot with the above and HWTarget J215AP = Update shown but showing 12.0.1 again.


Sent from my iPhone using Tapatalk

[Gradou]

4 minutes ago, SavageAUS said:

Boot with ExtendedFirmwareFeatures & Mask and FirmwareFeatures & Mask = no update shown.
Boot with the above and HWTarget J215AP = Update shown but showing 12.0.1 again.


Sent from my iPhone using Tapatalk

It is the second RC Release 21A559 verify the number of your actual version of 12.0.1

[SavageAUS]

It is the second RC Release 21A559 verify the number of your actual version of 12.0.1

I am definitely on 12.0.1 and the update that is downloaded (12.0.1 again) will not install just loops with both clover and OpenCore.


Sent from my iPhone using Tapatalk

[Jief_Machak]

1 hour ago, MifJpnAlphaPlus said:

% ~/CloverBootloader/CloverPackage/CloverConfigPlistValidator/CloverConfigPlistValidator_r5141 /Volumes/EFI/EFI/CLOVER/config.plist
Your plist looks so wonderful. Well done!

The CCPV is saying it. Thank you very much.
　However, the problem is that Clover says warnings. I don't think this is a problem. And there it says, "Look at CCPV and LOG.”
　So, saying that CCPV is "good" doesn't follow the logic,I think.
　Is the "V2" in your modified commit referring to the way SMBIOS is written?
　On the other hand, if the CCPV parser is "not good" or "warning" or "don't know", wouldn't it be better to indicate that and give an answer suggesting to follow Clover's log?
　Sorry. I think we might be looking at this like "says nothing = no problem."
　I'm not in a hurry, so please consider this. Please do.

Thank you very much.

THere is one case where ccpv can't check, but Clover can. This is when ProductName is not defined. And it's true I didn't differentiate the messages. However, you seem NOT in that case.

So, send a picture of your screen when you see the messages, the preboot.log and your config.plist.

[Gradou]

44 minutes ago, SavageAUS said:

I am definitely on 12.0.1 and the update that is downloaded (12.0.1 again) will not install just loops with both clover and OpenCore.


Sent from my iPhone using Tapatalk

Can you be more descriptive of what is happening, version number of 12.0.1 possibly already installed ?
Which version of OpenCore? Misc -> SecureBootModel on Disablesd or Default ?

Under Clover 5141 do you remove the HWTarget Key before update... ?
Your information is really very brief ...
"All these broken poorly informed posts are getting beyond the joke."🤣

Edited October 22, 2021 by Gradou

[PG7]

4 hours ago, Jief_Machak said:

Oups, was too quick to commit 23e4b83d...

Fixed (I think ).

here it always worked correctly !

Spoiler

 

[SavageAUS]

51 minutes ago, Gradou said:

Can you be more descriptive of what is happening, version number of 12.0.1 possibly already installed ?
Which version of OpenCore? Misc -> SecureBootModel on Disablesd or Default ?

Under Clover 5141 do you remove the HWTarget Key before update... ?
Your information is really very brief ...
"All these broken poorly informed posts are getting beyond the joke."🤣

Please see the attached screenshot as evidence of being on 12.0.1 and being offered 12.0.1 as an update.

I have attached my config.plist for verification.

I am using Clover 5141 as shown.

The update being shown is the same as the version i am running therefor HWTarget is having null affect. But yes i have commented it out to try the update process to no avail.

I have also tried latest OC 0.7.5 dated 21/10/2021 which also shows only the 12.0.1 update as available not 12.0.2.

I use Clover as my daily boot loader. Only use OpenCore when Clover fails to get an update.

config.plist

[matxpa]

19 minutes ago, SavageAUS said:

Please see the attached screenshot as evidence of being on 12.0.1 and being offered 12.0.1 as an update.

I have attached my config.plist for verification.

I am using Clover 5141 as shown.

The update being shown is the same as the version i am running therefor HWTarget is having null affect. But yes i have commented it out to try the update process to no avail.

I have also tried latest OC 0.7.5 dated 21/10/2021 which also shows only the 12.0.1 update as available not 12.0.2.

I use Clover as my daily boot loader. Only use OpenCore when Clover fails to get an update.

config.plist 10.59 kB · 0 downloads

 

What's offered to you is Monterey RC2 12.0.1 (21A559) (21A558 is the RC1)

[SavageAUS]

 
What's offered to you is Monterey RC2 12.0.1 (21A559) (21A558 is the RC1)

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

[arcade33]

24 minutes ago, MifJpnAlphaPlus said:

Thank you for your kind interest.
I'm sure everyone will ask CCPV first. After that, they will figure out how to get the log.
　I'm sure they will have questions about what exactly to do when Clover say the value is "ignored". (In fact, the log says "use the same default value". I think this expression is very kind.
Because it is set automatically, thus they can think it's okay to comment it out. )
　If the CCPV can't do everything (warnings, etc.), then I think it's better to "give a suggestion to follow the log.
　Specifically, there are implementation aspects, so I can absolutely say that your idea is correct.
　Thank you very much for your time.

2021-10-22_12-21_CLOVERX64.efi.log.zip 22.07 kB · 0 downloads

config.plist.zip 6.07 kB · 1 download

try this one config.plist 2.zip