Clover General discussion

chris1111 · November 11, 2020

@iCanaro thanks

Henry2010 · November 11, 2020

OTA to RC2 was done after 2 restarts. :thumbsup_anim:

But it was awkwardly slow for a new SSD... 30mins, srsly??? ...

(Didn't use watchdog=0 as I wanted to see how it would go.)

EDIT:

The RC2 upgrade removed my Command Line Tools. Srsly? :shock:

Edited November 11, 2020 by Henry2010

naiclub · November 11, 2020

Spoiler

975477514_ScreenShot2563-11-11at13_57_13.png.ea79bab0e9e82095e3de8e0094736840.png 153277731_ScreenShot2563-11-11at14_21_22.png.f6284241610e0980354379f138aaa525.png

List of my generation is gone.

Try to install the full RC2.

Edited November 11, 2020 by naiclub

Jief_Machak · November 11, 2020

16 hours ago, MacKonsti said:
Hi everyone, I did take the steps provided on a virgin (never installed gcc or other) system:
$ git clone --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git
cd CloverBootloader
./buildme
Then, I chose option 7 to build all. It installed needed tools (great!!) but I have this error reported (on my Catalina latest):
[...]
mkdir ./bin
make -C VfrCompile VfrLexer.h
BIN_DIR='.' make -C Pccts/dlg
cc -O -I. -I../support/set -I../h -DUSER_ZZSYN -DZZLEXBUFSIZE=65536 -c dlg_p.c
In file included from dlg_p.c:14:
In file included from ../h/pcctscfg.h:61:
../h/pccts_stdio.h:7:10: fatal error: 'stdio.h' file not found
#include <stdio.h>
         ^~~~~~~~~
1 error generated.
make[3]: *** [dlg_p.o] Error 1
make[2]: *** [Pccts/dlg/dlg] Error 2
make[1]: *** [VfrCompile/VfrLexer.h] Error 2
make: *** [Source/C] Error 2
Any idea what is this missing ../h/pccts_stdio.h file missing? Thanks

That's the second time we were reported this.

Looks like a mixed up in compiler PATH. Vfr must be compiled with host compiler and it looks like it's compiled with cross compiler. It doesn't come from your computer.

What if you use "./buildme XCODE8". Clean your Clover folder with "git -f -f -d -x" first. CAREFUL : "git -f -f -d -x" erase every file you created, to only keep the files that are on github. So the effect is that your Clover folder will be in the same state as a freshly cloned repo.

iCanaro · November 11, 2020

hack X570 :thumbsup_anim:

only precaution used, is that I used a specific config for update /installation in which only kernel patches that served big sur were active

Spoiler

iCanaro · November 11, 2020

hack Z370 :thumbsup_anim:

Spoiler

Jief_Machak · November 11, 2020

@everyone : I've reworked the version number problem. Before I commit (I'd like to avoid to commit big mistake ), could test this efi file : CloverX64-2020-11-11-12-57-35-0bbc1e3-dirty-jief.zip

NOTE : because you are (all) so impatient (), you probably have all your kexts in "Other" folder, for the 11.0.1 version. What I'd like you to test is that you can put back your kexts in folder "11", or "11.0" or "11.0.1" (your choice). I also like to know if I haven't introduced a regression for older macOS.

NOTE2: the kext folder your can create is like :

11 : will match version 11.x and 11.x.x

11.0 : will match version 11.0 and 11.0.x

11.0.1 : will match version 11.0.1 only.

for all folder created, you also can create one with "_install", "_normal", "_recovery" to match the OS type.

MacKonsti · November 11, 2020

3 hours ago, Jief_Machak said:

That's the second time we were reported this.

Looks like a mixed up in compiler PATH. Vfr must be compiled with host compiler and it looks like it's compiled with cross compiler. It doesn't come from your computer.

What if you use "./buildme XCODE8". Clean your Clover folder with "git -f -f -d -x" first. CAREFUL : "git -f -f -d -x" erase every file you created, to only keep the files that are on github. So the effect is that your Clover folder will be in the same state as a freshly cloned repo.

Thanks @Jief_Machak

Your command git -f -f -d -x did not work, you meant git clean f -f -d -x right?

That command was accepted.

Then ran ./buildme XCODE8
Selected option 1 and 7 to build all on purpose.

It downloaded some more stuff, not sure what.

Still same error for both options Here's the output. Thanks again for your response. I know you're busy with the BS released tomorrow officially, so when you got some time to check this let me know.

Spoiler


% ./buildme XCODE8

------------------------------------------------------------------------
buildme, Clover r5126 (SHA: 0bbc1e343)
TOOLCHAIN: XCODE8 (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: 7
[CHECK XCODE]
WORKSPACE: /Users/konsti/Desktop/BigSur/CloverBootloader
EDK_TOOLS_PATH: /Users/konsti/Desktop/BigSur/CloverBootloader/BaseTools
CONF_PATH: /Users/konsti/Desktop/BigSur/CloverBootloader/Conf
Copying $EDK_TOOLS_PATH/Conf/build_rule.template
     to /Users/konsti/Desktop/BigSur/CloverBootloader/Conf/build_rule.txt
Copying $EDK_TOOLS_PATH/Conf/tools_def.template
     to /Users/konsti/Desktop/BigSur/CloverBootloader/Conf/tools_def.txt
Copying $EDK_TOOLS_PATH/Conf/target.template
     to /Users/konsti/Desktop/BigSur/CloverBootloader/Conf/target.txt
[BUILD CLOVER]
TOOLCHAIN_DIR: /Users/konsti/Desktop/BigSur/CloverBootloader/toolchain

Status: cctools-949.0.1.tar.gz not found.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1922k  100 1922k    0     0  2013k      0 --:--:-- --:--:-- --:--:-- 2011k
- Creating new RAM disk

Initialized /dev/rdisk3 as a 300 MB case-insensitive HFS Plus volume
-  cctools-949.0.1 extract...
-  cctools-949.0.1 make mtoc...
-  cctools-949.0.1 installing mtoc...
-  cctools-949.0.1 mtoc installed in /Users/konsti/Desktop/BigSur/CloverBootloader/toolchain

- Ejecting RAM disk
"disk3" ejected.
MTOC_PREFIX: /Users/konsti/Desktop/BigSur/CloverBootloader/toolchain/bin/

Status: nasm-2.15.05.tar.xz not found.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  972k  100  972k    0     0   147k      0  0:00:06  0:00:06 --:--:--  288k
- Creating new RAM disk

Initialized /dev/rdisk3 as a 300 MB case-insensitive HFS Plus volume
-  nasm-2.15.05 extract...
-  nasm-2.15.05 configure...
-  nasm-2.15.05 make...
-  nasm-2.15.05 installing...
-  nasm-2.15.05 installed in /Users/konsti/Desktop/BigSur/CloverBootloader/toolchain

- Ejecting RAM disk
"disk3" ejected.
NASM_PREFIX: /Users/konsti/Desktop/BigSur/CloverBootloader/toolchain/bin/
NASM_VER: 2.15.05
Initializing workspace
WORKSPACE: /Users/konsti/Desktop/BigSur/CloverBootloader
EDK_TOOLS_PATH: /Users/konsti/Desktop/BigSur/CloverBootloader/BaseTools
CONF_PATH: /Users/konsti/Desktop/BigSur/CloverBootloader/Conf
Copying $EDK_TOOLS_PATH/Conf/build_rule.template
     to /Users/konsti/Desktop/BigSur/CloverBootloader/Conf/build_rule.txt
Copying $EDK_TOOLS_PATH/Conf/tools_def.template
     to /Users/konsti/Desktop/BigSur/CloverBootloader/Conf/tools_def.txt
Copying $EDK_TOOLS_PATH/Conf/target.template
     to /Users/konsti/Desktop/BigSur/CloverBootloader/Conf/target.txt
Building tools as they are not found
make -C Source/C
Attempting to detect HOST_ARCH from 'uname -m': x86_64
Detected HOST_ARCH of X64 using uname.
mkdir -p .
mkdir ./libs 
make -C Common
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  BasePeCoff.c -o BasePeCoff.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  BinderFuncs.c -o BinderFuncs.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  CommonLib.c -o CommonLib.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  Crc32.c -o Crc32.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  Decompress.c -o Decompress.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  EfiCompress.c -o EfiCompress.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  EfiUtilityMsgs.c -o EfiUtilityMsgs.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  FirmwareVolumeBuffer.c -o FirmwareVolumeBuffer.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  FvLib.c -o FvLib.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  MemoryFile.c -o MemoryFile.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  MyAlloc.c -o MyAlloc.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  OsPath.c -o OsPath.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  ParseGuidedSectionTools.c -o ParseGuidedSectionTools.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  ParseInf.c -o ParseInf.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  PeCoffLoaderEx.c -o PeCoffLoaderEx.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  SimpleFileParsing.c -o SimpleFileParsing.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  StringFuncs.c -o StringFuncs.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  TianoCompress.c -o TianoCompress.o
gcc  -c  -I .. -I ../Include/Common -I ../Include/ -I ../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/X64/  -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-deprecated-declarations -Wno-self-assign -Wno-unused-result -nostdlib -g -O2  PcdValueCommon.c -o PcdValueCommon.o
ar crs ../libs/libCommon.a BasePeCoff.o BinderFuncs.o CommonLib.o Crc32.o Decompress.o EfiCompress.o EfiUtilityMsgs.o FirmwareVolumeBuffer.o FvLib.o MemoryFile.o MyAlloc.o OsPath.o ParseGuidedSectionTools.o ParseInf.o PeCoffLoaderEx.o SimpleFileParsing.o StringFuncs.o TianoCompress.o PcdValueCommon.o
mkdir ./bin
make -C VfrCompile VfrLexer.h
BIN_DIR='.' make -C Pccts/dlg
cc -O -I. -I../support/set -I../h -DUSER_ZZSYN -DZZLEXBUFSIZE=65536 -c dlg_p.c
In file included from dlg_p.c:14:
In file included from ../h/pcctscfg.h:61:
../h/pccts_stdio.h:7:10: fatal error: 'stdio.h' file not found
#include <stdio.h>
         ^~~~~~~~~
1 error generated.
make[3]: *** [dlg_p.o] Error 1
make[2]: *** [Pccts/dlg/dlg] Error 2
make[1]: *** [VfrCompile/VfrLexer.h] Error 2
make: *** [Source/C] Error 2

P.S. I have not downloaded or using any Xcode.app in /Applications/

P.S. All those tools and compilers downloaded, any idea where they are stored? Just to see the space taken, that's all. Thanks!

Edited November 11, 2020 by MacKonsti

Matgen84 · November 11, 2020

26 minutes ago, Jief_Machak said:

@everyone : I've reworked the version number problem. Before I commit (I'd like to avoid to commit big mistake ), could test this efi file : CloverX64-2020-11-11-12-57-35-0bbc1e3-dirty-jief.zip

NOTE : because you are (all) so impatient (), you probably have all your kexts in "Other" folder, for the 11.0.1 version. What I'd like you to test is that you can put back your kexts in folder "11", or "11.0" or "11.0.1" (your choice). I also like to know if I haven't introduced a regression for older macOS.

NOTE2: the kext folder your can create is like :

11 : will match version 11.x and 11.x.x

11.0 : will match version 11.0 and 11.0.x

11.0.1 : will match version 11.0.1 only.

for all folder created, you also can create one with "_install", "_normal", "_recovery" to match the OS type.

@Jief_Machak works fine with 11 folder only. (BS 11.0.1 RC2) :thumbsup_anim:

debug_Jief_11-11-20.log

Jief_Machak · November 11, 2020

9 minutes ago, MacKonsti said:

you meant git clean f -f -d -x right?

Oups. Yes.

9 minutes ago, MacKonsti said:

Then ran ./buildme XCODE8
Selected option 7 to build all on purpose.

Unfortunately, it works as intended my computer. I don't know if it's a macOs version, XCode version or a setup problem.

I can only debug that if you share your screen. With teamviewer, for example.

iCanaro · November 11, 2020

38 minutes ago, Jief_Machak said:

@everyone : I've reworked the version number problem. Before I commit (I'd like to avoid to commit big mistake ), could test this efi file : CloverX64-2020-11-11-12-57-35-0bbc1e3-dirty-jief.zip

NOTE : because you are (all) so impatient (), you probably have all your kexts in "Other" folder, for the 11.0.1 version. What I'd like you to test is that you can put back your kexts in folder "11", or "11.0" or "11.0.1" (your choice). I also like to know if I haven't introduced a regression for older macOS.

NOTE2: the kext folder your can create is like :

11 : will match version 11.x and 11.x.x

11.0 : will match version 11.0 and 11.0.x

11.0.1 : will match version 11.0.1 only.

for all folder created, you also can create one with "_install", "_normal", "_recovery" to match the OS type.

hack Z370 :thumbsup_anim:

no files in the other folder
every macOS with its kexts
folder bigsur named 11
everything OK high sierra, mojave, catalina, BS start correctly without any problem detected... except with high sierra, after starting it, on the return to the GUI of Clover, usual problem, bigsur preboot (BF) with high sierra icon, I had backed up the systemversion.plist, restored and everything was back in place.

For me this is inexplicable... maybe it depends on the theme I use, since it's the same everywhere, I'll sooner or later have to give it a try by changing it

Spoiler

Jief_Machak · November 11, 2020

1 minute ago, iCanaro said:

on the theme I use

I can't imagine a theme being responsible for modifying a preboot partition. I never check, actually, but I think APFS EFI driver is readonly (not sure).

I'd say that HS is mistakenly updating the BS preboot partition.

All you disk UUID and APFS container UUID are different ? (you can see them in debug.log).

Are you the only one to have that, so far ?

iCanaro · November 11, 2020

6 minutes ago, Jief_Machak said:

I can't imagine a theme being responsible for modifying a preboot partition. I never check, actually, but I think APFS EFI driver is readonly (not sure).

I'd say that HS is mistakenly updating the BS preboot partition.

All you disk UUID and APFS container UUID are different ? (you can see them in debug.log).

Are you the only one to have that, so far ?

name Preboot bigsur --> 4EA0011C-1C8B-476D-BD5D-1AE8F7648F64

debug.log

Jief_Machak · November 11, 2020

4 minutes ago, iCanaro said:

name Preboot bigsur --> 4EA0011C-1C8B-476D-BD5D-1AE8F7648F64

Can't see any APFS container for HS. Is it installed on HFS ?

iCanaro · November 11, 2020

high sierra and mojave are installed in HFS+ (and this in all the hacks)

@Jief_Machak you say that could be the cause?

Jief_Machak · November 11, 2020

Just now, iCanaro said:

high sierra and mojave are installed in HFS+ (and this in all the hacks)

@Jief_Machak you say that could be the cause?

I wouldn't be surprised. If I remember well, Apple didn't support that. I could easily imagine a piece of software trying to update preboot : first thing is to get APFS container UUID. There isn't. But because it's not an expected state, so it's not tested. Result is that it's probably using the last container it found, because it's the last one it iterated over.

Most of programmers programs for when everything is in an expected state, and don't check first it's the case or not. I really wouldn't be surprised at all...

iCanaro · November 11, 2020

interesting hypothesis, but the "anomalous" behavior from me occurs only with high sierra, never happened with mojave, also in HFS+

Jief_Machak · November 11, 2020

2 minutes ago, iCanaro said:

interesting hypothesis, but the "anomalous" behavior from me occurs only with high sierra, never happened with mojave, also in HFS+

Yes, the programmer get fired, and the software piece was updated to fail instead of updating the wrong preboot folder !

iCanaro · November 11, 2020

4 hours ago, Jief_Machak said:

That's the second time we were reported this.

Looks like a mixed up in compiler PATH. Vfr must be compiled with host compiler and it looks like it's compiled with cross compiler. It doesn't come from your computer.

What if you use "./buildme XCODE8". Clean your Clover folder with "git -f -f -d -x" first. CAREFUL : "git -f -f -d -x" erase every file you created, to only keep the files that are on github. So the effect is that your Clover folder will be in the same state as a freshly cloned repo.

I have to thank you, thanks to this advice, I finally managed to compile Clover on the Catalina of the X570, before it always gave some mistake, this time everything OK :thumbsup_anim:

iCanaro · November 11, 2020

2 hours ago, Jief_Machak said:

@everyone : I've reworked the version number problem. Before I commit (I'd like to avoid to commit big mistake ), could test this efi file : CloverX64-2020-11-11-12-57-35-0bbc1e3-dirty-jief.zip

NOTE : because you are (all) so impatient (), you probably have all your kexts in "Other" folder, for the 11.0.1 version. What I'd like you to test is that you can put back your kexts in folder "11", or "11.0" or "11.0.1" (your choice). I also like to know if I haven't introduced a regression for older macOS.

NOTE2: the kext folder your can create is like :

11 : will match version 11.x and 11.x.x

11.0 : will match version 11.0 and 11.0.x

11.0.1 : will match version 11.0.1 only.

for all folder created, you also can create one with "_install", "_normal", "_recovery" to match the OS type.

tested on the AMD X570, catalina starts but big sur does not start, in my opinion does not load or correctly apply kernel patches for bigsur.
I checked config carefully, kexts in folder 11, but does not start
here are the logs preboot.log debug.log

With the previous Clover everything OK.

Jief_Machak · November 11, 2020

1 minute ago, iCanaro said:

tested on the AMD X570, catalina starts but big sur does not start, in my opinion does not load or correctly apply kernel patches for bigsur.
I checked config carefully, kexts in folder 11, but does not start
here are the logs preboot.log debug.log

With the previous Clover everything OK.

Yes, don't touch your config.

I completely forgot to check patches... On my way.

naiclub · November 11, 2020

@Jief_Machak

Just a moment ago I updated CatalinamacOS 10.15.7 (19H2) to macOS 10.15.7 (19H15). Smooth via pre-boot.

ct.log

hs.log

Jief_Machak · November 11, 2020

Yes, I see "[OS: 11.0.1 | MatchOS: 11 | MatchBuild: no] ==> not allowed by OS".

Could you send me a debug.log when it's working (same computer) ?

iCanaro · November 11, 2020

17 minutes ago, Jief_Machak said:

Yes, I see "[OS: 11.0.1 | MatchOS: 11 | MatchBuild: no] ==> not allowed by OS".

Could you send me a debug.log when it's working (same computer) ?

X570 AMD

of course you do, here it is debug.log

notes: this same config if in kernel patches i define bigsur with 11 does not start
if you impose 11.x instead then start

Jief_Machak · November 11, 2020

3 minutes ago, iCanaro said:

this same config if in kernel patches i define bigsur with 11 does not start

Not great for me, as I want to compare behaviour in the exact same context. Here, you modified config.plist. In the end, I'm not sure of what was working before and not working anymore with the version I've sent...

I'd prefer if you can restore the config.plist that was working with 5126 and not working with my last version, and send me the 2 debug.log.

Between the 2 debug.log, there should be no modification at all.

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