Jump to content
ErmaC

Clover General discussion

19,137 posts in this topic

Recommended Posts

2 minutes ago, Matgen84 said:

@Badruzeus @ellaosx

 

There is no issue with ApfsDriverloader.efi using Clover r4771 :)

 

If In understand well, ebuild.sh file: "--ext-co" "checkout & build external drivers at ..src/EXT_PACKAGES". It means download and compile from source this driver. Right? 

 

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

Share this post


Link to post
Share on other sites
Advertisement
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
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

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   0 members

    No registered users viewing this page.

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By AppleBytes
      OK, I've searching for days trying to gather up the tools to make my current install work correctly. I'm well on my way. But all the links to the things I currently must have were apparently nuked "during a forum upgrade". :(
      As far as EFI Studio goes; I can find many links to it. But for Insanelymac, they're broken (due to the upgrade), or for the Netkas site, they're links to either Rapidshare, or Mediafire that also no linger exist. I see many users here indicating that they used it to tweak their DSDT. But the web (google/duckduckgo), Instanelymac, and Netkas seem to have no idea where it's gone.
      Could some kind soul please share a copy, or a link? I'm a loooong time hacker, and would love to bring it back to life. In fact, I'd love to improve it -- or at least bring it up to current times. If only I knew where it was.
      Thank you for all your time, and consideration.
       
      --Chris
       
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
×