Bootloader Clover problems report & features request

[Matgen84]

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?

 

[Slice]

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.

[LockDown]

Isnt it too early to be compiling in Catalina.

[Slice]

I see no bug.

[Slice]

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

[nms]

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?

[Extreme™]

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.

 

 

[vector sigma]

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 July 11, 2019 by vector sigma

[Extreme™]

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

 

[Slice]

@Extreme

I see no relationship between DriverUEFI and GTX1080.

Did you loose bootargs "NDVA_DRV=1"?

[vector sigma]

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.

[Extreme™]

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.

Edited July 12, 2019 by Extreme™

[vector sigma]

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.

[davidm71]

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 July 17, 2019 by davidm71
added multiboot

[Slice]

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

[davidm71]

22 minutes ago, Slice said:

Click "Restart" and it will be first loaded system

 

Good to know. Thank you.

[davidm71]

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 July 17, 2019 by davidm71
added details

[Slice]

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.

[mhaeuser]

Macs do not boot non-Preboot APFS

[jerryy2]

Hello,

 

I am writing to ask for some help in upgrading Clover from v4972 to v5018. I have tried different options, but so far these have led to one of:

 

1.) Black screen with no disk activity.

2.) Constant bios screen reboot loop that never gets to the Clover screen.

3.) The prohibited sign, instead of the usual boot screens.

 

I have a Gigabyte Z370XP SLI motherboard with a i5-8400

 

Clover v4972 is working fine,  these are the drivers I have:

 

It seems that there are two drivers that have been dropped from Clover in the new v5018, but I did not know if this is the problem or not.

 

 

 

Going through the options in v5018, I have the following:

 

My question is this: What do I need to do to get the update working?

 

Thanks for your help!

 

[Matgen84]

5 hours ago, jerryy2 said:

Hello,

 

I am writing to ask for some help in upgrading Clover from v4972 to v5018. I have tried different options, but so far these have led to one of:

 

1.) Black screen with no disk activity.

2.) Constant bios screen reboot loop that never gets to the Clover screen.

3.) The prohibited sign, instead of the usual boot screens.

 

I have a Gigabyte Z370XP SLI motherboard with a i5-8400

 

Clover v4972 is working fine,  these are the drivers I have:

 

It seems that there are two drivers that have been dropped from Clover in the new v5018, but I did not know if this is the problem or not.

 

 

 

Going through the options in v5018, I have the following:

 

My question is this: What do I need to do to get the update working?

 

Thanks for your help!

 

 

Hi

 

First, AptioFixMemery is no more include in Clover: so you have to download yourself from Acidanthera repo on Github. 

 

For Clover itself, v2.5K introduce new directories or subdirectories. Put your drivers locate in Driver64UEFI (you can remove this old directory later) in appropriate folder: take a look below for explanation.

 

 

[jerryy2]

Hello @Matgen84

 

Thank you for your help, adding the two files back in made it work!

 

Just for completeness, after cleanup the folder looks like this:

 

So far, so good and thanks again.

[Matgen84]

19 minutes ago, jerryy2 said:

Hello @Matgen84

 

Thank you for your help, adding the two files back in made it work!

 

Just for completeness, after cleanup the folder looks like this:

 

So far, so good and thanks again.

 

Hi

 

If Clover work, you can remove old driversU64UEFI folder.

 

Do you use FileVault2? If not, don't install its drivers like AppleKeyAggregator.efi, AppleUITheme!.Uefi, AppleImageCodec, AppleKeyFeeder.efi, AptioInput.efi or HashServiceFix.efi.

[Matgen84]

12 hours ago, zkingtut said:

Excuse me 

What is fileValut2 means ? How to know if is used or no in my system ? 

I keep all mentioned drivers in my clover and I have no idea what its job ? 

 

Edited : OK  I got its job 

 

 

You don't have FileVault (encrypting data disk). So You can remove all  drivers mentioned in my previous quote. Do not install them when update Clover.

[Matgen84]

5 hours ago, zkingtut said:

 

I removed all this drivers and everything is still working without any issue

Good to know 

 

Because Clover 2.5k r5xxxx don't load drivers in Drivers64UEFI  So remove this folder is useful