Clover General discussion

[LAbyOne]

Forgot to mention updated also

There you can download Release 1.3r5

[Slice]

2 hours ago, LAbyOne said:

@Slice

 

here's an actualized version of buildme if needed

buildme.7z 4.34 kB · 9 downloads

 

- Updated checkTools to build gcc version 11

- Updated a few tools to actual release version

- Added to Utilities BigSurmount srw 2 --> info

Commit please by yourself to take responsibility for it.

[Slice]

I implemented hw.target (like OC did)

sergey@iMac2017 CloverBootloader % sudo sysctl hw.target   
Password:
hw.target: j160
sergey@iMac2017 CloverBootloader %

It should help for future updates of Monterey for T2 Models.

But I don't know how to assign default value depending on MacModel @Jief_Machak

[Matgen84]

15 hours ago, Slice said:

I implemented hw.target (like OC did)

sergey@iMac2017 CloverBootloader % sudo sysctl hw.target   
Password:
hw.target: j160
sergey@iMac2017 CloverBootloader %

It should help for future updates of Monterey for T2 Models.

But I don't know how to assign default value depending on MacModel @Jief_Machak

 

Hi @Slice Thanks.

 

The commit ec1f8a6a4 introduce changes : CsrActiveConfig (0xA85) and new key 'Hw.target' for the config-sample.plist

 

Do you plan to put some explanations on sub-forum "clover changes explanations" for all users.  Please.

[MacKonsti]

Hello everyone, I'd like a kind soul to help me out please?

 

1. I installed Clover 5139 on Beelink L55 for my cousin with Catalina with success. But with Big Sur as you know, only Preboot volume must be selected to boot.

 

I now moved to Clover 5140.1 and want to keep using Clover but as my cousin is a noob, I'd like to ask how to rename the word "Preboot" so that it's automatically selected?

 

In the boot screen there is only "Big Sur Preboot" and "Big Sur Recovery" options. It's possible that it was mentioned some time ago in 1108 pages, but is there any option to rename the "Preboot" word?

 

What have you guys done? Are you all booting Big Sur from "Preboot" name volume?

 

Finally a quick other question: For the Intel Wireless kext (itlmw) the AirportItlwm kext seems to only work with OpenCore due to the SecureBootModel key (set to "Default").

 

Any idea how to make this kext work in Clover? Your help is appreciated, I will post your instructions on my Github repo, too, once I figure out the exact steps...

 

P.S. For security reasons, both my "BooterConfig" and "CsrActiveConfig" keys are at 0x00 for security reasons!

Thank you!

Edited October 9, 2021 by MacKonsti

[MacKonsti]

14 minutes ago, MifJpnAlphaPlus said:

On my laptop, AirportItlwm kext also works with Clover.

Thank you for posting your photo, I very much appreciate it. I totally forgot that the folder name is "11" and not "11.0". Now it works, cheers mate! Arigatō!

Moreover, are you also booting from "Preboot" icon in boot screen? Did you perform any successful change of the name? Just curious...

 

@Slice please perhaps consider in the ZIP package to include a "11" folder together with all the "10.xx" folders in kexts folder, so that we remember it has no number after "11" ? In the latest 5140.1 ZIP I still only see "10.1x" folders.... Спасибо!

Edited October 9, 2021 by MacKonsti

[Slice]

1 hour ago, MacKonsti said:

Hello everyone, I'd like a kind soul to help me out please?

 

1. I installed Clover 5139 on Beelink L55 for my cousin with Catalina with success. But with Big Sur as you know, only Preboot volume must be selected to boot.

 

I now moved to Clover 5140.1 and want to keep using Clover but as my cousin is a noob, I'd like to ask how to rename the word "Preboot" so that it's automatically selected?

 

In the boot screen there is only "Big Sur Preboot" and "Big Sur Recovery" options. It's possible that it was mentioned some time ago in 1108 pages, but is there any option to rename the "Preboot" word?

 

What have you guys done? Are you all booting Big Sur from "Preboot" name volume?

 

Finally a quick other question: For the Intel Wireless kext (itlmw) the AirportItlwm kext seems to only work with OpenCore due to the SecureBootModel key (set to "Default").

 

Any idea how to make this kext work in Clover? Your help is appreciated, I will post your instructions on my Github repo, too, once I figure out the exact steps...

 

P.S. For security reasons, both my "BooterConfig" and "CsrActiveConfig" keys are at 0x00 for security reasons!

Thank you!

All vice versa.

1. Catalina can be booted by "Catalina" or by "Cataline Preboot" entries. But BigSur no.

BigSur can be booted ONLY by Preboot. The same for OpenCore as you already knows.

 

2. AirportItlwm works with Clover better than with with OpenCore. Link

3. For hackintosh reason if csr=0 then some kexts will not work. itlwm, voodoohda and others.

4. Who say you set BooterConfig to zero? Nonsense.

[MacKonsti]

Thank you @Slice for replying

a) If you remember that Chrome fiasco 1-2 years ago that prevented booting the Mac for those that had changed "BooterConfig" and "CsrActiveConfig" ? Ever since, I put all these to 0x00 like real Mac.

Please, what values to you suggest while keeping security? Besides the known 0x28 and 0x67 values obviously.

 

b) Thank you for the reply on the "Preboot" loading icon. Yes, I am aware same on OpenCore they just seem to hide the name, for aesthetic reasons I guess.

So for people that are not experienced in Hackintosh, is there a way to create a custom entry to boot the same "Preboot" volume but under a different name? My last efforts to create Custom Entries were not successful...

 

c) I have edited my reply above, please for your next release, can you include a folder "11" and "12" alongside "10.1x" so that we remember there is no "11.0" etc. for kexts? In the EFI ZIP? Thanks!

 

(you did not put a link for AirportItlwm working better with Clover but I believe you Good night to everyone! )

[Guest 5T33Z0]

I created a repo for an english Clover documnetation, since the  pdf is russian only.

 

Enjoy.

 

https://github.com/5T33Z0/Clover-Crate

[Slice]

Hi @Jief_Machak,

The message 

ProductName is not defined, the whole SMBIOS dict is ignored at line 437.

should not ever appear, because we have automatic definition

    Model = GetDefaultModel();

...

  SetDMISettingsForModel(Model, &gSettings, &GlobalConfig);

....

  settingsData->Smbios.ProductName = ApplePlatformData[Model].productName;

....

      if ( !ProductName.isDefined() ) {

        return xmlLiteParser->addWarning(generateErrors, S8Printf("ProductName is not defined, the whole SMBIOS dict is ignored at line %d.", keyPos.getLine()));

      }

 

This moment I will comment out this warning but why?

[Slice]

1 hour ago, Slice said:

Hi @Jief_Machak,

The message 

ProductName is not defined, the whole SMBIOS dict is ignored at line 437.

should not ever appear, because we have automatic definition

    Model = GetDefaultModel();

...

  SetDMISettingsForModel(Model, &gSettings, &GlobalConfig);

....

  settingsData->Smbios.ProductName = ApplePlatformData[Model].productName;

....

      if ( !ProductName.isDefined() ) {

        return xmlLiteParser->addWarning(generateErrors, S8Printf("ProductName is not defined, the whole SMBIOS dict is ignored at line %d.", keyPos.getLine()));

      }

 

This moment I will comment out this warning but why?

Because ProductName validate is occurred before we make default calculations?

[SavageAUS]

Based on the above are FirmwareFeatures and ExtendedFirmwareFeatures the same? Meaning the same value?

I really wish this was clarified as to where the get the ExtendedFirwmwareFeatures and ExtendedFirmwareFeaturesMask values from.
If these are going to be integral moving forward with Monterey then why aren’t the details published? Too much guessing going on.


Sent from my iPhone using Tapatalk

[Matgen84]

19 minutes ago, MifJpnAlphaPlus said:

I'm sorry for making so many mistakes.
　Apparently, the relationship between the existing FirmwareFeatures and ExtendedFirmwareFeatures is a logical OR, which simply means that the existing values have been converted to 64-bit by adding an "8" to the head.
　Without it, you can update, but you can't do a full install. As you know, a full installation takes a long time, so it took us a long time to provide you with a minimalist guide.
Sorry and Thanks.

 

Thanks @MifJpnAlphaPlus I don't know about the method. Only thing I know, ExtendedFirmwareFeatures and ExtendedFirmwareFeaturesMask are solving update loop installation for Monterey since Beta 7 (or Beta 8, I don't remember) on my Z390 system.

[LAbyOne]

17 hours ago, 5T33Z0 said:

I created a repo for an english Clover documnetation, since the  pdf is russian only.

 

Enjoy.

 

https://github.com/5T33Z0/Clover-Crate

Hi @5T33Z0

nice work, an up to date versions are always welcome

Wandering if could be also useful to have it linked into buildme...

In the meantime, may i use your sources to implement Clover's Documentation section into CloverSuiteBuilder?

 

[Jief_Machak]

On 10/8/2021 at 11:02 PM, Slice said:

But I don't know how to assign default value depending on MacModel

Tell me more and I'll explain.

[Jief_Machak]

10 hours ago, Slice said:

Hi @Jief_Machak,

The message 

ProductName is not defined, the whole SMBIOS dict is ignored at line 437.

should not ever appear, because we have automatic definition

    Model = GetDefaultModel();

...

  SetDMISettingsForModel(Model, &gSettings, &GlobalConfig);

....

  settingsData->Smbios.ProductName = ApplePlatformData[Model].productName;

....

      if ( !ProductName.isDefined() ) {

        return xmlLiteParser->addWarning(generateErrors, S8Printf("ProductName is not defined, the whole SMBIOS dict is ignored at line %d.", keyPos.getLine()));

      }

 

This moment I will comment out this warning but why?

The check made by the config.plist xml reader cannot depend of the hardware. Otherwise, CloverConfigPlistValidator cannot work.

 

I consider that, if someone wants to override SMBIOS default value, the first thing to do is to define ProductName. I'm pretty sure most of configs already define that. Proof is that this warning is present since months and nobody complains about it. I think someone mentioned it and we said to define ProductName and that was it.

 

It's of course possible to not do any checks when ProductName is not defined and still accept other values, but it's introducing a complexity level for what ? Just 2 lines in config.plist. The "rule" : always define ProductName is simpler and easier to understand and remember.

 

I don't understand why you want to comment out instead of defining ProductName in config.plist/SMBIOS.

 

[Slice]

1 hour ago, Jief_Machak said:

Tell me more and I'll explain.

HWTarget can have a default value as ApplePlatformData[Model].smcPlatform.

But I don't know what is the place/moment to do this and how to access "Model".

1 hour ago, Jief_Machak said:

 

I don't understand why you want to comment out instead of defining ProductName in config.plist/SMBIOS.

 

Because some users can't choose right ProductName while Clover knows GetDefaultModel(). Else why the procedure exists?

[Guest 5T33Z0]

@Slice

I added the new HWTarget parameter to the config:

 

But Clover doesn't like it. I have r5140.1 is installed:

Warning: Unknown key '/RtVariables/HWTarget:715'. Skipped.

Did I do something wrong?

sysctl hw.target
sysctl: unknown oid 'hw.target'

 

Edited October 11, 2021 by 5T33Z0

[Jief_Machak]

2 hours ago, Slice said:

But I don't know what is the place/moment to do this and how to access "Model

All methods dget...() is a place to return a default value ( dget for default_get) if not defined in config.plist. But of course, ProductName has to be defined.

 

It’s not hard to know what’s the right ProductName, and it looks like all users we know already has it.

if a user don’t know it’s ProductName, will he really defined other SMBIOS value, which are harder to understand ?

 

 

[Slice]

But yes, other values also depends on ProductName. So if it is not defined then SMBIOS values will be unreal mixed.

Anyway it is accessible like we think out some unreal serial numbers and can replace one model to another don't touchings others values.

[SavageAUS]

Clover Change Explanations
https://r.tapatalk.com/shareLink/topic?share_fid=30100&share_tid=304530&share_pid=2768896&url=https%3A%2F%2Fwww%2Einsanelymac%2Ecom%2Findex%2Ephp%3F%2Ftopic%2F304530-Clover-Change-Explanations%2Fpage__view__findpost__p__2768896&share_type=t&link_source=app

How do we get these values??


Sent from my iPhone using Tapatalk

[Slice]

I think hw.target value should be low case.

[SavageAUS]

Can someone please ELI5 the new hw.target and ExtendedFirmwareFeatures and ExtendedFirmwareFeaturesMask.
What are they?
What do they do?
Where do we get the values?

I’m sorry but if these items have been implemented and are a must have moving forward then surely some reasonable documentation should exist for what they are, how to use them and how to get the required values.

If this is common knowledge and I’m just a dummy then tell me I’m a dummy, all I want is a simple explanation of what they are, what they do, where to get them and are they needed.

I have asked for this information a few times already with no luck.


Sent from my iPhone using Tapatalk

[Matgen84]

1 hour ago, MifJpnAlphaPlus said:

Hello.
I have built the latest commit. (Commit: dfbdc8ae45b2aad608bc93f64ebe8d58758a56fc)
My rig is an iMac 19,2, so it doesn't have a T2 chip. So I configured it as follows.

 

% ./CloverConfigPlistValidator_r5140 /Volumes/EFI/EFI/CLOVER/config.plist
Your plist looks so wonderful. Well done!

 

% sysctl hw.target                             
hw.target: X86LEGACYAP

I think it may be too slow to download it from a Japanese PC. If you can download it from below, you might be happy.

Clover_r5140-dfbdc8ae45b2aad608bc93f64ebe8d58758a56fc.pkg

CloverV2-5140-dfbdc8ae45b2aad608bc93f64ebe8d58758a56fc.zip

 

Thank you

 

Thanks @MifJpnAlphaPlus for you method.

@Slice Is HWTarget key mandatory for non T2 chip config ! I use Imac19,1 (Corei7 9770K Z390 config):  T2 chip doesn't exist on Intel machines.

[Matgen84]

1 hour ago, Slice said:

I think hw.target value should be low case.

 

47 minutes ago, MifJpnAlphaPlus said:

Hello

I tested it with lower case letters.

% sysctl hw.target
hw.target: x86legacyyap

Monterey was able to boot.

Thank you very much.

 

@MifJpnAlphaPlus @Slice

My Z390 (SMBIOS Imac19,1) config boot Monterey without 'hwtarget' key in config.plist. 
 

% sysctl hw.target
hw.target:
%

How do you find the value: 

x86legacyyap

As I say before: Imac19,1 SMBIOS do not have T2 chip. So maybe Hw.target key and value aren't necessary !

 

My next questions is this:

Will the fact that an iMac has a T2 chip affect using the SMBIOS for a hackintosh?