Not technically an issue but device incompatibility

[theroadw]

I tried it on my Zbook G5 17, but the kext doesn't load. I believe it should work but I'm having a hard time trying to figure out my model info data to add in:

static const struct alps_model_info alps_model_data[]

in file alps.cpp

In OSX IOService the name is <"ALP001E"> and Ubuntu shows input:ALP001E:00044E:1222Mouse

Can you help me try to figure this out?

Thank you!

ZBook Alps Trackpad.zip

[1Revenger1]

[    4.961434] input: ALP001E:00 044E:1222 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-ALP001E:00/0018:044E:1222.0001/input/input12
[    4.961884] input: ALP001E:00 044E:1222 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-ALP001E:00/0018:044E:1222.0001/input/input13
[    4.962181] input: ALP001E:00 044E:1222 as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-ALP001E:00/0018:044E:1222.0001/input/input14

It appears the trackpad works over PS2 and I2C? Have you tried using VoodooI2C+VoodooI2CHID with this device?

Can you please provide a log using VoodooPS2-Alps with log show --last boot | grep -i Voodoo > ~/Desktop/ps2_log.txt?

[theroadw]

Voodoo-trackpad-log.txt

Yes This trackpad is nuts! It has a PS2 that doesn't get loaded in OSX if I2C attaches to it.

I believe If ACPI - OSYS is = < Windows 7 it only publishes the PS2 device If above, then the Alps device becomes active and can/will take over the PS2 version.

Linux is smart and creates this combo device with all the devices bunched up, trackstick, trackpad, ps2, etc... and it works. On Windows only the alps device shows up

I had the idea to trim down a trackstick device with buttons and then use that alongside VoodooI2C, but I may be overthinking it

edit with your version:

[1Revenger1]

The Alps driver handles both the tracks tick and mousepad - they're the same PS2 device. Linux just exposes them as two different devices I think, but they're on the same serial port and driven by the same Linux module. I don't think that trimming down VoodooPS2 to work alongside with the I2C driver at the same time would help with getting the buttons to work. The device would just stop responding over PS2 and only respond to I2C, or sending PS2 commands while it's in I2C mode could completely lock it up (Synaptics is fun with that on the SMBus side).

Hrmm, log doesn't show much unfortunately. Can you try adding msgbuf=1048576 to your boot-args and running sudo dmesg > ~/Desktop/dmesg_log.txt immediately after boot? That should hopefully give a better log

[theroadw]

On it, meantime found this

Interesting... The kext gets loaded and it shows in ioreg but doesn't work...

MacBook Pro.ioreg.zip

Here it is dmsg.log.txt

[1Revenger1]

I need the dmesg log from macOS, not Linux, sorry.

[theroadw]

Sorry about that, here it is:

mac dmesg.log.txt

[1Revenger1]

hrmm, it appears to detect the trackpad correctly as v8, does it work at all? Or is it just the trackpoint? The trackpoint is currently disabled, but I can give you a version with it enabled in the next day or so.

[theroadw]

It doesn't work, buttons don't work at all and trackpad doesn't move the pointer. however if I quickly tap on it, I get the odd click (maybe 1 in 30 taps manages to click)

(the trackpad prefs pane shows up)

[1Revenger1]

VoodooPS2Controller.kext.zip Can you try the above version? Added some more logging, and also provided the debug build. When using dmesg, filter it to just show ALPS as shown below, as otherwise key codes from keyboard presses can be shown. Also test to see if the trackpoint works now. sudo dmesg | grep -i ALPS > ~/Desktop/alps_log.txt

[theroadw]

I tried the new version and it fails to attach altogether, the log file is Zero bytes and there's no mention of any alps or ps2 devices and Ioreg shows nothing loaded. No keyboard, trackpad or trackpoint.