Clover General discussion

Jief_Machak · October 23, 2020

@iCanaro Thanks for all the tests, and for helping Clover community. It really help that you agree to boot 20 times a day to help me find a bug I can't create on my hardware. So thanks to yan man.

iCanaro · October 23, 2020

he did it again @Jief_Machak
on the Z370 last I tried high sierra and apart from going into kernel panic, on rebooting I found myself in the BigSur GUI with the high sierra icon.

Spoiler

I started catalina and mounted the BS preboot and in fact in

4EA0011C-1C8B-476D-BD5D-1AE8F7648F64/ System / Library / CoreServices / SystemVersion.plist

then inside there were high sierra values

i'll leave the log debugging of the attempted high sierra startup

Z370_5125 (master, commit d540f76b5) high_sierra_NOK_debug.log
the version of clover that I compiled (in case it depends on some compilation error)

924114689_Schermata2020-10-23alle22_46_33.png.82db2721d821f6aafb146979cc9c6648.png

CLOVERX64_5125_d540f76b5.efi.zip
then if you need anything else to understand this strange and annoying problem

Edited October 23, 2020 by iCanaro

Jief_Machak · October 23, 2020

@iCanaro To fix HS panic, do you have a backup folder with a working Clover ? (always always the same, I want to go back where it was working)

The system version.plist you're showing is BS, not HS value (ProductVersion=11.0). So looks good.

TIP : you can press space bar to get UUID information about a partition. In case of a preboot, you'll see a line about a target UUID. This will be the name of the folder on Preboot.

iCanaro · October 23, 2020

I restored the SystemVersion.plist and BS started working properly again

i tried several times to start high sierra with
CloverX64-2020-10-23-21-10-05-e4e57cb-dirty-jief
but beyond KP, other damage doesn't, so I assume that the problem arises from the version I fill out.

What steps do I need to take now to get a compiled version of Clover without any hassle?

13 minutes ago, Jief_Machak said:

The system version.plist you're showing is BS, not HS value (ProductVersion=11.0). So looks good.

ops between the different things I was doing, I got the plist wrong for the screenshot and put the picture of what I restored :rofl:

15 minutes ago, Jief_Machak said:

To fix HS panic, do you have a backup folder with a working Clover ? (always always the same, I want to go back where it was working)

high sierra I never use it, it's just there for testing, I find it strange that only he goes into kernel panic and not mojave, catalina and bigsur
You have another EFI with Clover, version 5122 where high sierra starts regularly, serves log debugging with a boot from this Clover?!

I am very concerned to solve the problem of compilation, since I also move on to other these Clovers, I would not like to generate problems on other hacks

iCanaro · October 23, 2020

PS: here's the high sierra log debugging started with another EFI where I have Clover 5122 with integrated the first step of the quirks

Z370_5122 (master, commit f4e10b1a2) _HS_OK_debug.log

Jief_Machak · October 23, 2020

12 minutes ago, iCanaro said:

PS: here's the high sierra log debugging started with another EFI where I have Clover 5122 with integrated the first step of the quirks

Z370_5122 (master, commit f4e10b1a2) _HS_OK_debug.log

If you put a 5124 in that EFI, does it start ?

iCanaro · October 23, 2020

12 minutes ago, Jief_Machak said:

If you put a 5124 in that EFI, does it start ?

i try and then i mean
I checked the kext well for 10.13 which were not ok, now they should be OK, I put the same of mojave, but always Kernel Panic

iCanaro · October 23, 2020

@Jief_Machak I tried CLOVERX64-5124-c7c079e0f.efi but I always got KP [this is the Clover Test Development EFI]

Z370_CLOVERX64-5124-c7c079e0f.efi_HS_NOK_debug.log

36 minutes ago, Jief_Machak said:

59 minutes ago, iCanaro said:

PS: here's the high sierra log debugging started with another EFI where I have Clover 5122 with integrated the first step of the quirks

Z370_5122 (master, commit f4e10b1a2) _HS_OK_debug.log

If you put a 5124 in that EFI, does it start ?

in the other EFI [stable] where I have Clover 5122, with this CLOVERX64-5124-c7c079e0f.efi always kernel panic

PS: I upgraded XCODE to version 12.1 GM

iCanaro · October 23, 2020

FIXED High Sierra Z370 hack :thumbsup_anim: . Z370_5125 (master, commit d540f76b5)_HS_OK_debug.log
ok well I think I fixed the compilation problems, I started and started HS leaving the kexts in EFI to the bare minimum (evidently there was one of those taken away that caused KP) using a Clover that I compiled CLOVERX64--5125--d540f76b5.efi.zip

83856788_Schermata2020-10-24alle01_10_00.png.53b563766907e39c5ee00fb1275e4a58.png

Edited October 23, 2020 by iCanaro

SavageAUS · October 24, 2020

Here we have it folks. Updated my AMD rig and boy was that easy. Using @iCanaro kernel patches and from the work of @Jief_Machak it was super simple. BootloaderChooser has been a great help in all my recent testing.
Here is debug log from a boot to Big Sur (Can provide log for Catalina if needed but it boots fine)
debug.log

Spoiler

I would like to hide these drives but i am having an issue, as you can see i have a Windows 10 custom entry (bottom image) after arch linux. I know i can turn off scanning for entries which will get rid of these but it also gets rid of Big Sur as i cannot get that one to work with a custom entry.

Edited October 24, 2020 by SavageAUS

Jief_Machak · October 24, 2020

7 hours ago, iCanaro said:

Yes, detached state is ok. You are at the last commit. Good.

7 hours ago, iCanaro said:

I started and started HS leaving the kexts in EFI to the bare minimum

Yes, that's always the way to go : strip down to the minimum and build up. Well done.

1 hour ago, SavageAUS said:

Updated my AMD rig and boy was that easy

Thanks for letting us know.

@PG7 : are you there ? Could we diagnose your bug ?

naiclub · October 24, 2020

19 hours ago, mifjpn said:

Thank you always, Jief.
I don't have Mojave.
However, there is something I would like to confirm.
I'm recursively not working by default with "git pull && git fetch".
I used "git pull --recurse-submodules && git fetch --recurse-submodules".
The result of "./buildme" is as follows.

% ./buildme

------------------------------------------------------------------------
buildme, Clover r5125 (SHA: e4e57cb33)
TOOLCHAIN: GCC53 (override example: './buildme XCODE8')

1) build Clover
2) build Clover with HFSPlus
3) make pkg
4) make app
5) make app (with Clover)
6) make iso
7) build all
8) test build (no autogen, no boot files)
9) status
10) update Clover
11) show diff
12) open CloverV2/EFI/CLOVER directory
13) update Clover (reset changes)
14) clean BaseTools
15) quit
Please enter your choice: 9
Fetching submodule OpenCorePkg
commit e4e57cb33121fb2ec9d574a666441498b83f367e (HEAD -> master, origin/master, origin/HEAD)
Author: jief666 <github.com@jfa.knudsen.ovh>
Date:   Fri Oct 23 16:29:39 2020 +0300

    Recurse submodules.
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
Entering 'OpenCorePkg'
commit 39fb43413e5d3377de65bd0355a11b790edada4f (HEAD, origin/master, origin/HEAD)
Author: jief666 <github.com@jfa.knudsen.ovh>
Date:   Wed Oct 21 17:26:33 2020 +0300

    Less log + global for InternalGetApfsSpecialFileInfo.
HEAD detached from f10d9d3c
nothing to commit, working tree clean

Is this okay?
Did you change the buildme for us at the time of writing like this?

Thank you.

Last login: Sat Oct 24 15:47:08 on console
baby@babys-iMac-Pro ~ % cd
baby@babys-iMac-Pro ~ % cd CloverBootloader
baby@babys-iMac-Pro CloverBootloader % git pull --recurse-submodules && git fetch --recurse-submodules
remote: Enumerating objects: 95, done.
remote: Counting objects: 100% (95/95), done.
remote: Compressing objects: 100% (37/37), done.
remote: Total 97 (delta 70), reused 82 (delta 57), pack-reused 2
Unpacking objects: 100% (97/97), done.
From https://github.com/CloverHackyColor/CloverBootloader
   d17d02b1f..1934a83d8  master     -> origin/master
Fetching submodule OpenCorePkg
From https://github.com/CloverHackyColor/OpenCorePkg
   b2824181..0857d517  master     -> origin/master
Updating d17d02b1f..1934a83d8
Fast-forward
 Include/Guid/AppleApfsInfo.h                       |   8 +-
 OpenCorePkg                                        |   2 +-
 Xcode/Clover/Clover.xcodeproj/project.pbxproj      |  12 +
 .../CloverX64/CloverX64.xcodeproj/project.pbxproj  |   4 +
 buildme                                            |  17 +-
 rEFIt_UEFI/Platform/BootLog.cpp                    |   2 +-
 rEFIt_UEFI/Platform/Hibernate.cpp                  |   2 -
 rEFIt_UEFI/Platform/LegacyBoot.cpp                 |   2 -
 rEFIt_UEFI/Platform/MemoryOperation.c              |  61 ++++-
 rEFIt_UEFI/Platform/MemoryOperation.h              |   2 +-
 rEFIt_UEFI/Platform/Nvram.cpp                      |   2 -
 rEFIt_UEFI/Platform/Posix/abort.cpp                |   2 +
 rEFIt_UEFI/Platform/Self.cpp                       |   7 +-
 rEFIt_UEFI/Platform/SelfOem.cpp                    |  36 ++-
 rEFIt_UEFI/Platform/SelfOem.h                      |   1 +
 rEFIt_UEFI/Platform/Settings.cpp                   |   7 +-
 rEFIt_UEFI/Platform/cpu.h                          |   2 +-
 rEFIt_UEFI/Platform/kernel_patcher.cpp             |   8 +-
 rEFIt_UEFI/Platform/kext_inject.cpp                |   3 +-
 rEFIt_UEFI/Platform/kext_patcher.cpp               |   3 +-
 .../find_replace_mask_Clover_tests.cpp             |  14 +-
 rEFIt_UEFI/entry_scan/entry_scan.h                 |   1 -
 rEFIt_UEFI/entry_scan/loader.cpp                   | 273 +++++++++++++++++----
 rEFIt_UEFI/gui/REFIT_MENU_SCREEN.cpp               |  27 +-
 rEFIt_UEFI/gui/REFIT_MENU_SCREEN.h                 |  74 ++++++
 rEFIt_UEFI/include/OC.h                            | 129 ++++++++++
 rEFIt_UEFI/libeg/libeg.h                           |  13 +-
 rEFIt_UEFI/refit.inf                               |   1 +
 rEFIt_UEFI/refit/lib.cpp                           |  56 ++++-
 rEFIt_UEFI/refit/lib.h                             |  25 +-
 rEFIt_UEFI/refit/main.cpp                          | 115 ++-------
 rEFIt_UEFI/refit/menu.cpp                          |   5 +-
 32 files changed, 682 insertions(+), 234 deletions(-)
 create mode 100644 rEFIt_UEFI/include/OC.h
Submodule path 'OpenCorePkg': checked out '0857d5170842cf01d0fce7433eb33c682a4754f7'
Fetching submodule OpenCorePkg
baby@babys-iMac-Pro CloverBootloader % ./buildme

------------------------------------------------------------------------
buildme, Clover r5125 (SHA: 1934a83d8)
TOOLCHAIN: GCC53 (override example: './buildme XCODE8')

 1) build Clover
 2) build Clover with HFSPlus
 3) make pkg
 4) make app
 5) make app (with Clover)
 6) make iso
 7) build all
 8) test build (no autogen, no boot files)
 9) status
10) update Clover
11) show diff
12) open CloverV2/EFI/CLOVER directory
13) update Clover (reset changes)
14) clean BaseTools
15) quit
Please enter your choice: 9
Fetching submodule OpenCorePkg
commit 1934a83d8434ddb5eb4b2d85f975edb0c7ea3e2a (HEAD -> master, origin/master, origin/HEAD)
Author: Sergey Isakov <isakov-sl@bk.ru>
Date:   Sat Oct 24 09:38:01 2020 +0300

    commit changes to OC
    
    Signed-off-by: Sergey Isakov <isakov-sl@bk.ru>
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
Entering 'OpenCorePkg'
commit 0857d5170842cf01d0fce7433eb33c682a4754f7 (HEAD, origin/master, origin/HEAD)
Author: Sergey Isakov <isakov-sl@bk.ru>
Date:   Sat Oct 24 09:05:30 2020 +0300

    avoid file read error
    return status not assert
    
    Signed-off-by: Sergey Isakov <isakov-sl@bk.ru>
HEAD detached from b2824181
nothing to commit, working tree clean

Why can't I see the same as you?

maclinuxG4 · October 24, 2020

@Jief_Machak plz send by by message the spefic rclover5125_oem.pkg from this https://github.com/CloverHackyColor/CloverBootloader/commit/70988228c43bccdbf2bb71acc5d708b70f9872fc

i need to assure that on mojave:

-investigaste, because some kext load seem e trunk

-error kernel that i haven't before

-sounds restricted on this kext.

refer to this

Common_Sense · October 24, 2020

Hi @Jief_Machak,

I am trying to override the name of the preboot volume being displayed in Clover GUI and it seems it does not work, do you think the new selection logic to display preboot volume and hide the main volume in the Clover GUI might override the custom entry defined in config.plist?

naiclub · October 24, 2020

I want to ask if now anyone has installed the full bigsurbeta10 with Clover2125. Have you recently been successful?

Jief_Machak · October 24, 2020

5 minutes ago, Common_Sense said:

Hi @Jief_Machak,

I am trying to override the name of the preboot volume being displayed in Clover GUI and it seems it does not work, do you think the new selection logic to display preboot volume and hide the main volume in the Clover GUI might override the custom entry defined in config.plist?

Hi,

Don't think so. I've just tried.

For my information, why are doing it with a custom entry, instead of a .VolumeLabel.txt at volume root ?

20 minutes ago, maclinuxG4 said:

@Jief_Machak plz send by by message the spefic rclover5125_oem.pkg from this https://github.com/CloverHackyColor/CloverBootloader/commit/70988228c43bccdbf2bb71acc5d708b70f9872fc

i need to assure that on mojave:

-investigaste, because some kext load seem e trunk

-error kernel that i haven't before

-sounds restricted on this kext.

refer to this

I don't do pkg. I don't know what is "rclover5125_oem.pkg". I know that 5125 is not that commit.

You can get a Clover efi file at specific commit here : https://github.com/jief666/CloverCommits. I don't remember a change in drivers, so you can just drop the efi file in your Clover folder.

naiclub · October 24, 2020

6 minutes ago, Jief_Machak said:

Hi,

Don't think so. I've just tried.

For my information, why are doing it with a custom entry, instead of a .VolumeLabel.txt at volume root ?

@Jief_Machak

Why boot into bigsur? It was 10:13 instead positions bigsur.

bdmesg.log

Spoiler

1419989285_ScreenShot2563-10-24at17_05_47.png.795380330fed53112bbeb83663a06c6e.png

Jief_Machak · October 24, 2020

1 hour ago, naiclub said:

I used "git pull --recurse-submodules && git fetch --recurse-submodules".

You should fetch first.

1 hour ago, naiclub said:

commit e4e57cb33121fb2ec9d574a666441498b83f367e (HEAD -> master, origin/master, origin/HEAD)

You are just 2 commits behind. Commits were yesterday night.

1 hour ago, naiclub said:

13) update Clover (reset changes)

If you have any

doubt, you can :
- use 13) in buildme

- check you are at last commit by checking

- here for Clover : https://github.com/CloverHackyColor/CloverBootloader/commits/master

- here for submodule OpenCorePkg : https://github.com/CloverHackyColor/OpenCorePkg/commits/master

1 hour ago, naiclub said:

Did you change the buildme for us at the time of writing like this?

Last change of buildme was yesterday 16:29 (don't know the timezone though). It's included in e4e57cb33121fb2ec9d574a666441498b83f367e

3 minutes ago, naiclub said:

Why boot into bigsur? It was 10:13 instead positions bigsur.

I guess you got the same problem as @iCanaro. Re-create your preboot entry in your preboot partition.

maclinuxG4 · October 24, 2020

hi bad new jief

i try 4 of dirty version:

First, i couldn't reproduice them including last version.

Second, i use final install (compile clover, then clover install) and install as classic.

( and during 10 days, i did get internal sounds without kernel error in system.log)

but now yes ? how to find this ?

three there is a potential delta between dev (dirty version) that valide, and final version.

So it is important out make and check again tha no software regression are detected.

it is not BS, but Big CHallenge

SavageAUS · October 24, 2020

2 hours ago, naiclub said:

I want to ask if now anyone has installed the full bigsurbeta10 with Clover2125. Have you recently been successful?

I have not tried yet but will do when I get a chance or when we see release.

MacKonsti · October 24, 2020

Hi everyone, thanks to @Jief_Machak and @iCanaro and everyone for your contribution.

Am I right to understand that we still have problems with booting previous macOS(X) versions with Clover?

Perhaps we could focus getting out a stable, pre-OpenCore build that fixes too the issues I have been reading (and trying to understand) in the last 2 pages... together with the patch for target device thing reported?

I know everyone is hot off to boot Big Sur but did you consider the possibility that the final release in a few days may again differ from this latest Beta 10 and there will still be yet more effort to re-understand what's happening?

Just to remind you guys that a nice, stable Clover pre-OpenCore for the rest of us would be really appreciated if it could be built and provided as an official release on GitHub... including the bugfixes reported lately for Mojave or High Sierra for example.

Many thanks to everyone!

Edited October 24, 2020 by MacKonsti

Jief_Machak · October 24, 2020

28 minutes ago, MacKonsti said:

Just to remind you guys that a nice, stable Clover pre-OpenCore

Just for so everyone knows. I fixed the broken TgtBridge in ACPI patch in release 5123. For me, this is the final pre-oc release for people who won't jump to BS. In that version, you can still use AptioMemoryFix or OcQuirks.

If there is still some problem in that version, we'll fix it.

@everyone who will stay with a pre-OCversion, please test and report.

@MacKonsti We will make a package with a "Final pre-OpenCore" release. Just give us some time. We are not sure yet that there is no problem in that version.

CLOVERX64.5123.1.efi

MacKonsti · October 24, 2020

A big thank you to you @Jief_Machak and everyone here, too. Yes please do check for other pre-BigSur and pre-OpenCore issues, as I have read in the previous pages there was an issue with Mojave and High Sierra, correct? It was fixed by @iCanaro if I am not mistaken? That would be great if we could include those, too.

iCanaro · October 24, 2020

solved by me no for sure i'll just provide debug log
and use clover compiled with latest commits

here last Clover CLOVERX64--5125--1934a83d8.efi.zip

https://github.com/CloverHackyColor/CloverBootloader/commit/1934a83d8434ddb5eb4b2d85f975edb0c7ea3e2a

Jief_Machak · October 24, 2020

4 minutes ago, MacKonsti said:

was an issue with Mojave

That was because of a bug in a feature that doesn't exist in 5123.

6 minutes ago, MacKonsti said:

It was fixed by @iCanaro

I pride myself to have been a part of the fix ! :hysterical:

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites