Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

deeveedee
deeveedee
Posted
Posted (edited)

This question is more to satisfy my curiosity than anything else (and because I think I might be doing it wrong): when I install OC ( just for testing :) ), I specify the following parms unique to my platform:

  • PlatformInfo > Generic > MLB
  • PlatformInfo > Generic > SystemProductName
  • PlatformInfo > Generic > SystemSerialNumber
  • PlatformInfo > Generic > SystemUUID

When I install CLOVER (I'm still on r5122 UEFI), I specify the following parms unique to my platform (there may be some I missed):

  • RtVariables > ROM
  • SMBIOS > BiosReleaseDate
  • SMBIOS > BiosVersion
  • SMBIOS > Board-ID
  • SMBIOS > BoardSerialNumber
  • SMBIOS > Family
  • SMBIOS > ProductName
  • SMBIOS > SerialNumber
  • SMBIOS > SmUUID
  • SystemParameters > CustomUUID

 

Am I specifying too many unique parms for CLOVER, or is there a reason that CLOVER requires so many more system-unique parms than OC?

Edited by tonyx86
  • Like 1
deeveedee
deeveedee
Posted
Posted (edited)
1 hour ago, ellaosx said:

@tonyx86

These will be filled up by clover on-the-fly based on your SMBIOS > ProductName 


SMBIOS > BiosReleaseDate
SMBIOS > BiosVersion
SMBIOS > Board-ID
SMBIOS > Family

 

 

Thank you @ellaosx (and thank you @Slice for your response, although I don't see it anymore).  Forgive what are remedial questions, but it's only upon closer inspection of my CLOVER vs. OC configs that I realize I've been doing things without understanding why I was doing them.

 

Correct me if I'm wrong, if I specify only the following in my CLOVER config.plist, these are sufficient to uniquely identify my rig and the rest will be completed "on-the-fly" by CLOVER:

  • RtVariables > MLB
  • SMBIOS > BoardSerialNumber
  • SMBIOS > SerialNumber
  • SMBIOS > SmUUID
  • SMBIOS > ProductName

If that's the case, then I should remove the following from my CLOVER config.plist - correct?

  • RtVariables > ROM
  • SMBIOS > BiosReleaseDate
  • SMBIOS > BiosVendor
  • SMBIOS > BiosVersion
  • SMBIOS > Board-ID
  • SMBIOS > BoardManufacturer
  • SMBIOS > BoardType
  • SMBIOS > BoardVersion
  • SMBIOS > ChassisAssetTag
  • SMBIOS > ChassisManufacturer
  • SMBIOS > ChassisType
  • SMBIOS > EfiVersion
  • SMBIOS > Family
  • SMBIOS > FirmwareFeatures
  • SMBIOS > FirmwareFeaturesMask
  • SMBIOS > LocationInChassis
  • SMBIOS > Manufacturer
  • SMBIOS > Mobile
  • SMBIOS > PlatformFeature
  • SMBIOS > Version
  • SystemParameters > CustomUUID

 

Also, in OC config.plist, I think that "PlatformInfo > Generic > MLB" is BoardSerialNumber.  Should they be the same in CLOVER config.plist and if so, is there a reason that CLOVER config.plist has both "RtVariables > MLB" and "SMBIOS > BoardSerialNumber?"  

Edited by tonyx86
LockDown
LockDown
Posted
Posted (edited)
51 minutes ago, tonyx86 said:

is there a reason that CLOVER config.plist has both "RtVariables > MLB" and "SMBIOS > BoardSerialNumber?"  

I dont specifically know the reason behind it, but from my test, i found the result of this...

 

A. If you fill up ONLY the BoardSerialNumber, then MLB will have the same entry as BoardSerialNumber.

B. If you fill up ONY the MLB, then BoardSerialNumber will be generated by clover. (Based on my test a year ago :D )

 

 

Edited by ellaosx
  • Like 2
  • Thanks 1
kushwavez
kushwavez
Posted
Posted

Could you guys help me about converting OpenCore rename patches to Clover?

 

I would like to convert this from OC:

Comment: TB3 RP09:_PS0 to RP09:XPS0

Find: 5F505330

Replace: 58505330

OemTableId: 52565037 52746433

TableLength: 7453

TableSignature: SSDT

 

But I don't really know how to do it in Clover.

Or just leave OemTableId, etc. then it'll find it by itself?

 

Slice
Slice
Posted
Posted
10 minutes ago, kushwavez said:

Could you guys help me about converting OpenCore rename patches to Clover?

 

I would like to convert this from OC:

Comment: TB3 RP09:_PS0 to RP09:XPS0

Find: 5F505330

Replace: 58505330

OemTableId: 52565037 52746433

TableLength: 7453

TableSignature: SSDT

 

But I don't really know how to do it in Clover.

Or just leave OemTableId, etc. then it'll find it by itself?

 

Very simple

Снимок экрана 2020-12-18 121900.png

Clover makes patches for all DSDT and SSDT tables, everywhere if the pattern true.

  • Like 1
  • Thanks 1
deeveedee
deeveedee
Posted
Posted

 

The OCD in me wants to be able to pare down my CLOVER config.plist to the minimally required RtVariables, SMBIOS and SystemParameters, but my attempts have only resulted in problems with iCloud/AppleID.  I'm trying to reconcile the values I specify in CLOVER's config.plist with the System Info reported by Hackintool, and I have found the following:

  • CLOVER's SMBIOS > SmUUID does not appear in Hackintool's System Info
  • CLOVER's SystemParameters > CustomUUID is reported by Hackintool as "System ID"
  • Hackintool reports a "Hardware UUID" value that isn't anywhere in my CLOVER config.plist
  • CLOVER's RtVariables > MLB is reported by Hackintool as "Board Serial Number" and I don't see CLOVER's SMBIOS > BoardSerialNumber in Hackintool

It looks like paring down a bloated CLOVER config.plist (with extraneous RtVariables, SMBIOS and SystemParameters) may not be trivial.

Slice
Slice
Posted
Posted
49 minutes ago, tonyx86 said:

 

The OCD in me wants to be able to pare down my CLOVER config.plist to the minimally required RtVariables, SMBIOS and SystemParameters, but my attempts have only resulted in problems with iCloud/AppleID.  I'm trying to reconcile the values I specify in CLOVER's config.plist with the System Info reported by Hackintool, and I have found the following:

  • CLOVER's SMBIOS > SmUUID does not appear in Hackintool's System Info
  • CLOVER's SystemParameters > CustomUUID is reported by Hackintool as "System ID"
  • Hackintool reports a "Hardware UUID" value that isn't anywhere in my CLOVER config.plist
  • CLOVER's RtVariables > MLB is reported by Hackintool as "Board Serial Number" and I don't see CLOVER's SMBIOS > BoardSerialNumber in Hackintool

It looks like paring down a bloated CLOVER config.plist (with extraneous RtVariables, SMBIOS and SystemParameters) may not be trivial.

This is a question to Hackintool which is not my affair.

  • Like 2
deeveedee
deeveedee
Posted
Posted
2 minutes ago, Slice said:

This is a question to Hackintool which is not my affair.

 

Ok.  What tool do you use to verify the "actual" system parms to compare to those specified in CLOVER config.plist?

deeveedee
deeveedee
Posted
Posted
32 minutes ago, Slice said:

What is "actual" system params?  You may open About This Mac.app

Will do. It takes me longer than most to grasp technical concepts, but I'll figure this out. Thanks for your help.

Slice
Slice
Posted
Posted
3 hours ago, tonyx86 said:

Will do. It takes me longer than most to grasp technical concepts, but I'll figure this out. Thanks for your help.

If you look into kernel sources 

https://opensource.apple.com/source/xnu/xnu-6153.141.1/iokit/Kernel/IOPlatformExpert.cpp.auto.html line:1373 and nexts

then you will find that kernel encodes system-id so UUID in About This Mac will differ from input.

There are two sources for UUID in Clover: SMBIOS or config.plist.

As well we can allow to encode the UUID or not.

What is the question?

  • Like 3
  • Thanks 1
deeveedee
deeveedee
Posted
Posted
28 minutes ago, Slice said:

... you will find that kernel encodes system-id so UUID in About This Mac will differ from input.

What is the question?

 

ah - that explains it.  Thank you.

Slice
Slice
Posted
Posted
4 hours ago, 1Ale1 said:

@Slice I'm trying to understand how "Generate C&P States" works on Clover. Is it possible to use a custom SSDT (maybe even after Clover has done its job) in order to be able to manually generate P&C states?

 

You may set Generate P & C states by Clover or you can set don't do this and use custom SSDT.

  • Like 1
deeveedee
deeveedee
Posted
Posted (edited)
21 hours ago, 1Ale1 said:

I'm trying to understand how "Generate C&P States" works on Clover. Is it possible to use a custom SSDT (maybe even after Clover has done its job) in order to be able to manually generate P&C states?

 

Someone else can chime in if you have overclocking experience... @1Ale1 - Is your signature an accurate description of your system (Motherboard: ASUS Z370 Prime-A II, CPU : Intel i7 9700k liquid cooled @5.1GHz)?  If so, I assume you want a custom SSDT because you are overclocking?  If that's the case, I'm not certain of this, but I think you might want to search for variants of ssdtPRGen.sh that have been modified for Coffee Lake.  I don't know if CLOVER's "automatic" C and P states are what you're looking for.

 

EDIT: I have read posts by others that simply enabling SSDT PluginType in CLOVER's config.plist (without a custom SSDT and without CLOVER's Generate C and P states) does correctly detect all overclocked Turbo modes.  You may find after experimentation that you don't need to do any more than enable PluginType.

Edited by tonyx86
  • Like 1
MacKonsti
MacKonsti
Posted
Posted

Hi everyone, Season Greetings!

Hi @Slice I have been talking to @tonyx86 about optimal Clover configurations and we have a question, please, as you know the code.

Do we need FSInject.efi anymore as a standard driver in latest r5xxx releases?

According to your post 8 years ago, the logic is still there but some systems boot Mojave and Catalina without FSInject. Is it because kernelcache changed somehow, in last macOS's?

Is now the functionality of FSInject.efi embedded in CLOVERX64.EFI binary?

Your insight would be much appreciated; perhaps it's only for older OS like Sierra or older?

Thank you!

1Ale1
1Ale1
Posted
Posted
10 hours ago, tonyx86 said:

EDIT: I have read posts by others that simply enabling SSDT PluginType in CLOVER's config.plist (without a custom SSDT and without CLOVER's Generate C and P states) does correctly detect all overclocked Turbo modes.  You may find after experimentation that you don't need to do any more than enable PluginType. 

Thanks to you and @Slicefor quick response, I have to update my signature since the 9700K is fine, with plugin-type=1 through ssdt...

 

My question was for another build, actually a very old legacy one with an i3 540, GT710 and H67 as a chipset (SMBIOS iMac11,2) everything works fine with the latest clover release, and actually I haven't tested what could happen without those 

 

So I wondered how those states got generated, and also ssdtprgen doesn't mention pre Sandy CPUs

 

Any ideas on how to generate or reverse engineer SSDT replacements (maybe from Clover's C&P generation results?) for this ancient but fully working i3 540 with 10.15.7 19H114?

 

I can provide logs, acpi, ioreg, bootlogs etc if required :D

deeveedee
deeveedee
Posted
Posted (edited)
3 hours ago, 1Ale1 said:

My question was for another build, actually a very old legacy one with an i3 540, GT710 and H67 as a chipset (SMBIOS iMac11,2) everything works fine with the latest clover release, and actually I haven't tested what could happen without those 

 

i3-540 is Clarkdale which is a Westmere derivative.  I have a socket 1156 (H55) system that works great through Catalina 10.15.7.  I achieve native CPU power management (no CLOVER Generate C/P states or custom SSDT necessary) simply by using LPCB IOName "3b09" and SMBIOS MacPro5,1.  Even though Catalina doesn't "officially" support MacPro5,1, I use boot-arg -no_compat_check and Catalina still natively implements the correct CPU and USB power management for the MacPro5,1.  I haven't upgraded to Big Sur, so I can't comment on performance beyond Catalina.  You should find that with properly patched LPCB._DSM (DSDT patching), your rig will still operate with "native" CPU power management through Catalina 10.15.7.

 

The DSDT patching of LPCB._DSM is similar to what I do here for my Dell Latitude E6410 (running Catalina 10.15.7).  My Socket 1156 solution is in another forum.  Google "TH55HD Catalina" to find it.

Edited by tonyx86
MacKonsti
MacKonsti
Posted
Posted (edited)
On 12/18/2020 at 3:38 AM, tonyx86 said:

Correct me if I'm wrong, if I specify only the following in my CLOVER config.plist, these are sufficient to uniquely identify my rig and the rest will be completed "on-the-fly" by CLOVER:

  • RtVariables > MLB
  • SMBIOS > BoardSerialNumber
  • SMBIOS > SerialNumber
  • SMBIOS > SmUUID
  • SMBIOS > ProductName

 

Hi @tonyx86 has this been confirmed to work with r5xxx release you are using, as the absolute minimum information required for SMBIOS (and by removing/commenting out the others you mention) eventually? Does Clover successfully fill-in the missing data? (the one you use, I mean, r5122 or r5123-1) Thanks... I wish all that extremely useful knowledge would go into some Wiki for everyone (including Google search) to find...

Edited by MacKonsti
MacKonsti
MacKonsti
Posted
Posted (edited)

Thanks @1Ale1 and @tonyx86 I think I may need the parameter <key>Trust</key> too (and set to TRUE) to be kept in my config.plist.

Please remind me, what is the Terminal command parameters for ioreg to see that all is injected OK? I see some blanks in IORegistryExplorer.app... like "platform-feature" etc.

 

UPDATE: I found this command, would it be enough to check SMBIOS data?

ioreg -d2 -c IOPlatformExpertDevice

 

Thanks

 

Edited by MacKonsti
 Share
Go to topic listing
×
×
  • Create New...