Clover General discussion

[Sherlocks]

32 minutes ago, Matgen84 said:

 

I understand well your point of vue: left click like macOS Build number for example. It would be a way to hide them.

 

Stupid question: How to get BIOS-ID and BOARD-ID on Hackintosh or real mac under macOS?

 

i didnot mention left click hide info.

just remove Apple ROM info. just like real mac.

realmac which has T2 chip, also there is no Apple ROM info in Hardware review in system profiler. clover added cosmetic info in hardware review part in system profiler.

 

[Slice]

No, Clover doesn't change System Profiler. The application remains native.

[Sherlocks]

22 minutes ago, Slice said:

No, Clover doesn't change System Profiler. The application remains native.

 

how can we back it like a real mac?

[LockDown]

Hi again

Starting from r5099, im getting stuck on error DMMP.

Do i need to rename this like the DSM to XDSM?

I never had this error. It only appeared after the commit in FixBiosDsdt.c.

Computer in question is my Desktop Legacy

[MICKHAEL]

5 hours ago, Sherlocks said:

 

how can we back it like a real mac?

well, if dev don't want, you could only hex patch clover binary file)

[Sherlocks]

3 minutes ago, MICKHAEL said:

well, if dev don't want, you could only hex patch clover binary file)

 

just add disable option if user dont want and keep vanilla.

[pkdesign]

On 12/9/2019 at 6:02 AM, Matgen84 said:

 

Just type OcQuirks on GitHub, you find this new memoryfix driver for Clover.

Doesn't work for me. I still have to use the "free" version.

[Riley Freeman]

8 hours ago, Sherlocks said:

just add disable option if user dont want and keep vanilla.

 

I'd second that. I know it's only cosmetic but it still bugs me which is why I've stuck with the last Clover revision before the change was made.

[n.d.k]

On 12/10/2019 at 7:56 AM, Sherlocks said:

 

just add disable option if user dont want and keep vanilla.

Or just comment out the PatchTableType11(); in rEFIt_UEFI/Platform/smbios.c

 

https://github.com/n-d-k/CloverBootloader/commit/4bbfece4b8ed9d05cab0fecc9284e2bf0bdb6467

[MICKHAEL]

23 minutes ago, n.d.k said:

Or just comment out the PatchTableType11(); in rEFIt_UEFI/Platform/smbios.c

 

https://github.com/n-d-k/CloverBootloader/commit/4bbfece4b8ed9d05cab0fecc9284e2bf0bdb6467

Compile please)

[n.d.k]

13 minutes ago, MICKHAEL said:

Compile please)

Sorry, my forked repo are heavy customized, you have to do it yourself!

[Slice]

On 12/10/2019 at 4:56 PM, Sherlocks said:

 

just add disable option if user dont want and keep vanilla.

You may do it by yourself.

Introduce a key in config.plist and insert line

if (!NoRomInfo) PatchTableType11();

[Sherlocks]

6 hours ago, Slice said:

You may do it by yourself.

Introduce a key in config.plist and insert line

if (!NoRomInfo) PatchTableType11();

 

thanks slice. after check, i will commit it

 

EDIT1.

committed

yes we back hardware overview like real mac, if you want it, add NoRomInfo TRUE in smbios part in config.

Edited December 12, 2019 by Sherlocks

[artur_pt]

hello Slice 

 

Clover last commit

 

 

thanks

[D-an-W]

For option 2 do I have to provide HFSPlus myself?

 

buildme, Clover v2.5k r5100 (SHA: f3797c12)
TOOLCHAIN: GCC53 (override example: './buildme XCODE8')

 1) build Clover
 2) build Clover with HFSPlus
 3) make pkg
 4) make app
 5) make iso
 6) build all
 7) test build (no autogen, no boot files)
 8) status
 9) update Clover
10) update Clover (reset changes)
11) show diff
12) open drivers directory
13) clean BaseTools
14) quit
Please enter your choice: 

 

Edited December 13, 2019 by D-an-W

[vector sigma]

11 minutes ago, D-an-W said:

For option 2 do I have to provide HFSPlus myself?

Sure as it is owned by Apple. Goes in:

CloverBootloader/FileSystems/HFSPlus/X64/HFSPlus.efi

 

Edited December 13, 2019 by vector sigma

[D-an-W]

Ok thanks, is there only one version of the file?

[maleorderbride]

@Slice

Can you complete your implementation of this protocol? Thank you!

https://github.com/CloverHackyColor/CloverBootloader/blob/master/rEFIt_UEFI/Platform/Injectors.c#L350-L355

 

//obligatory protocol
	Status = gBS->InstallProtocolInterface (&gImageHandle,
	&gDevicePropertiesGuid,
	EFI_NATIVE_INTERFACE,
	&mDeviceProperties
	);

Edited December 13, 2019 by maleorderbride

[mhaeuser]

@maleorderbride Out of curiousity, what are you planning to use it for?

[maleorderbride]

5 hours ago, Download-Fritz said:

@maleorderbride Out of curiousity, what are you planning to use it for?

I am attempting to inject some thunderbolt AAPL,PathProperties via .efi, but am unable to do so in Clover. OpenCore supports it, but Clover does not yet.

 

Even removing this partial implementation in Clover would be an improvement since then I could use EfiDevicePathPropertyDatabase.efi to enable AAPL,PathProperties injection via .efi, which used to work in older versions of Clover before Clover partially enabled this feature.

Edited December 14, 2019 by maleorderbride

[Matgen84]

Hi @vector sigma

 

Sorry for my stupid question: I don't understand this line in  Builme

 

buildCloverHFSPlus() {
if [[ -f "${CLOVERROOT}"/FileSystems/HFSPlus/X64/HFSPlus.efi ]]; then
  echo "building Clover with HFSPlus"
  buildClover HFSPlus
else
  echo "${CLOVERROOT}/FileSystems/HFSPlus/X64/HFSPlus.efi: no such file!"
  sleep 3
  menu
fi
}

There is no HFSPlus.efi in CloverBootloader Repo, we've to add manually in this specific directory in local repo.

 

Actually, I use "custom build script" to that: add to Clover PKG  What is the good way to add HFSPlus.efi.

 

Please

[vector sigma]

12 minutes ago, Matgen84 said:

Hi @vector sigma

 

Sorry for my stupid question: I don't understand this line in  Builme

 

buildCloverHFSPlus() {
if [[ -f "${CLOVERROOT}"/FileSystems/HFSPlus/X64/HFSPlus.efi ]]; then
  echo "building Clover with HFSPlus"
  buildClover HFSPlus
else
  echo "${CLOVERROOT}/FileSystems/HFSPlus/X64/HFSPlus.efi: no such file!"
  sleep 3
  menu
fi
}

 

If ../FileSystems/HFSPlus/X64/HFSPlus.efi exists then build Clover EFI with embedded HFSPlus instead of VBoxHfs

Otherwise tell the user that doesn't have HFSPlus, sleep 3 seconds and reload the initial menu.

12 minutes ago, Matgen84 said:

There is no HFSPlus.efi in CloverBootloader Repo, we've to add manually in this specific directory in local repo.

Is what I wrote 4 posts above your in this page.

 

12 minutes ago, Matgen84 said:

Actually, I use "custom build script" to that: add to Clover PKG  What is the good way to add HFSPlus.efi.

I'm not sure your custom build script will embed HFSPlus inside boot6 or boot7 .

Edited December 14, 2019 by vector sigma

[vector sigma]

18 hours ago, D-an-W said:

Ok thanks, is there only one version of the file?

it is coming from the Apple firmware, so I cannot know if and when they are going to update it. But I'm 99% sure that Apple have no great interest in making changes to an old driver used for years ... considering now it uses apfs.

[Matgen84]

3 minutes ago, vector sigma said:

If ../FileSystems/HFSPlus/X64/HFSPlus.efi does notexist then build Clover EFI with embedded HFSPlus instead of VBoxHfs

Otherwise tell the user that doesn't have HFSPlus, sleep 3 seconds and reload the initial menu.

Is what I wrote 4 posts above your in this page.

 

I'm not sure your custom build script will embed HFSPlus inside boot6 or boot7 .

 

After a few days in the hospital, my mind is not clear. Sorry.

 

Right, my custom script don't embed HFSPlus inside boot 6 or boot7 for my UEFI system. If I understand well, option 2 is optional. Is it mandatory to embed VBoxHFS or HFPlus to Clover Boot  I want to use Clover Installer like before.

 

My english is very bad

[vector sigma]

18 minutes ago, Matgen84 said:

After a few days in the hospital, my mind is not clear. Sorry.

oh, Hope you're be well soon 

18 minutes ago, Matgen84 said:

Right, my custom script don't embed HFSPlus inside boot 6 or boot7 for my UEFI system. If I understand well, option 2 is optional. Is it mandatory to embed VBoxHFS or HFPlus to Clover Boot  I want to use Clover Installer like before.

Is it not mandatory to use this option. HFSPlus should be used only for UEFi boot as boot6/7 already has an HFS driver. I.e. there is no need to add it to drivers/BIOS. If you use both, Is not clear what driver will be used or anyway you are going to load both and I really don't know which one will win or if some conflicts are going to happen. 

buildme tells ebuild.sh to use HFSPlus for legacy boot and also add it to the FileSystem drivers for UEFI booting, skipping VboxHfs (so will show up in the pkg). More than one driver is embedded, but if no HFSPlus is provided, VboxHfs will be used anyway.

Edited December 14, 2019 by vector sigma
typos