Jump to content

Lilu — kext and process patcher


vit9696
395 posts in this topic

Recommended Posts

@vit9696

Intel i7-5960X

Motherboard-X99

 

The 5960X CPU not load without this patch.

Find       483D0000 0040

Replace      483D0000 0080

Identifier       IOPCIFamily

 

I request to Lilu.Kext  help to 5960X CPU patch.

Thank you.I try to kext patch with OC but not work.

Edited by nmano
  • Like 1
Link to comment
Share on other sites

These kexts need to be updated to reflect the latest Lilu changes. The new Lilu version is scheduled for release next week.

 

Basically this is change needed:

https://github.com/acidanthera/WhateverGreen/commit/51dc5860450aabe9f6c74a222bc3242e233fe136#diff-39882920309ec9fa38bceb302a8a0becR120

Please ask these kext authors to update them or actually send pull request.

 

Side note, kext binaries built with the previous version of Lilu SDK kext will continue to work.

  • Like 1
Link to comment
Share on other sites

5 hours ago, vit9696 said:

These kexts need to be updated to reflect the latest Lilu changes. The new Lilu version is scheduled for release next week.

 

Basically this is change needed:

https://github.com/acidanthera/WhateverGreen/commit/51dc5860450aabe9f6c74a222bc3242e233fe136#diff-39882920309ec9fa38bceb302a8a0becR120

Please ask these kext authors to update them or actually send pull request.

 

Side note, kext binaries built with the previous version of Lilu SDK kext will continue to work.

Thanks

Done, all solved..

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...

Can't build any plugin (all master) since recent updates:

/Users/yurikoles/work/kexts/AirportBrcmFixup/Lilu.kext/Contents/Resources/Headers/kern_disasm.hpp:12:10: fatal error: 'Headers/hde64.h' file not found
#include <Headers/hde64.h>
         ^~~~~~~~~~~~~~~~~



 

 

Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...

  0:005  ->Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext.dSYM (v.)
  0:001  Failed to load extra kext (Info.plist not found): EFI\CLOVER\kexts\Other\Lilu.kext.dSYM

 

in relase, there a file call Lilu.kext.dSym that is all tiem set to 0 (no file)

 

thanks to fix this

 

Link to comment
Share on other sites

9 minutes ago, maclinuxG4 said:

  0:005  ->Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext.dSYM (v.)
  0:001  Failed to load extra kext (Info.plist not found): EFI\CLOVER\kexts\Other\Lilu.kext.dSYM

 

in relase, there a file call Lilu.kext.dSym that is all tiem set to 0 (no file)

 

thanks to fix this

 

 

In release folder, there is always two files: Lilu.kext and Lilu.kext.dSYM. Copy only Lilu.kext in EFI/CLOVER/Kexts/Other

 

No fix need :)

Link to comment
Share on other sites

lilu.kext.dSym is still to size 0 size that means not generate properly

 

Please donwload and check 

thank

 

the file lilu.kext.dSym is to fix.

 

i use also pacifist to chekc and i confirm: the size is 0 !!!!

(dwarf folder ??????)

Edited by maclinuxG4
  • Haha 1
Link to comment
Share on other sites

  • 1 month later...

Hi guys, I’m trying to basically combine a Lilu plugin that I wrote and works, and a generic IOKit driver that I wrote, conforming to IOService. Unfortunately, when I try to do that, I get an error: “Variable has protected destructor”. In kernel_start.cpp. 
Is it even possible to do that or would I need an extra object that acts as IOService?

I read the source code of CPUFriend, which is a Lilu plugin with IOService and it uses an extra object conforming to IOServce, but I don’t understand where it is created and how these objects (the main plugin class and the service) communicate. 
Any help would be appreciated, thanks!

Link to comment
Share on other sites

Okay, here some more info, sorry, I was in a hurry earlier.

 

I am trying to setup KEXT Controls like described in this Apple documentation:

https://developer.apple.com/library/archive/documentation/Darwin/Conceptual/NKEConceptual/control/control.html

 

I have to call ctl_register, in my KEXT's start function. Somehow though, the start function I declared in my Lilu plugin is never called.

 

I added this function declaration underneath my init and deinit declarations:

public:
        virtual bool init();
        virtual void deinit();
        virtual bool start(IOService* provider);

And this is the function's body. I see nothing in the logs though.

bool MYKEXT::start(IOService* provider)
{
    DBGLOG("mykext", "STARTING KEXT");
    return true;
}

Do I have to do anything else for the start function to be called? Or is the start function never called in a Lilu plugin maybe? Should I hook the start function of the Kext that I'm modifying with my plugin? I tried that already, but DBLOG output didn't appear in the console logs either.

 

 

EDIT:

If you have a different recommended way to communicate with a Lilu plugin, let me know! I would really appreciate it!

 

EDIT 2:

I got it to work, if anyone in the future reads this and needs help, PM me :)

Edited by unixb0y
Link to comment
Share on other sites

  • 2 months later...

I had Lilu working in Big Sur Beta 3 or 5 (I forget which) on my Mac mini 2018. Now it's not working in Big Sur Beta 6 (installed with WhateverGreen). I know that the patches might not work (I can fix that), but it should not stop booting. If I set -liluoff then it will boot successfully.

 

Has anyone else seen a problem with Lilu + WhateverGreen in Big Sur Beta 6?

 

Link to comment
Share on other sites

9 hours ago, joevt said:

I had Lilu working in Big Sur Beta 3 or 5 (I forget which) on my Mac mini 2018. Now it's not working in Big Sur Beta 6 (installed with WhateverGreen). I know that the patches might not work (I can fix that), but it should not stop booting. If I set -liluoff then it will boot successfully.

 

Has anyone else seen a problem with Lilu + WhateverGreen in Big Sur Beta 6?

 

DisableLinkeditJettison=YES is mandatory for 11.0 when using Lilu.

Edited by Andrey1970
  • Thanks 1
Link to comment
Share on other sites

17 hours ago, Andrey1970 said:

DisableLinkeditJettison=YES is mandatory for 11.0 when using Lilu.

But I'm not using Open Core or Clover. It's a real Mac mini. I want to use Lilu + WhateverGreen for some igfx patches. Do I really need DisableLinkeditJettison?

Link to comment
Share on other sites

  • 2 weeks later...

Hi there

Since a few days, i got a bunch of errors and i'm having troubles building latest Lilu from source

is there something new to be aware of during build or its just me?

 -> Building Lilu......
                             
/download/Lilu/capstone/utils.c:5:10: fatal error: 'Availability.h' file not found
#include <Availability.h>
         ^~~~~~~~~~~~~~~~
1 error generated.
download/Lilu/sha256/sha256.c:16:10: fatal error: 'libkern/libkern.h' file not found
#include <libkern/libkern.h>
         ^~~~~~~~~~~~~~~~~~~
1 error generated.
/download/Lilu/umm_malloc/umm_malloc.c:50:10: fatal error: 'Availability.h' file not found
#include <Availability.h>
         ^~~~~~~~~~~~~~~~
1 error generated.
In file included from /download/Lilu/lzvn/lzvn.c:24:
/download/Lilu/lzvn/lzvn.h:25:10: fatal error: 'Availability.h' file not found
#include <Availability.h>
         ^~~~~~~~~~~~~~~~
1 error generated.
In file included from /download/Lilu/Lilu/Sources/kern_util.cpp:9:
/download/Lilu/Lilu/Headers/kern_util.hpp:14:10: fatal error: 'libkern/libkern.h' file not found
#include <libkern/libkern.h>
         ^~~~~~~~~~~~~~~~~~~
1 error generated.
1 error generated.
error: the following command failed with exit code 1 but produced no further output
CompileC /download/Lilu/build/Lilu.build/Release/Lilu.build/Objects-normal/x86_64/kern_start.o /download/Lilu/Lilu/Sources/kern_start.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
In file included from /download/Lilu/Lilu/Sources/kern_rtc.cpp:8:
In file included from /download/Lilu/Lilu/Headers/kern_rtc.hpp:11:
/download/Lilu/Lilu/Headers/kern_util.hpp:14:10: fatal error: 'libkern/libkern.h' file not found
#include <libkern/libkern.h>
         ^~~~~~~~~~~~~~~~~~~
1 error generated.
1 error generated.
1 error generated.
1 error generated.
1 error generated.
1 error generated.
In file included from /download/Lilu/Lilu/Headers/kern_devinfo.hpp:12:
In file included from /download/Lilu/Lilu/Headers/kern_cpu.hpp:12:
In file included from /download/Lilu/Lilu/Headers/kern_iokit.hpp:12:
/download/Lilu/Lilu/Headers/kern_util.hpp:14:10: fatal error: 'libkern/libkern.h' file not found
#include <libkern/libkern.h>
         ^~~~~~~~~~~~~~~~~~~
1 error generated.
In file included from /download/Lilu/Lilu/Sources/kern_file.cpp:9:
In file included from /download/Lilu/Lilu/Headers/kern_file.hpp:12:
/download/Lilu/Lilu/Headers/kern_util.hpp:14:10: fatal error: 'libkern/libkern.h' file not found
#include <libkern/libkern.h>
         ^~~~~~~~~~~~~~~~~~~
1 error generated.
In file included from /download/Lilu/Lilu/Sources/kern_efi.cpp:8:
/download/Lilu/Lilu/Headers/kern_util.hpp:14:10: fatal error: 'libkern/libkern.h' file not found
#include <libkern/libkern.h>
         ^~~~~~~~~~~~~~~~~~~
1 error generated.
1 error generated.
1 error generated.
In file included from /download/Lilu/Lilu/Sources/kern_crypto.cpp:8:
 /download/Lilu/sha256/sha256.h:17:10: fatal error: 'stdint.h' file not found
#include <stdint.h>
         ^~~~~~~~~~
1 error generated.
/download/Lilu/Lilu/Sources/kern_cpu.cpp:8:
In file included from /download/Lilu/Lilu/Headers/kern_cpu.hpp:12:
In file included from /download/Lilu/Lilu/Headers/kern_iokit.hpp:12:
/download/Lilu/Lilu/Headers/kern_util.hpp:14:10: fatal error: 'libkern/libkern.h' file not found
#include <libkern/libkern.h>
         ^~~~~~~~~~~~~~~~~~~
1 error generated.
In file included from /download/Lilu/Lilu/Sources/kern_compression.cpp:12:
In file included from /download/Lilu/Lilu/Headers/kern_compression.hpp:15:
/download/Lilu/Lilu/Headers/kern_util.hpp:14:10: fatal error: 'libkern/libkern.h' file not found
#include <libkern/libkern.h>
         ^~~~~~~~~~~~~~~~~~~
1 error generated.
1 error generated.
/download/Lilu/hde/hde64.c:10:10: fatal error: 'string.h' file not found
#include <string.h>
         ^~~~~~~~~~
1 error generated.
1 error generated.
1 error generated.

1 error generated.
In file included from /download/Lilu/capstone/arch/X86/X86IntelInstPrinter.c:23:
/download/Lilu/capstone/include/platform.h:27:10: fatal error: 'stdbool.h' file not found
#include <stdbool.h>
         ^~~~~~~~~~~
1 error generated.
1 error generated.
/download/Lilu/capstone/arch/X86/X86Disassembler.c:23:10: fatal error: 'Availability.h' file not found
#include <Availability.h>
         ^~~~~~~~~~~~~~~~
1 error generated.
/download/Lilu/capstone/SStream.c:5:10: fatal error: 'stdint.h' file not found
#include <stdint.h>
         ^~~~~~~~~~
1 error generated.
In file included from /download/Lilu/capstone/MCRegisterInfo.c:17:
/download/Lilu/capstone/MCRegisterInfo.h:23:10: fatal error: 'stdint.h' file not found
#include <stdint.h>
         ^~~~~~~~~~
1 error generated.
In file included from /download/Lilu/capstone/MCInstrDesc.c:4:
/download/Lilu/capstone/MCInstrDesc.h:22:10: fatal error: 'stdint.h' file not found
#include <stdint.h>
         ^~~~~~~~~~
1 error generated.
/download/Lilu/capstone/MCInst.c:5:10: fatal error: 'Availability.h' file not found
#include <Availability.h>
         ^~~~~~~~~~~~~~~~
1 error generated.
/download/Lilu/build/Lilu.build/Release/Lilu.build/DerivedSources/Lilu_info.c:1:10: fatal error: 'mach/mach_types.h' file not found
#include <mach/mach_types.h>
         ^~~~~~~~~~~~~~~~~~~
1 error generated.
error: strip: can't open file: Lilu.kext/Contents/MacOS/Lilu (No such file or directory)
Command PhaseScriptExecution emitted errors but did not return a nonzero exit code to indicate failure
note: Using new build systemnote: Planning buildnote: Constructing build description
** BUILD FAILED **

 

Edited by LAbyOne
Link to comment
Share on other sites

  • 5 weeks later...
  • 3 weeks later...
On 9/8/2020 at 10:33 AM, neemagha said:

Any hope for DRM issues in Big Sur being fixed in the next few months? Thanks for all of your hard work. 

I am also waiting for this. After messing with different smbios, I settled with iMac19,1. If I need drm, I add -igfxvesa boot arg and drm works fine without any issues. During boot there is about 10 secs lag with black screen. That is better than changing smbios or bios settings.

Link to comment
Share on other sites

×
×
  • Create New...