Jump to content
Welcome to InsanelyMac.com - No more ads! And some exciting news... Read more... ×
ErmaC

Clover problems report & features request

964 posts in this topic

Recommended Posts

Hi, about GUI too. If there's any dev could manage "volume_external_recovery.icns" to show correctly on boot screen. Specially useful for theme with OS badge.

 

Thanks  :) 

Share this post


Link to post
Share on other sites

the last clover 4313 as well as several revision before

do not see the apple icons after an install startosinstall method on the boot, he see an HD

Share this post


Link to post
Share on other sites

I understand nothing.

with the startosinstall method normally you have this icon in first boot 

os_mac10.png

and for some reason the last clover 4313 as well as several revision before

Clover do not see the apple icons  only this icons

vol_in10.png

Share this post


Link to post
Share on other sites

with the startosinstall method normally you have this icon in first boot 

os_mac10.png

and for some reason the last clover 4313 as well as several revision before

Clover do not see the apple icons  only this icons

vol_in10.png

Is it APFS? Or new OS revision has new boot.efi location? This icon is working but wrong picture?

Why it should be apple icon what the icon means?

Share this post


Link to post
Share on other sites

Is it APFS? Or new OS revision has new boot.efi location? This icon is working but wrong picture?

Why it should be apple icon what the icon means?

yes APFS  HS 10.13.1

IT must be an apple when he boot on macOS Install Data 

startosinstall method

 

captu109.png

Share this post


Link to post
Share on other sites

Too far from here  :(

I do not know which revision more recent than 4222 is correct?

Sorry  :blush:

edit***

Anyway its not really important, just remember that to it's an HD and not an apple

Share this post


Link to post
Share on other sites

I do not know which revision more recent than 4222 is correct?

Sorry  :blush:

edit***

Anyway its not really important, just remember that to it's an HD and not an apple

But what this icon should launch?

// OS X installer paths
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"
};

Or something else?

Share this post


Link to post
Share on other sites

But what this icon should launch?

// OS X installer paths
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"
};

Or something else?

Not sure but I think its this one

L"\\macOS Install Data\\Locked Files\\Boot Files\\boot.efi",

 

 

post-951341-0-94355800-1511382383_thumb.png

post-951341-0-06067500-1511382391_thumb.png

Share this post


Link to post
Share on other sites

 

the last clover 4313 as well as several revision before

do not see the apple icons after an install startosinstall method on the boot, he see an HD

 

 

Clover uses the generic Apple logo only when it doesn't know the OS version it is booting eg when a new OS X comes out or if a custom entry is used in config.plist without specifying a custom image file to use ...

 

post-846696-0-66505300-1511383783_thumb.png

post-846696-0-82443000-1511383884_thumb.png

 

Since Clover r4293, Clover correctly recognizes the OS version in the "macOS Install Data" folder by reading the SystemVersion.plist ---> fixed kext injection failing from /CLOVER/kexts/10.13 due to OS ver not being recognised.  This had the side-effect of now showing the correct OS ver icon/badge instead of the generic Apple logo before...

 

post-846696-0-78695700-1511384512_thumb.png

 

I think what you are wanting is actually a new feature request - a supplementary icon/badge beside the main icon when the loader entry type is OSXInstaller eg like the plus sign for OSXRecovery...

Share this post


Link to post
Share on other sites

Clover uses the generic Apple logo only when it doesn't know the OS version it is booting eg when a new OS X comes out or if a custom entry is used in config.plist without specifying a custom image file to use ...

 

 

 

Since Clover r4293, Clover correctly recognizes the OS version in the "macOS Install Data" folder by reading the SystemVersion.plist ---> fixed kext injection failing from /CLOVER/kexts/10.13 due to OS ver not being recognised.  This had the side-effect of now showing the correct OS ver icon/badge instead of the generic Apple logo before...

 

 

I think what you are wanting is actually a new feature request - a supplementary icon/badge beside the main icon when the loader entry type is OSXInstaller eg like the plus sign for OSXRecovery...

I do not want new future I just wanted the apple as before in High Sierra  :D

Since the first day High Sierra the apple was there for startosinstall method and its disappear :(

If you say that it was disappear because of the version stystem fix ; I did not know that now is the HS icons os_mac11.pngos_mac12.png

I was going to do without  :lol: I thought the apple was really connected to startosinstall method

Edit ****

@fusion71au thanks for the explanations and sorry @Slice for disturbing you with this.

I was blinding through the apple and I did not see that the version was well HS

Share this post


Link to post
Share on other sites

Any way to make Clover boot into macOS installer when update? When I click update & restart on App Store, Clover should boot into "macOS installer volume name" if Clover found it, if not Clover should continue boot into "macOS system volume name". That way make Clover Bootloader look like a real mac and more easier to set update

Share this post


Link to post
Share on other sites

I tried to install Clover on my desktop, to use its UEFI emulator to be able to boot Windows 10 on a GPT partitioned disk on a legacy BIOS motherboard (P6T Deluxe V2), but I am unable to get it to boot into Clover. I plan to dual boot Windows 10 and NixOS (a Linux distribution). Normally I use NixOS on my desktop, so I first created a disk image with Clover on it, by using the following script: https://github.com/m13253/clover-linux-installer

 

I ran this disk image via Grub2 and memdisk (from Syslinux) on my laptop (Asus UL30A), which worked fine. It took a while because my USB stick is very slow, but it did boot into Clover without any issue. I then installed Clover on my new desktop disk using the same script. Unfortunately all I got was an underscore in the top left of the screen. When I try to boot Clover from the same USB stick as I used for the laptop, it eventually just reboots. I then tried to boot the Arch Linux iso on my desktop with the same USB stick, Grub2 and memdisk, and that did work, so it probably has to do with the hardware configuration of my desktop compared to my laptop. I changed quite a lot in my BIOS settings of my desktop, so I tried resetting it to the defaults, but that had no effect, still no Clover.

 

Any ideas what I could do to make Clover work on my desktop? Are the others with similar hardware that ran into issues? Should I maybe use an older version of Clover?

 

For now I will go with my plan B, to format the disk with MBR, install Windows 10, reformat the partition table to GPT and boot into Windows via a memdisk loaded MBR drive image that contains Windows 10's boot files. This allows me to boot into Windows 10 on a GPT partition disk, but I'd rather use Clover instead of this workaround.

 

Some more info about my desktop's hardware configuration:

CPU: i7 920 2.67Ghz (normally overclocked to 3.6Ghz)

MB: Asus P6T Deluxe v2

Share this post


Link to post
Share on other sites

Any way to make Clover boot into macOS installer when update? When I click update & restart on App Store, Clover should boot into "macOS installer volume name" if Clover found it, if not Clover should continue boot into "macOS system volume name". That way make Clover Bootloader look like a real mac and more easier to set update

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.

Share this post


Link to post
Share on other sites

@Slice It is not that I have trouble booting Windows 10 with Clover, it is that I am unable to get Clover to show in the first place. I figure that I have to enable or disable some BIOS setting on my desktop, since the same setup works on my laptop.

Share this post


Link to post
Share on other sites

@Slice It is not that I have trouble booting Windows 10 with Clover, it is that I am unable to get Clover to show in the first place. I figure that I have to enable or disable some BIOS setting on my desktop, since the same setup works on my laptop.

Sounds like the boot order needs changing. If clover is installed properly you should be able to set that drive as first option in bios.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

@SavageAUS I did change the boot order after installing clover and used the "select boot device" popup at startup to boot into my USB stick, so I do not see how that could be the issue, but it was a good suggestion. I have searched quite a bit before posting here, but I have not found anything worthwhile to help me fix it, hence me posting here. I did found two people with the same hardware configuration with regards to the CPU and MB, so it should work in theory:

 

http://www.insanelymac.com/forum/topic/301376-complete-yosemite-on-x-powergtx480i7-920267/

http://www.insanelymac.com/forum/topic/329066-cant-boot-ubuntu-when-selecting-from-clover-on-legacy-triple-boot/

 

I am now going to try a preconfigured boot USB stick, to see if clover boots from there on my desktop:

https://www.aioboot.com/en/features/

Share this post


Link to post
Share on other sites

I tried AIO Boot, but when I run Clover from it, I get the same as before. I did however now notice a 7 showing up after about 2 seconds, which I assume is Clover telling me that it is using boot7 (Clover 64-bit with BiosBlockIO driver that works with any controller supported by the BIOS). However it just shows me the underscore in the top, no forced reboot, but I rebooted it myself after waiting a few minutes. I also tried pressing 6 at this two seconds pause, because it is stated that it will then boot in a different 64-bit boot loader, but I can press 6 however many times I want, it will still show me the 7 at the end of the 2 second interval.

Share this post


Link to post
Share on other sites

  • Similar Content

    • By 5T33Z0
      Background: Since the Pre-Release of Clover v5123, OpenCore Momory Fixes have been integrated into Clover in the form of OpenRuntime.efi. It replaces previous AptioMemory Fixes. Since v5126 AptioMemoryFixes are obsolete and no longer supported, so an upgrade to v5126 is mandatory in order to be able to install and boot macOS BigSur with Clover.
       
      This guide is for everyone trying to update to the latest Clover version or having issues while updating from previous versions, so they can install and run BigSur on their Machines. While updating to the latest iteration of Clover, there are several obstacles one can come across along the way. This guide is here to assist users trying to make the switch from the "old" Clover version with AptioMemory Fixes to the new one with OpenRuntime and Quirks Settings in CloverConfigurator.
       
      Problem: If you update your existing Clover installation by either installing the clover.pkg file or manually updating it the way you used to this will most likely result in an inoperable bootlader due to missing boot parameters.
       
      Approach: In order to avoid the dilemma of your system not wanting to boot, you have to know that the following files are obsolete and are no longer necessary, so they should eiither be disbabled/deleted when updating Clover from a built prior to v 5123 or omitted altogether when setting up a new EFI Folder:
       
      AptioMemoryFixes: AptioMemoryFix.efi, OsxAptioFix3Drv.efi, OsxAptioFixDrv.efi and everyhing else containing "memoryfix". Unnecessary Drivers (for UEFI-based Systems): DataHubDxe.efi – enables DataHub Protocol Support if it is missing from the BIOS. Modern UEFI BIOSes support this. So it's probably only necessary for Legacy Systems. FSInject.efi – For Kext-Injecttion. But pretty much obsolete since it's fully integrated in Clover nowadays. Might be necessary for Legacy Systems, though. SMCHelper.efi – Necessary when using FakeSMC.kext and ONLY FakeSMC. If you use it in combination with VirtualSMC.efi, it leads to an instant Kernel Panics. So, in other words: when using VirtualSMC – which is higly recommended over FakeSMC – DON'T use SMCHelper, use it in conjunction with VirtulSMC.efi (although unnecessary in most cases). EmuVariableUefi.efi – necessary for emulating NVRAM, if NVRAM is either not available (legacy systems) or working incorrectly. OcQuirks.efi and OcQuirks.plist – delete if present. OcQuirks is a relict from earlier attempts to include OpenCore Booter Quirks into Clover up until version 5122. Incompatible Kexts – wherever possible, you should use the latest available kexts provided by acidanthera (one of the devs behind OpenCore). Because incompatible Kexts are a source for Kernel Panics. I had an issue with my Laptop where VoodooPS2Controller.kext would cause a kernel Panic when used alongside VoodooPS2Mouse.kext, VoodooPS2Trackpad.kext and VoodooPS2Controller.kext. At the time I updated clover from 5122 to 5123, I didn't know that these 3 kexts are now includes as plugins inside of VoodooPS2Controller, so having them twice would cause a panic.

      In general, having Kexts wich have depedencies to oher kexts can cause a KernelPanic if not loaded in the correct order. In OpenCore, you can and have to set up the correct loading order of kexts manually by yourself, but in Clover only a few essential kexts like Lilu and Fake/VirtualSMC are hard-coded in, so they are always loaded first. It took me a while to figure this out. So when you update Clover and you are using lot of Kexts (usually on Laptops), try to update all Kexts first using Kext-Updater which is incredibly useful tool to download all sorts of bootloader-related files, have a look inside of them so see if they include more kexts as plugins and make sure nothing is present twice – HID, Wifi and Bluetooth kexts come to mind here. If you get panics you can not isolate, just move all unnecessary kexts to the "off" folder to temporarily to work around the issue by starting with a minimal set up to get the system running. Then put the disabled kexts back one by one to find the culprit for the panic.  
      Updating your EFI
       
      Prepare an USB Stick. Format it to FAT32 (MBR). We'll use it for testing our updated EFI Folder first, before copying it to the ESP on the HDD. Download the latest Clover Release  as a .zip archive for a manual update (currently "CloverV2-5126.zip"): https://github.com/CloverHackyColor/CloverBootloader/releases Extract the .zip. We'll create our EFI based on the one insides of it. Have a look at the "EFI > Clover > drivers > off > UEFI" Folder – you find the following Files: Copy the following files over to EFI > Clover > drivers > UEFI: ApfsDriverLoader.efi, VBoxHfs.efi and OpenRuntime.efi Now we have a minimal set of Drivers which looks like shown below. The files tagged in gray are in the drivers Folder by defautl and are most likely unnecessary on UEFI-based systems. As mentioned earlier, SMCHelper MUST be deleted when using VirualSMC.kext! I would turn of each of the gray drivers one by one and chick if the system still boots without them.
      Next, copy over your kexts (updated to the latest available version, of course), your ACPI > patched folder and your config.plist form your existing EFI Folder Open CloverConfigurator and update it to the latest Version. It should now include a new section at the bottom called Quirks, as mentioned earlier Now open your config.plist you copied over from your working EFI and click on "Quirks". It should look like this (without the descriptions of course):
      Head over to the OpenCore Install Guide and pick the guide for your CPU Family and Platform. Jump to the "Booter" Section. It contains all required Booter Quirks tinted green in the screenshot. Make sure to unfold the "more in-depth info" box to see what they do. Find the options for your system and tick them away in Clover Configurator. Next, jump to the "Kernel" section of Dortania's guide and copy over the settings from "Quirks" and "Scheme". Again, make sure to unfold the "more in-depth" section to find all necessary settings. NOTE: some of the settings Located in "Kernel > Quirks" have different names and are located in the "Kernel and Kext Patches" section of Clover Configurator. These include:

      In most cases you have these set up correctly already, otherwise your system wouldn't have started before. But it's good to double check if you have settings enabled which may be unnecessary. Once you've ticked all the necessary quirks, save your configuration, copy the new EFI Folder to the root of your USB Flash Drive and try booting from it. If everything was set up correctly, the system should boot as expected. If it does boot, you can mount the ESP partition of your hard drive, backup your EFI Folder, delete it and put in the one from your USB Flash drive to make the changes permanent.  
      TROUBLESHOOTING: If you get Kernel Panics take a note of them and head over to the OpenCore Troubleshooting Guide and have a look at the "OpenCore Boot issues" and "Kernelspace Issues" sections to find your error message and possible fixes to resolve it. Another great resource to check if your Clover config is set-up correctly in general (excluding Quirks) is the Hackintosh Vanilla Desktop Guide For more info about how OpenCore differs from clover and see which settings, drivers and features are compatible, check out the Clover Conversion Guide.
       
      Good luck!
       
      PS: If you run into trouble after following this guide you can upload your config.plist and I can have a look at the quirks.
      PSS: When running BigSur, you need to remove the PreBoot Volume from the "Hide" Section of the GUI because if I understand correctly, BigSur requires booting from it.
      PSSS: if your system boots correctly you can upload a screenshot with your quirks with additional Info like your Board and CPU which might be helpful for other users.
       
    • By MaLd0n
      iMac20,1 Hackintosh 
      A good build for professional audio and video processing.
      We love silence and Cooler SCYTHE Ninja 5 is mandatory in this case!
      A very custom DSDT for best experience under macOS. Removed all unused devices, injected all Apple devices, essentials, cosmetics, real improvements.
       
       

       
       
      -OpenCore Vanilla TUTORIAL-
       
       
      -USB Port Mapping TUTORIAL-
       
       
      -Bios/UEFI Settings-
      CSM Support - Disabled
      Internal Graphics - Enable
      -Thunderbolt Configuration-
      Security Level - No Security
      GPIO3 Force Pwr - Enabled
       
      -Hardware-
      Mobo - Ga Z490 Vision D
      https://tinyurl.com/y4gajha4

      Processor - i7 or i9 10th Intel
      https://tinyurl.com/y6jlskwz

      GPU - RX 580, 590, VEGA 56, VEGA64, 5700XT or RADEON VII
      https://tinyurl.com/y4mxc7t6

      Cooler - SCYTHE Ninja 5 
      https://tinyurl.com/yyrbx5lf

      NVME - WD Black SN750 NVMe SSD
      https://tinyurl.com/vnq46yr
       
      -EFI folders- 
      Clover - https://tinyurl.com/yxzftuyr
      OpenCore - https://tinyurl.com/y3lt8t9l
      Just paste EFI folder into EFI partition, reboot and extract one SendMe. Post this dump here for full ACPI solution!
      Download RunMe.app dumper
       
      -If you want to buy me a beer - Donations with PayPal
      https://tinyurl.com/r2bvzm7
       
      -DSDT- Complete Solution
      DSDT.Z490 VISION D MaLd0n.zip
       
      -SSDT- Not complete solution
      SSDT-OLARILA.aml.zip
       
      -DSDT Patches-
       
       
       
      -USB Solution-
      USB SOLUTION.zip
       
       
       
       
      -Boot Time with Clover or Opencore is same-
       
      -Screenshots-































       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thx to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!

      We're all here to have fun and learn from each other!
    • By VortexisTV
      So I've been trying to update to Big Sur from Catalina but I get stuck at the +++ message at the beginning. I made sure I have all my kexts and drivers updated. Updating to Clover revision 5126 would only get me kernel panics. Am I doing something wrong? Any response would be greatly appreciated. EFI
       
      ASUS Zenbook UX331FN
      Intel Core i5-8265U
      Intel UHD 620
      Clover 5120
       

    • By amadeusex
      Hey guys - how are you holding up?
      Because of a lot of free time and after abandoning the idea to get Catalina installed i tried to run Mojave on my beloved z820v2.
      Everything went fine except power management.
      I've used @WoodCabin's EFI folders to install and later on run Mojave (14.6).
      Here's a glimpse of what i get as soon as i put the patched (from 10.13 as suggested on stinga's X79 power management topic) AppleIntelCPUPowerManagement.kext into S/L/E
       

       
      I tried also @stinga11 s kext patches for Mojave but still either PM's not working or KP.
      Here's my my EFI folder

      @antonio.clb
    • By MaLd0n
      -OpenCore Vanilla TUTORIAL-
       
       
      -USB Port Mapping TUTORIAL-
       
        1 -Create a USB bootable
       
      Create your usb installer, use this tool and download Catalina or Big Sur from Apple servers
       
      Catalina
      installScript_allfullapp.zip
       
      Big Sur
      installScript_1016fullapp.zip
       
      Credits: crazybirdy
       
      Copy Catalina / Big Sur installer to Applications folder, open terminal and run
       
      Catalina
       
       
      Big Sur
       
       
      If you want check one step by step, check here
       
      -Opencore Vanilla Tutorial
      https://tinyurl.com/ycvcnp8h
       
      2- EFI folder USB installation
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/y6avuxsv
       
       
      3- EFI folder SSD
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD 
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD
      https://tinyurl.com/y6avuxsv
       
      4- Start Fine Tune
       
      Run this app and post full dump here for full ACPI solution
       
      RunMe.app
      https://tinyurl.com/y9562hz7
       
       
      If you like a SSDT way, here we go
      SSDT-OLARILA.aml.zip
       
      5- USB Solution
      USB INTEL SERIE 400.zip
       
      Use these kexts, enable XHCI port limit patch and follow this tutorial for remap USB ports
       
       
       
      --DSDT PATCHES--
       
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE ID -DMAC -REMOVE LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM -REAL TIME CLOCK -SLPB -DARWIN / WINDOWS -XHCI -PLUGIN TYPE -HDEF -ARTC -IPIC -TIMR -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -kUSBCompanionIndex -io-device-location -IMEI -EC -PNLF -ARPT -GFX0 -NVME -ACPI-WAKE-GPE -DTGP -HDMI / HDAU  
      --SCREENSHOTS--































      -If you want to buy me a beer - Donations with PayPal
      https://tinyurl.com/r2bvzm7
       
      Big Thanks to XLR and your Badass Motherboard, Ultrafast CPU, Coolest Heatsink, Huge Graphics Card, Tonnes of RAM,
      Gigantic Hard Drive, Lightspeed Disk Burner, Professional Sound Card, Massive LCD Display.
       
       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!

      We're all here to have fun and learn from each other!
×