Contribute
Register

New VoodooPS2Controller, Keyboard, Trackpad

Status
Not open for further replies.
Ahhhh!! I was thinking the standard ones would work
 
Thank you so much for your detailed explanation of your PS2 keyboard kext, keyboard layout and so on. The discrepancy in keyboard layout I was experiencing was in Ukelele playing with a custom layout... I couldn't find a ready-made layout whose modifier keys are in the same location as mine -regardless of the keyboard they all seemed follow the Apple model (meta/command/apple keys directly adjacent to the spacebar)- ultimately a completely pointless endeavor. ADD got the better of me!

I love the additional functionality & customization that it has opened up. It took me a while to find the correct set of keycodes and ADB codes I needed- but that's the sort of thing I enjoy. I spent half the night playing with it and testing out different mods.

Good stuff! Thanks again for sharing!!!
 
Trackpad - Increased precision movement (with maybe 2 or 3 finger movement) ?

Is possible to do this with the probook trackpad? maybe with 3 fingers down on trackpad like holding a mouse and all 3 fingers moving as though you were holding and moving a real mouse, but with same response as using a mouse and high sensitive to input?

usage. editing fine detailed graphics applications or hairline markers in audio/video editing.
 
appleiscool said:
Trackpad - Increased precision movement (with maybe 2 or 3 finger movement) ?

Is possible to do this with the probook trackpad? maybe with 3 fingers down on trackpad like holding a mouse and all 3 fingers moving as though you were holding and moving a real mouse, but with same response as using a mouse and high sensitive to input?

usage. editing fine detailed graphics applications or hairline markers in audio/video editing.
Click to expand...

I don't think you're going to get any precision with more than one finger down on the pad. For some jobs, a mouse is best.
 
keep forgetting to post this.

I see this on my console log every once in awhile. do you know what it may be caused by?

btw, I'm still on 0315
Code: 
6/30/13 10:18:17.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 10:18:17.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 10:18:17.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (38) from PS/2 controller
6/30/13 10:18:17.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (10) from PS/2 controller
6/30/13 10:21:45.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 10:21:45.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 10:21:45.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (36) from PS/2 controller
6/30/13 10:21:45.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (16) from PS/2 controller
6/30/13 3:04:45.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 3:04:45.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 3:04:45.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (57) from PS/2 controller
6/30/13 3:04:45.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (1c) from PS/2 controller
6/30/13 3:46:00.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 3:46:00.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 3:46:00.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (36) from PS/2 controller
6/30/13 3:46:00.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (18) from PS/2 controller
6/30/13 6:43:38.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 6:43:38.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 6:43:38.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (57) from PS/2 controller
6/30/13 6:43:38.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (12) from PS/2 controller
6/30/13 8:53:41.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 8:53:41.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 8:53:41.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (59) from PS/2 controller
6/30/13 8:53:41.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (18) from PS/2 controller

oops sorry... wrong thread again. intended to post on the generic thread
 
ikkoku said:
keep forgetting to post this.

I see this on my console log every once in awhile. do you know what it may be caused by?

btw, I'm still on 0315
Code: 
6/30/13 10:18:17.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 10:18:17.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 10:18:17.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (38) from PS/2 controller
6/30/13 10:18:17.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (10) from PS/2 controller
6/30/13 10:21:45.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 10:21:45.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 10:21:45.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (36) from PS/2 controller
6/30/13 10:21:45.000 AM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (16) from PS/2 controller
6/30/13 3:04:45.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 3:04:45.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 3:04:45.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (57) from PS/2 controller
6/30/13 3:04:45.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (1c) from PS/2 controller
6/30/13 3:46:00.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 3:46:00.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 3:46:00.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (36) from PS/2 controller
6/30/13 3:46:00.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (18) from PS/2 controller
6/30/13 6:43:38.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 6:43:38.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 6:43:38.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (57) from PS/2 controller
6/30/13 6:43:38.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (12) from PS/2 controller
6/30/13 8:53:41.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected reset (aa 00) request from PS/2 controller
6/30/13 8:53:41.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (d0) from PS/2 controller
6/30/13 8:53:41.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (59) from PS/2 controller
6/30/13 8:53:41.000 PM kernel[0]: ApplePS2SynapticsTouchPad: Unexpected byte0 data (18) from PS/2 controller

oops sorry... wrong thread again. intended to post on the generic thread
Click to expand...

It means your trackpad is spontaneously resetting itself. Synaptics documents that this can happen:

"On rare occasions, the TouchPad may experience a spurious reset, often due to a power supply brownout or an electrostatic discharge (ESD). If this happens, the TouchPad will mostly reset itself as if after a power-on reset. If data reporting was enabled before the spurious reset, the TouchPad will attempt to come up re-enabled and without an $AA, $00 announcement so that the host does not experience an interruption of service. However, any other PS/2 settings or TouchPad mode byte settings will be lost. In particular, note that a spurious reset will cause the TouchPad to spontaneously revert from Absolute to Relative mode. If the host notices the TouchPad spontaneously reverting to the Relative mode packet format, it should reinitialize the TouchPad in the same manner as at power-up."

I have code in there to detect it, but the code I originally wrote to perform the reset was causing problems/lockups. And I haven't had time to revisit it. Part of the problem is that my trackpad never demonstrates this, so I'm not able to properly test for it.

As I'm sure your trackpad is disabled after this event, you can reset it by putting your laptop to sleep, then waking it.
 
RehabMan said:
It means your trackpad is spontaneously resetting itself. Synaptics documents that this can happen:

"On rare occasions, the TouchPad may experience a spurious reset, often due to a power supply brownout or an electrostatic discharge (ESD). If this happens, the TouchPad will mostly reset itself as if after a power-on reset. If data reporting was enabled before the spurious reset, the TouchPad will attempt to come up re-enabled and without an $AA, $00 announcement so that the host does not experience an interruption of service. However, any other PS/2 settings or TouchPad mode byte settings will be lost. In particular, note that a spurious reset will cause the TouchPad to spontaneously revert from Absolute to Relative mode. If the host notices the TouchPad spontaneously reverting to the Relative mode packet format, it should reinitialize the TouchPad in the same manner as at power-up."

I have code in there to detect it, but the code I originally wrote to perform the reset was causing problems/lockups. And I haven't had time to revisit it. Part of the problem is that my trackpad never demonstrates this, so I'm not able to properly test for it.

As I'm sure your trackpad is disabled after this event, you can reset it by putting your laptop to sleep, then waking it.
Click to expand...

ok. thanks... I wonder if this has to do with the dsdt edits/ssdt I've been playing with.

also, the trackpad is not disabled after the event. I do not need to reboot or put the laptop to sleep to regain trackpad use. If I didn't look at the logs, it seems transparent.
 
ikkoku said:
ok. thanks... I wonder if this has to do with the dsdt edits/ssdt I've been playing with.

also, the trackpad is not disabled after the event. I do not need to reboot or put the laptop to sleep to regain trackpad use. If I didn't look at the logs, it seems transparent.
Click to expand...

Hmm... weird. Just bad data coming from ps2 port then... and bad data that just happens to match reset announcement sequence (AA 00). I'm not going to worry about it then. There is nothing I can do about bad data from the trackpad other than ignore it.
 
I *HAD* it disabled...but at one time during my many freezes on the OS, it rebooted and I could not disable it any more...even after re-installing the kext file....
 
adambuble2 said:
I *HAD* it disabled...but at one time during my many freezes on the OS, it rebooted and I could not disable it any more...even after re-installing the kext file....
Click to expand...

Try an EC reset: Shutdown, remove battery, remove AC plug, hold power button 30 sec, put everything back & restart.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top