Clover General discussion

[Jief_Machak]

Thanks @Slice for the first bug. Dual log was very helpful.

Thanks @yapan4, I found something else.

 

How about this one : CloverX64-2021-10-01-11-18-28-83b9323-dirty-jief.zip ?

[Matgen84]

1 hour ago, Jief_Machak said:

Thanks @Slice for the first bug. Dual log was very helpful.

Thanks @yapan4, I found something else.

 

How about this one : CloverX64-2021-10-01-11-18-28-83b9323-dirty-jief.zip ?

 

@Jief_Machak This CloverX64 can boot Monterey.

 

There is something wrong with memory detection: 2132MHZ instead of 3000MHZ

 

Now

SmbiosTable.Type17->Vendor = Corsair
SmbiosTable.Type17->SerialNumber = 00000000
SmbiosTable.Type17->PartNumber = CMK16GX4M2B3000C15
SMBIOS Type 17 Index = 2 => 2 1:
BANK 0 DIMM1 2132MHz 8192MB(Ext:0MB)
Table index 3:!trustSMBIOS !gRAM.SMBIOS.doesSlotForIndexExist(SMBIOSIndex) 
SPD data in use:
SmbiosTable.Type17->Vendor = Corsair
SmbiosTable.Type17->SerialNumber = 00000000
SmbiosTable.Type17->PartNumber = CMK16GX4M2B3000C15
SMBIOS Type 17 Index = 3 => 3 3:
BANK 1 DIMM1 2132MHz 8192MB(Ext:0MB)
mTotalSystemMemory = 16384

Before r5140 (master, commit 83b93234b)

Type 16 Index = 0
0:102  0:000  Total Memory Slots Count = 4
0:102  0:000  Type 17 Index = 0
0:102  0:000  Ignoring insane frequency value 0MHz
0:102  0:000  Type 17 Index = 1
0:102  0:000  SmbiosTable.Type17->Speed = 3000MHz
0:102  0:000  SmbiosTable.Type17->Size = 8192MB
0:102  0:000  SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1
0:102  0:000  SmbiosTable.Type17->Vendor = 029E
0:102  0:000  SmbiosTable.Type17->SerialNumber = 00000000
0:102  0:000  SmbiosTable.Type17->PartNumber = CMK16GX4M2B3000C15
0:102  0:000  Type 17 Index = 2
0:102  0:000  Ignoring insane frequency value 0MHz
0:102  0:000  Type 17 Index = 3
0:102  0:000  SmbiosTable.Type17->Speed = 3000MHz
0:102  0:000  SmbiosTable.Type17->Size = 8192MB
0:102  0:000  SmbiosTable.Type17->Bank/Device = BANK 3 ChannelB-DIMM1
0:102  0:000  SmbiosTable.Type17->Vendor = 029E
0:102  0:000  SmbiosTable.Type17->SerialNumber = 00000000
0:102  0:000  SmbiosTable.Type17->PartNumber = CMK16GX4M2B3000C15
0:102  0:000  Boot status=0

 

2021-10-01_09-41_CloverX64-2021-10-01-83b9323-dirty-jief.efi.log

[yapan4]

Sorry, @Jief_Machak, i can test before- after- work only:-(

[SavageAUS]

I can no longer boot arch Linux with clover 5140.1. Booting from uefi boot picker works.
Was working with 5138 and 5139.


Sent from my iPhone using Tapatalk

[Slice]

7 hours ago, Jief_Machak said:

Thanks @Slice for the first bug. Dual log was very helpful.

Thanks @yapan4, I found something else.

 

How about this one : CloverX64-2021-10-01-11-18-28-83b9323-dirty-jief.zip ?

Successfully booted by the version.

There is non-significant memory difference with stock 5140

 

 

2133 is better then 2132 🤪

[yapan4]

...and my  two cents

yapan4_1001_2.zip

[Slice]

9 hours ago, maclinuxG4 said:

@jief: i propose that you reverse back before TMSC change,

 

and set a label, then continue to integration of OC

 

by the way, bad news 

 

i get this when i try to compile

CHECK XCODE]
- Building GCC 10.2.0 toolchain for x64
- to /Users/ericcoin/Desktop/CloverBootloader/toolchain/cross/bin/x86_64-clover-linux-gnu
  Running on Mac OS X 10.14, with x86_64 architecture.
  Using Xcode SDK: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk
Status: gmp-6.2.0 not found.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (60) SSL certificate problem: certificate has expired
More details here: https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure.

 

plz check.

 

I don't know what is your problem. Certificate for curl?

I downloaded this without a problem

sergey@iMac2017 src % curl -f -o download.tmp --remote-name https://ftp.gnu.org/gnu/gmp/${GMP_VERSION}.tar.xz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1965k  100 1965k    0     0  1362k      0  0:00:01  0:00:01 --:--:-- 1368k

 

[Matgen84]

@Jief_Machak

In my Z390 BIOS, XMP Profile is activated (2133MHZ---> 3000MHZ). Not in config.plist:

 

<key>XMPDetection</key>
<integer>-1</integer>

With r5140 (master, commit 83b93234b) from my local repo: Clover detects 3000MHZ (BIOS Information). CLOVERX64-2021-10-01-11-18-28-83b93234b-dirty-jief: displays only 2132MHZ as I said in my previous post.

 

@Jief_Machak

EDIT: in both case

 <key>Trust</key>
 <true/>

 

Edited October 1, 2021 by Matgen84

[Slice]

I made one more experiment: with stock Clover 5140.1 I set in config.plist SMBIOS->Trust=NO and got new System Information

[SavageAUS]

Are you all right, sir?
On 5140.1, Ubuntu shows the same as before.

You might want to check the debug logs for both versions.

The icon shows up just fine but trying to boot it gives a black screen. I’ll look into more later.
Have you booted Ubuntu? Or just looked at the icon?


Sent from my iPhone using Tapatalk

[SavageAUS]

I'm sorry.
I just checked the boot.
As you can see, Grub2.04 booted and Ubuntu20.04 ran as usual.
Is your Linux loader ok?
Or, preparing a bootable stub may work. (cp /boot/EFI/arch_grub/grubx64.efi /boot/EFI/boot/bootx64.efi)

My Arch Linux boots fine from EFI I’ll check my config when I get a chance but I swear nothing has changed.


Sent from my iPhone using Tapatalk

[Jief_Machak]

16 hours ago, Slice said:

Successfully booted by the version.

There is non-significant memory difference with stock 5140

 

 

2133 is better then 2132 🤪

There is manufacturer 0 instead of NoName.

Which Clover version is the first screen, and which is the second ?

[Jief_Machak]

17 hours ago, yapan4 said:

...and my  two cents

yapan4_1001_2.zip 34.14 kB · 0 downloads

Sorry, the last version I've sent contains debug code that overwrite memory modules info.

 

New version : CloverX64-2021-10-02-12-25-13-83b9323-dirty-jief.zip

 

20 hours ago, MifJpnAlphaPlus said:

Clock are same...

Thanks for testing. But are you saying it's ok for you ?

 

[PG7]

Il y a 59 minutes, Jief_Machak a dit :

Nouvelle version : CloverX64-2021-10-02-12-25-13-83b9323-sale-jief.zip

démarrage ok 

2021-10-02_10-10_BOOTX64.EFI-CloverX64-2021-10-02-12-25-13-83b9323-dirty-jief.efi.log
 

 

commettre/83593a5ab91c1a9485d1ce167ad13e035b75aeb2 2021-10-02_10-20_BOOTX64.EFI-commit: 83593a5ab91c1a9485d1ce167ad13e035b75aeb2.log

Edited October 2, 2021 by PG7

[yapan4]

yapan4_1002.zip

[SavageAUS]

I stand corrected, tonight Arch Linux decided to boot with no changes.

Will keep testing to see what went wrong.

[MacKonsti]

Hello everyone! @Slice I understand you are busy with fixes for Monterey mate, but I come back to you regarding the non-automatic selection with countdown of the drive when doing the security update to my Catalina with r5139.

Since you had mentioned that it was fixed, please check these logs when you have time:

• Updated to latest Catalina security update
• r5139 used with debug=true
• first boot selected "Data" partition OK with countdown
• second reboot selected "Data" partition OK without countdown
• third reboot selected normal partition OK with countdown.

Hope the logs will be helpful...

 

Also as I have a hard time to follow the developments for Monterey and the new requirements in settings, parameters and files for Clover r5140+ (not even sure I found what BLC is that is mentioned by @Jief_Machak ) please if a kind soul manages to install from scrath, kindly post a guide with a link of steps and parameters/files needed -- that would be appreciated !

r5139-Catalina-Update-Automatic-Select-Bug.zip

[SavageAUS]

BLC = Boot Loader Chooser.
Can choose to boot different version of clover or OpenCore etc.


Sent from my iPhone using Tapatalk

[Slice]

19 hours ago, Jief_Machak said:

There is manufacturer 0 instead of NoName.

Which Clover version is the first screen, and which is the second ?

Very simple question. 2132 is for your version, 2133 is for my version.

And the manufacture depends on Trust.

[Slice]

@Jief_Machak

             XBool b = true;
               if ( !super::validate(xmlLiteParser, xmlPath, keyPos, generateErrors) ) b = false;

Why not

             XBool b = super::validate(xmlLiteParser, xmlPath, keyPos, generateErrors);

Is it the same?

[Slice]

New commit 542b

0:161  0:000  === [ Get Smbios ] ==============================
0:161  0:000  Type 16 Index = 0
0:161  0:000  Total Memory Slots Count = 4
0:161  0:000  Type 17 Index = 0
0:161  0:000  Ignoring insane frequency value 0MHz
0:161  0:000  Type 17 Index = 1
0:161  0:000  SmbiosTable.Type17->SlotIndex = 1
0:161  0:000  SmbiosTable.Type17->ModuleSize = 4096MB
0:161  0:000  SmbiosTable.Type17->Type = 0MB
0:161  0:000  SmbiosTable.Type17->Frequency = 2133MHz
0:161  0:000  SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1
0:161  0:000  SmbiosTable.Type17->Vendor = 0000
0:161  0:000  SmbiosTable.Type17->SerialNo = 00000000
0:161  0:000  SmbiosTable.Type17->PartNo = 
0:161  0:000  Type 17 Index = 2

what is Type=0Mb?

[Jief_Machak]

2 hours ago, Slice said:

Very simple question. 2132 is for your version, 2133 is for my version.

This, I have no idea. It's not calculated, where does this number comes from ?

I improved the logs. Could you send me one ?

 

2 hours ago, Slice said:

And the manufacture depends on Trust.

For what I understood, if SMBIOS is trusted, the manufacturer comes from that, else it comes from what is detected. Is that right ? It yes, it could make sense that they are different, right ?

What do you have in your smbios.plist ?

Send me a log in that case.

 

1 hour ago, Slice said:

XBool b = super::validate(xmlLiteParser, xmlPath, keyPos, generateErrors);

Yes sure. Way more readable that way. I guess it comes from copy/paste before I used a bool.

12 minutes ago, Slice said:

New commit 542b

0:161  0:000  === [ Get Smbios ] ==============================
0:161  0:000  Type 16 Index = 0
0:161  0:000  Total Memory Slots Count = 4
0:161  0:000  Type 17 Index = 0
0:161  0:000  Ignoring insane frequency value 0MHz
0:161  0:000  Type 17 Index = 1
0:161  0:000  SmbiosTable.Type17->SlotIndex = 1
0:161  0:000  SmbiosTable.Type17->ModuleSize = 4096MB
0:161  0:000  SmbiosTable.Type17->Type = 0MB
0:161  0:000  SmbiosTable.Type17->Frequency = 2133MHz
0:161  0:000  SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1
0:161  0:000  SmbiosTable.Type17->Vendor = 0000
0:161  0:000  SmbiosTable.Type17->SerialNo = 00000000
0:161  0:000  SmbiosTable.Type17->PartNo = 
0:161  0:000  Type 17 Index = 2

what is Type=0Mb?

fixed.

[Jief_Machak]

2 hours ago, Jief_Machak said:

2 hours ago, Slice said:

New commit 542b

0:161  0:000  === [ Get Smbios ] ==============================
0:161  0:000  Type 16 Index = 0
0:161  0:000  Total Memory Slots Count = 4
0:161  0:000  Type 17 Index = 0
0:161  0:000  Ignoring insane frequency value 0MHz
0:161  0:000  Type 17 Index = 1
0:161  0:000  SmbiosTable.Type17->SlotIndex = 1
0:161  0:000  SmbiosTable.Type17->ModuleSize = 4096MB
0:161  0:000  SmbiosTable.Type17->Type = 0MB
0:161  0:000  SmbiosTable.Type17->Frequency = 2133MHz
0:161  0:000  SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1
0:161  0:000  SmbiosTable.Type17->Vendor = 0000
0:161  0:000  SmbiosTable.Type17->SerialNo = 00000000
0:161  0:000  SmbiosTable.Type17->PartNo = 
0:161  0:000  Type 17 Index = 2

what is Type=0Mb?

Expand  

fixed.

I mean, type is the constant for DDR DDR2, etc. MB was just some left over text.

[SavageAUS]

With all of these recent discussions I’m seeing and commits to clover is 5140.1 stable to use or does it have bugs? Without going back pages and pages I don’t see where it all started or what it all relates too. Is it just memory mhz people are having issues with or more?


Sent from my iPhone using Tapatalk

[Slice]

4 hours ago, Jief_Machak said:

This, I have no idea. It's not calculated, where does this number comes from ?

I improved the logs. Could you send me one ?

 

For what I understood, if SMBIOS is trusted, the manufacturer comes from that, else it comes from what is detected. Is that right ? It yes, it could make sense that they are different, right ?

What do you have in your smbios.plist ?

Send me a log in that case.

 

Yes sure. Way more readable that way. I guess it comes from copy/paste before I used a bool.

fixed.

I have no SMBIOS.plist. There is SMBIOS section in config.plist and almost all commented out.

 

config.plist.zip bootlog-6238.txt.zip

SMBIOS/DMI is always dynamic data created by BIOS or by the bootloader.

SMBIOS->Trust=true if we suppose BIOS makes good data. Trust=false if we read SPD and use it to fill SMBIOS data.