Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

jsl2000
jsl2000
Posted
Posted (edited)
56 minutes ago, Slice said:

Reduce BIOS overclock. It is too big!

Thanks again !

The same problem remained without any BIOS overclock.

Two debug logs are attached:

The first one when "O" was entered and crashed with red screen errors showing.

The second one after successful booting of Big Sur 11.3 beta.

2021-2-27_9-35-20_CLOVERX64.EFI.log 2021-2-27_9-36-14_CLOVERX64.EFI.log

Edited by jsl2000
Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted
21 hours ago, Allan said:

I've visit the Sinetek's page and noticed that he had updated the kext 11 days ago. Now, with this new version everything works just fine :thumbsup_anim:

 

Can you kindly share the URL please as I have not found it? GitHub has a project but it seems abandoned.... Thank you (or send me a PM to not flood this thread, better)

 

On 2/24/2021 at 11:46 PM, MacKonsti said:

Hi everyone, @Slice and @Jief_Machak thank you again for your hard work.

Is the key/function DeleteUnused of any use, these days? What is it supposed to do today? I recall that it was supposed to remove Device XYZ from DSDTs/ACPI Tables, but specific names like floppies or other generic-named devices.

Can you briefly comment on its usefulness in Clover releases from the past 1-2 years? (or even r5xxx)

 

Coming back to Clover discussion and knowledge, please can I kindly ask you @Slice on this Clover key? Does it really have a meaning? Is it trying to remove Device (XYZ) from a fixed-list of known devices for example? (that aren't Mac supported anyway) Thank you.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
58 minutes ago, MacKonsti said:

 

Can you kindly share the URL please as I have not found it? GitHub has a project but it seems abandoned.... Thank you (or send me a PM to not flood this thread, better)

 

 

Coming back to Clover discussion and knowledge, please can I kindly ask you @Slice on this Clover key? Does it really have a meaning? Is it trying to remove Device (XYZ) from a fixed-list of known devices for example? (that aren't Mac supported anyway) Thank you.

This key will delete these devices 

    DsdtLen = DeleteDevice("CRT_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("DVI_"_XS8, temp, DsdtLen);
    //good company
    DsdtLen = DeleteDevice("SPKR"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("ECP_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("LPT_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("FDC0"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("ECP1"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("LPT1"_XS8, temp, DsdtLen);

Why are you interesting?

  • Thanks 1
Link to comment
Share on other sites
MacKonsti
MacKonsti
Posted
Posted (edited)
1 hour ago, Slice said:

This key will delete these devices 



    DsdtLen = DeleteDevice("CRT_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("DVI_"_XS8, temp, DsdtLen);
    //good company
    DsdtLen = DeleteDevice("SPKR"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("ECP_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("LPT_"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("FDC0"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("ECP1"_XS8, temp, DsdtLen);
    DsdtLen = DeleteDevice("LPT1"_XS8, temp, DsdtLen);

Why are you interesting?

 

Hi @Slice thank you for your valuable input on the deeper features of Clover.

As mentioned in my earlier post, I am in the process of updating the guides in my hack repo and wanted to ask you, since you have access and understanding of Clover code.

I have been using DeleteUnused for years but I had a feeling that this was no longer needed as it was most likely addressing to older PCs and their ACPI tables, with device names that no longer exist in modern PCs (last 5-6 years at least).

So thanks for confirming that DeleteUnused=TRUE key is no longer needed on my hacks!

Edited by MacKonsti
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
1 hour ago, MacKonsti said:

 

Hi @Slice thank you for your valuable input on the deeper features of Clover.

As mentioned in my earlier post, I am in the process of updating the guides in my hack repo and wanted to ask you, since you have access and understanding of Clover code.

I have been using DeleteUnused for years but I had a feeling that this was no longer needed as it was most likely addressing to older PCs and their ACPI tables, with device names that no longer exist in modern PCs (last 5-6 years at least).

So thanks for confirming that DeleteUnused=TRUE key is no longer needed on my hacks!

In the past, on very old PC this patch was very useful to switch from black screen to working system.

  • Thanks 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
19 hours ago, jsl2000 said:

Thanks again !

The same problem remained without any BIOS overclock.

Two debug logs are attached:

The first one when "O" was entered and crashed with red screen errors showing.

The second one after successful booting of Big Sur 11.3 beta.

2021-2-27_9-35-20_CLOVERX64.EFI.log 10.65 kB · 1 download 2021-2-27_9-36-14_CLOVERX64.EFI.log 89.97 kB · 1 download

Install OpenRuntime.efi.

 

@Jief_Machak

See. For legacy boot we lived without AptioMemoryFix and all was good.

Then we switch to OpenRuntime that does almost same functions switched on-off by Quirks.

Then we switch to Clover+OC and now legacy boot can't works without OpenRuntime. Red Screen panic. Why?

The problem seems related to ConsoleGop?

Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
3 hours ago, Slice said:

Install OpenRuntime.efi.

 

@Jief_Machak

See. For legacy boot we lived without AptioMemoryFix and all was good.

Then we switch to OpenRuntime that does almost same functions switched on-off by Quirks.

Then we switch to Clover+OC and now legacy boot can't works without OpenRuntime. Red Screen panic. Why?

The problem seems related to ConsoleGop?

Thanks.

But install OpenRuntime.efi in EFI/CLOVER/drivers/BIOS still got the same crash if "O" was selected during booting.

I guess there's something incompatibility in BOOTX64.efi after Clover + OC integration because it occurred before in AMD CPU hackintoshs with older Clover too.

Edited by jsl2000
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
2 hours ago, jsl2000 said:

Thanks.

But install OpenRuntime.efi in EFI/CLOVER/drivers/BIOS still got the same crash if "O" was selected during booting.

I guess there's something incompatibility in BOOTX64.efi after Clover + OC integration because it occurred before in AMD CPU hackintoshs with older Clover too.

If there is legacy boot then BOOTX64.EFI is unused.

The chain is follow

BIOS-> MBR-> PBR-> boot (for example boot6)-> CLOVERX64.efi

because boot6 directly calls /EFI/CLOVER/CLOVERX64.EFI

 

AMD CPU is very different story.

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

The problem is follow:

When we start legacy Clover without OpenRuntime then start system by timeout then Clover crashed.

Снимок экрана 2021-02-28 в 19.24.14.png

It happen with Clover 5129+ but not with 5128.

 

The I made git bisection. Yes. There is the result 

iMac2017:CloverBootloader sergey$ git bisect bad
16c627596faff40d2d3b91d308aeeb4e16b18575 is the first bad commit
commit 16c627596faff40d2d3b91d308aeeb4e16b18575
Author: jief666 <github.com@jfa.knudsen.ovh>
Date:   Sun Jan 31 12:50:23 2021 +0300

    Rename OSVersion to macOSVersion.
    Fixed some icons ordering in main menu.
    Fixed macOs version detection for custom entries.
    Fixed main Big Sur partition appearing in menu.
    Refactor IsValidGuidAsciiString.

:160000 160000 620e4378f9a3d0558c144936e3fc5affbf445e44 78708c2edcfb358a6577f92a6afda1f99f2f48a0 M	OpenCorePkg
:040000 040000 faff6df313e126409cd11edce0266cebd289c994 c2827fd686b8bf596529a0b55d7cde26121d5b4a M	Xcode
:040000 040000 20082b1202448709b95f0a2f0ff1372da8a22e4a 405dacb7b36f725cc2b6c6368a7125e22bb1bde9 M	rEFIt_UEFI
iMac2017:CloverBootloader sergey$

During the bisection OpenCore subproject remained unchanged while the crash inside it between messages 

7:725  0:000  OCST: Missing vault data, ignoring...
7:768  0:043  config-oc.plist isn't use at all

 

  • Like 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
11 hours ago, jsl2000 said:

Thanks.

But install OpenRuntime.efi in EFI/CLOVER/drivers/BIOS still got the same crash if "O" was selected during booting.

I guess there's something incompatibility in BOOTX64.efi after Clover + OC integration because it occurred before in AMD CPU hackintoshs with older Clover too.

Can you compile and test new commit? I am not sure you have the same issue.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
On 2/27/2021 at 12:57 PM, jsl2000 said:

Thanks again !

The same problem remained without any BIOS overclock.

Two debug logs are attached:

The first one when "O" was entered and crashed with red screen errors showing.

The second one after successful booting of Big Sur 11.3 beta.

2021-2-27_9-35-20_CLOVERX64.EFI.log 10.65 kB · 1 download 2021-2-27_9-36-14_CLOVERX64.EFI.log 89.97 kB · 1 download

Your break is inside DUET i.e. boot6 file. Try to use another one from older revision.

Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
4 hours ago, Slice said:

Your break is inside DUET i.e. boot6 file. Try to use another one from older revision.

Thank you very much for your prompt reply and kind help.

I just waked up and my mind is not so clear now.

I have no experience to compile the new commit of Clover.

Can you show me how to get proper older revision of DUET i.e. boot6 file because I found copy from 10.11.6 Partition/usr/standalone/i386/boot or /i386/x64/boot6 to Legacy USB and rename to boot can not solve this problem.

Do you think re-install with Clover r.5128 or older version can fix it ?

 

Edited by jsl2000
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
7 hours ago, jsl2000 said:

Thank you very much for your prompt reply and kind help.

I just waked up and my mind is not so clear now.

I have no experience to compile the new commit of Clover.

Can you show me how to get proper older revision of DUET i.e. boot6 file because I found copy from 10.11.6 Partition/usr/standalone/i386/boot or /i386/x64/boot6 to Legacy USB and rename to boot can not solve this problem.

Do you think re-install with Clover r.5128 or older version can fix it ?

 

Open any old release. For example 5103

https://github.com/CloverHackyColor/CloverBootloader/releases/tag/5103

Download CloverV2-5103.zip

Unpack.

Take CloverV2-5103->Bootloader->x64->boot6

Rename it to "boot" and copy to /Volumes/EFI/

Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
40 minutes ago, Slice said:

Open any old release. For example 5103

https://github.com/CloverHackyColor/CloverBootloader/releases/tag/5103

Download CloverV2-5103.zip

Unpack.

Take CloverV2-5103->Bootloader->x64->boot6

Rename it to "boot" and copy to /Volumes/EFI/

Thanks again !

I have followed your suggestion step by step and the result is the same as before:

I can boot to desktop of Big Sur without any problem, but got red screen crash immediately if select "O" on booting menu for Option.

So it could be related to the newer CLOVERX64.efi which integrated with OpenCore causing such an unexpected abnormal phenomenon.

Can you provide any new CLOVERX64.efi for me to test/fix it ?

Edited by jsl2000
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
1 hour ago, jsl2000 said:

Thanks again !

I have followed your suggestion step by step and the result is the same as before:

I can boot to desktop of Big Sur without any problem, but got red screen crash immediately if select "O" on booting menu for Option.

So it could be related to the newer CLOVERX64.efi which integrated with OpenCore causing such an unexpected abnormal phenomenon.

Can you provide any new CLOVERX64.efi for me to test/fix it ?

I can provide you new Clover only at evening when I will at home. May be someone else can compile latest commit?

Anyway your question is in priority. I will investigate it.

Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
38 minutes ago, kushwavez said:

Sure thing mate

here you are @jsl2000 

CloverX64-RELEASE_XCODE8-20210228224257-45801ef.zip 698.85 kB · 1 download

Thanks for your kind help and prompt reply.

Unfortunately this new CLOVERX64.efi got worse than previous release version of 5131.

It got red screen panic immediately on booting and the first line of error codes changed from previous 0x000000000000000D to 0x000000000000000E besides its file size was bigger than previous version (1.5 MB vs. 1.3 MB).

1 hour ago, Slice said:

I can provide you new Clover only at evening when I will at home. May be someone else can compile latest commit?

Anyway your question is in priority. I will investigate it.

Thanks for your kind help and prompt reply.

Unfortunately this new CLOVERX64.efi got worse than previous release version of 5131.

It got red screen panic immediately on booting and the first line of error codes changed from previous 0x000000000000000D to 0x000000000000000E besides its file size was bigger than previous version (1.5 MB vs. 1.3 MB).

Edited by jsl2000
Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted
10 minutes ago, Slice said:

1.5 vs 1.3 is normal because gcc makes more optimisation than clang.

But this crash may be related to the compiler bug.

Looking forward to your new CLOVERX64.efi as soon as possible to test and fix my booting problem.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
4 hours ago, jsl2000 said:

Looking forward to your new CLOVERX64.efi as soon as possible to test and fix my booting problem.

Take please the version for test, try to enter "Option" and give me the debug.log.

It should ended with messages

test 1

test 2

and so on. I wish to know when it crashes.

CLOVERX64.efi.zip

  • Like 1
Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
8 hours ago, Slice said:

Take please the version for test, try to enter "Option" and give me the debug.log.

It should ended with messages

test 1

test 2

and so on. I wish to know when it crashes.

CLOVERX64.efi.zip 647.17 kB · 3 downloads

Thanks for your kind help and prompt reply again !

It seems going further before crashed with red screen panic.

Not sure whether it related to this new version or addition of DataHubDxe.efi & EmuVariableUefi.efi or not.

My current boot file and config.plist as well as debug log are attached:

Log 1: Successful booting to desktop of Big Sur without problem.

Log 2: Crashed immediately when "O" was entered.

P.S.

I need go to hospital for medical service of out-patients from 8 am to 4 pm today.

Will waiting for your solution and re-testing then.

boot config.plist 2021-3-1_23-10-19_CLOVERX64.EFI.log 2021-3-1_23-18-49_CLOVERX64.EFI.log

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