Clover General discussion

[matxpa]

16 hours ago, miliuco said:

@matxpa

If the key is to show 08030000 instead of 0x0803000 as @Slice says (I'm not sure of understand completely this statement), it's easy to remove 0x in the tooltip:

 if sipValue.length == 12 && !sipValue.contains("(0x\">\"g)") { osSipInfo += "(" + "\(sipValue.dropFirst(3))\n" } else { osSipInfo += "\n"}

What do you think about it?

 

  Reveal hidden contents

 

 

@miliuco

 

Hi

 

ioreg -fiw0 -p IODeviceTree -rn options | grep "csr-active-config" | awk '{print substr($NF,8,2) substr($NF,6,2) substr($NF,4,2) substr($NF,2,2)}' | sed -e 's/^0*/(0x/g' -e 's/0*$/)/g'

(0x803)

nvram csr-active-config | sed 's/%//g' | awk '{print substr($NF,8,2) substr($NF,6,2) substr($NF,4,2) substr($NF,2,2)}' | sed -e 's/^0*/(0x/g' -e 's/0*$/)/g'

(0x803)

 

Regards

Edited January 12, 2024 by matxpa

[rramon]

On 1/10/2024 at 8:03 PM, MakAsus said:

If you only have one Sonoma, then all the kexts can be put in the folder  EFI/CLOVER/kexts/Other, but even in this case, I think it’s more correct to put the problematic kexts in the folder  EFI/CLOVER/kexts/"system number". This will allow you, in an emergency, to boot into the installer of the previous version of the OS.
Mini-PCIE 12+6 Pin Adapter plugged directly on my motherboard, so no "classic" PCI-E It works exactly the same way for a friend of mine.
Otherwise, you set the value 0x0803, then you will fulfill the requirement for the root OCLP patch. I do not recommend disabling SIP completely; most programs will stop working. And you will need to find patches for each of them, and so Lilu and AMFIPass do everything you need automatically.
One last thing: I have never used OCPL from Clover before. Always from OpenCore. This is a much more difficult way requiring more power understanding each of the settings. In my case, the order to adding each kext was strictly important.
IOSkywalkFamily.kext should be below WhateverGreen.kext like on a picture:

 

Thanks for your thorough explanation, this helps so much! 👍

 

I have one last question regarding SIP:

just checked and my current setting is 0x67 (I‘m using Plist Editor Pro to edit my config.plist). Would this work with OCLP and if not, is 0x0803 similar in safety as 0x67 or more strict? 
 

Thanks again 

[miliuco]

@rramon

0x803 is mandatory for OCLP root patch. No patch with any other value. 

[Slice]

0x867 will be logical sum of these two values.

42 minutes ago, miliuco said:

@rramon

0x803 is mandatory for OCLP root patch. No patch with any other value. 

I doubt about any. But I can't check as I need no OCLP.

[LAbyOne]

1 hour ago, miliuco said:

@rramon

0x803 is mandatory for OCLP root patch. No patch with any other value. 

 

Not true (in my case at least) as to run certain app i needed 867 and OCLP never failed

 

[rramon]

Hmm, I have a mid 2012 MacBook Pro 9,1 running fine with OCLP (Ventura) and completely disabled SIP - but I‘m not sure about Clover in combination with OCLP..

 

Does OCLP actually „know“ the 0x67 value?

Edited January 12, 2024 by rramon

[LAbyOne]

OCLP

Run after checking the minimum requirements to operate are met,

is just an application made to apply a bunch of patches to enable older hardware on most recent OS

 

the value suggested by Dortania being 803 is the CSR minimum needed configuration to apply patches

 

1 hour ago, rramon said:

Does OCLP actually „know“ the 0x67 value?

 

Who cares?

SIP is the one that take care of it not OCLP

you can use whatever CSR configuration if it integrates the minimum values required to modify the System

[miliuco]

@Slice @LAbyOne 

Not tried all values, this statement follows from the OCLP guide. In my experience, when SIP is not 0x803 OCLP says to set SIP to 0x803 and reboot before applying root patch.

Edited January 13, 2024 by miliuco

[cankiulascmnfye]

13 hours ago, rramon said:

Hmm, I have a mid 2012 MacBook Pro 9,1 running fine with OCLP (Ventura) and completely disabled SIP - but I‘m not sure about Clover in combination with OCLP..

 

Does OCLP actually „know“ the 0x67 value?

 

• OCLP has 2 main features:
  1. Installing OpenCore Bootloader (on real Macs)
  2. Applying patches to the system volume (installing removed kexts, frameworks, patching system files, etc) to make macOS work with legacy hardware
• So, you can patch the system with OCLP but use Clover to boot (if it is configured correctly)

As far as SIP "0x67" is concerned:

• 0x67 = Big Endian, used by Clover. OpenCore uses Little Endian, in this case: 07060000 which is insufficient for patching macOS with OCLP
• For patching macOS when using Clover, you must change the CsrActiveConfig to 0x803 as mentioned by miliuco

And: OCLP doesn't need to "know" the value, because it gets it from the system, which gets it from NVRAM which gets it form the bootloader (injected value set in config.plist).

[rramon]

12 hours ago, LAbyOne said:

Who cares?

I do 😊

 

11 minutes ago, cankiulascmnfye said:

 

• OCLP has 2 main features:
  1. Installing OpenCore Bootloader (on real Macs)
  2. Applying patches to the system volume (installing removed kexts, frameworks, patching system files, etc) to make macOS work with legacy hardware
• So, you can patch the system with OCLP but use Clover to boot (if it is configured correctly)

As far as SIP "0x67" is concerned:

• 0x67 = Big Endian, used by Clover. OpenCore uses Little Endian, in this case: 07060000 which is insufficient for patching macOS with OCLP
• For patching macOS when using Clover, you must change the CsrActiveConfig to 0x803 as mentioned by miliuco

And: OCLP doesn't need to "know" the value, because it gets it from the system, which gets it from NVRAM which gets it form the bootloader (injected value set in config.plist).

Great and very informative, thank you!

[Slice]

I don't know but OCLP may contains check as 

if (SIP != 0x803) exit;

although it is not really needed. They should say the recommendation and let user to try.

[matxpa]

On 1/11/2024 at 7:35 PM, Slice said:

Again

"csr-active-config" = <03080000> is right

But About_This_Hack shows 0x03080000 which is wrong.

https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&comment=2815397

 

 

Hi 

A more satisfying version ?

 

 

 

or this one

 

 

Regards

 

Edited January 13, 2024 by matxpa

[miliuco]

@matxpa
I can’t add anything more. Perfect. Better without green checks. Is it in yout repo?

[MakAsrock]

1 hour ago, matxpa said:

 

Hi 

A more satisfying version ?

 

 

 

or this one

 

 

Regards

 

It seems to me that without green checks is better. Where can I download it?

[matxpa]

2 hours ago, miliuco said:

@matxpa
I can’t add anything more. Perfect. Better without green checks. Is it in yout repo?

 

@miliuco @MakAsus

Hi

 

In my Repo, get (select all & copy) only HardwareCollectors/HCVersion.swift, the only one which was modified and GREEN checkMark use in comment

https://github.com/matxpa/About-This-Hack/blob/main/About This Hack/HardwareCollectors/HCVersion.swift

 

Regards

[cankiulascmnfye]

9 hours ago, Slice said:

I don't know but OCLP may contains check as 

if (SIP != 0x803) exit;

although it is not really needed. They should say the recommendation and let user to try.

 

No, you shouln't let users just try it. Because OCLP is for Apple users who don't know isht about the inner workings of macOS

[MakAsrock]

On 1/13/2024 at 8:58 PM, matxpa said:

 

@miliuco @MakAsus

Hi

 

In my Repo, get (select all & copy) only HardwareCollectors/HCVersion.swift, the only one which was modified and GREEN checkMark use in comment

https://github.com/matxpa/About-This-Hack/blob/main/About This Hack/HardwareCollectors/HCVersion.swift

 

Regards

Thanks for regexps. I'm not very good with them, and I would spend a week to do this.
I got only HardwareCollectors/HCVersion.swift from yours repository and clone the remain sources from the main repository 0xCUB3/About-This-Hack, but I took the old icons from repository Slice (I like them better) until I make my own.

Edited January 15, 2024 by MakAsus

[MakAsrock]

Now it looks like this:

 

Edited January 14, 2024 by MakAsus

[Henry2010]

Thanks for the 5157 update and happy new year!

[odemolay]

happy new year (we are going to need some wishes and hopes  this year again) wonderful work Clover runs my hacks....and they love it

Edited January 14, 2024 by odemolay

[MakAsrock]

On 1/11/2024 at 9:22 PM, MakAsus said:

 

I changed my config file:
 

	<dict>
		<key>Memory</key>
		<dict>
			<key>Channels</key>
			<integer>2</integer>
		</dict>
		<key>Trust</key>
		<true/>
	</dict>

and nothing has changed.

preboot.log 67.5 kB · 3 downloads

I found my old preboot log, when the order of the dims was determined correctly still to Clover revision: 5119 (HEAD, commit a0948b2). Maybe this will help localize the problem.

preboot.log

Edited January 15, 2024 by MakAsus

[fabiosun]

hi @Slice

i have followed this instructions to convert some Kernel patches to Clover:

 

Name seems to be skipped:

Warning: Unknown key '/KernelAndKextPatches/KernelToPatch[10]/Name:636'. Skipped.
Warning: Unknown key '/KernelAndKextPatches/KernelToPatch[11]/Name:668'. Skipped.

Attached the patches used for Opencore and Clover Bootloaders

 

Could you help to understand?

Thank you

patches.zip

Edited January 15, 2024 by mariosun

[Slice]

Kernel has no Name. It is for kext patching.

[fabiosun]

35 minutes ago, Slice said:

Kernel has no Name. It is for kext patching.

In Opencore there is only a patch section

So in Clover i have to use it in Kext to patch also with latest opencore implementation done in Clover?

 

Edit:

Ok in KextToPatch works as Slice said (different from OpenCore also in latest implementation) 

 

Edited January 15, 2024 by mariosun

[PG7]

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