Clover General discussion

vector sigma · August 9, 2018

4 minutes ago, fusion71au said:

Yes, all is good but spelling mistake in log for stage 1 "Writting" should be "Writing" . Install log for r4643...

Sorry, I forgot about it. I'm still working on the package so next time I'll do the correction!

Badruzeus · August 10, 2018

@fusion71au any explanation why I can boot normally with Clover UEFI on my mach (sig) only with this?

sudo newfs_msdos -F 32 -b 2048 -v EFI /dev/rdiskXsY

w/o "-b 2048" I get strange behaviour with it (CaseSensitive issue, not loaded EFI kexts, broken themes, etc).

Is this specific BIOS firmware limitation or what? TIA.

#EDIT: Yeah, my partition map is GUID for sure.

#EDIT2: Also tried with various ~Aptio*.efi driver, PartitionDxe, but still.. I need this for my ESP:

Allocation Block Size:    2048 Bytes

Edited August 10, 2018 by Badruzeus

fusion71au · August 10, 2018

14 minutes ago, Badruzeus said:
@fusion71au any explanation why I can boot normally with Clover UEFI on my mach (sig) only with this?
sudo newfs_msdos -F 32 -b 2048 -v EFI /dev/rdiskXsY
w/o "-b 2048" I get strange behaviour with it (CaseSensitive issue, not loaded EFI kexts, broken themes, etc).

Is this specific BIOS firmware limitation or what? TIA.

#EDIT: Yeah, my partition map is GUID for sure.

#EDIT2: Also tried with various ~Aptio*.efi driver, PartitionDxe, but still.. I need this for my ESP:
Allocation Block Size:    2048 Bytes

Not sure but I'm guessing its probably something specific to your BIOS firmware.

TBH, I've rarely had the need to format my EFI System partition and never specified block size, -b, when using newfs_msdos to format it - just omitted the setting and it usually works. Apparently, 2KiB is the sector size for CD/DVD-ROMS?

Slice · August 10, 2018

7 hours ago, Badruzeus said:
@fusion71au any explanation why I can boot normally with Clover UEFI on my mach (sig) only with this?
sudo newfs_msdos -F 32 -b 2048 -v EFI /dev/rdiskXsY
w/o "-b 2048" I get strange behaviour with it (CaseSensitive issue, not loaded EFI kexts, broken themes, etc).

Is this specific BIOS firmware limitation or what? TIA.

#EDIT: Yeah, my partition map is GUID for sure.

#EDIT2: Also tried with various ~Aptio*.efi driver, PartitionDxe, but still.. I need this for my ESP:
Allocation Block Size:    2048 Bytes

You should use Fat.efi driver because the one from firmware is not good.

Slice · August 10, 2018

13 hours ago, fantomas1 said:

Hi Clover team

As you can see, this topic has became expansive enough (more than 700 pages, 25 posts per page) and to continue posting further would be more counterproductive, IMO.

Without dwelling on that (I think you've all understood that no one is so crazy about reading the 700 pages to be up to date, right?), I suggest you to open another topic (v2.0 ) and continue to discuss.

This thread is like a chat for short conversation: a question and an answer that not deserves separate thread.

For long-live solution that can be interesting in history we have to create separate topics.

Matgen84 · August 10, 2018

Hi

With latest commit r4643, a security check box appears when I launch Clover to update (install). No check box with previous version r4639. I don't understand why?

Edited August 10, 2018 by Matgen84

vector sigma · August 10, 2018

1 hour ago, Matgen84 said:

No check box with previous version r4639

Isn't a checkbox, it's an alert window and is what make this installer better -> commit

chris1111 · August 12, 2018

macOS Mojave 10.14 Beta 6 (18A353d)

Xcode Version 10.0 beta 5 (10L221o)

Clover Revision

4644

UDK2018 Revision

37970

AptioMemoryFix Revision

#define APTIOMEMORYFIX_PROTOCOL_REVISION 22

ApfsDriverLoader Version

#define APFSDRIVERLOADER_VERSION L"1.3.2"

All good here

☟

Spoiler

Badruzeus · August 12, 2018

6 minutes ago, chris1111 said:

macOS Mojave 10.14 Beta 6 (18A353d)

Xcode Version 10.0 beta 5 (10L221o)

Clover Revision

4644

UDK2018 Revision

37970

AptioMemoryFix Revision

#define APTIOMEMORYFIX_PROTOCOL_REVISION 22

ApfsDriverLoader Version

#define APFSDRIVERLOADER_VERSION L"1.3.2"

All good here

☟

Hide contents

Anyway, how to check *.efi driver version / revision using Terminal?

chris1111 · August 12, 2018

23 minutes ago, Badruzeus said:

Anyway, how to check *.efi driver version / revision using Terminal?

svn info /$HOME/src/UDK2018/Clover | grep "Revision" | awk '{print $2;}'

svn info /$HOME/src/UDK2018 | grep "Revision" | awk '{print $2;}'

grep REVISION /$HOME/src/UDK2018/AptioFixPkg/Include/Protocol/AptioMemoryFixProtocol.h

grep APFSDRIVERLOADER_VERSION /$HOME/src/UDK2018/ApfsSupportPkg/Platform/ApfsDriverLoader/Version.h

Edited August 12, 2018 by chris1111

Badruzeus · August 12, 2018

5 minutes ago, chris1111 said:

svn info /$HOME/src/UDK2018/Clover | grep "Revision" | awk '{print $2;}'
svn info /$HOME/src/UDK2018 | grep "Revision" | awk '{print $2;}'
grep REVISION /$HOME/src/UDK2018/AptioFixPkg/Include/Protocol/AptioMemoryFixProtocol.h
grep APFSDRIVERLOADER_VERSION /$HOME/src/UDK2018/ApfsSupportPkg/Platform/ApfsDriverLoader/Version.h

I mean, from prebuilt *.efi binary driver.. but, thank you.

Edited August 12, 2018 by Badruzeus

chris1111 · August 12, 2018

1 minute ago, Badruzeus said:

I mean, from prebuilt *.efi binary driver. Thank you.

which efi drivers

Badruzeus · August 12, 2018

2 minutes ago, chris1111 said:

which efi drivers

Any pre-installed *.efi drivers:

Spoiler


0:980  0:000  === [ LoadDrivers ] =======================================
0:985  0:004  Loading ApfsDriverLoader-64.efi  status=Success
1:003  0:017   - driver needs connecting
1:003  0:000  Loading AppleImageCodec-64.efi  status=Success
1:004  0:000  Loading AppleKeyAggregator-64.efi  status=Success
1:005  0:000  Loading AppleUITheme-64.efi  status=Success
1:006  0:000  Loading AptioMemoryFix-64.efi  status=Success
1:006  0:000  Loading CsmVideoDxe-64.efi  status=Success
1:007  0:000   - driver needs connecting
1:007  0:000  Loading DataHubDxe-64.efi  status=Success
1:012  0:004  Loading FirmwareVolume-64.efi  status=Success
1:012  0:000  Loading FSInject-64.efi  status=Success
1:013  0:000  Loading HashServiceFix-64.efi  status=Success
1:014  0:000  Loading SMCHelper-64.efi  status=Success
1:015  0:000  Loading VBoxHfs-64.efi  status=Success
1:015  0:000   - driver needs connecting
1:015  0:000  3 drivers needs connecting ...
1:015  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
1:015  0:000  APFS driver loaded

chris1111 · August 12, 2018

34 minutes ago, Badruzeus said:

Any pre-installed *.efi drivers:

Reveal hidden contents



0:980  0:000  === [ LoadDrivers ] =======================================
0:985  0:004  Loading ApfsDriverLoader-64.efi  status=Success
1:003  0:017   - driver needs connecting
1:003  0:000  Loading AppleImageCodec-64.efi  status=Success
1:004  0:000  Loading AppleKeyAggregator-64.efi  status=Success
1:005  0:000  Loading AppleUITheme-64.efi  status=Success
1:006  0:000  Loading AptioMemoryFix-64.efi  status=Success
1:006  0:000  Loading CsmVideoDxe-64.efi  status=Success
1:007  0:000   - driver needs connecting
1:007  0:000  Loading DataHubDxe-64.efi  status=Success
1:012  0:004  Loading FirmwareVolume-64.efi  status=Success
1:012  0:000  Loading FSInject-64.efi  status=Success
1:013  0:000  Loading HashServiceFix-64.efi  status=Success
1:014  0:000  Loading SMCHelper-64.efi  status=Success
1:015  0:000  Loading VBoxHfs-64.efi  status=Success
1:015  0:000   - driver needs connecting
1:015  0:000  3 drivers needs connecting ...
1:015  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
1:015  0:000  APFS driver loaded

maybe look at UDK2018/Build/Cover ?

chris1111 · August 12, 2018

InstallBootsectors/postinstall

the script not cleanup /tmp file

Spoiler

not working with the scrip but terminal is ok

Strange now I rebuild new package and the file changing the name

newbs, origbs

I need terminal for removing the file

It is not really important because is remove at reboot

Spoiler

51Capture.png.adcc3691383fa765dd700e3d3ab9e4a1.png

Edited August 12, 2018 by chris1111
put image in spoiler and clean my post

vector sigma · August 12, 2018

11 hours ago, chris1111 said:

It is not really important because is remove at reboot

Is not important just because dd overwrite those file in any case before proceed. No need for any other task.

Tetonne · August 15, 2018

how can i upgrade my Window 10 on a dual boot (window/HS) same HD?

the upgrade always failed

==> easy win 10 upgrade on a dual boot clover HD

Badruzeus · August 15, 2018

8 minutes ago, Tetonne said:

how can i upgrade my Window 10 on a dual boot (window/HS) same HD?

the upgrade always failed

==> easy win 10 upgrade on a dual boot clover HD

It maybe, your configuration issue? Not becaused of Clover. (not mentioning Legacy/UEFI)

Cyberdevs · August 16, 2018

Hey guys;

Hi @savvamitrofanov

According to these statement:

"Now for security reasons you should load AppleLoadImage.efi right before ApfsDriverLoader.efi. If you use Clover bootloader, you can just put AppleLoadImage.efi and ApfsDriverLoader.efi into your drivers64uefi folder."

Source

We need to install AppleLoadImage.efi as well but when I put the driver inside drivers64UEFI my system simply won't boot, it just hangs on the logo, and even if it decides to boot the only partition that is detected by clover is the EFI partition on the hard disk that I have windows installed.

Is it gonna be implemented in the clover by default or we just need to compile it manually?

What am I missing?

These are the drivers that I currently use to boot into macOS without any issues:

ApfsDriverLoader.efi

AptioMemoryFix-64.efi

VBoxHfs-64.efi

Any input on the matter will be highly appreciated.

Thanks.

Edited August 16, 2018 by Cyberdevs

Sherlocks · August 16, 2018

11 minutes ago, Cyberdevs said:

Hey guys;

According to these statement:
"Now for security reasons you should load AppleLoadImage.efi right before ApfsDriverLoader.efi. If you use Clover bootloader, you can just put AppleLoadImage.efi and ApfsDriverLoader.efi into your drivers64uefi folder."

Source

We need to install AppleLoadImage.efi as well but when I put the driver inside drivers64UEFI my system simply won't boot, it just hangs on the logo, and even if it decides to boot the only partition that is detected by clover is the EFI partition on the hard disk that I have windows installed.

Is it gonna be implemented in the clover by default or we just need to compile it manually?
What am I missing?

These are the drivers that I currently use to boot into macOS without any issues:
ApfsDriverLoader.efi
AptioMemoryFix-64.efi
VBoxHfs-64.efi

Any input on the matter will be highly appreciated.

Thanks.

+1. hang on oem logo. need to report it to @savva

built this "https://github.com/acidanthera/AppleSupportPkg/commit/68f14f8161179d718374f4d5ee0f3e902eef416f"

and tested both files in driver64UEFI folder

ApfsDriverLoader.efi
AppleImageLoader.efi

나의 LG-F800S 의 Tapatalk에서 보냄

Edited August 16, 2018 by Sherlocks

Badruzeus · August 16, 2018

Seems normal here, but... these are some logs from yesterday 10.14 APFS, my bad I just cleanse installed it with HFS+

Spoiler


0:976  0:000  === [ LoadDrivers ] =======================================
0:981  0:005  Loading ApfsDriverLoader-64.efi  status=Success
1:003  0:022   - driver needs connecting
1:003  0:000  Loading AppleImageCodec-64.efi  status=Success
1:004  0:000  Loading AppleKeyAggregator-64.efi  status=Success
1:005  0:000  Loading AppleUITheme-64.efi  status=Success
1:006  0:000  Loading AptioMemoryFix-64.efi  status=Success
1:006  0:000  Loading CsmVideoDxe-64.efi  status=Success
1:007  0:000   - driver needs connecting
1:007  0:000  Loading DataHubDxe-64.efi  status=Success
1:012  0:004  Loading FirmwareVolume-64.efi  status=Success
1:013  0:000  Loading FSInject-64.efi  status=Success
1:013  0:000  Loading HashServiceFix-64.efi  status=Success
1:014  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
1:015  0:000  Loading SMCHelper-64.efi  status=Success
1:016  0:000  Loading VBoxHfs-64.efi  status=Success
1:016  0:000   - driver needs connecting
1:016  0:000  3 drivers needs connecting ...
1:016  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
1:016  0:000  APFS driver loaded
1:016  0:000  Video driver loaded: disconnect Success

I still don't get it yet, *.efi drivers can be sorted upon load?

Cyberdevs · August 16, 2018

40 minutes ago, Sherlocks said:

+1. hang on oem logo. need to report it to @savva

built this "https://github.com/acidanthera/AppleSupportPkg/commit/68f14f8161179d718374f4d5ee0f3e902eef416f"

and tested both files in driver64UEFI folder

ApfsDriverLoader.efi
AppleImageLoader.efi

I believe I just used that build, I just cloned the GitHub about two hours ago.

I'm gonna give it another try.

4 minutes ago, Badruzeus said:

Seems normal here, but... these are some logs from yesterday 10.14 APFS, my bad I just cleanse installed it with HFS+

Reveal hidden contents



0:976  0:000  === [ LoadDrivers ] =======================================
0:981  0:005  Loading ApfsDriverLoader-64.efi  status=Success
1:003  0:022   - driver needs connecting
1:003  0:000  Loading AppleImageCodec-64.efi  status=Success
1:004  0:000  Loading AppleKeyAggregator-64.efi  status=Success
1:005  0:000  Loading AppleUITheme-64.efi  status=Success
1:006  0:000  Loading AptioMemoryFix-64.efi  status=Success
1:006  0:000  Loading CsmVideoDxe-64.efi  status=Success
1:007  0:000   - driver needs connecting
1:007  0:000  Loading DataHubDxe-64.efi  status=Success
1:012  0:004  Loading FirmwareVolume-64.efi  status=Success
1:013  0:000  Loading FSInject-64.efi  status=Success
1:013  0:000  Loading HashServiceFix-64.efi  status=Success
1:014  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
1:015  0:000  Loading SMCHelper-64.efi  status=Success
1:016  0:000  Loading VBoxHfs-64.efi  status=Success
1:016  0:000   - driver needs connecting
1:016  0:000  3 drivers needs connecting ...
1:016  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
1:016  0:000  APFS driver loaded
1:016  0:000  Video driver loaded: disconnect Success

I still don't get it yet, *.efi drivers can be sorted upon load?

I guess what it means is just simply place it in the driversUEFI64 folder. Not to actually load it upon boot like Ozmosis.

Matgen84 · August 16, 2018

47 minutes ago, Sherlocks said:

+1. hang on oem logo. need to report it to @savva

built this "https://github.com/acidanthera/AppleSupportPkg/commit/68f14f8161179d718374f4d5ee0f3e902eef416f"

and tested both files in driver64UEFI folder

ApfsDriverLoader.efi
AppleImageLoader.efi

나의 LG-F800S 의 Tapatalk에서 보냄

How to build AppleImageLoader.efi for testing. Please.

Cyberdevs · August 16, 2018

@Sherlocks

Still the same issue,

If I press Tab twice on the OEM logo clover loads but still doesn't detect any of my hard disks except for the Windows's EFI partition.

These are the files I'm using.

AppleSupport-v2.0.1-RELEASE.zip

savvas · August 16, 2018

Hello guys!

I hope I fixed this issue for now, you can try this debug prebuilt binaries

AppleSupport-v2.0.1-DEBUG.zip

Edited August 16, 2018 by savvamitrofanov

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites