Clover General discussion

[cankiulascmnfye]

8 hours ago, MakAsus said:

How can I make the configs switch themselves depending on the OS? In case I use SMBIOS_ventura and general SMBIOS with the same value CsrActiveConfig = 0x0000, I can replace it with 0x0803 before the patch only in general SMBIOS. BlockSkywalk already OS dependent. Now the value CsrActiveConfig = 0x0803 is interferes me in Ventura.

 

1. You can't. You have to switch configs manually from the boot menu gui (under Options/Configs). Oh, and the system might freeze after loading the 2nd config.

2. You also have to change the CsrActiveConfig manually (under Options/System Parameters) because it's not part of the SMBIOS but RT variables. BTW: the correct value is: 0x803

[Slice]

9 hours ago, tluck said:

recently tried to the lasted 5157 from v5156
but the changes after commit "Changes in OC" 5817644aa00228c74dbf873a43e6cff7e49ca288 (5817644) break Clover for me.
I get
1) unsupported graphics -> black screen
2) also no kexts were injected from the ESP. 
 

Impossible. May be you are using VirtualSMC which was declared as not Clover compatible?

[fabiosun]

15 hours ago, MakAsus said:

How can I make the configs switch themselves depending on the OS? In case I use SMBIOS_ventura and general SMBIOS with the same value CsrActiveConfig = 0x0000, I can replace it with 0x0803 before the patch only in general SMBIOS. BlockSkywalk already OS dependent. Now the value CsrActiveConfig = 0x0803 is interferes me in Ventura.

duplicate your main config

ie

config.plist

config-1.plist

set in config.plist Sip and other values as you like ie to use it with OCLP for modern wireless Network patch

set config-1.plist with sip enabled and disabling the new sonoma kext block

 

the only two problems you may have could be of this type:

 

1)I use my second config to disable BlockSkywalk but i have the older ones  in Kext folder so i have to block also the kexts (press space bar and block kexts as you like)

2) sip value may need of a Reset Nvram (F11) to change

 

I have no particular freeze (maybe i am lucky)

I can use 0x803 or 0x0803 to soft disable SIP (and maybe i am lucky also in this)

 

 

 

 

 

Edited January 22, 2024 by mariosun

[MakAsrock]

4 hours ago, mariosun said:

duplicate your main config

ie

config.plist

config-1.plist

set in config.plist Sip and other values as you like ie to use it with OCLP for modern wireless Network patch

set config-1.plist with sip enabled and disabling the new sonoma kext block

 

the only two problems you may have could be of this type:

 

1)I use my second config to disable BlockSkywalk but i have the older ones  in Kext folder so i have to block also the kexts (press space bar and block kexts as you like)

2) sip value may need of a Reset Nvram (F11) to change

 

I have no particular freeze (maybe i am lucky)

I can use 0x803 or 0x0803 to soft disable SIP (and maybe i am lucky also in this)

 

 

 

 

 

This is how I do it now, but I would like it to be like this (Because BlockSkywalk works in an OS higher than Ventura):

Edited January 22, 2024 by MakAsus

[fabiosun]

ok @MakAsus i miss your was a "features" request

 

maybe it would be more simple add a matchOS parameter for that section

 

Edited January 22, 2024 by mariosun

[cankiulascmnfye]

4 hours ago, mariosun said:

 

I can use 0x803 or 0x0803 to soft disable SIP

 

Fist of all: there is no such thing as "soft-disable". csractiveconfig is a bitmask consisting of 12 possible bits representing flags - in this case Bits 00, 01 and bit 11. Nothing "soft" about it!

Second: Clover uses BIG Endian. So the leading zero (0x) already represents the 0 you added.  You can consider yourself lucky that the additional zero is just ignored of shifting bits around!

[MakAsrock]

1 hour ago, mariosun said:

ok @MakAsus i miss your was a "features" request

 

maybe it would be more simple add a matchOS parameter for that section

 

By the way, yes. This may be simpler, but what if someone needs a value other than 0x0000 for an OS below Sonoma, or a value other than 0x0803 for Sonoma (for example, if they don't have WiFi)?
If I take out my Fenvi FV-HB1200, I no longer need the OSPL patch.

 

1 hour ago, cankiulascmnfye said:

 

Fist of all: there is no such thing as "soft-disable". csractiveconfig is a bitmask consisting of 12 possible bits representing flags - in this case Bits 00, 01 and bit 11. Nothing "soft" about it!

Second: Clover uses BIG Endian. So the leading zero (0x) already represents the 0 you added.  You can consider yourself lucky that the additional zero is just ignored of shifting bits around!

Maybe I didn’t express myself quite correctly somewhere, I meant partial disabling of SIP. As for the values 0x803, I apparently missed when in Clover changed to BIG Endian. Made some minor fixes to the repository.

Edited January 22, 2024 by MakAsus

[Slice]

Not sure about words "BIG endian". Numbers, decimal or hexadecimal always written as Arabian numbers, right to left. So 2024 has 4 as low significant digit. 0x0803 has bit 0 at the right of the sequence. It is the sense of "Little Endian". Endian located at the end of the word, at the right. The most right digit has lowest significant.

 

[tluck]

7 hours ago, Slice said:

Impossible. May be you are using VirtualSMC which was declared as not Clover compatible?

hmm. i am just reporting the facts as I see them! 
Note: I downloaded your 5157 build of Clover and replaced my BOOTX64.efi
5156 is fine and some of the new 5157 changes up this change works for me.

-> the change in gma.cpp with IPGU_LESS seem to be problematic?
not sure why kexts are not injected - i didnt track down the issue with kext injection yet.

I use FakeSMC.kext - does the name kexts vs Kexts matter?
 

$ ls -ld1 kexts/Other/*

kexts/Other/ACPIBatteryManager.kext

kexts/Other/ACPIPoller.kext

kexts/Other/AX88179_178A.kext

kexts/Other/AppleALC.kext

kexts/Other/BlueTooth_Injector_T420.kext

kexts/Other/EFICheckDisabler.kext

kexts/Other/FakeSMC.kext

kexts/Other/IOAHCIBlockStorageInjector.kext

kexts/Other/Lilu.kext

kexts/Other/USBInjectAll.kext

kexts/Other/VoodooPS2Controller.kext

kexts/Other/WhateverGreen.kext

[Slice]

To clarify the question about Little and Big Endian let consider UUID. There is a big difference.

Internally UUID represented as 128 bit value which consists of one 32bit value Data0, two 16bit values Data1, Data2, and eight 8bit values.

For example {0x8BE4DF61, 0x93CA, 0x11D2, {0xAA, 0x0D, 0x00, 0xE0, 0x98, 0x03, 0x2B, 0x8C}};

But convert to string value requires arrangement is it Little Endian (as Microsoft, Intel and UEFI) or Big Endian (as Apple and FreeBSD AFAIK).

So we'll obtain different strings

"8BE4DF61-93CA-11D2-AA0D-00E098032B8C" or

"61DFE48B-CA93-D211-AA0D-00E098032B8C"

As Clover works from UEFI for macOS we have to convert string UUID from Little Endian (UEFI protocols) to Big Endian (Partitions UUID).

 

40 minutes ago, tluck said:

hmm. i am just reporting the facts as I see them! 
Note: I downloaded your 5157 build of Clover and replaced my BOOTX64.efi
5156 is fine and some of the new 5157 changes up this change works for me.

-> the change in gma.cpp with IPGU_LESS seem to be problematic?
not sure why kexts are not injected - i didnt track down the issue with kext injection yet.

I use FakeSMC.kext - does the name kexts vs Kexts matter?
 

$ ls -ld1 kexts/Other/*

kexts/Other/ACPIBatteryManager.kext

kexts/Other/ACPIPoller.kext

kexts/Other/AX88179_178A.kext

kexts/Other/AppleALC.kext

kexts/Other/BlueTooth_Injector_T420.kext

kexts/Other/EFICheckDisabler.kext

kexts/Other/FakeSMC.kext

kexts/Other/IOAHCIBlockStorageInjector.kext

kexts/Other/Lilu.kext

kexts/Other/USBInjectAll.kext

kexts/Other/VoodooPS2Controller.kext

kexts/Other/WhateverGreen.kext

Yes, may be IGPU_LESS influences on your case. Can you unset the define to check if this is the case?

[Slice]

But why no kexts injected? All is fine for me and others.

 

[MakAsrock]

6 hours ago, MakAsus said:

By the way, yes. This may be simpler, but what if someone needs a value other than 0x0000 for an OS below Sonoma, or a value other than 0x0803 for Sonoma (for example, if they don't have WiFi)?
If I take out my Fenvi FV-HB1200, I no longer need the OSPL patch.

 

Maybe I didn’t express myself quite correctly somewhere, I meant partial disabling of SIP. As for the values 0x803, I apparently missed when in Clover changed to BIG Endian. Made some minor fixes to the repository.

No, I checked the source code and the correct value is still 0x0803. I returned it as it was.

[jsl2000]

On 1/17/2024 at 1:55 AM, Slice said:

I propose this. And hope to success.

Did anyone can update whose Monterey, Ventura, or Sonoma with legacy Clover 5156 or 5157 now ?

Mine always failed up to now !

[tluck]

11 hours ago, Slice said:

 

 

Yes, may be IGPU_LESS influences on your case. Can you unset the define to check if this is the case?

Ok I moved my kexts from Clover/OEM/boardID/kexts/Other to Clover/kexts/Other and kext inject from ESP worked with the latest 5157.
I reverted the gma.cpp from the old commit and all is good now.


 

[Slice]

2 hours ago, tluck said:

Ok I moved my kexts from Clover/OEM/boardID/kexts/Other to Clover/kexts/Other and kext inject from ESP worked with the latest 5157.
I reverted the gma.cpp from the old commit and all is good now.


 

So OEM/boardID cancel to work since some moment? Since join with OC?

[phi777]

I have a problem with v5156 and v5157. When I copy it, as ususal, I can restart and boot without a problem. But after powering down and starting I am always getting "found dead pci device GFX0" and booting stops. Should I look into this blockskywalk thing? I am using latest ventura. Thank you for reading this.

Edited January 23, 2024 by phi777

[Slice]

BlockSkywalk works only for Sonoma.

Your problem looks like BIOS problem. Or may be CPU cores synchronization.

Make preboot.log I will see it. 

[phi777]

Here they are, both are using the same config.plist

preboot-v5155-good.log preboot-v5157-deadgfx0.log

EDIT: I have attached one preboot, where I updated from 5155 to 5157 and restarted, without powering down the computer, which works.

preboot-v5157-withoutPowerDown.log

Edited January 23, 2024 by phi777

[fabiosun]

@Slice Is it possible to block a kext using a config.plist parameter/section?

 

IE

For modern wireless patch done by OCLP app we need to use two old kext, AMFIpass.kext and some other things like  SIP @0x0803 

In this condition OSX is not able to update itself with delta update

 

Now i can use a different Config,plist and very useful Clover feature in Boot Menu stage ( I press space and block unwanted kexts from there)

 

Is it possible? or Could it be a wishlist feature to ask you and Jief?

Thank you

[tluck]

7 hours ago, Slice said:

So OEM/boardID cancel to work since some moment? Since join with OC?

Ok interesting.  OEM/boardID/kexts works up to now. meaning some change in december for 5157.

[MakAsrock]

1 hour ago, mariosun said:

@Slice Is it possible to block a kext using a config.plist parameter/section?

 

IE

For modern wireless patch done by OCLP app we need to use two old kext, AMFIpass.kext and some other things like  SIP @0x0803 

In this condition OSX is not able to update itself with delta update

 

Now i can use a different Config,plist and very useful Clover feature in Boot Menu stage ( I press space and block unwanted kexts from there)

 

Is it possible? or Could it be a wishlist feature to ask you and Jief?

Thank you

Yes, as far as I know, this is possible.
Only instead of just block unwanted kexts, I put them in the EFI/CLOVER/kexts/14 folder
By space they are locking and from there, but they don’t interfere with Ventura.

[Slice]

7 hours ago, phi777 said:

Here they are, both are using the same config.plist

preboot-v5155-good.log 50.2 kB · 1 download preboot-v5157-deadgfx0.log 49.91 kB · 2 downloads

The logs are almost same. But I wonder if 5155 works and 5156 no. There is no differences which may prevent old working config to be working with new Clover.

Test latest version

 

CLOVERX64.efi.zip

[fabiosun]

3 minutes ago, MakAsus said:

Yes, as far as I know, this is possible.
Only instead of just block unwanted kexts, I put them in the EFI/CLOVER/kexts/14 folder
By space they are locking and from there, but they don’t interfere with Ventura.

Yes this is how it works

but i need for sonoma

Using OCLP i use different kext as you know if you patch WIFI

in OCLP patched condition i cant update to new sonoma beta

So i use a second config where i enable sip and disable the usual block

Then manually i block the two kexts i have in other or in 14 folder

If it was possible to declare in config a kext block as we can do with Skywalk it would be possible only to change config.plist (unvaluable clover feature)

 

 

[Slice]

50 minutes ago, tluck said:

Ok interesting.  OEM/boardID/kexts works up to now. meaning some change in december for 5157.

May be boardID changed? Because now it injected after OS choose. I will check.

No, the feature was in 5155.

[fabiosun]

7 minutes ago, mariosun said:

Yes this is how it works

but i need for sonoma

Using OCLP i use different kext as you know if you patch WIFI

in OCLP patched condition i cant update to new sonoma beta

So i use a second config where i enable sip and disable the usual block

Then manually i block the two kexts i have in other or in 14 folder

If it was possible to declare in config a kext block as we can do with Skywalk it would be possible only to change config.plist (unvaluable clover feature)

 

 

 

A simple solution is to use BootloaderChooser and use two different EFI but Kext blocking in config.plist would be a perfect solution (and i think Clover has this feature in its code)