Clover General discussion

[iCanaro]

21 minutes ago, Jief_Machak said:

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

 

it seems to be all OK, big sur has started correctly and AMDPower Gadget reports cpu temperature

 

debug.log

PS: I was wondering, if it was possible to clear log debugging from the Clover GUI, for example with a combination of CTRL + F11o other keys

[PG7]

Good Morning

 

here with CloverX64-2020-11-12-10-39-28-0bbc1e3-dirty-jief.efi and with the folder for kext called 11 it works perfect with BigSur RC2

 

 

debug.log

preboot.log

[MICKHAEL]

Hello @Jief_Machak,  i see that you are working on kext loading order
i have a problem and im suspecting this order as culpit
the problem is that not all the time i have a working power management... and also, interesting, after reset NVRAM, power management are working till first reboot...
what could be?
im ussing CPUFriend in combination with SSDT-PLUG to achieve it
Thanks

[Jief_Machak]

31 minutes ago, MICKHAEL said:

Hello @Jief_Machak,  i see that you are working on kext loading order
i have a problem and im suspecting this order as culpit
the problem is that not all the time i have a working power management... and also, interesting, after reset NVRAM, power management are working till first reboot...
what could be?
im ussing CPUFriend in combination with SSDT-PLUG to achieve it
Thanks

Yes, we really have to implement properly the kext ordering. I won't have time before January. That's why we hard code so far.

CPUFriend needs lilu. Lilu is hard coded to be the first to load. So I'd say that shouldn't be the problem.

I don't know what could cause that. Don't know either if NVRAM could have an effect or if it's just coincidence...

Sorry.

 

@everyone : have a look in plist of your kext :

	<key>OSBundleLibraries</key>
	<dict>
		<key>as.vit9696.Lilu</key>
		<string>1.2.0</string>
		<key>com.apple.iokit.IOACPIFamily</key>
		<string>1.0.0d1</string>
		<key>com.apple.kpi.bsd</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.dsep</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.iokit</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.libkern</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.mach</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.unsupported</key>
		<string>12.0.0</string>
	</dict>

ignore the com.apple.*.

If there is a dependence on an other kext, tell me. We'll hard coding it. NOTE : if it's lilu, like in this example, no need to report. As I said, Lilu is first in all case.

 

 

[iCanaro]

4 minutes ago, Jief_Machak said:

Yes, we really have to implement properly the kext ordering. I won't have time before January. That's why we hard code so far.

 

there is no problem, so far you have done a great job, thank you 

[Common_Sense]

17 minutes ago, Jief_Machak said:

Yes, we really have to implement properly the kext ordering. I won't have time before January. That's why we hard code so far.

CPUFriend needs lilu. Lilu is hard coded to be the first to load. So I'd say that shouldn't be the problem.

I don't know what could cause that. Don't know either if NVRAM could have an effect or if it's just coincidence...

Sorry.

 

@everyone : have a look in plist of your kext :

	<key>OSBundleLibraries</key>
	<dict>
		<key>as.vit9696.Lilu</key>
		<string>1.2.0</string>
		<key>com.apple.iokit.IOACPIFamily</key>
		<string>1.0.0d1</string>
		<key>com.apple.kpi.bsd</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.dsep</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.iokit</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.libkern</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.mach</key>
		<string>12.0.0</string>
		<key>com.apple.kpi.unsupported</key>
		<string>12.0.0</string>
	</dict>

ignore the com.apple.*.

If there is a dependence on an other kext, tell me. We'll hard coding it. NOTE : if it's lilu, like in this example, no need to report. As I said, Lilu is first in all case.

 

 

 

I thought kext order loading could be done in Clover already? Simply by using directories inside kexts. Please refer to screenshot in attachment. Inside Lilu.kext/Contents/PlugIns the Lilu kexts are located and because of that they always load after Lilu.kext, correct? The order between them is of course undefined but doesn't matter I think. Of course PlugIns directories can be created inside any kexts and therefore the order of kext loading can be controlled even further if required, by nesting directories.

 

Clover bdmesg output shows the following:

91:549  0:001  AddKextsInArray from Other

91:549  0:000  ->Extra kext: Other\AppleALC.kext (v.1.5.5)

91:549  0:000  ->Extra kext: Other\IntelMausiEthernet.kext (v.2.5.3d1)

91:549  0:000  ->Extra kext: Other\Lilu.kext (v.1.5.0)

91:549  0:000      |-- PlugIn kext: Other\Lilu.kext\Contents\PlugIns\HibernationFixup.kext (v.1.3.8)

91:549  0:000      |-- PlugIn kext: Other\Lilu.kext\Contents\PlugIns\WhateverGreen.kext (v.1.4.5)

91:549  0:000      |-- PlugIn kext: Other\Lilu.kext\Contents\PlugIns\USBInjectAll.kext (v.0.7.5)

91:549  0:000      |-- PlugIn kext: Other\Lilu.kext\Contents\PlugIns\CPUFriend.kext (v.1.2.2)

91:549  0:000      |-- PlugIn kext: Other\Lilu.kext\Contents\PlugIns\EFICheckDisabler.kext (v.0.5)

91:549  0:000  ->Extra kext: Other\VirtualSMC.kext (v.1.1.9)

91:549  0:000      |-- PlugIn kext: Other\VirtualSMC.kext\Contents\PlugIns\SMCSuperIO.kext (v.1.1.9)

91:549  0:000      |-- PlugIn kext: Other\VirtualSMC.kext\Contents\PlugIns\SMCProcessor.kext (v.1.1.9)

 

 

 

 

 

[chris1111]

@iCanaro Please let me known if this work  Thank you

Archive.zip

[chris1111]

@iCanaro If not work try this icon  Thank you

 

 

Archive.zip

[iCanaro]

30 minutes ago, chris1111 said:

@iCanaro Please let me known if this work  Thank you

Archive.zip

 

22 minutes ago, chris1111 said:

@iCanaro If not work try this icon  Thank you

 

 

Archive.zip

 

am I by any chance becoming the human case of november?! 
still no EFI icon with both archives...

now I want to try some other hacks for confirmation as well and not just on X570

[chris1111]

3 minutes ago, iCanaro said:

 

 

am I by any chance becoming the human case of november?! 
still no EFI icon with both archives...

now I want to try some other hacks for confirmation as well and not just on X570

With Neon Theme on X570 do you have EFI ? 

 

Post picture screenshot of neon theme if you have thanks

Edited November 12, 2020 by chris1111

[iCanaro]

37 minutes ago, chris1111 said:

With Neon Theme on X570 do you have EFI ? 

 

Post picture screenshot of neon theme if you have thanks

I tried on the Z370 and Z68 but no EFI icon and this one with both Neon and OCintegration theme

 

Spoiler

 

[chris1111]

12 minutes ago, iCanaro said:

I tried on the Z370 and Z68 but no EFI icon and this one with both Neon and OCintegration theme

 

  Hide contents

 

Thanks that's confirm this is not a theme issue its a clover issue I think but not sure? 

@iCanaro This attaching icon solved EFI 

 

 

os_unknown.icns.zip

Edited November 12, 2020 by chris1111
attaching icon solved EFI

[iCanaro]

12 minutes ago, chris1111 said:

Thanks that's confirm this is not a theme issue its a clover issue I think but not sure? 

@iCanaro This attaching icon solved EFI 

 

 

os_unknown.icns.zip

 

oh you'd say you've centered the problem  

Fixed

Spoiler

 

[chris1111]

Just now, iCanaro said:

 

oh you'd say you've centered the problem  

Fixed

  Hide contents

 

Thank you verry much for your time and test  really appreciate 

[PG7]

 

here it was also good !!!

merci Chris

Spoiler

[iCanaro]

there's such a long line of changes, I'll be a rookie, but so far I hadn't seen it 

 

 

 

[iCanaro]

Clover went through a difficult exam, I updated AMD X570 without any kexts in the other folder and with the default config, with which I can start high sierra, mojave, catalina and big sur. This means, it means that on the first restart you didn't get lost or messed up with the kernel patches, everything went as it should, successful update 

 

it seems to me a really good job of the developers, 10 minutes of applause 

 

 

 

CLOVERX64-5126-7f1b87c92.efi.zip

Edited November 13, 2020 by iCanaro

[cyrhex]

@iCanaro

would you mind to share the clovex64.efi

[Vinicius P. Miranda]

Guys, is there any way to test NVRAM or repair the permissions and give it read and write permission again? I went to use Open Core 0.6.3 and I used the OC's NVRAM Reset option, it happened to break my bios. I can't find any more UEFI drives on my hard drives. I have Clover on an SSD and on an HD, the bios can't find them to boot and the Clover screen appears. I have already reset the bios, I have already rewritten it (Ez Flash) but I cannot find the UEFI units to boot. I only find the UEFI unit of the flash drive when I connect it to a USB port.
I entered Catalina using the EFI of the flash drive, installed Clover on the SSD and HD by .pkg, but there is still no boot option for the disks in my bios.

I believe the problem is NVRAM because I used the Open Core 0.6.3 Reset NVRAM option. Did this cause my bios to lose access to NVRAM? Is there any way to repair it? I used the F11 on the Clover screen of the flash drive, but nothing worked.

I can't keep my bios without the boot option.

[iCanaro]

6 minutes ago, cyrhex said:

would you mind to share the clovex64.efi

I updated my post on

[iCanaro]

3 minutes ago, Vinicius P. Miranda said:

Guys, is there any way to test NVRAM or repair the permissions and give it read and write permission again? I went to use Open Core 0.6.3 and I used the OC's NVRAM Reset option, it happened to break my bios. I can't find any more UEFI drives on my hard drives. I have Clover on an SSD and on an HD, the bios can't find them to boot and the Clover screen appears. I have already reset the bios, I have already rewritten it (Ez Flash) but I cannot find the UEFI units to boot. I only find the UEFI unit of the flash drive when I connect it to a USB port.
I entered Catalina using the EFI of the flash drive, installed Clover on the SSD and HD by .pkg, but there is still no boot option for the disks in my bios.

I believe the problem is NVRAM because I used the Open Core 0.6.3 Reset NVRAM option. Did this cause my bios to lose access to NVRAM? Is there any way to repair it? I used the F11 on the Clover screen of the flash drive, but nothing worked.

I can't keep my bios without the boot option.

 

you have a fragile BIOS, but remedying, when you know the steps it is very simple.

1- more complex option, you start the EFI Shell and manually add entries that the BIOS cannot integrate

2- very easy option, the one I use in particular on a hack, which you lose the entries to make it bau... you operate from an livepe or windows the tool is bootice

[chris1111]

Latest Clover work good on Final release BS  Thanks to all Devs and tester

 

Edited November 13, 2020 by chris1111

[LockDown]

23 hours ago, ellaosx said:

@Jief_Machak mentioned that we need to unhide the preboot in config.plist for the BS.

But since im not testing BS and still at High Sierra, did this made it to r5126 or no? Cause the preboot is showing in r5126

 

20 hours ago, Jief_Machak said:

Tried here, and the preboot doesn't show IF the main partition is accessible. debug.log + screenshot ?

One of the pic inside the zip shows the preboot of highsierra is detected as 11.0? I dont have that folder and BS installed.

ellaosx.zip

Edited November 13, 2020 by ellaosx

[iCanaro]

@Jief_Machak if you have more Clover releases in the pipeline to test, I'll wait to update the other hacks, let me know, thank you  

[Matgen84]

3 minutes ago, iCanaro said:

@Jief_Machak if you have more Clover releases in the pipeline to test, I'll wait to update the other hacks, let me know, thank you  

@Jief_Machak Same here for Z390. Let me know. Thank you too