Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted

Hi @Badruzeus, @arsradu

 

I think i's a AptiofixPg problem not Clover. There is some commits last 4hours 1hour in OCSupportPkg and OpenCore.

 

So wait and see :)

 

What flag to use for external package in ebuild.sh ( ---ext-co or --ext-pre)?

 

Sorry for my bad english

 

arsradu
arsradu
Posted
Posted (edited)
8 minutes ago, Matgen84 said:

Hi @Badruzeus, @arsradu

 

I think i's a AptiofixPg problem not Clover. There is some commits last 4hours 1hour in OCSupportPkg and OpenCore.

 

So wait and see :)

 

What flag to use for external package in ebuild.sh ( ---ext-co or --ext-pre)?

 

Sorry for my bad english

 

At this point, all ebuild.sh parameters related to external packages will cause errors. Some will cause the error I mentioned before, others will cause other errors.

 

Anyway, these are the available options, and I've tried all of them with no success. 

print_option_help "--ext-pre" "enable external driver download"
print_option_help "--ext-co" "checkout & build external drivers at ..src/EXT_PACKAGES"
print_option_help "--ext-build" "build existing external drivers located at ..src/EXT_PACKAGES"

The only way I could find to build Clover at this point is to build only Clover (no external drivers)

Edited by arsradu
  • Thanks 1
arsradu
arsradu
Posted
Posted (edited)
6 minutes ago, Slice said:

Clover has enough drivers to be build without external one.

I think maybe the only one I need from those packages is ApfsDriverLoader. Do we have something similar for apfs, too? I mean, built with Clover? Cause apfs.efi itself is not open-source for as far as I know. And if you wanna use it and update it, you need to extract it yourself.

Edited by arsradu
Pene
Pene
Posted
Posted (edited)
On 6/9/2019 at 8:19 AM, PMheart said:

Hi,

 

I propose this new patch for kext injection of 10.15: 


Index: rEFIt_UEFI/Platform/kext_inject.c
===================================================================
--- rEFIt_UEFI/Platform/kext_inject.c	(revision 4959)
+++ rEFIt_UEFI/Platform/kext_inject.c	(working copy)
@@ -681,8 +681,8 @@
 // Catalina (SIP)
 // PMheart: checked
 // Need to pair with KBEMojaCata*EXT
-UINT8   KBECataSearchSIP[]            = { 0x00, 0x85, 0xC0, 0x0F, 0x84, 0x87, 0x00, 0x00, 0x00, 0x49 };
-UINT8   KBECataReplaceSIP[]           = { 0x00, 0x85, 0xC0, 0x90, 0x90, 0x90, 0x90, 0x90, 0x90, 0x49 };
+UINT8   KBECataSearchSIP[]            = { 0xE8, 0xB0, 0xEE, 0x0C, 0x00, 0x85, 0xC0, 0x0F, 0x84 };
+UINT8   KBECataReplaceSIP[]           = { 0xE8, 0xB0, 0xEE, 0x0C, 0x00, 0x31, 0xC0, 0x0F, 0x84 };
 
 // Mojave 10.14 - 10.14.3
 // Avoid race condition in OSKext::removeKextBootstrap when using booter kexts without keepsyms=1.

Don't ask me if it works, of course it does - just read the asm code. ;)

 

PMheart

 

@PMheart I have several reports injection does not work with the new patch in 10.15. Cannot test myself currently.

Edited by Pene
  • Thanks 1
pinarek
pinarek
Posted
Posted

I now have 2 APFS containers, 1 Catalina and 1 Mojave 10.14.6-Beta1.

In the Clover boot menu, I see only the last installed APFS partition, so the Catalina OS in the boot selection next to HFS + 10.14.4, etc.

The systems are installed on an SSD.

 

I also installed a second SSD on test 2 APFS systems, it seems like there is always only 1 APFS system in the Clover

Boot menu is displayed, can one change that?

 

How is it possible to view and boot from 2 or more APFS bootable systems in the boot menu of Clover 4945 ?

I do not use UEFI but Legacy EFI as a folder and no ESP partition for Clover.

 

With only HFS + partitions there are no problems. See and select 3 or 4 macOS systems.

 

Thanks for help.

arsradu
arsradu
Posted
Posted (edited)

So far so good with OsXAptioFixDrv3. I remember we talked here about OsXAptioFix drivers versus AptioMemoryFix. And...I think someone recommended AptioMemoryFix because of better, more up-to-date, support.

 

Also, at some point I had some issues with EmuVariable on a Skylake system with Nvidia Drivers. And since then, I was using AptioMemoryFix on that specific build for that specifc reason. Now, it was a long time ago so I don't remember exactly what the reason was, but basically I couldn't boot with EmuVariable and Nvidia Drivers anymore.

 

I haven't tried OsXAptioFixDrv3 with that...but now I'm not using Nvidia Drivers with that system. So it doesn't really matter anymore.

 

Thing is, guys...and I think I'm speaking for a lot of people here...options are good. But too many options are not. Cause it gets confusing.

 

For example, we've got 3 or 4 choices for memory fixing (OsXAptioFixDrv v1-v3 + AptioMemoryFix), a dedicated emulated NVRAM solution (EmuVariable), but if you're using OSXAptioFixDrv3 or AptioMemoryFix (both including fixes for non-native NVRAM), you don't need that anymore... And so on so forth.

 

There are too many options, in my opinion. Some of which are either redundant, obsolete or both. I think we need a bit of cleanup there. And only keep the stuff that people really use, without being confusing.

 

Also, Aptio memory fixes are NOT supposed to be used together, for as far as I know. Still, there is no protection inside Clover (and I've suggested this functionality before) to prevent users from selecting all of them if they want to. Cause they don't know which one does what. Which one has which features. Which one is good for which configuration. Which one is obsolete. And so on so forth. Now, I know Clover is not for stupid people. But that's not an excuse to make it confusing on purpose, is it?. :))

 

I also think we need more unity with this project. Especially when it comes to drivers. If they have the same scope, just choose the best option out there for the user, and use it by default inside Clover. The one with the best "coverage". The most complete one for most users.

 

Just to be clear, I'm not complaining. I think this has been an amazing project for many, many years! And I'm really grateful for everything you guys have achieved. I'm only suggesting a few things to make it even better.

Edited by arsradu
  • Like 2
UefiBooter
UefiBooter
Posted
Posted
33 minutes ago, arsradu said:

So far so good with OsXAptioFixDrv3. I remember we talked here about OsXAptioFix drivers versus AptioMemoryFix. And...I think someone recommended AptioMemoryFix because of better, more up-to-date, support.

 

Also, at some point I had some issues with EmuVariable on a Skylake system with Nvidia Drivers. And since then, I was using AptioMemoryFix on that specific build for that specifc reason. Now, it was a long time ago so I don't remember exactly what the reason was, but basically I couldn't boot with EmuVariable and Nvidia Drivers anymore.

 

I haven't tried OsXAptioFixDrv3 with that...but now I'm not using Nvidia Drivers with that system. So it doesn't really matter anymore.

 

Thing is, guys...and I think I'm speaking for a lot of people here...options are good. But too many options are not. Cause it gets confusing.

 

For example, we've got 3 or 4 choices for memory fixing (OsXAptioFixDrv v1-v3 + AptioMemoryFix), a dedicated emulated NVRAM solution (EmuVariable), but if you're using OSXAptioFixDrv3 or AptioMemoryFix (both including fixes for non-native NVRAM), you don't need that anymore... And so on so forth.

 

There are too many options, in my opinion. Some of which are either redundant, obsolete or both. I think we need a bit of cleanup there. And only keep the stuff that people really use, without being confusing.

 

Also, Aptio memory fixes are NOT supposed to be used together, for as far as I know. Still, there is no protection inside Clover (and I've suggested this functionality before) to prevent users from selecting all of them if they want to. Cause they don't know which one does what. Which one has which features. Which one is good for which configuration. Which one is obsolete. And so on so forth. Now, I know Clover is not for stupid people. But that's not an excuse to make it confusing on purpose, is it?. :))

 

I also think we need more unity with this project. Especially when it comes to drivers. If they have the same scope, just choose the best option out there for the user, and use it by default inside Clover. The one with the best "coverage". The most complete one for most users.

 

Just to be clear, I'm not complaining. I think this has been an amazing project for many, many years! And I'm really grateful for everything you guys have achieved. I'm only suggesting a few things to make it even better.

 

Personally i think clover has become too much of a mess, why not just join forces and all get behind OpenCore ?

 

  • Like 4
blackosx
blackosx
Posted
Posted (edited)

I agree. It's been a long time since Clovers inception...

 

rq1cAe0.png

 

And Clover has grown hugely in it's ability and popularity. Clover has the user base, familiarity and an installer which will appeal to many so I believe Clover will be around for a long time to come.

 

Clover has been great for me and like Chameleon, I will support it as long as I can.

 

But moving on to today, OpenCore does look to be the new daddy on the block with great documentation and works perfectly for me.

 

Edited by blackosx
  • Like 5
arsradu
arsradu
Posted
Posted

Personally I'm all for unity. And I think combining the experience of Clover with the freshness of OpenCore...results might be really interesting. Now, I've heard this many times before: we want to collaborate, but the other guys don't...

That, in my opinion, is not helping anyone. I think the power of a team doesn't consist in the number of its members, but in the quality of each one of them. And I think there are plenty of really good devs out there who can make really incredible things if they were to work together.

  • Like 3
  • Thanks 1
  • Popular Post
Slice
Slice
Posted
  • Popular Post
Posted

Clover has protection against installing all AptioFix drivers. If AptioMemoryFix presents then others will be ignored.

I will support Clover as long as it will be useful for anybody.

  • Like 12
  • Thanks 8
blackosx
blackosx
Posted
Posted (edited)
6 minutes ago, Slice said:

I will support Clover as long as it will be useful for anybody.

 

@Slice - You have worked hard everyday to develop and support Clover. Your contribution to this community has been exceptional. Thank you :)

Edited by blackosx
  • Like 9
  • Thanks 4
arsradu
arsradu
Posted
Posted (edited)
2 hours ago, Slice said:

Clover has protection against installing all AptioFix drivers. If AptioMemoryFix presents then others will be ignored.

I will support Clover as long as it will be useful for anybody.

 

Yeah, I was talking about protection when selecting them in the installer. You can select all of them there. But I'm guessing the protection you're talking about is when those drivers are actually copied into their locations. So basically in the background. I see... Ok then.

 

I would also like to thank you very much for supporting this project for so long! I'm sure it hasn't been easy.

Edited by arsradu
  • Like 2
Badruzeus
Badruzeus
Posted
Posted

@Slice I've lost Pointer on Clover GUI with my PS2Trackpad (ELAN) since r4952.

I usually use "\drivers64UEFI\Ps2MouseDxe-64.efi" to make it works with "Mouse: Enabled=true" but now it doesn't.

Thanks.

  • Sad 1
Balamut
Balamut
Posted
Posted
On 6/11/2019 at 5:16 AM, Slice said:

Clover has protection against installing all AptioFix drivers. If AptioMemoryFix presents then others will be ignored.

I will support Clover as long as it will be useful for anybody.

 

Still using it :)

Slice
Slice
Posted
Posted
12 hours ago, Badruzeus said:

@Slice I've lost Pointer on Clover GUI with my PS2Trackpad (ELAN) since r4952.

I usually use "\drivers64UEFI\Ps2MouseDxe-64.efi" to make it works with "Mouse: Enabled=true" but now it doesn't.

Thanks.

There was a mistake. Check latest version.

  • Thanks 1
 Share
Go to topic listing
×
×
  • Create New...