Thinkpad X1 Carbon (3rd Gen) - Could use some hints.

[jcsnider]

Fixed the sleeping, finally. Root cause was the fingerprint scanner trying to turn on whenever the pc is off. It is a good windows feature to auto-sign in by the finger swipe but it killed yosemite.

 

[RehabMan]

Fixed the sleeping, finally. Root cause was the fingerprint scanner trying to turn on whenever the pc is off. It is a good windows feature to auto-sign in by the finger swipe but it killed yosemite.

Disabled the fingerprint reader?

 

[jcsnider]

Sorry, wasn't clear. The Thinkpad BIOS had a Security > Fingerprint Reader > Pre-Desktop Authentication option that I disabled.

 

[RehabMan]

Sorry, wasn't clear. The Thinkpad BIOS had a Security > Fingerprint Reader > Pre-Desktop Authentication option that I disabled.

Ok... yes.. Thinkpads have all sorts of goofy security devices that need to be disabled (TPM, etc).

I say goofy, because all data is available simply by removing the HDD from the computer and doing whatever the crook wants to do with it...

 

[jcsnider]

Last critical thing on my list is the Trackpoint + buttons.

Do the buttons generally map like brightness/sound keys as ACPI events? I am working my way through the VoodooPS2Trackpad.kext right now.

Edit: It was a long shot but enabling the logging of ACPI events didn't post anything when the dedicated trackpoint buttons were clicked. Same for PS2 logging via ioio.

 

[RehabMan]

Last critical thing on my list is the Trackpoint + buttons.

Do the buttons generally map like brightness/sound keys as ACPI events?

No. Buttons on PS2 devices are handled as PS2 mouse events.

 

[jcsnider]

Based off of my initial tests and your GitHub changelog, I'm guessing that the ApplePS2SynapticsTouchPad devices do not have any parameters that can be set to log ids and events to the console (using ioio)?

My first thought was to remap the buttons like I remapped keys on the keyboard, it's not going to be that easy it seems.

 

[RehabMan]

Based off of my initial tests and your GitHub changelog, I'm guessing that the ApplePS2SynapticsTouchPad devices do not have any parameters that can be set to log ids and events to the console (using ioio)?

My first thought was to remap the buttons like I remapped keys on the keyboard, it's not going to be that easy it seems.

The debug version will log PS2 mouse/trackpad packet data to system.log. From there, determine what is wrong and experiment with changes in the code (assuming you know C++)...

 

[jcsnider]

(assuming you know C++)...

More than I'd like to admit, yet not nearly enough.

I in no way did it "properly" but the trackpoint is now moving at a normal speed and the left and right dedicated trackpoint buttons are functioning (clicks, double clicks, right clicks, dragging, etc) and the trackpad is still operating at full functionality. Only things left to touch up on is a weird delay between the end of a drag and the release of a window for the touchpad and getting the middle mouse (scroll button) to work for the trackpoint. I will eventually post my updated .kext but it will be strictly for the 3rd Gen Carbon and maybe a select few similar Thinkpads.

 

[RehabMan]

More than I'd like to admit, yet not nearly enough.

I in no way did it "properly" but the trackpoint is now moving at a normal speed and the left and right dedicated trackpoint buttons are functioning (clicks, double clicks, right clicks, dragging, etc) and the trackpad is still operating at full functionality. Only things left to touch up on is a weird delay between the end of a drag and the release of a window for the touchpad and getting the middle mouse (scroll button) to work for the trackpoint. I will eventually post my updated .kext but it will be strictly for the 3rd Gen Carbon and maybe a select few similar Thinkpads.

"Weird delay" for release of double-tap-hold(drag) is by design (it is a 1 second delay to facilitate 'extended' drags). Try it on a real Mac and you'll see.

Please make your changes in a github fork, and I'll see about pulling in the changes...