Jump to content
30960 posts in this topic

Recommended Posts

3 hours ago, PG7 said:

Report Error boot Clover r5157 

Lenovo ThinkCentre M810z
intel i3-7100 KabyLake
intel HD630

Clover r5156 OK 
Clover r5157 No Boot 

Preboot.log 

preboot Clover r5156 work.log 60.19 kB · 1 download preboot Clover r5157 no work.log 57.86 kB · 1 download

You have different quirks

5156:

5:982  0:000  Kernel quirks
5:982  0:000  ACPCL 1 AXCL 1 AXEM 0 AXFB 0 CSG 0 DIM 1 DLJ 1 DRC 0 DPM 0 EBTFF 0 EDI 0 IPBS 0 LKP 0 PNKD 1 PTKP 1 TPD 1 XPL 0 PCC 0

5157:

7:890  0:000  Kernel quirks
7:890  0:000  ACPCL 0 AXCL 0 AXEM 0 AXFB 0 CSG 0 DIM 1 DLJ 1 DRC 0 DPM 0 EBTFF 0 EDI 0 FAI 0 IPBS 0 LKP 0 PNKD 1 PTKP 1 TPD 1 XPL 0 PCC 0

Simple way is to use same config.plist.

  • Like 2

@big thanks goes @Jief_Machak

now also AM5 AMD users could use Clover Bootloader with a perfectly working audio

 

i suggest to test when it is available his Clover commit to all user who have had audio problem in the past solved using some weird CPU parameters in config . plist

Maybe could help also for older platform than AM5 ;)

 

Edited by mariosun
  • Like 2
4 minutes ago, mariosun said:

@big thanks goes @Jief_Machak

now also AM5 AMD users could use Clover Bootloader with a perfectly working audio

 

i suggest to test when it is available his Clover commit to all user who have add audio problem in the past solved used some weird CPU parameters in config . plist

Maybe could help also for older platform than AM5 ;)

 

Thanks,

That's not even committed yet...

  • Like 2
50 minutes ago, Slice said:

You have different quirks

5156:

5:982  0:000  Kernel quirks
5:982  0:000  ACPCL 1 AXCL 1 AXEM 0 AXFB 0 CSG 0 DIM 1 DLJ 1 DRC 0 DPM 0 EBTFF 0 EDI 0 IPBS 0 LKP 0 PNKD 1 PTKP 1 TPD 1 XPL 0 PCC 0

5157:

7:890  0:000  Kernel quirks
7:890  0:000  ACPCL 0 AXCL 0 AXEM 0 AXFB 0 CSG 0 DIM 1 DLJ 1 DRC 0 DPM 0 EBTFF 0 EDI 0 FAI 0 IPBS 0 LKP 0 PNKD 1 PTKP 1 TPD 1 XPL 0 PCC 0

Simple way is to use same config.plist.


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 preboot Clover r5156 work.log

Edited by PG7
  • Like 1

@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

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
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
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
2 hours ago, PG7 said:

@Slice @Jief_Machak

With these NVRAM2 steps, is it possible to install and update Ventura and Sonoma on a PC with Legacy bios?
 

 

I propose this. And hope to success.

  • Like 2
  • Thanks 1
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
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

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

 

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

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

 

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
×
×
  • Create New...