Jump to content
30960 posts in this topic

Recommended Posts

9 minutes ago, laobamac_yyds said:

Emmm, bro, actually you can use -amfipassbeta boot-arg and AMFIPass.kext when patching with OCLP-Mod.Non-need disable AMFI.

26.4B1 can install the wireless network card patch separately for normal operation, and other patches need to wait for KDK.

 

Off-topic: What on earth is Apple doing? Since the XNU version number has been updated, why not follow the new KDK? Shouldn't KDK follow the new version of XNU to be released synchronously?🤬

Unfortunately, even -amfipassbeta doesn't help in my case. I immediately get a kernel panic. 🙁

  • Like 1
  • Sad 1
17 minutes ago, Slice said:

Check in VoodooHDA this line

Снимок экрана 2026-02-23 в 19.12.49.png

The InputMonitor may produce a noise.

Also reduce Mixer values to 90-95. Value of 100 produces a noise.

I am waiting to see your find.

Hi @Slice! 👋 It turned out to be unimportant and I reverted it. I did, however, fix a typo and an unclosed parenthesis in loader.cpp, but you've already merged my request. 
Thanks for bringing the VoodooHDA setting to my attention. I'll give it a try. 🤝

Edited by MakAsrock
  • Like 1
16 hours ago, MakAsrock said:

Release-5169 updated to 84a42ce 1 hour ago.
I'm already writing from it. 😊

Huh

SWPrintf("\\.IABootFilesSystemVersion.plist"); // 10.9 - 10.13.3

How long this bug exists? More than year?

  • Like 2
1 hour ago, Slice said:

Huh

SWPrintf("\\.IABootFilesSystemVersion.plist"); // 10.9 - 10.13.3

How long this bug exists? More than year?

Starting with OS X Mavericks 10.9, if I'm not mistaken and up to macOS High Sierra 10.13.

Edited by MakAsrock
  • Like 1

Hello my dear coder friends, just to let you know that Xcode 26.4 B2 and the Command Line Tools for 26.4 B2 are compiling Clover perfectly.

 

Don't forget run this command before start use Xcode

 

Beta

sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer && xcode-select -p && xcodebuild -version 

 

CapturadeTela2026-02-24s09_43_01.thumb.png.d0d9e55e2abc75d1846bdb507d7673e0.png

 

 

I have been use my Clover Compiler Builder v14.3 ;) 

  • Like 2

@laobamac_yyds You may want to move the VoodooHDA discussion to here.  Now that you're officially a Dev (congrats!), maybe you can rewrite VoodooHDA so that it can be injected by a boot loader (without installing in /L/E).

 

EDIT: Note that VoodooHDA.kext was able to be injected by boot loader until more recent versions of macOS.

Edited by deeveedee
  • Like 2
  • Thanks 2
20 hours ago, MakAsrock said:

I confirm. It built without errors, but didn't boot into the GUI.

I repair the problem. Very big commit.

But the next problem is still not resolved

Same sources compiled by clang

46:256  0:002  OSName=sequoia

compiled by gcc

56:660  0:001  OSName=伀汃獡s瑰污ⴱ㈴0

So the memory is still broken if compile by gcc.

  • Like 2
  • Thanks 1
5 hours ago, LockDown said:

@Slice based on your post, wil there be changes in config.plist structure even we don't use customEntry?

This is a very old idea to insert KernelAndKextPatches inside customEntry but I think nobody use it. Since 5170 it is prohibited. Otherwise don't care.

2 hours ago, LockDown said:

where can i see this bug? tried searching my GUI & logs, nothing! 😕

I found this bug with testing SMBIOS new feature. It should choose different SMBIOS based on OSName

3:109  0:000  ... ACPI
3:109  0:000  ... Boot
3:109  0:000  ... BootGraphics
3:109  0:000  ... CPU
3:109  0:000  ... Devices
3:109  0:000  ... GUI
3:109  0:000  ... Graphics
3:109  0:000  ... KernelAndKextPatches
3:109  0:000  ... SMBIOS
3:109  0:000  ... SMBIOS_sequoia
3:109  0:000  ... SMBIOS_tahoe
3:109  0:000  ... SystemParameters
3:109  0:000  ... RtVariables
3:109  0:000  ... Quirks

But somehow it is not working if Clover compiled by GCC151. 

  • Like 3

This is just gcc bug.

Codes:

  XStringW FileName;


DBG("OSName=%ls at 1445\n", OSName.wc_str());
  FileName = LoaderPath.basename();
DBG("OSName=%ls at 1447\n", OSName.wc_str());

debug.log

6:811  0:002  OSName=sequoia at 1679
6:814  0:002  OSName=sequoia at 1445
6:816  0:002  OSName=boot.efi at 1447
6:819  0:002  OSName=boot.efi at 1452

OSName was replaced after assigning to local variable FileName!

  • Like 2
2 hours ago, Slice said:

This is just gcc bug.

Codes:

  XStringW FileName;


DBG("OSName=%ls at 1445\n", OSName.wc_str());
  FileName = LoaderPath.basename();
DBG("OSName=%ls at 1447\n", OSName.wc_str());

debug.log

6:811  0:002  OSName=sequoia at 1679
6:814  0:002  OSName=sequoia at 1445
6:816  0:002  OSName=boot.efi at 1447
6:819  0:002  OSName=boot.efi at 1452

OSName was replaced after assigning to local variable FileName!

After this fix, when changing the theme, by pressing enter, the menu freezes completely. 🙁
I made a revert for myself.

  • Like 1
2 hours ago, MakAsrock said:

After this fix, when changing the theme, by pressing enter, the menu freezes completely. 🙁
I made a revert for myself.

But my workaround can't influence on theme! So this is one more bug.

  • Like 1
  • Sad 1

Here I wrote a utility called ToolsCheckIissues.py which scans for strings with suspicious syntax.
It finds potentially extra spaces and unclosed parentheses.
Creates a file with pointers: strings.txt
Usage:
Place it in the file folder or folder containing files.
Place the utility next to it, thenPlace the file in a folder or folder containing files.
Place the utility next to it, then enter the command:
cd "path to folder"
./ToolsCheckIissues.py >strings.txt 

ToolsCheckIissues.zip

  • Like 4
×
×
  • Create New...