They will not do anything when Apple's kexts are not installed.
If the new VoodooI2C release won't be out until you update your system, add the patches instead of removing Apple's kexts again (They'll come back after an OS update).
You won't need those patches with the next VoodooI2C release :)
As @Edd1024 said, there are kext patches available.
Next release won't require any patching/whatever, as VoodooI2C will take over Apple's kexts by itself.
You didn't install any satellite - how are you expecting input?
Your device requires VoodooI2CELAN.
You'll also need to patch for GPIO...
Expected something like the second log you attached in the first message (Has *** Panic Report *** at the beginning, and a backtrace).
Do NOT remove Apple's kexts.
Anyway, how are you expecting it to work when VoodooI2C is not installed?
You'll also need the I2C controllers patch from the...
Please attach a panic log made with keepsyms=1 boot flag :)
Do you mean it panics once laptop is trying to sleep?
Notice -disablegfxfirmware is not needed with recent WEG versions, and nv_disable=1 is not needed with Intel-only graphics.
Can you briefly explain what's wrong, again? @jamesxxx1997
To me it seems like VoodooPS2 is used for trackpad & keyboard, while VoodooI2C + VoodooI2CHID are used for touchscreen & pen.
Please also attach a kernel log for debugging, though I'm not sure what the issue is, still :P
Just make sure...
Your SSDT is wrong...
It adds an external reference to SBFB and SBFG, but they don't exist.
The ones that do exist are located under your trackpad's scope, you must specify the whole path.
Your SSDT is also invalid because your trackpad already has a _CRS method in the DSDT.
Advise the OpenCore manual to learn how you can replace a specific method.
Don't override your whole trackpad DSDT code. Just replace your _CRS method to return the original SBFB, SBFG instead...
If you'd like me to analyze your problem, you'll need to attach all of the requested files. It's...
I believe it's a hardware problem, as it's not 100% compatible with Apple's drivers. Using a wireless card found in an Apple device will probably resolve that.
Never saw anyone having Auto Unlock working correctly with a BCM94352Z.
Like you, I had it enabled, but it didn't actually work. Only...
@northernlights said it's enough to remove it in VoodooGPIO. Does it still lag on your machine when keeping VoodooI2CControllerDriver unmodified?
I also suggested making those methods const and mark them as override, change access to public.
Try that instead of removing it on both classes.
So it's not fixed for you by removing just VoodooGPIO::getWorkLoop()?
Maybe we should mark it as a const function, like the original declaration, and mark as const override in the headers?
IOService.h suggests it should be public.
Please try implementing those changes (const override, public)...