Closed VinylNerd closed 2 years ago
1Revenger1
commented
2 years ago are you able to provide a log using DebugEnhancer.kext and sudo dmesg | grep -i VRMI > ~/Desktop/log.txt? This requires the debug version of VoodooRMI, and you'll want to try and not use the trackpad until you run the command after booting. There is a lot of spam in the log when using the trackpad which can overwrite the logs from bootup.
VinylNerd
commented
2 years ago @1Revenger1 thanks, ill do that now, just to be clear the debug version is VoodooRMI.kext.dSYM right?
1Revenger1
commented
2 years ago No, the dSym are debug symbols not useful to most people. Download the debug version from the release page.
VinylNerd
commented
2 years ago thanks, here you go
[ 3.816503]: VRMI - Info: Found PS2 Trackpad driver! Waiting for registerService()
[ 3.816773]: VRMI - Debug: Too early notification - No VoodooInput on PS2 yet
[ 4.190018]: VRMI - Debug: Found GPIO data!
[ 4.190024]: VRMI - Info: VoodooPS2Trackpad finished init, starting...
[ 7.131649]: ALF, old data swfs_pid_entry
1Revenger1
commented
2 years ago Looks like the buttons are found. Mind sending a log after trying to use the track point and buttons?
VinylNerd
commented
2 years ago yes, i rebooted and did that for you
first track point (small red dot on keyboard) just to be clear then all 3 buttons a few times each and then trackpoint again
[ 3.768667]: VRMI - Info: Found PS2 Trackpad driver! Waiting for registerService()
[ 3.768928]: VRMI - Debug: Too early notification - No VoodooInput on PS2 yet
[ 4.141999]: VRMI - Debug: Found GPIO data!
[ 4.142006]: VRMI - Info: VoodooPS2Trackpad finished init, starting...
[ 6.610483]: ALF, old data swfs_pid_entry
1Revenger1
commented
2 years ago Log doesn’t look any different. You did it after right? No need to reboot for these logs Edit: you can upload the file itself if you drag and drop it in here btw.
VinylNerd
commented
2 years ago yes i did the log after, is there anything else i can do to try to help? are these logs getting you anywhere?
1Revenger1
commented
2 years ago The log you gave is helpful because it recognizes the buttons are there. I need a log which shows the track point and buttons being used though to see why it isn’t working. If you could try again, that’d be helpful.
1Revenger1
commented
2 years ago It looks like F30 isn't generating interrupts when clicking with the trackpoint buttons. What you could try is to hold them down and then click the clickpad at the same time to see if it registers (atleast in the logs). You said they don't work in windows, and it may be some configuration with the trackpad itself that we can't change in VRMI. I'll look around a bit and see though.
1Revenger1
commented
2 years ago hrmmm, they still read as "Up", so something is wrong with them. I'll look further I guess.
VinylNerd
commented
2 years ago here is some more logs for you, happy to do anything else, i think it might be best to verify i have same hardware ID as someone else to verify my part is genuine, but not sure best way to do that as i feel the kexts may be spoofing the HWID or something like that, however my product feels quality and to be genuine. its my understanding that my trackpad should be supported by the kext yes?
log.txt
VinylNerd
commented
2 years ago it seems my trackpad is not genuine as another user tried my EFI with his synaptics and said it works, i have orderd a new one from amazon and will report back if i have luck, however the fact we can see the buttons being pressed is still confusing, only had to open my laptop about 5 times now to try to troubleshoot this lol, thought possibly i damaged the cable at first and when i went back to alps i would also loose the buttons but when i go back to alps it works as expected
amazon delivery comes tomorrow so will report back soon
VinylNerd
commented
2 years ago 
1Revenger1
commented
2 years ago Not really sure if it’s an authenticity problem, it’s probably something related to how the trackpad is configured internally or wired up to your device. It sees that the buttons are there, but can not figure out if they’re pressed down. Because it never sees that they are pressed down, it never sends an interrupt/notification to a driver. I’m looking at some things to see if there is a way to configure it though. Probably won’t have anything to test until later this week once finals are done, if you are willing to test. May just be worth replacing it though and see if it works and leaving it alone.
VinylNerd
commented
2 years ago i see, that makes sense. well im replacing it, but i have been fully refunded without return so can keep this to test, my new one arrives today, will report back later today after ive tried it out
VinylNerd
commented
2 years ago 
this trackpad works, i noticed the clips under the left and right buttons are red rather than black in the one wich did not work for me, thanks for help
Hello, please forgive my lack of logs and IO reg data per my first post, as it seems the way this should be setup is literally explained different in 3-4 places, and i have multiple guides telling me what to do with nothing working whatsoever.
basically i seen some posts where people said it only worked for them with voodoo RMI 1.2 and older, and im assuming the guide is updated for the most recent version, since the way the kexts are included in builds have been changing it seems impossible for me to verify how i should be attemtping this.
trackpad works, but 3 buttons dont
they also dont work in windows, but that also seems to be a problem, someone on reddid has said its working for them with voodooRMI and voodoosmbus kext aswell as voodoops2 and disable voodoo input, but it is not working for me.
this situation is extra confusing because at this point since its not working im feeling the 3 buttons are broken Last login: Fri Dec 3 13:45:36 on ttys000 Connor@Connors-MBP-2 ~ % kextstat | grep Voodoo Executing: /usr/bin/kmutil showloaded No variant specified, falling back to release 78 1 0 0x18000 0x18000 de.leo-labs.VoodooSMBus (3.0) C7EA611A-7A6E-3210-800F-79585B09468C <14 6 5 3> 88 1 0 0x29000 0x29000 com.1Revenger1.VoodooRMI (1.3.4) E101F26E-9935-3092-AFF4-7796D1B84130 <6 5 3> 118 0 0 0x19000 0x19000 me.kishorprins.VoodooInput (1.1.3) 374A88BF-5D62-3ED2-8E75-6A331AF58A2E <61 6 5 3> Connor@Connors-MBP-2 ~ SynapticsTrackpadTroubleshoot.zip %