Jump to content

Clover General discussion


ErmaC
29,866 posts in this topic

Recommended Posts

ok I fix the problem Drivers for FileVault2.

I build my Package like this

⬇︎

Spoiler

90179652_Capturedcranle2018-09-1601_31_47.png.b3cbd64c974beaefac6a111054bb1e59.png

 

1478589605_Capturedcranle2018-09-1601_49_34.png.ea9b4056c703674b59747b411af77c50.png

395136580_Capturedcranle2018-09-1601_38_25.png.d4c453f5ec1bf56c57f208ab5c2e39ae.png

 

For my part I not using  FileVault2. Its look like this on my EFI Folder

nothing related to  FileVault2.

t1991320571_Capturedcranle2018-09-1601_46_03.png.2cb4e89683f61b3198ee8ef16c444815.png

 

  • Like 1
Link to comment
Share on other sites

On 9/11/2018 at 7:10 PM, Slice said:

The list of drivers usefull ONLY for FV2


AppleImageCodec-64.efi
AppleKeyAggregator-64.efi
AppleKeyFeeder.efi
AppleKeyMapAggregator.efi
AppleUISupport-64.efi
AppleUITheme-64.efi
FirmwareVolume-64.efi
HashServiceFix-64.efi
AptioInputFix-64.efi
AppleEvent.efi

 

 

thank you for clear.

i removed these files. and disappeared key delay in GUI.

  • Like 2
Link to comment
Share on other sites

ok I fix the problem Drivers for FileVault2.
I build my Package like this

Spoiler 90179652_Capturedcranle2018-09-1601_31_47.png.b3cbd64c974beaefac6a111054bb1e59.png
 
1478589605_Capturedcranle2018-09-1601_49_34.png.ea9b4056c703674b59747b411af77c50.png
395136580_Capturedcranle2018-09-1601_38_25.png.d4c453f5ec1bf56c57f208ab5c2e39ae.png
 
For my part I not using  FileVault2. Its look like this on my EFI Folder
nothing related to  FileVault2.
t1991320571_Capturedcranle2018-09-1601_46_03.png.2cb4e89683f61b3198ee8ef16c444815.png
 


Can you please post this in the build_clover.command thread so it can be added to the script hopefully.


Sent from my iPhone using Tapatalk
  • Like 3
Link to comment
Share on other sites

11 hours ago, SavageAUS said:

 


Can you please post this in the build_clover.command thread so it can be added to the script hopefully.


Sent from my iPhone using Tapatalk

 

Here attaching the origin buildpkg.sh

mod with two more choice 

line 1034 # build FileVault2UEFI packages

line 1061 # build FileVault2 packages

you need  this command before build packages

and your only made a script to move all drivers in place or doing this manually

NOTE; you have FileVault2 drivers in Drivers-Off and mandatory Drivers

mkdir -p ~/src/UDK2018/Clover/CloverPackage/CloverV2/drivers-Off/FileVault2UEFI

mkdir -p ~/src/UDK2018/Clover/CloverPackage/CloverV2/drivers-Off/FileVault2

maibe dev or coder doing the rest to make a script because I can not post here my script because my package is different of the one on SF

 

This is what its like finish

Spoiler

936099419_Capturedcran.png.825204372e5c0dccb4818672a0274f8e.png

189928552_Capturedcran1.png.ef40a27ec763dfe35d93fdcde2a99093.png

 

553503555_Capturedcranle2018-09-1615_29_09.png.9bdd1d8df0a501254c4626de9d0074c3.png

 

 

I confirm that without any FileVault Drivers the boot on APFS is much faster. The trim is activate in addition

buildpkg.sh.zip

Edited by chris1111
CORRECTION TYPO IN FILE
  • Like 1
Link to comment
Share on other sites

I confirm it after moving to macOS Mojave on my main SSD of my HP ProBook 6570B

The boot on an APFS SSD Trim enabler activate is much faster (twice as fast) :plane:
having no FileVault Drivers

Here are my UEFI drivers
Note I use the last drivers apfs.efi from Mojave 10.14 (18A389)

Clover compile in Mojave 10.14 (18A389)

UDK2018, Xcode Version 10.0 (10A254a)

784894778_Capturedcranle2018-09-1708_35_56.thumb.png.0aa343b8352fc60b79fc479b64d298da.png

Edited by chris1111
  • Like 3
Link to comment
Share on other sites

On 9/11/2018 at 12:10 PM, Slice said:

The list of drivers usefull ONLY for FV2


AppleImageCodec-64.efi
AppleKeyAggregator-64.efi
AppleKeyFeeder.efi
AppleKeyMapAggregator.efi
AppleUISupport-64.efi
AppleUITheme-64.efi
FirmwareVolume-64.efi
HashServiceFix-64.efi
AptioInputFix-64.efi
AppleEvent.efi

 

AptioInputFix-64.efi is good anyway. It fix a problem with my keyboard after sleep (first key pressed remains pressed), and I can awake the PC by just moving the mouse, no otherwise. This is a good driver in any cases.

IMHO all those drivers should remain where they are since the package already allow to deselect all them:

if I'm not mistaken they allow an unencrypted fusion corestoage volume to be loaded as well? If true they are just essential, and w/o them... is just a custom configuration...

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

8 hours ago, Allan said:

I see. You had notice that you have a better performance? Speed, etc...?

And thank you for your answer. :)

No difference performance and apfs.efi as no relation of the boot speed I think

for me its FilVault Drivers because without the boot speed is more fast

  • Like 1
Link to comment
Share on other sites

6 hours ago, Matgen84 said:

Hi

 

This morning, Xcode 10 is in regular software update on Appstore for High Sierra system :) Interesting for those who build Clover.

Just Upgrade to this version

1920563636_Capturedcranle2018-09-1808_12_58.png.ce72978443defcf77f164cdcd39bd364.png

  • Like 1
Link to comment
Share on other sites

I updated Xcode to 10. Clover compiled without problem.

Apple LLVM version 10.0.0 (clang-1000.11.45.2)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

 

  • Like 3
Link to comment
Share on other sites

  • 2 weeks later...
3 hours ago, Dr. Hurt said:

Could the Clover installer possibly be updated to work with with SIP enabled?

 

I get installation failed error when SIP is engaged.

I don't know exactly but I may propose that the Clover installer should be signed with Apple's trusted developer. The license costs money.

  • Like 3
Link to comment
Share on other sites

17 hours ago, Slice said:

I don't know exactly but I may propose that the Clover installer should be signed with Apple's trusted developer. The license costs money.

Even with a trusted code-signed certificate SIP wont allow to install things in System's directories, so is it useless anyway.

  • Like 4
Link to comment
Share on other sites

6 minutes ago, D-an-W said:

Is there an APFS.efi that will work with both Mojave and Sierra that has the debug info at boot removed maybe?

Yes you can use the same APFS.efi or APFSDriverLoader.efi for both macOS High Sierra and Mojave.

Link to comment
Share on other sites

10 minutes ago, Cyberdevs said:

Yes you can use the same APFS.efi or APFSDriverLoader.efi for both macOS High Sierra and Mojave.

 

Hi, its just Sierra (Never bothered with High Sierra, new baby in the house when it was released!) and is there one with the debug info removed?

Link to comment
Share on other sites

3 minutes ago, D-an-W said:

Hi, its just Sierra (Never bothered with High Sierra, new baby in the house when it was released!) and is there one with the debug info removed?

Congrats on the baby :)

Try these and let me know

apfs.efi is the patched version of the original Mojave's apfs and the Archive contains the ApfsDriverLoader-64.efi and AppleImageLoader-64.efi

apfs.efi.zip

Archive.zip

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

1 minute ago, D-an-W said:

Thanks, will try now.

 

Is ApfsDriverLoader-64.efi just a direct replacement for APFS.efi or do I need both files from Archive.zip in there?

 

My current Drivers64UEFI Folder Content:

868776254_ScreenShot2018-09-30at16_26_59.png.01db1b4b0f9cdc1551d9f8fe1ab2a91e.png

 

You're welcome, you only need to use only one of these drivers so either remove the apfs.efi and use (ApfsDriverLoader-64.efi and AppleImageLoader-64.efi) instead or only use apfs.efi

  • Thanks 1
Link to comment
Share on other sites

×
×
  • Create New...