Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

PG7
PG7
Posted
Posted
18 hours ago, Mr MagOO said:

Hello!

I tried clover 5140 and it does not boot.

Back to 5139 and it boots well.

Too old rig ?

◊         

boot OK r5140

HP DV6 2140ef
intel i5 M430
Geforce Nvidia GT320M

Monterey Beta

16 hours ago, Slice said:

New Clover requires new OpenRuntime but I am not sure about legacy mode.

Can you make debug.log?

Boot ok Legacy confirmed

 

Spoiler

1937680420_Capturedecran2021-09-29a14_03_43.thumb.png.1678349fce96d0c5f4645cd9b75c9279.png

 

2021-09-29_11-45_CLOVERX64.EFI.log preboot.log

  • Like 2
Jief_Machak
Jief_Machak
Posted
Posted
20 hours ago, Slice said:

@Jief_Machak

You changed something? 

0:279  0:000  Calibrated TSC Frequency = 0 = 0MHz

Somehow the system works.

Interesting side effect. Because the static objects are constructed, not before main() as in a normal C++ program, but when we call construct_globals_objects(), the assignment of gCPUStructure.TSCCalibr was resetted by the gCPUStructure ctor.

  • Like 2
Slice
Slice
Posted
Posted
3 hours ago, Jief_Machak said:

Interesting side effect. Because the static objects are constructed, not before main() as in a normal C++ program, but when we call construct_globals_objects(), the assignment of gCPUStructure.TSCCalibr was resetted by the gCPUStructure ctor.

Thanks for finding. Now fine 

0:265  0:000  Calibrated TSC Frequency = 2712383230 = 2712MHz

Replace 5140 release?

  • Like 1
Jief_Machak
Jief_Machak
Posted
Posted
4 hours ago, Slice said:

I have a new idea:

OpenRuntime loaded after GUI so we can make manually choose one of OpenRuntime/AptioFix drivers same way as kexts Enable/Disable.

No completely sure of what you mean, but I don't think we have a choice : with a specific OC version goes a specific OpenRuntime version. Giving the choice of loading on old OpenRuntime won't work.

But I might not have understood well the idea.

1 hour ago, antuneddu said:

I extracted it from the pkg yesterday ... if you want

 

 

OpenRuntime.efi.zip 4.1 kB · 0 downloads

Please, rename it to OpenRuntime-v12.efi. That way, the next time (for OpenRuntime v13) it'll be easier.

  • Like 3
SavageAUS
SavageAUS
Posted
Posted
Download CloverV2-5140.zip, extract
\CloverV2\EFI\CLOVER\drivers\off\UEFI\MemoryFix\Openruntime.efi

So if 5140 has the updated OpenRuntime then shouldn’t 5140-1 have the same OpenRuntime?
Or do we have to have the 5140 OpenRuntime?


Sent from my iPhone using Tapatalk
  • Like 1
Matgen84
Matgen84
Posted
Posted
1 hour ago, SavageAUS said:


So if 5140 has the updated OpenRuntime then shouldn’t 5140-1 have the same OpenRuntime?
Or do we have to have the 5140 OpenRuntime?


Sent from my iPhone using Tapatalk

 

Right, it's the same. With OC-Integration 0.7.3 (Openruntime-v12.efi)

  • Like 2
Slice
Slice
Posted
Posted
28 minutes ago, SavageAUS said:

Do the new ExtendedFirmwareFeatures and ExtendedFirmwareFeaturesMask values need to be changed? Or are the defaults set to use for all?


Sent from my iPhone using Tapatalk

I can't check every config so you can use default value and if not success then return to the question.

Changed compared to what? To 5139 - YES, to 5140 - NO.

Matgen84
Matgen84
Posted
Posted (edited)
1 hour ago, Jief_Machak said:

Could check, everyone, if you boot on this : CloverX64-2021-09-30-13-35-43-83b9323-dirty-jief.zip that the memory information (in system information) is the same as with 5140.1 ?

 

Thanks

 

Hi @Jief_Machak

BLC don't want this new CloverX64 :  

Press any text
* Hit any key to continue *

After, I shortened his name:
 

After Clover GUI >

 

EXITBS START ++++++++++++++++++ and underscore

2021-09-30_12-01_CloverX64-83b9323-dirty-jief.efi.log

Edited by Matgen84
  • Sad 1
Jief_Machak
Jief_Machak
Posted
Posted
Just now, Matgen84 said:

 

Hi @Jief_Machak

BLC don't want this new CloverX64 :  

Press any text
* Hit any key to continue *

After, I shortened his name:
 

After Clover GUI >

 

EXITBS START ++++++++++++++++++ and underscore

You might have a hard limit on efi file name ?

If it's the case, I'm thinking a way to go around this. We'll try soon, I'll PM you.

 

"EXITBS START ++++++++++++++++++ and underscore" : are you sure a FixUSBOwnership didn't came back to true ?

Matgen84
Matgen84
Posted
Posted (edited)
8 minutes ago, Jief_Machak said:

You might have a hard limit on efi file name ?

If it's the case, I'm thinking a way to go around this. We'll try soon, I'll PM you.

 

"EXITBS START ++++++++++++++++++ and underscore" : are you sure a FixUSBOwnership didn't came back to true ?

 

I'm very sure because I can boot successfully r5140 commit commit 83b9323 (build 29/09/2021 from my local repo).

2021-09-30_12-13_CLOVERX64-5140-83b9323.efi.log

Edited by Matgen84
Slice
Slice
Posted
Posted
6 hours ago, Jief_Machak said:

Could check, everyone, if you boot on this : CloverX64-2021-09-30-13-35-43-83b9323-dirty-jief.zip that the memory information (in system information) is the same as with 5140.1 ?

 

Thanks

No start. 

See memory information in debug-log

My Clover 

0:170  0:000  Starting Clover revision: 5138 (master, commit f7add0788) on American Megatrends EFI
0:170  0:000  Build id: 20210901193835-f7add07-dirty
0:170  0:000  Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -D LESS_DEBUG -t GCC53 | --cmd-len=50000 -D NO_GRUB_DRIVERS_EMBEDDED -D LESS_DEBUG --conf=/Users/sergey/src/CloverBootloader/Conf -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: 12]
0:170  0:000  SimpleTextEx Status=Success
0:170  0:000  === [ Get Smbios ] ==============================
0:170  0:000  Type 16 Index = 0
0:170  0:000  Total Memory Slots Count = 4
0:170  0:000  Type 17 Index = 0
0:170  0:000  Ignoring insane frequency value 0MHz
0:170  0:000  Type 17 Index = 1
0:170  0:000  SmbiosTable.Type17->Speed = 2133MHz
0:170  0:000  SmbiosTable.Type17->Size = 4096MB
0:170  0:000  SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1
0:170  0:000  SmbiosTable.Type17->Vendor = 0000
0:170  0:000  SmbiosTable.Type17->SerialNumber = 00000000
0:170  0:000  SmbiosTable.Type17->PartNumber = 
0:170  0:000  Type 17 Index = 2
0:170  0:000  Ignoring insane frequency value 0MHz
0:170  0:000  Type 17 Index = 3
0:170  0:000  SmbiosTable.Type17->Speed = 2133MHz
0:170  0:000  SmbiosTable.Type17->Size = 4096MB
0:170  0:000  SmbiosTable.Type17->Bank/Device = BANK 3 ChannelB-DIMM1
0:170  0:000  SmbiosTable.Type17->Vendor = 0000
0:170  0:000  SmbiosTable.Type17->SerialNumber = 00000000
0:170  0:000  SmbiosTable.Type17->PartNumber = 
0:170  0:000  Boot status=0
0:170  0:000  Running on: 'Z170X-UD5 TH' with board 'Z170X-UD5 TH-CF'
0:170  0:000  === [ GetCPUProperties ] ========================

Your version 

=== [ Starting Clover ] =========================
Now is 30.09.2021,  16:38:09 (GMT)
Starting Clover revision: 5140 (master, commit 83b93234b) on American Megatrends EFI
Build id: 2021-09-30-13-35-43-83b9323-dirty-jief
Build with: [jief]
SimpleTextEx Status=Success
=== [ Get Smbios ] ==============================
Type 16 Index = 0
Total Memory Slots Count = 4
SmbiosTable.Type17->Speed = 2133MHz
SmbiosTable.Type17->Size = 0MB
SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1
SmbiosTable.Type17->Vendor = 0000
SmbiosTable.Type17->SerialNumber = 00000000
SmbiosTable.Type17->PartNumber = 
SmbiosTable.Type17->Speed = 2133MHz
SmbiosTable.Type17->Size = 0MB
SmbiosTable.Type17->Bank/Device = BANK 3 ChannelB-DIMM1
SmbiosTable.Type17->Vendor = 0000
SmbiosTable.Type17->SerialNumber = 00000000
SmbiosTable.Type17->PartNumber = 
Boot status=0
Running on: 'Z170X-UD5 TH' with board 'Z170X-UD5 TH-CF'
=

All zeros.

Sherlocks
Sherlocks
Posted
Posted
Spoiler

337220704_Capturedecran2021-10-01a00_50_23.thumb.png.746dcd47db0dea3b9e8159714b3a61b9.png

 

your backlight level is max. did you install nvram script for legacy? seems latest clover broken stored emulated nvram. i tested it before.

before reboot, decrese low brightness then check backlight level after boot

Sent from my SM-N960N using Tapatalk


maclinuxG4
maclinuxG4
Posted
Posted

@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.

 

  • Sad 1
Jief_Machak
Jief_Machak
Posted
Posted
20 minutes ago, yapan4 said:

Do not boot too

yapan4_logs_1001.zip 30.17 kB · 0 downloads

Now the memory seems to be read well, but maybe there is a problem at patching.

I'm surprised that a problem in smbios memory prevent the boot. I didn't know that.

@yapan4 Could you send me a log of a successful boot with 5140.1 ?

  • Like 1
 Share
Go to topic listing
×
×
  • Create New...