Jump to content
30960 posts in this topic

Recommended Posts

16 minutes ago, kushwavez said:

Clover cannot boot with this, error:

"_initialize : m_KextsDir != NULL

A fatal error happened. System halted."

no debug.log created.

 

IMG_3324.jpg

Wow, that looks that something that can't happen... and yet...

I've changed the message. Try this CloverX64-2020-10-22-16-47-28-bef59cc-dirty-jief.zip

1 hour ago, Jief_Machak said:

@iCanaro : start by doing "diskutil apfs updatePreboot" and see if the icon is still HS.

didn't solve
by the way, I do not know if it is normal or a strangeness, after the restart changes position in the list the preboot of big sur
 

Spoiler

146055409_Schermata2020-10-22alle15_44_19.thumb.png.769b5b93fb41b878332ff71a1d8752ab.png1447511298_Schermata2020-10-22alle15_47_47.thumb.png.5c569200697a1c3b88fa21552e5b3f8b.png

 

  • Confused 1
6 minutes ago, iCanaro said:

didn't solve
by the way, I do not know if it is normal or a strangeness, after the restart changes position in the list the preboot of big sur
 

  Hide contents

146055409_Schermata2020-10-22alle15_44_19.thumb.png.769b5b93fb41b878332ff71a1d8752ab.png1447511298_Schermata2020-10-22alle15_47_47.thumb.png.5c569200697a1c3b88fa21552e5b3f8b.png

 

Not sure what do you mean by "position". If you're talking about the name of the disk (disk2 instead of disk1) : there is specific order. Even your boot disk can be disk2. It may change at every boot.

 

Do a "sudo diskutil mount disk{number}" of your BS preboot. Then, with finder, you can go to /Volumes/Preboot, zip and send it to me.

  • Thanks 1
10 minutes ago, Jief_Machak said:

Wow, that looks that something that can't happen... and yet...

I've changed the message. Try this CloverX64-2020-10-22-16-47-28-bef59cc-dirty-jief.zip

 

I took the previous file, but opted for the most recent one, and I have the same result: debug.log

13 minutes ago, Jief_Machak said:

Wow, that looks that something that can't happen... and yet...

I've changed the message. Try this CloverX64-2020-10-22-16-47-28-bef59cc-dirty-jief.zip

Same error, but now it's not "m_KextsDir" but "Kexts dir"

no debug.log

1 hour ago, Jief_Machak said:

The commit "refactor selfOem. Created getConfigDir... methods" is 70988228c43bccdbf2bb71acc5d708b70f9872fc, but you example is "build id: 20201021172059-1803805".

Send at least 2 debug.log, each one containing ONE boot, renaming the log so it's clear which one worked and which one didn't.

Or setup a repo we can share. See https://jief-machak.gitbook.io/cloverhelp/

Your screenshot was in French. I can help you in French.

 

the boot are the same in both case, that the problem. No diff

 

i saw the difference only in system.log with the error in kernel.

 

in my opinion,  somes tests on specific version  (at high level) could be done without many modifications, to be sure, that there not a commit that not fix, but avoid this problem anymore.

 

there are somes commit after that are important, specially console, clean and install/ update openrunetime.efi manuel, until clover fix it.

But i am not sur for other. are they necessay ? i don't know, because a lot of configuration existent now, and need to be properly test or integrated.

 

iti not me to answer, but we need to some thing focus on a specific version and make more test on various mac os.

15 minutes ago, Jief_Machak said:

 

boot OK

slightly slower than the last commit you posted I always encounter the same problem - Preboot disk's preboot is repeated on both partitions I have BigSur installed twice for testing and the names are different but it always only shows the name of one in the two preboot!

I changed the machine to not have all those disks and to be able to make a mess I leave 2 prints of the Clover boot image to see the name he repeats

 

Google Translate !

 

HP Envy Recline 23-K300BR

i3-4130T

intel HD4400 (Nvidia 830A Optimus desactived DSDT)

SSD 240 GO

8 GO ram

 

Spoiler

screenshot1.thumb.png.cef18880a74a1c2d267081ff3b993283.pngscreenshot0.thumb.png.f5e097e3f42606e690fde853ceeec88c.pngprint menu boot Clover problem

 

debug.log

  • Like 1

Guys, guys, please, take turns !

@PG7 : if it doesn't prevent you to boot, I'll focus on the other ones. Remind me in a day or 2.

@kushwavez this one CloverX64-2020-10-22-16-47-28-bef59cc-dirty-jief.zip ?

EDIT : @kushwavez Sorry, no it's not for you.

EDIT2 : @JorgeMax this for you CloverX64-2020-10-22-16-47-28-bef59cc-dirty-jief.zip

@kushwavez Can I have a picture of the screen ?

Edited by Jief_Machak
12 minutes ago, Jief_Machak said:

Guys, guys, please, take turns !

@PG7 : if it doesn't prevent you to boot, I'll focus on the other ones. Remind me in a day or 2.

@kushwavez this one CloverX64-2020-10-22-16-47-28-bef59cc-dirty-jief.zip ?

EDIT : @kushwavez Sorry, no it's not for you.

EDIT2 : @JorgeMax this for you CloverX64-2020-10-22-16-47-28-bef59cc-dirty-jief.zip

@kushwavez Can I have a picture of the screen ?

 

Same result: debug.log

 

Friend I thank you too much for your effort, but it will work

Sorry guys, my build system failed me and I kept sending you the same version (16:47) !

Try this CloverX64-2020-10-22-18-08-14-6a96d48-dirty-jief.zip

@kushwavez I've added message on screen. If you still get the panic, take a picture.

@JorgeMax Let's hope ! Keep sending me debug.log if it fails.

  • Like 1
28 minutes ago, Jief_Machak said:

Sorry guys, my build system failed me and I kept sending you the same version (16:47) !

Try this CloverX64-2020-10-22-18-08-14-6a96d48-dirty-jief.zip

@kushwavez I've added message on screen. If you still get the panic, take a picture.

@JorgeMax Let's hope ! Keep sending me debug.log if it fails.

 

In the same: debug.log

18 minutes ago, Jief_Machak said:

You're messages are appeared: 

_initialize : enter.
Kexts dir = '\EFI\CLOVER\Kexts'
_initialize : leave.
initialize : leave. Status=Success.

They're repeating for 14 times tho (reInitialize): 

Spoiler

CloverX64-2020-10-22-18-08-14-6a96d48.thumb.jpg.55398fbc48f64b840abde6ee6ac0ad9f.jpg

reInitialize : enter.
closeHandle : enter.
closeHandle : leave.
_initialize : enter.
Kexts dir = '\EFI\CLOVER\Kexts'
_initialize : leave.
reInitialize : leave. Status=Success.

The installed system booted up fine, but with the USB Big Sur Beta 10 installer attached, Clover is freezing, even if I plug in when the GUI is ready. This time I could obtain the debug.log

Move recovery entry 0 before system 0

This is going on infinitely in debug.log, have to remove the USB and restart the system. 

debug_2020-10-22-18-08-14-6a96d48-failed-acer.log

6 minutes ago, eSaF said:

No no no my friend I still have Clover on quite a few USB drives because I wasn't sure or too confident in the beginning about OC plus I still have a series of old Clover versions on a drive. I am a bit of a Hoarder.:lol:

Was just kidding. Let me know when you'd like to come back to Clover !

23 minutes ago, Jief_Machak said:

@JorgeMax No you're facing the same bug as @kushwavez ! Good, one less.

I think I got the right algorithm this time. @JorgeMax @kushwavez try CloverX64-2020-10-22-18-50-45-6a96d48-dirty-jief.zip

 

It's working, thank your effort very much! Kexts are now loading fine, everything's looking good so far. 

Big Sur Beta 10 Installed system: OK, log: debug_2020-10-22-18-50-45-6a96d48-acer-big-sur10-success.log

Big Sur Beta 10 Installer USB: OK, log: debug_2020-10-22-18-50-45-6a96d48-acer-big-sur10-installer-success.log

Catalina 10.15.7 Installer USB: OK, log: debug_2020-10-22-18-50-45-6a96d48-acer-cata-installer-success.log

Windows 10 : OK

  • Like 4
35 minutes ago, Jief_Machak said:

@JorgeMax No you're facing the same bug as @kushwavez ! Good, one less.

I think I got the right algorithm this time. @JorgeMax @kushwavez try CloverX64-2020-10-22-18-50-45-6a96d48-dirty-jief.zip

 

 

Now it's gone. Perfect startup: 

Spoiler

IMG_0945.thumb.JPG.af03eeeffbbeaa3c5b451a4f37918235.JPG  971938386_CapturadeTela2020-10-22s13_23_17.thumb.png.324702ad98726cb293e567fb386c85b4.png

 

debug.log

 

Dude I just thank you for your effort, and the members for helping with their configurations to find a perfect result

 

Let's see what the next step is

@Jief_Machak

thank you for your effort

this attached is a part of two debug, focalised on kernel patches application useful to AMd cpu to boot

left part is a part of a booting system

right part no

1265233455_ScreenShot2020-10-22at19_20_11.thumb.png.1f24ad2525e5d5a14be6b5f64a2d2900.png

same config.plist with (I hope ) proper matchOS declaration

 

the question is: why it seems to consider only High Sierra and it allows patches shouldn't not be allowed?

these debug is from :

Starting Clover revision: 5125 (master, commit 6a96d4833) on American Megatrends EFI

 

with two different and no properly compiled configs I can boot both OSX I want (High Sierra and BigSur)

If I compile properly matchOS data for OSX no

and why If I boot from Big Sur I see always

OS:10.13.6 before MatchOS : (any values added by me in config)?

8 minutes ago, fabiosun said:

why it seems to consider only High Sierra and it allows patches shouldn't not be allowed?

@fabiosun iCanaro show me the bug. I'll investigate.

@iCanaro Looks like your OpenCorePkg is not up to date. Did you "git fetch --recurse-submodules" and "git pull --recurse-submodules" ?

×
×
  • Create New...