alexandred/VoodooI2CDev

Ben Raz

@ben9923

Why not just pushing the code to another branch?

balopez83

@balopez83

Hi @ben9923 let me know if the “Send Me” zip contains the information you need in the logs. That was generated from Big Sur currently with secure boot turned off since the Goodix kext will not work on any OS with it turned on

balopez83

@balopez83

Let me know if you need anything else or more detail and I will be happy to provide it.

balopez83

@balopez83

Also to your other question, I don’t have access to the original GitHub repo so cannot add a new branch but at some point I will add it to the fork I made of the repo soon when I have some good changes.. Right now I havent made any changes that warrant uploading at this point

balopez83

@balopez83

@ben9923 so one of the guys working on this managed to get it running on Big Sur and secure boot enabled using Voodooi2c ver 2.3 with some minor tweaks. We are still unable to get things working on the latest Voodooi2c but suspect we just don’t understand the difference in how the satellite is supposed to interact now with ver 2.5.2 versus how it interacted in ver 2.3. While it will attach on ver 2.5.2 I suspect it isn’t passing the touch input correctly to be received and used with Voodooi2c. Perhaps something to do with voodooinput but I don’t really know. If you have any thoughts where we should look we would most appreciate it.

Ben Raz

@ben9923

Big Sur + Secure Boot has major issues, as of beta 10
I don't think we should mess with those too much until there are stable machines & Big Sur is not a beta anymore

That doesn't look too good:

2020-10-24 09:14:23.505095-0700 0x276      Default     0x0                  0      0    kernel: Refusing new kext org.coolstar.VoodooGPIO, v1.1: a loaded copy with a different executable UUID is already present.
2020-10-24 09:14:23.523157-0700 0x276      Default     0x0                  0      0    kernel: Refusing new kext com.alexandred.VoodooI2CServices, v1.0: a loaded copy with a different executable UUID is already present.

OC folder not included so I have no idea what's going on there
I'd also disable VoodooPS2Mouse that seems to spam the logs

balopez83

@balopez83

@ben9923 I completely understand, we may be making some more progress getting our kext updated and I also may have found some additional issues with my setup specifically. Also my apologies for forgetting the OC folder. Let me see where we end up with our work over the next week and I’ll try to send an updated complete zip with OC folder. Thanks for your help and advice

CoolStar

@coolstar

I just updated VoodooI2C/VoodooI2CHID and the button on my trackpad no longer works (but the trackpad is otherwise working with tap to click)

was something changed with the MT2 emulation?

Kishor Prins

@kprinssu

@nikhil19rathore99 I have removed you from this Gitter channel, I've dealt with you on Github and it was not pleasant. This is very much how you're loading your kexts. Please do not use the dev channel for support questions.

@coolstar There have changes to automatically get the GPIO pin and some upstream changes in VoodooInput

I am not sure what changes are in VoodooInput as I do not follow the project as closely

CoolStar

@coolstar

@kprinssu I think trackpad click might just be broken in Big Sur

I downgraded VoodooI2C to pre-VoodooInput version and it's still broken

marianopela

@marianopela

@coolstar Not happening to me. It is all behaving exactly the same as on Catalina. Maybe it's something device-specific?

This is the only strange thing I noticed. Not sure it's relevant. Sorry if it's not

Kishor Prins

@kprinssu

@coolstar I am not sure what exactly has changed, from what I know many users have not reported the issue you are facing

it's been quite the opposite, Big Sur simply works and have not reported any major issues

CoolStar

@coolstar

@kprinssu weird, I'll probably boot up a catalina install to double check then

I also noticed some issues with sleep/wake in recent versions of VoodooI2C where trackpad stops working (GPIO interrupts)

I've downgraded to version 2.4.3 which seems to be working decently-ish

CoolStar

@coolstar

actually nvm didn't need to do that... I'm actually kinda annoyed lol. Booted into Windows and click wasn't working there either

turned out the laptop back panel got misaligned somehow and the click physically wasn't working... lol

Kishor Prins

@kprinssu

@coolstar that's weird to hear it was a physical issue, but glad you got working
in regards to sleep/wake, it's been reported and probably related to the changes made within the GPIO controller

relevant PRs:
VoodooI2C/VoodooI2C#390
VoodooI2C/VoodooI2C#385
VoodooI2C/VoodooI2C#370

@coolstar @ben9923 whenever you get the chance, can you one of you guys look at this PR, VoodooI2C/VoodooI2C#398

CoolStar

@coolstar

@kprinssu yeah it's one of the changes between 2.4.3 and 2.4.4

CoolStar

@coolstar

@blankmac @kprinssu do I have to do anything special to get my stylus working in macOS? got a Wacom 50FC here

CoolStar

@coolstar

oh seems like the IOProbeScores for the touch screen / stylus drivers were backwards

flipped it and stylus is working

Kishor Prins

@kprinssu

@coolstar can you narrow down which commit broke things?

it's been about 6 months since those were released so I am not too sure in detail as to what causes your issue

Avery Black

@1Revenger1

hrmm
Palm rejection is harder than I thought it'd be lol

I took a stab at implementing "zones" where fingers get invalidated (until lifted) while typing/using the trackpoint. This seems to work pretty well actually
VoodooSMBus/VoodooRMI#61

I think I'm gonna wait on implementing anything into VoodooInput until I've put it into VoodooRMI's master and gotten feedback on it (or lack of feedback showing it's working?)

marianopela

@marianopela

Hi, have you considered switching to Github Actions?

Kishor Prins

@kprinssu

@ben9923 has brought it up, personally I'm indifferent but I am also not as keen on changing when things are not broken with Circle

blankmac

@blankmac

Seems that they've made some changes to the transducer array in voodooinput?

zhen-zen

@zhen-zen

I think that's just Trackpoint?

blankmac

@blankmac

They’ve also eliminated transducer->id in favor of some attempt at designating a thumb. Haven’t gone through it fully yet though.

Avery Black

@1Revenger1

setting the thumb helps a lot with 4 finger gestures I've found

not sure why it was originally changed though

blankmac

@blankmac

Maybe so. A heads up would have been nice if there wasn’t one. Haven’t been around much lately. LOL. It’s a fundamental change tho that breaks everything that hasn’t been updated to account for it, so....

Ben Raz

@ben9923

@blankmac Should be easy enough, see VoodooI2C implementation:
VoodooI2C/VoodooI2C#333

blankmac

@blankmac

@ben9923 Thank you. :) I updated my wife's Elite and of course the trackpad stopped working. Drove me crazy for a little bit, lol.

Ben Raz

@ben9923

@blankmac Haha as long as we ship VoodooInput with VoodooI2C I guess it's fine

Where communities thrive

People

Repo info

Activity