VoodooRMI

Question

VoodooRMI

yusifsalam opened this issue 4 years ago · 24 comments

Current issue:
When using VoodooRMI instead of VoodooPS2Controller for the trackpad, VoodooInput does not load and the trackpad does not register any input

Answer 1 · 2020-06-26T06:49:15.000Z

Turns out T490 uses F12 for trackpad data, which hasn't been implemented in the VoodooRMI project yet.
Waiting for the implementation for now.

Answer 2 · 2020-07-07T11:42:39.000Z

F12 is now implemented in VoodooRMI, trackpad and trackpoint seem to be working.
More testing required before merging to master.

Answer 3 · 2020-07-17T10:01:50.000Z

VoodooRMI currently does not support the trackpad button, and the reason is not clear. On other trackpads F30 is responsible for the ButtonDevice, but that is not the case with T490. Additionally, the button does not work under linux when using RMI, since the function needed for its functionality (most likely F3A) is missing from the linux source code.
Closing the issue for now, since this is unlikely to be resolved in the near future. Master branch will remain on the VoodooPS2 kext.

Answer 4 · 2020-09-22T12:11:36.000Z

So the F3A function might not be so difficult to implement after all, and the developer of VoodooRMI is very kind to help with that.
Reopening this issue while the work is being done to get the trackpad button working.

Answer 5 · 2020-09-22T19:57:56.000Z

Well that was quick! Trackpad button should work now
dd9c631

Answer 6 · 2020-09-23T12:40:37.000Z

Tested and running great now! I guess we don't need the PS2 config anymore 👍

Answer 7 · 2020-09-24T16:25:18.000Z

I have used the latest EFI folder with voodooRMI and the trackpad buttons are not working. The trackpoint doesn't work either. Am I the only one with this problem?

Answer 8 · 2020-09-24T16:51:04.000Z

Don’t forget you need to update the config.plist too as it’s there all what is on or off. It’s not just a copy of files! #> sudo mail from:Denzil #> Sent successful (elapsed .001 seconds)

…

On 24. Sep 2020, at 19.25, gfalo10 ***@***.***> wrote: I have used the latest EFI folder with voodooRMI and the trackpad buttons are not working. The trackpoint doesn't work either. Am I the only one with this problem? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Answer 9 · 2020-09-24T17:01:15.000Z

I've downloaded all the files from this web t490-macos-master.zip, including the config.plist, updated it with my Serial Number, and copied everything to the EFI folder. It's enough?

Answer 10 · 2020-09-24T17:13:02.000Z

Hum... yeah that should have done it... unless your laptop has a different controller on the trackpad. What CPU gen is your machine? I’m on i7 gen 8 T490. #> sudo mail from:Denzil #> Sent successful (elapsed .001 seconds)

…

On 24. Sep 2020, at 20.01, gfalo10 ***@***.***> wrote: I've downloaded all the files from this web t490-macos-master.zip, including the config.plist, updated it with my Serial Number, and copied everything to the EFI folder. It's enough? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Answer 11 · 2020-09-24T17:17:20.000Z

Can you try pressing once the PrintScreen keyboard key? I found the other day that it actually acts as an off/on switch for the trackpad and trackpoint... #> sudo mail from:Denzil #> Sent successful (elapsed .001 seconds)

…

On 24. Sep 2020, at 20.12, Denzil Ferreira ***@***.***> wrote: Hum... yeah that should have done it... unless your laptop has a different controller on the trackpad. What CPU gen is your machine? I’m on i7 gen 8 T490. #> sudo mail from:Denzil #> Sent successful (elapsed .001 seconds) >> On 24. Sep 2020, at 20.01, gfalo10 ***@***.***> wrote: >> > > I've downloaded all the files from this web t490-macos-master.zip, including the config.plist, updated it with my Serial Number, and copied everything to the EFI folder. It's enough? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub, or unsubscribe.

Answer 12 · 2020-09-24T17:30:24.000Z

I´m on i5 gen8 T490. Trackpad works, but no buttons and no trackpoint. Pressing PrintScreen key nothing works. It's like VoodooRMI.kext before, when both congig.plist were (PS2 and RMI)

Answer 13 · 2020-09-24T17:39:14.000Z

@gfalo10 can you show the output from kextstat | grep -i voodoo

Answer 14 · 2020-09-24T17:59:25.000Z

Can you also show me how you have your trackpad settings on the system preferences? Especially interested in the tap to click tab. ![Screenshot 2020-09-19 at 17 32 56](https://user-images.githubusercontent.com/8342829/93669663-68e77f00-fa9e-11ea-9e82-2374e3a6cc02.png) That's how I have it, but removed the tap to click as it's no longer needed with the RMI kext

…

On 24. Sep 2020, at 20.30, gfalo10 ***@***.***> wrote: I´m on i5 gen8 T490. Trackpad works, but no buttons and no trackpoint. Pressing PrintScreen key nothing works. It's like VoodooRMI.kext before, when both congig.plist were (PS2 and RMI) — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Answer 15 · 2020-09-24T18:04:37.000Z

69 1 0xffffff7f84038000 0x14000 0x14000 as.acidanthera.voodoo.driver.PS2Controller (2.1.6) 428B7521-9084-3B43-BF12-57C762C5BD68 <12 8 6 5 3 1>
80 1 0xffffff7f85ac2000 0x19000 0x19000 de.leo-labs.VoodooSMBus (3.0) 64FF9746-57C5-31F3-9530-95E48367A35C <63 13 6 5 3>
82 1 0xffffff7f85adb000 0x2d000 0x2d000 com.1Revenger1.VoodooRMI (1.1) FF0A1781-AEE9-33DF-B1A8-0B8944B4C8FF <63 6 5 3>
102 0 0xffffff7f84051000 0xd000 0xd000 as.acidanthera.voodoo.driver.PS2Keyboard (2.1.6) BA82B5A4-FB9A-3A7C-AA26-C665B19BBCB0 <69 63 8 6 5 3 1>
109 0 0xffffff7f85b24000 0x1a000 0x1a000 me.kishorprins.VoodooInput (1.0.8) 30A238C9-4C00-3B76-ACA8-127AAFD8A25E <63 6 5 3>
111 0 0xffffff7f85b3e000 0x11000 0x11000 com.VoodooSMBus.VoodooTrackpoint (1) 4EF7C2C3-A957-3BB5-8172-5256CE1F12C4 <63 6 5 3>

Answer 16 · 2020-09-24T18:13:23.000Z

gfalo10 commented 4 years ago

Answer 17 · 2020-09-24T18:52:28.000Z

@gfalo10 everything looks in to be in order, the kexts are loading so everything should work.
We can try to debug a bit more if you're interested, if not you can revert to the config_ps2.plist from a few commits back.
For debugging: copy the repo files to somewhere on your drive (not EFI), then open a new terminal in the kext directory.
unload VoodooRMI sudo kextunload -vvvv -b com.1Revenger1.RMISMBus -b com.1Revenger1.VoodooRMI
change file owner sudo chown -R root:wheel VoodooRMI.kext, sudo chown -R root:wheel VoodooSMBus.kext, sudo chmod -R 755 VoodooSMBus.kext/, sudo chmod -R 755 VoodooRMI.kext/.
load the VoodooRMI kext sudo kextutil -vvvv -d VoodooRMI.kext -d VoodooSMBus.kext VoodooRMI.kext/Contents/PlugIns/RMISMBus.kext
click the trackpoint buttons now, then
log the init message to a file sudo log show --last 1m | grep VRMI > ~/Desktop/log.txt
Attach the log.txt file and I will take a look.

Answer 18 · 2020-09-24T19:11:31.000Z

log.txt
I hope I did well, I am a newbie. It's amazing to have macos working so well on Thinkpads.
Thanks.

Answer 19 · 2020-09-24T19:24:56.000Z

@gfalo10 you took a bit too long to do the log so it didn't catch the init of VoodooRMI :D

could you unload VoodooRMI and load it again (you don't have to change the owner anymore) but this time you can do sudo log show --last 5m | grep VRMI > ~/Desktop/log.txt

Answer 20 · 2020-09-24T20:06:25.000Z

Sorry!!! Here you are:
log.txt

Answer 21 · 2020-09-24T20:56:26.000Z

can you try with this version of VoodooRMI?
https://github.com/VoodooSMBus/VoodooRMI/pull/68/checks?check_run_id=1162679195
click on "artifacts", download the archive, replace the VoodooRMI kext in the kexts folder and then try to load it again (you'll have to run chown and chmod on the new kext file again)

Answer 22 · 2020-09-24T21:46:47.000Z

Hi!! It's works perfect now!! what was the problem?
Thank you!!

Answer 23 · 2020-09-24T22:18:37.000Z

The trackpoint didn't return a success when resetting to default values. I just made it throw out a warning rather than completely stop initializing the trackpoint, which should be fine because we completely reset the trackpoint anyways right before which was successfully happening.

Answer 24 · 2020-09-25T05:20:11.000Z

@1Revenger1 Thanks Avery, helpful as always