Just to help save some information here for future use, here's a link I found with a little more info on psmouse proto options:
http://www.idevelopment.info/data/Unix/ ... nKVM.shtml
This isn't really specific to what we're doing but it gives a little explanation of some of the options, and I'm having some trouble turning up a lot of specific information on this. Anyway, here are some of the options:
proto=auto
proto=bare
proto=imps
proto=exps
(Using exps instead of imps has advantages when you like to use your thumb buttons)
proto=raw
proto=base
resetafter=10 (restarts the driver after 10 bad packets)
proto=bare seems like it may serve well for testing when folks have issues -- I'll check to see if it gets just the touch pad and mouse buttons working (no scrolling, etc.). It's supposed to strip it down to a basic mouse.
Obviously, I'm no expert at this, but it would seem that proto=auto is working on most systems (since this is the first piece of hardware of which we are aware that doesn't function properly with it), and it must be autoconfiguring the setting to one of the options above (or some option that is available that I haven't found yet). It sounds almost like there is a problem specific to this hardware that is fooling the driver into thinking it should have the wrong setting. Maybe the hardware support just needs to mature in the kernel.
If anyone is experiencing similar problems with their hardware, please, PLEASE post about it so that we can resolve this more effectively.
rnport, when you have time, please try loading these other options then testing your mouse, and let us know which ones work normally, which don't work at all, and especially tell us if any of them repeat the exact behavior you were having with proto=auto:
rmmod psmouse && modprobe psmouse proto=bare
rmmod psmouse && modprobe psmouse proto=exps
rmmod psmouse && modprobe psmouse proto=raw
rmmod psmouse && modprobe psmouse proto=base
rmmod psmouse && modprobe psmouse proto=any
rmmod psmouse && modprobe psmouse proto=synaptics
I'm not sure if this last one is a valid option or not...
EDIT:
I went trawling through the driver code (psmouse-base.c:
http://lxr.free-electrons.com/source/dr ... use-base.c), and if I'm reading it correctly, these are available options as well:
bare
logitech
thinkps
genius
imps
exps
synaptics
alps
lifebook
trackpoint
touchkit
hgpk
elantech
fsp
cortps
any (any might be the more correct way to call 'auto', though I think it triggers the same series of events to test the hardware for the correct configuration)
Again, I'm leaving these here for future reference, and will test some of them (especially 'any', 'exps' and 'synaptics' on my machine).
EDIT#2:
well, proto=base, raw, and synaptics all came up as invalid arguments, so I guess I misread the driver source, and some of those are not valid.
proto=bare, exps, and imps all work fine with my touchpad and buttons, but don't work with scrolling on the touchpad.
proto=any and proto=auto work perfect, and include touchpad scrolling.