Jump to content
ErmaC

Clover General discussion

22,503 posts in this topic

Recommended Posts

Advertisement

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
On 6/15/2018 at 9:29 AM, Sherlocks said:

 

this is awesome driver.

OsxAptioFix2Drv-free2000

and

OsxAptioFixDrv on sandy laptop(10.6~10.13).

 

there is no problem.

thank you so much.

 

Do you use both OsxAptioFix2 together on the same laptop? I have a sandy bridge laptop and use AptioFixDrv and works but I have some glitches and sometimes the display freezes.

 

What about you? no freezes/glitches? I have 8GB of RAM.

 

I'm gonna try OsxAptioFix2Drv-free2000 alone later.

Edited by el_charlie

Share this post


Link to post
Share on other sites
On 6/18/2018 at 6:30 AM, smolderas said:

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

UGH!! Right about June 6 my Messages/Facetime, which have been working for many years, just stopped working. It wouldn’t activate. I spent at least eight hours on Monday trying to figure out why. I deleted pref files, even changed my rock solid config file with new serial number, board serial, ROM, MLB, etc. I even called Apple which I know was a stupid idea.

 

So others are having this same issue? I tried to go back to version 4497 but it didn't work. I think I've screwed something up with Apple activation servers now.

Share this post


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

UGH!! Right about June 6 my Messages/Facetime, which have been working for many years, just stopped working. It wouldn’t activate. I spent at least eight hours on Monday trying to figure out why. I deleted pref files, even changed my rock solid config file with new serial number, board serial, ROM, MLB, etc. I even called Apple which I know was a stupid idea.

 

So others are having this same issue? I tried to go back to version 4497 but it didn't work. I think I've screwed something up with Apple activation servers now.

i am not alone!!! right, something like that. yesterday I tried to fix but...

Share this post


Link to post
Share on other sites

Following the discussion from the separate topic (good investigation, guys!), it seems that the iMessage problem originates from the change at device-inject.c from commit 4497.

 

Before this commit, built-in property injection for LAN was being made by default.

Starting with 4497, an option to control this feature was added, with its default being set to FALSE (so built-in property is being injected only when LANInjection setting is activated).

 

And as we already confirmed in the past, iMessage activation is insisting on the built-in property to exist on some device in order to activate, even if the actual connection is from a different network device.

Perhaps we could consider setting LANInjection default to TRUE, to avoid breaking iMessage for people that are relying on this.

 

Edited by Pene

Share this post


Link to post
Share on other sites
Just now, KGP-iMacPro said:

 

AptioMemoryFix.efi for me works flawless and also is up-to-date.. Give it a try.. The same states for VBoxHfs.efi.. you might realise that HFSPlus.efi is not needed when using VBoxHfs.efi :wink_anim:

 

Yes, it is not needed. For as far as I know, they both do the same thing. BUT....I head VBoxHFs is slower. That's why I'm using HFSPlus in the first place. But maybe I was wrong about this, as well... 

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.

Announcements

  • Similar Content

    • By pink101
      So, here's what i think clover do when it patch ati framebuffer, first it read a cached kext, then it search the original hex value of the connector, then it changed the value with the new one. Is it correct? now, here's what i find confusing... let's say that i want to patch AMD7000Controller.kext, in that kext, i want to patch "AJI" framebuffer with a new value, so clover try to find the hex value of "AJI" connector then replace it with the new one, simple right? but when i search the AMD7000Controller binary file for other framebuffer, some of them didn't exist in the binary, for example, i tried to patch "Ramen" framebuffer, from various source, it said that:
      Ramen (6) @ 0xeba70 LVDS, HDMI, DP, DP, DP, DP 020000000001000039050108000000002001050600000000 000800000402000000010200000000001000030500000000 000400000403000000010343000000001102010100000000 000400000001000000010431000000002103040300000000 000400000403000000010563000000001204020200000000 000400000001000000010651000000002205040300000000 So i open a hex editor and search for:
      020000000001000039050108000000002001050600000000000800000402000000010200000000001000030500000000000400000403000000010343000000001102010100000000000400000001000000010431000000002103040300000000000400000403000000010563000000001204020200000000000400000001000000010651000000002205040300000000 but, it turns out that hex editor couldnt find that hex value in AMD7000Controller,

       
      most of the framebuffer exist in the AMD7000Controller, but some doesnt, If this is the case, then, where does clover find the original framebuffer to be patched? am i missing something?
       
       
    • By tluck
      Lenovo T460 macOS with Clover Guide
      Latest Release on GitHub (July 2020) Updated to Clover r5120 Updated Lilu based kexts - Lilu, ALC, WEG Added AirportBrcmFixup.kext
        Various Tweaks over Last months The main branch in my github repo is a complete Clover ESP (/EFI) bundle and kext pack for the Lenovo T460. The current file bundle seems to work on Sierra, HighSierra, Mojave and Catalina. There is an OpenCore branch in the repo as an alternative to Clover. This guide was developed for a Clover implementation. But the thread has evolved to include discussion of both Clover and Opencore for these systems: T460 and T470 family of ThinkPads.
       
      Full Clover file set - config.plist etc. Includes all custom kexts Includes custom DSDT/SSDT scripts and patches Utility scripts The zip bundles are posted to GitHub: https://github.com/tluck/Lenovo-T460-Clover/releases
      Caveat: The T460 systems used here was configured with: i5-6300U, Intel HD Graphics 520, 1920x1080 touch screen. If you have a different system model, then extract the ACPI files and use the included scripts to create a set of files consistent with your system type and BIOS version. See below for details.
      Credits: RehabMan, Shmilee, vusun123, TimeWalker, Mieze from which, much of their work and help is/was was used to get the T460 to this point.
      Devices and aspects working:
      Ethernet -  Intel I219LM is enabled via IntelMausiEthernext.kext WiFi/BT - substitute the Intel WiFi/BT with a compatible Broadcom or Atheros chip Audio - ALC293 codec implemented via AppleALC.kext (the old AppleHDA_ALC293 and CodecCommander kexts are not needed) PS2 - ClickPad + TrackPoint + all 3 buttons - using a modified VoodooPS2Controller to support new layouts - and added some custom Fn key maps based on 440/450 dsdt USB - implemented via custom SSDT + USBInjectAll kext. All USB3/USB2 ports are intel-based and work -  3 external USB and internal Camera, BT, etc  Sleep/Wake - the sleepwatcher package and custom sleep/wake scripts are used to help with sleep/wake for BT and PS2 devices. Note: have not tried to implement the SD card reader - no driver found.
      ACPI Files
      New Installation - Steps and Details
      Part 1 - OS Installation
      Part 2- Post OS Installation and Setup
      Notes on Custom Kexts
       
    • By tlefko
      News
      In light of the recent WWDC, we will begin testing the functionality of our EFI on macOS 11 for this device with the latest developer preview Version Info
      Features and Overview
      Now Compatible with 10.15.6 Please leave feedback with issues or w/o Comitted to Updating up to OS 11 Multitouch Trackpad Support 4K @60 Hz Fixed Bluetooth and Wifi Stability Issues Preformance and Power Management Additional Patches for 4K Display updated for 15.6 rev 1 Sleep Wake is functional for some models ----if screen glitches on wake or reopen lid. If this is a bother just disable sleep. This is issue is resolved in Big Sur Bugs
      Some models may experience screen split in half. If so disable. USB devices eject (external) No Internal Mic What Works
      Everything minus sleep issue above, internal microphone. (audio is fine, headphones / usb mic fine, just not laptop mic) POST
      run sudo pmset -a hibernatemode 0
      Description
      This esentially an ultra-simplistic version that is stable without the use of a deploy or complicated file installations and copies. You can easily view all the DSDT patches along with configuration files for the bootloader as they are all documented clearly in the files. This does include a copy of Clover, which of course I do not contribute to and am only responsible for the provided files, patches, and kext placements This guide provides a working setup with little knowledge of the topic and without "optimization" (because often they can break things). But, it is fully functional and preforms properly and is stable.
      Unsupported Wifi
      Make sure you are using DW1560 or 1820a for wifi or else there is a risk of KP. If not using remove BRCM kexts from CLOVER>kexts>other Styling
      This guide is designed to be literally as thorough as possible to appeal all types of users. It does not cover complex topics like undervolting etc etc only to provide a completely functional system
      Notes
      Never tested USB C except for charging, USB, works great (not sure about DispOut) 4K model has sleep wake issues occasionally, 1080P is fully functional BIOS
      Disable Secure Boot Disable Vt-d Recommended: Clean Install (Preinstall steps)
      Format a USB (16GB) as Journaled and then proceed to download the latest Catalina Installer Patcher Application. Download the latest Catalina installer from within the Patcher App, and select to download a new copy and install to your USB device Download the clover configurator application and mount the EFI of the USB partition, then copy the contents of the Files linked above to A new EFI Folder (that you create) within the EFI partition. ** This is because the App Store installers will often not download a full installer, just an truncated version that downloads the installer files from the interent while installing. Thus, they're not bootable from a USB as they're not complete. That is why you should use this method to make sure the installer is usable for bootable media.
      Boot From USB
      Use f9, copy EFI folder to efi partition of your usb. after installation complete copy EFI to your ssd. Boot Entry Setup
      Reccomend using windows to find a tool to add a UEFI bios entry to boot EFI/Boot/bootx64 Credits
      @MaLd0n for DSDT Patches and support (HUGE SHOUTOUT) Original Kexts Authors Clover Headphones and Audio
      All audio from speakers should work perfectly along with Bluetooth and USB audio Finished!
      Congratulations, there really aren't any more steps that are required. Feel free to contact me with any questions.
      Donations
      Send me a coffee lefkotyler@gmail.com
      EFI Catalina.zip
       
      **for latest releases and faster replies please refer to GitHub https://github.com/tlefko/HP-ENVY-13-2020-Catalina
    • By geheim19
      I’m new here and hope a lot of answers to my questions to find.
       
    • By STLVNUB
      *Put the script into its own folder as it will create other folders*
      What is BTB?
      Script file to clone and help build Clover or Opencore repos
      Script will create link to itself in /usr/local/bin/bob
      Script SHOULD fix up any stray bobs you may have.
      Then you only need to type bob. and a parameter
      "a" for ACID repo, official
      "d" for ACID repo DUET build
      "c" for CLOVER
      "e" to erase UDK Folder
      Easier typing bob than.....usual stuff
      YOU WILL NEED TO cmod+x THE SCRIPT
      Enjoy
       
×