Bootloader Clover problems report & features request

[savvas]

1 minute ago, camillionario said:

Download the folder that says savvas and copy it in src / edk2 /. Before you have to rename it to Efipkg.
It worked for me in this way.

I fixed this problem, no need to do this steps

[Matgen84]

7 minutes ago, savvas said:

I fixed this problem, no need to do this steps

 

Thanks a lot. All works fine again with macbuild.tool and Dids Build script 

Edited September 27, 2018 by Matgen84

[LockDown]

6 hours ago, Matgen84 said:

 

Thanks a lot. All works fine again with macbuild.tool and Dids Build script 

@Matgen84

Hi. Can you please share your script to build clover. Thanks

Edited September 27, 2018 by ellaosx

[illdev]

Hi,

 

tried 4674 pkg installer from sourceforge yesterday, it installed well and seems to have worked.

However it reported back to be 4658 in the bottom right corner.

Never ever had this happen before.

Haven't seen somebody else report this, so there you go.

 

Rolled back to 4658 (which runs flawlessly so far). It's probably only irrelevant cosmetics, but eh… 

[simmel]

Mojave installer refuses installation and wants a firmware update on MacPro5,1 SMBIOS. I'm using Clover revision 4674 with bios version MP51.88Z.F000.B00.1807300628 and with bios release date 07/30/18. Boot-ROM-Version is reported as MP51.F000.B00. Workaround (found here, german posting): If I manually change boot ROM version to 138.0.0.0.0 in clover boot options, then I'm able to install Mojave. Boot-ROM-Version then is reported correctly as 138.0.0.0.0, like on real Macs.

[chris1111]

Commits 4687 I don't think SMCHelper-64.efi is a FileVault Drivers ??

 

➣ Slice said here

➣ SMCHelper

Edited October 1, 2018 by chris1111

[LockDown]

6 hours ago, chris1111 said:

Commits 4687 I don't think SMCHelper-64.efi is a FileVault Drivers ??

 

➣ Slice said here

I think its FV2 property. According to vit9696's post.

Edited October 1, 2018 by ellaosx

[chris1111]

17 minutes ago, ellaosx said:

I think its FV2 property. According to vit9696's post.

I see

SMCHelper.efi (for FakeSMC).

[LockDown]

@chris1111

To my understanding if using FV, use VirtualSmc.efi on VirtualSMC.kext or SMCHelper.efi on FakeSMC.

Remove both if not using FV.

 

Correct me if im wrong

 

Update: I saw you have updated your post. It seems you're correct that SMCHelper/VirtualSmc is NOT part of FV.

Edited October 1, 2018 by ellaosx
post updated

[LockDown]

AptioInputFix is part of FV?

[Matgen84]

3 hours ago, ellaosx said:

@chris1111

To my understanding if using FV, use VirtualSmc.efi on VirtualSMC.kext or SMCHelper.efi on FakeSMC.

Remove both if not using FV.

 

Correct me if im wrong

 

Update: I saw you have updated your post. It seems you're correct that SMCHelper/VirtualSmc is NOT part of FV.

 

In Virtualsmc FAQ: "VirtualSMC.efi module is recommended for boot.efi compatibility when FileVault 2 is enabled. SMCHelper-64.efi is not compatible with VirtualSMC.efi and must be removed."  FAQ   SMCHelper efi driver is not a replacement for FakeSMC.kext, it is a helper for it. Slice

 

For AptioInpuFix, "Reference driver to shim AMI APTIO proprietary mouse & keyboard protocols for File Vault 2 GUI input support" Read.md In my case, I don't use FV2 but this kext efi is the only way to have mouse for Clover GUI 'Asus Z77 mobo). 

 

If I Understand well, for no FV2 users: in EFI/Kexts/XX

 

• FakeSMC + SMCHelper.efi (this efi in EFI/Drivers64UEFI)
• or VirtualSMC

Edited October 1, 2018 by Matgen84

[LockDown]

50 minutes ago, Matgen84 said:

I don't use FV2 but this kext is the only way to have mouse for Clover GUI 'Asus Z77 mobo). 

you mean efi instead of kext.

 

"I don't use FV2 but this efi is the only way to have mouse for Clover GUI"

Edited October 1, 2018 by ellaosx

[Matgen84]

1 minute ago, ellaosx said:

you mean efi instead of kext.

 

"I don't use FV2 but this efi is the only way to have mouse for Clover GUI 'Asus Z77 mobo). "

 

That's right, sorry

[chris1111]

8 hours ago, ellaosx said:

@chris1111

To my understanding if using FV, use VirtualSmc.efi on VirtualSMC.kext or SMCHelper.efi on FakeSMC.

Remove both if not using FV.

 

Correct me if im wrong

 

Update: I saw you have updated your post. It seems you're correct that SMCHelper/VirtualSmc is NOT part of FV.

Not sure because now the mistake is correct to r4690 SMCHelper is back to Mandatory 

[WinstonAce]

Well, calling it "Mandatory" is obviously wrong.

[chris1111]

3 minutes ago, WinstonAce said:

Well, calling it "Mandatory" is obviously wrong.

Since the introduce this drivers is mandatory 

[WinstonAce]

Your system will work fine without it, so it's not mandatory.

Sent from my SM-G960F using Tapatalk

[LockDown]

AptioInputFix is alternative of XhciDxe?

Edited October 1, 2018 by ellaosx

[camillionario]

49 minutes ago, chris1111 said:

Dado que la introducción de este controlador es obligatoria 

I start with the laptop and the tower without SMC helper.efi without problems, so I do not think it is mandatory.

[Badruzeus]

@vector sigma Thanks for your commit anyway.. as you've said it works only with Xcode 5 #ATM so.. it seems I get some localizations issue after building r4692 using Xcode 8 (missing FileVault for Legacy && UEFI driver menus).

Edited October 1, 2018 by Badruzeus

[vector sigma]

1 hour ago, Badruzeus said:

as you've said it works only with Xcode 5

I've asked vit9696 to implement a fix.. waiting for an answere

1 hour ago, Badruzeus said:

(missing FileVault for Legacy && UEFI driver menus).

Is not missing, just it takes the wrong translation. Need to take a better look on how Poedit works... since I've installed it only yestarday and I used it once.... but I'll do that tomorrow, now here is really late.

[Matgen84]

16 hours ago, camillionario said:

I start with the laptop and the tower without SMC helper.efi without problems, so I do not think it is mandatory.

 

Here some explanation from Slice about SMCHelper.efi. Take a look if you want: Click Here

[Badruzeus]

Thanks for ur commit @Sherlocks (and @vector sigma too), FileVault2 title/description are now shown properly on r4695 Clover package.

[gujiangjiang]

@Slice

I have found a problem between EDID injection and DevicesProperties injection.

 

If Devices-Properties was empty and the EDID can inject without problem.

 

If there's contents in Devices-Properties, the EDID injection will fail, but according to boot.log generated by Clover, the injection succeeded.

 

I've tested this 3 times and it seems that these two functions conflict with each other.

 

Thanks.

 

Edited October 3, 2018 by gujiangjiang

[Dids]

Due to various 3rd party package changes (EfiPkg's development branch got renamed to develop, EfiMiscPkg got removed and OcSupportPkg is now required instead) Clover's build script (ebuild.sh) --ext-co build flag no longer works.

 

Here's a quick diff/patch for fixing it (tested and confirmed on latest revision):

--- Clover/ebuild.sh
+++ Clover/ebuild.sh
@@ -799,8 +799,8 @@
     # add github links below to checkout packages
     local extDriversDependecies=( 'https://github.com/acidanthera/AptioFixPkg'
                                   'https://github.com/acidanthera/AppleSupportPkg'
+                                  'https://github.com/acidanthera/OcSupportPkg'
                                   'https://github.com/CupertinoNet/CupertinoModulePkg'
-                                  'https://github.com/CupertinoNet/EfiMiscPkg'
                                   'https://github.com/CupertinoNet/EfiPkg')
     # add below drivers you want to build
     local externalDrivers=( AptioFixPkg AppleSupportPkg )
@@ -824,7 +824,7 @@
         local branch=master
 
         case $pkg in
-        CupertinoModulePkg | EfiMiscPkg | EfiPkg)
+        CupertinoModulePkg)
           branch=development
         ;;
         esac

 

Edited October 9, 2018 by Dids
Updated diff and comment about EfiMiscPkg being removed.