Arch Linux

forks

Member

Registered: 2013-01-06

Posts: 1

PS/2 Pointing Stick axis problems/configuration

Hi,
I have a Unicomp EnduraPro PS/2 buckling spring keyboard, which comes with an old IBM style pointing stick and mouse buttons.  For clarity:

>>moderator edit: Removed large image. Please read Forum Etiquette: Pasting Pictures and Code. Thanks. --fsckd<<

The problem I am experiencing is that the mouse cursor seems to not recognize the left axis or something.

When pushing the stick to the right, it travels to the right normally, in a straight line. 
When pushing the stick upwards, it travels in a diagonal line to the up-right.
The same for pushing it downwards, it travels down-right. 
When pushing it to the left, the cursor does not move.
The left mouse button appears to do nothing.
The right mouse button acts as the left mouse button.

I have an additional USB mouse, which works perfectly well.

After researching as much as possible, I checked xinput:

─> xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech G500                           	id=8	[slave  pointer  (2)]
⎜   ↳ Logitech G500                           	id=9	[slave  pointer  (2)]
⎜   ↳ PS/2 Generic Mouse                      	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=10	[slave  keyboard (3)]

It appears it is recognizing it as "PS/2 Generic Mouse     id=11" so I checked it's individual properties:

─> xinput list-props 11
Device 'PS/2 Generic Mouse':
	Device Enabled (141):	1
	Coordinate Transformation Matrix (143):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	Device Accel Profile (269):	0
	Device Accel Constant Deceleration (270):	1.000000
	Device Accel Adaptive Deceleration (271):	1.000000
	Device Accel Velocity Scaling (272):	10.000000
	Device Product ID (258):	2, 1
	Device Node (259):	"/dev/input/event14"
	Evdev Axis Inversion (273):	0, 0
	Evdev Axes Swap (275):	0
	Axis Labels (276):	"Rel X" (151), "Rel Y" (152)
	Button Labels (277):	"Button Left" (144), "Button Middle" (145), "Button Right" (146), "Button Wheel Up" (147), "Button Wheel Down" (148)
	Evdev Middle Button Emulation (278):	0
	Evdev Middle Button Timeout (279):	50
	Evdev Third Button Emulation (280):	0
	Evdev Third Button Emulation Timeout (281):	1000
	Evdev Third Button Emulation Button (282):	3
	Evdev Third Button Emulation Threshold (283):	20
	Evdev Wheel Emulation (284):	0
	Evdev Wheel Emulation Axes (285):	0, 0, 4, 5
	Evdev Wheel Emulation Inertia (286):	10
	Evdev Wheel Emulation Timeout (287):	200
	Evdev Wheel Emulation Button (288):	4
	Evdev Drag Lock Buttons (289):	0

And this is the point at which I have no idea how to progress from, is there a way to determine what numbers I need to set these variables to, to straighten this all out?  Anyone have any experience configuring this stuff manually at all?  Google seems to not know much about it, and the only relevant wiki page I was able to find was Mouse Acceleration.  Additionally, the man page for xinput doesn't seem to shed much light on discovering what variables one might need to use.

It also occurred to me that the recent news item regarding modular PS/2 keyboard support may have an effect, so I checked:

─> dmesg -t | grep '^i8042'
i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12

So I don't believe that to be the issue, but I may be wrong.

Last edited by fsckd (2014-04-23 13:35:40)