Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

MifJpnAlphaPlus
MifJpnAlphaPlus
Posted
Posted
2 hours ago, Slice said:

@LAbyOne

I tested gcc12 and came to conclusions:

1. Thanks for new warnings and errors. They must be eliminated. The error with UsbBus has origin from MdeModulePkg which is still wrong. Let OpenCore use it ahead.

2. Clover compiled by gcc12 is not working. Crash at "construct_globals_objects(gImageHandle);". Attention to @Jief_Machak. I am not able to correct this.

So I switch back to gcc11.

Same here

SMBIOSPlist.h: line 674

      g.takeValueFromBE(SmUUID.value());

Thank you so much @Slice

Everything has been fixed.

Spoiler

1973420201_2022-05-0723_59_07.thumb.png.64fe9634368b9012a91d2a955fd164fc.png1973420201_2022-05-0723_59_07.thumb.png.64fe9634368b9012a91d2a955fd164fc.png

Spoiler

475081239_2022-05-080_03_58.thumb.png.3dc79d40cacb0ea78abdbbae701e1e48.png

 

  • Like 2
Guest 5T33Z0
Guest 5T33Z0
Posted
Posted (edited)

This might be interesting: Since my "new" used GPU arrived, I did run some tests in Geekbench and compared Clover vs OpenCore since I got configured identical (as far as this is possible). And in direct comparison, Clover always came out on top. Results here

Edited by 5T33Z0
Slice
Slice
Posted
Posted
30 minutes ago, 5T33Z0 said:

This might be interesting: Since my "new" used GPU arrived, I did run some tests in Geekbench and compared Clover vs OpenCore since I got configured identical (as far as this is possible). And in direct comparison, Clover always came out on top. Results here

It may be different bus speed calculations.

  • Like 2
Slice
Slice
Posted
Posted
6 hours ago, 5T33Z0 said:

@Slice You are right. I entered sysctl hw.busfrequency in Terminal. For Clover it returned 100 mHz and in OpenCore it returned 400 mHz.

The correct value should not be round. It must be like 99.973MHz. It provides maximum CPU speed because small deviations causes hangs.

  • Like 1
rafale77
rafale77
Posted
Posted
On 5/7/2022 at 7:45 PM, 5T33Z0 said:

This might be interesting: Since my "new" used GPU arrived, I did run some tests in Geekbench and compared Clover vs OpenCore since I got configured identical (as far as this is possible). And in direct comparison, Clover always came out on top. Results here

 

Looking at your results and based on my experience with GB5, and maybe it is just my setup, the differences you are seeing are far within the standard deviation of the test and therefore not statistically significant. I wouldn’t conclude that there is any difference at all except maybe on some of the extremes of the Metal test. Have you run multiple consecutive tests? For example GB5 single core on my 10900 ranges from 1280-1400. Multi-Core typically from 9450-9600. I have less experience on the compute test and it seems a little more stable but around the 21K mark I see variations of up to +/-~500 points under the exact same conditions so I would think in the 50K that +/-1200pts would be within noise.

  • Like 4
Guest 5T33Z0
Guest 5T33Z0
Posted
Posted (edited)

 @rafale77 In my short experice with the compute tests, I noticed that results deviate more than results from the CPU tests. But everytime I switched to Clover and repeated a test, the result was better. I also did some rendering in Davinci Resolve and when using Clover it was a bit faster – 33 seconds instead of 35. I have to see if I can find some type of bigger test project to render a larger file.

 

@Hervé Are you talking about me or who is the OP you are referring to?

Edited by 5T33Z0
Common_Sense
Common_Sense
Posted
Posted (edited)

I might have seen a bug in Clover, it behaves a bit strange with the partitions that I can select in the boot menu.

 

I cloned an SSD using Super Duper. As expected I got 2 macOS and 2 Recovery partitions in the boot menu.

 

I now go into Windows and re-partition the old SSD to an NTFS drive.

 

In the boot menu, I still have 2 macOS and 2 Recovery partitions.

 

How can it be?

Edited by Common_Sense
justApple
justApple
Posted
Posted
On 4/11/2022 at 12:17 AM, chris1111 said:

Guys the HP Probook Elitebook Clover is ready Big Sur and Monterey, its a great peace of software 👌

Thanks to @Slice for developing and maintaining Clover on TOP ! :wink_anim:

  Reveal hidden contents

155245353-8fd23843-912f-4288-9623-e067f733a918.png.4d2f4da73f277cb76e9d56f7607482b7.png

 

thanks good work

 

does this work with hp g1 gx probook elitebooks like the the rehabman guide?

 

 

Slice
Slice
Posted
Posted
54 minutes ago, justApple said:

 

ok thanks

 

the info on github and websites doesnt say probook or elitebook g1/g2/gx etc like in rehabmans guide for probook elitebook zbook etc.

May be you can tell me what is g2 elitebook etc.? I never saw it.

Common_Sense
Common_Sense
Posted
Posted
On 5/10/2022 at 3:09 PM, 5T33Z0 said:

@Common_Sense I doubt that this is a Clover issue. Can I see a screenshot of windows diskmanagent for the drive, please? Also check your config.plist and see if it has custom entries in the GUI section and delete those.

 

Indeed not a Clover issue, something weird with the partitions inside the APFS container after disk cloning with SuperDuper. I re-installed macOS and used data migration instead of cloning the drive, and it looks normal now.

LAbyOne
LAbyOne
Posted
Posted

@Slice

Sorry for not replying sooner to your message, i just did not notice,

Thanks for the fix on usbdxe driver

tested again GCC 12

only noticeable thing is this warning  during compil 

[SLINK] CLOVERX64
[DLINK] CLOVERX64
lto-wrapper: warning: using serial compilation of 26 LTRANS jobs
lto-wrapper: note: see the '-flto' option documentation for more information
[OBJCOPY] CLOVERX64
[GENFW] CLOVERX64

but Clover now build just fine.

Last thing to be addressed for Release version is ccpv, still fails. I  guess @Jief_Machak should take a look when he has time.

 

tell me if you want me to push changes for buildme and buildgcc

  • Like 2
Slice
Slice
Posted
Posted
14 hours ago, LAbyOne said:

@Slice

Sorry for not replying sooner to your message, i just did not notice,

Thanks for the fix on usbdxe driver

tested again GCC 12

only noticeable thing is this warning  during compil 

[SLINK] CLOVERX64
[DLINK] CLOVERX64
lto-wrapper: warning: using serial compilation of 26 LTRANS jobs
lto-wrapper: note: see the '-flto' option documentation for more information
[OBJCOPY] CLOVERX64
[GENFW] CLOVERX64

but Clover now build just fine.

Last thing to be addressed for Release version is ccpv, still fails. I  guess @Jief_Machak should take a look when he has time.

 

tell me if you want me to push changes for buildme and buildgcc

But I see no you resolved problems with gcc12. Are you sure the Clover will work when compiled by gcc12?

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