Jump to content
ErmaC

Clover problems report & features request

124 posts in this topic

Recommended Posts

Already done.

What Clover version you mean?

@grayen

 

I had an experience to boot macOS and Windows 7 Pro 64bit UEFI on GPT formatted disk on legacy-BIOS computer with Core2Duo CPU by Clover. It is possible as you said. I don't know if Windows 10 required something more.

I mean make Clover boot like BIOS, if Clover can't find macOS installer to update. It'll boot into macOS partition, it'll make update easier. Also, I'm using the latest.

Share this post


Link to post
Share on other sites
Advertisement

Clover can find macOS installer to update. Thousands users do update this way.

Show your preboot.log where can we look on all partitions and loaders.

STATIC CHAR16 *OSXInstallerPaths[] = {
  L"\\Mac OS X Install Data\\boot.efi",
  L"\\macOS Install Data\\boot.efi",
  L"\\macOS Install Data\\Locked Files\\Boot Files\\boot.efi",
  L"\\OS X Install Data\\boot.efi",
  L"\\.IABootFiles\\boot.efi"
};
 

Share this post


Link to post
Share on other sites

 

Clover can find macOS installer to update. Thousands users do update this way.

Show your preboot.log where can we look on all partitions and loaders.

STATIC CHAR16 *OSXInstallerPaths[] = {
  L"\\Mac OS X Install Data\\boot.efi",
  L"\\macOS Install Data\\boot.efi",
  L"\\macOS Install Data\\Locked Files\\Boot Files\\boot.efi",
  L"\\OS X Install Data\\boot.efi",
  L"\\.IABootFiles\\boot.efi"
};
 

No, I mean we have an option to set default boot volume right? But it only boots into 1 volume, sometimes I need to update macOS. App Store will create another volume of macOS Install or something, anyway I can make Clover boot into macOS install first like BIOS. If Clover can't find macOS install then it'll boot into second default boot volume like macOS system

Share this post


Link to post
Share on other sites

slice I think what he wants is that after an apple update clover use boot next to automatically finish the os update install instead of having to manually select the updater volume from clover gui

Share this post


Link to post
Share on other sites

slice I think what he wants is that after an apple update clover use boot next to automatically finish the os update install instead of having to manually select the updater volume from clover gui

 

 

You are right, that way I can set App Store to update macOS automatically

Share this post


Link to post
Share on other sites

I started macOS as usual then I see update in AppStore and click OK. 

macOS loads update, begins it and then restarted into "macOS install". 

It is already happens.

I can't set "BootNext" variable because Clover is not working during this process.

Share this post


Link to post
Share on other sites

I started macOS as usual then I see update in AppStore and click OK. 

macOS loads update, begins it and then restarted into "macOS install". 

It is already happens.

I can't set "BootNext" variable because Clover is not working during this process.

 

I mean, we have Default Boot Volume to help Clover to boot into "that partition" when you Clover starting. I set it to my macOS volume, it works perfectly but when I try to update to some macOS version. App Store will create a volume name "macOS install" right, so what I asking for is can you make more option like Default Boot Volume 2, 3,... If Clover can't find the first Default Boot Volume 1, it'll boot into Default Boot Volume 2. It'll make we update macOS easier

Share this post


Link to post
Share on other sites

OK, I understand.

I have DefaultBootVolume=LastBootedVolume. As far as I remember it automatically switched to update.

But it didn't switch back to my macOS partition. If I have more option, Clover will switch to update when I reboot from App Store. Or if Clover can't find that update partition, it'll switch back to my macOS partition. That's simple

Share this post


Link to post
Share on other sites

My case, Single SSD

High Sierra Vol name = Macintosh HD

DefaultBootVolume = Macintosh HD in config

Timeout 3 in config

 

Update from appstore, clover automatically enter high sierra installer(macOS install Macintosh HD). After install update, there is no installer in GUI, and enter Macintosh HD.

 

 

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

My case, Single SSD

High Sierra Vol name = Macintosh HD

DefaultBootVolume = Macintosh HD in config

Timeout 3 in config

 

Update from appstore, clover automatically enter high sierra installer(macOS install Macintosh HD). After install update, there is no installer in GUI, and enter Macintosh HD.

 

 

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Mine too

1 SSD, macOS High Sierra vol name = macOS (same with DefaultBootVolume)

Timeout = 5

Clover still boot into macOS even Clover found macOS install when I try to update

Share this post


Link to post
Share on other sites

Mine too

1 SSD, macOS High Sierra vol name = macOS (same with DefaultBootVolume)

Timeout = 5

Clover still boot into macOS even Clover found macOS install when I try to update

Strange. In my case. There is no problem that i mentioned above.

 

On my laptop, i can't use lastvolumename option. So i selected mac partition name for defaultvolumename.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

i have same issue on haswell laptop 1ssd with win10/10.13.x clover timeout does not work config set to 5sec but at boot clover sits there forever until i manually chose os. works fine on my other machines though. it has always happened on this machine so it does not bother me any longer LOL.

Share this post


Link to post
Share on other sites

On some more recent HP UEFI implementations (including the Spectre x360 and Envy x360's) Clover is unable to boot OS X without a workaround. HP's UEFI loads some sort of touch keyboard (likely indicative of a debug mode), and when OS X is loaded boot.efi will hang and never proceed. No kernel panic occurs, boot.efi simply does not start loading. This problem can be resolved by chainloading clover from a text only bootloader (grub works, secure boot workarounds like Preloader.efi work best), or by modifying the source code of clover. The issue is something left over from rEFIt, as rEFInd also loads the touch keyboard. It appears that the function

BOOLEAN ReadAllKeyStrokes(VOID)

is broken. When the function body is commented and the function is modified to only return false, like so:

BOOLEAN ReadAllKeyStrokes(VOID)
{
    //problem code
    /*
    BOOLEAN       GotKeyStrokes;
    EFI_STATUS    Status;
    EFI_INPUT_KEY key;
    
    GotKeyStrokes = FALSE;
    for (; {
        Status = gST->ConIn->ReadKeyStroke (gST->ConIn, &key);
        if (Status == EFI_SUCCESS) {
            GotKeyStrokes = TRUE;
            continue;
        }
        break;
    }
    return GotKeyStrokes;*/
    return FALSE;
}

Clover does not encounter the touch keyboard issue and loads OSX successfully with no workarounds. I believe that something in this method triggers HP's UEFI to enter a type of debug mode and load the touch keyboard. Any ideas on how this method could be fixed to prevent this error?

Share this post


Link to post
Share on other sites

A typo from time ago

in clover bootmenu / options / PCI Devices

 

custom properies should be custom properties?

probably you mean this...

 

menu.c

NewEntry(&Entry, &SubScreen, ActionEnter, SCREEN_DEVICES, "Custom properies->");
and yes is a typo... should be "Custom properties->"

 

ErmaC

Share this post


Link to post
Share on other sites

Dear devs,

 

I just realized that I need to use "-DANDX86" everytime on buildclover script to make PhoenixOS && RemixOS (Android-x86) detected by Clover bootloader.

 

If possible.. May I propose these flags to be true, so Clover detects Android-x86 based OSes by default? Thanks.

 

 

#!ifdef ANDX86
  DEFINE ANDX86_FLAG = -DANDX86
#!endif 

 

 

Share this post


Link to post
Share on other sites

Dear devs,

 

I just realized that I need to use "-DANDX86" everytime on buildclover script to make PhoenixOS && RemixOS (Android-x86) detected by Clover bootloader.

 

If possible.. May I propose these flags to be true, so Clover detects Android-x86 based OSes by default? Thanks.

 

 

#!ifdef ANDX86
  DEFINE ANDX86_FLAG = -DANDX86
#!endif 

 

 

I think it is possible because I see no reason why not. 

It was added conditionally because no one need it.

Share this post


Link to post
Share on other sites
I hope this is the right place, a recommendation
 

Is possible change the position of letters?

They are hidden underneath and there is to scroll
 
Centered is much better visually. Thank.-

post-471348-0-36534600-1515777341_thumb.png

post-471348-0-46007700-1515777373_thumb.png

post-471348-0-33471800-1515777384_thumb.png

Share this post


Link to post
Share on other sites

I hope this is the right place, a recommendation

 

Is possible change the position of letters?

They are hidden underneath and there is to scroll

 

Centered is much better visually. Thank.-

Yes is a simple html with inline css, and the last one as you show is... conclusion.html

located here https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/CloverPackage/package/Resources/templates/

 

and if I understand you correctly (align the copyright text on the right) will be:

from:

https://sourceforge.net/p/cloverefiboot/code/HEAD/tree/CloverPackage/package/Resources/templates/Conclusion.html#l14

to (changed line 14)

p.copyright{margin: 0px; font:13px 'Lucida Grande'; text-align: right}
ErmaC

Share this post


Link to post
Share on other sites

feature needed  : pass-by HP840g3 bios locked and being able to boot with clover ;)

just kidding, but if you dev this i'll take it :)

Thanks U to all clover dev

best

Share this post


Link to post
Share on other sites

feature needed  : pass-by HP840g3 bios locked and being able to boot with clover ;)

just kidding, but if you dev this i'll take it :)

Thanks U to all clover dev

best

I have no HP840g3 and so I have no idea what about you tell.

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 zebity
      Hi Hypervisors,
       
      I have been working to move my Late 2009 Xserve MacOS Server onto Ubuntu 18.04 LTS QEMU/KVM based virtual machine using OVMF and Clover.
       
      After much effort and testing based on the following information from: Kraxel's, Kholia, Gordon Turner and Clover site:
      https://www.kraxel.org/blog/2017/09/running-macos-as-guest-in-kvm/
      https://github.com/kholia/OSX-KVM
      https://gist.github.com/gordonturner/2a2e5ecde5e7860b52e2
      https://clover-wiki.zetam.org/Home
       
      I have now managed to get OVMF/Clover boot and install of MacOS Sierra.
       
      I started with Ubuntu 16.04 initially but this required download and compile of QEMU to get update of machines to: pc-q35-2.9 or better, so I moved to Ubuntu 18.04, which has pc-q35.2.11 available as standard.
       
      So I am now working with standard Ubuntu 18.04 LTS based systems with following packages: kvm/qemu/libvirt/bridge-utils/ovmf/virt-manager
       
      As I want to use PCIe Passthrough for a number of PCIe card currently installed in the server (SmallTree 10GbE & Areca ARC-1883 SAS RAID) I set up my machine with linux kernel boot configuration (/etc/default/grub) of: 
      GRUB_CMDLINE_LINUX_DEFAULT="iommu=1 intel_iommu=on" (as my machine is intel VT-d based HW virtualisation)
       
      This resulted in creation of a number of iommu groups (see /sys/kernel/iommu_group directory for this and this posting for information: https://forum.level1techs.com/t/ubuntu-17-04-vfio-pcie-passthrough-kernel-update-4-14-rc1/119639 , noting that Ubuntu 18.04 LTS has kernel version: 4.15.0-22-generic so there is no need to do kernel update for iommu to work).
       
      Using bare minimal Clover config.plist:
       
       
      And following Clover UEFI drivers:
       
      I can boot MacOS, but it is very very slow... it sits on the apple boot logo for over a minutes before finally moving onto the progress bar.
      The other problem I have is that no PCI or Network devices appear in the "About This Mac" System Information Report and I cannot get any network connectivity from bridged E1000 network device.
       
      Here is my virtlib.xml dump for the virtual machine:
       

      Can any one advise of whether I need to update the CLOVER config.plist to add extra items in to allow network and PCI Passthrough to work.
       
      Thank you.
       
      Regards,
       
      Zebity
       
    • By frankiee
      Hi there, time for my first guide after asking so many things
       
      Updated for newer Clover versions and with additional instructions for more apps: gdisk and RU.
       
      So what may be overlooked sometimes in the whole boot loader discussion is the ability of UEFI to do more than just loading an OS. This is why I see ".efi" files as "apps" because in fact they just are, built on a special kind of API: UEFI. So, you can actually do stuff like editing, diagnosing, testing certain stuff at the lowest possible system level without booting to any OS.
       
      DISCLAIMER: Use this guide at your own risk! For educational purposes only! Should do not any harm, but remember you are dealing with rather low level stuff. But at least for me everything went flawless.
       
      Prerequisites:
      Working clover installation Clover Configurator or some app to edit the config.plist  
      1) Memtest
       
      This is how to install the UEFI version of Memtest with Clover:
      Download memtest, I used this link: Image for creating boot-able USB Drive Open the archive by double clicking on it. Mount the file memtest86-usb.img within by double clicking again. Now, you should see a folder named EFI in this volume, containing a folder BOOT. Open it. The files containing it are the actual app, in 32 and 64 bit versions. Think in almost all cases we want to use the 64 bit version. Now, mount your EFI partition, using Clover configurator. Create a folder named MemTest86 in the EFI folder on your main drive. Copy all files in the EFI/BOOT folder from the mounted image to your newly created folder. That ends the basic setup! Now, we add the correct Menu entry to the clover boot menu, so that we can actually start this app.
       
      Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Under "Custom Entries", add an entry like this:
       

       
      Please note while the path you enter is not case sensitive, you must make sure you use the backslash "\" for entering paths, and not a slash. So basically what we do is tell clover where it can find the app, give it a name, and tell clover it is a "Windows" app. Note: with older Clover versions we had to set this to "Linux", but for now "Windows" is the setting that works.
       
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <true/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>MemTest86</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string>\EFI\CLOVER\themes\Icons\os_mint.png</string> <key>Path</key> <string>\EFI\MemTest86\BOOTX64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> Now, save and reboot and you should see the newly created entry. Note that I also used a custom Icon - this is optional - in case you don't you will just see a generic windows icon instead:
       

       
      And this is how it looks like:
       

       

       
      PS: also noticeably faster and you get also more features with this version than with the older version, for example it does now write a log file. For more Information, see: http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%28Pure-UEFI%29
       
       
      2) gdisk
       
      Another app you can use is the UEFI version of gdisk (aka GPT fdisk), which you can use to edit and change your partitions.
       
      Warning! Install and use this app at your own risk! If you do something wrong here you might nuke your drive(s), so only use that if you know what you are doing.
       
      This is how to do it (even easier):
      Download here: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download Mount your EFI partition Unzip the file and copy the resulting folder to your EFI Folder, so your path goes like this "/Volumes/EFI/EFI/gdisk-efi" Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Add an entry like this:  
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <false/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>GDisk</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string></string> <key>Path</key> <string>\EFI\gdisk-efi\gdisk_x64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> When everything went OK you should see this after selecting the respective entry in Clover:
       

       
       
      3) RU
       
      I recently found one more app that might be interesting to some, and thats "Read Universal" or in short "RU". This is a tool that enables you to debug your BIOS and read (and modify!) every imaginable data, including UEFI variables, ACPI Tables etc.
       
      Warning, again! I think blindly messing around with this app is even more dangerous, but on the other hand it gives you access to a lot of potentially interesting stuff.
      Download here: http://ruexe.blogspot.de/ The next steps are basically the same as above so make a folder in your EFI partition, copy the .EFI files and make another custom entry in your config.plist Here are some screens:
       

       

       

       
       
      So this is what you also can do with UEFI and clover. I am curious which other useful applications might exist!
       
      Anybody who knows, maybe post it here?
    • By TimNeumann
      MB: Asus X99 A-II
      RAM: G.Skill Ripjaws V F4-3200C16D-32GVK (3200MHz, 4x 16GB DIMMs, so Total 64GB) in quad-channel configuration.
      CPU: i7 6800k @4.0Ghz
      GPUs: GTX 1080 Ti and GTX 1060 3GB
      (each one a monitor, because I can't get DVI to run parallel with DP on the 1080Ti, and my second monitor only has DVI/VGA)
      OS: High Sierra 10.13.2 (17C88) / Clover revision: 4392
       
      Hello everybody,
      I occasionally have system crashes and suspect that it is related to RAM. However, this RAM is completely new, and a run with MemTest86+ from the USB stick showed no errors. However, if I use Memtest on MacOS, I get a bunch of error messages, but sometimes none (I restart the computer between tests).  
      As I just discovered, my RAM is not on the recommended vendor list of my motherboard, nor is it on the manufacturer side of the RAM. I have read several times that the RAM may not have been tested by the manufacturer on this platform. Not a single X99 motherboard is listed for this RAM.
      So I also suspect that my RAM is not compatible.
      But if that were the case, how could it sometimes work completely error-free?
       
      During RAM tests in summer 2017 (a slightly different setup, 4x8GB but still G.Skill Ripjaws V) I had no errors at Memtest under MacOS, if I remember correctly. At that time it ran under Sierra 10.12.6. AptioMemoryFix.efi could also cause problems.
      I am appreciative for any help!
       
      Here is an excerpt from a faulty test.
      It is noticeable that it is always the same address during the test, but a different one after each test.
      Memtest version 4.22 (64-bit) Copyright (C) 2004 Charles Cazabon Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port) Licensed under the GNU General Public License version 2 only Mac OS X 10.13.2 (17C88) running in multiuser mode Memory Page Size: 4096 System has 12 Intel core(s) with SSE Requested memory: 57232MB (60012990464 bytes) Available memory: 57232MB (60012990464 bytes) Allocated memory: 57232MB (60012990464 bytes) at local address 0x00000001033e1000 Attempting memory lock... locked successfully Partitioning memory into 2 comparison buffers... Buffer A: 28616MB (30006495232 bytes) starts at local address 0x00000001033e1000 Buffer B: 28616MB (30006495232 bytes) starts at local address 0x00000007ffc4d800 Running 1 test sequence... (CTRL-C to quit) Test sequence 1 of 1: Running tests on full 57232MB region... Stuck Address : ok Linear PRN : testing 7 of 16 FAILURE! Data mismatch at local address 0x0000000e88133d30 Expected Data: 0xc4c340079ac9a645, Actual Data: 0xc4c3400788468846 Running comparison tests using 28616MB buffers... Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : testing 80 of 256 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x4f4f4f4f4f4f4f4f, BUFB Data: 0x4f4f4f4f88468846 Checkerboard : testing 3 of 64 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x5555555555555555, BUFB Data: 0x5555555588468846 Bit Spread : testing 1 of 128 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000005, BUFB Data: 0x0000000088468846 Bit Flip : testing 74 of 512 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000200, BUFB Data: 0x0000000088468846 Walking Ones : testing 40 of 128 Clover Files attached
      config.plist
      drivers64UEFI.zip
      kexts.zip
      ACPI.zip
    • By BurpSuite
      screenshot:
       

       
      description:
      github: https://github.com/burpsuite/clover_theme
×