Jump to content
ErmaC

Clover problems report & features request

710 posts in this topic

Recommended Posts

Advertisement
On 4/2/2019 at 9:47 AM, Download-Fritz said:

 

Let me second that real quick, utter rubbish, please stop spreading FUD. The kext data to link, i.e. the executable and the Info.plist, are put in a buffer that resides in the booter's Device Tree memory, then it is picked up by the kernel from there and linked into the kernel space, as any kext is. The mechanism used to inject kexts now is literally the Apple mechanism to boot without kextcache several versions ago.


I'm not a computer engineer, so please don't be aggressive. I understand what you and the others explained. I've been building hackintoshes for me and friends for about ten years, so I have no interest in spreading rubbish, nor am I naive enough to not be able to understand the meaning and implications of choices like this one, of a kext, flag or whatever. 
Sadly, I have no time to further discuss this, given that I've been experiencing random and quite fast KP reboots once or twice a day. The system never had a single issue, literally the only change I made this month was moving all my kexts from L/E to Extra, but I'm sure there is no relation: post hoc ergo propter hoc, right? This is going off-topic though, sorry for that.

Share this post


Link to post
Share on other sites
Posted (edited)
17 hours ago, Power Mac said:


I'm not a computer engineer, so please don't be aggressive. I understand what you and the others explained. I've been building hackintoshes for me and friends for about ten years, so I have no interest in spreading rubbish, nor am I naive enough to not be able to understand the meaning and implications of choices like this one, of a kext, flag or whatever. 
Sadly, I have no time to further discuss this, given that I've been experiencing random and quite fast KP reboots once or twice a day. The system never had a single issue, literally the only change I made this month was moving all my kexts from L/E to Extra, but I'm sure there is no relation: post hoc ergo propter hoc, right? This is going off-topic though, sorry for that.

 

Yeah, no problem because this will be the last time I respond. No one said you were a computer engineer but I'm going to go ahead and say you have completely no idea what you are talking about. You've been building hackintoshes for ten years?? But yet you don't even know how clover works, also that clover doesn't even have an Extra folder, that you don't even know how to see what is causing the panic and fix it, that installing to /L/E is stupid for any kext you need to boot, because you won't be able to run the installer to upgrade, and also some kexts do not work properly if they are not injected, so no idea what you mean. No one said inject all your kexts, in fact I am now explicitly stating it to you for the FOURTH time, INJECT KEXTS THAT ARE NEEDED TO BOOT OR REQUIRE INJECTION AND PROPERLY INSTALL THE REST. For the sake of everyone in the world's sanity, stop reading tonymac! That website is full of trash and misinformation, and why every other hackintosh site literally will remove anything to do with that site, and even ban you for repeatedly doing it. Not to mention that you are far more likely to be banned from that site for just saying something inane than anywhere I have ever seen. I just googled install unsigned kexts and found several guides that literally are almost word for word copies, it's like no one there can actually do anything but look at the same site and make the same posts with the same wrong information. They don't even have consistent information, I will go over that below because I see this exact same block of text in multiple places on that site and it is wrong. Also, I really hope you don't use any of those tools from that site because you have absolutely no idea what they do and they sign stuff with an actual developer certificate so they can pretty much install any sort of malware and you'd have absolutely no idea unless you knew what to look for, which it's obvious you would not. And hilariously those tools are all available from the actual developers, tonymac just steals everything to make advertising money off unsuspecting people like yourself. There's very little useful information on that site and I only trust two people because I know that they research and go else where too, Rehabman and Toleda.

 

The previous three times, I stated to inject kexts needed for booting and that don't work unless injected:

 

Destroying this idiotic statement I see all over tonymac:

Injected Kexts live outside of "protected MacOS memory" *
...
* Note: I use the term "protected MacOS memory" in this guide as a generic descriptive term. In reality kext's installed in /L/E are loaded into MacOS's kernel memory which is 'protected' (IE: segregated) form application memory and execution memory. Everything running in kernel memory (including kexts) is actively managed and monitored by MacOS.

Doesn't realize that every kext must be in kernel memory or it couldn't work, also how would it be extending the kernel if it wasn't? You know, the main purpose of a kernel extension....? Every kext no matter what is placed into kernel memory.

Injecting a large amount of kexts can result in an unstable system.

This is somewhat true, but unless you have very little memory (less than the requirement for macOS) it's most likely not going to be any issue since at most this may be a few hundred MBs (which even that is extremely high and you are probably more likely injecting somewhere around a few to maybe tens of MBs). You actually have a higher chance of having too many devices cause more memory problems than this, also newer aptio fix helps alleviate this issue by placing the kernel in any random position that is still available for KASLR.

Many 3rd party kexts will not work correctly when injected by Clover.

Then it doesn't need injected. The only reason to inject kexts is to boot and because they need to be loaded and initialized before other kexts that are in the kernelcache, especially ones that are prioritized by the kernel.

 

EDIT: I forgot that the kext doesn't work because you injected the kext before its prerequisite kexts were initialized. If you force load those prereq kexts it will work, however you now run the risk of one of the injection only kexts that patch any of those kexts to possibly fail to do so.

Injected Kexts are not included in the kernel cache and thus are excluded form MacOS error checking.

I don't even know how to respond to this. This is just so utterly stupid. First, every kext is loaded by the kernel, checked, and initialized, no matter what. This scenario here would be equivalent to using kextload to only load a kext temporarily, it's not in the cache but it's certainly in kernel memory and checked....

Installing kexts in /Library/Extensions is the Apple endorsed and recommended location for all 3rd Party kexts.

Ok, that's wonderful, and has absolutely nothing to do with how to boot macOS because you can't really do that without injecting kexts or making special installers every time and constantly installing kexts every time you use the installer...

If you purchase a piece of hardware that requires the installation of a manufactures MacOS driver, the kexts will be installed in /Library/Extensions so why treat hackingtosh kexts any different ?

Because a hackintosh IS different, if it wasn't, clover would not be needed in the first place. You can install stuff into /L/E all day but if you need that kext to boot, because of my last point it's not really that helpful is it...?

 

EDIT: Typos.

 

EDIT2: I totally forgot about RampageDev, where he removed his posts from tonymac because they were being jerks, so they sent a DMCA request against his site because it had the same information. Or Mieze (who wrote like every network driver) got banned for pointing out that one of the drivers from tonymac was from an open source linux GPL driver, which requires the source code to be released and they refused. Why would they do that? Probably because it does something that they don't want people to know about. Not to mention literally everything on the site is stolen, modified(?), and closed sourced, which is pretty much against the license of almost every project. In fact, they are currently violating the clover license as well as they actually are not allowed to use the name of the project or authors without the written consent of the project.

Edited by apianti

Share this post


Link to post
Share on other sites

There's a ticket on SourceForge about this. The installer fails to find the ESP partition of APFS-formatted Fusion Drives and instead installs Clover to the system root. To update I have to manually copy those files to the ESP partition. I'm not sure if the same issue occurs with AppleRAID volumes, APFS or not.

Share this post


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

There's a ticket on SourceForge about this. The installer fails to find the ESP partition of APFS-formatted Fusion Drives and instead installs Clover to the system root. To update I have to manually copy those files to the ESP partition. I'm not sure if the same issue occurs with AppleRAID volumes, APFS or not.

Yes, known problem with all system volumes in a container partition. It is detection problem in installer, workaround is exactly what you are doing for now...

Share this post


Link to post
Share on other sites
8 hours ago, shrieken213 said:

There's a ticket on SourceForge about this. The installer fails to find the ESP partition of APFS-formatted Fusion Drives and instead installs Clover to the system root. To update I have to manually copy those files to the ESP partition. I'm not sure if the same issue occurs with AppleRAID volumes, APFS or not. 

https://github.com/corpnewt/CloverExtractor.git Use this script to install Clover in the right partition

Share this post


Link to post
Share on other sites

Hi @Slice

 

Clover r4928: I've a problem with Windows partition name (see pictures below). One in french language: é is not recognized, another is blank no name at all. I don't understand why?

 

screenshot0.png

screenshot1.png

Share this post


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

Hi @Slice

 

Clover r4928: I've a problem with Windows partition name (see pictures below). One in french language: é is not recognized, another is blank no name at all. I don't understand why?

 

 

 

Raster themes have only ascii character set, no extended latin. (as a bonus russian and korean by special efforts)

SVG themes may have any characters including chinese but author or user should provide the SVG font with all needed letters.

Share this post


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

For different additional SSDT table. You seems have 8 tables.

Then the message must include SSDT ID just to avoid confusion?

Share this post


Link to post
Share on other sites
Posted (edited)

Clover 4988 is a stinker!  I can't boot at all with it.   Can't even get to the Apple logo before it stops me dead......managed to disable all of my booting for all of my drives (mainly because I use Clover as my bootloader)......

 

Clover 4972 works............this one's (4988) a turkey, guys.........

Edited by meaganmargaret

Share this post


Link to post
Share on other sites
11 minutes ago, meaganmargaret said:

Clover 4988 is a stinker!  I can't boot at all with it.   Can't even get to the Apple logo before it stops me dead......managed to disable all of my booting for all of my drives (mainly because I use Clover as my bootloader)......

 

Clover 4972 works............this one's a turkey, guys.........

 

Agree! 

The «driverss64UEFI» folder has disappeared and in its place there is another one called simply «drivers» and inside it is the «UEFI» folder.

On reboot the nvidia 1080Ti is no longer detected.

 

 

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, Extreme™ said:

The «driverss64UEFI» folder has disappeared and in its place there is another one called simply «drivers» and inside it is the «UEFI» folder.

On reboot the nvidia 1080Ti is no longer detected.

Since the official release didn't remove the driverss64UEFI nor drivers64, can I ask where did you get the installer

if [[ -d  "${EFI_ROOT_DIR}/EFI/CLOVER/drivers64" && \
    ! -d "${EFI_ROOT_DIR}/EFI/CLOVER/drivers/@CLOVER_DRIVERS_LEGACY@" ]]; then
  mkdir -p "${EFI_ROOT_DIR}/EFI/CLOVER/drivers"
  cp "${EFI_ROOT_DIR}/EFI/CLOVER/drivers64" "${EFI_ROOT_DIR}/EFI/CLOVER/drivers/@CLOVER_DRIVERS_LEGACY@"
fi

if [[ -d  "${EFI_ROOT_DIR}/EFI/CLOVER/drivers64UEFI" && \
    ! -d "${EFI_ROOT_DIR}/EFI/CLOVER/drivers/@CLOVER_DRIVERS_UEFI@" ]]; then
  mkdir -p "${EFI_ROOT_DIR}/EFI/CLOVER/drivers"
  cp "${EFI_ROOT_DIR}/EFI/CLOVER/drivers64UEFI" "${EFI_ROOT_DIR}/EFI/CLOVER/drivers/@CLOVER_DRIVERS_UEFI@"
fi

as I can see only cp commands in official release?

Edited by vector sigma

Share this post


Link to post
Share on other sites

Hello vector sigma

 

I downloaded the version from sourceforge. I prepared a comparison in images between the version of clover 4972 and the 4988. Look at the differences.
In 4988, by installing the same drivers that i install in 4972, when i restarted High Sierra don't see 1080Ti

 

screenshot-84.png

screenshot-85.png

screenshot-86.png

Share this post


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

I downloaded the version from sourceforge. I prepared a comparison in images between the version of clover 4972 and the 4988. Look at the differences.

I know the difference but you aren't surprised a directory gone without lauch any rm command? I'm saying this because only unreleased revision before 4988 did this during our tests you can follow at the "general discussion" topic.

1 hour ago, Extreme™ said:

In 4988, by installing the same drivers that i install in 4972, when i restarted High Sierra don't see 1080Ti

Changing directory to load drivers do nothing to the functionality of Clover. A change regarding nvidia is introduced in r4981 but not sure can have downsides for you.

Share this post


Link to post
Share on other sites
Posted (edited)

Problem solved. 

 

The nvidia 1080Ti was not detected because in the 4998 version of Clover it is no longer possible to install the AptioMemoryFix-64.efi driver. 

So i took this AptioMemoryFix-64.efi driver from version 4972 and put it in the Clover / drivers / UEFI/ folder of version 4998: now everything works fine.

screenshot_89.png

Edited by Extreme™

Share this post


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

The nvidia 1080Ti was not detected because in the 4998 version of Clover it is no longer possible to install the AptioMemoryFix-64.efi driver. 

So i took this AptioMemoryFix-64.efi driver from version 4972 and put it in the Clover / drivers / UEFI/ folder of version 4998: now everything works fine.

Is not included in Clover unless you compile it with third party scripts (unless Slice did this). By the way to avoid surprise next time ensure that no one driver is selected under "Memory Fix" because if one of them is selected all other drivers that contains "aptiomem" or "osxaptiofix" will get deleted. If none of them is selected your AptioMemoryFix wil stay in safe forever. This because the installer records what have you done in previous installations.

Share this post


Link to post
Share on other sites

Feature request:

 

As I understand if you want to change the boot order in Clover in a multi boot system you have define what disk should load first in the plist via its UUID. A little complicated.

 

So I had an idea that it would be pretty cool if you could with in Clover boot environment click and drag to the front the icon for the partition you want to 

boot first. Much like how some UEFI bioses do it where you drag the disk up top.

 

Thanks

Edited by davidm71
added multiboot

Share this post


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

Feature request:

 

As I understand if you want to change the boot order in Clover in a multi boot system you have define what disk should load first in the plist via its UUID. A little complicated.

 

So I had an idea that it would be pretty cool if you could with in Clover boot environment click and drag to the front the icon for the partition you want to 

boot first. Much like how some UEFI bioses do it where you drag the disk up top.

 

Thanks

Click "Restart" and it will be first loaded system

Снимок экрана 2019-07-17 в 19.16.35.png

Share this post


Link to post
Share on other sites

Just tried setting Mojave as the startup disk  in settings and when it rebooted it had selected the 'Preboot' partition instead. 

 

Using Clover 4920.

 

So it didn't work.

 

 

Edited by davidm71
added details

Share this post


Link to post
Share on other sites

It did work. Show me Clover preboot.log corresponding to the situation.

It must work because this is Apple's control panel, invented by Apple not me.

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?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
×