Clover General discussion

[chris1111]

1 hour ago, iCanaro said:

 

it stores what I told you, it made me go crazy for over 1 month, if you remember I had also posted several screenshots.
Clover may be young for big sur, but he does very well, at least in my hacks, I also updated Z68/Z97/Z370/X570 to BS 11.3beta1 with Clover5129

See I just Formate the HS partition

Spoiler

 

And boot from Clover  then now Preboot is BS Icon  on my two BS SSD 

This is non sense 

 

EDIT****

I try Sierra 

 

 

 

Edited February 5, 2021 by chris1111
I try Sierra 

[LockDown]

On 1/31/2021 at 5:28 PM, ellaosx said:

I remember clover version 5115 used to auto detect model identifier even if i dont put smbios in config.plist. But later versions now defaults to MacPro3,1.

 

On 2/1/2021 at 9:15 PM, Andrey1970 said:

I confirm, auto detect it is broken.

 

Hi @Jief_Machak

One more issue. here or il create ticket?

 

Edited February 5, 2021 by ellaosx

[chris1111]

Sierra is installed updated it seem working good and booting correct with Big Sur

 

Spoiler

 

[Jief_Machak]

Yes, create the issue on GitHub.

Yes, I remember now that the issue is when HS in installed on HFS, which is not supported by Apple, I think... It's probably possible to create a workaround (like : do not use SystemVersion.plist from Preboot to get the version number) but does someone really need that ?

[iCanaro]

4 hours ago, Jief_Machak said:

Yes, create the issue on GitHub.

Yes, I remember now that the issue is when HS in installed on HFS, which is not supported by Apple, I think... It's probably possible to create a workaround (like : do not use SystemVersion.plist from Preboot to get the version number) but does someone really need that ?

apart from me, I think not many. 
Perhaps it would be useful to understand what reference OC has, since when high sierra modifies the systemversion.plist in the preboot of big sur, OC has no problems and starts it the same unlike Clover who identifies it as high sierra

[Jief_Machak]

Just now, iCanaro said:

Clover who identifies it as high sierra

I think the only problem here is that we need to identify the version before launching because of kext dir name.

OC doesn't need that, I think. OC use kernel build for conditional matching. Would be interesting to see if OC get the right kernel build when preboot is wrong (modified by HS). Most likely yes.

Then we could hard code something like : if systemversion.plist says HS, but kernel version says BS, correct BS version.

[Slice]

On 2/1/2021 at 4:15 PM, Andrey1970 said:

I confirm, auto detect it is broken.

 

On 2/2/2021 at 3:33 AM, Andrey1970 said:

I don't know when it is broken. Tables from old Clover work perfectly.
Generation not working tables, frequency doesn't change and is constant 800 MHz. (It even is less than minimum for i7-3610QM 1200 MHz. )
I think generation tables is broken for all CPU IvyBridge and older.

 

From old Clover Working tables.zip

From new Clover Not working tables.zip

Check commit e24ceaa47.

This is 5 years old bug. It was not noticed before if not used default settings.

[Andrey1970]

4 hours ago, Slice said:

 

Check commit e24ceaa47.

This is 5 years old bug. It was not noticed before if not used default settings.

Works.

[Slice]

@Jief_Machak

Entries ordering works good.

[iCanaro]

I compiled all today's commits, tried the various Clover on X570 and Z370, no problem detected 

[maclinuxG4]

plz all seems good as before. 5May be a weid case with OC and sounds, a bug.)

 

[iCanaro]

36 minutes ago, iCanaro said:

I compiled all today's commits, tried the various Clover on X570 and Z370, no problem detected 

single note, with last commit, does not detect Clover version
https://github.com/CloverHackyColor/CloverBootloader/commit/1a02f530db91fdfa6880295b6a8b3f096c29e7cc

 

this does not create log debugging

PS: opss sorry, I said a fesseria, log debugging is OK

Edited February 6, 2021 by iCanaro

[Slice]

Clover version is unknown

0:100  0:000  Now is 07.02.2021,  05:58:41 (GMT)
0:100  0:000  Starting unknown on American Megatrends EFI
0:100  0:000  Build id: unknown

 

[Jief_Machak]

Sorry I didn't see iCanaro's post, that's why I'm fixing it only now.

Yes, I cleaned one include too much !

Committed.

[Slice]

All is fine now.

[Matgen84]

@Slice @Jief_Machak

I can't build Clover latest commit. 

 

[DLINK] CLOVERX64
Undefined symbols for architecture x86_64:
  "___bzero", referenced from:
      REFIT_MENU_SCREEN::REFIT_MENU_SCREEN() in lto.o
      REFIT_MENU_SCREEN::REFIT_MENU_SCREEN(unsigned long long, XStringW, XStringW) in lto.o
      REFIT_MENU_SCREEN::REFIT_MENU_SCREEN(unsigned long long, XStringW, XStringW, REFIT_ABSTRACT_MENU_ENTRY*, REFIT_ABSTRACT_MENU_ENTRY*) in lto.o
      KEXT_PATCH::KEXT_PATCH() in lto.o
      __GLOBAL__sub_I_Settings.cpp in lto.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.dll] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/mathieu/src/Cloverbootloader/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

 

[Jief_Machak]

Hum ???!

Probably the compiler that automatically replaced a memset(p, 0, x) by bzero. But I compiled here before commit... What about GCC ?

[Matgen84]

35 minutes ago, Jief_Machak said:

Hum ???!

Probably the compiler that automatically replaced a memset(p, 0, x) by bzero. But I compiled here before commit... What about GCC ?

 

I can build latest commit with GCC, not with XCODE8 

[Jief_Machak]

Just now, Matgen84 said:

 

I can build latest commit with GCC, not with XCODE8 

Ok, yes, so it's clang optimization.

I had to change the setup of clang flags. The goal was not to change them for regular compilation. I'll compare with the previous version and see.

It still strange that I tried to compile with XCODE8. Pretty it worked before I committed...

[iCanaro]

all OK

[Slice]

6 hours ago, Jief_Machak said:

Ok, yes, so it's clang optimization.

I had to change the setup of clang flags. The goal was not to change them for regular compilation. I'll compare with the previous version and see.

It still strange that I tried to compile with XCODE8. Pretty it worked before I committed...

Because you compile DEBUG?

I comfirm the problem with XCODE8 compilation in REFIT_MENU_SCREEN::REFIT_MENU_SCREEN()

 

ScrollState{0,0,0,0,0,0,0,0,0,0,0},

?

[iCanaro]

i can't compile in anymore i do on all the hacks i've tried 

 

Spoiler

10) update Clover

11) show diff

12) open CloverV2/EFI/CLOVER directory

13) update Clover (reset changes)

14) clean BaseTools

15) quit

Please enter your choice: 7

[CHECK XCODE]

WORKSPACE: /Users/utente/CloverBootloader

EDK_TOOLS_PATH: /Users/utente/CloverBootloader/BaseTools

CONF_PATH: /Users/utente/CloverBootloader/Conf

Copying $EDK_TOOLS_PATH/Conf/build_rule.template

     to /Users/utente/CloverBootloader/Conf/build_rule.txt

Copying $EDK_TOOLS_PATH/Conf/tools_def.template

     to /Users/utente/CloverBootloader/Conf/tools_def.txt

Copying $EDK_TOOLS_PATH/Conf/target.template

     to /Users/utente/CloverBootloader/Conf/target.txt

[BUILD CLOVER]

TOOLCHAIN_DIR: /Users/utente/CloverBootloader/toolchain

NASM_PREFIX: /Users/utente/CloverBootloader/toolchain/bin/

NASM_VER: 2.15.05

Initializing workspace

recreate Conf folder

WORKSPACE: /Users/utente/CloverBootloader

EDK_TOOLS_PATH: /Users/utente/CloverBootloader/BaseTools

CONF_PATH: /Users/utente/CloverBootloader/Conf

Copying $EDK_TOOLS_PATH/Conf/build_rule.template

     to /Users/utente/CloverBootloader/Conf/build_rule.txt

Copying $EDK_TOOLS_PATH/Conf/tools_def.template

     to /Users/utente/CloverBootloader/Conf/tools_def.txt

Copying $EDK_TOOLS_PATH/Conf/target.template

     to /Users/utente/CloverBootloader/Conf/target.txt

 

Running edk2 build for CloverX64 using the command:

build  -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/utente/CloverBootloader/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -p Clover.dsc  -a X64 -b RELEASE -t GCC53 -n 13 

 

Build environment: Darwin-19.6.0-x86_64-i386-64bit

Build start time: 16:45:36, Feb.07 2021

 

WORKSPACE        = /Users/utente/CloverBootloader

EDK_TOOLS_PATH   = /Users/utente/CloverBootloader/BaseTools

CONF_PATH        = /Users/utente/CloverBootloader/Conf

 

 

Architecture(s)  = X64

 

Processing meta-data Build target     = RELEASE

.Toolchain        = GCC53

 

Active Platform          = /Users/utente/CloverBootloader/Clover.dsc

..

 

build.py...

/Users/utente/CloverBootloader/rEFIt_UEFI/refit.inf(-1): error 000E: File/directory not found in workspace

/Users/utente/CloverBootloader/rEFIt_UEFI/Platform/DataHub.cpp

 

 

- Failed -

Build end time: 16:45:39, Feb.07 2021

Build total time: 00:00:03

 

logout

Saving session...

...copying shared history...

...saving history...truncating history files...

...completed.

 

[Processo completato]

 

[Matgen84]

Hi @Slice @Jief_Machak

Like @iCanaro I can't build 

 

Spoiler

build  --conf=/Users/mathieu/src/Cloverbootloader/Conf -D USE_LOW_EBDA -p Clover.dsc  -a X64 -b RELEASE -t XCODE8 -n 9 

Build environment: Darwin-18.7.0-x86_64-i386-64bit
Build start time: 16:52:17, Feb.07 2021

WORKSPACE        = /Users/mathieu/src/Cloverbootloader
EDK_TOOLS_PATH   = /Users/mathieu/src/Cloverbootloader/BaseTools
CONF_PATH        = /Users/mathieu/src/Cloverbootloader/Conf

Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE8

Processing meta-data .
Active Platform          = /Users/mathieu/src/Cloverbootloader/Clover.dsc
...

build.py...
/Users/mathieu/src/Cloverbootloader/rEFIt_UEFI/refit.inf(-1): error 000E: File/directory not found in workspace
    /Users/mathieu/src/Cloverbootloader/rEFIt_UEFI/Platform/DataHub.cpp

 

[Slice]

Sorry I forget to commit the files. Done!

[Matgen84]

@Slice @Jief_Machak

 

 

Thanks for commit commit 05dd5ca.

 

As before in the day, I can't build with XCODE because  "___bzero" 

 

 

Spoiler

[SLINK] CLOVERX64
[DLINK] CLOVERX64
Undefined symbols for architecture x86_64:
  "___bzero", referenced from:
      REFIT_MENU_SCREEN::REFIT_MENU_SCREEN() in lto.o
      REFIT_MENU_SCREEN::REFIT_MENU_SCREEN(unsigned long long, XStringW, XStringW) in lto.o
      REFIT_MENU_SCREEN::REFIT_MENU_SCREEN(unsigned long long, XStringW, XStringW, REFIT_ABSTRACT_MENU_ENTRY*, REFIT_ABSTRACT_MENU_ENTRY*) in lto.o
      KEXT_PATCH::KEXT_PATCH() in lto.o
      __GLOBAL__sub_I_Settings.cpp in lto.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.dll] Error 1

build.py...
 : error 7000: Failed to execute command
    make tbuild [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]

build.py...
 : error F002: Failed to build module
    /Users/mathieu/src/Cloverbootloader/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]
 

 

Edited February 7, 2021 by Matgen84