Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

Are you all right, sir?
On 5140.1, Ubuntu shows the same as before.
IMG20211002091039.jpg.16c4000e0f6149a9ed9d556d96842d48.jpg
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
Link to comment
Share on other sites

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)
IMG20211002125504.jpg.3ccc3d79eca32b55905416cb90be413c.jpg
IMG20211002125007.jpg.f38ec7451a1a4438f9151ca2c798c5f3.jpg

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
Link to comment
Share on other sites

16 hours ago, Slice said:

Successfully booted by the version.

There is non-significant memory difference with stock 5140

 

Screenshot 2021-10-01 at 19.00.38.png

Screenshot 2021-10-01 at 19.12.34.png

 

2133 is better then 2132 🤪

There is manufacturer 0 instead of NoName.

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

Link to comment
Share on other sites

17 hours ago, yapan4 said:

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 ?

 

  • Like 1
Link to comment
Share on other sites

CloverX64-2021-10-02-12-25-13-83b9323-dirty-jief_efi.png.4789b94294985e0be2f8fa1891ac0126.png437780830_commit83593a5ab91c1a9485d1ce167ad13e035b75aeb2.png.6c8b29a63860794cdb8303c99b7cd0dc.png

Il y a 59 minutes, Jief_Machak a dit :



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 by PG7
  • Like 1
Link to comment
Share on other sites

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:D:D ) 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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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?

  • Like 1
Link to comment
Share on other sites

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.

  • Like 3
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

  • Like 3
Link to comment
Share on other sites

 

2 hours ago, Slice said:

Nothing wrong in my case.

Ah ok. I though, when you said this following :

16 hours ago, Slice said:

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

And the manufacture depends on Trust.

that something is not right.

 

 

Link to comment
Share on other sites

3 hours ago, MifJpnAlphaPlus said:

Hmmm.
configure doesn't exist.
It is using autoreconf.
I can't solve it.🥲

I make the script to create gcc11.2.0 and successfully.

But I don't know how to download good ISL version.

Old site is down. Meinersbur provide sources without configure.

I downloaded from Ubuntu but I can make download from script. I placed isl-0.24 into Clover release 5140 but again I can't download it from script.

So the method is follow:

1. ./build_gcc11.sh

it failed because of no isl.

2. Download isl-0.24.tar.xz manually from Clover release 5140

3. place it into ~/src/tools/download/

4. ./build_gcc11.sh

Yes! It now will work.

 

But then I encounter next problem

[GENFW] CLOVERX64
Section 1 .text mCoffOffset=576(0x240) mCoffOffsetNew=576(0x240) diff=0(0x0), size=1306432
Section 7 .eh_frame mCoffOffset=1307008(0x13f180) mCoffOffsetNew=1545792(0x179640) diff=238784(0x3a4c0), size=0
Section 3 .data mCoffOffset=1545792(0x179640) mCoffOffsetNew=1307008(0x13f180) diff=-238784(0xfffc5b40), size=238704
Section 5 .ctors mCoffOffset=1545712(0x1795f0) mCoffOffsetNew=1545728(0x179600) diff=16(0x10), size=8
GenFw: ERROR 3000: Invalid
  /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/DEBUG/CLOVERX64.dll: Bad definition for symbol '__cxa_pure_virtual'@0 or unsupported symbol type.  For example, absolute and undefined symbols are not supported.
make: *** [/Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/OUTPUT/CLOVERX64.efi] Error 1

@Jief_Machak May be you know what is it.

  • Like 3
Link to comment
Share on other sites

×
×
  • Create New...