Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

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

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

Link to comment
Share on other sites

@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)?

Link to comment
Share on other sites

1 minute ago, Jief_Machak said:

No, I was talking about the zip of the content of your Preboot volume. I thought you did it and sent it ? Am I wrong ?

If you didn't, could you do it ?

I sent the link hours ago :D see PM

https://mega.nz/file/Wqpm3YwL#2Dbo6VkANbO6LjH06a2W4UCc79PFdLWAIZqAukkcyBo

PS: on the X570 AMD I reinstalled big sur beta 10 with OC, now everything has been fixed in the Clover GUI.
Considering that I happened to have this strange problem after I tested on high sierra, I think either of some bug or that kernels to patch do some harm

Link to comment
Share on other sites

I know. Too many pages of this forum. I tried to go back but couldn't find it. Oh, it was a PM ? Couldn't find that either...

A forum is probably not the best tool to do multitasking bug resolution...

I don't know why we don't use the github issues mechanism. Just habit. I'll think about that...

 

Ok got it.

It may not be a Clover bug. In your preboot volume, folder "47AB2C83-D8B5-4E45-A896-9002D2B2C6D2/System/Library/CoreServices/SystemVersion.plist", you can see yourself that there is this

	<key>ProductVersion</key>
	<string>10.13.6</string>

So of course, Clover thinks it's HS.

Can you try to rename the folder "47AB2C83-D8B5-4E45-A896-9002D2B2C6D2". Something like "47AB2C83-D8B5-4E45-A896-9002D2B2C6D2.old" and redo the diskutil apfs updatepreboot?

Then check the file "47AB2C83-D8B5-4E45-A896-9002D2B2C6D2/System/Library/CoreServices/SystemVersion.plist".

 

 

  • Thanks 1
Link to comment
Share on other sites

18 minutes ago, Jief_Machak said:

@fabiosun You seem to have the same problem. Could you send me the content of your preboot apfs volume ?

I have no problem I think as icanaro has said in his amd rig

i can boot fine and I do not loose anything independently which high Sierra or Big Sur if I use two different config to boot them

problem for me is that if I use correct matchos i see always getos as highsierra also if I boot with Big Sur and it seems always the same patches are applied in both different OS X (10.13 and 11 I mean)

Link to comment
Share on other sites

Just now, fabiosun said:

if I use correct matchos i see always getos as highsierra also if I boot with Big Sur and it seems always the same patches are applied in both different OS X (10.13 and 11 I mean)

Seems to exactly be the problem that iCanaro has.

I got iCanaro preboot. I'll debug with him and let you know.

Link to comment
Share on other sites

9 minutes ago, Jief_Machak said:

Seems to exactly be the problem that iCanaro has.

I got iCanaro preboot. I'll debug with him and let you know.

I am referring that he looses Big Sur functionality if he tries to boot in high Sierra 

here this not happens

here a config with matcOS tab used boots fine with high sierra

without boots fine in Big Sur 

i will wait your debug with him:angel:

ps

thank you 

Edited by Guest
Link to comment
Share on other sites

1 hour ago, Jief_Machak said:

I know. Too many pages of this forum. I tried to go back but couldn't find it. Oh, it was a PM ? Couldn't find that either...

A forum is probably not the best tool to do multitasking bug resolution...

I don't know why we don't use the github issues mechanism. Just habit. I'll think about that...

 

Ok got it.

It may not be a Clover bug. In your preboot volume, folder "47AB2C83-D8B5-4E45-A896-9002D2B2C6D2/System/Library/CoreServices/SystemVersion.plist", you can see yourself that there is this


	<key>ProductVersion</key>
	<string>10.13.6</string>

So of course, Clover thinks it's HS.

Can you try to rename the folder "47AB2C83-D8B5-4E45-A896-9002D2B2C6D2". Something like "47AB2C83-D8B5-4E45-A896-9002D2B2C6D2.old" and redo the diskutil apfs updatepreboot?

Then check the file "47AB2C83-D8B5-4E45-A896-9002D2B2C6D2/System/Library/CoreServices/SystemVersion.plist".

 

 

 

thank you for your valuable information, I understood what happened, and possibly how to fix it, without having to reinstall BS beta 10 [I backed up the entire preboot]
what I just can't understand, is how it could have happened that it was possible to change the macOS in the systemversion.plist

Link to comment
Share on other sites

5 minutes ago, Jief_Machak said:

Did you try that ? Did it restore the whole "47AB2C83-D8B5-4E45-A896-9002D2B2C6D2" folder ?

I restored, a little coarsely, by reinstalling bigsur beta 10, so it repaired 47AB2C83-D8B5-4E45-A896-9002D2B2C6D2
now the systemversion.plist reports the correct values related to the bigsur version

Link to comment
Share on other sites

2 minutes ago, iCanaro said:

I restored, a little coarsely, by reinstalling bigsur beta 10, so it repaired 47AB2C83-D8B5-4E45-A896-9002D2B2C6D2
now the systemversion.plist reports the correct values related to the bigsur version

Wouldn't have been simpler to try "diskutil apfs updatepreboot" first ? :wink_anim:

Link to comment
Share on other sites

7 minutes ago, Jief_Machak said:

Wouldn't have been simpler to try "diskutil apfs updatepreboot" first ?

of course yes, but when I read your answer, the "damage" had already been done :P  but I saved all the commands, so when I try to start high sierra, if you generate the same problem, I should have simpler and more effective weapons to solve :lol:

Link to comment
Share on other sites

2 hours ago, Jief_Machak said:

this build on the X570 AMD starts catalina and BS, but does not start mojave

mojave_NOK_debug.log

 

 

this clover commit starts mojave catalina and bs

mojave_5125 (master, commit 18038055a)OK_debug.log

 

used the same configuration, changed only Clover build

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...