Clover General discussion

[matxpa]

35 minutes ago, Matgen84 said:

 

I only report that @Slice has recommended, several time, to use FakeSMC with Clover. This is a solid argument 😅
That's all folks 

Saying that Slice recommends FakeSMC with Clover is a strong enough argument to demonstrate that "VirtualSMC is no longer compatible with Clover for a long time".

You have a rather peculiar conception of logic.

[Matgen84]

34 minutes ago, matxpa said:

Saying that Slice recommends FakeSMC with Clover is a strong enough argument to demonstrate that "VirtualSMC is no longer compatible with Clover for a long time".

You have a rather peculiar conception of logic.

 

Like VirtualSMC, FakeSMC is a System Management Controller emulator. It operates similar to VirtualSMC but it uses plugins to provide additional functionality to macOS. It  should  be used when VirtualSMC is found to be incompatible with some hardware. This is enough logical 😅

 

Personaly, I use FakeSMC with Clover and VirtualSMC with Opencore: this is my logical choice. 😋

 

Have a nice day, Bro.

[matxpa]

8 minutes ago, Matgen84 said:

 

Like VirtualSMC, FakeSMC is a System Management Controller emulator. It operates similar to VirtualSMC but it uses plugins to provide additional functionality to macOS. It  should  be used when VirtualSMC is found to be incompatible with some hardware. This is enough logical 😅

 

Personaly, I use FakeSMC with Clover and VirtualSMC with Opencore: this is my logical choice. 😋

 

Have a nice day, Bro.

 "VirtualSMC is found to be incompatible with some hardware" means "VirtualSMC is no longer compatible with Clover for a long time".

So for your Clover is (for a long time) a Hard no more a Soft.

[Alpha22]

I confirm that VirtualSMC.kext works with macOS Sequoia Beta 5 

 

Spoiler

 

[MaLd0n]

1 hour ago, Alpha22 said:

I confirm that VirtualSMC.kext works with macOS Sequoia Beta 5 

Same here. With beta 5 work again.

[matxpa]

And I can confirm what Alpha22, MaLd0n and so many others confirm too that : VirtualSMC works on Sequoia Beta5 and even with Clover r5160 (5333dff)

 

 

 

 

 

 

Regards

Edited August 10, 2024 by matxpa

[Slice]

To remind

 

[naiclub]

On 8/13/2024 at 2:40 AM, Slice said:

To remind

 

Hello, Clover doesn't show the model name of the cpu. What should I fix? As for OC, it shows the model name beautifully. Thank you very

[Slice]

Don't wonder if you use RestrictEvents.kexts. Just read documentation

https://github.com/acidanthera/RestrictEvents

OC left boot-args in NVRAM.

[Max.1974]

7 horas atrás, Slice disse:

Não se pergunte se você usa RestrictEvents.kexts. Basta ler a documentação

https://github.com/acidanthera/RestrictEvents

OC deixou os boot-args na NVRAM.

Hi @Fatia is there some way to fix this with Clover ? Thanks! 

[deeveedee]

That's a cool trick.  How do I create an alias?

[LockDown]

Alias of?

[deeveedee]

[naiclub]

12 hours ago, Max.1974 said:

Hi @Fatia is there some way to fix this with Clover ? Thanks! 

Clover, I think developers should find a way to do this. Otherwise, it will make everyone bored.

[deeveedee]

@naiclub Slice has provided the solution and I showed you how to implement it. The RestrictEvents instructions I gave you should work with CLOVER if you move the NVRAM properties to boot-args. Read my instructions again in the OpenCore discussion thread and be patient with yourself. See if you can figure this out yourself with the help that has already been provided to you. Be persistent and don't give up easily. You can do it.

[naiclub]

24 minutes ago, deeveedee said:

@naiclub Slice has provided the solution and I showed you how to implement it. The RestrictEvents instructions I gave you should work with CLOVER if you move the NVRAM properties to boot-args. Read my instructions again in the OpenCore discussion thread and be patient with yourself. See if you can figure this out yourself with the help that has already been provided to you. Be persistent and don't give up easily. You can do it.

Thank you very much, Grandma. I have tried many ways but it did not work as I expected. I do not know how to proceed. If I continue to be stubborn, I may not be able to boot again (I tried to put the values in OC into Clover, it did not work).

[deeveedee]

@naiclub I know you can do this. Always test your EFI changes with  a bootable USB thumbdrive so you don't risk being unable to boot. Don't give up too easily. The harder you try and the more times you fail before succeeding, the more you'll learn.

 

If you let others do it for you, it will be boring.

Edited August 16, 2024 by deeveedee

[Alpha22]

@naiclub post your config.plist deleting the serials from the smbios

[Slice]

15 hours ago, Max.1974 said:

Hi @Fatia is there some way to fix this with Clover ? Thanks! 

        <key>Boot</key>
        <dict>
            <key>Arguments</key>
            <string>revpatch=auto</string>

No?

[naiclub]

1 hour ago, Alpha22 said:

@naiclub post your config.plist deleting the serials from the smbios

I added PlatforInfo=ProcessorType=3841 by copying from OC, but it still doesn't work. The cause might be that the Clover developer didn't put this value in, or maybe I'm just guessing. I put this value in OC, it will show the name as we set. If I put 0, it will show an unknown name. But with Clover, putting this value has no meaning. It doesn't respond.

Spoiler

 

config.plist.zip

Edited August 16, 2024 by naiclub

[Alpha22]

@naiclub replace config.plist, restart Reset NVRAM use f11 

config.plist.zip

[naiclub]

27 minutes ago, Slice said:

        <key>Boot</key>
        <dict>
            <key>Arguments</key>
            <string>revpatch=auto</string>

No?

Spoiler

I tried to enter the values as you suggested, but it didn't respond.

[Max.1974]

@naiclub try using Hackintool to convert Decimal 3841 to Hex F01 and insert in Clover  CPU Type menu (im using Clover Configurator)

 

 

Spoiler

 

 

Spoiler

 

 

Hi @Slice thx i will try with this fix! 

 

 

Spoiler

 

[deeveedee]

As has been discussed before, revpatch=auto (which includes revpatch=cpuname) is part of the solution.  Read this and this.

[Max.1974]

1 minute ago, deeveedee said:

As has been discussed before, revpatch=auto (which includes revpatch=cpuname) is part of the solution.  Read this and this.

 

Hi @deeveedee 

I hope you are well. When I use Clover, and disable the e-cores of my i9-13900k processor in the Bios, it recognizes it without the need for any boot-arg. When I try to use it in Clover and enter the parameters as in the screenshots above, it only works if I boot it once, with Opencore, in this case with e-cores activated, that is, the efficiency cores. I don't mind much, but if we can learn. With Opencore, I enter all the parameters you mentioned (because you only use them in Opecore, right?) and it recognizes it. 

Interestingly, if I boot with Opencore, it registers in Nvram and even if I return with Clover, what was injected remains in Nvram, until we do a ResetNvram the name remains. But because some people have problems with this, we ask if there is a solution. For my part, just boot with Opencore and keep the e-cores treds activated in Bios. Hugs!