Thanks.Īh, I just saw your post on alexandred's github. Also, I was using VoodooI2C 2.2 before, and I didn't have kernel panic on boot and also didn't have it at sleep. Just to confirm: although I didn't experience kernel panic on boot, I do have kernel panic on sleep with the latest VoodooI2C, even if I apply the patch. This is the most stable configuration so far. The startup KPs have stopped, and VoodooI2C 2.2 does not give me KPs after wake from sleep. I have implemented some ACPI patches as recommended by the xxxzc repo to compliment VoodooI2C 2.2. Instead, I am now back to using VoodooI2C and VoodooI2CHID, but version 2.2 instead of 2.3 (due to KPs after wake from sleep). So, as a test, I have removed the plugin from inside of it entirely, and have stopped using VoodooInput as well (since it is dependent upon that plugin to work). UPDATE 3: It appears VoodooPS2Controller was still causing startup KPs, specifically from the VoodooPS2Trackpad plugin. The startup KPs have stopped, and VoodooI2C 2.2 does not give me KPs after wake from sleep.
It could have been triggered by what I was doing, but it is likely that I am still getting random KPs from the newest version of the kext. UPDATE 2: As I was tinkering with workarounds for the touchscreen issue, I got a startup KP from VoodooPS2Controller. I attempted a few workarounds for this, but no success to speak of as of yet. This is somewhat disappointing, but expected. UPDATE: I later realized that VoodooInput does not enable multi-touch support for the 4k touchscreen. Will update if this changes. Still testing for KPs. 4k Touchscreen Multi-touch ***not working (see update below) (working as of update #3).4K Touchscreen (single finger) working!.VoodooPS2Controller.kext version 2.1.2 using VoodooPS2Trackpad plugin from version 2.0.4 VoodooInput.kext version 1.0.3 removed as of update #3 below.VoodooI2CHID.kext (satellite for I2C above).See update #3.įor reference, here are all of the changes I've made to my kexts folder, versus the current repo for 10.14.6: This helped me in two ways: It stabilized my trackpad cursor movement (it is perfect now!) and now that I can use the newest version of VoodooPS2Controller (with old VoodooPS2Trackpad plugin), I have a working caps-lock LED!Īs long as I don’t experience any KPs, this is a big improvement all around. I used an old version of the plugin located inside my original VoodooPS2Controller to replace the newest version that was causing problems. This plugin has been removed entirely as of update #3. I found this out by tinkering with the plugin inside of VoodooPS2Controller, called VoodooPS2Trackpad. Long story short: VoodooPS2Controller was the reason behind my trackpad cursor instability, not VoodooInput. Actually, it looks like I found a solution after all!
0 kommentar(er)
