Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

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

Jief_Machak
Jief_Machak
Posted
Posted

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
Guest
Guest
Posted
Posted
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)

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

Guest
Guest
Posted
Posted (edited)
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
Jief_Machak
Jief_Machak
Posted
Posted
Just now, iCanaro said:

fixed the problem of compiling clover i deleted the folder and ran again 

 

Git clone --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git

Then

./buildme 

Which is not a correct version, as I haven't committed some bug fix yet.

  • Sad 1
iCanaro
iCanaro
Posted
Posted
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

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

Jief_Machak
Jief_Machak
Posted
Posted
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:

iCanaro
iCanaro
Posted
Posted
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:

iCanaro
iCanaro
Posted
Posted
2 hours ago, Jief_Machak said:

In the meantime use this : CloverX64-2020-10-22-21-08-09-6a96d48-dirty-jief.zip

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

I haven’t tried using any of the updated Clovers on my AMD rig yet so my config has no matchos in it and it works fine <- I’ll get around to updating soon but in the meantime I wanted to ask if I need to do anything with mmiowhitelist? If everything is working (except sleep - yes I’ve mapped USB ports, no I have not checked wake reason yet)

Guest
Guest
Posted
Posted (edited)

@SavageAUS

to say it works fine does not help developer because it is working fine in some situations (single system) and some parameters seem not to work in a multi OSX configuration as ie opencore does
 

Also Kext to patch needs some adjustment because it applies some patching also when you do not need of it (see aquantia kext to patch if you use)


@Jief_Machak

 

if could be useful this is a part of a working opencore debug.log one booting with BigSur the other with HighSierraSame config, same disks configuration.
Disk configuration is also the same I use in clover testing, the only difference is I am booting from an USB pen when I use Clover

Schermata 2020-10-23 alle 8.09.51 AM.png

Edited by Guest
config--->debug.log
Jief_Machak
Jief_Machak
Posted
Posted
7 hours ago, iCanaro 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

The logs are the same ! Few messages more here and then but same.

Are you sure you don't have random non-start ?

Jief_Machak
Jief_Machak
Posted
Posted
5 minutes ago, fabiosun said:

it works fine does not help developer

That's ok. It's sometimes encouraging to know that it's working for someone ! In that sense, it helps.

 

6 minutes ago, fabiosun said:

if could be useful this is a part of a working opencore config one booting with BigSur the other with HighSierraSame config, same disks configuration.
Disk configuration is also the same I use in clover testing, the only difference is I am booting from an USB pen when I use Clover

Schermata 2020-10-23 alle 8.09.51 AM.png

I'm really not sure what you are showing here.

I don't know what your are calling "Disk configuration". Do you mean the same Clover folder ?

I'm not sure either it's OC log or Clover log.

8 minutes ago, fabiosun said:

seem not to work in a multi OSX configuration

If something is not working, we'll fix it. But you have to say what.

 

9 minutes ago, fabiosun said:

Kext to patch needs some adjustment

Hum, yes, ok. Which one ?

 

Your tests and reports are welcomed. But you have to be way more precise...

Jief_Machak
Jief_Machak
Posted
Posted

@iCanaro If you think you don't have random non-start, could try commits taken from here : https://github.com/jief666/CloverCommits

Start with "C-20201021172059-1803805.efi", just to make sure that the problem doesn't come from my own compilation.

If this one works, try the more recent ones.

  • Like 2
Guest
Guest
Posted
Posted (edited)

@Jief_Machak

as I wrote it is a debug log of opencore

one booting in high sierra OSX, the other one booting in Big Sur

In one of this you see an ifgetOS..but I do not why and if it is useful to address then the use or not of the proper kernel patches AMD users need to boot properly

These patches are different from each OSX version

 

about Disks configuration

disk A is dedicated to big Sur

Disk B is dedicated to High Sierra

Disk B contain an EFI with Opencore boot loader (used to boot both systems)

I can say that with the same config I can boot all system available from high Sierra to latest Big Sur beta

 

I use an USB pen with Clover to boot the same disk configurations above

 

About Kext to patch

I, and other AMD users have to use a patch for aquantia 10G ethernet card to have it working on OSX greater than HighSierra

Clover seems to patch always..also High Sierra kext

Opencore instead skips correctly if patching is not needed.

 

I hope is more clear, and to be clear I appreciate your great efforts you are doing as a single devs..but I can't say also if always I read it works it is no good for me..but eiii it is an only an educated opinion..or not?

 

and..for me your Clover 5124 works well in all OSX I have tested using different way to do matchos configuration stuff (and using multiple config.plist file, which is to say it all one of the reason I am following your interesting and great job ;)

 

 

Edited by Guest
typo
Jief_Machak
Jief_Machak
Posted
Posted
2 minutes ago, fabiosun said:

fgetOS

I don't know where that come from and what that mean. OC stuff, I guess.

 

2 minutes ago, fabiosun said:

Clover seems to patch always..also High Sierra kext

Did you configure correctly MatchOS in your config.plist ?

 

4 minutes ago, fabiosun said:

Clover 5124 works well in all OSX

If so, follow this : https://jief-machak.gitbook.io/cloverhelp/ and I will make it work with the latest Clover.

I'll also find why "Clover seems to patch always..also High Sierra kext".

 

7 minutes ago, fabiosun said:

but I can't say also if always I read it works it is no good for me..but eiii it is an only an educated opinion..or not?

I'm not totally sure of what that means. What is no good for you ?

Again, if it was working before, and not anymore , follow this : https://jief-machak.gitbook.io/cloverhelp/ 

  • Like 2
Guest
Guest
Posted
Posted
2 minutes ago, Jief_Machak said:

I'm not totally sure of what that means. What is no good for you ?

Again, if it was working before, and not anymore , follow this : https://jief-machak.gitbook.io/cloverhelp/ 

it is not good to say it works without adding in which situation (OSX used and Clover Commit used) but it is a my personal opinion

 

I can say in my case from 5124 it works well always if I use two different config.plist file without mixing KernelPatches stuff from one os to others

 

It never works with an only one config because every commit I have tested seems to overlap patches which are not useful ie in Big sur

As also a betatester here as said to you (I think SavageAUS but maybe also @Icanaro )

To be more clear (I hope) problem (not for all) but only for AMD cpu users are in kernelPatches detection and utilisation in clover! :)

I will try to understand better how to debug as you requested ;)

 

 

MacKonsti
MacKonsti
Posted
Posted

Good day everyone, can I kindly ask a capable developer (or you @Jief_Machak) for a recompiled final version of Clover pre-OpenCore such as r5122 (release version, official etc.) including the bug fix (reported after r5122 in https://github.com/CloverHackyColor/CloverBootloader/issues/252 ) that fixes the broken patching with target bridge data? @Slice can you help getting a final pre-OC release build for anybody that wants to keep this as a reference version pre-OC please?

 

Just for machines that never intend to get Big Sur and to be able to benefit from the last ever per-OC Clover... I assume the compiled drivers in that r5122 release are not having issues, yes? Just the main EFI

 

I would hope that even the official release would reflect this but a compiled ZIP of the main boot-loader here would suffice :D I wish to update a couple of older hacks that are 6+ years old and that I won't bother even try Big Sur on them...

 

Thank you in advance.

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