Jump to content
ErmaC

Clover General discussion

19,692 posts in this topic

Recommended Posts

27 minutes ago, arsradu said:

But it couldn't have been that easy, now could it? :)) Now it says there is ' nothing to be done for "all" '.

 

Well, I disagree. I think there are a plenty of things to be done. For all! :)) Not sure what does it mean by that.

./ebuild.sh cleanpkg

Share this post


Link to post
Share on other sites
Advertisement

Hi guys...

 

while everything just worked fine with Clover_v2.4k_r4522, system boot fails on both my X299 and X99 Systems with clover Clover_v2.4k_r4532. After several months,  I am again confronted with memory allocation errors or system boot failures at *********.

 

Did you change once more AptioMemoryFix.efi,  or what is the source of the problem? 

 

If I change back to Clover_v2.4k_r4522, everything works as expected. 

 

This morning I was able to download and build Clover_v2.4k_r4532 with Build_Clover.command on my X99 system after deleting the "src" directory in my home directory. However, on my X299 system, the clover build failed even after deleting the src directory and rebuilding clover from scratch.

 

Now , when I try to download and build clover from scratch, I also get server connection errors as already reported by others... 

 

Any thoughts on the above? Hope we can find the way back to a working clover configuration. 

 

Cheers,

 

KGP

 

Share this post


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

May be you should update svn client? I have


Subversion command-line client, version 1.8.11.

Apache version is 1.10.1 https://subversion.apache.org/packages

 

Hmm...

 

"Brew install subversion" reveals the following errors:

 

957582419_Screenshot2018-06-11at20_49_03.png.3c349332f779f4aaea6a2b11fd5153e2.png

 

I don't use Xcode 10.0 beta. Still with Xcode 9.4. The same states for the Command Line Tools. 

 

Although now I can do the initial clover download and step 2 without problems. The download is still slow though .. 

 

1799717016_Screenshot2018-06-11at20_45_44.png.a5f84929990880408e671b6c59655064.png

 

However, when building the existing revision for release (5), I still get the following error on my X299 rig, while (5) works fine on my X99 rig:

 

95305492_Screenshot2018-06-11at20_44_45.png.662d4b3d0b47635962278bd576e87bca.png

 

I am now left with the NASM issue on X299, mentioned in several posts before? 

 

All this apart from the remaining AptioMemoryFix.efi issue apparently persistent in Clover_v2.4k_r4532.... Can you please compare version of AptioMemoryFix.efi included in Clover_v2.4k_r4522 (working) and  Clover_v2.4k_r4532 (not working).. ?

 

Edited by KGP-iMacPro

Share this post


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

sudo mkdir /opt

sudo mkdir /opt/local

sudo mkdir /opt/local/bin

mkdir -p is your friend...

9 minutes ago, KGP-iMacPro said:

I am now left with the NASM issue on X299, mentioned in several posts before?

Then read how arsradu solved it.

Edited by Zenith432

Share this post


Link to post
Share on other sites
7 minutes ago, KGP-iMacPro said:

 

I am now left with the NASM issue on X299, mentioned in several posts before? 

 

All this apart from the remaining AptioMemoryFix.efi issue apparently persistent in Clover_v2.4k_r4532.... Can you please compare version of AptioMemoryFix.efi included in Clover_v2.4k_r4522 (working) and  Clover_v2.4k_r4532 (not working).. ?

 

NASM issue discussed few posts before.

4522 is from sf.net? It is my compilation.

4532 is from where? Who is the creator?

Share this post


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

I tried to download the sources manually and then run that script...but that didn't work. It still tries to connect to SVN...which again is down. So...that's why I was asking for an updated build method, using sources already downloaded (assuming I can download them without SF cutting my connection over and over again).

if sf is down, you cannot checkout Clover as well. problem solved:D

Share this post


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

NASM issue discussed few posts before.

4522 is from sf.net? It is my compilation.

4532 is from where? Who is the creator?

 

4522 downloaded from sourceforge.net

4532 downloaded and build with Build_Clover.command 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
14 minutes ago, KGP-iMacPro said:

 

All this apart from the remaining AptioMemoryFix.efi issue apparently persistent in Clover_v2.4k_r4532....

 

2 minutes ago, KGP-iMacPro said:

 

4532 downloaded with Build_Clover.command 

Test this file

AptioMemoryFix.efi.zip

Or choose OsxAptioFix3Dxe-64.efi from Clover package instead.

Share this post


Link to post
Share on other sites
Generating BootSectors
[NASM] boot0af.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0af
[NASM] boot0ss.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0ss
[NASM] boot0md.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0md
[NASM] boot1h.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1h
[NASM] boot1h2.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1h2
[NASM] boot1f32.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1f32
[NASM] boot1f32alt.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1f32alt
[NASM] boot1x.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1x
[NASM] boot1xalt.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1xalt
Description.txt -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/Description.txt
Installation.txt -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/Installation.txt
Done!
192-168-0-116:Clover jimmy$

What now? :))

 

I love how it just says "Done !" like "all fine here". But I have no freaking Clover installer!!!

Edited by arsradu

Share this post


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

 

Test this file

AptioMemoryFix.efi.zip

Or choose OsxAptioFix3Dxe-64.efi from Clover package instead.

 

Allright..

 

just realised that AptioMemoryFix.efi does not seem to be part of Clover_v2.4k_r4532 at all. Thus, when installing the Clover_v2.4k_r4532 package, it simply get's removed!

 

That's what caused all my boot issues independent from 10.13.5, 10.13.6, 10.14 or X299 and X99. If I include the AptioMemoryFix.efi, which you attached above after the  Clover_v2.4k_r4532 package installation, all works as expected and system boot of both rigs is just fine!

 

Without any intention to offend anybody :-) My experience with AptioMemoryFix.efi is just gorgeous, while I faced several issues with OsxAptioFix3Dxe-64.efi derivatives during the last months.  Thus, would it be possible to implement AptioMemoryFix.efi in the Clover build to be downloaded with the Build_Clover.command? 

 

BTW.. Why do you still include OsxAptioFix2Dxe-64.efi and OsxAptioFixDxe-64.efi, which seem not to work at all? 

 

Yet it does not seem clear to me from the previous posts how to properly solve the NASM issue... 

 

 

 

 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
32 minutes ago, KGP-iMacPro said:

Yet it does not seems clear to me form the previous posts how to properly solve the NASM issue... 

 

Two things you have to do to try and fix the NASM issues.

 

1. do a nasm -v in Terminal to see which version are you currently using. It's most likely outdated.

 

It should say something like this. If it doesn't, go to step 2. :)

NASM version 2.13.03 compiled on Feb  7 2018

2. to use that version, make sure your nasm file is downloaded from https://www.nasm.us/pub/nasm/releasebuilds/2.13.03/macosx/nasm-2.13.03-macosx.zip and is included in the $PATH.

Create /opt/local/bin and put it there, but don't forget to also add /opt/local/bin to your actual path (in case you don't already have it).

 

If everything ok, when you do nasm -v, you should see the correct version .

 

Edited by arsradu

Share this post


Link to post
Share on other sites
2 hours ago, arsradu said:

 

Two things you have to do to try and fix the NASM issues.

 

1. do a nasm -v in Terminal to see which version are you currently using. It's most likely outdated.

 

It should say something like this. If it doesn't, go to step 2. :)


NASM version 2.13.03 compiled on Feb  7 2018

2. to use that version, make sure your nasm file is downloaded from https://www.nasm.us/pub/nasm/releasebuilds/2.13.03/macosx/nasm-2.13.03-macosx.zip and is included in the $PATH.

Create /opt/local/bin and put it there, but don't forget to also add /opt/local/bin to your actual path (in case you don't already have it).

 

If everything ok, when you do nasm -v, you should see the correct version .

 

 

Now?

 

1306307292_Screenshot2018-06-12at00_06_41.png.7a72370aff519292c6b7020c81d9de03.png

 

1029068988_Screenshot2018-06-12at00_11_20.thumb.png.1ca62d0f081191c80115dd2e652e7bda.png

Share this post


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

I just run build_clover script under Ubuntu 18.04 and also got issue with network connectivity.. it seems something wrong with the server but I'm not really sure, done with local ~/src rebuilt from scratch this morning under mac, then tonight we see this.

Screenshot from 2018-06-11 23-45-12.jpg

 

1.PNG.c144f6d9e75ceae8f422373e57e10d62.PNG

 

in my case, host force to disconnected my connection. maybe sf dowload file size max is 48.01mb at once? what is happen in sf? strange...

Share this post


Link to post
Share on other sites
56 minutes ago, Sherlocks said:

in my case, host force to disconnected my connection. maybe sf dowload file size max is 48.01mb at once? what is happen in sf? strange...

 

I gave up on SF. I'm not even gonna try. Looks like they have their servers on a boat. Every time the wind blows, they go offline.

Share this post


Link to post
Share on other sites
5 hours ago, KGP-iMacPro said:

Now?

Hmm... Not sure.

Can you do ./ebuild.sh cleanpkg and try to build again?

Also, could you, please, do echo $PATH in Terminal and post the output? Is nasm added to opt/local/bin ?

 

 

Edited by arsradu

Share this post


Link to post
Share on other sites

But why we need to add a PATH to opt/local/bin?

There is already

  if [[ -f "/opt/local/bin/nasm" ]]; then
    export NASM_PREFIX="/opt/local/bin/"
  elif [[ -f "${TOOLCHAIN_DIR}/bin/nasm" ]]; then
    # using $TOOLCHAIN_DIR here should allow Clover source to be
    # inside any sub folder instead of only in ~/
    export NASM_PREFIX="${TOOLCHAIN_DIR}/bin/"
  else
    export NASM_PREFIX=""
  fi

ebuild.sh do this automatically!

Is it a mistake of build_clover_command?

 

EDITED: It is a mistake of tools_def.txt which didn't contain right NASM_PATH for XCODE8 toolset.

Fixed in 4533.

Share this post


Link to post
Share on other sites

The per-toolchain definitions are redundant because of a default

##################
# NASM tool definitions
##################
*_*_*_NASM_PATH                = ENV(NASM_PREFIX)nasm
# NASMB uses NASM produce a .bin from a .nasmb NASM source file
*_*_*_NASMB_FLAGS              = -f bin

But build of Clover.dsc uses ${NASM_PREFIX}nasm

and BootHFS/Makefile uses just "nasm" from ${PATH}

Which can be different.

${PATH} always contains ${TOOLCHAIN_DIR}/bin because of pathmunge in ebuild.sh.

But ${PATH} may not contain /opt/local/bin - which is where correct version may be installed with only other version in ${PATH} is outdated Apple nasm.

I think that's cause of mismatch.

Share this post


Link to post
Share on other sites

Morning guys! :)

 

Well, I downloaded sources for 4533 and tried to compile. But....I got stuck at exactly the same point. No error. But...no build either. I'm not sure how does it work for you... :)))

@Slice thank you very much for the updated build. :)

Generating BootSectors
[NASM] boot0af.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0af
[NASM] boot0ss.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0ss
[NASM] boot0md.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot0md
[NASM] boot1h.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1h
[NASM] boot1h2.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1h2
[NASM] boot1f32.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1f32
[NASM] boot1f32alt.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1f32alt
[NASM] boot1x.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1x
[NASM] boot1xalt.s -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/boot1xalt
Description.txt -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/Description.txt
Installation.txt -> /Users/jimmy/src/UDK2018/Clover/CloverPackage/CloverV2/BootSectors/Installation.txt
Done!

Clover descriptions are fixed. But...shouldn't there be a feature to help people check only the relevant/non-mutually exclusive drivers? I thought there should be. But maybe I got this wrong.

 

The idea is to make sure people (especially new users) don't select (as I actually saw this before) ALL the drivers in Drivers64UEFI, simply because they don't know which ones they need.

In short, my opinion is that, the installer shouldn't allow you to just check ALL drivers. Or if you do that, it should only select the ones that are not mutually exclusive/redundant.

That's another reason why I think grouping Drivers by their purpose is a good idea. It makes it a lot clearer to new users.

 

Just like we did with "install for UEFI booting only" which, once checked, will disable legacy options, since they don't go together, the same way we could do for the Drivers options. Once one of them is checked, the other one needs to be disabled, if it's not compatible, or if it's redundant.

 

249469627_Screenshot2018-06-12at09_07_54.png.56ef13f5299b2442573d8dfe0a69b398.png

Edited by arsradu

Share this post


Link to post
Share on other sites
6 minutes ago, KGP-iMacPro said:

@arsradu, @Slice

 

Error still persistent with 4533.. 

 

 

Yep... I'm not sure why do you get an error though... I'm also stuck, as you can see above. But there is no error in my case.

You have Java installed, right? I remember that was necessary for building.

 

By the way guys, do you need JDK for building or you can use JRT as well? I got the JDK just in case. But...I'm not sure if it actually makes a difference here.

Share this post


Link to post
Share on other sites
4 hours ago, Sherlocks said:



1.PNG.c144f6d9e75ceae8f422373e57e10d62.PNG

in my case, host force to disconnected my connection. maybe sf dowload file size max is 48.01mb at once? what is happen in sf? strange...

Using @Pene's method here, seems better to me. I have SF account already so nothing to worry.
Hhh, build succeeded moment ago, but when open this.. it has been released hours ago, what worsing my time #lol

Screenshot 26.png

Edited by Badruzeus

Share this post


Link to post
Share on other sites

what is pene method? need to login? download source before? how about source download in linux?

Using [mention=42278]Pene[/mention]'s method here, seems better to me. I have SF account already so nothing to worry.
Hhh, build succeeded moment ago, but when open this.. it has been released hours ago, what worsing my time #lol
1263425089_Screenshot26.png.b11c61a5466d03badd629cac4057bb17.png


나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites
12 minutes ago, Sherlocks said:

what is pene method? need to login? download source before? how about source download in linux?

 

Oops, sorry was missing link on prev. post. I mean HERE

Edited by Badruzeus

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   1 member

  • Similar Content

    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
    • By metaphysician
      hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer

      i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
       
      however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    • By Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
×