Jump to content
ErmaC

Clover General discussion

19,690 posts in this topic

Recommended Posts

2 hours ago, SavageAUS said:

Can this driver please be incorporated into clover package or at least into build_clover script.

Sent from my SM-G930F using Tapatalk

Can this driver please be incorporated into clover package or at least into build_clover script.

Sent from my SM-G930F using Tapatalk
 

Hi, you can try it 

 

Build_Clover.command

 

 

Share this post


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

Rev 4540

New driver developed by savvas https://github.com/acidanthera/ApfsSupportPkg/

You may exclude private apfs.efi from drivers64UEFI folder and place here the driver ApfsDriverLoader.efi.

It performs loading the driver from APFS container by DiskIO protocol.

The driver is open source but located not in Clover repository and at link above. It contains macbuild.tool for those who want to compile by himself.

Hi,

I tried this driver (the prebuilt one) and it completely hangs my system in a way that it never gets to Clover. I don't see a topic about it, so I'm not sure where to report...

Share this post


Link to post
Share on other sites
37 minutes ago, Pene said:

Hi,

I tried this driver (the prebuilt one) and it completely hangs my system in a way that it never gets to Clover. I don't see a topic about it, so I'm not sure where to report...

Please update aptiomemoryfix. Hang occured because MOStartImage in aptiofix didn't check null devicepath inside load image, so it hangs. APFSDriverLoader gives LoadImage source buffer and its size with NULL device path. 

Edited by savvamitrofanov

Share this post


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

Please update aptiomemoryfix. Hang occured because MOStartImage in aptiofix didn't check null devicepath inside load image, so it hangs. APFSDriverLoader gives LoadImage source buffer and its size with NULL device path. 

Yes, that fixed it. Nice work!

By the way, if I have two APFS volumes, say High Sierra and Mojave, will it load the most recent driver?

Share this post


Link to post
Share on other sites
24 minutes ago, SavageAUS said:

.. Does the ApfsDriverLoader work for USB installs?

On my case, my 10.14 USB installer is formatted as HFS+, not really sure if it's needed (pre-install). I just did test placing it within /drivers~ folder and it works to load macOS Mojave with APFS (post-install). Thanks.

Edited by Badruzeus

Share this post


Link to post
Share on other sites

Hi guys,

 

Shouldn't Clover automatically detect if you already have HFSPlus.efi installed, and not push you to install VBoxHfs.efi in this case? I thought it should remember what you have and what you don't have from previous installations, and suggest to keep that configuration by default, when you reinstall/upgrade.

 

Well, in this case, it keeps pushing to install VBoxHfs, although I didn't have it before (it would be a new install) and I already have HFSPlus. Interestingly enough, it doesn't do the same with ApfsDriverLoader.

Is this intended?

 

207371327_Screenshot2018-06-17at00_32_48.png.8c3ee5929b4d8bbd9f2c1d3cfc1773da.png

Share this post


Link to post
Share on other sites

@Slice 

 

Thanks to your latest commits regarding mtoc.NEW locations, I was able to compile Clover 4551 using UDK2018 with no errors anymore. Thank you very much! :) 


By the way, since we can build nasm with ./buildnasm.sh (which has also been fixed), I think we can remove the first steps from the instructions page and add a new line for it under Step nr 4 (Prepare sources).

 

Also, to avoid error

./edksetup.sh: line 149: return: can only `return' from a function or sourced script

when invoking that script with "./" , maybe we can update the instructions so that it will be invoked with  ". edksetup.sh" instead. This should work perfectly fine.

 

Just a few ideas, of course. :)

Edited by arsradu

Share this post


Link to post
Share on other sites
3 minutes ago, arsradu said:

@Slice 

 

 

 

Also, to avoid error


./edksetup.sh: line 149: return: can only `return' from a function or sourced script

when invoking that script with ./, maybe we can update the instructions so that it will be invoked with  ". edksetup.sh" instead. This should work perfectly fine.

 

 

I don't know it. Never encounter.

Share this post


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

I don't know it. Never encounter.

 

Really? :)))

 

Cause I always do...when building with UDK2018. And, even though I'm building in Mojave (Xcode 10)...I doubt this has anything to do with it.

 

192-168-0-116:UDK2018 jimmy$ ./edksetup.sh
Loading previous configuration from /Users/jimmy/src/UDK2018/Conf/BuildEnv.sh
WORKSPACE: /Users/jimmy/src/UDK2018
EDK_TOOLS_PATH: /Users/jimmy/src/UDK2018/BaseTools
CONF_PATH: /Users/jimmy/src/UDK2018/Conf
./edksetup.sh: line 149: return: can only `return' from a function or sourced script
192-168-0-116:UDK2018 jimmy$ 

 

Edited by arsradu

Share this post


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

But it is not our script. Report to EDK2-devel group.

 

I think it's already been reported...here: https://patches.linaro.org/patch/79255/

 

If I got this right, they say that invoking the script with ./ is actually not ok for this case. I'm not sure why. I'm not an expert. This is just what I got from it...

Edited by arsradu

Share this post


Link to post
Share on other sites

bdmesg started to report faulty version number:

3:616  0:000  Starting Clover revision: 01314556 on CLOVER EFI

Do the ebuild.sh script update the Version.h file?

Here is mine:

#define FIRMWARE_BUILDDATE "2018-06-17 15:46:09"
#define FIRMWARE_REVISION L"01314556"
#define REVISION_STR "Clover revision: 01314556"
#define BUILDINFOS_STR "Args: -n 9 -t XCODE8 --vbios-patch-cloverefi --only-sata0 --no-ext -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 --x64 | -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 -D ENABLE_VBIOS_PATCH_CLOVEREFI -D ONLY_SATA_0 -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.5 | XCODE: 9.4"

So the script should be faulty...

Share this post


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

bdmesg started to report faulty version number:


3:616  0:000  Starting Clover revision: 01314556 on CLOVER EFI

Do the ebuild.sh script update the Version.h file?

Here is mine:


#define FIRMWARE_BUILDDATE "2018-06-17 15:46:09"
#define FIRMWARE_REVISION L"01314556"
#define REVISION_STR "Clover revision: 01314556"
#define BUILDINFOS_STR "Args: -n 9 -t XCODE8 --vbios-patch-cloverefi --only-sata0 --no-ext -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 --x64 | -D USE_LOW_EBDA -D NO_GRUB_DRIVERS -D NO_GRUB_DRIVERS_EMBEDDED -D EXIT_USBKB=1 -D ENABLE_VBIOS_PATCH_CLOVEREFI -D ONLY_SATA_0 -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.5 | XCODE: 9.4"

So the script should be faulty...

All OK

0:100  0:000  Now is 17.6.2018,  15:52:50 (GMT)
0:100  0:000  Starting Clover revision: 4558 on American Megatrends EFI

Share this post


Link to post
Share on other sites
6 minutes ago, Ukr55 said:

All OK

0:100  0:000  Now is 17.6.2018,  15:52:50 (GMT)
0:100  0:000  Starting Clover revision: 4558 on American Megatrends EFI

I removed the file, and tried to build with ebuild.sh, same issue. Somewhere along there is an error.

Share this post


Link to post
Share on other sites
9 minutes ago, Ukr55 said:

All OK

0:100  0:000  Now is 17.6.2018,  15:52:50 (GMT)
0:100  0:000  Starting Clover revision: 4558 on American Megatrends EFI

I removed the file, and tried to build with ebuild.sh, same issue. Somewhere along there is an error.

 

Edit: I found the culprit:

Change the line 614 in the ebuild.sh to 

		repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}')

So here is the diff:

614c614
< 		repoRev=$(svn info | grep "Revision" | tr -cd [:digit:])
---
> 		repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}')

 

Share this post


Link to post
Share on other sites
33 minutes ago, smolderas said:

I removed the file, and tried to build with ebuild.sh, same issue. Somewhere along there is an error.

 

Edit: I found the culprit:

Change the line 614 in the ebuild.sh to 


		repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}')

So here is the diff:


614c614
< 		repoRev=$(svn info | grep "Revision" | tr -cd [:digit:])
---
> 		repoRev=$(svn info|awk '{ if ($1=="Revision:") {print $2}}')

 

Why ome method is better then another? What is your subversion client version?

What is full output of "svn info" in EDK2 folder? In UDK2018 folder?

Share this post


Link to post
Share on other sites

I tried some hours getting iMessage to work, after updating to 10.13.5. After many testing, i found that CLOVER was to blame. Before i updated to 10.13.5, i installed CLOVER 4498 (coming from 4428).

 

Any CLOVER Version i tried prevented activating iMessage (iMessage Error in systemlog: 13)

 

I tried 4497, 4509, 4458 and 4522. Rolling back to CLOVER 4428 brought back the capability to activate iMessage. iMessage is set up correctly regarding ROM and MLB and never was a issue before.

 

 

Any ideas?

 

Share this post


Link to post
Share on other sites

Hi guys,

 

Are the drivers that Clover proposes for installation documented anywhere? I know some of them are. But I couldn't find a proper description for most of them.

And the description within the installer itself is far from being...descriptive enough. :))

 

So, unless you used them before, or you somehow know what they are good for, it's very hard to choose the right ones. Rule of thumb is usually start with only a few ones. But how do you know WHICH ones? Especially since they're not grouped in any way. You don't know which ones are good for what.

 

Some of them are documented here, for as far as I could see. Some of them are in Clover Change Explanations thread...and some others probably scattered throughout the forum.

 

I can collect them in a single thread, that's not a problem (in case nobody did that already). Although, in my opinion, the first place where they should be documented, is on the Clover Wiki. After that, they should be in the actual description box of the installer itself.

 

Still, in order to do that, I would still need a good description for each one of them, in terms of what they are, and what are they good for. Also, whether or not they create conflicts with other drivers.

 

Edited by arsradu

Share this post


Link to post
Share on other sites
17 hours ago, ApexDE said:

I tried some hours getting iMessage to work, after updating to 10.13.5. After many testing, i found that CLOVER was to blame. Before i updated to 10.13.5, i installed CLOVER 4498 (coming from 4428).

 

Any CLOVER Version i tried prevented activating iMessage (iMessage Error in systemlog: 13)

 

I tried 4497, 4509, 4458 and 4522. Rolling back to CLOVER 4428 brought back the capability to activate iMessage. iMessage is set up correctly regarding ROM and MLB and never was a issue before.

 

 

Any ideas?

 

I too have the same issue, I was trying to find the culprit. I'll take a look at it on the weekend.

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