Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

lclerte
lclerte
Posted
Posted
16 hours ago, Matgen84 said:

 

My Clover config.plist works fine with Catalina. But why not try another to isolate the problems with Big Sur. It's a good idea. I'm happy to try the EFI you created. It's nice.

hello friends ! does it mean that Clover works to boot BigSur ( after beta 3 ) ? thanks 

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

I've plugged the kernel patch.

I'm not sure how they exactly work, though. I never had to use them. Of course, "Find" in Clover become "Find" in OC. Same for replace. So that should work.

 

"MaskFind" for Clover is transferred to "Mask" in OC and "MaskReplace" to "ReplaceMask". But I don't know if they works exactly the same.

 

I add a log. You should see something like this in your log : 

01:891 00:001 OC: Kernel patch [0] IOAHCIBlockStorage (TRIM for SSD)
02:704 00:813 OCAK: IOAHCIBlockStorage (TRIM for SSD) replace count - 2

check the replace count to see if it works.

 

 

14 hours ago, Jief_Machak said:
14 hours ago, yapan4 said:

probably kernel patches do not work

Did I forget to tell that kernel patches doesn't work yet. Sorry if I forgot. I'll do them in few hours.

@yapan4 What about now ? If it doesn't boot, send me your config.plist so I can see which feature you are using.

 

CloverX64.efi.zip

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted

Hi @Jief_Machak

 

Fifth test: commit 7470ecc7

 

I try several change to my EFI folder (update kexts to release, add SSDT PMC...), but I don't find how convert working Z390 OpenCore config.plist to Clover.

Always same issue: Busy timeout [0],  (60s) 'AppleACPICPU' 'ARTC'  follow by Black Screen ---->> Timeout error screenshot attached

 

Spoiler

1.thumb.jpg.dfeae0cad9076e2eb922cde8b5e5daee.jpg

 

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

Just to be clear, in case of doubt : I sincerely respect people from OC. It's been years they developed things that everyone uses. They solve a lot of problems etc.

I am really not attacking anyone ! Who knows, if I was in the debate at the beginning of OpenCore, maybe I agreed to restart fresh.

Writing is always a challenge because you're not there to correct if you feel the other take it wrong or bad. So if I gave the impression to attack or reproach someone, I apologise. That never was any of my intention.

@Matgen84 Send your debug.log, I'll have a look.

Link to comment
Share on other sites
iCanaro
iCanaro
Posted
Posted

@Jief_Machak 

If I can, I'll gladly give you a hand
Keep in mind that to communicate, I use google translate


I have Z370 hacks where OC and Clover start with the same SSDT and identical or almost configuration

I tested the 2 Cloverx64.efi posted, but they do not start BS or even cataline, do not leave the initial loading phase and get stuck

 

https://mega.nz/file/q7ZnxSzQ#XPhDWXvaqEVsncNtJQA82sQKvKxTBwkfTq0JDIws2BA

 

https://mega.nz/file/XrRTUIbD#g1fYwMy29iLTwpC5LuIsTS5Urq-2Xsw_cI_6jCc9lZA

Link to comment
Share on other sites
SavageAUS
SavageAUS
Posted
Posted

To continue the conversation I would like to add my 2 cents.

I absolutely respect both teams (Clover and OC) and unity would be great (“CloverCore” , “OpenLeaf” < OpenClover sounds funny). All jokes aside the way OC boots and handles macOS booting and patching is fantastic and then Clovers handling of every other OS is also great with no “Mac stuff” passed through (that I am aware of). If we as users could get the best of both worlds it would be a winner. Personally I prefer the way Clover handles “other operating systems” like windows with no ACPI_BIOS_ERROR “Mac stuff” but I prefer OpenCore for booting macOS. This is just my thoughts, no attack and no disrespect meant. 

  • Like 2
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
7 minutes ago, chris1111 said:

1128407454_Capturedcranle2020-09-0806_52_06.png.bad942a35bcd91ed0a94bc355d4ce0e2.png

I've fixed a git branch name.

 

Try again  

git clone -b opencore_integration --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git

I just did and it compiles. Remember that there is an error at the end.

 

@everyone 

  If you want to fetch and pull, I recommend entering once for all  

git config --global submodule.recurse true

so your next fetch and pull will also include the submodule.

 

  • Like 2
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted
12 minutes ago, Jief_Machak said:

I've fixed a git branch name.

 

Try again  


git clone -b opencore_integration --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git

I just did and it compiles. Remember that there is an error at the end.

 

@everyone 

  If you want to fetch and pull, I recommend entering once for all  


git config --global submodule.recurse true

so your next fetch and pull will also include the submodule.

 

The build works now

thanks

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
4 minutes ago, Jief_Machak said:

@Matgen84 You are using the head version of Clover. You must switch a the branch opencore_integration.

Simplest is to re-clone  


git clone -b opencore_integration --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git

   

 

@Jief_Machak Since the beginning, I git clone OpenCore_integration branch and build.  For the fifth test, I Use cloverx64 that you post in this topic

So I don't understand :(
5 minutes ago, I remade git clone + git config --global submodule.recurse true for other test.

 

Question: Is it necessary to rename your cloverx64.efi to bootx64.efi, and replace the file in Boot folder?

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
2 minutes ago, Matgen84 said:

Question: Is it necessary to rename your cloverx64.efi to bootx64.efi, and replace the file in Boot folder?

I'd say it depends if you boot on it ! Sorry, it's a bad answer. But UEFI firmware can sometimes be configured to boot on any file you want. But the default is EFI/BOOT/BOOTX64.efi. In that case, CloverX64.efi is just ignored and you don't need to have one.

  • Thanks 2
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
4 minutes ago, Jief_Machak said:

I'd say it depends if you boot on it ! Sorry, it's a bad answer. But UEFI firmware can sometimes be configured to boot on any file you want. But the default is EFI/BOOT/BOOTX64.efi. In that case, CloverX64.efi is just ignored and you don't need to have one.

 

I've got a problem to build Master branch: see below 

How to include submodule for compiling Master Branch. Please.

 

Sorry for my bad knowledge !

  

Target revision: HEAD
2020-09-08T14:26:29CEST Checking for updates to Clover..
fatal: bad numeric config value 'true' for 'submodule.recurse': invalid unit
2020-09-08T14:26:29CEST Build failed!

 

Edited by Matgen84
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
8 minutes ago, chris1111 said:

No boot file in build ? no BOOTX64.efi and no CLOVERX64.efi

There won't be any in CloverPackage because there is an error at the end of compilation. Get the efi from Build/Clover/DEBUG_XCODE8/X64

 

7 minutes ago, Matgen84 said:

I've got a problem to build Master branch: see below 

How to include submodule for compiling Master Branch. Please.

Do this in terminal : 

git clone -b opencore_integration --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git [name_of_folder_you_chose]
cd [name_of_folder_you_chose]
git config --global submodule.recurse true
sh ./ebuild.sh --gcc53 --buildtarget=DEBUG --define=DEBUG_ON_SERIAL_PORT

 

 

 

 

or just try this efi.

 

To try it, you "probably" have torename it BOOTX64.efi and copy it in EFI/BOOT.

 

The way I do it :

I put CloverX64.efi in EFI/CLOVER as usual, and I double click the script attached. The script has to be in EFI/CLOVER.

That way, I'm sure they are both the same...

CloverX64.efi.zip

CloverX64.efi.zip

copy cloverX64 to efi_boot

  • Thanks 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
20 minutes ago, Matgen84 said:

 

Question: Is it necessary to rename your cloverx64.efi to bootx64.efi, and replace the file in Boot folder?

I see there are many people not understanding what is what. Let me clarify.

UEFI BIOS usually boot to /EFI/BOOT/BOOTX64.EFI but this file can be replaced by Windows installation or by Linux installation so why we decided to keep Clover as separate file /EFI/CLOVER/CLOVERX64.EFI which will be untouchable by other systems. But UEFI BIOS doesn't know Clover! How to learn it to boot to Clover? We developed a way to do this, regards to Dmazar. 

In the Clover GUI you may see second line of entries like tools entries. First one is to call Shell.efi and the second one with a Clover sign is for writing the boot entry /EFI/CLOVER/CLOVERX64.EFI into nvram to use as default boot entry.

So now on my computer #1 I have two boot entries which I can choose by pressing F12:

"UEFI Boot from HDD" which linked to /EFI/BOOT/BOOTX64.EFI which is older good working Clover 5122.

"Clover boot from HDD" which linked to /EFI/CLOVER/CLOVERX64.EFI which is current test version.

The file BOOTX64.EFI is just the file CLOVERX64.EFI of other revision being renamed.

 

  • Like 1
  • Thanks 3
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
30 minutes ago, Slice said:

I see there are many people not understanding what is what. Let me clarify.

UEFI BIOS usually boot to /EFI/BOOT/BOOTX64.EFI but this file can be replaced by Windows installation or by Linux installation so why we decided to keep Clover as separate file /EFI/CLOVER/CLOVERX64.EFI which will be untouchable by other systems. But UEFI BIOS doesn't know Clover! How to learn it to boot to Clover? We developed a way to do this, regards to Dmazar. 

In the Clover GUI you may see second line of entries like tools entries. First one is to call Shell.efi and the second one with a Clover sign is for writing the boot entry /EFI/CLOVER/CLOVERX64.EFI into nvram to use as default boot entry.

So now on my computer #1 I have two boot entries which I can choose by pressing F12:

"UEFI Boot from HDD" which linked to /EFI/BOOT/BOOTX64.EFI which is older good working Clover 5122.

"Clover boot from HDD" which linked to /EFI/CLOVER/CLOVERX64.EFI which is current test version.

The file BOOTX64.EFI is just the file CLOVERX64.EFI of other revision being renamed.

 

 

Thanks for these explanation.


On my Z390 computer with F12, I have only one entry (macOS and Windows are on separate drive):

 "UEFI OS P0" is for macOS

 

I use USB bootable for test.

When I rename, @Jief_Machak CLOVERX64.efi to BOOTX64.efi, Clover GUI hangs on Options for Boot macOS from BigSur - Data via Prebbot on Preboot. When I replace it by a master branch one: works fine. I can navigate in Options section.

 

Sorry for my bad English

 

Edited by Matgen84
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
6 minutes ago, Jief_Machak said:

Where is that ?

Could that be hidden by the theme ?

See the post 

Second row has second entry with sign ⌘. This is the entry.

It can be hidden by config but not by theme.

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted
24 minutes ago, Slice said:

Second row has second entry with sign ⌘. This is the entry.

It can be hidden by config but not by theme.

My second entry is Options and 3rd is about Clover with Clover sign.

 

 

Send me your debug.log. It doesn't do that here, so I can't tell.

Screenshot 2020-09-08 at 16.36.57.png

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...