- Joined
- Jan 16, 2014
- Messages
- 25
- Motherboard
- LG GRAM 17Z990
- CPU
- i7-8565U
- Graphics
- UHD 620
- Mobile Phone
A little bit more into my touchpad problem:
I would say I have my DSDT correctly patched, as long as It worked with Mojave.
Did the patching changed from Mojave?
Now... when I try to load VoodooI2C.kext from a desktop folder (EFI's FAT32 cannot be used for security, I understand) here it comes the error:
I find almost nothing on the internet regarding __ZN11IOHIDDevice22_RESERVEDIOHIDDevice12Ev
so I must assume my problem is not common.
The kernel extension loader works somehow. Before I try to load VoodooI2C.kext the system shows:
And after failing to load it says:
Now, my only clue is that somewere I saw something related to System Integrity Protection. I have it disabled:
Let's see what happens if I turn it on. Not sure if it makes any sense, but I am clueless.
I would say I have my DSDT correctly patched, as long as It worked with Mojave.
Did the patching changed from Mojave?
Now... when I try to load VoodooI2C.kext from a desktop folder (EFI's FAT32 cannot be used for security, I understand) here it comes the error:
sudo kextutil -v 6 ./VoodooI2C.kext
Kext user-space log filter changed from 0xff2 to 0xfff.
Kext kernel-space log filter changed from 0xff2 to 0xfff.
Kext library architecture set to x86_64.
Can't stat /AppleInternal - No such file or directory.
Defaulting to kernel file '/System/Library/Kernels/kernel'
Executing: /usr/bin/kmutil load --bundle-path /Users/eduardp/Desktop/esborram/VoodooI2C.kext
Error Domain=KMErrorDomain Code=31 "Error occurred while building a collection:
1: One or more binaries has an error which prevented linking. See other errors.
2: Could not use 'com.alexandred.VoodooI2C' because: Failed to bind '__ZN11IOHIDDevice22_RESERVEDIOHIDDevice12Ev' as could not find a kext with 'com.alexandred.VoodooI2CServices' bundle-id
com.alexandred.VoodooI2C specific:
1: Failed to bind '__ZN11IOHIDDevice22_RESERVEDIOHIDDevice12Ev' as could not find a kext with 'com.alexandred.VoodooI2CServices' bundle-id
" UserInfo={NSLocalizedDescription=Error occurred while building a collection:
1: One or more binaries has an error which prevented linking. See other errors.
2: Could not use 'com.alexandred.VoodooI2C' because: Failed to bind '__ZN11IOHIDDevice22_RESERVEDIOHIDDevice12Ev' as could not find a kext with 'com.alexandred.VoodooI2CServices' bundle-id
com.alexandred.VoodooI2C specific:
1: Failed to bind '__ZN11IOHIDDevice22_RESERVEDIOHIDDevice12Ev' as could not find a kext with 'com.alexandred.VoodooI2CServices' bundle-id
}
sudo kextlibs -undef-symbols VoodooI2C.kext
Password:
For all architectures:
com.apple.iokit.IOACPIFamily = 1.4
com.apple.iokit.IOHIDFamily = 2.0
com.apple.iokit.IOPCIFamily = 2.9
com.apple.kpi.iokit = 20.4
com.apple.kpi.libkern = 20.4
com.apple.kpi.mach = 20.4
For x86_64:
6 symbols not found in any library kext:
__ZN11IOHIDDevice22_RESERVEDIOHIDDevice13Ev
__ZN11IOHIDDevice22_RESERVEDIOHIDDevice12Ev
__ZN10VoodooGPIO9metaClassE
__ZN11IOHIDDevice22_RESERVEDIOHIDDevice15Ev
__ZN11IOHIDDevice22_RESERVEDIOHIDDevice14Ev
__ZN10VoodooGPIO22setInterruptTypeForPinEii
I find almost nothing on the internet regarding __ZN11IOHIDDevice22_RESERVEDIOHIDDevice12Ev
so I must assume my problem is not common.
The kernel extension loader works somehow. Before I try to load VoodooI2C.kext the system shows:
sudo kextstat|grep 'Voodoo'
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
52 0 0 0xb000 0xb000 com.alexandred.VoodooI2CServices (1) DBFA5EBE-2783-30ED-8E39-5829C42D6832 <5 3>
And after failing to load it says:
So some things have been loaded.sudo kextstat|grep 'Voodoo'
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
52 0 0 0xb000 0xb000 com.alexandred.VoodooI2CServices (1) DBFA5EBE-2783-30ED-8E39-5829C42D6832 <5 3>
158 0 0 0x19000 0x19000 me.kishorprins.VoodooInput (1.1.1) 2DBFF028-3A8F-37C9-A5D7-B435F5AA516F <54 6 5 3>
159 0 0xffffff7f9c23d000 0x5000 0x5000 org.coolstar.VoodooGPIO (1.1) 7ED39A4D-2EFD-35AE-9BC6-6215C17D93F1 <13 6 5 3>
Now, my only clue is that somewere I saw something related to System Integrity Protection. I have it disabled:
csrutil status
System Integrity Protection status: unknown (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
BaseSystem Verification: disabled
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.
Let's see what happens if I turn it on. Not sure if it makes any sense, but I am clueless.