I don't think i will be of much help as i'm not really familiar with touchpads. But there are a couple of good suggestions to note. Incidentally, would changing the protocol for your mouse away from "atuo" be a good idea. Sounds like it leaves it up to X to guess. And will be relying on it being able to get that info from the device, which it would appear to be failng at. Never assume that X is really that smart (grin).
I'd backup your existing config as suggested, check over your kernels configuration just for good measure ... ie; sight that the required input device support does exist, then do a stripped reconfigure. Without the touchpad ... get it to work with the PS/2 mouse first, then add the touch pad. And keep it as bare bones as possible. Adding things one at a time untill you find out just which bit is causing it to fail.
Seems like a curious XF86Config file though, different to mine (X v4.3), Id be inclined to add the core pointer stuff to the actual input deve sections too, rather that state it in the server layout section. Such as, mine looks like....
- Code: Select all
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Default Keyboard"
InputDevice "Configured Mouse"
InputDevice "Generic Mouse"
I think towry71s' config is a good example. Two input devices using the same protocol, and with their own device file associations. So that they wont get the chance to step on one another
With my own logitech PS/2 mouse, i was getting a dead curser at first. But the "send core events" "true" setting fixed that.