Jump to content
InsanelyMac Forum
Micky1979

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

Recommended Posts

Advertisement
5 minutes ago, Awesome Donkey said:

Same here too. Can't the script be made to ignore that (at least for BaseTools/Bin/Win32)?

Unfortunately, no. That external repo (which BTW is not even needed for macOS/Linux) is being called automatically every time when you update your Basetools repo, unlike the edk2 repo at GitHub, where such relationship doesn't exist.

Share this post


Link to post
Share on other sites
14 minutes ago, Philip Petev said:

I was wondering if there is such functionality in svn. Thanks for the tip!

Thanks for r4.7.9 :)

Share this post


Link to post
Share on other sites

Yeah 4.7.9 seems to be working fine :)

Thanks for the fix

Spoiler

 

 Build info.
 ===========
  Package name: Clover_v2.4k_r4418.pkg
  MD5:          935db55325b803b61c0a0d2540b25cdd
  Version:      v2.4k
  Stage:        v2.4k
  Date/Time:    2018-03-20 12:02:08
  Built by:     cyberdevs
  Copyright     2012-2018

  adding: Clover_v2.4k_r4418.pkg (deflated 0%)
  adding: Clover_v2.4k_r4418.pkg.md5 (stored 0%)
total 51776
drwxr-xr-x   9 cyberdevs  staff       288 Mar 20 12:03 .
drwxr-xr-x  15 cyberdevs  staff       480 Mar 20 12:03 ..
-rw-r--r--@  1 cyberdevs  staff  13085053 Mar 20 12:03 Clover_v2.4k_r4418.pkg
-rw-r--r--   1 cyberdevs  staff        68 Mar 20 12:03 Clover_v2.4k_r4418.pkg.md5
-rw-r--r--   1 cyberdevs  staff  13036974 Mar 20 12:03 Clover_v2.4k_r4418.zip
drwxr-xr-x   3 cyberdevs  staff        96 Mar 20 12:02 Resources
drwxr-xr-x   7 cyberdevs  staff       224 Mar 20 12:02 build
drwxr-xr-x   3 cyberdevs  staff        96 Mar 20 12:03 package
drwxr-xr-x   7 cyberdevs  staff       224 Mar 20 12:02 utils
================================================================================
build started at:
Tue Mar 20 12:01:03 +0330 2018
finished at
Tue Mar 20 12:03:02 +0330 2018

Done!

                             <--------------------------------------------------
Clover was built successfully!
Press any key to continue...

 


 

Share this post


Link to post
Share on other sites
Posted (edited)

is it possible to add a suggested EDK version to BuildCloverConfig.txt

like SUGGESTED_EDK_REV= for testing instead of editing the script itself like that it won't get erased on script updates?

Edited by bronxteck

Share this post


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

is it possible to add a suggested EDK version to BuildCloverConfig.txt

like SUGGESTED_EDK_REV= for testing instead of editing the script itself like that it won't get erased on script updates?

I've already done something similar several days ago with:

Build_Clover.command --edk2rev 26467

:)

Edited by vector sigma

Share this post


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

hstest$ Build_Clover.command --edk2rev 26467

-bash: Build_Clover.command: command not found

 

Just drag and drop build_clover.command in terminal, add --edk2rev 26467 for example

Share this post


Link to post
Share on other sites
thanks. I thought that the script asked to install the binary on first run so that it could be called from anywhere but maybe not.
It did. You can run "buildclover" from terminal.

Sent from my SM-G930F using Tapatalk Pro

Share this post


Link to post
Share on other sites
Posted (edited)

so then the should it have worked the first time without dragging the script to terminal.

or it won't accept the edk rev if you call it from terminal ? unless high Sierra is blocking it?

Edited by bronxteck

Share this post


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

so then the should it have worked the first time without dragging the script to terminal.

or it won't accept the edk rev if you call it from terminal ? unless high Sierra is blocking it?

It worked for me

	Shanes-MBP:~ shane$ buildclover --edk2rev 26467
	 
	================================================================================
	Build_Clover script v4.7.9                                  No update available.
	                             <--------------------------------------------------
	================================================================================
	By Micky1979 based on Slice, apianti, vit9696, Download Fritz, Zenith432,
	STLVNUB, JrCs,cecekpawon, Needy, cvad, Rehabman, philip_petev, ErmaC
	 
	Supported OSes: macOS X, Ubuntu (16.04/16.10), Debian Jessie and Stretch
	                             <--------------------------------------------------
	CLOVER Remote revision: 4418 Local revision: 4418
	EDK2 Remote revision: 26700 Local revision: 26300
	 
	User-provided EDK2 revision: 26467
	 
	The current local EDK2 revision is not the suggested one (26467)!
	It's recommended to change it to the suggested one,
	using the update Clover + force edk2 update option!
	Used settings: /Users/shane/BuildCloverConfig.txt 
	                             <--------------------------------------------------
	Please enter your choice: 
	 1) update Clover only (no building)
	 2) update Clover + force edk2 update (no building)
	 3) run my script on the source
	 4) build existing revision (no update, for testing only)
	 5) build existing revision for release (no update, standard build)
	 6) build existing revision with custom macros enabled
	 7) enter Developers mode (only for devs)
	 8) Try Clover Configurator Pro.app
	 9) edit the configuration file
	 10) Exit
	? 
	

Share this post


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

so then the should it have worked the first time without dragging the script to terminal.

or it won't accept the edk rev if you call it from terminal ? unless high Sierra is blocking it?

If you don't want to drag the script in terminal, you can select option 1 for symlink, as @SavageAUS. After add --edk2rev XXXX (XXXX= user choose revision). It's work here also for me

================================================================================
Build_Clover script v4.7.9                                  No update available.
                             <--------------------------------------------------
================================================================================
By Micky1979 based on Slice, apianti, vit9696, Download Fritz, Zenith432,
STLVNUB, JrCs,cecekpawon, Needy, cvad, Rehabman, philip_petev, ErmaC

Supported OSes: macOS X, Ubuntu (16.04/16.10), Debian Jessie and Stretch
                             <--------------------------------------------------
CLOVER	Remote revision: 4418	Local revision: 4418
EDK2	Remote revision: 26700	Local revision: 26300

The current local EDK2 revision is the suggested one (26300). 
Used settings: /Users/mathieu/src/BuildCloverConfig.txt 
                             <--------------------------------------------------
Please enter your choice: 
 1) add "buildclover" symlink to /usr/local/bin
 2) update Clover only (no building)
 3) update Clover + force edk2 update (no building)
 4) run my script on the source
 5) build existing revision (no update, for testing only)
 6) build existing revision for release (no update, standard build)
 7) build existing revision with custom macros enabled
 8) enter Developers mode (only for devs)
 9) edit the configuration file
 10) Exit
?

 

Share this post


Link to post
Share on other sites
35 minutes ago, D-an-W said:

4419 doesn't want to build here, anyone else tried?

Before update by Philip, you can replace -26300 by -26764 in the script. And select option 3. All work fine here

Share this post


Link to post
Share on other sites

No issues here either 

Share this post


Link to post
Share on other sites
[SLINK] GenericBdsLib
/Users/balamut/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/BmDriverHealth.c:432:1: error: conflicting types for 'BmRepairAllControllers'
BmRepairAllControllers (
^
/Users/balamut/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/InternalBm.h:352:1: note: previous declaration is here
BmRepairAllControllers (
^
[CC] FilePaths
/Users/balamut/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/BmDriverHealth.c:580:32: error: use of undeclared identifier 'MAX_RECONNECT_REPAIR'
    if (ReconnectRepairCount < MAX_RECONNECT_REPAIR) {
                               ^
/Users/balamut/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/BmDriverHealth.c:581:31: error: too many arguments to function call, expected 0, have 1
      BmRepairAllControllers (ReconnectRepairCount + 1);
      ~~~~~~~~~~~~~~~~~~~~~~  ^~~~~~~~~~~~~~~~~~~~~~~~
/Users/balamut/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/InternalBm.h:351:1: note: 'BmRepairAllControllers' declared here
VOID
^
/Users/balamut/src/edk2/MdePkg/Include/Base.h:337:19: note: expanded from macro 'VOID'
#define VOID      void
                  ^
3 errors generated.
make: *** [/Users/balamut/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdeModulePkg/Library/UefiBootManagerLib/UefiBootManagerLib/OUTPUT/BmDriverHealth.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/balamut/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdeModulePkg/Library/UefiBootManagerLib/UefiBootManagerLib]


build.py...
 : error F002: Failed to build module
	/Users/balamut/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/UefiBootManagerLib.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 15:29:24, Mar.31 2018
Build total time: 00:00:14


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

 

Share this post


Link to post
Share on other sites

Clover or script?

	================================================================================
	Build_Clover script v4.7.9                                  No update available.
	                             <--------------------------------------------------
	================================================================================
	By Micky1979 based on Slice, apianti, vit9696, Download Fritz, Zenith432,
	STLVNUB, JrCs,cecekpawon, Needy, cvad, Rehabman, philip_petev, ErmaC
	 
	Supported OSes: macOS X, Ubuntu (16.04/16.10), Debian Jessie and Stretch
	                             <--------------------------------------------------
	CLOVER Remote revision: 4422 Local revision: 4422
	EDK2 Remote revision: 26767 Local revision: 26300
	 
	The current local EDK2 revision is the suggested one (26300). 
	Used settings: /Users/shane/BuildCloverConfig.txt 
	                             <--------------------------------------------------
	Please enter your choice: 
	 1) update Clover only (no building)
	 2) update Clover + force edk2 update (no building)
	 3) run my script on the source
	 4) build existing revision (no update, for testing only)
	 5) build existing revision for release (no update, standard build)
	 6) build existing revision with custom macros enabled
	 7) enter Developers mode (only for devs)
	 8) Try Clover Configurator Pro.app
	 9) edit the configuration file
	 10) Exit
	? 5
	 
	 
	 
	 
	 
	 
	 
	================================================================================
	Select the desired architecture
	                             <--------------------------------------------------
	1) Standard x64 only
	2) ia32 and x64 (ia32 is deprecated)
	3) ia32 only (deprecated)
	4) Back to Main Menu
	5) Exit
	? 1
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	================================================================================
	Select the desired pkg type
	                             <--------------------------------------------------
	1) Standard
	2) slim pkg that skip themes and CloverThemeManager.app
	3) slim pkg that skip themes and CloverThemeManager.app, updater and PrefPanel
	4) slim pkg UEFI only, without RC Scripts, themes & CTM, updater and PrefPanel
	5) Back to Select architecture menu
	6) Exit
	? 1
	================================================================================
	Running from: macOS 10.13.4
	Xcode 9.3
	Build version 9E145
	                             <--------------------------------------------------
	================================================================================
	Compiler settings
	                             <--------------------------------------------------
	Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/usr/include/c++/4.2.1
	Apple LLVM version 9.1.0 (clang-902.0.39.1)
	Target: x86_64-apple-darwin17.5.0
	Thread model: posix
	InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
	                             <--------------------------------------------------
	================================================================================
	BUILDTOOL is XCODE8
	                             <--------------------------------------------------
	 
	================================================================================
	nasm check:
	                             <--------------------------------------------------
	NASM version 2.13.03 compiled on Feb  7 2018
	================================================================================
	gettext check:
	                             <--------------------------------------------------
	found gettext at /Users/shane/src/opt/local/bin
	================================================================================
	mtoc check:
	                             <--------------------------------------------------
	mtoc found in /Users/shane/src/opt/local/bin.
	================================================================================
	 
	Loading previous configuration from /Users/shane/src/edk2/Conf/BuildEnv.sh
	WORKSPACE: /Users/shane/src/edk2
	EDK_TOOLS_PATH: /Users/shane/src/edk2/BaseTools
	CONF_PATH: /Users/shane/src/edk2/Conf
	Build environment: Darwin-17.5.0-x86_64-i386-64bit
	Build start time: 11:17:26, Apr.01 2018
	 
	WORKSPACE        = /Users/shane/src/edk2
	ECP_SOURCE       = /Users/shane/src/edk2/EdkCompatibilityPkg
	EDK_SOURCE       = /Users/shane/src/edk2/EdkCompatibilityPkg
	EFI_SOURCE       = /Users/shane/src/edk2/EdkCompatibilityPkg
	EDK_TOOLS_PATH   = /Users/shane/src/edk2/BaseTools
	CONF_PATH        = /Users/shane/src/edk2/Conf
	 
	 
	Architecture(s)  = X64
	Build target     = RELEASE
	Toolchain        = XCODE8
	 
	Active Platform          = /Users/shane/src/edk2/AptioFixPkg/AptioFixPkg.dsc
	 
	Processing meta-data . done!
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseLib/BaseLib.inf [X64]
	Building ... /Users/shane/src/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseMemoryLib/BaseMemoryLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiBootServicesTableLib/UefiBootServicesTableLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BasePrintLib/BasePrintLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiMemoryAllocationLib/UefiMemoryAllocationLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiDevicePathLib/UefiDevicePathLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiRuntimeServicesTableLib/UefiRuntimeServicesTableLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/UefiHiiServicesLib/UefiHiiServicesLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiLib/UefiLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/UefiHiiLib/UefiHiiLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiUsbLib/UefiUsbLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/AptioFixPkg/Platform/AptioInputFix/AptioInputFix.inf [X64]
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseRngLib/BaseRngLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseCpuLib/BaseCpuLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/AptioFixPkg/Platform/AptioMemoryFix/AptioMemoryFix.inf [X64]
	make: Nothing to be done for `tbuild'.
	 
	- Done -
	Build end time: 11:17:28, Apr.01 2018
	Build total time: 00:00:02
	 
	================================================================================
	boot6
	                             <--------------------------------------------------
	TOOLCHAIN_DIR: /Users/shane/src/opt/local
	MTOC_PREFIX: /Users/shane/src/opt/local/bin/
	NASM_PREFIX: /Users/shane/src/opt/local/bin/
	NASM_VER: 2.13.03
	Building from: /Users/shane/src/edk2
	 
	Running edk2 build for CloverX64 using the command:
	build  -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/shane/src/edk2/Conf -D USE_LOW_EBDA -p Clover/Clover.dsc  -a X64 -b RELEASE -t XCODE8 -n 9 
	 
	Build environment: Darwin-17.5.0-x86_64-i386-64bit
	Build start time: 11:17:28, Apr.01 2018
	 
	WORKSPACE        = /Users/shane/src/edk2
	ECP_SOURCE       = /Users/shane/src/edk2/EdkCompatibilityPkg
	EDK_SOURCE       = /Users/shane/src/edk2/EdkCompatibilityPkg
	EFI_SOURCE       = /Users/shane/src/edk2/EdkCompatibilityPkg
	EDK_TOOLS_PATH   = /Users/shane/src/edk2/BaseTools
	CONF_PATH        = /Users/shane/src/edk2/Conf
	 
	 
	Architecture(s)  = X64
	Build target     = RELEASE
	Toolchain        = XCODE8
	 
	Active Platform          = /Users/shane/src/edk2/Clover/Clover.dsc
	Flash Image Definition   = /Users/shane/src/edk2/Clover/Clover.fdf
	 
	Processing meta-data .... done!
	Building ... /Users/shane/src/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [X64]
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseMemoryLib/BaseMemoryLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseLib/BaseLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BasePrintLib/BasePrintLib.inf [X64]
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseReportStatusCodeLibNull/BaseReportStatusCodeLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic.inf [X64]
	make: Nothing to be done for `tbuild'.
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/DxeCoreMemoryAllocationLib/DxeCoreMemoryAllocationLib.inf [X64]
	Building ... /Users/shane/src/edk2/MdePkg/Library/DxeCoreEntryPoint/DxeCoreEntryPoint.inf [X64]
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiRuntimeServicesTableLib/UefiRuntimeServicesTableLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiDevicePathLib/UefiDevicePathLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiBootServicesTableLib/UefiBootServicesTableLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BasePeCoffExtraActionLibNull/BasePeCoffExtraActionLibNull.inf [X64]
	Building ... /Users/shane/src/edk2/MdePkg/Library/DxeCoreHobLib/DxeCoreHobLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiLib/UefiLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseCacheMaintenanceLib/BaseCacheMaintenanceLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseUefiDecompressLib/BaseUefiDecompressLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BasePerformanceLibNull/BasePerformanceLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/Clover/Library/VBoxPeCoffLib/VBoxPeCoffLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BasePeCoffGetEntryPointLib/BasePeCoffGetEntryPointLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/DxeExtractGuidedSectionLib/DxeExtractGuidedSectionLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/Clover/Library/DuetTimerLib/DuetTimerLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/DxeServicesLib/DxeServicesLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/DebugAgentLibNull/DebugAgentLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/CpuExceptionHandlerLibNull/CpuExceptionHandlerLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiMemoryAllocationLib/UefiMemoryAllocationLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/DxeHobLib/DxeHobLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/UefiRuntimeLib/UefiRuntimeLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/VarCheckLib/VarCheckLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/BaseSynchronizationLib/BaseSynchronizationLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdePkg/Library/DxeServicesTableLib/DxeServicesTableLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/TpmMeasurementLibNull/TpmMeasurementLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/AuthVariableLibNull/AuthVariableLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/VarCheckUefiLib/VarCheckUefiLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/DxeCapsuleLibNull/DxeCapsuleLibNull.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/DxeSecurityManagementLib/DxeSecurityManagementLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/Clover/Library/UefiHiiServicesLib/UefiHiiServicesLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/UefiSortLib/UefiSortLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/UefiHiiLib/UefiHiiLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/UefiBootManagerLib.inf [X64]
	Building ... /Users/shane/src/edk2/MdePkg/Library/DxePcdLib/DxePcdLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/MdeModulePkg/Library/CustomizedDisplayLib/CustomizedDisplayLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/Clover/Library/LzmaCustomDecompressLib/LzmaCustomDecompressLib.inf [X64]
	make: Nothing to be done for `tbuild'.
	Building ... /Users/shane/src/edk2/Clover/Library/GenericBdsLib/GenericBdsLib.inf [X64]
	/Users/shane/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/BmDriverHealth.c:432:1: error: conflicting types for 'BmRepairAllControllers'
	BmRepairAllControllers (
	^
	/Users/shane/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/InternalBm.h:352:1: note: previous declaration is here
	BmRepairAllControllers (
	^
	/Users/shane/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/BmDriverHealth.c:580:32: error: use of undeclared identifier 'MAX_RECONNECT_REPAIR'
	    if (ReconnectRepairCount < MAX_RECONNECT_REPAIR) {
	                               ^
	Building ... /Users/shane/src/edk2/Clover/Library/OsxBdsPlatformLib/PlatformBds.inf [X64]
	make: Nothing to be done for `tbuild'.
	/Users/shane/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/BmDriverHealth.c:581:31: error: too many arguments to function call, expected 0, have 1
	      BmRepairAllControllers (ReconnectRepairCount + 1);
	      ~~~~~~~~~~~~~~~~~~~~~~  ^~~~~~~~~~~~~~~~~~~~~~~~
	/Users/shane/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/InternalBm.h:351:1: note: 'BmRepairAllControllers' declared here
	VOID
	^
	/Users/shane/src/edk2/MdePkg/Include/Base.h:337:19: note: expanded from macro 'VOID'
	#define VOID      void
	                  ^
	3 errors generated.
	make: *** [/Users/shane/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdeModulePkg/Library/UefiBootManagerLib/UefiBootManagerLib/OUTPUT/BmDriverHealth.obj] Error 1
	 
	 
	build.py...
	 : error 7000: Failed to execute command
	make tbuild [/Users/shane/src/edk2/Build/Clover/RELEASE_XCODE8/X64/MdeModulePkg/Library/UefiBootManagerLib/UefiBootManagerLib]
	 
	 
	build.py...
	 : error F002: Failed to build module
	/Users/shane/src/edk2/MdeModulePkg/Library/UefiBootManagerLib/UefiBootManagerLib.inf [X64, XCODE8, RELEASE]
	 
	- Failed -
	Build end time: 11:17:34, Apr.01 2018
	Build total time: 00:00:07
	 
	 
	o_Ops, ./ebuild.sh exited with error(s), aborting..
	Shanes-iMac:~ shane$ 
	

Share this post


Link to post
Share on other sites
Posted (edited)

@Philip Petev,

Why don't you just start using the git version of the repo from github, the one on SF is terrible. The reason it has issues is because it's a badly synced svn mirror of the git repo.

EDIT: I only use the git repo of EDK2, and might explain why I haven't been having issues when others have been. The clover repo should be fine but the EDK2 repo on SF sucks since they moved to git.

@everyone,

If you are getting this build error it's because the script apparently does not properly use Patches_for_EDK2. You need to copy the contents of this directory to the EDK2 directory to overwrite files that have problems.

EDIT: Also this is a terrible method because it requires that you revert the changes made to the EDK2 before updating it.

EDIT2: Also there was a mistake, I fixed it in r4423. My gift to you guys, lol.

EDIT3: To revert an svn repo:

svn revert --recursive .
svn cleanup --remove-unversioned .

To revert a git repo:

git reset HEAD --hard
git clean -fd

Obviously both those run from the EDK2 directory.

Edited by apianti

Share this post


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

If you are getting this build error it's because the script apparently does not properly use Patches_for_EDK2. You need to copy the contents of this

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.

Edited by vector sigma

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:
       
      <?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>Boot</key>
          <dict>
              <key>Arguments</key>
              <string></string>
              <key>DefaultVolume</key>
              <string>clover</string>
              <key>Debug</key>
              <false/>
              <key>Secure</key>
              <false/>
              <key>Timeout</key>
              <integer>3</integer>
          </dict>
          <key>GUI</key>
          <dict>
              <key>Scan</key>
              <dict>
                  <key>Entries</key>
                  <true/>
                  <key>Tool</key>
                  <true/>
              </dict>
              <key>ScreenResolution</key>
              <string>1024x768</string>
              <key>Theme</key>
              <string>embedded</string>
          </dict>
          <key>RtVariables</key>
          <dict>
              <key>BooterConfig</key>
              <string>0x28</string>
              <key>CsrActiveConfig</key>
              <string>0x3</string>
          </dict>
          <key>SMBIOS</key>
          <dict>
              <key>Trust</key>
              <false/>
          </dict>
          <key>SystemParameters</key>
          <dict>
              <key>InjectKexts</key>
              <false/>
              <key>InjectSystemID</key>
              <true/>
          </dict>
      </dict>
      </plist>
       
      And following Clover UEFI drivers:
      apfs.efi
      AppleImageCodec-64.efi
      AppleKeyAggregator-64.efi
      AppleUITheme-64.efi
      DataHubDxe-64.efi
      FirmwareVolume-64.efi
      FSInject-64.efi
      OsxFatBinaryDrv-64.efi
      PartitionDxe-64.efi
      SMCHelper-64.efi
      UsbKbDxe-64.efi
      UsbMouseDxe-64.efi
      VBoxHfs-64.efi
       
      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:
       
      <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
        <name>NAME-server-macos-10.12</name>
        <uuid>38986f0a-d1fd-476d-8478-3220afa50422</uuid>
        <memory unit='KiB'>16777216</memory>
        <currentMemory unit='KiB'>16777216</currentMemory>
        <vcpu placement='static' current='2'>8</vcpu>
        <os>
          <type arch='x86_64' machine='pc-q35-2.11'>hvm</type>
          <loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
          <nvram>/home/USER/Documents/virtual-machines/NAME.server.macos-10.12/OVMF_VARS.fd</nvram>
          <bootmenu enable='yes'/>
        </os>
        <features>
          <acpi/>
          <vmport state='off'/>
        </features>
        <cpu mode='custom' match='exact' check='full'>
          <model fallback='forbid'>Penryn</model>
          <vendor>GenuineIntel</vendor>
          <topology sockets='2' cores='4' threads='1'/>
          <feature policy='require' name='vme'/>
          <feature policy='require' name='x2apic'/>
          <feature policy='require' name='hypervisor'/>
          <feature policy='require' name='invtsc'/>
          <feature policy='require' name='aes'/>
          <feature policy='require' name='xsave'/>
          <feature policy='require' name='avx'/>
          <feature policy='require' name='xsaveopt'/>
          <feature policy='require' name='avx2'/>
          <feature policy='require' name='smep'/>
        </cpu>
        <clock offset='utc'>
          <timer name='rtc' tickpolicy='catchup'/>
          <timer name='pit' tickpolicy='delay'/>
          <timer name='hpet' present='no'/>
        </clock>
        <on_poweroff>destroy</on_poweroff>
        <on_reboot>restart</on_reboot>
        <on_crash>destroy</on_crash>
        <pm>
          <suspend-to-mem enabled='no'/>
          <suspend-to-disk enabled='no'/>
        </pm>
        <devices>
          <emulator>/usr/bin/kvm-spice</emulator>
          <disk type='file' device='disk'>
            <driver name='qemu' type='qcow2'/>
            <source file='/home/USER/Documents/virtual-machines/NAME.server.macos-10.12/NAME-hd1-01.qcow2'/>
            <target dev='sdb' bus='sata'/>
            <address type='drive' controller='0' bus='0' target='0' unit='1'/>
          </disk>
          <disk type='file' device='disk'>
            <driver name='qemu' type='raw'/>
            <source file='/home/USER/Documents/virtual-machines/images/macos-sierra-install.img'/>
            <target dev='sdc' bus='sata'/>
            <address type='drive' controller='0' bus='0' target='0' unit='2'/>
          </disk>
          <disk type='file' device='disk'>
            <driver name='qemu' type='qcow2'/>
            <source file='/home/USER/Documents/virtual-machines/images/clover-boot-24k-r4458.qclow2'/>
            <target dev='sdd' bus='sata'/>
            <boot order='1'/>
            <address type='drive' controller='0' bus='0' target='0' unit='3'/>
          </disk>
          <controller type='usb' index='0' model='ich9-ehci1'>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x1d' function='0x7'/>
          </controller>
          <controller type='usb' index='0' model='ich9-uhci1'>
            <master startport='0'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x1d' function='0x0' multifunction='on'/>
          </controller>
          <controller type='usb' index='0' model='ich9-uhci2'>
            <master startport='2'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x1d' function='0x1'/>
          </controller>
          <controller type='usb' index='0' model='ich9-uhci3'>
            <master startport='4'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x1d' function='0x2'/>
          </controller>
          <controller type='sata' index='0'>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
          </controller>
          <controller type='pci' index='0' model='pcie-root'/>
          <controller type='pci' index='1' model='dmi-to-pci-bridge'>
            <model name='i82801b11-bridge'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
          </controller>
          <controller type='pci' index='2' model='pci-bridge'>
            <model name='pci-bridge'/>
            <target chassisNr='2'/>
            <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
          </controller>
          <controller type='pci' index='3' model='pcie-root-port'>
            <model name='pcie-root-port'/>
            <target chassis='3' port='0x10'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
          </controller>
          <controller type='pci' index='4' model='pcie-root-port'>
            <model name='pcie-root-port'/>
            <target chassis='4' port='0x11'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
          </controller>
          <controller type='pci' index='5' model='pcie-root-port'>
            <model name='pcie-root-port'/>
            <target chassis='5' port='0x12'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
          </controller>
          <controller type='pci' index='6' model='pcie-root-port'>
            <model name='pcie-root-port'/>
            <target chassis='6' port='0x13'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
          </controller>
          <controller type='pci' index='7' model='pcie-root-port'>
            <model name='pcie-root-port'/>
            <target chassis='7' port='0x14'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
          </controller>
          <controller type='virtio-serial' index='0'>
            <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
          </controller>
          <controller type='scsi' index='0' model='virtio-scsi'>
            <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
          </controller>
          <interface type='bridge'>
            <mac address='52:54:00:4b:c6:e8'/>
            <source bridge='br50'/>
            <model type='e1000'/>
            <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
          </interface>
          <serial type='pty'>
            <target type='isa-serial' port='0'>
              <model name='isa-serial'/>
            </target>
          </serial>
          <console type='pty'>
            <target type='serial' port='0'/>
          </console>
          <channel type='spicevmc'>
            <target type='virtio' name='com.redhat.spice.0'/>
            <address type='virtio-serial' controller='0' bus='0' port='1'/>
          </channel>
          <input type='keyboard' bus='usb'>
            <address type='usb' bus='0' port='2'/>
          </input>
          <input type='mouse' bus='ps2'/>
          <input type='tablet' bus='usb'>
            <address type='usb' bus='0' port='3'/>
          </input>
          <input type='keyboard' bus='ps2'/>
          <graphics type='spice' autoport='yes'>
            <listen type='address'/>
            <image compression='off'/>
          </graphics>
          <sound model='ich6'>
            <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
          </sound>
          <video>
            <model type='vga' vram='65536' heads='1' primary='yes'/>
            <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
          </video>
          <hostdev mode='subsystem' type='pci' managed='yes'>
            <source>
              <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/>
            </source>
            <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
          </hostdev>
          <hostdev mode='subsystem' type='pci' managed='yes'>
            <source>
              <address domain='0x0000' bus='0x0b' slot='0x00' function='0x1'/>
            </source>
            <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/>
          </hostdev>
          <redirdev bus='usb' type='spicevmc'>
            <address type='usb' bus='0' port='5'/>
          </redirdev>
          <redirdev bus='usb' type='spicevmc'>
            <address type='usb' bus='0' port='1'/>
          </redirdev>
          <memballoon model='virtio'>
            <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
          </memballoon>
        </devices>
        <seclabel type='none' model='apparmor'/>
        <qemu:commandline>
          <qemu:arg value='-readconfig'/>
          <qemu:arg value='/home/USER/Documents/virtual-machines/NAME.server.macos-10.12/macos.cfg'/>
        </qemu:commandline>
      </domain>
       
       
      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
×