Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,135 posts in this topic

Recommended Posts

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.

Link to comment
Share on other sites
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

Link to comment
Share on other sites
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

Link to comment
Share on other sites
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
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

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.

Link to comment
Share on other sites
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 ?

Link to comment
Share on other sites
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.

Link to comment
Share on other sites
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.

Link to comment
Share on other sites
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?

Link to comment
Share on other sites
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.

Link to comment
Share on other sites
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>

Link to comment
Share on other sites
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.

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

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

Take this version. It has no console switching

CLOVERX64.efi.zip

 

1 hour ago, kushwavez said:

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.

First one 

            <key>RenameDevices</key>
            <dict>
                <key>_SB.PCI0.RP09._PS0</key>
                <string>XPS0</string>
            </dict>

Same for others but look your DSDT for exact names/pathes.

Count and Skip are not correct because we must rename all occurence of the name.

Long path in Clover guaranties that rename will be only where needed.

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

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

GUI->

<key>ProvideConsoleGop</key>

<true/>

<key>ConsoleMode</key>

<string>0</string>

Unfortunately this new CLOVERX64.efi still got crashed on "O" selection and unable to save debug log.

Only successful booting log and new config.plist are attached here.

Is it possible related to OpenCore integration codes because older than Clover 5116 seems no such a crash.

2021-3-4_7-40-21_CLOVERX64.EFI.log config.plist

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

Impossible that it is related to opencore integration.

Can you confirm that 5116 works and 5117 no?

Yes, 5116 can boot 10.15.7 without such a crash but it can not boot Big Sur without integration of OpenCore.

Edited by jsl2000
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

But the crash is before system loading so doesn't matter what system you want to boot.

I want to refine my question.

Is it true that "O" in Clover GUI causes crash on version 5117 and doesn't on 5116?

13 hours ago, jsl2000 said:

Unfortunately this new CLOVERX64.efi still got crashed on "O" selection and unable to save debug log.

Only successful booting log and new config.plist are attached here.

Is it possible related to OpenCore integration codes because older than Clover 5116 seems no such a crash.

2021-3-4_7-40-21_CLOVERX64.EFI.log 59.23 kB · 3 downloads config.plist 17.95 kB · 2 downloads

There is a question. What is the crash with this my new version and why there is no debug.log. It must be!

Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted (edited)

@Slice I test Legacy bootx64 on ESP on my OptiPlex 790 Intel I5 2500k / Geforce GT 710 Legacy mode Red screen here also a user notice the same on my forum on X58 P6TSE

R5129 no issue red screen

Edited by chris1111
Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
11 hours ago, Slice said:

But the crash is before system loading so doesn't matter what system you want to boot.

I want to refine my question.

Is it true that "O" in Clover GUI causes crash on version 5117 and doesn't on 5116?

There is a question. What is the crash with this my new version and why there is no debug.log. It must be!

I have double checked and quite sure that there is no debug log produced on crashed with red screen.

No such issue at Clover 5116 which can not boot/install Big Sur yet due to lack of OpenCore integration.

Successful boot log of 10.11.6 was attached for your reference.

I found the other users (e.g. chris1111) who use legacy booting also have the same problem as mine !

debug.log

Edited by jsl2000
Link to comment
Share on other sites
jsl2000
jsl2000
Posted
Posted (edited)
7 hours ago, chris1111 said:

@Slice I test Legacy bootx64 on ESP on my OptiPlex 790 Intel I5 2500k / Geforce GT 710 Legacy mode Red screen here also a user notice the same on my forum on X58 P6TSE

R5129 no issue red screen

Can you share your legacy booting Clover 5129 (CLOVERX64.efi) & config.plist without such a crash for me to test ? If the CLOVERX64.efi is release version please let me know its commit code.

My version of 5129 still got crash on booting if "O" is entered.

Screen Shot 2021-03-05 at 2.09.57 PM.png

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

This debuglog has no interest because I have to see a moment of crash.

Thanks.

I found Clover 5127 can boot Big Sur without such a crash on "Option" selection.

Screen Shot 2021-03-05 at 4.15.53 PM.png

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