Jump to content

Clover General discussion


ErmaC
30,156 posts in this topic

Recommended Posts

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.

 

  • Like 1
Link to comment
Share on other sites

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

  • Confused 1
Link to comment
Share on other sites

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?

  • Like 1
Link to comment
Share on other sites

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.

  • Like 1
Link to comment
Share on other sites

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 !

Link to comment
Share on other sites

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.


 

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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 by phi777
  • Sad 1
Link to comment
Share on other sites

BlockSkywalk works only for Sonoma.

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

Make preboot.log I will see it. 

  • Like 2
Link to comment
Share on other sites

@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

  • Like 1
Link to comment
Share on other sites

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.

  • Confused 1
Link to comment
Share on other sites

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.

  • Like 1
Link to comment
Share on other sites

7 hours ago, phi777 said:

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

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

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

 

 

  • Like 1
Link to comment
Share on other sites

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.

  • Like 1
Link to comment
Share on other sites

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)

  • Like 1
Link to comment
Share on other sites

11 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) :)

 

 

Yes. It also works the way you described.

Link to comment
Share on other sites

1 hour ago, tluck said:

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

Probably commit 956cfc1ad4b45acda7a4d99c7118bd23e1f55e40?

  • Like 1
Link to comment
Share on other sites

30 minutes ago, mariosun said:

Explain how :) Please

I would like to block thiese kext in blue:

image.png.d9fe10eab822d593669b3edadda0561e.png

Please, here are the screenshots:

screenshot0.png

screenshot1.png

screenshot2.png
As a result, I booted into pure Sonoma, with SIP enabled.

Edited by MakAsus
  • Like 2
Link to comment
Share on other sites

Ok @MakAsus this is how it works and i use in this way as you say with pictures :)

 

45 minutes ago, mariosun said:

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

 

but i would like to know if we can add those kexts blocking feature inside our second config-1 plist:

image.png.52f58b6a4dfb436904fab90d8d8c74b6.png

 

In my picture a whishlist feature request :)

In this way

i would change only the config.plist

I hope i have explained in a more clear way! 

  • Like 1
Link to comment
Share on other sites

10 minutes ago, mariosun said:

Ok @MakAsus this is how it works and i use in this way as you say with pictures :)

 

 

but i would like to know if we can add those kexts blocking feature inside our second config-1 plist:

image.png.52f58b6a4dfb436904fab90d8d8c74b6.png

 

In my picture a whishlist feature request :)

In this way

i would change only the config.plist

I hope i have explained in a more clear way! 

 

I assume this has not been implemented. However, no one is stopping you from temporarily moving these Kexts to the off folder. I'm not a programmer and I can't do this.

Edited by MakAsus
  • Like 2
Link to comment
Share on other sites

×
×
  • Create New...