Jump to content
30960 posts in this topic

Recommended Posts

2 hours ago, Jief_Machak said:

This version is the same as previous one + "Unknown" kext folder if version is not recognized (that's not supposed to happen, right ?)

CloverX64-2020-11-12-10-39-28-0bbc1e3-dirty-jief.zip

 


Thanks. @Jief_Machak The "Unknown" kext folder  replace Other folder or it's in addition. 

It's an addition. I wouldn't intentionally make a change like this, that can prevent boot, all of a sudden. (That doesn't mean I never made a change by mistake that prevent boot :hysterical:)

It's not exactly the same as "Other" anyway, because Unknown is ignored when version is known. Obvious, right ?

 

For "Other" :

When I created the possibility of having a folder "10" (which was before BS), I thought it would replaced "Other". It didn't see it coming the version 11 instead of 10.16.

The plan is to add a folder "All", and keep the "Other" folder for some time with a warning at boot like "Please rename Other to All".

  • Like 2
  • Thanks 1
14 minutes ago, Jief_Machak said:

Without "Other" folder ?

 

OK done more testing by completely emptying the other folder 
calling the bigsur 11 folder starts correctly; if instead we nod it 11.x what doing bigsur doesn't start
 

bigsur = 11 OK

bigsur = 11.x NOK

matchOS works OK

 

debug.log

  • Like 1

notes to developers:

 

on AMD systems, but not only that, I also think of notebooks with I2C, for some kext it is very important that a certain loading order is defined.
For example, on my AMD X570 AMDRyzenCPUPowerManagement.kext must be loaded before SMCAMDProcessor.kext; At the same time, AMDRyzenCPUPowerManagement.kext must be loaded after VirtualSMC.kext; but VirtualSMC is also a LILU plugin, so LILU must be at the top of the load order.
All this serves for the perfect functioning and integration of the various kexts
now on clover the only distinction is that the kexts in the other folder will be loaded as a priority over kexts in folders 10.xx 11
IMHO would be useful to have the ability to define load order for kexts, if not for everyone, but for some

  • Like 2
2 hours ago, Jief_Machak said:

 

It's not exactly the same as "Other" anyway, because Unknown is ignored when version is known. Obvious, right ?

 

Mmm-m-m... or vice versa? Unknown is used when the version is unknown?

  • Like 2
10 minutes ago, chris1111 said:

@iCanaro Sorry I forgot the OS Clover :angel_not: Can you tell me if it's correct

os_clover.icns.zip

 

I would have liked to tell you that everything is OK, but unfortunately clover icon is not loaded (must it be inserted in the icons folder, correct?!)

since you are so kind and you are working on it, I would have a request, and that is the arrow of the selector, instead of being white, that you notice little, maybe do it of other color, red, yellow, green ... something you notice well with black background and other white writing
 

Spoiler

screenshot0.thumb.png.86032078feb1ef7981d8abd12cc5d513.png

 

  • Like 2
2 hours ago, iCanaro said:

 

OK done more testing by completely emptying the other folder 
calling the bigsur 11 folder starts correctly; if instead we nod it 11.x what doing bigsur doesn't start
 

bigsur = 11 OK

bigsur = 11.x NOK

matchOS works OK

 

debug.log

The kext folder CANNOT be named "11.x". "11.x" is a syntax for MatchOS.

 

kext folder names can be "11", "11.0", "11.0.1". You can also have "11_install", "11_normal", "11_recovery", "11.0_install", "11.0_normal", "11.0_recovery",  "11.0.1_install", "11.0.1_normal", "11.0.1_recovery".

  • Like 2
  • Thanks 1
  • Sad 1
1 hour ago, mifjpn said:

Thank you Jief.
As you can see in the log below, on the second boot of the installer or update

No-Ver-BigSur11.0.1.log

47: 497 0:042 UniOSVersion ==
47: 538 0:041 UniShortOSVersion ==
Will occur.

I will try it with BigSur RC2.

You're still using 5125. Version detection was improved. Use my latest efi CloverX64-2020-11-12-15-13-22-0bbc1e3-dirty-jief.zip

Look in your log, you should find a line starting with "GetOSVersion: "

If the version number is incorrect, send me a zip of the preboot partition of the installer.

  • Like 1
13 minutes ago, Jief_Machak said:

Yes ! Form a rigorous logic point of view, it's "Unknown is used only when the version is unknown"

Was I wrong in my double-negation ?:rolleyes::rofl:

Double negotiation causes muddle :rofl:

  • Like 1
13 minutes ago, iCanaro said:

 

I would have liked to tell you that everything is OK, but unfortunately clover icon is not loaded (must it be inserted in the icons folder, correct?!)

since you are so kind and you are working on it, I would have a request, and that is the arrow of the selector, instead of being white, that you notice little, maybe do it of other color, red, yellow, green ... something you notice well with black background and other white writing
 

  Reveal hidden contents

screenshot0.thumb.png.86032078feb1ef7981d8abd12cc5d513.png

 

Thank to you ;)

I put the green selector and you can try to change os clover because I do not understand why it does not load in volume

On my systems I don't have this icon which tries to load

Archive.zip

  • Thanks 1

I had to wipe my hard drives now I cannot install macOS on my X570. Tried RC1 and RC2 with 5126. No config changes but after second reboot I get a very quick text scroll then reboot. Using install macOS via preboot. Not sure if it’s a config error or kernel patches but I’ll keep trying I guess. If anyone on X570 can post a working install config for RC1 or 2 I would appreciate it. 

11 minutes ago, chris1111 said:

Thank to you ;)

I put the green selector and you can try to change os clover because I do not understand why it does not load in volume

On my systems I don't have this icon which tries to load

Archive.zip

 

thank you, the selector is now perfect. 
Instead Clover icon does not want to know to be loaded, I reset the NVRAM, reloaded the theme, but nothing to do.
If you have other things to do, I don't want to keep you busy for a no problem... it's not that every time you start in GUI you press F3 to see the EFI :D 

Spoiler

screenshot1.thumb.png.965ef71352c92ec365a344969c46a89d.png


 

  • Like 1
1 minute ago, iCanaro said:

 

thank you, the selector is now perfect. 
Instead Clover icon does not want to know to be loaded, I reset the NVRAM, reloaded the theme, but nothing to do.
If you have other things to do, I don't want to keep you busy for a no problem... it's not that every time you start in GUI you press F3 to see the EFI :D 

  Reveal hidden contents

screenshot1.thumb.png.965ef71352c92ec365a344969c46a89d.png


 

Thank you verry much I will try to find the solution :)

  • Thanks 1
16 minutes ago, SavageAUS said:

I had to wipe my hard drives now I cannot install macOS on my X570. Tried RC1 and RC2 with 5126. No config changes but after second reboot I get a very quick text scroll then reboot. Using install macOS via preboot. Not sure if it’s a config error or kernel patches but I’ll keep trying I guess. If anyone on X570 can post a working install config for RC1 or 2 I would appreciate it. 

 

attach your config that i try to modify it specific to big sur installation

  • Like 1
22 minutes ago, SavageAUS said:

I had to wipe my hard drives now I cannot install macOS on my X570. Tried RC1 and RC2 with 5126. No config changes but after second reboot I get a very quick text scroll then reboot. Using install macOS via preboot. Not sure if it’s a config error or kernel patches but I’ll keep trying I guess. If anyone on X570 can post a working install config for RC1 or 2 I would appreciate it. 

Use my latest efi, there is a better OS version detection.

At Clover GUI, press space when on the installer entry to check the detected version. Do that check at each reboot.

CloverX64-2020-11-12-15-57-18-0bbc1e3-dirty-jief.zip

If version is not detected, send me a zip of the preboot partition, from the installer container if it's an installer entry, or from the container you installed into.

  • Like 1
20 minutes ago, SavageAUS said:

This is the one i was using before prior to RC releases.

config.plist

test config-Install_BS-SavageAUS.plist

 

if you still have problems move other lilu weg virtualsmc/fakesmc to the other folder
 

1 hour ago, iCanaro said:

notes to developers:

 

on AMD systems, but not only that, I also think of notebooks with I2C, for some kext it is very important that a certain loading order is defined.
For example, on my AMD X570 AMDRyzenCPUPowerManagement.kext must be loaded before SMCAMDProcessor.kext; At the same time, AMDRyzenCPUPowerManagement.kext must be loaded after VirtualSMC.kext; but VirtualSMC is also a LILU plugin, so LILU must be at the top of the load order.
All this serves for the perfect functioning and integration of the various kexts
now on clover the only distinction is that the kexts in the other folder will be loaded as a priority over kexts in folders 10.xx 11
IMHO would be useful to have the ability to define load order for kexts, if not for everyone, but for some

When can put this kext in the hard coded order list.

(please everybody, don't start with "it's bad to hard code, etc.").

  • Like 1
9 minutes ago, iCanaro said:

test config-Install_BS-SavageAUS.plist

 

if you still have problems move other lilu weg virtualsmc/fakesmc to the other folder
 

Thanks I’ll give that a try when I can and report back. 
Updating my laptop now to RC2 and all going well so far. @Jief_Machak pressing space bar detected version as 11.0.1 on intel laptop on 2nd reboot. 

2 hours ago, iCanaro said:

notes to developers:

 

on AMD systems, but not only that, I also think of notebooks with I2C, for some kext it is very important that a certain loading order is defined.
For example, on my AMD X570 AMDRyzenCPUPowerManagement.kext must be loaded before SMCAMDProcessor.kext; At the same time, AMDRyzenCPUPowerManagement.kext must be loaded after VirtualSMC.kext; but VirtualSMC is also a LILU plugin, so LILU must be at the top of the load order.
All this serves for the perfect functioning and integration of the various kexts
now on clover the only distinction is that the kexts in the other folder will be loaded as a priority over kexts in folders 10.xx 11
IMHO would be useful to have the ability to define load order for kexts, if not for everyone, but for some

Ok, I've added AMDRyzenCPUPowerManagement.kext and SMCAMDProcessor.kext in the list.

 

AMDRyzenCPUPowerManagement will be loaded after VirtualSMC, and SMCAMDProcessor after AMDRyzenCPUPowerManagement.

 

CloverX64-2020-11-12-16-50-51-0bbc1e3-dirty-jief.zip

  • Like 2
×
×
  • Create New...