Clover General discussion

[Slice]

Clover 4091, High Sierra ready, released at sf.net.

[D-an-W]

Thanks Slice, am I right in saying if I compile with the latest Build_Clover.command I get the same compatibility?

[Slice]

Thanks Slice, am I right in saying if I compile with the latest Build_Clover.command I get the same compatibility?

I don't know.

My build is

./ebuild.sh -fr

[smolderas]

I don't know.

My build is

./ebuild.sh -fr

Simple and sleek.

[abdouoi]

Clover 4091, High Sierra ready, released at sf.net.

This version installed clover on my main partition instead of the EFI partition like previous clover versions

[Sherlocks]

This version installed clover on my main partition instead of the EFI partition like previous clover versions

Right. Now clover install script has issue if you have apfs partition(target)

 

You have to copy each clover binary files to esp parition from main parition.

 

나의 LG-F800S 의 Tapatalk에서 보냄

[abdouoi]

Right. Now clover install script has issue if you have apfs partition(target)

 

You have to copy each clover binary files to esp parition from main parition.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Ok. But is there going to be a fix ? Also do I still need to keep apfs.efi in Drivers64UEFI ?

[Sherlocks]

Ok. But is there going to be a fix ? Also do I still need to keep apfs.efi in Drivers64UEFI ?

Keep apfs.efi

-yes.

 

But is there going to be a fix

-someone(coder or developer)

 

I reverted sierra. Because i have to use daily os

 

Thanks

 

나의 LG-F800S 의 Tapatalk에서 보냄

[Matgen84]

Simple and sleek.

 

In build_Clover.command with Developer mode, you can chose "ebuild.sh -fr" or else. I just tested

[mashny]

I've been trying to upgrade my current installation to 10.13. But an upgrade wouldn't work. The Install OSX entry wouldn't even show up in clover. But I can successfully install 10.13 on a separate partition (even APFS) from 10.12.

 

I am using Clover 4089 and here is my config .

[Slice]

I've been trying to upgrade my current installation to 10.13. But an upgrade wouldn't work. The Install OSX entry wouldn't even show up in clover. But I can successfully install 10.13 on a separate partition (even APFS) from 10.12.

 

I am using Clover 4089 and here is my config .

Clover 4091, High Sierra ready, released at sf.net.

[Philip Petev]

In build_Clover.command with Developer mode, you can chose "ebuild.sh -fr" or else. I just tested

 

No need for that. Option 5. build existing revision for release (no update, standard build) is sufficient, as that option uses -fr by default.

[xtddd]

Clover 4091, High Sierra ready, released at sf.net.

great! well done

[smolderas]

In build_Clover.command with Developer mode, you can chose "ebuild.sh -fr" or else. I just tested

Why would I need another script?

[Philip Petev]

You don't. The script is just one more way to build it.

[Vinicius P. Miranda]

I updated to the Clover r4091 and now I'm stuck here. Does anyone know how to solve it?

 

[xtddd]

just update to clover 4091 ..all fine.

[SavageAUS]

Right. Now clover install script has issue if you have apfs partition(target)

 

You have to copy each clover binary files to esp parition from main parition.

 

나의 LG-F800S 의 Tapatalk에서 보냄

I've been doing this (on 4092 now) but clover boot screen is showing 4087. Maybe I did something wrong but I chose install to esp, it installed to root of hdd so I copy and paste from / to esp still shows 4087. Negligible issue and more than likely my mistake.

 

Edit: yeah was my bad lol.

 

Sent from my SM-G930F using Tapatalk

[Cyberdevs]

I tried to install 4091 on the ESP partition and still it installed the clover on the root of the macOS High Sierra bootable drive, so I had to copy/paste the EFI folder manually.

Update:

I guess there's still some problems regarding the APFS volumes?!

[savvas]

I updated to the Clover r4091 and now I'm stuck here. Does anyone know how to solve it?

 

Try this build plz

BOOTX64.efi.zip

Or you are using legacy boot?

[Vinicius P. Miranda]

Try this build plz

BOOTX64.efi.zip

Or you are using legacy boot?

It did not work, still stuck. I use UEFI, it had never happened before. And the boot is installed on an SSD.

[savvas]

It did not work, still stuck. I use UEFI, it had never happened before. And the boot is installed on an SSD.

            #2146            

[mashny]

 

I've been trying to upgrade my current installation to 10.13. But an upgrade wouldn't work. The Install OSX entry wouldn't even show up in clover. But I can successfully install 10.13 on a separate partition (even APFS) from 10.12.

 

I am using Clover 4089 and here is my config .

Clover 4091, High Sierra ready, released at sf.net.

 

 

Nope the same issue persists.

[p.H]

if (Prop && IsPropertyTrue (Prop)) {
+        gSettings.HWP = TRUE;
+        AsmWriteMsr64 (MSR_IA32_PM_ENABLE, 1);
+      }

Here is the code for turning HWP on for Clover. But it became ineffective when computer waked up from sleep. Is there a way we can manually call this method so that HWP remains effective after sleep?

[frnic]

General Question for Clover dev's. 

I have a multiboot setup and now have MacOS 10.12.6 on one drive and 10.13 on another couple (when I figure out what combination I want I will update my sig). 

My question is, does Clover use the same serial number and other id details in the Clover config.plist for any of the MacOS systems in the boot list options? Because this seems to be annoying iCloud security when I switch from one version of the OS to another, and it wants me to re-signin every time. I worked around this by installing Clover to each MacOS drive and putting a different config.plist with unique ID info for each. That works and apparently iCloud (security checking) is happy that I have 3 different machines registered, and it stops asking me to sign in every time I reboot now.

This is a little annoying since I have to stop the BIOS and switch boot drives to change to a different Clover install and get the right S/N etc. for each system. Would it be possible to have the config.plist associated with each of the boot drives - so, maybe in the custom configuration options we could specify which config.plist (by unique names?) we wanted each drive to use when it boots - or to restart Clover with the right config.plist - or however you could easily (hate that word) make it work? 

Thanks

Frank