Jump to content

Clover General discussion


ErmaC
30,157 posts in this topic

Recommended Posts

@Jief_Machak

I don't know if it is a user problem or Clover related problem

i can't use in Clover the same Opencore kext combination

 

VirtualSMC has inside a plugin folder with inside some kext for radeon and Sensor for CPU and motherboard

image.png.253e5c96065f9245980e4a9d26fe53c3.png

they all are loaded in Clover Bootloader and they conflict with two other kexts  I use:

SMCProcessorAMD.kext

SMCSuperIO.kext

 

In Opencore no problem and system boots fine

In Clover I solved deleting inside VirtualSMC plugin folder SMCProcessor and SMCSuperIO kexts

 

Then it seems that another kext does not work at all in Clover Bootloader:

RestrictEvents.kext

I use Restrictevents to manage memory module misconfiguration and AMD CPU name

 

Is it your work related or it is unrelated to what you can do adjusting and fixing things in Clover Bootloader?

 

Thank you

 

 

 

 

 

 

 

 

Edited by mariosun
  • Like 1
Link to comment
Share on other sites

The author of VirtualSMC, vit9696 said that VirtualSMC is not compatible with Clover. 

For me FakeSMC is better and provide additional features when using Clover.

 

RestrictEvents should work but you have to load also AMFIpass.kext as far as I remember.

  • Like 2
  • Thanks 1
Link to comment
Share on other sites

12 minutes ago, Slice said:

RestrictEvents should work but you have to load also AMFIpass.kext as far as I remember.

Thanks for your answer

no it is not needed. i use also Amfipass.kext for other reasons

 

VirtualSMC works perfectly with Clover Bootloader and using Clover Kext block feature or  if you delete additional plugin he has insite  it boots fine(obviusly if you load also other similar kext)

I will try FakeSMC as you advised...i am trying to have the same kext for both bootloaders and i have found this different beahviour

 

  • Like 1
Link to comment
Share on other sites

21 minutes ago, mariosun said:

Thanks for your answer

no it is not needed. i use also Amfipass.kext for other reasons

 

VirtualSMC works perfectly with Clover Bootloader and using Clover Kext block feature or  if you delete additional plugin he has insite  it boots fine(obviusly if you load also other similar kext)

I will try FakeSMC as you advised...i am trying to have the same kext for both bootloaders and i have found this different beahviour

 

See please

https://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?do=findComment&comment=2789856

 

  • Like 1
Link to comment
Share on other sites

On 1/15/2024 at 6:37 PM, PG7 said:


no, I use exactly the same ones without changing anything
only change is the Clover.efi nothing else!

* up
excuse me, this preboot.log is true that it is another test
I immediately update a new Preboot

 

preboot 5157 No boot.log 57.89 kB · 2 downloads preboot Clover r5156 work.log 60.19 kB · 2 downloads

Spoiler

image.thumb.png.635d306ea6637edc026a0aeec640e4e3.png


Clover r5157 Work

Thanks 

  • Like 1
Link to comment
Share on other sites

6 hours ago, mariosun said:

@Jief_Machak

I don't know if it is a user problem or Clover related problem

i can't use in Clover the same Opencore kext combination

 

VirtualSMC has inside a plugin folder with inside some kext for radeon and Sensor for CPU and motherboard

image.png.253e5c96065f9245980e4a9d26fe53c3.png

they all are loaded in Clover Bootloader and they conflict with two other kexts  I use:

SMCProcessorAMD.kext

SMCSuperIO.kext

 

In Opencore no problem and system boots fine

In Clover I solved deleting inside VirtualSMC plugin folder SMCProcessor and SMCSuperIO kexts

 

Then it seems that another kext does not work at all in Clover Bootloader:

RestrictEvents.kext

I use Restrictevents to manage memory module misconfiguration and AMD CPU name

 

Is it your work related or it is unrelated to what you can do adjusting and fixing things in Clover Bootloader?

 

Thank you

 

 

 

 

 

 

 

 

https://github.com/acidanthera/VirtualSMC/releases/tag/1.3.2

 

if this is the latest version of virtualsmc, no plug in is contained within it

  • Like 2
Link to comment
Share on other sites

Clover bootloader uses also kext inside plugin folder 

and this feature was also useful to WiFi fenvi problem (and we were lucky it uses these kext in the correct order)

Opencore needs to declare exactly any kext user want to use also the ones hidden inside contents/plugin folder and this way it is possible to ‘give’ an order as needed

 

as I said in my previous post I would like to use the same kexts combinations for both bootloaders

it seems not possible but it is not a big problem

 

  • Like 1
Link to comment
Share on other sites

 

oclp Skip compatibility check    

 

        <key>Booter</key>
        <dict>
            <key>MmioWhitelist</key>
            <array/>
            <key>Patch</key>
            <array>
                <dict>
                    <key>Arch</key>
                    <string>x86_64</string>
                    <key>Comment</key>
                    <string>Skip Board ID check</string>
                    <key>Count</key>
                    <integer>0</integer>
                    <key>Enabled</key>
                    <true/>
                    <key>Find</key>
                    <data>AFAAbABhAHQAZgBvAHIAbQBTAHUAcABwAG8AcgB0AC4AcABsAGkAcwB0</data>
                    <key>Identifier</key>
                    <string>Apple</string>
                    <key>Limit</key>
                    <integer>0</integer>
                    <key>Mask</key>
                    <data></data>
                    <key>Replace</key>
                    <data>AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu</data>
                    <key>ReplaceMask</key>
                    <data></data>
                    <key>Skip</key>
                    <integer>0</integer>
                </dict>

 

 

oc>clover?

 

QQ截图20240117151230.png

Link to comment
Share on other sites

10 hours ago, jackacc said:

 

oclp Skip compatibility check    

 

        <key>Booter</key>
        <dict>
            <key>MmioWhitelist</key>
            <array/>
            <key>Patch</key>
            <array>
                <dict>
                    <key>Arch</key>
                    <string>x86_64</string>
                    <key>Comment</key>
                    <string>Skip Board ID check</string>
                    <key>Count</key>
                    <integer>0</integer>
                    <key>Enabled</key>
                    <true/>
                    <key>Find</key>
                    <data>AFAAbABhAHQAZgBvAHIAbQBTAHUAcABwAG8AcgB0AC4AcABsAGkAcwB0</data>
                    <key>Identifier</key>
                    <string>Apple</string>
                    <key>Limit</key>
                    <integer>0</integer>
                    <key>Mask</key>
                    <data></data>
                    <key>Replace</key>
                    <data>AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu</data>
                    <key>ReplaceMask</key>
                    <data></data>
                    <key>Skip</key>
                    <integer>0</integer>
                </dict>

 

 

oc>clover?

 

QQ截图20240117151230.png

Don't skip board-id. It is much better to write it explicitly. This is the Clover way inaccessible by OC.

Screenshot 2024-01-17 at 20.17.29.png

41 minutes ago, mariosun said:

@Slice

CPU type parameter is always working also in latest Clover Bootloader release?

 

Thank you

Why the question? Any doubts?

  • Thanks 2
Link to comment
Share on other sites

25 minutes ago, Slice said:

Why the question? Any doubts?

spent some time with Jief to understand a problem

to solve i have to put this:

image.png.6bdef8c46967b657d0d561198de261c7.png

 

With 0x0F01 i see correct CPU name using RestrictEvents kext

or Intel Xeon without using that kext

 

Is it documented in your WIKI?

Thank you

  • Like 1
Link to comment
Share on other sites

 

12 hours ago, jackacc said:

 

oclp Skip compatibility check    

 

        <key>Booter</key>
        <dict>
            <key>MmioWhitelist</key>
            <array/>
            <key>Patch</key>
            <array>
                <dict>
                    <key>Arch</key>
                    <string>x86_64</string>
                    <key>Comment</key>
                    <string>Skip Board ID check</string>
                    <key>Count</key>
                    <integer>0</integer>
                    <key>Enabled</key>
                    <true/>
                    <key>Find</key>
                    <data>AFAAbABhAHQAZgBvAHIAbQBTAHUAcABwAG8AcgB0AC4AcABsAGkAcwB0</data>
                    <key>Identifier</key>
                    <string>Apple</string>
                    <key>Limit</key>
                    <integer>0</integer>
                    <key>Mask</key>
                    <data></data>
                    <key>Replace</key>
                    <data>AC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAuAC4ALgAu</data>
                    <key>ReplaceMask</key>
                    <data></data>
                    <key>Skip</key>
                    <integer>0</integer>
                </dict>

 

Workaround for Clover: use boot-args: -no_compat_check and revpatch=sbvmm and add RestrictEvents.kext. The first one skips the board-id check, the 2nd one re-enables updates.

  • Like 1
Link to comment
Share on other sites

12 hours ago, mariosun said:

spent some time with Jief to understand a problem

to solve i have to put this:

image.png.6bdef8c46967b657d0d561198de261c7.png

 

With 0x0F01 i see correct CPU name using RestrictEvents kext

or Intel Xeon without using that kext

 

Is it documented in your WIKI?

Thank you

It is the question to RestrictEvents.kext if it set CPU name depending on CPU type.

If we speak about OS without RestrictEvents then CPU type must be one present in real MACs and than you'll see CPU name as in the real MAC. No matter of you real CPU.

  • Like 1
Link to comment
Share on other sites

1 hour ago, Slice said:

It is the question to RestrictEvents.kext if it set CPU name depending on CPU type.

If we speak about OS without RestrictEvents then CPU type must be one present in real MACs and than you'll see CPU name as in the real MAC. No matter of you real CPU.

Yes i think we are saying the same thing

 

In my case without RestrictEvents.kext and processor type set to 0

About my Mac has Xeon 16 Cores as CPU and this is the same with Clover Bootloader using Type set to 0x0F01

 

For both bootloaders with RestrictEvents.kext about my mac has AMD Ryzen 9 7950X 16-Core Processor

 

 common "problem" for both bootloaders is the frequency posted in About My Mac (4.3 Ghz)

It should be 4.5 Ghz

image.png.60275b2f37347c613a66f77c3269553c.png

 

OSX put the remain part here:

image.thumb.png.731cd49a9d78d4152ccac768da46a4bc.png

 

And this should be a common OSX problem for both AMD and Intel platform

 

Have you any experience in this? (For cpu with frequency greater than 4.3 GHz I mean)

 

Edited by mariosun
  • Like 1
Link to comment
Share on other sites

If the value 4.3GHz came from CPUID BrandString that I can do nothing. It is ROM.

But for System Profilier I can set own value

CPU->FrequencyMHz=4500

  • Thanks 1
Link to comment
Share on other sites

Hello everyone, I would like to know if anyone else is having problems with booting in version 5157. For me, since commit 00466c6 "reduce clover size" of version 5156 I have early boot hang on my z390 setup. Sorry for my English and I appreciate any help. thanks

Link to comment
Share on other sites

×
×
  • Create New...