Jump to content
ErmaC

Clover General discussion

21,372 posts in this topic

Recommended Posts

3 hours ago, D-an-W said:

Not working here (Using a fresh install of the "standard" Build_Clover.command)...

Hi, not sure Build_Clover.command can build latest source, but if you want you can try the new Clover on github by using the attached wrapper

 

 

 

Clover.zip

Edited by vector sigma
corrected

Share this post


Link to post
Share on other sites
Advertisement

Thanks for the file, it didn't complete the build however...

Building ... /Users/dan/src/CloverBootloader/Library/OpensslLib/OpensslLibNull.inf [X64]
[CC] DivU64x32
[CC] SetMem
[CC] InternalGetSpinLockProperties
"/nasm" -I/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/X64/ -I/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/X64/ -I/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/ -I/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/DEBUG/ -I/Users/dan/src/CloverBootloader/MdePkg/ -I/Users/dan/src/CloverBootloader/MdePkg/Include/ -I/Users/dan/src/CloverBootloader/MdePkg/Include/X64/ -f macho64 -o /Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/X64/IoFifo.obj /Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/X64/IoFifo.iii
/bin/sh: /nasm: No such file or directory
make: *** [/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/X64/IoFifo.obj] Error 127


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseLib/BaseLib]


build.py...
 : error F002: Failed to build module
	/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 21:18:46, Sep.05 2019
Build total time: 00:00:13

Dans-Mac-mini:~ dan$ 

 

Share this post


Link to post
Share on other sites
2 hours ago, D-an-W said:

Thanks for the file, it didn't complete the build however...


Building ... /Users/dan/src/CloverBootloader/Library/OpensslLib/OpensslLibNull.inf [X64]
[CC] DivU64x32
[CC] SetMem
[CC] InternalGetSpinLockProperties
"/nasm" -I/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/X64/ -I/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/X64/ -I/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/ -I/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/DEBUG/ -I/Users/dan/src/CloverBootloader/MdePkg/ -I/Users/dan/src/CloverBootloader/MdePkg/Include/ -I/Users/dan/src/CloverBootloader/MdePkg/Include/X64/ -f macho64 -o /Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/X64/IoFifo.obj /Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/X64/IoFifo.iii
/bin/sh: /nasm: No such file or directory
make: *** [/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/X64/IoFifo.obj] Error 127


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseLib/BaseLib]


build.py...
 : error F002: Failed to build module
	/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 21:18:46, Sep.05 2019
Build total time: 00:00:13

Dans-Mac-mini:~ dan$ 

 

 

23 minutes ago, STLVNUB said:

Looks like it can't find nasm, is it installed?

More than likely not set properly in script.

Yes it is a bug, the last. I made the buildme script to find the first worthy nasm to build Clover, but in ebuild.sh there's something apparently weird because looks for hard coded paths. Not sure why, but /opt/local/bin/nasm for example is preferred. Ok, the one shipped with macOS is bad, so I can assume someone wanted this for convenience.

/bin/sh: /nasm: No such file or directory

yep, no nasm at "/", that's the problem. Tomorow I'll fix it.

Share this post


Link to post
Share on other sites
32 minutes ago, Slice said:

Up to now revision 5071 on sf.net is the same as latest on github.

There was talk y e a r s ago, glad to see you guys finally saw the light.

Now to top it off, how about getting rid of patches and adjusting Clover

Go with the flow.

Share this post


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

Could you, kindly, try a fresh repository without even the opt directory to see if all is fine now?

Just open buildme and select:


4) build all

on the fresh souce. thanks in advance

 

I've got always some issue. I don't understand why. Terminal file in attachment

Thanks

Test on Terminal

Share this post


Link to post
Share on other sites
1 hour ago, ellaosx said:

is it still ok to use sf and compile for now?

Yes, but need to upgrade edk2 to latest stable edk2-stable201908.

 

1242717681_Cloverr5071SFBuild.thumb.png.dcd3b1a0f9b44905f2826ea9e654f4b4.png

 

For those still wanting to compile Clover from SourceForge via svn

1.  Delete old ~/src/edk2 folder (but keep existing ~/src/opt and ~/src/tools folders)
2.  Download latest stable edk2-stable201908.zip & extract into ~/src, renaming it edk2
3.  Open terminal and type the following lines, followed by <Enter> to prepare build tools

cd ~/src/edk2
svn co svn://svn.code.sf.net/p/cloverefiboot/code/ Clover
source edksetup.sh
cp -R Clover/Patches_for_EDK2/* ./
make -C BaseTools

4.  Open terminal and type the following lines, followed by <Enter> to build Clover

cd ~/edk2/Clover
ebuild.sh -fr -D NO_GRUB_DRIVERS_EMBEDDED                  //builds Clover with boot6
ebuild.sh -fr -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED     //builds Clover with boot7

5.  Open terminal and type the following lines, followed by <Enter> to build Clover installer pkg and/or iso

cd CloverPackage
./makepkg
make iso

 

If you want to build from scratch from CloverHackyColor GIT

1.  Open terminal and type the following lines, followed by <Enter> to download Clover source files.  Note:  no need to download edk2 :)...

mkdir ~/src // if src folder does not already exist in user's home folder
cd ~/src
git clone https://github.com/CloverHackyColor/CloverBootloader.git

2.  Install/build nasm

cd CloverBootloader
./buildnasm.sh

3.  Run @vector sigma's buildme script...

./buildme // Select option 4 (build all)

1230012398_Cloverr5072fromGIT.png.826c57746d81f9e4ec1cef6d14f49327.png

Share this post


Link to post
Share on other sites
1 hour ago, fusion71au said:

2.  Install/build nasm


cd CloverBootloader
./buildnasm.sh

3.  Run @vector sigma's buildme script...


./buildme // Select option 4 (build all)

 

why the need of #2, vector's builme script wont do it automatically?

Share this post


Link to post
Share on other sites

Working with GitHub is simpler.

About sf.net I will propose the follow sequence

1. cd ~

2. mkdir src

3. cd src

4. git clone https://github.com/CloverHackyColor/edk2.git --depth 1

SIC! There is already patched EDK2. depth 1 make your download times smaller.

5. cd edk2

6. make -C BaseTools/Source/C

7. svn co svn://svn.code.sf.net/p/cloverefiboot/code/ Clover

8. source edksetup.sh

9. cd Clover

10. ./buildnasm.sh

11. ./buildgettext.sh

12. ./buildmtoc.sh

13. ./ebuild.sh -fr -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED   if you want BIOS_BLOCK_IO legacy boot7
14. ./ebuild.sh -fr -D NO_GRUB_DRIVERS_EMBEDDED

15. cd CloverPackage

16 ./makepkg

17. ./makeiso if you want

 

 

Share this post


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

 

Yes it is a bug, the last. I made the buildme script to find the first worthy nasm to build Clover, but in ebuild.sh there's something apparently weird because looks for hard coded paths. Not sure why, but /opt/local/bin/nasm for example is preferred. Ok, the one shipped with macOS is bad, so I can assume someone wanted this for convenience.


/bin/sh: /nasm: No such file or directory

yep, no nasm at "/", that's the problem. Tomorow I'll fix it.

 

18 minutes ago, ellaosx said:

why the need of #2, vector's builme script wont do it automatically?

 

As @vector sigma mentioned in the post above yours, there is a bug/incompatibility in the buildme script at the moment ---> nasm not present error thrown up.  This should be fixed soon.

 

I found in my situation that running the buildnasm script before the buildme script worked to compile Clover successfully :).

 

PS Anyone notice "invalid option 5" when selecting to update Clover (discard local changes)?

buildme Beta, Clover v2.5k r5072 (SHA: ac97cf5)
Remote SHA: ac97cf5

1) build Clover
2) make pkg
3) make iso
4) build all
5) update Clover (discard local changes)
6) update Clover (stash local changes)
7) status
8) show diff
9) quit
Please enter your choice: 5
invalid option 5

 

Share this post


Link to post
Share on other sites
7 hours ago, Matgen84 said:

 

I've got always some issue. I don't understand why. Terminal file in attachment

Thanks

Test on Terminal

 

4 hours ago, fusion71au said:

As @vector sigma mentioned in the post above yours, there is a bug/incompatibility in the buildme script at the moment ---> nasm not present error thrown up.  This should be fixed soon.

 

I found in my situation that running the buildnasm script before the buildme script worked to compile Clover successfully :).

 

14 hours ago, D-an-W said:

Thanks for the file, it didn't complete the build however...


Building ... /Users/dan/src/CloverBootloader/Library/OpensslLib/OpensslLibNull.inf [X64]
[CC] DivU64x32
[CC] SetMem
[CC] InternalGetSpinLockProperties
"/nasm" -I/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/X64/ -I/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/X64/ -I/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/ -I/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/DEBUG/ -I/Users/dan/src/CloverBootloader/MdePkg/ -I/Users/dan/src/CloverBootloader/MdePkg/Include/ -I/Users/dan/src/CloverBootloader/MdePkg/Include/X64/ -f macho64 -o /Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/X64/IoFifo.obj /Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/X64/IoFifo.iii
/bin/sh: /nasm: No such file or directory
make: *** [/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/X64/IoFifo.obj] Error 127


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/dan/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BaseLib/BaseLib]


build.py...
 : error F002: Failed to build module
	/Users/dan/src/CloverBootloader/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 21:18:46, Sep.05 2019
Build total time: 00:00:13

Dans-Mac-mini:~ dan$ 

 

fixed! (at github)

Share this post


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

Working with GitHub is simpler.

About sf.net I will propose the follow sequence

1. cd ~

2. mkdir src

3. cd src

4. git clone https://github.com/CloverHackyColor/edk2.git --depth 1

SIC! There is already patched EDK2. depth 1 make your download times smaller.

5. cd edk2

6. make -C BaseTools/Source/C

7. svn co svn://svn.code.sf.net/p/cloverefiboot/code/ Clover

8. source edksetup.sh

9. cd Clover

10. ./buildnasm.sh

11. ./buildgettext.sh

12. ./buildmtoc.sh

13. ./ebuild.sh -fr -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED   if you want BIOS_BLOCK_IO legacy boot7
14. ./ebuild.sh -fr -D NO_GRUB_DRIVERS_EMBEDDED

15. cd CloverPackage

16 ./makepkg

17. ./makeiso if you want

 

 

I can propose to leave Clover outside edk2?

1) is easy using PAKAGES_PATH, patched module will leave separately in the workspace

2) your edk2 repository will be always untouched

3) Clover from git and Clover from svn can coexist in the same src dir

Share this post


Link to post
Share on other sites
2 minutes ago, vector sigma said:

I can propose to leave Clover outside edk2?

1) is easy using PAKAGES_PATH, patched module will leave separately in the workspace

2) your edk2 repository will be always untouched

3) Clover from git and Clover from svn can coexist in the same src dir

Mostly all issues with git-Clover already resolved so I will leave it in the new state.

I may propose to include sf-Clover into folder https://github.com/CloverHackyColor/edk2

and make git-svn synchronization between sf and github. I just don't know how to do this.

Share this post


Link to post
Share on other sites
16 minutes ago, Slice said:

Mostly all issues with git-Clover already resolved so I will leave it in the new state.

I may propose to include sf-Clover into folder https://github.com/CloverHackyColor/edk2

and make git-svn synchronization between sf and github. I just don't know how to do this.

 

10 minutes ago, vector sigma said:

no idea, never done...

 

Hi @Slice @vector sigma

 

Thanks for your great job.

 

I found this: http://manpages.ubuntu.com/manpages/cosmic/man1/svn2git.1.html  But I don't know if is interesting or a solution.

svn2git  -  is  a tiny utility for migrating projects from Subversion to Git while keeping
       the trunk, branches and tags where they should  be.  It  uses  git-svn  to  clone  an  svn
       repository  and  does  some  clean-up  to  make  sure  branches and tags are imported in a
       meaningful way, and that the code checked into master ends up being  what's  currently  in
       your svn trunk rather than whichever svn branch your last commit was in.

...

As of svn2git 2.0 there is a new feature to pull in the latest changes from SVN
          into your git repository created with svn2git.  This is a one way sync, but
          allows you to use svn2git as a mirroring tool for your SVN repositories.

 

Share this post


Link to post
Share on other sites
1 hour ago, D-an-W said:

@vector sigma thanks, compiled ok this time.

 

As I have to uncomment a line before compiling can I confirm I should use Option 7 so I don't loose the change?

It should, but it is not guaranteed your change will not generate conflicts with the incoming update ...which you will then have to solve.

Edited by vector sigma

Share this post


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

Guys, I've updated the buildme wrapper at sourceforge to use CloverHackyColor/edk2.

You guys are going in reverse

Work with stock standard EDK2 and ADJUST Clover to work with it.

I compile Clover with NO patches and stock EDK2

You guys one step forward, ten steps back 

Its a joke.

Share this post


Link to post
Share on other sites

Eh wait, why my username changed to `sergey`, who is he? (Hah haa..) :lol: Oh my bad..

Screen Shot 2019-09-07 at 08.19.18.jpg

 

#EDIT: was bad prev. BuildEnv.sh, sorry.. solved already.

Screen Shot 2019-09-07 at 08.40.28.jpg

Edited by Badruzeus

Share this post


Link to post
Share on other sites
16 minutes ago, Badruzeus said:

Eh wait, why my username changed to `sergey`, who is he? (Hah haa..) :lol: Oh my bad..

Screen Shot 2019-09-07 at 08.19.18.jpg

because of https://github.com/CloverHackyColor/CloverBootloader/blob/master/Conf/BuildEnv.sh

I've added again to .gitignore but wont to be ignored Lol. Clean BaseTools, will go away

Share this post


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

because of https://github.com/CloverHackyColor/CloverBootloader/blob/master/Conf/BuildEnv.sh

I've added again to .gitignore but wont to be ignored Lol. Clean BaseTools, will go away

Nevermind, I just did `rm -rf Build && make -C BaseTools/Source/C clean` from WORKSPACE.

(or manually `nano ../Conf/BuildEnv.sh` to adapt my custom Path). Thanks anyway.

Share this post


Link to post
Share on other sites
1 minute ago, Badruzeus said:

Nevermind, I just did `rm -rf Build && make -C BaseTools/Source/C clean` from WORKSPACE.

(or manually `nano ../Conf/BuildEnv.sh` to adapt my custom Path). Thanks anyway.

Ok, was tracked in the cache and so not ignored,  anyway finally is removed.

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

  • Similar Content

    • By Simon's InsaneMac
      Hi, I'm kind of lost when scrolling to Clover Configurator, so I decided to use an EFI from the web and just configure the most basic stuff. But that sadly didn't work, im always getting the attached screen IMG_0054.HEIC (and I don't know whether all the errors are listed, as I can't scroll). 
      Anyways I thought it'd be better to do a custom setup. Can anyone give me some help with what to choose in the settings? Here's my rig:
      i7 8700k
      Asus z370-G (Rog Strix)
      gtx 1060 6gb
      samsung ssd (SATA)
      WD hard drive
       
      Your help would be much appreciated!
    • By kylon
      A big thanks to wegface for teaching me a lot of things.
       
       
      Tested on Catalina 10.15.4 and Clover EFI 5104 (Catalina Patcher)
       
      Not Working:
      - realtek sd card reader (pm me if you have a fix)
       
      Notes:
      **CPU patches are disabled, if you are using a locked BIOS you must enable them**
       
      Clover EFI:
      - Install it in UEFI Mode and change your hdd partition table to GPT.
      - You will be able to install ANY OS in EFI mode, even if this pc does not support EFI at all! (No guide available for this)
       
      You will need:
      My unlocked BIOS (OPTIONAL) (here) Latest Clover config from CCE Bank (here) (asus k53sj-kylon) Rehabman Voodoo PS2 Controller (here) acidanthera AppleALC (here) acidanthera Lilu (here) acidanthera VirtualSMC (here) acidanthera SMCBatteryManager (here) acidanthera SMCLightSensor (here) acidanthera WhateverGreen (here) Mieze Realtek RTL8111 (here)
    • By Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

       
      https://www.dropbox.com/s/drkek0eaz19ina5/OC.zip?dl=0
       
    • By y010204025
      Disclaimer: All files of this article are from itpwd.com and rehabman ’s github.com

       
      After Testing:
       
      Graphics card: NVIDIA K1000M / K2000M / K2100M / K3000M / K3100M / K4000M / M1000M (ordinary TN1600x900 or 1920x1080), AMD W5170M / W7170M (DC2 or 4K), Intel HD4000 (ordinary TN1600x900 or 1920x1080) can be driven normally, but NVIDIA graphics card Brightness adjustment is disabled. AMD W5170m and w7170m are the best choices on 8570W and 8770W. The brightness can be adjusted normally and the graphics performance is very good. For WX7100m and WX4170m, the graphics card fans cannot be controlled, and other methods are required to control the fans. CPU: 3rd generation Intel Core i3, i5 and i7 (Ivy Bridge architecture, including all dual-core and quad-core. Celeron and Pentium are not supported), frequency conversion is normal. In general: If you have 8570W, 8770W, and hope you can get the best Hackintosh experience, it is recommended to replace the CPU with i7-3840QM / i7-3940XM, 8570W is recommended to choose W5170M, 8770W, and it is recommended to choose W7170M. In addition: If you want to have a 4K experience or perfect HIDPI, W5170m / W7170M supports 4K output, you can choose a suitable 4K screen to replace, but because 4K screens are mostly edp interface, and 8570W / 8770W motherboard is lvds interface, This requires a custom screen cable, which seems to be a difficult choice, but you can choose to do it yourself or buy it separately. In China, taobao.com is almighty and may be more suitable for you than eBay.
       
      EFI features:
      out of the box, the relevant hardware can be driven after the OS is installed, and it is easy to use without code operation.
      Supported models: HP EliteBook 8470p, 8570p, 8570w, 8770w (click the model for official specifications)
      Wireless network card: Recommended: BCM94360cd (requires ipex4 to ipex1,3 antenna 1300mbps), BCM94352HMB / DW1550 (2 antennas, 867mbps)
      Wireless characteristics: no white list, wireless network card with Bluetooth does not support the Bluetooth function of the wireless network card (also does not need to shield the pins), but the wireless normal use, you need the Bluetooth function to use this machine comes with Bluetooth:
      Clover version: 5103, keyboard mapping has been added Command key = Alt key, Option key = Win key
      Supported systems: macOS Mojave 10.14.6 (18G103)-macOS Catalina 10.15.x,
       
      Notes on known issues:
      1. The touchpad and the left and right keys under the touchpad are normal, the pointing stick and the left and right keys above the touchpad are temporarily unavailable (recommended to use the second generation of Apple Magic Trackpad)
      2. Indicator display problem (can be ignored, function is normal): Caps light is sometimes not switched in time, mute / wireless key may be yellow
      3.AMD graphics card / Intel nuclear display has supported sleep and 15 levels of brightness adjustment, NVIDIA has no
      4. If the AMD graphics card enters Huaping, refer to editing the Clover startup parameters, and add the Boot parameter radpg = 15 (the EFI file that has been configured with this parameter has been uploaded, refer to the following EFI-guided download link)
      5. Using the above NVIDIA graphics card with a normal TN screen 1600x900 or 1920x1080 can not enter the installation interface, please check whether the VBiOS of the graphics card is exclusively for HP, thank you for your test face K1000M
      6. Due to product design defects, the MSata positions of 8570w and 8770w cannot be used as boot disks, so EFI boot can only be placed on the main hard disk (turn the machine over and open the hard disk in the lower left corner of the cover, which is the main hard disk). Put on msata plate
      +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
      Hardware requirements:
      Model: 8470p, 8570p, 8570W, 8770W 1 or more, it is recommended to use another notebook for emergency Hard disk: It is recommended to choose an SSD hard disk of 240g or more. Samsung or Intel SATA hard disk is a good choice. Wireless card: BCM94352HMB, DW1550, BCM94360CD, miniPCIe slot U disk: 1 for 16g and above, another winPE emergency USB disk is recommended If you use a rescue USB flash drive, it means that you read this post carefully
       
      Make and install a USB flash drive:
      Get the mirror: please do it your way Making and installing a USB flash drive: macOS command line production is recommended, whether it is a real macOS model or a virtual machine (although this is not allowed to be discussed in many forums)Or you can choose to use TransMac or ether under Windows. This is not recommended, but it is simple enough for those new to Hackintosh. Make boot U disk: If you know how to put the boot into the installation U disk, unzip the EFI file and put it in the EFI partition, or you can choose a fat32 format U disk to store the EFI file separately Note: EFI is an unzipped folder, not a zip or ISO suffix file.
       
      BIOS settings From RehabMan
      To start, set BIOS to defaults.
      Then insure:
      UEFI boot is enabled (hybrid/with CSM for best result) secure boot is disabled disable fast boot IGPU graphics memory set to 64mb, if available disable the serial port via BIOS option, if available disable "LAN/WLAN switching", if available disable "Extended Idle Power States" if you find it under "Power Management Options" disable "Wake on LAN" and "Wake on USB" disable Firewire/IEEE 1394, if your laptop has it for Skylake and KabyLake laptop, enable "Launch Hotkeys without Fn keypress" Note: If you have a laptop with switchable graphics, leave it enabled. You can still use it on Windows, although the discrete card will be disabled when running OS X by the ACPI patches provided here. If you want to also disable it in Windows (via BIOS option), make sure you read about the DGPU option in your model specific SSDT (source is in SSDT-HACK.dsl), as in the scenario where the DGPU is disabled by BIOS, DGPU should be set to zero.
       
      Install:
      Please modify according to the above BIOS settings: Press F9 after booting, select the boot efi to file option, which is generally the last item. Enter your boot USB disk to find the location of cloverx64.efi, select cloverx64.efi, press Enter, and enter the clover boot interface. Select the location of the install entry and press Enter. Enter the macOS interface, use the disk tool to format the partition you need to install to hfs + or apfs format, do not choose the encryption option, this will make your efforts in vain. Note: The disk must be in gpt format, and the remaining EFI space is greater than 200M, 300mb + is recommended. If it is not, please try to modify it in WindowsPE environment. This may cause you to lose the Windows system boot and disk data. Please prepare for backup.
      After formatting the partition successfully, close the disk tool and select install, you will find the partition you installed, and follow the interface prompts. When the installation reaches a certain progress, it will restart. When restarting, select F9, enter from the boot U disk, select the disk partition where you installed macOS (no longer the U disk installation), the installation will continue, and it may restart 2 ~ 3 times Every time, you need F9 to select the boot. After entering the installation interface, except for the first installation, select the U disk, and then select the disk installation partition. Eventually you will enter the settings interface. After following the interface prompts, you will enter the macOS system interface. Remember the system password and turn off the Find my mac option.  
      Post install:
       
      After the installation is complete, you need to hang the EFI partition of the disk, copy the EFI file of the U disk to the EFI partition of the disk, so that you can directly use the disk to boot, otherwise you need to select the U disk to boot each time. The mount tool can choose cloverconfigurator. If after copying the EFI file to the disk, the computer cannot recognize your clover boot, you can use the custom boot option of bios: set the custom boot path to \efi\clover\cloverx64.efi, and set it as the first boot, Use bootice or easyUEFI to increase the clover boot option under Windows and set it as the first boot. If you do not have a wireless network card available temporarily, you can use the USB binding function of your Android phone to share the network. This may require the HoRndis driver. It is not recommended to use a US wireless network card. If you need Windows or Linux, you can install it normally. Be careful not to let Windows overwrite your boot files.  
      For other uses of macOS and brew, please pay attention to forums and other communities. Hackintosh is just the beginning.
       
      Finally, I would like to thank rehabman, vit9696 and others who contributed to Hackintosh. I also thank Cwen for his efforts to modify files and hardware tests. I hope that Hackintosh will be eternal.
       
      Please comply with the laws and regulations of your country or region. My description may not be clear or professional, but I think it is necessary. I think the existence of Hackintosh is everyone's technical hobby and experience macOS, not as a substitute for macOS cheap hardware.

      EFI_8x70_5103_W7170m_20200116 .zip
    • By StarFighter_77
      I built this hack years ago now. Started with Lion, now on El Cap. I want to update now to High Sierra.

      I think I messed up my Clover when I downloaded the update .pkg and just installed it without taking my time or customizing the install. Was on Clover r3423, now I think I'm on r5104

      I've been searching and reading this site and others for a few days before making this thread, but I need help compiling what I've learned to get my system running correctly again and ready to update to High Sierra. Then, eventually, I want to update my graphics card, switch to UEFI (if necessary) and update to Mojave.

      I couldn't get system to boot. Could get to Clover and all the options, except the Shell... I hit enter on the Shell and I get black screen and nothing.

      The only way I got it to boot was to add -v to boot args, and change smbios from 14,2 to 13,2. Not sure why that worked still. Also I'm running two monitors, but I can only now run one of them off the Intel 3000 Graphics and the second one off my GFX Card.

      So now I'm afraid to shut down or reboot.... I could really use some help with Clover.

      I'm pretty sure my config file in Clover is not right. Also, some of the files in my Clover backups are not in the new Clover install. (2.5k 5104)

      If someone could please take a look at the files I've attached and help me sort this out, I would be grateful. Thank you, Thank you, Thank you.

      I've attached
      - The last boot log
      - The current Clover folder from the EFI partition after performing Clover update. (.zip)
      - The Clover backup that was working before Clover update (.zip)
      - Library/Extensions Folder (screen shot)
      - System/Library/Extensions Folder (.zip)

      Here is my current hardware:

      Mobo: GIGABYTE GA-Z68MX-UD2H-B3

      CPU: Intel Core i7-2600K

      GPU: GIGABYTE ATI Radeon HD6870 1GB DDR5 2DVI/HDMI/2x

      RAM: Corsair Vengeance Blue 16 GB DDR3 SDRAM Dual Channel Memory Kit CMZ16GX3M4A1600?C9B

      HD0 (for OS and Apps): OCZ Technology 120 GB Vertex Series SATA II Solid State Drive

      HD1 (file storage, Adobe scratch disk): Samsung 1 TB Spinpoint 7200 RPM 32MB Cache SATA

      BURNER: LG CD/DVD Burner Model GH22NS50

      CPU COOLER: Corsair Cooling Hydro Series H50 All in One High-performanc?e CPU Cooler CWCH50-1

      P/S: Antec CP-850 850 Watt CPX Power Supply Unit

      CASE: Antec Performance One P183 V3 Case
      CLOVER.zip
      CloverBackup.zip
      bootlog.txt

      S_L_E.zip
×