Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

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.

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.

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
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/

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
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.

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
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.

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
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
Slice
Slice
Posted
Posted

Now there is a crash at EmuVariable.

As you have legacy Clover then you have to correct you set of efi drivers 

8:490  0:000  === [ LoadDrivers ] =============================
8:503  0:013  Loading HFSPlus.efi  status=Success
8:517  0:013   - driver needs connecting
8:517  0:000  Loading apfs-64.efi  status=Success
8:596  0:079   - driver needs connecting
8:596  0:000  Loading NvmExpressDxe-64.efi  status=Success
8:610  0:013   - driver needs connecting
8:610  0:000  Loading DataHubDxe.efi  status=Success
8:636  0:026  Loading EmuVariableUefi.efi  status=Success
8:650  0:013  EmuVariableUefi Initialize: VariableCommonInitialize = Success, orig services stored, install gEmuVariableControlProtocolGuid = Success
8:650  0:000  Loading AudioDxe-64.efi  status=Success
8:664  0:013   - driver needs connecting
8:664  0:000  Loading HfsPlusLegacy.efi  status=Success
8:704  0:039   - driver needs connecting
8:704  0:000  5 drivers needs connecting ...

Exclude HFSPlus.efi because you have HfsPlusLegacy.efi.

Exclude DataHubDxe.efi because it embedded into boot6. Moreover, it also embedded into Clover 5131.

Exclude EmuVariableUefi.efi because it is for UEFI boot. Lecagy Clover has own Variables driver.

Exclude AudioDxe.efi for the test. You may include it later when all will work.

I am not sure if you have M2 controller so if not  you may exclude NvmExpressDxe-64.efi.

And try again.

jsl2000
jsl2000
Posted
Posted
2 hours ago, Slice said:

Now there is a crash at EmuVariable.

As you have legacy Clover then you have to correct you set of efi drivers 


8:490  0:000  === [ LoadDrivers ] =============================
8:503  0:013  Loading HFSPlus.efi  status=Success
8:517  0:013   - driver needs connecting
8:517  0:000  Loading apfs-64.efi  status=Success
8:596  0:079   - driver needs connecting
8:596  0:000  Loading NvmExpressDxe-64.efi  status=Success
8:610  0:013   - driver needs connecting
8:610  0:000  Loading DataHubDxe.efi  status=Success
8:636  0:026  Loading EmuVariableUefi.efi  status=Success
8:650  0:013  EmuVariableUefi Initialize: VariableCommonInitialize = Success, orig services stored, install gEmuVariableControlProtocolGuid = Success
8:650  0:000  Loading AudioDxe-64.efi  status=Success
8:664  0:013   - driver needs connecting
8:664  0:000  Loading HfsPlusLegacy.efi  status=Success
8:704  0:039   - driver needs connecting
8:704  0:000  5 drivers needs connecting ...

Exclude HFSPlus.efi because you have HfsPlusLegacy.efi.

Exclude DataHubDxe.efi because it embedded into boot6. Moreover, it also embedded into Clover 5131.

Exclude EmuVariableUefi.efi because it is for UEFI boot. Lecagy Clover has own Variables driver.

Exclude AudioDxe.efi for the test. You may include it later when all will work.

I am not sure if you have M2 controller so if not  you may exclude NvmExpressDxe-64.efi.

And try again.

Thanks for your kind help and prompt reply again !

It crashed with red screen panic before test2 following your advice.

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

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

2021-3-2_7-56-44_CLOVERX64.EFI.log 2021-3-2_8-26-50_CLOVERX64.EFI.log

Slice
Slice
Posted
Posted

The crash is inside boot6 

  MsgLog("test 1\n");
    Status = GraphicsOutput->SetMode(GraphicsOutput, ModeNumber);
  MsgLog("test 2\n");
  const char* strStatus = efiStrError(Status);

Take other version for test

Upzip and place into /Volume/EFI/

 

Or changes screen resolution to 1280x800 or 1280x1024

boot.zip

jsl2000
jsl2000
Posted
Posted (edited)
11 hours ago, Slice said:

The cash is inside boot6 



  MsgLog("test 1\n");
    Status = GraphicsOutput->SetMode(GraphicsOutput, ModeNumber);
  MsgLog("test 2\n");
  const char* strStatus = efiStrError(Status);

Take other version for test

Upzip and place into /Volume/EFI/

 

Or changes screen resolution to 1280x800 or 1280x1024

boot.zip 373.71 kB · 1 download

I have copy your boot and change resolution to 1280x800 , 1280x1024 or 1024x768 all got the same crash on enter "O".

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

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

It can pass test1 and stop before test2 shown.

2021-3-3_13-5-16_CLOVERX64.EFI.log 2021-3-3_5-16-4_CLOVERX64.EFI.log

Edited by jsl2000
jsl2000
jsl2000
Posted
Posted
1 minute ago, Slice said:

Are you sure the change of "boot" file took place? Or you are still using old boot?

Try to use boot7 renamed to boot. In this case you will see number 7_ at the left screen corner at initial time.

I am quite sure about it because it shows 6 during booting.

Should I try boot7 instead ?

Slice
Slice
Posted
Posted

I have nothing to do with Clover.

- the error inside boot file which works on thousand computers

- you videocard if Nvidia Kepler which works on all computers.

What else?

Just now, jsl2000 said:

I am quite sure about it because it shows 6 during booting.

Should I try boot7 instead ?

Yes try.

jsl2000
jsl2000
Posted
Posted
5 minutes ago, Slice said:

I have nothing to do with Clover.

- the error inside boot file which works on thousand computers

- you videocard if Nvidia Kepler which works on all computers.

What else?

Yes try.

Unfortunately boot7 can not boot my Clover 5131.

It reboot immediately after shown 7.

Slice
Slice
Posted
Posted

Ok, then return to boot6 which I upload.

I may propose to prepare special Clover for you with commented out the crash line assuming you will use fixed resolution.

But I can compile only at evening. Someone else?

jsl2000
jsl2000
Posted
Posted
8 minutes ago, Slice said:

Ok, then return to boot6 which I upload.

I may propose to prepare special Clover for you with commented out the crash line assuming you will use fixed resolution.

But I can compile only at evening. Someone else?

That's all right for me because I can wait for your special version until you're available.

Slice
Slice
Posted
Posted
6 hours ago, jsl2000 said:

That's all right for me because I can wait for your special version until you're available.

Before I make you new version, test please correction in config.plist:

GUI->

<key>ProvideConsoleGop</key>

<true/>

<key>ConsoleMode</key>

<string>0</string>

kushwavez
kushwavez
Posted
Posted

How can I transform OpenCore ACPI patches to Clover?

In OC I have these (and more like these) for my Thunderbolt 3 controller on X1C6.

(all patches are here: https://github.com/tylernguyen/x1c6-hackintosh/blob/master/EFI-OpenCore/EFI/OC/config.plist, and the TB3*.amls for them are in EFI/OC/ACPI) 

TableSignature: SSDT
OemTableId: 52565037 52746433
TableLength: 7453
Find: 5F505330
Replace: 58505330
Comment: TB RP09:_PS0 to RP09:XPS0
Count: 1
Find: 5F494E49
Replace: 58494E49
Comment: RP09._INI to RP09.XINI for ICM disable
Count: 1
Skip: 11
TableSignature: SSDT
OemTableId: 50726F6A 53736474
TableLength: 6103
Find: 5F555043
Replace: 58555043
Comment: XHC1: _UPC to XUPC

 

If I simply just put the Find & Replace value in Clover, Thunderbolt 3 does not work unfortunately.

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