Clover General discussion

[Guest 5T33Z0]

8 hours ago, Slice said:

The correct place is here

@Slice,

 

@WeBeRiO was refering to ProvideConsoleGopEnable, which is a quirk indeed. But since this quirk is not listed in the sample-config by default and does not show up unless you enable it once, I think the validator falsely reports it as "Unknown", because it wasn't in the list of quirks when the "blueprint" for validating the config was created, you know?

Edited May 1, 2021 by 5T33Z0

[SavageAUS]

I don't know but when I got this Gop error with validator I have deleted it at all from config.plist and it seems everything is OK . [mention=112217]Slice[/mention] is that key is necessary in all cases ? i mean (ProvideConsoleGop) 
I can boot without it ,
Skylake Desktop Rx 580 Big Sur 

My rig is AMD so there will be differences.
Maybe I made other changes that messed it up. First I need to fix the slow animations then I’ll work on my config.


Sent from my iPhone using Tapatalk

 
You are making it really harder on yourself than necessary by using a text editor. Use the linux version of this plist editor instead: https://github.com/ic005k/PlistEDPlus/releases

Thanks for the tip.


Sent from my iPhone using Tapatalk

[SavageAUS]

These are the current errors i get on my config

Warning: Expect a string of 4 chars for tag '/ACPI/DropTables[0]/Signature:27'.Warning: Expect a string of 4 chars for tag '/ACPI/DropTables[1]/Signature:31'.Warning: Expect a boolean, an int8 or a string starting with 'n' or '-' for '/Boot/XMPDetection:113'.Warning: Unknown key '/GUI/Custom/Entries[0]/Ignore:154'. Skipped.Warning: Unknown key '/GUI/Custom/Entries[1]/Ignore:174'. Skipped.Warning: Unknown key '/GUI/Custom/Entries[2]/Ignore:186'. Skipped.Warning: Unknown key '/GUI/Custom/Entries[3]/Ignore:204'. Skipped.Warning: Boolean value contained in a string. Please use  instead of yes for tag '/SystemParameters/InjectKexts:1342'Warning: Unknown key '/Quirks/ProvideConsoleGopEnable:1403'. Skipped.

 
I’ve gotten it down to just the ProvideConsoleGopEnable quirk and it’s still booting just fine on 5133

When and why was this quirk removed?
I see nothing in OpenCores changelog to reflect the removal of this quirk.

As soon as I update to 5134 even with this quirk in place after clover GUI I get black screen.

Anyone else on AMD updated to 5134?

[LockDown]

Hi

quick question...

RC script is only for UEFI, or can be in legacy too?

Edited May 2, 2021 by ellaosx

[Matgen84]

6 hours ago, SavageAUS said:

These are the current errors i get on my config


 

Warning: Expect a string of 4 chars for tag '/ACPI/DropTables[0]/Signature:27'.Warning: Expect a string of 4 chars for tag '/ACPI/DropTables[1]/Signature:31'.Warning: Expect a boolean, an int8 or a string starting with 'n' or '-' for '/Boot/XMPDetection:113'.Warning: Unknown key '/GUI/Custom/Entries[0]/Ignore:154'. Skipped.Warning: Unknown key '/GUI/Custom/Entries[1]/Ignore:174'. Skipped.Warning: Unknown key '/GUI/Custom/Entries[2]/Ignore:186'. Skipped.Warning: Unknown key '/GUI/Custom/Entries[3]/Ignore:204'. Skipped.Warning: Boolean value contained in a string. Please use  instead of yes for tag '/SystemParameters/InjectKexts:1342'Warning: Unknown key '/Quirks/ProvideConsoleGopEnable:1403'. Skipped.

 

 
I’ve gotten it down to just the ProvideConsoleGopEnable quirk and it’s still booting just fine on 5133

When and why was this quirk removed?
I see nothing in OpenCores changelog to reflect the removal of this quirk.

As soon as I update to 5134 even with this quirk in place after clover GUI I get black screen.

Anyone else on AMD updated to 5134?

 

Hi @SavageAUS

Since September 2020 (commit bd8d3140b), ProvideConsoleGopEnable was removed from Quirks section, renamed/replaced by ProvideConsoleGop put to true (boolean) in GUI section.

[maclinuxG4]

hello

 

on last version, with a config.plist valided,  i could select partition, but no boot

 

Edited May 2, 2021 by maclinuxG4
hide

[Cyberdevs]

Hi guys,

I successfully updated to Clover r5134.

 

I removed all the unused Quircks, moved the ProvideConsoleGop to the GUI section and fixed some errors in the config using CloverConfigPlistValidator so thanks a lot for all your hard work and support. 

 

Spoiler

 

[SavageAUS]

1 hour ago, Matgen84 said:

 
Hi [mention=1083558]SavageAUS[/mention]

Since September 2020 (commit bd8d3140b), ProvideConsoleGopEnable was removed from Quirks section, renamed/replaced by ProvideConsoleGop put to true (boolean) in GUI section.

Yeah I’ve tried that but still on 5134 I boot to black screen. I’ll take another look into it.

 

I've attached my current config that i am trying to get working with Clover r5134 but get a black screen.

config.plist

Edited May 2, 2021 by SavageAUS

[Guest 5T33Z0]

1 hour ago, Matgen84 said:

 

Hi @SavageAUS

Since September 2020 (commit bd8d3140b), ProvideConsoleGopEnable was removed from Quirks section, renamed/replaced by ProvideConsoleGop put to true (boolean) in GUI section.

 

Wow, I didn't know this was removed. So since September 2020, Clover Configurator wasn't updated to reflect the new feature set? That's scary! So back to plist editor for clover config, too.

[Allan]

15 hours ago, 5T33Z0 said:

 

Well,

open the config with a plist editor to edit the entries.

- AppleXcpmCfgLock is not a Quirk used by Clover. Delete it and enable "KernelPM" under Kernel and Kext Patches instead

- Move ProvideConsoleGop to GUI Section

- As for the GUI entries: I would delete those, save and open the config with Clover Configurator and select the options you need again which recreates the entries. Or compare your config with the sample-config to see if there are difference in formatting (classes, data types, etc.).

 

Thank you so much 

[Cyberdevs]

Hi guys,

I am recently experiencing BIOS reset (with OpenCore and Clover) which might be because of the mainboard itself but I wanted to make sure if there is something that I can check before jumping to any conclusions. I know that H97 and Z97 mainboards have an issue with the BIOS but the good thing is that I'm still able to access BIOS/UEFI so this might be because of something that I have over looked.

Do I need to use RC Scripts or is there something else that I need to do?

 

I'm having this issue with my Haswell rig (GA-H97-D3H)

Thanks in advance

 

bootlog.txt config.plist

[Guest 5T33Z0]

2 hours ago, Cyberdevs said:

Hi guys,

I am recently experiencing BIOS reset (with OpenCore and Clover) which might be because of the mainboard itself but I wanted to make sure if there is something that I can check before jumping to any conclusions. I know that H97 and Z97 mainboards have an issue with the BIOS but the good thing is that I'm still able to access BIOS/UEFI so this might be because of something that I have over looked.

Do I need to use RC Scripts or is there something else that I need to do?

 

I'm having this issue with my Haswell rig (GA-H97-D3H)

Thanks in advance

 

bootlog.txt 51.32 kB · 0 downloads config.plist 6.28 kB · 0 downloads

 

Maybe this helps? https://github.com/5T33Z0/OC-Little-Translated/tree/main/06. CMOS-related Fixes

[MacKonsti]

Hi everyone, thanks again to @Jief_Machak and @Slice and everyone else that I am not aware of the dev and release of 5134; I wish I could know more details on the release log and see what has improved !

However I have a question, please Jief regarding the default output of CloverConfigPlistValidator and why is there a mention of "dirty" in the official binary 5134 on the release page?

./CloverConfigPlistValidator
ConfigPlistValidator for 'Clover revision: 5134 (master, commit fb86ee152)'
Build id is '20210429211313-fb86ee1-5134-dirty'
Usage ConfigPlistValidator path_to_config.plist

I see this "dirty" reference in some CloverX64.efi builds kindly provided from time to time from people compiling them, but not sure why "dirty" would make it on the final Release? Unless I am missing some GitHub process...

Thanks again.

[iCanaro]

T-Ryzo OK 

 

[Allan]

Hey Clover guys! I have a doubt.

 

If there's an error in our config.plist that didn't pass thought CloverConfigPlistValidator tool, those error messages will always appears before Clover GUI? There's no way to skip/hide it?

 

Thanks

 

My config.plist is "wonderful" btw 

[iCanaro]

13 hours ago, SavageAUS said:

Yeah I’ve tried that but still on 5134 I boot to black screen. I’ll take another look into it.

 

I've attached my current config that i am trying to get working with Clover r5134 but get a black screen.

config.plist 33.03 kB · 3 downloads

 

test config-savage.plist

[SavageAUS]

 
test config-savage.plist

Thanks mate, I’ll give it a test tonight.


Sent from my iPhone using Tapatalk

[Cyberdevs]

6 hours ago, Allan said:

Hey Clover guys! I have a doubt.

 

If there's an error in our config.plist that didn't pass thought CloverConfigPlistValidator tool, those error messages will always appears before Clover GUI? There's no way to skip/hide it?

 

Thanks

 

My config.plist is "wonderful" btw 

Hi @Allan

The error will appear until you fix it. Send me your config in PM and I'll try to fix it. When the error is fixed your config will be even "More Wonderful" 

[phi777]

Just wanted to tell that v5134 works good for me! Thank you very much developers and testers!!

[Matgen84]

12 hours ago, MacKonsti said:

Hi everyone, thanks again to @Jief_Machak and @Slice and everyone else that I am not aware of the dev and release of 5134; I wish I could know more details on the release log and see what has improved !

However I have a question, please Jief regarding the default output of CloverConfigPlistValidator and why is there a mention of "dirty" in the official binary 5134 on the release page?

./CloverConfigPlistValidator
ConfigPlistValidator for 'Clover revision: 5134 (master, commit fb86ee152)'
Build id is '20210429211313-fb86ee1-5134-dirty'
Usage ConfigPlistValidator path_to_config.plist

I see this "dirty" reference in some CloverX64.efi builds kindly provided from time to time from people compiling them, but not sure why "dirty" would make it on the final Release? Unless I am missing some GitHub process...

Thanks again.

Hi @MacKonsti CloverConfigPlistValidator  is not a part of Clover Binaries (Releease r5134). The project is independent. The mention "dirty", maybe because it's a @Jief_Machak project Beta (ongoing development)  and he do not put it to Release in GitHub repo. 

[maclinuxG4]

troubleshoot ?

0:133  0:000  === [ GetEarlyUserSettings ]  no debug ? ?

 

 

0:106  0:000   - LAN: 1 Vendor=Intel

but at the end
27:474  0:023  Found internal video device 0 @3B1C
27:502  0:027  Skipping Method(_DSM) for 1002 card
27:525  0:022  patch Display #0 of Vendor=0x1002
27:547  0:022  patch LAN0 in DSDT

 

LAN 1 but inject LAN 0 !!!!!!

 

[Allan]

7 hours ago, Cyberdevs said:

Hi @Allan

The error will appear until you fix it. Send me your config in PM and I'll try to fix it. When the error is fixed your config will be even "More Wonderful" 

HI @Cyberdevs, how are you man?

 

Oh thank you so much, now I don't have such messages anymore. It was just a doubt, if the user don't want to fix these issues he/her can skip or disable the messages.

 

But thank you so much anyway 

[Cyberdevs]

@Allan

I'm doing fine thanks, I hope you're doing great as well.

You're welcome bro 

 

To be honest I don't know if we can disable these messages or how to disable them, I guess it's a part of the new Clover like OpenCore and it's a very useful addition to Clover IMHO, but maybe @Slice or @Jief_Machak can explain wether we can disable these messages or not.

[LAbyOne]

On 4/28/2021 at 11:06 PM, Jief_Machak said:

So you can now compile the validator yourself : just go to Xcode/CloverConfigPlistValidator and open the xcode project. Compile the scheme "CloverConfigPlistValidator_Release" and voila.

Is there someone up to integrate this in buildme and in the CloverPackage ?

@Slice and @Jief_Machak

there you go, works fine here, but i will just wait for this till will properly build under any Xcode.. otherwise can become "uncomfortable" for the build itself.

 

 

P.S.

Forgot to add,

- adding a Makefile inside the CloverConfigPlistValidator will make the build nicer ?

- I guess i forgot to mkdir when installing tool onto destination, sorry.

Edited May 6, 2021 by LAbyOne

[SavageAUS]

 
test config-savage.plist

Unfortunately still the same black screen with 5134.


Sent from my iPhone using Tapatalk