Jump to content
InsanelyMac Forum
ErmaC

Clover General discussion

Recommended Posts

oh sorry, you said:

"i don't have graphics at all" and I thought this appen with Clover (no QE/CI

at all), .......perhaps I misunderstood.

 

only 2 thing, the string in the config.plist is property converted to BASE64, and maybe you have to remove your custom override file in S/L/D/O, using the Clover injection?

 

bye

Share this post


Link to post
Share on other sites
Advertisement

Thz Michele ...now try to edited again ...you know key for my sandy bridge 2700k ?

For edited key cpu ?

something like this:

 

<key>CPU</key>
<dict>
<key>Turbo</key>
<string>Yes</string>
<key>ProcessorType</key>
<string>0x0601</string>
<key>CpuFrequencyMHz</key>
<string>3500</string>
<key>BusSpeedkHz</key>
<string>99800</string>
<key>QPI</key>
<string>5000</string>
</dict>
</plist>

 

http://ark.intel.com/products/61275/

 

2700k-idle.jpg

 

but this is really unnecessary, Clover already know everything for CPUs, risk if there is any value busted, so do not use it!!!!!!

 

Micky

 

 

Edit

 

do not know if only this can be inserted, to make appear in System Profiler:

 

<key>CPU</key>
<dict>
<key>QPI</key>
<string>5000</string>
</dict>
</plist>

 

better to ask ErmaC or Slice

Share this post


Link to post
Share on other sites

He know how to manipulate EDID, but the problem is that needs to work in Clover, without customedid files in

S/L/D/O,

the goal is that, in this topic :wink2:

 

sorry, didn't follow his real intentions :(

Share this post


Link to post
Share on other sites

Does this bootloader works (now) with an ASUS UEFI MB?

Yes. Works without issues at my ASUS P8P67-M board in legacy BIOS boot mode (BIOS -> boot0 -> boot1 -> boot -> CloverX64.efi -> OSX) and in UEFI mode (UEFI -> CloverX64.efi -> OSX).

 

More info about UEFI boot here: http://www.projectos...?showtopic=2428

And some kind of a guide here: http://www.projectos...682

Share this post


Link to post
Share on other sites

Yes. Works without issues at my ASUS P8P67-M board in legacy BIOS boot mode (BIOS -> boot0 -> boot1 -> boot -> CloverX64.efi -> OSX) and in UEFI mode (UEFI -> CloverX64.efi -> OSX).

 

More info about UEFI boot here: http://www.projectos...?showtopic=2428

And some kind of a guide here: http://www.projectos...682

Thanks! :)

 

Going to test it, seems to be difficult, but I would like to use the UEFI-mode on OS X.

Share this post


Link to post
Share on other sites

hello

 

yes i have graphics and working ok, like in chameleon, but what i want is inject the edid by clover in config file, and not use the file in s/l/d/o

 

because in updates, if change anything is this folder, i must edit again the file with the custom edid.

 

anyway thanks for u contribution.

 

Clover is a child, but very good job in another boot loader.

 

must give time to slice to see all the little issues in the code.

 

good hack

Share this post


Link to post
Share on other sites

Yes, I know,

 

it's nice to hope that system continues working after each update, this is even more cool, especially now that Apple do Updates "only copy the updated parts"!

this way is the best!!!

Share this post


Link to post
Share on other sites

First try:

1. Created latest pkg with CloverGrower

2. Format USB-stick in OS X with Disk Utility > MBR > 1 partition > FAT32 > Named: DUET

3. Install pkg to USB-stick with the given options

4. Copied DSDT to the EFI/ACPI/patched folder

5. Boot USB in Bios-mode

 

The above steps are working, I can boot with Clover and run OS X without any problem.

 

UEFI-booting is not working:

1. Run the installer again, but now selected the Drivers64 as option

2. After installation, copied the files inside Drivers64 to Drivers64UEFI

3. Copied Files/HFSPlus/x64/HFSPlus.efi to usb Drivers64UEFI/HFSPlus-64.efi

Files inside Drivers64UEFI:

FSInject-64.efi

HFSPlus-64.efi

OsxAptioFixDrv-64.efi

OsxFatBinaryDrv-64.efi

 

Tried to reboot with UEFI mode, see the Clover menu, select OS X Volume, but hang. (See image)

 

EDIT: Replaced HFSPlus-64.efi with VboxEFI from this post. It boots.. but hangs on the message Loading drivers ..........

EDIT2: Found this topic (http://www.projectosx.com/forum/index.php?showtopic=2428) seems to be issues with my MB

 

Hope someone can help! Thanks a lot!

post-326232-0-47354000-1348481164_thumb.jpg

Share this post


Link to post
Share on other sites

I use the volume GUID. So for example, here's mine:

 

You can get the GUID of each volume by checking your Clover bootlog.

Or easier still, run DarwinDumper and select the Disk Volume UUID & GUID option.

 

No use... Partitions still can't be hidden.

 

This is what I've done in the config.plist:

<key>Volumes</key>
<dict>
<key>HideAllLegacy</key>
<string>Yes</string>
<key>HideVolumes</key>
<dict>
<key>0</key>
<dict>
<key>VolumeString</key>
<string>44171289-EC4C-4B98-8234-B0AD0364A317</string>
</dict>
<key>1</key>
<dict>
<key>VolumeString</key>
<string>D243A418-64CD-4E2D-89E3-410057EA815C</string>
</dict>
<key>2</key>
<dict>
<key>VolumeString</key>
<string>2476444A-F2CC-4877-814D-0624A4432237</string>
</dict>
<key>3</key>
<dict>
<key>VolumeString</key>
<string>BA1F5552-B72B-430F-A0D1-7C25FE07AAA1</string>
</dict>
</dict>
</dict>

 

-Problem sloved by updateing clover-

Share this post


Link to post
Share on other sites

UEFI-booting is not working:

...

 

You are fast. I think you should not have any problems with UEFI boot on your mobo.

 

Notes:

 

1. If UEFI booting ML with OsxAptioFixDrv driver, you MUST add slide=0 in config.plist in boot args

 

<key>boot-args</key>

<string>-v slide=0</string>

 

2. You can use the same stick for BIOS Clover boot and UEFI boot. The Clover setup difference between BIOS and UEFI boot for me is only in drivers. BIOS Clover boot will use drivers from /EFI/Drivers64/ and UEFI Clover boot will use /EFI/Drivers64UEFI/.

 

3. For BIOS Clover boot you probably do not need any drivers. So /EFI/Drivers64 can be empty. You can add FSInject-64.efi in there if there is a need to block kernelcache and load with kernel+kexts.

 

4. For UEFI Clover boot you need in /EFI/Drivers64UEFI:

- some HFS+ driver (HFSPlus.efi or VBoxHFS.efi) - to allow Clover to read HFS+ volumes

- OsxFatBinaryDrv-64.efi - to add support for fat binary (multi-architecture binaries) .efi files (Apple's boot.efi is such file)

- OsxAptioFixDrv-64.efi - to overcome some UEFI memory problems on our mobos

- optionally FSInject-64.efi

 

Do not forget slide=0. Good luck.

 

Edit:

5. If UEFI booting from FAT32 USB stick, you can boot directly to Clover by copying /EFI/Boot/CloverX64.efi into /EFI/Boot/BootX64.efi. BootX64.efi is default app that will be started when the stick is selected for UEFI boot.

Share this post


Link to post
Share on other sites

...

Thanks for your post. I have done everything you listed above.

Unfortunately it is still hanging.

 

I can see Clover and can select the OS X partition at the menu. When hit Enter, it loads but displays (the same error):

Error loading kernel 'mach_kernel' (0x9)

Error: Aborted returned from boot.efi

 

Thanks, hope you can help.

Share this post


Link to post
Share on other sites

I can see Clover and can select the OS X partition at the menu. When hit Enter, it loads but displays (the same error):

Error loading kernel 'mach_kernel' (0x9)

Error: Aborted returned from boot.efi

Are you booting Mountain Lion? Are you sure you have slide=0 added? Is there maybe additional config.plist somewhere on your stick or EFI partition with different settings?

You can check for this slide=0 by starting Clover and then pressing letter 'O' - slide=0 should appear in boot args.

Share this post


Link to post
Share on other sites

Are you booting Mountain Lion? Are you sure you have slide=0 added? Is there maybe additional config.plist somewhere on your stick or EFI partition with different settings?

You can check for this slide=0 by starting Clover and then pressing letter 'O' - slide=0 should appear in boot args.

Going to try again, thanks.

 

UPDATE: Fixed by apianti. Removed OsxLowMemFixDrv-64.efi and added slide=0 fixes the problem.

Drivers64UEFI contents:

DataHubDxe-64.efi
FSInject-64.efi
HFSPlus-64.efi (renamed HFSPlus x64)
OsxAptioFixDrv-64.efi
OsxFatBinaryDrv-64.efi
PartitionDxe-64.efi

 

config.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
   <key>ACPI</key>
   <dict>
       <key>DropOemSSDT</key>
       <string>Yes</string>
       <key>GenerateCStates</key>
       <string>Yes</string>
       <key>GeneratePStates</key>
       <string>Yes</string>
       <key>EnableC6</key>
       <string>No</string>
       <key>EnableC4</key>
       <string>No</string>
       <key>EnableC2</key>
       <string>Yes</string>
       <key>EnableISS</key>
       <string>Yes</string>
   </dict>
   <key>Graphics</key>
   <dict>
       <key>GraphicsInjector</key>
       <string>Yes</string>
       <key>LoadVBios</key>
       <string>Yes</string>
   </dict>
   <key>SystemParameters</key>
   <dict>
       <key>boot-args</key>
       <string>slide=0</string>
       <key>prev-lang:kbd</key>
       <string>en:0</string>
       <key>DefaultBootVolume</key>
       <string>Macintosh HD</string>
       <key>CustomUUID</key>
       <string>***</string>
   </dict>
   <key>SMBIOS</key>
   <dict>
       <key>FirmwareFeatures</key>
       <string>0xC0001403</string>
   </dict>
</dict>
</plist>

 

Thanks for the help.

Share this post


Link to post
Share on other sites

Is there an option to change the smbios to MacPro5,1? I have searched on FirmwareFeatures and the given string 0xC001F537, but found nothing.

 

Thanks,

Share this post


Link to post
Share on other sites

How can I make clover to boot windows?

 

Also, how can I make clover boot windows dvd?

It showed "cdboot cannot boot from cd - code 4" while I was trying to install from windows dvd.

Share this post


Link to post
Share on other sites

How can I make clover to boot windows?

Legacy boot may work, may no. If NO then sorry.

UEFI boot works.

Also, how can I make clover boot windows dvd?

It showed "cdboot cannot boot from cd - code 4" while I was trying to install from windows dvd.

Clover has no UDF driver. Sorry, impossible.

Copy the DVD on USB stick and use it.

Share this post


Link to post
Share on other sites

Legacy boot may work, may no. If NO then sorry.

UEFI boot works.

 

Clover has no UDF driver. Sorry, impossible.

Copy the DVD on USB stick and use it.

Get it, thanks for reply! :)

Share this post


Link to post
Share on other sites

Are you booting Mountain Lion? Are you sure you have slide=0 added? Is there maybe additional config.plist somewhere on your stick or EFI partition with different settings?

You can check for this slide=0 by starting Clover and then pressing letter 'O' - slide=0 should appear in boot args.

hi dmazar.

It seems to be a little rude to talk to you this way.

But I dont know if you have seen the feedback I already told you.

The restart function works fine. But the countdown is not working using your method of adding

panic_restart_timeout=10

Share this post


Link to post
Share on other sites

Thank you, Fabio! I will apply your additions.

But about code formatting see, please, rules by Tiano: https://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Code_Style/C

CamelCase used for variables, functions and file names
UPPERCASE used for types and macros
Use UEFI types rather than C types
int=>INTN; unsigned int=>UINTN; void=>VOID; etc...
Limit line length to 80 characters
2 spaces of indentation
Never use tab characters.
Set editor to insert spaces rather than a tab character.
if, for, while, etc. always use { }, even when there is only one statement
The opening brace ({) should always appear at the end of the line previous line.
The opening brace ({) for a function should always appear separately on the a new line.

Share this post


Link to post
Share on other sites

Is there a trick to getting Clover to use the config.plist? I can boot with Clover just fine but, I keep having to change the Graphics Injection to off, and I would like to use a 12,2 definition instead of the 12,1 that it's detecting.

 

config.plist.zip

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 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
×