Clover General discussion

[iCanaro]

commit https://github.com/CloverHackyColor/CloverBootloader/commit/02235676488328f2ff6a01d81bbecf7da21f93bc

 

on the Z370 it all seems OK 2021-4-28_19-34_CLOVERX64-5133-022356764.efi.log

[Slice]

I also found no issue.

[Jief_Machak]

Thanks @iCanaro @Slice. I worked a lot on testing and anti-regression tests (remember the config.plist parsing mass testing?) to try to make it as little painful as it can be.

Since this mass testing, I thinks I worked full time on this ! So it's nice if my effort is not in vain.

Thanks.

[eng_redaesm]

@Jief_Machak  working good no issue complied with gcc  but  again the compiled commit with xcode blank screen 

[iCanaro]

@Jief_Machak which is the latest version of CloverConfigValidator??? I had stayed at 0.7

[Jief_Machak]

1 minute ago, eng_redaesm said:

working good no issue complied with gcc  but  again the compiled commit with xcode blank screen 

Oh yes we still have that thing.

I have to add ctor to all objects as there is a bug in Xcode. We'll see if that improves. If not I will need you help to find the problem. But I'm going away for a few days so that'll next week,

Just now, iCanaro said:

which is the latest version of CloverConfigValidator??? I had stayed at 0.7

It's 0.7 and not up to date. You'll get one tmo, promise 

[Jief_Machak]

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 ?

[tluck]

well I got a bunch of warnings and then nothing.

cant compile validator - hit a bug - something about <size_t> (__v) - can't cast unsigned long long to unsigned long...

Edited April 28, 2021 by tluck

[Jief_Machak]

6 hours ago, tluck said:

well I got a bunch of warnings and then nothing.

cant compile validator - hit a bug - something about <size_t> (__v) - can't cast unsigned long long to unsigned long...

Any compile log ? Screenshot ?

[yapan4]

Hey guys, please remind me the correct set of commands for clone from master. Thanks.

Edited April 29, 2021 by yapan4

[Matgen84]

10 hours ago, iCanaro said:

@Jief_Machak which is the latest version of CloverConfigValidator??? I had stayed at 0.7

 

10 hours ago, Jief_Machak said:

It's 0.7 and not up to date. You'll get one tmo, promise 

Hi @iCanaro @Jief_Machak

On https://github.com/jief666/CloverCommits there is CloverConfigValidator 0.8. So the next one, will be CloverConfigValidator 0.9 

Now, Build and test latest commit efb5e87. Thanks @Jief_Machak

[Jief_Machak]

1 minute ago, Matgen84 said:

there is CloverConfigValidator 0.8

Oups, forgot that one... Must have been very late when I made it 

[Matgen84]

18 minutes ago, yapan4 said:

Hey guys, please remind me the correct set of commands for git clone. Thanks.

 

git clone --recurse-submodules "https://github.com/CloverHackyColor/CloverBootloader.git" "DESTINATION_PATH" 

Of course, replace "DESTINATION_PATH" by your own location.

5 minutes ago, Jief_Machak said:

Oups, forgot that one... Must have been very late when I made it 

Hi @Jief_Machak Where we can find Xcode/CloverConfigPlistValidator ? It's a good idea  to integrate this tool in buildme and in the CloverPackage

[Slice]

50 minutes ago, yapan4 said:

Hey guys, please remind me the correct set of commands for clone from master. Thanks.

I do the follow

cd ~
mkdir src
cd src
git clone https://github.com/CloverHackyColor/CloverBootloader.git
cd CloverBootloader
git clone https://github.com/CloverHackyColor/OpenCorePkg.git
./buildme

 

[yapan4]

Compiled and  boot 11.4b1 successful

2021-4-29_7-37_BOOTX64.EFI.log

[Slice]

This is simpler with the same result

cd ~
mkdir src
cd src
git clone --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git
cd CloverBootloader
./buildme

 

[Jief_Machak]

11 hours ago, eng_redaesm said:

the compiled commit with xcode blank screen 

Could you try this : CLOVERX64.efi.zip ?

[Matgen84]

@Jief_Machak
 

I build commit  efb5e87 (Xcode 11.3.1 - Mojave - IvyBridge). I can successfully boot Big Sur 11.4 Beta 1 (Z390 config). 

[Jief_Machak]

You can also :

git submodule foreach --recursive git clean -d -f -f -x
git clean -d -f -f -x
git submodule foreach git checkout master
git checkout master
git reset --hard --recurse-submodules

this will restore the repo in the exact same state as if it were freshly cloned. Only difference is that it doesn't need to re-download.

Edited April 29, 2021 by Jief_Machak

[kushwavez]

@Jief_Machak with latest commits my X1C6 won't boot.

Compiled with GCC: Black screen after selecting Big Sur entry.

 

2021-4-29_8-4_CloverX64-RELEASE_GCC53-20210429000358-efb5e87.efi.log

[Jief_Machak]

3 minutes ago, kushwavez said:

@Jief_Machak with latest commits my X1C6 won't boot.

Compiled with GCC: Black screen after selecting Big Sur entry.

 

2021-4-29_8-4_CloverX64-RELEASE_GCC53-20210429000358-efb5e87.efi.log 32.38 kB · 0 downloads

Could you send me your config.plist and a log of a successful boot ?

[eng_redaesm]

6 minutes ago, kushwavez said:

@Jief_Machak with latest commits my X1C6 won't boot.

Compiled with GCC: Black screen after selecting Big Sur entry.

 

2021-4-29_8-4_CloverX64-RELEASE_GCC53-20210429000358-efb5e87.efi.log 32.38 kB · 1 download

seems to work good but i have these messages on screen 

 

[naiclub]

[Jief_Machak]

1 hour ago, eng_redaesm said:

seems to work good but i have these messages on screen 

 

Yes, it's a way for me to know where it crashes when it crashes before being able to save the log.

 

Unfortunately, my compilation works, but not yours.

So, edit the file main.cpp, line 2685. Change

//#define DEBUG_ERALY_CRASH

by

#define DEBUG_ERALY_CRASH

compile and try.

[eng_redaesm]

1 minute ago, Jief_Machak said:

Yes, it's a way for me to know where it crashes when it crashes before being able to save the log.

 

Unfortunately, my compilation works, but not yours.

So, edit the file main.cpp, line 2685. Change

//#define DEBUG_ERALY_CRASH

by

#define DEBUG_ERALY_CRASH

compile and try.

i will try and inform you