Jump to content
ErmaC

Clover General discussion

22,334 posts in this topic

Recommended Posts

2 minutes ago, Badruzeus said:

It should be: Yes (compiled from source using latest commit).

 

I just rebuilt r4771 using UDK, and weird is.. still ApfsDriverLoader gives debug logs (files attached).

@ellaosx is your 10.13 (or 10.14) using HFS+ or APFS? On my case is: HFS+, though I saw no diff with APFS previously. 

r4771-UDK-Apfs.zip

Same here HFS+ 10.13  latest 3 releases have this behaviour previous versions don't

Share this post


Link to post
Share on other sites
Advertisement
1 hour ago, Badruzeus said:

It should be: Yes (compiled from source using latest commit).

 

I just rebuilt r4771 using UDK, and weird is.. still ApfsDriverLoader gives debug logs (files attached).

@ellaosx is your 10.13 (or 10.14) using HFS+ or APFS? On my case is: HFS+, though I saw no diff with APFS previously. 

r4771-UDK-Apfs.zip

 

If you want, you can test my apfsdriverloader: it works well on Mojave

ApfsDriverLoader-64.efi.zip

Share this post


Link to post
Share on other sites
On 11/22/2018 at 5:31 AM, pkdesign said:

Latest Clover 4769 breaks legacy BIOS boot. Had to revert back to 4741 in order to boot my system.

 

Try replacing just the "boot" file with the one attached, compiled with GCC53.  I have also attached Clover_v2.4k_r4772 package installer compiled with GCC53...

 

1603819292_bootfile.png.2ad1145c5c4ef0610c131ba081ad6168.png

 

I noticed that for the latest officially released Clover r4769 from Sourceforge, the boot process would hang on my legacy desktop after seeing "6" on the screen.  It seems that CloverEFI (the boot6/boot7 "boot" file) compiled with XCODE 10.1 fails to chainload CLOVERX64.efi but CloverEFI compiled with GCC53 works OK.

 

Bug possibly due to latest edk2 28338 sync with commit r4761?

 

Clover_v2.4k_r4772.pkg.zip

boot.zip

Edited by fusion71au
XCODE 10.1 problem but XCODE 8, 9 and GCC OK

Share this post


Link to post
Share on other sites
6 hours ago, fusion71au said:

 

Try replacing just the "boot" file with the one attached, compiled with GCC53.  I have also attached Clover_v2.4k_r4772 package installer compiled with GCC53...

 

1603819292_bootfile.png.2ad1145c5c4ef0610c131ba081ad6168.png

 

I noticed that for the latest officially released Clover r4769 from Sourceforge, the boot process would hang on my legacy desktop after seeing "6" on the screen.  It seems that CloverEFI (the boot6/boot7 "boot" file) compiled with XCODE fails to chainload CLOVERX64.efi but CloverEFI compiled with GCC53 works OK.

 

Bug possibly due to latest edk2 28338 sync with commit r4761?

 

Clover_v2.4k_r4772.pkg.zip

boot.zip

officially released Clover 4769 compiled with UDK2018 without any changes for a long period.

Share this post


Link to post
Share on other sites
On 11/23/2018 at 9:27 PM, Slice said:

officially released Clover 4769 compiled with UDK2018 without any changes for a long period.

 

@Slice,

 

Notice that commit r4761 includes a change to Variable.c in /Patches_for_UDK2018/MdeModulePkg/Universal/Variable/RuntimeDxe/ ...

 

Spoiler

--- a/Patches_for_UDK2018/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
+++ b/Patches_for_UDK2018/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
@@ -2459,6 +2459,8 @@
         if (Variable->CurrPtr != NULL) {
           if (VariableCompareTimeStampInternal (&(((AUTHENTICATED_VARIABLE_HEADER *) CacheVariable->CurrPtr)->TimeStamp), TimeStamp)) {
             CopyMem (&AuthVariable->TimeStamp, TimeStamp, sizeof (EFI_TIME));
+          } else {
+            CopyMem (&AuthVariable->TimeStamp, &(((AUTHENTICATED_VARIABLE_HEADER *) CacheVariable->CurrPtr)->TimeStamp), sizeof (EFI_TIME));
           }
         }
       }

 

 

Also noticed that official Clover r4769 was compiled with XCODE 10.1 (with tool chain set to XCODE8) but r4741 was compiled with XCODE 8.3.3 ---> successful boot...

 

6:891  0:000  Starting Clover revision: 4741 on CLOVER EFI
6:891  0:000  Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.12.6 | XCODE: 8.3.3]

Edit

Further to XCODE 10.1 being the problem, my legacy desktop boots fine with Clover r4772 compiled with XCODE 8.2.1 or XCODE 9.2 (both with tool chain set to XCODE8)....

 

6:897  0:000  Starting Clover revision: 4772 on CLOVER EFI
6:897  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/fusion71au/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 3 | OS: 10.11.6 | XCODE: 8.2.1]

 

6:911  0:000  Starting Clover revision: 4772 on CLOVER EFI
6:911  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D USE_APPLE_HFSPLUS_DRIVER -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/fusion71au/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.13.6 | XCODE: 9.2]

 

If I swap out the boot6 "boot" file with one compiled with XCODE 10.1, the boot hangs ---> after seeing "6" on the screen, it stops at an underscore symbol "_" and no GUI appears.

Edited by fusion71au
r4772 tested OK compiled with XCODE 8.2.1, 8.3.3 or 9.2 but not 10.1

Share this post


Link to post
Share on other sites
18 hours ago, fusion71au said:

 

@Slice,

 

Notice that commit r4761 includes a change to Variable.c in /Patches_for_UDK2018/MdeModulePkg/Universal/Variable/RuntimeDxe/ ...

 

 

 

This is never used.

For legacy Clover boot6 and boot7 there is

MdeModulePkg/Universal/Variable/EmuRuntimeDxe/

And for EmuVariableDxe.efi there is separate sources

Clover/Protocols/EmuVariableUefi/EmuVariableRuntimeDxe.inf

Otherwise we have hardware NVRAM and use Variable functions from UEFI BIOS.

Share this post


Link to post
Share on other sites
1 hour ago, SavageAUS said:

Is there a way to reset nvram on a system that gets stuck at scanning entries?

I switched to the Clovy theme and now it’s stuck at scanning entries. F11 does nothing.

 

Is there a way to clear nvram via UEFI shell?

If "Clovy" theme is the cause, I guess you could just remove it via UEFI Shell over USB.

(FS0 is relative to your Internal EFI from your Disk map for sure)

FS0:
cd \EFI\CLOVER\themes\
  rm "Theme Name"
exit

EFI-Shell.png

 

#EDIT: It wiill force using "embedded" bcoz specified theme was not found.

Edited by Badruzeus

Share this post


Link to post
Share on other sites
1 minute ago, Badruzeus said:

If "Clovy" theme is the cause, I guess you could just remove it via UEFI Shell over USB.

(FS0 is relative to your Internal EFI from your Disk map for sure)


FS0:
cd \EFI\CLOVER\themes\
  rm "Theme Name"
exit

 

EFI-Shell.png

Sorry bro, i deleted my post from here and moved it HERE

Share this post


Link to post
Share on other sites
11 minutes ago, SavageAUS said:

Sorry bro, i deleted my post from here and moved it HERE

Seems not #OffTopic even you was posting here, it was also Clover related (I think, but your choice).

Hmmb, I just have no idea why previously created 2 same posts on diff threads #LoL

Edited by Badruzeus

Share this post


Link to post
Share on other sites
3 minutes ago, Allan said:

 

 

which one should I be looking at? Looking at the link, the only think remotely similar to what I want is dual booting with Windows and the answer there doesn't apply. Thanks

Share this post


Link to post
Share on other sites

There is something wrong with PS/2 Keyboatd and Mouse in revison 4769.
After loading Clover, it did not working PS/2 Device. Is there someone any same experience as me?

Sented by Tapatalk in my Android SM-G930S

Share this post


Link to post
Share on other sites
15 minutes ago, Ritz Carltn said:

There is something wrong with PS/2 Keyboatd and Mouse in revison 4769.
After loading Clover, it did not working PS/2 Device. Is there someone any same experience as me?

Sented by Tapatalk in my Android SM-G930S
 

It looks like wrong compilation of file boot. Take it from previous revision.

Share this post


Link to post
Share on other sites

Hi,

 

Why there is a file "Shell.inf" in EFI/CLOVER/Tools? Please, I don't understand

 

Thanks

 

Share this post


Link to post
Share on other sites
5 minutes ago, Matgen84 said:

Hi,

 

Why there is a file "Shell.inf" in EFI/CLOVER/Tools? Please, I don't understand

 

Thanks

 

Because of a build script bug.

Share this post


Link to post
Share on other sites
20 minutes ago, Slice said:

Because of a build script bug.

 

 

Build_clover.command (EDK2) and Dids script (UDK2018) have the same issue in r4777: a file "Shell.inf" in EFI/CLOVER/Tools. I also found this file in a old version r4761.

 

Some solution.

Share this post


Link to post
Share on other sites
On 11/22/2018 at 1:54 AM, Badruzeus said:

Working fine here either, I've 3 ancient machines using Legacy.

 

On my case is not Clover, but recent "ApfsDriverLoader*.efi".

I just built v 4779 using BuildClover command and I still can not boot my legacy machine. All I see it a blinking cursor.

 

I do not have APFS driver in kext since I don’t use it. 

Share this post


Link to post
Share on other sites
18 hours ago, Matgen84 said:

 

 

Build_clover.command (EDK2) and Dids script (UDK2018) have the same issue in r4777: a file "Shell.inf" in EFI/CLOVER/Tools. I also found this file in a old version r4761.

 

Some solution.

Drag the file to trash.

Share this post


Link to post
Share on other sites
1 minute ago, Slice said:

Drag the file to trash.

 

Ok. I did that. But Shell.inf is created for each version in EFI/CLOVER/TOOLS, I don't know why.

Share this post


Link to post
Share on other sites
10 hours ago, pkdesign said:

I just built v 4779 using BuildClover command and I still can not boot my legacy machine. All I see it a blinking cursor.

 

I do not have APFS driver in kext since I don’t use it. 

There should be more information about the issue.

Did you try other boot6 or boot7 files? From previous revisions.

Did you set Boot->Debug=YES to get a debug.log?

What efi drivers do you have?

3 minutes ago, Matgen84 said:

 

Ok. I did that. But Shell.inf is created for each version in EFI/CLOVER/TOOLS, I don't know why.

Because of build script.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

Announcements

  • Similar Content

    • By cvad
      View File Bootdisk Utility
      Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
      Anyone who likes the program, please support its Community Score.
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
    • By STLVNUB
      Script file to clone and help build Clover or Opencore repos
      Script will create link to itself in /usr/local/bin/bob
      Script SHOULD fix up any stray bobs you may have.
      Then you only need to type bob. and a parameter
      "a" for ACID repo, official
      "d" for ACID repo DUET build
      "c" for CLOVER
      "e" to erase UDK Folder
      Easier typing bob than.....usual stuff
      YOU WILL NEED TO cmod+x THE SCRIPT
      Enjoy
       
    • By PropoFlexWX4
      After hearing that OpenCore is so much better than Clover, and that it will probably be able to boot Big Sur before Clover does, I decided to take the jump.
       
      Running Catalina 10.15.5 18F101 with OC 0.5.9.
       
      So far I like the result. The OS feels faster, boots faster.
      And absolutely everything works (sleep, network, etc...)
       
      So, that's it? Is there anything else I have to do?
×