Jump to content

Clover General discussion


ErmaC
30,140 posts in this topic

Recommended Posts

I don't know when it was happened but I see a problem

new Clover

4:997  0:000  === [ GetMacAddress ] ===========================
4:997  0:000  === [ ScanSPD ] =================================

Old Clover rev 5130

2:441  0:000  === [ GetMacAddress ] ===========================
2:441  0:000   get legacy LAN MAC, 1 card found
2:441  0:000  Legacy MAC address of LAN #0= 1C:1B:0D:66:5B:71:
2:441  0:000  === [ ScanSPD ] =================================

Why?

Link to comment
Share on other sites

I made the bisection

iMac2017:CloverBootloader sergey$ git bisect good
4a3bc612b85e61a77b8f760099a090b7bf2e9636 is the first bad commit
commit 4a3bc612b85e61a77b8f760099a090b7bf2e9636
Author: jief666 <github.com@jfa.knudsen.ovh>
Date:   Fri Mar 26 12:43:15 2021 +0300

    Create settings section Graphics, RtVariables.
    Mobe Turbo in GlobalConfig.

:040000 040000 2e1ae25009c9ebd84fd157d31061127a3b8ac1a5 ed70fa0b6dd4245c53409c9c924858f19923054b M	Include
:040000 040000 e3ddb98143e78428b9c483bc441727c4a663b478 a239dd5a7cd310a7e9ff972cbd38d32379165c31 M	Library
:040000 040000 0088f3300ecf989d50a1944e619e71ab45a181cc 2a7849860861a9145e3fcee454ef1cf8f9d2e8c0 M	Xcode
:040000 040000 9e0a346019e22a79f3ce62fcaa1c2b28339f51c9 9688c3002e6763c4f115f6640b7798d09cf9c9ff M	rEFIt_UEFI
iMac2017:CloverBootloader sergey$ 

 

Link to comment
Share on other sites

16 hours ago, Jief_Machak said:

compare the debug.log when it’s working and not. Or send them to me.

@Jief_Machak here is the debug for not ok hevc and ok also ioreg not ok and ok

can you figure out what is the problem 

thanks

2021-4-2_10-8_CloverX64-RELEASE_GCC53-20210401110653-69a47c5.efi_nok_hevc.log 2021-4-2_10-29_CloverX64-RELEASE_GCC53-20210401110653-69a47c5.efi_ok_hevc.log ioreg_nok.txt ioreg_ok.txt

Link to comment
Share on other sites

3 hours ago, eng_redaesm said:

Unfortunately, I can't see anything different...

 

If you have reproduce this few times already, now you can use an old version, like 5130, and see if it does the same. If not, we know that it's because a commit in between. With dichotomy, we'll find it quite quick.

  • Like 1
Link to comment
Share on other sites

52 minutes ago, Jief_Machak said:

Another refactoring. This time mainly on Smbios. Anyone who could check that there is no regression is welcome.

Use dmidecode before and after trying the last commit. Any change is a problem I'll fix.

Thanks.

dmidecode 120.89 kB · 1 download


@Jief_Machak I build new commit, and try with dmiecode :) How to use this tool ?

Edited by Matgen84
  • Like 1
Link to comment
Share on other sites

39 minutes ago, Matgen84 said:


@Jief_Machak I build new commit, and try with dmiecode :) How to use this tool ?

just double click on it or eventually drag to terminal window and pipe to some editor if you want to keep the file.

i.e.

dmidecode > out.txt

 

your file will be in $HOME

 

or if you need somthing more specific its always a good idea to use --help

 

 

dmidecode --help

Usage: dmidecode [OPTIONS]

Options are:

 -i, --input-file       Decode DMI data from a binary file

 -d, --dev-mem FILE     Read memory from device FILE (default: I/O Registry)

 -h, --help             Display this help text and exit

 -q, --quiet            Less verbose output

 -s, --string KEYWORD   Only display the value of the given DMI string

 -t, --type TYPE        Only display the entries of given type

 -H, --handle HANDLE    Only display the entry of given handle

 -u, --dump             Do not decode the entries

     --dump-bin FILE    Dump the DMI data to a binary file

     --from-dump FILE   Read the DMI data from a binary file

     --no-sysfs         Do not attempt to read DMI data from sysfs files

     --oem-string N     Only display the value of the given OEM string

 -V, --version          Display the version and exit

Edited by LAbyOne
Link to comment
Share on other sites

11 minutes ago, LAbyOne said:

just double click on it or eventually drag to terminal window and pipe to some editor if you want to keep the file.

i.e.

dmidecode > out.txt

 

your file will be in $HOME

 

@Jief_Machak Last commit not booting (Z390 Big Sur 11.3 Beta 6)

 

 

2021-4-3_16-11_CLOVERX64-2021-04-03-17-48-6ff5bab.efi.log

Link to comment
Share on other sites

@Jief_Machak Unfortunately I have trouble with building (./buildme XCODE8)

[...]
Building ... /Users/kushwavez/git/CloverBootloader/Library/MemLogLibDefault/MemLogLibDefault.inf [X64]
Building ... /Users/kushwavez/git/CloverBootloader/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull.inf [X64]
[CC] MemLogLib
Building ... /Users/kushwavez/git/CloverBootloader/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf [X64]
Building ... /Users/kushwavez/git/CloverBootloader/MdePkg/Library/UefiLib/UefiLib.inf [X64]
[CC] BaseReportStatusCodeLib
[CC] DriverEntryPoint
Building ... /Users/kushwavez/git/CloverBootloader/MdePkg/Library/BasePciLibCf8/BasePciLibCf8.inf [X64]
[CC] Acpi
clang: error: argument unused during compilation: '-mabi=ms' [-Werror,-Wunused-command-line-argument]
clang: error: argument unused during compilation: '-mabi=ms' [-Werror,-Wunused-command-line-argument]
Building ... /Users/kushwavez/git/CloverBootloader/MdePkg/Library/BaseDebugPrintErrorLevelLib/BaseDebugPrintErrorLevelLib.inf [X64]
clang: error: argument unused during compilation: '-mabi=ms' [-Werror,-Wunused-command-line-argument]
make: *** [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull/OUTPUT/BaseReportStatusCodeLib.obj] Error 1
make: *** [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint/OUTPUT/DriverEntryPoint.obj] Error 1
[CC] PciLib
clang: error: argument unused during compilation: '-mabi=ms' [-Werror,-Wunused-command-line-argument]
make: *** [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/Library/MemLogLibDefault/MemLogLibDefault/OUTPUT/MemLogLib.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull]
make: *** [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiLib/UefiLib/OUTPUT/Acpi.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/Library/MemLogLibDefault/MemLogLibDefault]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiLib/UefiLib]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BasePciLibCf8/BasePciLibCf8]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/kushwavez/git/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseDebugPrintErrorLevelLib/BaseDebugPrintErrorLevelLib]


build.py...
 : error F002: Failed to build module
	/Users/kushwavez/git/CloverBootloader/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 18:18:27, Apr.03 2021
Build total time: 00:00:17

fresh clone

Mojave 10.14.6 (18G8022) - Xcode 11.3.1 (11C505)

Command line tools version: 10.3.0.0.1.1562985497

 

gcc --version:

Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1

Apple LLVM version 10.0.1 (clang-1001.0.46.4)

Target: x86_64-apple-darwin18.7.0

Thread model: posix

InstalledDir: /Library/Developer/CommandLineTools/usr/bin

 

EDIT: with ./buildme (not XCODE8) its building okay. Would be good to be able to build with XCODE8 tho

Edited by kushwavez
  • Sad 1
Link to comment
Share on other sites

@Jief_Machak I use F11 several time to boot Big Sur with last commit. Strange

I upload the two output files. There are some differences.

Note: BIOS Version, BIOS Release: I update them few week ago. I use custom SerialNumber, UUID (System Information).
 

Clover r5132 96909661a.txt Clover r5132 6ff5bab.txt

Edited by Matgen84
Link to comment
Share on other sites

14 minutes ago, Jief_Machak said:

Yes, these were a bit complicated BIOS Version, BIOS Release. Ok I'll have a look.

Do NOT modify your config.plist !!!

Ok. Take a look to Base Board Information. Please

Note: I check the config.plist (USB/HDD)
EDIT: >>>> I forgot to update SMBIOS section (USB). I  try another test :) Sorry.

Edited by Matgen84
Link to comment
Share on other sites

Boot OK - Mojave 10.14.6 - X1 Carbon 6th

 kushwavez  ~  Downloads  ./dmidecode > dmidecode_v5132_6ff5bab.txt
 kushwavez  ~  Downloads  diff dmidecode_v5132.txt dmidecode_v5132_6ff5bab.txt 
 kushwavez  ~  Downloads  

no differences

 

edit: have to mention that I have NoRomInfo=True therefore there is no visible diff between Clover versions because that isn't there. But I double checked & booted the latest commit with BootloaderChooser

Edited by kushwavez
  • Like 1
Link to comment
Share on other sites

@Jief_Machak  Boot OK (Z390 Big Sur 11.3 Beta 6)

 

iMac-de-Mathieu:~ mathieu$ diff /Users/mathieu/Desktop/Clover\ r5132\ 96909661a.txt /Users/mathieu/Desktop/New\ Clover\ r5132\ 6ff5bab.txt 
147c147
< 0010: 03 8C 19 00 10 0E F8 11 41 32 44 00 45 00 46 00
---
> 0010: 03 8C 19 00 11 0E F8 11 41 32 44 00 45 00 46 00
189c189
< 	Max Speed: 3600 MHz
---
> 	Max Speed: 3601 MHz
281c281
< 	String 1: Apple ROM Version..Board-ID : Mac-AA95B1DDAB278B95....  Powered by Clover revision: 5132 (master, commit 96909661a).
---
> 	String 1: Apple ROM Version..Board-ID : Mac-AA95B1DDAB278B95....  Powered by Clover revision: 5132 (master, commit 6ff5bab8a).

not really differences :D

New Clover r5132 6ff5bab.txt Clover r5132 96909661a.txt

Link to comment
Share on other sites

3 hours ago, Matgen84 said:

@Jief_Machak I use F11 several time to boot Big Sur with last commit. Strange

I upload the two output files. There are some differences.

Note: BIOS Version, BIOS Release: I update them few week ago. I use custom SerialNumber, UUID (System Information).
 

Clover r5132 96909661a.txt 25.2 kB · 1 download Clover r5132 6ff5bab.txt 25.19 kB · 1 download

I can see it's not injected.

Don't know why, it is here on my VM.

Could you try CloverX64-2021-04-03-23-31-49-6ff5bab-dirty-jief.zip. Check in your Base Board Information, Version must be 1.0 and not IMac19,1. Also, your serial number in "system information" was not right. If it's still the case, could you send me the debug.log and you config.plist and the dmidecode output, so I'll try to reproduce here.

2 hours ago, MifJpn said:

Crucial Technology

Shorten manufacturer name should be fixed as well.

4 hours ago, kushwavez said:

Mojave 10.14.6 (18G8022) - Xcode 11.3.1 (11C505)

Command line tools version: 10.3.0.0.1.1562985497

 

gcc --version:

Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1

Apple LLVM version 10.0.1 (clang-1001.0.46.4)

Target: x86_64-apple-darwin18.7.0

Thread model: posix

InstalledDir: /Library/Developer/CommandLineTools/usr/bin

Anyone having this version who can make a compile test ?

Link to comment
Share on other sites

×
×
  • Create New...