Jump to content
InsanelyMac Forum
Micky1979

Build_Clover.command, another Script to build standard Clover (or customized)

Recommended Posts

Advertisement
9 hours ago, vector sigma said:

Do you mean that below cmd does'nt work?


cp -R "${DIR_MAIN}"/edk2/Clover/Patches_for_EDK2/* "${DIR_MAIN}"/edk2/

here works good, but this is right from @SavageUS?


The current local EDK2 revision is the suggested one (26300).

should not be r26767 like mentioned by this guy?

Working with Slice's HWMonitor on sf is a pain as well  maybe is just sourceforge.. I also see that Aptiofix is already synced with a git reposytory, maybe you guys can you just do the same with edk2.

Well I just tested it by reverting my local copy of the EDK2 to it's original state and I got those errors that were being posted. I copied Patches_for_EDK2 to EDK2 dir, they disappeared because it built (besides one error that I fixed, unsure how anyone was building but ok). Then I reverted again then updated to the newest EDK2 commit, got build errors again. Recopied the patches, and it built. So yes if you are getting those errors it's because the patches were not copied. Maybe you might want to add the -f flag to copy so that it forcibly overwrites the files, just in case? Or maybe see if the result of the return from cp is an error because it failed? I don't know what you mean about AptioFix being synced, it is not. That is an external dependency just like EDK2, and is basically AptioFix3 with some added stuff that were basically what I had been saying should happen, no one listened and argued with me a bunch. Then decided that it should behave that way and wrote it separately from clover because that was easier to maintain.... I constantly have to remove it to properly build because either the repo can't update because its down (I have way more trouble with most stuff on github than I've ever had at SF, which is why I don't think the problem is truly SF, but then again I live like right by one of the main servers so it may be a proximity/routing thing) or because the code is broken and won't build. Which is why I didn't want it as an external dependency but I was overruled by Slice because I'm assuming he didn't want to have to constantly maintain packporting the fix into clover. Since even though I give anyone who asks and has demonstrated any ability to code the chance to at least have an opportunity to submit commits, I apparently wouldn't allow AptioFix to be updated (with my own ideas, mind you) by anyone else. Which is complete {censored} because no one ever asked to submit code ever, not once. Seems more like an opportunity to steal other people's work and pass it off as there own.... Which whatever, I don't really care. Recognition is like being constantly shot in the face with a fire hose, it's fun for about one millisecond, and then your head is being blasted with a fire hose....

Share this post


Link to post
Share on other sites
Posted (edited)

Hi Sir apianti, I'm sorry but I cannot understand what you mean or referring to AptioFix stories, but me at least, I was only referring on how the script (as per title of the topic) checkout/update AptioFix from github into a svn one and I was wondering if this can be done with edk2 ...and get rid of sourceforge. No some thing else. About the copy of the patches.. how this cannot work? cp in -R mode continue copying even on errors, so that I agree with -f, but errors are printed to the stdout and this is not the case. Those errors only happened to me when patches for edk2 inside Clover aren't good for the local revision of edk2 itself why I showned you this:

The current local EDK2 revision is the suggested one (26300).

Sir Zenith432 committed new patches compatible with newer r26764 but the guy who showned a fail on the log was using 26300.

So, if you revert edk2, don't forget to revert Clover as well, otherwise errors for sure. You know, simply that. 

EDIT
unless you are talking about reverting edk2 to the same revision but untouched:D. Anyway mentioned cp command is inside clover() func, so to apply patches you have to ensure to update clover with an option of that script. So yes if you cannot update Clover because sf is down, patches cannot be applied but anyway are the old one. Speaking by using this script ^_^

EDIT II

maybe you have to move the cp command outside this function, or eventually have this code in ebuild.sh.

Edited by vector sigma
spelling

Share this post


Link to post
Share on other sites
5 hours ago, vector sigma said:

Hi Sir apianti, I'm sorry but I cannot understand what you mean or referring to AptioFix stories, but me at least, I was only referring on how the script (as per title of the topic) checkout/update AptioFix from github into a svn one and I was wondering if this can be done with edk2 ...and get rid of sourceforge. No some thing else. About the copy of the patches.. how this cannot work? cp in -R mode continue copying even on errors, so that I agree with -f, but errors are printed to the stdout and this is not the case. Those errors only happened to me when patches for edk2 inside Clover aren't good for the local revision of edk2 itself why I showned you this:


The current local EDK2 revision is the suggested one (26300).

Sir Zenith432 committed new patches compatible with newer r26764 but the guy who showned a fail on the log was using 26300.

So, if you revert edk2, don't forget to revert Clover as well, otherwise errors for sure. You know, simply that. 

EDIT
unless you are talking about reverting edk2 to the same revision but untouched:D. Anyway mentioned cp command is inside clover() func, so to apply patches you have to ensure to update clover with an option of that script. So yes if you cannot update Clover because sf is down, patches cannot be applied but anyway are the old one. Speaking by using this script ^_^

EDIT II

maybe you have to move the cp command outside this function, or eventually have this code in ebuild.sh.

No, I had the patches copied over and had to revert the EDK2 repo to its original state. The revision actually matters very little, not as much as made out to be, sometimes when there are large changes to one of the headers or something there is an issue but most of the time it's fine because it overwrites the entire file, not just patch it. You only need the patches if you are building the firmware, the GUI alone shouldn't need the patches but then you have to specifically build each module. Which I doubt the script does. The script can definitely be changed to use the git repo, it's not my script, and was my initial point, switch to the github repo of EDK2 and you will probably have less issues.

Share this post


Link to post
Share on other sites

can't the edk repo just be changed in the BuildCloverConfig.txt on line 16

EDK2_REP=svn://svn.code.sf.net/p/edk2/code/trunk/edk2

or is there more to it then just that?

Share this post


Link to post
Share on other sites
27 minutes ago, bronxteck said:

can't the edk repo just be changed in the BuildCloverConfig.txt on line 16

EDK2_REP=svn://svn.code.sf.net/p/edk2/code/trunk/edk2

or is there more to it then just that?

No it's more than that as the commands would need to be switched to use git instead of subversion. It would also require removing any working copy.

Share this post


Link to post
Share on other sites
Posted (edited)
8 hours ago, bronxteck said:

can't the edk repo just be changed in the BuildCloverConfig.txt on line 16

EDK2_REP=svn://svn.code.sf.net/p/edk2/code/trunk/edk2

or is there more to it then just that?

 

7 hours ago, apianti said:

No it's more than that as the commands would need to be switched to use git instead of subversion. It would also require removing any working copy.

I'm confident that this:

EDK2_REP=https://github.com/tianocore/edk2/trunk

in BuildCloverConfig.txt will work as expected :D. Just need a clean src the first time. Bye bye sourceforge... now we need Clover on github..

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)

I suspected such sync issues may occur.

Migrating all the repos to git would require a major change in the source code versioning and I think that's up to @Slice to decide.

Edited by Philip Petev

Share this post


Link to post
Share on other sites

Hi Sir Philip Petev, of course yes. About the revision,by calling:

Build_Clover.command --edk2rev 36852

everything went fine, but can we assume that differences is always the same?? 

Share this post


Link to post
Share on other sites
Posted (edited)
4 minutes ago, vector sigma said:

Hi Sir Philip Petev, of course yes. About the revision,by calling:


Build_Clover.command --edk2rev 36852

everything went fine, but can we assume that differences is always the same?? 

The only way to be sure is to svn-checkout both the git and the SF repos in different folders and compare them with visual diff tool like Kaleidoscope. If they are identical, you won't see any occurrences when you load them in the app.

Edited by Philip Petev

Share this post


Link to post
Share on other sites
Posted (edited)
10 minutes ago, Philip Petev said:

The only way to be sure is to checkout both the git and the SF repos in different folders and compare them with visual diff tool like Kalleidoscope.

IMHO, is just the revision that comes with sf that is missleading, main repo is on github. I mean that if Slice will decide to use:

https://github.com/tianocore/edk2/trunk

instead of 

svn://svn.code.sf.net/p/edk2/code/trunk/edk2

then the rivision will be just the latest he wants to be ha ha. He just need to checkout new modules with new url. Is always a svn repo and have to do this only once and syntax He's using will be always the same (i.e. He can continue to use ~/src/edk2/Clover/update.sh)

Edited by vector sigma
spelling

Share this post


Link to post
Share on other sites
Posted (edited)

There is no reason to need to continue with any revision for EDK2, it is only used to update the patches, which is why at some point there is a "suggested" revision. However, the git and svn repos are identical, except that the svn repo constantly syncs with the git repo. Clover v2 repo won't be changing git, just the script using git for EDK2, it still would need to use subversion for Clover. And if you do switch to git for the EDK2 repo you'll have to make sure the entire working copy is erased to pull from the git repo or you'll run into issues.

EDIT: Also I switched to the git EDK2 repo a long time ago when the svn repo switched to syncing instead of direct commits. Never had an issue.

Edited by apianti

Share this post


Link to post
Share on other sites
25 minutes ago, apianti said:

make sure the entire working copy is erased to pull from the git repo or you'll run into issues

yeah, just compare each packages by doing the following (in this case BaseTools):

cd ~/src/edk2/BaseTools
svn info . | grep '^URL'

then if the output is not "URL: ${EDK2_REP}/BaseTools" you'll have delete it and checkout it again.

 

Share this post


Link to post
Share on other sites
Posted (edited)

SF is out for lunch... again.

Edit: guys, take a look at this:

Spoiler

================================================================================
boot6
                             <--------------------------------------------------
TOOLCHAIN_DIR: /Users/philip/src/opt/local
MTOC_PREFIX: /Users/philip/src/opt/local/bin/
NASM_PREFIX: /Users/philip/src/opt/local/bin/
NASM_VER: 2.13.03
Building from: /Users/philip/src/edk2

Running edk2 build for CloverX64 using the command:
build  -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/philip/src/edk2/Conf -D USE_LOW_EBDA -p Clover/Clover.dsc  -a X64 -b RELEASE -t XCODE8 -n 9

Build environment: Darwin-16.7.0-x86_64-i386-64bit
Build start time: 22:24:40, Apr.02 2018

WORKSPACE        = /Users/philip/src/edk2
ECP_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EDK_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EFI_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /Users/philip/src/edk2/BaseTools
CONF_PATH        = /Users/philip/src/edk2/Conf


Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE8

Active Platform          = /Users/philip/src/edk2/Clover/Clover.dsc
Flash Image Definition   = /Users/philip/src/edk2/Clover/Clover.fdf

Processing meta-data ..

build.py...
/Users/philip/src/edk2/MdePkg/Library/BaseLib/BaseLib.inf(452): error 000E: File/directory not found in workspace
    /Users/philip/src/edk2/MdePkg/Library/BaseLib/X64/WriteTr.nasm


- Failed -
Build end time: 22:24:44, Apr.02 2018
Build total time: 00:00:04


o_Ops, ./ebuild.sh exited with error(s), aborting..

That's clean source download (no ~/src/edk2) from the GH repo.

Edited by Philip Petev

Share this post


Link to post
Share on other sites
11 hours ago, vector sigma said:

yeah, just compare each packages by doing the following (in this case BaseTools):


cd ~/src/edk2/BaseTools
svn info . | grep '^URL'

then if the output is not "URL: ${EDK2_REP}/BaseTools" you'll have delete it and checkout it again.

 

No, if you switch to a git repo from using subversion repo, you need to erase the entire working copy. They are completely different tools and hold the commits in different ways, they cannot be checked out into the same directory. In fact git usually refuses to checkout into a non empty directory without flags and also if I recall correctly also complains that its already being tracked by subversion. You can however convert it to git but that won't help you because you want to have the remote git repo's commits/history, not create a new one.

7 hours ago, Philip Petev said:

SF is out for lunch... again.

Edit: guys, take a look at this:

  Hide contents

================================================================================
boot6
                             <--------------------------------------------------
TOOLCHAIN_DIR: /Users/philip/src/opt/local
MTOC_PREFIX: /Users/philip/src/opt/local/bin/
NASM_PREFIX: /Users/philip/src/opt/local/bin/
NASM_VER: 2.13.03
Building from: /Users/philip/src/edk2

Running edk2 build for CloverX64 using the command:
build  -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/philip/src/edk2/Conf -D USE_LOW_EBDA -p Clover/Clover.dsc  -a X64 -b RELEASE -t XCODE8 -n 9

Build environment: Darwin-16.7.0-x86_64-i386-64bit
Build start time: 22:24:40, Apr.02 2018

WORKSPACE        = /Users/philip/src/edk2
ECP_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EDK_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EFI_SOURCE       = /Users/philip/src/edk2/EdkCompatibilityPkg
EDK_TOOLS_PATH   = /Users/philip/src/edk2/BaseTools
CONF_PATH        = /Users/philip/src/edk2/Conf


Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE8

Active Platform          = /Users/philip/src/edk2/Clover/Clover.dsc
Flash Image Definition   = /Users/philip/src/edk2/Clover/Clover.fdf

Processing meta-data ..

build.py...
/Users/philip/src/edk2/MdePkg/Library/BaseLib/BaseLib.inf(452): error 000E: File/directory not found in workspace
    /Users/philip/src/edk2/MdePkg/Library/BaseLib/X64/WriteTr.nasm


- Failed -
Build end time: 22:24:44, Apr.02 2018
Build total time: 00:00:04


o_Ops, ./ebuild.sh exited with error(s), aborting..

 

I have been using SF all day and haven't had one problem, lol.

7 hours ago, Philip Petev said:

That's clean source download (no ~/src/edk2) from the GH repo.

What do you mean? I use the GH git repo for EDK2, and the SF svn repo for Clover, in multiple OSes and it works perfectly fine. Just built with newest commits from each repo, works great...?

Share this post


Link to post
Share on other sites
Posted (edited)
8 hours ago, apianti said:

No, if you switch to a git repo from using subversion repo, you need to erase the entire working copy. They are completely different tools and hold the commits in different ways, they cannot be checked out into the same directory. In fact git usually refuses to checkout into a non empty directory without flags and also if I recall correctly also complains that its already being tracked by subversion. You can however convert it to git but that won't help you because you want to have the remote git repo's commits/history, not create a new one.

We are saying a similar thing of Just checking if the repo is not the same, then you can erase it or not. But me I'm talking by using "svn co" on github not git, otherwise you can ignore me :)

16 hours ago, Philip Petev said:

That's clean source download (no ~/src/edk2) from the GH repo.

Wrong revision of edk2 (probably is old), take latest or use r36852 as I already tried. EDIT: just for testing purpose, assuming you're using github.

Edited by vector sigma

Share this post


Link to post
Share on other sites
Posted (edited)

My point was subversion counts the revisions in the git repo the wrong way. Trying to pull out the latest preferred revision (r26764), subversion downloaded unusable copy (probably another revision), so changing the edk2 url with the GH repo doesn't work, at least no as it should be.

And the latest revision works only because nothing has been changed much (or at all) in the files from the Patches_for_edk2 folder.

Edited by Philip Petev

Share this post


Link to post
Share on other sites
Posted (edited)
58 minutes ago, Philip Petev said:

subversion downloaded unusable copy (probably another revision)

there's probably a diferences of 10086:

svn info https://github.com/tianocore/edk2/trunk
Path: trunk
URL: https://github.com/tianocore/edk2/trunk
Relative URL: ^/trunk
Repository Root: https://github.com/tianocore/edk2
Repository UUID: 72af8a33-8d04-ae46-851a-ce57b7db7bff
Revision: 36858
Node Kind: directory
Last Changed Author: carsey..jaben
Last Changed Rev: 36858
Last Changed Date: 2018-04-03 11:39:34 +0200 (Mar, 03 Apr 2018)

vs sourceforge:

svn info svn://svn.code.sf.net/p/edk2/code/trunk/edk2
Path: edk2
URL: svn://svn.code.sf.net/p/edk2/code/trunk/edk2
Relative URL: ^/trunk/edk2
Repository Root: svn://svn.code.sf.net/p/edk2/code
Repository UUID: 6f19259b-4bc3-4df7-8a09-765794883524
Revision: 26772
Node Kind: directory
Last Changed Author: edk2buildsystem
Last Changed Rev: 26768
Last Changed Date: 2018-04-02 11:05:26 +0200 (Lun, 02 Apr 2018)

so by checking out r26764 from github (svn) is like having downloading r16678 from sf :D

EDIT

..but sf is actually one day older. Maybe We can checkout a single BaseTools from both url (r36858 and r26772) and see if the commit message is the same with:

cd .../BaseTools
svn log --revision xxxxx

EDIT II

Anyway git is best, but the big problem is if Slice wants that??

Edited by vector sigma
typo

Share this post


Link to post
Share on other sites
On 1/4/2018 at 8:28 PM, apianti said:

So yes if you are getting those errors it's because the patches were not copied

Got it. I'm playing with Clover to make a customized iso with nvme+apfs drivers for virtualbox. I've entered the called "Developer mode", and this really doesn't copy patches. Don't know if this is a bug or is wanted, unsure.

Good night

Share this post


Link to post
Share on other sites

You need to check out the github URL with git. You did that right? If you only changed the URL and still used svn then it probably did something weird.

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
×