Clover General discussion

[Slice]

@Matgen84,

It depends on your version of Xcode.

If < 14 then use XCODE8 toolset

if 14 then use XCODE14 toolset

if 15 then use XCODE15 toolset

Or just use GCC131 toolset.

[Matgen84]

2 minutes ago, Slice said:

@Matgen84,

It depends on your version of Xcode.

If < 14 then use XCODE8 toolset

if 14 then use XCODE14 toolset

if 15 then use XCODE15 toolset

Or just use GCC131 toolset.

 

@Slice I use as I said before: XCODE14 toolset. Without success. Can you take alook to spoiler: there is eoor message.

[Slice]

4 minutes ago, Matgen84 said:

 

@Slice I use as I said before: XCODE14 toolset. Without success. Can you take alook to spoiler: there is eoor message.

Because you are on Monterey? I saw your spoiler.

OSError: [Errno 66] Directory not empty: '/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8'

[Matgen84]

3 minutes ago, Slice said:

Because you are on Monterey? I saw your spoiler.

OSError: [Errno 66] Directory not empty: '/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8'

 

In fact, it's a GitHub issue: red cross on commit is replacing by green circle button. Now I can build latest commit without any problem (XCODE14 RELEASE folder).

 

Thanks.

[LockDown]

are there any lists of SMBIOS to avoid with T2 chip?

[Slice]

4 hours ago, LockDown said:

are there any lists of SMBIOS to avoid with T2 chip?

iMac19,1

MacBookPro15,1

AFAIK that's all that allowed for Sonoma software update.

[Matgen84]

@LockDown @Slice

I use SMBIOS iMac20,1 (Z390 config). Despite of explanation on support.apple, this iMac don't have T2 chip. 

 

To be sure having incremental update for Sonoma: I put restricevents.kext in Clover/Kext Folder, and revpatch=sbvmm with HWTarget to J185AP. I kept crsActiveConfig <key>0x285</key> from previous iMac19,1 config.plist.

Edited December 20, 2023 by Matgen84

[LockDown]

@Matgen84

revpatch=sbvmm would bypass it

[miliuco]

@Matgen84

I think that iMac20,1 does have T2 chip, so it has specific SecureBootModel value (j185).

SMBIOS lacking T2 doesn't need RestrictEvents to be notified of updates.

Reading your post I understand that you need RestrictEvents to get updates notifications, right?

[Matgen84]

21 hours ago, miliuco said:

@Matgen84

I think that iMac20,1 does have T2 chip, so it has specific SecureBootModel value (j185).

SMBIOS lacking T2 doesn't need RestrictEvents to be notified of updates.

Reading your post I understand that you need RestrictEvents to get updates notifications, right?

 

@miliuco

I apologize: you're right, iMac20,1 have a T2 chip. 

 

In summary, using iMac20.1 without RestrictEvents.kext I get update notifications but the updates are full-size. After the system is updated, RestrictEvents.kext and the boot argument can be disabled because they are not required for normal Sonoma operation.

 

21 hours ago, LockDown said:

@Matgen84

revpatch=sbvmm would bypass it

 

@LockDown

 

Since June and first Sonoma Beta, I add revpatch=sbvmm to boot arguments. I don't try to remove it before updating the system.

[Slice]

On 12/8/2023 at 9:05 PM, matxpa said:

@Slice

 

Hi

Here's what you want and what you need (BOOTX64.efi (and CLOVERX64.efi) after renaming the below efi components) of : 

 

 

r5157_a9b0654 (20231112-03h48) --> Wifi BCM 4360 works    CloverX64_r5157_20231112-03h48_a9b0654_XCODE15_RELEASE_master_local.efi

 

r5157_1914496 (20231116-19h14)   --> Wifi BCM 4360 works    CloverX64_r5157_20231116-19h14_1914496 _XCODE15_RELEASE_master_local..efi

 

r5157_bdb7a95 (20231116-22h10)  --> Wifi BCM 4360 works    CloverX64_r5157_20231116-22h10_bdb7a95_XCODE15_RELEASE_master_local.efi

 

What else ...

      ACPI/DSDT/Fixes           : FixAirport=TRUE

      Devices/FakeID             : WIFI=0x43a014e4

      KernelAndKextPatches : BlockSkywalk = TRUE 

      RtVariables                    : CsrActiveConfig=0x803 (just F.Y.I)

 

     kexts/14                          : AMFIPass.kext, IOSkywalkFamily.kext, IO80211FamilyLegacy.kext and RestrictEvents.kext) --> latest OC or OCLP releases

     kexts/Other                    : (Std kexts) ALC LILU WEG SMC(Virtual and specifics Asus X75VB kexts for RJ45, WebCam, KBD & PAD) --> latest OC or others Dev. releases

     

 

NB in KernelAndKextPatches/KextsToPatch

I don't need (Disabled=YES) the patch from www.applelife.ru (Broadcom 94360 activation AirPort.BrcmNIC)
 

Regards

Anyway these versions is not working on my computer, hang just after BootKernelExtensions.kc in verbose.mode if BlockSkywalk set.

If unset then all is good.

But I can't understand why it works in QEMU. What is the difference? Same file and same treatments. Somehow related to  memory map which is different?

[Slice]

Test please this version with BlockSkywalk. I don't promise full success but I excluded some CPU panics.

CLOVERX64.efi

Just wonder why native Opencore randomly works.

[jsl2000]

6 hours ago, Slice said:

Test please this version with BlockSkywalk. I don't promise full success but I excluded some CPU panics.

CLOVERX64.efi 1.46 MB · 4 downloads

Just wonder why native Opencore randomly works.

Thanks but this new BOOTX64.efi/CLOVERX64.efi did NOT work as the following in my Z490 hackintosh:

1. Booting Sonoma 14.2.1 got early hang just after BootKernelExtensions.kc in verbose.mode if BlockSkywalk set.

2. Booting Sonoma 14.2 got KP as shown here:

Hope you can find the solution ASAP !

Edited December 26, 2023 by jsl2000

[Slice]

Not sure about ASAP.

[mariosun]

13 hours ago, Slice said:

Test please this version with BlockSkywalk. I don't promise full success but I excluded some CPU panics.

CLOVERX64.efi 1.46 MB · 4 downloads

Just wonder why native Opencore randomly works.

Thanks Slice

Same problem of previous version on AM5 platform

[matxpa]

On 12/22/2023 at 5:14 PM, Slice said:

Anyway these versions is not working on my computer, hang just after BootKernelExtensions.kc in verbose.mode if BlockSkywalk set.

If unset then all is good.

But I can't understand why it works in QEMU. What is the difference? Same file and same treatments. Somehow related to  memory map which is different?

Hi Slice.

 

With your latest CloverX64.efi I don't get stuck immed. (after +/- 10 debug lines) but I get stuck with a memory fault KP (as jsl200 reports)

Preboot.log ends with a "Closing log", with previous commits (after bdb7a95 which one works fine with IOSkywalkFamily boolean and kext) Preboot.log didn't end as this last one does.

 

...

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

Regards

[MakAsus]

On 12/26/2023 at 12:58 PM, matxpa said:

Hi Slice.

 

With your latest CloverX64.efi I don't get stuck immed. (after +/- 10 debug lines) but I get stuck with a memory fault KP (as jsl200 reports)

Preboot.log ends with a "Closing log", with previous commits (after bdb7a95 which one works fine with IOSkywalkFamily boolean and kext) Preboot.log didn't end as this last one does.

 

...

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

Regards

Alas, even with the latest build, loading does not go further than this:

preboot.log

Edited December 27, 2023 by MakAsus

[MakAsus]

Clover revision: 5156 (master, commit f6fcfeccb) starts to behave differently. Instead of stopping loading with an early kernel panic, it happens a little later.

 

preboot.log

Edited December 27, 2023 by MakAsus

[STLVNUB]

Anybody With A 100% Working EFI For Sonoma Please Send It To Me Thanks

[Slice]

55 minutes ago, STLVNUB said:

Anybody With A 100% Working EFI For Sonoma Please Send It To Me Thanks

For example. This is my Skylake computer. SN changed.

EFI-slice.7z

[STLVNUB]

1 minute ago, Slice said:

For example. This is my Skylake computer. SN changed.

EFI-slice.7z 1.43 MB · 0 downloads

Thanks

[Slice]

Boot->Debug set to true for your test. You should set it to false finally.

And this is my DSDT. You should exclude it.

[STLVNUB]

42 minutes ago, Slice said:

Boot->Debug set to true for your test. You should set it to false finally.

And this is my DSDT. You should exclude it.

Thanks

[Slice]

One more note. There is DMAR.aml in the /EFI/CLOVER/ACPI/patched folder. Exclude it as it is hardware dependent for my computer.

[Jief_Machak]

Hi everyone,

I'm in the process to upgrade the OpenCore component of Clover to the latest 0.9.7.

It means that I will have to do a dozen of commits before you can try it.

 

I'm just saying that to avoid you wasting time compiling and trying.

 

I'll post a new message as soon as it is supposed to work. Should be in the next 48 hours.